WO2012167480A1

WO2012167480A1 - Method, device and system for detecting and establishing local route

Info

Publication number: WO2012167480A1
Application number: PCT/CN2011/077273
Authority: WO
Inventors: 王岩; 胡伟华
Original assignee: 华为技术有限公司
Priority date: 2011-07-18
Filing date: 2011-07-18
Publication date: 2012-12-13
Also published as: CN103004151B; CN103004151A

Abstract

Disclosed are a method, device and system for detecting and establishing a local route, relating to the field of communications able to reduce the transmission time delay, and improving user experience. A method for detecting a local route includes: searching for the context information corresponding to the IP address of source UE and that corresponding to the IP address of destination UE in a context look-up table; detecting whether or not the network elements on the bearer links of the source UE and the destination UE have the ability to establish a local route; and, if they have the ability to establish a local route, a local route request will be sent to the network elements on the bearer links of the source UE and the destination UE. A method for establishing a local route includes: receiving a local route request; establishing a binding relationship between a data message sent from source UE to destination UE and a downlink bearer of the destination UE and establishing a binding relationship between a data message sent from the destination UE to the source UE and a downlink bearer of the source UE. The embodiments of the present invention are mainly used in a routing device of an EPS system.

Description

Local route detection, establishment method, device and system

The present invention relates to the field of communications, and in particular, to a method, an apparatus, and a system for detecting, establishing, and configuring a local route. Background technique

The EPS (Evolved Packet System) system is an evolution network corresponding to the SAE (Service Architecture Evolution) group. It optimizes network performance from the perspective of network architecture. After the UE (User Equipment) is attached to the EPS system, it is carried by the eNodeB (Evolved NodeB, Evolved NodeB, SGW (Serving Gateway), PGW (Packet Data Network Gateway) , to connect to the external PDN network. Currently, when the data transmission between the UEs is implemented, the data sent by the source UE needs to be transmitted to the PGW via the established bearer, and is sent by the PGW to the external PDN network, and after the external PDN network loops back, The PGW transmits the data to the destination UE. In the process of implementing the above technical solutions, the inventors have found that at least the following problems exist in the prior art: With the development of technology, communication services between UEs in an EPS system are becoming more and more abundant, and the requirements for communication speed between UEs are increasing. The higher the existing EPS system cannot provide the intra-network local route between the source UE and the destination UE for data transmission; even if the source UE and the destination UE are connected in the same SGW or eNodeB, or the source UE and the destination UE are respectively connected in the adjacent In the case of different SGWs or eNodeBs, the data traffic flows that communicate with each other also need to exchange data through the external PDN network. In this scenario, the communication route between the UEs is not optimized, which increases the transmission burden of the mobile operator's backhaul network and the transmission network and the processing load of the PGW gateway, and increases the transmission delay and reduces the user service experience. Summary of the invention

Embodiments of the present invention provide a method, a device, and a system for detecting, establishing, and reducing a local route. In order to achieve the above object, the embodiment of the present invention uses the following technical solution: In an aspect, the embodiment of the present invention provides a method for detecting a local route, including: searching for a source UE in a context query table that generates an IP address and a context association. Context information corresponding to the IP address and context information corresponding to the IP address of the destination UE;

Detecting, in the context information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has a local route establishment capability;

When the local routing establishment capability is available, the local routing request is sent to the source UE and the network element on the destination UE bearer link, so that the source UE and the destination UE carry the local element routing configuration, and the source UE and the source UE The data packets between the destination UEs are locally routed.

On the other hand, an embodiment of the present invention provides a method for establishing a local route, including: receiving a local routing request;

Establish a binding relationship between the data packet sent by the source UE and the destination UE to the downlink bearer of the source UE, and establish a binding relationship between the data packet sent by the source UE and the source UE to the downlink bearer of the source UE, so that the source UE and the destination are configured. The data packets between the UEs are locally routed according to the binding relationship.

In an aspect, the embodiment of the present invention provides a local routing detection apparatus, including: a context information searching unit, configured to search for a context information corresponding to an IP address of a source UE and a destination UE in a context query table that generates an IP address and a context association. Context information corresponding to the IP address;

The local routing capability detecting unit is configured to detect, in the context information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has a local route establishing capability;

a routing request sending unit, configured to send a local routing request to the source UE and the network element on the destination UE bearer link when the local routing establishment capability is enabled, so that the source UE and the destination UE carry the local element of the network element on the bearer link Configure and locally route data packets between the source UE and the destination UE.

On the other hand, an embodiment of the present invention provides a device for establishing a local route, including: a route request receiving unit, configured to receive a local route request;

The local route establishing unit is configured to establish a binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE, and establish a binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE. To enable data packets between the source UE and the destination UE. Local routing based on the binding relationship.

In another aspect, an embodiment of the present invention provides a system for implementing local route establishment, including a detecting device and a establishing device, where the detecting device is configured to send a local routing request to the establishing device, where the establishing device is configured to receive After the local routing request is made, a local route is established. The method for detecting, establishing, and the local route of the local route provided by the embodiment of the present invention is such that when the source UE and the destination UE are connected to the same SGW or the eNodeB, or the source UE and the destination UE are respectively connected to different SGWs or eNodeBs, The local routing path can be established, so that the data message sent by the source UE to the destination UE does not need to be looped back through the external PDN network, thereby reducing the transmission delay, improving the user experience, and reducing the processing load of the PGW.

DRAWINGS

1 is a schematic diagram of data packet transmission between a source UE and a destination UE via an external PDN network in the prior art;

2 is a flowchart of a method for detecting a local route according to Embodiment 1 of the present invention; FIG. 3 is a flowchart of a method for establishing a local route according to Embodiment 1 of the present invention; FIG. 4 is a flowchart of a local route according to Embodiment 2 of the present invention; FIG. 5 is a signaling flowchart of a method for establishing a local route according to Embodiment 2 of the present invention; FIG. 6 is a signaling flowchart of a method for establishing a local route according to Embodiment 3 of the present invention; A flowchart of a method for establishing a local route in Embodiment 4 of the present invention;

8 is a flowchart of a method for establishing a local route according to Embodiment 5 of the present invention;

9 is a block diagram of a local route detecting apparatus in Embodiment 6 of the present invention;

Figure 10 is a block diagram of another local routing detection apparatus based on Figure 9; Figure 1 is a block diagram of a local routing establishment apparatus in Embodiment 6 of the present invention;

1 is a block diagram of a local routing unit in Embodiment 6 of the present invention;

FIG. 13 is a block diagram of another local routing unit in Embodiment 6 of the present invention; FIG.

FIG. 14 is a schematic diagram of a system for implementing local route establishment in Embodiment 7 of the present invention; FIG. FIG. 15 is a schematic diagram of a system composed of a source SGW, a destination SGW, and a PGW according to Embodiment 7 of the present invention;

FIG. 16 is a schematic diagram of a network application scenario in Embodiment 2 of the present invention;

FIG. 17 is a schematic diagram of a network application scenario in Embodiment 3 of the present invention.

detailed description

The technical solutions of the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings of the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present invention without creative work are within the scope of the present invention.

A common EPS system is shown in Figure 1. After the UE is attached to the EPS system, the UE is connected to the external PDN network through the bearer of the eNodeB, the SGW, and the PGW. In the scenario of data packet transmission and reception between the source UE and the destination UE as shown in FIG. 1, the data packet is also transmitted through the external PDN network after being carried by the PGW. The network between the eNodeB and the SGW is a backhaul network, and the network between the SGW and the PGW is a dedicated bearer transmission network. If the source UE and the destination UE can perform local routing within the range of the backhaul network, and the data packet between the source UE and the destination UE is not sent to the PGW, the transmission network bandwidth resource can be effectively saved and the delay of data transmission can be reduced. Example 1

An embodiment of the present invention provides a method for detecting a local route. As shown in FIG. 2, the method includes the following steps:

The context information corresponding to the IP address of the source UE and the context information corresponding to the IP address of the destination UE are searched in the context query table that generates the IP address and the context.

In the data item of the context query table, the association between the IP address of the source UE/destination UE and the context information of the IP address of the corresponding source UE/destination UE is recorded, that is, the corresponding context information can be queried by using the IP address. The context information includes network element information on a link of a PDN connection established by the source UE/destination UE. For example, the PDN connection established by UE 1 is PDN1. The context information related to the PDN1 of the UE 1 includes: information about the bearer network element (eNodeB, SGW, PGW, etc.) on the PDN 1 bearer link (the IP address of the SGW/eNodeB, and the bearer network element after receiving the data packet) Forward the address of the destination NE and its bearer ID, etc.).

And detecting, in the context information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has a local route establishment capability.

The network element on the source UE and the destination UE bearer link may be an SGW that simultaneously carries the PDN connection between the source UE and the destination UE, or may be an eNodeB that simultaneously carries the PDN connection between the source UE and the destination UE, or may be a bearer source. The source SGW of the PDN connection of the UE and the destination SGW of the PDN connection of the destination UE, or the source eNodeB of the PDN connection of the source UE and the destination eNodeB of the PDN connection of the destination UE.

Specifically, the local routing establishment capability may be implemented by a local routing parameter manually set in the network element. When the local routing parameter exists, the network element has a local routing establishment capability, and when the local routing parameter does not exist, When the network element does not have the local route establishment capability. Certainly, the local routing parameter may also be configured with multiple status values, for example, the value of the status value is set to 0 or 1. When the status value is 1, the network element has local routing establishment capability, and when the status value is 0, the network element does not have the ability to establish local routes.

For example, the PDN connection established by UE 1 is PDN1, PDN 1 is carried by SGW1, the PDN connection established by UE2 is PDN2, and PDN2 is carried by SGW2. And both PDN1 and PDN2 are carried via the same PGW (PGW-1). The status value of the local routing parameter 1 in the SGW1 is recorded in the context information of the UE 1, and the status value of the local routing parameter 1 in the SGW2 is also recorded. You can set the NE to have the local route establishment capability when the status value is 1. When the status value is 0, the NE does not have the local route establishment capability. When PGW-1 detects that at least one of the local routing parameter 1 and the local routing parameter 2 has a status value of G, the current process is terminated. When the status values of local route parameter 1 and local route parameter 1 are both 1, go to step 1 03.

1 03. Send a local routing request to the source UE and the network element on the destination UE bearer link. The local routing request is received, and the local NE and the network element on the destination UE bearer link are locally configured, so that the data between the source UE and the destination UE is locally routed.

The UE 1 and UE 2 in step 102 are still taken as an example for illustration. The PGW-1 will send a local routing request to the source UE with the local route establishment capability and the network element on the destination UE bearer link on the PDN connection path of the UE 1 and the UE 2 respectively. SGW1 and SGW2 receiving the local routing request will perform local routing configuration separately to implement local transmission of data packets between UE1 and UE2. Routing.

In addition, the embodiment of the present invention further provides a method for establishing a local route. As shown in FIG. 3, the method includes the following steps:

201. Receive a local routing request.

202. Set a binding relationship between the data packet sent by the source UE and the destination UE to the downlink bearer of the destination UE, and establish a binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE.

A binding relationship between the data packet sent by the source UE and the destination UE is established, and the data packet sent by the source UE is sent to the destination UE through a local route. The binding relationship between the data packet sent by the UE to the source UE and the downlink bearer of the source UE is established, so that the data packet sent by the destination UE is sent to the source UE through the local route. For example, the PDN connections of UE1 and UE2 are carried over the same SGW (SGW3), and SGW3 is connected to PGW-2. After the PGW-2 performs the local routing feasibility detection method, the local routing request is sent to the SGW3. After receiving the local routing request from the PGW-2, the SGW3 establishes a binding relationship between the data packet sent by the UE1 to the UE2 and the downlink bearer of the UE2, and the binding relationship between the data packet sent by the UE2 to the UE1 and the downlink bearer of the UE1. After that, the UE1 sends a data packet destined for UE2 to SGW3, and then forwards it to UE2 by SGW3. After the data packet returned by UE2 to UE1 is transmitted to SGW3, it will also be forwarded by SGW3 to UE1 without having to enter through PGW-2. The external PDN network loops back.

The method for detecting a local route and the method for establishing a local route provided by the embodiment of the present invention, by detecting and establishing a local route, the data message sent by the source UE to the destination UE and the data returned by the destination UE to the source UE are both The loopback of the external PDN network is not required, thereby reducing the transmission delay, improving the user experience, and reducing the processing load of the PGW.

Example 2:

In the EPS system, the PDN connection of the source UE and the PDN connection of the destination UE are respectively carried by the source SGW and the destination SGW, and the source SGW and the destination SGW are connected to the same PGW. The active MME is set on the PDN connection path of the source UE, and the destination MME is set on the PDN connection path of the destination UE. The network architecture is shown in FIG. 16. In this scenario, the embodiment of the present invention provides a method for detecting a local route. As shown in FIG. 4, the method includes the following steps:

301. After the source UE/destination UE establishes a PDN connection, the PGW records the correspondence between the IP address of the source UE/destination UE and the context information generated after the PDN connection is established in the context query table. Relationship.

After the source UE/destination UE establishes its own PDN connection, the PGW stores the context information of the PDN connection. The context information includes network element information of a PDN connection established by the source UE/destination UE. For example, the PDN connection established by UE 1 is PDN1. The context information related to the PDN1 of the UE 1 includes: information about the network element (eNodeB, SGW, PGW, etc.) on the link to which the PDN1 is connected (the IP address of the SGW, and the forwarding destination address after the network element receives the data packet) And bearer ID, etc.). The PGW records the correspondence between the IP address of the source UE/destination UE and the context information generated after the PDN connection is established to the PGW's own context query table.

302. Obtain, from the data sent by the source UE, the IP address of the source UE and the IP address of the destination UE.

When the source UE has started to send data packets, the data packets sent by the source UE will be sent to the external PDN network through the PGW for loopback. After receiving the data packet sent by the source UE, the PGW obtains the IP address used by the source UE and the IP address used by the destination UE from the data packet sent by the source UE.

303. Search, in the context query table, context information corresponding to the IP address of the source UE and context information corresponding to the IP address of the destination UE.

And determining, by the found source information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has a local route establishment capability.

When the PGW detects that at least one of the source SGW and the destination SGW does not have the local route establishment capability, the current process is terminated. When both the source SGW and the destination SGW have the local route establishment capability, the process proceeds to step 305.

305. Detect whether the source UE and the destination UE meet the local routing policy.

The local routing policy specifies whether to allow local execution of data packets sent and received by the UE. The type of data message that performs local routing. For example, the local routing policy prohibits a type of user that is legally intercepted by the operator to perform local routing. The local routing policy allows local routing to be performed for voice-type data packets communicated between the UEs.

When the PGW does not configure the local routing policy, step 305 further includes:

305- PGW) The Policy and Charging Rule Function (PCRF) sends a routing policy request message, where the routing policy request message carries a user identifier (such as IMSI) or an IP address of the source UE and the destination UE.

305_2. The PGW receives a corresponding local routing policy that is obtained by the PCRF according to the user identifier or the IP address of the source UE and the destination UE.

The PGW can detect whether the source UE and the destination UE meet the local routing policy set in the PGW or the local routing policy returned by the PCRF. When at least one of the source UE and the destination UE does not comply with the local routing policy, the current process is terminated; When the UE meets the local routing policy, step 306 is performed.

306. Send a local routing request to the source SGW.

After the PGW sends a local routing request to the source SGW, the embodiment of the present invention further provides a method for establishing a local route. As shown in FIG. 5, the method includes the following steps:

401. The source SGW receives a local routing request sent by the PGW.

The local routing request includes the identifier of the source UE, the identifier of the destination UE, the identifier of the source UE, the identifier of the destination UE, the IP address of the source SGW, and the IP address of the destination SGW. If the PDN connection of the UE is required, If the NAT address translation is performed, the local routing request also needs to include the NAT mapping information. If the data packet that performs the local routing is separately charged, the local routing request needs to include the charging information, such as the charging identifier. Billing method, etc.

402. After receiving the local routing request, the source SGW forwards the local routing request to the source MME.

403. After receiving the local routing request from the source SGW, the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW.

The source MME sends a tunnel establishment request from the source SGW to the destination SGW to the destination SGW according to the IP address of the destination SGW in the local routing request from the source SGW.

The forwarding tunnel request for establishing the source SGW to the destination SGW includes: an identifier of the destination UE, The downlink bearer identifier of the destination UE.

4 04. Purpose The SGW allocates a forwarding tunnel identifier from the source SGW to the destination SGW.

The binding relationship between the forwarding tunnel identifier and the downlink bearer identifier of the destination UE is established in the destination SGW.

After the forwarding tunnel identifier is allocated, the destination SGW searches for the context of the destination UE according to the destination UE identifier, and records the binding relationship between the forwarding tunnel identifier and the destination UE downlink bearer identifier in the context.

4 06. Return the identifier of the forwarding tunnel from the source SGW to the destination SGW to the source MME.

4 07. The source MME returns the forwarding tunnel identifier of the source SGW to the destination SGW to the source SGW.

The binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE is established in the source SGW.

After receiving the identifier of the forwarding tunnel allocated by the destination SGW, the source SGW establishes a binding relationship between the identifier of the forwarding tunnel and the data packet sent by the source UE to the destination UE, so that the data packet of the source UE passes through the forwarding tunnel. Pass to the destination UE. After the source SGW establishes a binding relationship between the identifier of the forwarding tunnel and the data packet sent by the source UE to the destination UE, the source SGW may send a source UE to the destination UE local route establishment complete message to the PGW.

The data packet sent by the source UE to the destination UE and the data packet sent by the source UE to other destinations may be simultaneously transmitted in the uplink bearer of the source UE, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the source UE to the destination UE may be: the IP address of the source UE, the port number of the source UE, and the IP address of the destination UE in the data packet sent by the source UE to the destination UE. The address, the port number of the destination UE, and the transmission protocol between the source UE and the destination UE are used as a quintuple, and the identifier of the forwarding tunnel and the source UE are sent to the destination UE according to the correspondence between the quintuple and the downlink bearer of the destination UE. Binding relationship of data packets. In the source SGW, the data packet that meets the description of the quintuple can be filtered by a data stream filtering device (such as TFT, Tr a f f i c F ow Temp a t e, service flow template).

After the foregoing steps 401 to 408 are completed, the local route that the source UE sends a data packet to the destination UE is established. After the data packet is transmitted to the source SGW by the source UE, the source SGW encapsulates the data packet with the identifier of the forwarding tunnel according to the binding relationship between the identifier of the forwarding tunnel allocated by the destination SGW and the data packet sent by the source UE to the destination UE. And transmitting to the destination SGW, after the destination SGW receives the data packet, according to the identifier of the forwarding tunnel and the destination UE The binding relationship carried by the line sends the data packet to the destination UE.

In addition, the PGW also establishes a local route for the destination UE to send data packets to the source UE. Including Step 4 09 to Step 4 1 6 :

4 09. Purpose The SGW receives the local routing request sent by the PGW.

After the local routing establishment of the data message sent by the source UE to the destination UE is completed, the PGW may send a local routing request to the destination SGW where the PDN connection of the destination UE is located after step 408. Of course, the PGW may also first establish a local route for the destination UE to send data packets to the source UE, and then establish a local route for the source UE to send data packets to the destination UE, which is not limited by the embodiment of the present invention.

4 1 0. Destination After receiving the local routing request, the SGW forwards the local routing request to the destination MME.

After the local MME receives the local routing request from the destination SGW, it sends a forwarding tunnel establishment request to the source SGW to the source SGW.

4 1 2. The source SGW allocates a forwarding tunnel identifier from the destination SGW to the source SGW.

The binding relationship between the identifier of the forwarding tunnel and the identifier of the downlink bearer of the source UE is established in the source SGW.

4 14. Return the forwarding tunnel identifier of the destination SGW to the source SGW to the destination MME.

4 1 5. Purpose The MME returns the forwarding tunnel identifier of the destination SGW to the source SGW to the destination SGW.

The binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE is established in the destination SGW.

After receiving the forwarding tunnel identifier that is allocated by the source SGW, the destination SGW establishes a binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE, so that the data packet of the destination UE is transmitted to the forwarding tunnel to the forwarding tunnel. Source UE. After the SGW establishes the binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE, the SGW may send a destination UE to the source UE local route establishment complete message to the PGW.

Because the uplink bearer of the destination UE can simultaneously transmit the data packet sent by the destination UE to the source UE and the data packet sent by the destination UE to other destinations, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the destination UE to the source UE may be: sending the data packet sent by the destination UE to the source UE. The IP address of the destination UE, the port number of the destination UE, the IP address of the source UE, the port number of the source UE, and the transmission protocol between the source UE and the destination UE are used as a quintuple according to the quintuple and the source UE. Corresponding to the downlink bearer, the binding relationship between the identifier of the forwarding tunnel and the data packet sent by the destination UE to the source UE is established. In the destination SGW, a data flow screening device (such as a TFT) may be used to select a data packet that meets the description of the quintuple.

In addition, when there is a NAT mapping device between the EPS system and the external PDN network, the data packet is translated on the NAT mapping device by the IP address and port number of the public and private network. In the embodiment of the present invention, in order to implement local routing, the function of NAT address translation needs to be migrated. Specifically, when the address and port information of the NAT mapping device are pre-stored in the PGW, the PGW initiates a NAT information acquisition request to the NAT mapping device according to the pre-stored address and port information. NAT device receives the NAT information acquisition request, the NAT mapping information stored therein is returned to the PGW ₀ when the PGW not stored NAT mapping device address and port information, PGW can detect a NAT device by NAT traversal techniques, and from The NAT mapping information is obtained on the detected NAT device.

The NAT mapping information includes the mapping between the private network IP address of the source UE and the corresponding public network IP address, the correspondence between the private network transmission protocol port number and the corresponding public network transmission protocol port number, and the private network IP address of the destination UE. Correspondence relationship with the corresponding private network IP address, the private network transmission protocol port number of the destination UE, and the corresponding public network transmission protocol port number. The PGW transmits the obtained NAT mapping information to the source SGW and the destination SGW. Establishing, by the source SGW, the correspondence between the data packet sent by the source UE and the NAT mapping information, and establishing the correspondence between the data packet sent by the destination UE and the source mapping information on the destination SGW, so that the source SGW is at the source SGW. NAT address translation is performed on the destination SGW.

Specifically, after receiving the data packet sent by the source UE to the destination UE, the source SGW performs NAT address translation on the data packet, and converts the private network address of the source UE and the private network transmission protocol port number to the corresponding public network address. And the public network transmission protocol port number, converting the public network address of the destination UE and the public network transmission protocol port number into the corresponding private network address and the private network transmission protocol port number, and performing NAT through the forwarding tunnel from the source SGW to the destination SGW. The address converted data message is sent to the destination SGW. The SGW sends the data packet to the destination UE. Correspondingly, the data packet sent by the destination UE to the source UE is also translated by the NAT address on the destination SGW, and finally transmitted to the source UE.

Establishing a local route through the forwarding tunnel between the source SGW and the destination SGW, the source UE The data of the UE and the destination UE are no longer address translated via the NAT mapping device between the PGW and the external PDN network. The public network address and the public network transmission protocol port allocated for the data packet of the executed local route are reclaimed when the NAT mapping device fails to receive the data packet of the local route in the preset mapping release time period. The source SGW and the destination SGW periodically send a heartbeat packet to the NAT mapping device to notify the NAT mapping device to continue to maintain the public network address and the public network transmission protocol port number allocated for the data packet of the local route. The sending period of the heartbeat packet should be smaller than the mapping release period.

The method for detecting the local route and the method for establishing the local route provided by the embodiment of the present invention, so that when the source UE and the destination UE are respectively connected to the source SGW and the destination SGW, a forwarding tunnel is established between the source SGW and the destination SGW. The establishment of a local route. The local route is used to prevent the data packet transmission between the source UE and the destination UE from being looped back through the external PDN network, reducing the transmission delay of data packets between the source UE and the destination UE, and improving the user experience. It also reduces the processing load of the PGW.

Example 3:

In the EPS system, the PDN connection of the source UE and the PDN connection of the destination UE are respectively carried by the source eNodeB and the destination eNodeB, and the source eNodeB and the destination eNodeB are connected to the same SGW. The network architecture of the system is shown in FIG. For the detection method of the local route in this scenario, refer to the description of Embodiment 1 of the present invention. The network element PGW that performs the local route detection method needs to detect the source UE and the destination UE in the context information corresponding to the IP address of the source UE and the context information corresponding to the IP address of the destination UE. Whether the source eNodeB on the bearer link and the destination eNodeB where the destination UE is located have local route establishment capability.

In addition, the embodiment of the present invention further provides a method for establishing a local route, as shown in FIG. 6, including the following steps:

5 01. The PGW sends a local routing request to the SGW.

The local routing request includes the identifier of the source UE, the identifier of the destination UE, the bearer identifier of the source UE, the identifier of the destination UE, the IP address of the source SGW, and the IP address of the destination SGW, if the PDN connection of the UE needs to be performed. In the NAT address translation, the local routing request also needs to include the NAT mapping information. If the data packet that performs the local routing needs to be separately charged, the local routing request needs to include the charging information, such as the charging identifier. Fee method, etc. 5 02. The SGW forwards the local routing request to the source MME.

The SGW queries the corresponding context according to the identifiers of the source UE and the destination UE, and detects the location of the eNodeB where the source UE and the destination UE are located and whether the local route establishment capability is available. If the source eNodeB of the source UE and the destination eNodeB of the destination UE are different eNodeBs, and both have the local routing capability, the local routing establishment request is sent to the source MME, including: the identifier of the source UE, the identifier of the destination UE, and the source UE. The 7-digit identifier, the 7-digit identifier of the destination UE, the IP address of the source eNodeB, and the IP address of the destination eNodeB. If the NAT address translation is required in the PDN connection of the UE, the local routing request must also include NAT mapping information. The local routing request needs to include the accounting information, such as the charging identifier and the charging method.

5 03. The source MME sends a forwarding tunnel establishment request from the source eNodeB to the destination eNodeB to the destination eNodeB.

The source MME forwards the forwarding tunnel establishment request to the destination eNodeB according to the IP address of the destination eNodeB.

The forwarding tunnel establishment request includes: an identifier of the destination UE, and a downlink bearer identifier of the destination UE.

5 04. Purpose The eNodeB branches to a source eNodeB destination eNodeB forwarding channel identifier.

The binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE is established in the destination eNodeB.

00. Return the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source MME.

5 07. The source MME sends the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source eNodeB.

The binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE is established in the source eNodeB.

After receiving the forwarding tunnel identifier allocated by the destination eNodeB, the source eNodeB establishes a binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE, so that the data packet of the source UE is transmitted to the forwarding tunnel to the forwarding tunnel. Destination UE. Establishing the forwarding tunnel label After the binding relationship between the source UE and the data packet sent by the source UE is received, the source eNodeB sends a forwarding tunnel setup complete message to the source MME, and the local route from the source eNodeB to the destination eNodeB to the destination UE is completed. The MME sends a local route setup complete message from the source UE to the destination UE direction to the SGW, and forwards the message to the PGW via the SGW.

The data packet sent by the source UE to the destination UE and the data packet sent by the source UE to other destinations may be simultaneously transmitted in the uplink bearer of the source UE, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the source UE to the destination UE may be: the IP address of the source UE, the port number of the source UE, and the IP address of the destination UE in the data packet sent by the source UE to the destination UE. The address, the port number of the destination UE, and the transmission protocol between the source UE and the destination UE are used as a quintuple, and the identifier of the forwarding tunnel and the source UE are sent to the destination UE according to the correspondence between the quintuple and the downlink bearer of the destination UE. Binding relationship of data packets. The source eNodeB may select a data packet that meets the description of the quintuple by using a data stream filtering device (such as a TFT).

In addition, the PGW also establishes a local route for the destination UE to send data packets to the source UE. Including Step 5 09 to Step 5 1 6:

5 09. The PGW sends a local routing request to the SGW.

The PGW may send a local route request to the SGW after the local route of the source UE sends the data packet to the destination UE, that is, after the step 5 08, to establish a local route for the destination UE to send the data packet to the source UE. Of course, the PGW may also first establish a local route for the destination UE to send data packets to the source UE, and then establish a local route for the source UE to send data packets to the destination UE, which is not limited in this embodiment of the present invention.

5 1 0. The SGW forwards the local routing request to the destination MME.

5 1 1. Purpose The MME sends a forwarding tunnel establishment request from the destination eNodeB to the source eNodeB to the source eNodeB.

The destination MME forwards the forwarding tunnel establishment request to the source eNodeB according to the IP address of the source eNodeB.

The forwarding tunnel establishment request includes: an identifier of the source UE, and a downlink bearer identifier of the source UE.

5 1 2. The source eNodeB divides the forwarding track identifier of the eNodeB source eNodeB. The binding relationship between the forwarding tunnel identifier and the downlink bearer identifier of the source UE is established in the source eNodeB.

5 1 4, return the forwarding tunnel identifier of the destination eNodeB to the source eNodeB to the destination MME.

5 1 5. Purpose The MME sends the forwarding tunnel identifier of the destination eNodeB to the source eNodeB to the destination eNodeB.

The binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE is established in the destination eNodeB.

After receiving the forwarding tunnel identifier allocated by the source eNodeB, the destination eNodeB establishes a binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE, so that the data packet of the destination UE is transmitted to the forwarding tunnel to the forwarding tunnel. Source UE. After the binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE is established, the destination eNodeB sends a tunnel establishment complete message to the destination MME, and the destination MME establishes a local route completion message from the destination UE to the source UE. Sent to the SGW and forwarded to the PGW via the SGW.

Because the uplink bearer of the destination UE can simultaneously transmit the data packet sent by the destination UE to the source UE and the data packet sent by the destination UE to other destinations, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the destination UE to the source UE may be: an IP address of the destination UE, a port number of the destination UE, and an IP address of the source UE in the data packet sent by the destination UE to the source UE. The address, the port number of the source UE, and the transmission protocol between the source UE and the destination UE are used as a quintuple, and the identifier of the forwarding tunnel and the destination UE are sent to the source UE according to the correspondence between the quintuple and the downlink bearer of the source UE. Binding relationship of data packets. In the destination eNodeB, the data packet matching the description of the quintuple can be selected by a data stream filtering device (such as a TFT) data selection device.

In addition, when there is a NAT mapping device between the EPS system and the external PDN network, the data packet is translated on the NAT mapping device by the IP address and port number of the public and private network. In the embodiment of the present invention, in order to implement local routing, the function of NAT address translation needs to be migrated. Specifically, when the address and port information of the NAT mapping device are pre-stored in the PGW, the PGW initiates a NAT information acquisition request to the NAT mapping device according to the pre-stored address and port information. NAT device receives the NAT information acquisition request, the NAT mapping information stored therein is returned to the PGW ₀ when the PGW not stored NAT mapping device address and port information, PGW can detect a NAT device by NAT traversal techniques, and from Detected on the detected NAT device Describe NAT mapping information.

The NAT mapping information includes the mapping between the private network IP address of the source UE and the corresponding public network IP address, the correspondence between the private network transmission protocol port number and the corresponding public network transmission protocol port number, and the private network IP address of the destination UE. Correspondence relationship with the corresponding private network IP address, the private network transmission protocol port number of the destination UE, and the corresponding public network transmission protocol port number. The PGW transmits the obtained NAT mapping information to the source eNodeB and the destination eNodeB via the SGW and the MME. Establishing, on the source eNodeB, the correspondence between the data sent by the source UE and the destination information, and the mapping between the data packet sent by the destination UE and the source mapping information on the destination eNodeB. NAT address translation is performed on the eNodeB and the destination eNodeB.

Specifically, after receiving the data packet sent by the source UE to the destination UE, the source eNodeB performs NAT address translation on the data packet, and converts the private network address of the source UE and the private network transmission protocol port number to the corresponding public network address. And the public network transmission protocol port number, converting the public network address of the destination UE and the public network transmission protocol port number into the corresponding private network address and the private network transmission protocol port number, and performing NAT through the forwarding tunnel of the source eNodeB to the destination eNodeB. The address converted data message is sent to the destination eNodeB. The eNodeB sends the data packet to the destination UE. Correspondingly, the data packet sent by the destination UE to the source UE is also translated by the NAT address on the destination eNodeB, and finally transmitted to the source UE.

A local route is established through the forwarding tunnel between the source eNodeB and the destination eNodeB, and the data packets of the source UE and the destination UE are no longer address translated by the NAT mapping device between the PGW and the external PDN network. To prevent the NAT mapping device from receiving the data message of the local route that has been executed within the preset mapping release time period, the public network address and the public network transmission protocol allocated for the data of the executed local route are recovered. The port number, the source eNodeB, and the destination eNodeB periodically send a heartbeat packet to the NAT mapping device to notify the NAT mapping device to transmit the protocol port number. The sending period of the heartbeat packet should be smaller than the mapping release period.

As another supplement to the embodiment of the present invention, the SGW may be used as a network element for performing a local route detection method. For the detection method of the local route and the method for establishing the local route in this scenario, refer to the foregoing description of the embodiment of the present invention, and details are not described herein again.

The method for detecting the local route and the method for establishing the local route provided by the embodiment of the present invention, so that when the source UE and the destination UE are respectively connected to the source eNodeB and the destination eNodeB, The establishment of a local route is established by establishing a forwarding tunnel between the source eNodeB and the destination eNodeB. The local route is used to prevent the data packet transmission between the source UE and the destination UE from being looped back through the external PDN network, reducing the transmission delay of data packets between the source UE and the destination UE, and improving the user experience. It also reduces the processing load of the PGW.

Example 4:

In the system architecture as shown in FIG. 17, the local routing establishment function may be set in the SGW. In this scenario, the embodiment of the present invention provides a method for establishing a local route, as shown in FIG. The following steps:

6 01. The SGW receives the local routing request sent by the PGW.

By receiving the local routing request, the SGW establishes a local route for the data to be sent by the source UE to the destination UE and a local route for the data transmission by the destination UE to the source UE.

Before the step 6 01 is performed, the PGW has completed the detection of the local route, and the description of the method for detecting the local route by the PGW can be referred to the descriptions in Embodiment 2 and Embodiment 3 of the present invention, and details are not described herein again.

The local routing request includes the identifier of the source UE, the identifier of the destination UE, the identifier of the source UE, and the bearer identifier of the destination UE. If the NAT address translation needs to be performed in the PDN connection of the UE, the local routing request needs to be included in the local routing request. The NAT mapping information needs to include the accounting information, such as the charging identifier and the charging method, in the local routing request, if the data packet is to be separately charged.

6 02. The SGW establishes a binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE.

The SGW establishes a binding relationship between the data packet sent by the UE and the source UE to the downlink bearer of the source UE.

In an actual application, after the SGW establishes a binding relationship between the data packet sent by the source UE and the destination UE, and the downlink bearer of the source UE, the SGW may continue to establish the binding of the data packet sent by the destination UE to the source UE and the downlink bearer of the source UE. After the binding relationship between the data packet sent by the source UE and the destination UE and the downlink bearer of the destination UE is established, the route establishment complete message from the source UE to the destination UE is sent to the PGW. After receiving the route establishment complete message, the PGW sends a local routing request to the SGW, so that the SGW continues to establish the destination UE to the source UE. Binding relationship between the sent data packet and the downlink bearer of the source UE.

After establishing a binding relationship between the data packet sent by the destination UE and the source UE and the downlink bearer of the source UE, the SGW may send a local route establishment complete message of the destination UE to the source UE to the PGW.

The data packet sent by the source UE to the destination UE and the data packet sent by the source UE to other destinations may be simultaneously transmitted in the uplink bearer of the source UE, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the source UE to the destination UE may be: the IP address of the source UE, the port number of the source UE, and the IP address of the destination UE in the data packet sent by the source UE to the destination UE. The address, the port number of the destination UE, and the transmission protocol between the source UE and the destination UE are used as a quintuple, and the destination UE downlink bearer identifier is established and the source UE sends the destination UE to the destination UE according to the downlink bearer corresponding to the quintuple and the destination UE. Binding relationship of data packets.

Because the uplink bearer of the destination UE can simultaneously transmit the data packet sent by the destination UE to the source UE and the data packet sent by the destination UE to other destinations, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, The binding of the forwarding tunnel identifier to the data packet sent by the destination UE to the source UE may be: an IP address of the destination UE, a port number of the destination UE, and an IP address of the source UE in the data packet sent by the destination UE to the source UE. The address, the port number of the source UE, and the transmission protocol between the destination UE and the source UE are used as a quintuple. According to the correspondence between the quintuple and the downlink bearer of the source UE, the source UE downlink bearer identifier is established, and the destination UE is sent to the source UE. Binding relationship of data packets.

In the SGW, the data packet that meets the description of the quintuple can be filtered by a data stream filtering device (such as a TFT).

In addition, when there is a NAT mapping device between the EPS system and the external PDN network, the data packet needs to be translated on the NAT mapping device according to the NAT mapping information to the IP address and port number of the public and private network. In the embodiment of the present invention, in order to implement local routing, the function of NAT address translation needs to be migrated. For details, refer to the description in Embodiment 2 of the present invention, and details are not described herein again.

The NAT mapping information includes the mapping between the private network IP address of the source UE and the corresponding public network IP address, the correspondence between the private network transmission protocol port number and the corresponding public network transmission protocol port number, and the private network IP address of the destination UE. Correspondence relationship with the corresponding private network IP address, the private network transmission protocol port number of the destination UE, and the corresponding public network transmission protocol port number. The PGW transmits the obtained NAT mapping information to the SGW. SGW establishes source UE to the target Correspondence between the data packet sent by the UE and the NAT mapping information, and the correspondence between the data packet sent by the destination UE to the source UE and the NAT mapping information, so that NAT address translation can be implemented on the SGW.

Specifically, after receiving the data packet sent by the source UE to the destination UE, the SGW performs NAT address translation on the data packet, and converts the private network address and the private network transmission protocol port number into corresponding public network addresses and public network transmissions. The protocol port number, the public network address of the destination UE, and the public network transmission protocol port number are converted into the corresponding private network address and the private network transmission protocol port number, and the data packet of the NAT address translation is sent to the downlink bearer of the destination UE. Destination UE. Correspondingly, after receiving the data packet sent by the destination UE to the source UE, the SGW also sends the NAT packet to the source UE.

As another supplement to the embodiment of the present invention, the function of detecting the local route can also be integrated in the SGW. Specifically, after the source UE/destination UE establishes a PDN connection, the SGW records the correspondence between the IP address of the source UE/destination UE and the context information generated after establishing the PDN connection in the context query table stored in the SGW. Then, the IP address of the source UE and the IP address of the destination UE are obtained from the data packet sent by the source UE. If the SGW finds the context information corresponding to the IP address of the source UE and the context information corresponding to the IP address of the destination UE in the context query table, the SGW has the local routing capability. The SGW continues to detect whether the source UE and the destination UE comply with the local routing policy. When the local routing policy is met, the SGW starts to implement the local routing establishment method.

The method for establishing a local route is provided in the embodiment of the present invention, so that when the source UE and the destination UE are connected to the same SGW, the data message forwarding between the source UE and the destination UE is performed through the SGW, thereby realizing the establishment of the local route. Therefore, the data packet transmission between the source UE and the destination UE does not need to be looped back through the external PDN network, and the transmission delay of the data packet between the source UE and the destination UE is reduced, thereby improving the user experience; when the SGW is simultaneously integrated When the function of detecting local routes is performed, the processing load of the PGW can be further reduced.

Example 5:

In the EPS system, the PDN connection of the source UE and the PDN connection of the destination UE are carried by the same eNodeB, and the system also has an SGW and an MME connected to the eNodeB. In this scenario, the embodiment of the present invention provides a method for establishing a local route. As shown in FIG. 8, the method includes the following steps:

7 01. The eNodeB receives the local route sent by the SGW to the MME and forwarded by the MME. begging.

Before the step S101 is performed, the SGW has completed the detection of the local route. The method for detecting the local route can be referred to the description in Embodiment 2 and Embodiment 3 of the present invention, and details are not described herein. The SGW sends a local routing request to the MME, so that the MME forwards the local routing request to the eNodeB.

The local routing request includes an identifier of the source UE, an identifier of the destination UE, a bearer identifier of the source UE, a bearer identifier of the destination UE, NAT mapping information, and a charging standard.

7 02. The eNodeB establishes a binding relationship between the data sent by the source UE to the destination UE and the downlink bearer of the destination UE.

7 03. The eNodeB establishes a binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE.

In an actual application, after establishing the binding relationship between the data packet sent by the source UE and the destination UE and the downlink bearer of the destination UE, the eNodeB may continue to establish the binding of the data packet sent by the destination UE to the source UE and the downlink bearer of the source UE. After the binding relationship between the data packet sent by the source UE and the destination UE to the downlink bearer of the destination UE is established, the source UE to the destination UE route establishment complete message is sent to the MME, and the route establishment complete message is sent by the MME. After the SGW ₀ SGW receives the route setup complete message, it sends a local route request to the MME, and the MME forwards the request to the eNodeB, so that the eNodeB continues to establish the data packet sent by the destination UE to the source UE and the downlink bearer of the source UE. Binding relationship.

After establishing a binding relationship between the data packet sent by the destination UE and the source UE and the downlink bearer of the source UE, the eNodeB may send a route establishment complete message of the destination UE to the source UE to the MME, and the MME forwards the message to the SGW.

The number of destination UEs that can be sent to the source UE can be simultaneously transmitted in the uplink bearer of the destination UE. According to the packet and the data packet sent by the destination UE to the other destination, in order to uniquely determine the binding relationship between the forwarding tunnel identifier and the data packet, the forwarding tunnel identifier is bound to the data packet sent by the destination UE to the source UE. The IP address of the destination UE, the port number of the source UE, the IP address of the source UE, the port number of the source UE, and the transmission protocol between the destination UE and the source UE in the data packet sent by the destination UE to the source UE may be: As a quintuple, a binding relationship between the downlink bearer identifier of the source UE and the data packet sent by the destination UE to the source UE is established according to the correspondence between the quintuple and the downlink bearer of the source UE.

In addition, when there is a NAT mapping device between the EPS system and the external PDN network, the data packet needs to be translated on the NAT mapping device according to the NAT mapping information to the IP address and port number of the public and private network. In the embodiment of the present invention, in order to implement local routing, the function of NAT address translation needs to be migrated. For details, refer to the description in Embodiment 2, and details are not described herein again.

The NAT mapping information includes the mapping between the private network IP address of the source UE and the corresponding public network IP address, the correspondence between the private network transmission protocol port number and the corresponding public network transmission protocol port number, and the private network IP address of the destination UE. Correspondence relationship with the corresponding private network IP address, the private network transmission protocol port number of the destination UE, and the corresponding public network transmission protocol port number. The PGW transmits the obtained NAT mapping information to the eNodeB. The eNodeB establishes a correspondence between the data packet sent by the source UE to the destination UE and the NAT mapping information, and the correspondence between the data packet sent by the destination UE to the source UE and the NAT mapping information, so that NAT address translation can be implemented on the eNodeB.

Specifically, after receiving the data packet sent by the source UE to the destination UE, the eNodeB performs NAT address translation on the data packet, and converts the private network address and the private network transmission protocol port number into the corresponding public network address and the public network transmission. The protocol port number is used to convert the public network address of the destination UE and the public network transmission protocol port number into the corresponding private network address and the private network transmission protocol port number, and send the data packet for NAT address translation through the downlink bearer of the destination UE. Give the destination UE. Correspondingly, after receiving the data packet sent by the destination UE to the source UE, the eNodeB also needs to perform NAT conversion, and then sends the downlink bearer of the source UE to the source UE.

The function of detecting the local route may also be integrated in the PGW, that is, the function of the SGW in the embodiment of the present invention is performed by the PGW, and details are not described herein again.

As a further addition to the embodiments of the present invention, the function of detecting local routes can also be integrated in the eNodeB. Specifically, after the source UE/destination UE establishes a PDN connection, the eNodeB The correspondence between the IP address of the source UE/destination UE and the context information generated after the PDN connection is established is recorded in the context query table stored in itself. Then, the IP address of the source UE and the IP address of the destination UE are obtained from the data packet sent by the source UE. If the eNodeB finds the context information corresponding to the IP address of the source UE and the context information corresponding to the IP address of the destination UE in the context query table, the eNodeB has the local route establishment capability. The eNodeB continues to check whether the source UE and the destination UE comply with the local routing policy. When the local routing policy is met, the eNodeB starts to implement the local routing establishment method.

The method for establishing a local route is provided in the embodiment of the present invention, so that when the source UE and the destination UE are respectively connected to the same eNodeB, the eNodeB performs data packet forwarding between the source UE and the destination UE, thereby implementing local route establishment. Therefore, the data packet transmission between the source UE and the destination UE does not need to be looped back through the external PDN network, and the transmission delay of the data packet between the source UE and the destination UE is reduced, thereby improving the user experience; when the eNodeB is simultaneously When the function of detecting local routes is integrated, the processing load of the SGW and the PGW can be further reduced.

Example 6:

The embodiment of the invention provides a local routing detection device, as shown in FIG. The device includes: a context information finding unit 91, a local routing capability detecting unit 92, and a routing request transmitting unit 93.

The context information searching unit 91 is configured to search context information corresponding to the IP address of the source UE and context information corresponding to the IP address of the destination UE in the context query table that generates the IP address and the context.

The local routing capability detecting unit 92 is configured to detect, in the context information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has local route establishment capability.

The routing request sending unit 93 is configured to send a local routing request to the network element having the local routing establishment capability, so that the network element with the local routing establishment capability performs local routing configuration, and the data packet between the source UE and the destination UE is configured. Make local routes.

Further, as shown in FIG. 10, the apparatus further includes a routing policy detecting unit 94. The routing policy detecting unit 94 is configured to detect whether the source UE and the destination UE meet the local routing policy, so that when the local routing policy is met, the routing request sending unit 93 sends a local routing request to the network element having the local routing establishment capability. . The local routing policy specifies whether to allow local routing for data packets sent and received by the UE. Local routing policy The class of UEs that are prohibited from performing local routing and the type of data packets that are allowed to perform local routing are slightly defined. For example, the local routing policy prohibits a type of user that is legally intercepted by the operator to perform local routing. The local routing policy allows local routing to be performed for voice-type data packets communicated between the UEs.

In addition, the embodiment of the present invention further provides a device for establishing a local route. As shown in FIG. 11, the method includes: a route request receiving unit 111, and a local route establishing unit 112.

The routing request receiving unit 111 is configured to receive a local routing request.

The local route establishing unit 112 is configured to establish a binding relationship between the data packet sent by the source UE and the destination UE, and establish a binding relationship between the data packet sent by the destination UE and the source UE. The data packet between the source UE and the destination UE is locally routed according to the binding relationship.

Further, the local route establishing unit 112 is integrated in the source SGW when the network element for establishing the local route is the source SGW of the PDN connection where the source UE is located and the destination SGW of the PDN where the destination UE is located. As shown in FIG. 12, the local route establishing unit 112 further includes: a tunnel request sending module 1121, a first tunnel receiving module 1122, a first binding establishing module 1123, a tunnel request receiving module 1124, and a second binding establishing module 1125. The first tunnel sending module 1126.

The tunnel request sending module 1121 is configured to forward the local routing request to the source MME on the PDN connection where the source UE is located, so that the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW, and the source SGW allocates the source. After forwarding the tunnel to the destination SGW, the SGW returns the forwarding tunnel identifier to the source MME.

The first tunnel receiving module 1122 is configured to receive a forwarding tunnel identifier that is forwarded by the source SGW to the source MME and forwarded by the source MME.

The first binding establishment module 1123 is configured to establish a binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE, so that the data packet is transmitted to the destination SGW through the forwarding tunnel.

The tunnel request receiving module 1124 is configured to receive a forwarding tunnel establishment request from the destination SGW to the source SGW sent by the destination MME.

The second binding establishment module 1125 is configured to allocate a forwarding tunnel of the destination SGW to the source SGW and establish a binding relationship between the forwarding tunnel identifier and the downlink bearer of the source UE. The first tunnel sending module 1126 is configured to send the forwarding tunnel identifier of the destination SGW to the source SGW to the destination MME, so that the destination MME forwards the forwarding tunnel identifier of the destination SGW to the source SGW to the destination SGW, and the destination SGW establishes the destination SGW to the source SGW. The binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE.

When the local route establishing unit 112 is integrated in the source SGW, the local route establishing unit 112 is also integrated in the destination SGW.

In addition, when the network element that is configured by the local route is the source eNodeB on the PDN connection where the source UE is located and the destination eNodeB connected to the PDN where the destination UE is located, the local route establishment unit 112 is integrated in the destination eNodeB. As shown in FIG. 13, the local route establishing unit 112 further includes: a third binding establishment module 1127, a second tunnel sending module 1128, a second tunnel receiving module 1129, and a fourth binding establishing module 1130.

The third binding establishment module 1127 is configured to: after receiving the forwarding P-channel establishment request sent by the source eNodeB and the destination eNodeB, the forwarding tunnel of the eNodeB of the source eNodeB is configured to establish the forwarding tunnel identifier and the downlink bearer of the destination UE. The binding relationship is such that the data transmitted to the destination eNodeB by the forwarding tunnel of the source eNodeB to the destination eNodeB is sent to the destination UE.

The second tunnel sending module 1128 is configured to return the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source MME, so that the source MME forwards the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source eNodeB, and the source eNodeB establishes the source eNodeB to the destination. The binding relationship between the forwarding tunnel identifier of the eNodeB and the data packet sent by the source UE to the destination UE.

The second tunnel receiving module 1129 is configured to receive a forwarding tunnel identifier of the destination eNodeB that is allocated by the source eNodeB and forwarded by the destination MME to the source eNodeB.

The fourth binding establishment module 1130 is configured to establish a binding relationship between the forwarding tunnel identifier of the destination eNodeB and the source eNodeB and the data packet sent by the destination UE to the source UE.

When the local route establishing unit 112 is integrated in the destination eNodeB, the local route establishing unit 112 is also integrated in the source eNodeB.

The local routing detection apparatus and the local routing establishment apparatus provided by the embodiments of the present invention detect and establish a local route, so that the data message sent by the source UE to the destination UE and the data message returned by the destination UE to the source UE are not The external PDN network needs to be looped back, and local routing is performed through the SGW or the eNodeB, thereby reducing the transmission delay, improving the user experience, and reducing the processing load of the PGW. Example 7

The embodiment of the invention provides a system for implementing local route establishment, as shown in FIG. 14 . The system includes a detection device 141 and an establishment device 142.

Detection device 141 is configured to send a local routing request to setup device 142. The establishing device 142 is configured to establish a binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE, and establish a datagram sent by the destination UE to the source UE, after receiving the local route establishment request of the detecting device 141. The binding relationship between the source and the downlink bearer of the source UE, so that the data packets between the source UE and the destination UE are locally routed according to the binding relationship.

As an application scenario of the embodiment of the present invention, the establishing apparatus 141 may be included in an SGW of an EPS system, and the detecting apparatus 142 may be included in a PGW of an EPS system. As shown in FIG. 15, the system includes a source SGW 151 on the PDN connection where the source UE is located, and a destination SGW 152 on the PDN where the destination UE is located, and the PGW 153.

The PGW 153 is configured to send a local routing request to the source SGW 151 and the destination SGW 152 respectively, so that the source SGW and the destination SGW perform local routing configuration, and locally route data packets between the source UE and the destination UE.

The source SGW 151 is configured to: after receiving the local routing request of the PGW 153, forward the local routing request to the source MME on the PDN connection where the source UE is located, so that the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW 152.

The SGW 152 is configured to return the forwarding tunnel identifier of the allocated source SGW to the destination SGW to the source MME, and forward the source tunnel to the source SGW 151.

The destination SGW 152 is further configured to: after receiving the local routing request of the PGW 153, forward the received local routing request to the destination MME on the PDN connection where the destination UE is located, so that the destination MME sends the forwarding STU of the destination SGW to the source SGW to the source SGW 151. request.

The source SGW 151 is further configured to return the forwarding tunnel identifier of the allocated destination SGW to the source SGW to the destination MME, and forwarded by the destination MME to the destination SGW 152.

After the SGW 152 allocates the forwarding tunnel identifier of the source SGW to the destination SGW, the SGW 152 also establishes a binding relationship between the forwarding tunnel identifier of the source SGW and the destination SGW and the downlink bearer of the destination UE, so that the data packet sent by the source UE to the destination UE is forwarded. After reaching the destination SGW 152, it is forwarded by the destination SGW 152 to the destination UE. After receiving the forwarding tunnel identifier from the source SGW to the destination SGW, the source SGW 151 establishes a binding relationship between the forwarding tunnel identifier of the source SGW and the destination SGW and the data packet sent by the source UE to the destination UE, so that the source UE sends the data to the destination UE. Message arrival source After the SGW1 51 is forwarded to the destination SGW1 52 via the forwarding tunnel of the source SGW to the destination SGW. In addition, the source SGW1 151 establishes a binding relationship between the forwarding tunnel identifier of the destination SGW and the source SGW and the downlink bearer of the source UE, so that the source UE sends the data to the source UE, after the destination SGW to the source SGW. After the message is forwarded to the source SGW1 5 1 , it is forwarded to the source UE by the source SGW1 5 1 . After the destination SGW receives the forwarding tunnel identifier from the destination SGW to the source SGW, the destination SGW1 52 establishes a binding relationship between the forwarding tunnel identifier of the destination SGW and the source SGW and the data packet sent by the destination UE to the source UE, so that the destination UE sends the data to the source UE. After the data packet arrives at the destination UE, it is forwarded to the source SGW1 51 through the forwarding tunnel of the destination SGW to the source SGW.

Of course, in other implementation scenarios, the establishing device 1 4 1 may be included in an eNodeB of the EPS system, and the detecting device 1 42 may be included in an SGW or a PGW of the EPS system.

The system for implementing local route establishment provided by the embodiment of the present invention sends a local routing request to the establishing device by using the detecting device, and the local device establishes a local route, so that the data packet transmitted between the source UE and the destination UE does not need to pass through the device. The external PDN network loopback is transmitted directly through the SGW or the eNodeB, which reduces the transmission delay, improves the user experience, and reduces the processing load of the PGW.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus necessary general hardware, and of course, by hardware, but in many cases, the former is a better implementation. . Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a readable storage medium, such as a floppy disk of a computer. A hard disk or optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

The above description is only the specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto, and any technical person skilled in the art can disclose the technical scope disclosed by the present invention. Variations or substitutions are readily conceivable within the scope of the invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

Claim

A method for detecting the feasibility of a local route, which is characterized by comprising:

Querying, in the context query table that generates the IP address and the context, the context information corresponding to the IP address of the source UE and the IP address of the destination UE;

When the local routing establishment capability is available, the local routing request is sent to the source UE and the network element on the destination UE bearer link, so that the source UE and the destination UE carry the local element routing configuration on the bearer link, and the source UE and the source UE The data packets between the destination UEs are locally routed.

2. The method according to claim 1, further comprising:

After the source UE/destination UE establishes a PDN connection, the context query table records the correspondence between the IP address of the source UE/destination UE and the context information generated after the PDN connection is established.

The method according to claim 2, wherein before the context information corresponding to the IP address of the source UE and the context information corresponding to the IP address of the destination UE are searched in the context query table, the method further includes:

The IP address of the source UE and the IP address of the destination UE are obtained from the data packet sent by the source UE.

4. The method according to claim 1, further comprising:

When the source UE and the target UE bearer link have the local route establishment capability, check whether the source UE and the destination UE comply with the local routing policy, so that when the local routing policy is met, the source UE and the destination are The network element on the UE bearer link sends a local routing request; the local routing policy defines a network element capable of performing local routing.

The method according to any one of claims 1 to 4, further comprising: acquiring NAT mapping information from the NAT mapping device, so that the data message sent by the source UE and the data returned by the destination UE are The packet performs NAT address mapping according to the obtained NAT mapping information, and does not need to perform NAT address mapping on the NAT mapping device.

A method for establishing a local route, which is characterized by comprising:

Receiving a local routing request; Establish a binding relationship between the data packet sent by the source UE and the destination UE to the downlink bearer of the source UE, and establish a binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE, so that the source UE and the destination The data packets between the UEs are locally routed according to the binding relationship.

7. The method according to claim 6, further comprising:

Sending a heartbeat packet to the NAT mapping device at a preset time interval, so that the NAT mapping device continues to maintain the existing NAT mapping after receiving the heartbeat packet.

The method according to claim 6 or 7, wherein, when the network element that performs the local route establishment is the source SGW on the PDN connection where the source UE is located and the destination SGW on the PDN where the destination UE is located, the establishment is performed. The binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE further includes:

The source SGW forwards the local routing request to the source MME on the PDN connection where the source UE is located, so that the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW, and the destination SGW allocates the source SGW to the destination SGW. After forwarding the tunnel, the forwarding tunnel identifier is returned to the source MME;

Receiving, by the receiving destination SGW, the forwarding tunnel identifier that is forwarded by the source MME and forwarded by the source MME; establishing a binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE, so that the data packet passes through the forwarding tunnel Pass to the destination SGW.

The method according to claim 8, wherein the destination SGW establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE after the forwarding tunnel of the source SGW to the destination SGW is allocated, so that the forwarding tunnel is The data message transmitted to the destination SGW is sent to the destination UE.

The method according to claim 8, wherein the binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE is further included:

The source SGW receives the forwarding tunnel establishment request from the destination SGW to the source SGW by the destination MME; assigns the forwarding tunnel of the destination SGW to the source SGW, and establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the source UE;

Sending the forwarding tunnel identifier of the destination SGW to the source SGW to the destination UE. After the destination MME forwards the forwarding tunnel identifier of the destination SGW to the source SGW to the destination SGW, the destination SGW establishes the forwarding tunnel identifier and destination UE of the destination SGW to the source SGW. Binding relationship of data packets sent to the source UE.

1 1. The method according to claim 6 or 7, wherein when the local road is performed The binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE is established when the source network element is the source eNodeB connected to the PDN of the source UE and the destination eNodeB connected to the destination UE. Also includes:

After receiving the forwarding tunnel establishment request from the source eNodeB to the destination eNodeB, the destination eNodeB allocates a forwarding tunnel from the source eNodeB to the destination eNodeB, and establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE, so that the source eNodeB The data packet sent by the destination eNodeB to the destination eNodeB is sent to the destination UE.

Returning the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source MME, so that the source MME forwards the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source eNodeB, and the source eNodeB establishes the forwarding tunnel identifier of the source eNodeB to the destination eNodeB and the source UE. Binding relationship of data packets sent to the destination UE.

The method according to claim 1, wherein the binding relationship between the data packet sent by the destination UE to the source UE and the downlink bearer of the source UE is further included:

The eNodeB receives the forwarding tunnel identifier of the destination eNodeB that is forwarded by the source eNodeB and forwarded by the destination MME to the source eNodeB.

The binding relationship between the forwarding tunnel identifier of the destination eNodeB and the source eNodeB and the data packet sent by the destination UE to the source UE is established.

The method according to claim 12, wherein, after the source eNodeB allocates the forwarding tunnel of the destination eNodeB to the source eNodeB, the binding relationship between the forwarding tunnel identifier of the destination eNodeB and the source eNodeB and the downlink bearer of the source UE is established. .

1 4, a local routing detection device, comprising:

a context information searching unit, configured to search, in a context query table that generates an IP address and a context, context information corresponding to an IP address of the source UE and context information corresponding to an IP address of the destination UE;

The local routing capability detecting unit is configured to detect, in the context information of the source UE and the destination UE, whether the network element on the source UE and the destination UE bearer link has a local route establishment capability;

a routing request sending unit, configured to send a local routing request to the source UE and the network element on the destination UE bearer link when the local routing establishment capability is enabled, so that the source UE and the destination UE carry the local element of the network element on the link Configure, and enter data packets between the source UE and the destination UE. Line local route.

The device according to claim 14, further comprising:

The routing policy detecting unit is configured to: when the source UE and the target UE bearer link have the local routing establishment capability, check whether the source UE and the destination UE meet the local routing policy, so that the local routing policy is met. The local routing request is sent to the source UE and the network element on the destination UE bearer link.

A device for establishing a local route, comprising:

a routing request receiving unit, configured to receive a local routing request;

The local route establishing unit is configured to establish a binding relationship between the data packet sent by the source UE to the destination UE and the downlink bearer of the destination UE, and establish a binding relationship between the data packet sent by the destination UE and the source UE to the downlink bearer of the source UE. The data packet between the source UE and the destination UE is locally routed according to the binding relationship.

The device according to claim 16, wherein, when the network element that performs the local route establishment is the source SGW on the PDN connection where the source UE is located and the destination SGW on the PDN where the destination UE is located, the local The route establishment unit further includes:

The tunnel request sending module is configured to forward the local routing request to the source MME on the PDN connection where the source UE is located, so that the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW, and the destination SGW is in the allocation source. After the SGW forwards the tunnel to the destination SGW, the forwarding tunnel identifier is returned to the source MME;

a first tunnel receiving module, configured to receive a forwarding tunnel identifier that is forwarded by the source SGW to the source MME and forwarded by the source MME;

The first binding establishment module is configured to establish a binding relationship between the forwarding tunnel identifier and the data packet sent by the source UE to the destination UE, so that the data packet is delivered to the destination SGW through the forwarding tunnel.

The apparatus according to claim 17, wherein the destination SGW establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE after the source SGW is allocated to the forwarding tunnel of the destination SGW, so that the destination SGW establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE. The data packet that is forwarded to the destination SGW by the forwarding tunnel is sent to the destination UE.

The device according to claim 17, wherein the local route is established. The unit also includes:

a tunnel request receiving module, configured to receive a forwarding tunnel establishment request from a destination SGW to a source SGW sent by the destination MME;

a second binding establishment module, configured to allocate a forwarding tunnel of the destination SGW to the source SGW, and establish a binding relationship between the forwarding tunnel identifier and the downlink bearer of the source UE;

The first tunnel sending module is configured to send the forwarding tunnel identifier of the destination SGW to the source SGW to the destination MME, so that the destination MME forwards the forwarding tunnel identifier of the destination SGW to the source SGW to the destination SGW, and the destination SGW establishes the destination SGW to the source SGW. The binding relationship between the forwarding tunnel identifier and the data packet sent by the destination UE to the source UE.

The apparatus according to claim 16, wherein, when the network element that performs the local route establishment is the source eNodeB on the PDN connection where the source UE is located and the destination eNodeB connected to the PDN where the destination UE is located, the local The route establishment unit further includes:

The third binding establishment module is configured to: after receiving the forwarding tunnel establishment request from the source eNodeB to the destination eNodeB, the source eNodeB allocates a forwarding tunnel to the destination eNodeB, and establishes a binding relationship between the forwarding tunnel identifier and the downlink bearer of the destination UE. And transmitting, by the source eNodeB, the forwarding tunnel of the source eNodeB to the destination eNodeB to the destination UE, and the second tunnel sending module, configured to return the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source MME, to The source MME forwards the forwarding tunnel identifier of the source eNodeB to the destination eNodeB to the source eNodeB, and the source eNodeB establishes a binding relationship between the forwarding tunnel identifier of the source eNodeB and the destination eNodeB and the data packet sent by the source UE to the destination UE.

The device according to claim 20, wherein the local route establishing unit further comprises:

a second tunnel receiving module, configured to receive a forwarding tunnel identifier of the destination eNodeB that is allocated by the source eNodeB and forwarded by the destination MME to the source eNodeB;

The fourth binding establishment module is configured to establish a binding relationship between the forwarding tunnel identifier of the destination eNodeB and the source eNodeB and the data packet sent by the destination UE to the source UE.

The device according to claim 2, wherein after the source eNodeB allocates the forwarding tunnel of the destination eNodeB to the source eNodeB, the destination eNodeB is established to the source eNodeB. The binding relationship between the forwarding tunnel identifier and the downlink bearer of the source UE.

A system for implementing local route establishment, characterized in that the system comprises the detecting device according to claims 14 to 15 and the establishing device according to claims 16 to 22.

The system according to claim 23, wherein when the source SGW on the PDN connection where the source UE is located and the destination SGW on the PDN connection where the destination UE is located include the establishing device, when the PGW includes the detecting device,

The PGW is configured to send a local routing request to the source SGW and the destination SGW, so that the source SGW and the destination SGW perform local routing configuration, and locally route the data between the source UE and the destination UE.

The source SGW is configured to: after receiving the local routing request of the PGW, forward the local routing request to the source MME on the PDN connection where the source UE is located, so that the source MME sends a forwarding tunnel establishment request from the source SGW to the destination SGW to the destination SGW;

The destination SGW is configured to return the forwarding tunnel identifier of the source SGW to the source SGW, and the source MME forwards the source tunnel to the source SGW.

The destination SGW is further configured to: after receiving the local routing request of the PGW, forward the received local routing request to the destination MME on the PDN connection where the destination UE is located, so that the destination MME sends the forwarding tunnel of the destination SGW to the source SGW to the source SGW. Request

The source SGW is further configured to return the forwarding tunnel identifier of the allocated destination SGW to the source SGW to the destination MME, and forwarded by the destination MME to the destination SGW.

The system according to claim 23 or 24, wherein the detecting device is integrated in an SGW or a PGW, and the establishing device is integrated in an SGW or an eNodeB.