WO2010031317A1

WO2010031317A1 - Processing method and apparatus for routing optimization bearing

Info

Publication number: WO2010031317A1
Application number: PCT/CN2009/073880
Authority: WO
Inventors: 胡伟华; 张进; 吴问付; 朱志明
Original assignee: 华为技术有限公司
Priority date: 2008-09-22
Filing date: 2009-09-11
Publication date: 2010-03-25
Also published as: CN101686522B; CN101686522A

Abstract

A processing method for routing optimization bearing is adapted for a scenario in which a terminal moves from an original visitor location routing optimization area to a target routing optimization area, when said terminal has created a routing optimization bearing in the original visitor location routing optimization area. The method includes: determining that the terminal has moved from the original visitor location routing optimization area to the target routing optimization area, or obtaining a notice to delete the routing optimization bearing; deleting the routing optimization bearing. Two processing devices for the routing optimization bearing are also provided.

Description

Route optimization bearer processing method and device

The present application claims priority to Chinese Patent Application No. 200810211456.7, entitled "Processing Method and Apparatus for Route Optimization Carrying", filed on September 22, 2008, the entire contents of which is hereby incorporated by reference. in.

Technical field

The present invention relates to wireless communication technologies, and in particular, to a method and apparatus for processing a route optimization bearer. Background technique

Currently, a Public Land Mobile Network (PLMN) typically includes at least one radio access network and at least one core network. The PLMNs are connected by a backbone transmission network. A network element in the core network provides access to an external packet data network (PDN, Packet Data Network). The PDN may be a packet data network in the form of the Internet, a Virtual Private Network (VPN), an IP Multimedia Subsystem (IMS), or the like. PDN is used to provide IP data services such as web browsing (WWW), VoIP (voice over IP), instant messaging (IM), video services, and data download services. Different PLMNs generally have different charging standards and provide different access services. If the range of a PLMN is too large, the PLMN can be further divided into a plurality of different areas, each of which includes at least one radio access network and at least one core network. There will also be different billing standards between these areas, as well as different access services. These areas are also connected by a backbone transmission network. For convenience of the following description, an area including at least one radio access network and at least one core network is collectively referred to as a route optimization area. For example, a PLMN may be referred to as a route optimization area, and the above-mentioned area included in the PLMN may also be referred to as a route optimization area, that is, a PLMN may include at least one route optimization area. A route optimization area may be an area covered by a country's mobile network, or may be an area of a country's mobile network including a radio access network and a core network.

In the prior art, when a terminal needs to use the data service provided by the PDN in its home route optimization area (generally, the home location is the place where the user of the terminal signs the contract with the operator and opens the mobile service), The terminal establishes a bearer for transmitting service data in its home route optimization area, so that the terminal can transmit service data between the bearer and the PDN. When the terminal moves to another route optimization area (generally called a visited route optimization area), if the terminal needs to transmit service data with the PDN, under normal circumstances, the terminal will establish a worship The radio access network of the in-situ route optimization area, the core network of the visited route optimization area, and the bearer of the core network of the home route optimization area for transmitting service data, and accessing the PDN through the core network of the home route optimization area . This bearer is called a non-route optimized bearer. Between the route optimization areas, the backbone transmission network is usually connected. Under normal circumstances, the backbone transmission network is expensive and expensive to use. When the terminal needs to use the data service provided by the PDN accessed from the core network of the visited route optimization area, the terminal can establish a route optimization bearer for transmitting the service data only in the visited route optimization area (ie, from the visit) The core network of the routing optimization area accesses the PDN), so that the terminal can transmit the service data between the PDNs accessed by the core network from the visited route optimization area by the route optimization bearer without using the original The bearer established in the route optimization area transmits the service data to the route optimization area to which it belongs, saves the network resources of the backbone transmission network connecting the route optimization areas, and reduces the tariff of the roaming service using the cross-route optimization area.

The inventor of the present invention found in the process of implementing the present invention: In the prior art, when the terminal moves from the visited route optimization area to another route optimization area, if the terminal has established a route in the visited route optimization area To optimize the bearer, the terminal switches the route optimized bearer established in the original visited route optimization area to the other route optimization area, and the bearer is connected to the above by the radio access network and the core network of the other route optimization area. When the number of terminals that access the route optimization area and access the PDN sample is particularly large, the bandwidth of the transmission resources between the occupied route optimization areas will be particularly large.

Summary of the invention

The embodiment of the present invention provides a method and a device for processing a route optimization bearer, where a terminal that establishes a route optimization bearer in a visited route optimization area moves from a visited route optimization area to another route optimization area, and the terminal needs to When transmitting service data between PDNs, the transmission resources between the route optimization areas are saved.

A route optimization bearer processing method is applicable to a terminal moving from a source visited route optimization area to a

The scenario of establishing a route optimization bearer includes: determining that the terminal moves from the source visited route optimization area to the target route optimization area, or obtaining a notification of deleting a route optimized bearer; deleting the route optimization bearer.

A processing device for routing optimized bearer, suitable for the terminal to move from the source visited route optimization area to The loading scenario includes: a detecting unit, configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area; and a bearer processing unit, configured to determine, in the detecting unit, that the terminal moves from the source visited route optimization area to the target After the route optimization area is deleted, the route optimization bearer created by the terminal in the route optimization area of the source visited area is deleted.

A processing device for routing optimized bearer, comprising: a message sending and receiving unit, configured to: when the terminal moves from the source visited route optimization area to the target route optimization area, obtain a notification of deleting the route optimized bearer; the bearer processing unit is used in the After receiving the notification of deleting the route optimization bearer, the message sending and receiving unit deletes the route optimization bearer created by the terminal in the route optimization area of the source visited area.

In the embodiment of the present invention, if it is determined that the terminal that establishes the route optimization bearer in the source visited route optimization area moves from the source visited route optimization area to the target route optimization area, the route optimization bearer may be deleted, so that Traffic data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any creative work.

FIG. 1 is a flowchart of a method for processing a route optimized bearer according to an embodiment of the present invention;

2 is a schematic diagram of an architecture of an evolved network;

3 is a schematic diagram of a network architecture of a Universal Mobile Terrestrial Service (UMTS) I General Packet Radio Service (GPRS); FIG. 4 is a network with mobility management function according to an embodiment of the present invention; FIG. 5 is a schematic structural diagram of another network element having a mobility management function according to an embodiment of the present invention; FIG. 6 is a flowchart of another method for processing a route optimization bearer according to an embodiment of the present invention; 7 is a schematic structural diagram of a network element having a function of creating a routing bearer according to an embodiment of the present invention; FIG. 8 is a schematic structural diagram of another network element having a function of creating a routing bearer according to an embodiment of the present invention;

FIG. 9 is a flowchart of another method for processing a route optimization bearer according to an embodiment of the present invention; FIG. 10 is a schematic structural diagram of another network element with mobility management function according to an embodiment of the present invention; FIG.

FIG. 11 is a schematic structural diagram of another network element with mobility management function according to an embodiment of the present invention; FIG.

FIG. 12 is a tracking area update in a cross-route optimization area according to a first preferred embodiment of the present invention;

(TAU, Trace Area Update) Flowchart for processing route optimization bearers in the process;

13 is a flowchart of processing a route optimization bearer in a relocation process in a cross-route optimization area according to a first preferred embodiment of the present invention;

14 is a flowchart of processing a route optimized bearer in a TAU flow across a route optimization area according to a second preferred embodiment of the present invention;

15 is a flowchart of processing a route optimized bearer in a Relocation process of a cross-route optimization area according to a second preferred embodiment of the present invention;

16 is a flowchart of processing a route optimization bearer in a TAU flow across a route optimization area according to a third preferred embodiment of the present invention;

17 is a flowchart of processing a route optimization bearer in a Relocation process of a cross-route optimization area according to a third preferred embodiment of the present invention;

18 is a flowchart of processing a route optimization bearer in a TAU flow across a route optimization area according to a fourth preferred embodiment of the present invention;

Figure 19 is a flow chart of processing a route optimized bearer in a Relocation flow across a route optimization area according to a fourth preferred embodiment of the present invention.

detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. 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.

First, a method and an apparatus for processing a route optimization bearer according to an embodiment of the present invention are described. A route optimization bearer processing method is applicable to a terminal moving from a source visited route optimization area to a

The scenario of establishing a route optimization bearer includes: determining that the terminal moves from the source visited route optimization area to the target path By the optimization area, or obtaining the notification of deleting the route optimization bearer; deleting the route optimization bearer. In the embodiment of the present invention, the network element with the mobility management function of the source route optimization area, the network element with the mobility management function of the target route optimization area, or the source route optimization area is created with the route optimization bearer. The network element may determine that the terminal moves from the source visited route optimization area to the target route optimization area; the network element with the mobility management function of the source visited route optimization area, and the network element or source with the mobility management function of the target route optimization area The network element with the route optimization bearer created in the route optimization area of the visited area can delete the route optimization bearer. For example, the mobility management network element (MME, Mobility Management Entity) of the source PLMN or the serving GPRS Supporting Node (SGSN), the network element with mobility management function of the target route optimization area is, for example, the target PLMN. MME or SGSN, source visited route optimization area, the network element with route optimization bearer is, for example, the source PLMN's Serving Gateway (S-GW, Serving Gateway) or the Gateway General Packet Radio Service Support Node (GGSN, Gateway GPRS Supporting Node) ).

The network element with the mobility management function of the source-destination route optimization area determines that the terminal moves from the source-destination route optimization area to the target route optimization area, which may include: the network element with the mobility management function of the source-destination route optimization area is The location update process receives the handover request message sent by the network element with the mobility management function, and the handover request message carries the identifier of the route optimization area where the network element with the mobility management function is located; the source route optimization area The network element with the mobility management function determines whether the network element with the mobility management function has the mobility management function in the route optimization area of the source visited according to the identifier of the route optimization area where the network element with the mobility management function is located. In the route optimization area where the network element is located, if not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area. Here and below, the network element having the mobility management function is located in the target route optimization area to which the terminal moves, and the network element having the mobility management function is, for example, the target MME or the target SGSN.

The network element with the mobility management function of the source-destination route optimization area determines that the terminal moves from the source-destination route optimization area to the target route optimization area, which may include: the network element with the mobility management function of the source-destination route optimization area is The location update process or the relocation process obtains a specific identifier, and the specific identifier has a mapping relationship with the identifier of a route optimization area; the source visited route optimization area has The network element of the mobility management function obtains the identifier of the route optimization area where the target network element having the mobility management function corresponding to the specific identifier is located according to the mapping relationship between the specific identifier and the identifier of the route optimization area, and determines that the target has a movement. Whether the network element of the sexual management function is in the route optimization area where the network element with mobility management function of the source route optimization area is located, if not, determines that the terminal moves from the source visited route optimization area to the target route optimization area.

The notification of the deleted route optimization bearer may be: the network element with the mobility management function or the route optimization area of the source visited route optimization area, and the network element with the route optimization bearer obtains the notification of deleting the route optimized bearer; The route optimization optimization bearer is specifically: the network element with the mobility management function or the route optimization area of the source visited route optimization area is created by the network element deleting the route optimization bearer.

The network element deleting the route optimization bearer of the mobility management function of the source-destination route optimization area may include: the MME requesting the source-destined route optimization area, the S-GW of the source-destination route optimization area, the route-optimized bearer, or the source visited The SGSN of the local route optimization area requests the GGSN of the route optimization area to delete the route optimized packet data protocol context (PDP, Packet Data Protocol Context).

The network element with the mobility management function of the target route optimization area determines that the terminal moves from the source visited route optimization area to the target route optimization area, which may include: the network element with the mobility management function of the target route optimization area is in the location update process. Receiving a request context response message sent by the network element with the mobility management function, and requesting the context response message carrying the identifier of the route optimization area where the source network having the mobility management function is located; and the mobility management of the target route optimization area The function network element determines whether the network element with the mobility management function is in the route optimization of the network element with the mobility management function in the target route optimization area according to the identifier of the route optimization area where the source network having the mobility management function is located. In the area, if not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The network element with the mobility management function of the target route optimization area determines that the terminal moves from the source visited route optimization area to the target route optimization area, which may include: the target routing optimization area has the mobility management function of the network element in the location update process or A specific identifier is obtained in the relocation process, and the mapping between the specific identifier and the identifier of a route optimization area is performed; and the mapping between the specific identifier and the identifier of the route optimization area is determined by the network element with the mobility management function of the target route optimization area. , obtained with a specific identifier The corresponding source has the identifier of the route optimization area where the network element of the mobility management function is located, and determines whether the network element with the mobility management function is in the route optimization area where the network element with the mobility management function in the target route optimization area is located. If not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The network element deleting the route optimization bearer with the mobility management function in the target route optimization area may include: the network element with the mobility management function of the target route optimization area, and the network element with the mobility management function of the source route optimization area of the visited route The route optimization bearer is deleted, or the MME of the target route optimization area notifies the S-GW of the target route optimization area to delete the part of the route bearer that is switched to the target route optimization area.

The destination route optimization area is created. The network element with the route optimization bearer obtains the notification of the deleted route optimization bearer. The specific information may be: The packet data network gateway (P-GW, Packet Data Network Gateway) of the source visited route optimization area obtains the source visit. The notification of the deleted route optimization bearer sent by the S-GW of the local route optimization area, or the GGSN of the source visited route optimization area obtains the notification of deleting the route optimized bearer issued by the SGSN of the source visited route optimization area.

The source-deleted route optimization area is created by the source-deleted route optimization. The source-deleted route-optimized bearer may include: the source-destined route optimization area is created.

In the foregoing method, if it is determined that the terminal that establishes the route optimization bearer in the route optimization area of the source visited area moves from the source visited route optimization area to the target route optimization area, the route optimization bearer may be deleted, so that crossover does not occur. The service data transmission in the route optimization area saves the transmission resources between the route optimization areas.

In addition to the processing method of the route optimization bearer, the embodiment of the present invention further provides a processing device for routing optimized bearer, which is suitable for the terminal to move from the source visited route optimization area to the target route optimization area and the terminal is routed in the source visited route. A scenario in which a route optimization bearer is created in the area includes: a detecting unit, configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area; the bearer processing unit, except for the route optimization created by the terminal in the source visited route optimization area Hosted.

The processing device of the route optimization bearer may be disposed in the network element with the mobility management function in the route optimization area of the source visited area, and the detecting unit may include: a message sending and receiving unit, used in the location update process Receiving a handover request message sent by a network element having a mobility management function, where the handover request message carries an identifier of a route optimization area where the network element having the mobility management function is located; and a determination unit, configured to be mobility according to the target The identifier of the route optimization area where the network element of the management function is located determines whether the network element with the mobility management function is in the route optimization area where the network element with mobility management function of the source route optimization area is located, if not, It is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The processing device of the route optimization bearer may be disposed in the network element with the mobility management function of the source route optimization area, and the detecting unit may include: a message sending and receiving unit, configured to obtain a specific identifier in the location update process or the relocation process, The specific identifier has a mapping relationship with the identifier of a route optimization area; the determining unit is configured to obtain, according to the mapping relationship between the specific identifier and the identifier of the route optimization area, the network element having the mobility management function corresponding to the specific identifier The identifier of the route optimization area, and whether the network element with the mobility management function is located in the route optimization area where the network element with mobility management function of the source route optimization area is located, if not, the terminal is determined from The source visited route optimization area moves to the target route optimization area.

The processing device of the route optimization bearer may be set in the MME of the source visited route optimization area or

In the SGSN, the bearer processing unit may include: a requesting unit, configured to request the S-GW of the source visited route optimization area to delete the route optimized bearer, or request the GGSN of the source visited route optimization area to delete the route optimized PDP context.

The processing device of the route optimization bearer may be disposed in the network element with the mobility management function in the target route optimization area, and the detecting unit may include: a message sending and receiving unit, configured to receive the source network having the mobility management function in the location update process The request context response message sent by the element, the request context response message carries the identifier of the route optimization area where the source network element having the mobility management function is located; the determining unit is configured to optimize the route according to the source network element with the mobility management function The identifier of the area determines whether the network element with the mobility management function is in the route optimization area where the network element with the mobility management function of the target route optimization area is located, and if not, determines that the terminal moves from the source visited route optimization area to Target route optimization area.

The processing device of the route optimization bearer may be disposed in the network element with the mobility management function in the target route optimization area, and the detecting unit may include: a message sending and receiving unit, configured to acquire the specific identifier, the specific identifier in the location update process or the relocation process Mapping with the identity of a route optimization zone a determining unit, configured to obtain, according to a mapping relationship between the specific identifier and the identifier of the route optimization area, obtain an identifier of a route optimization area where the source with the mobility management function corresponding to the specific identifier is located, and determine that the source has a movement Whether the network element of the sexual management function is in the route optimization area where the network element with mobility management function of the target route optimization area is located, if not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The processing device of the route optimization bearer may be set in the MME of the target route optimization area, and the bearer processing unit may include: a notification unit, configured to notify the MME of the source visited route optimization area to delete the route optimization bearer, or notify the target route optimization area of the S - GW deletes the part of the route bearer that is switched to the target route optimization area.

The processing device of the route optimization bearer may be set in the network element of the route-optimized area of the source-destined routing optimization area, and the bearer processing unit may include: an initiating unit, configured to initiate the delete route optimization bearer.

In the above apparatus, if the detecting unit determines that the terminal that establishes the route optimization bearer in the route optimization area of the source visited area moves from the source visited route optimization area to the target route optimization area, the bearer processing unit may delete the route optimized bearer, Traffic data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

The embodiment of the present invention further provides another processing device for routing optimized bearer, including: a message sending and receiving unit, configured to obtain a notification for deleting a route optimized bearer when the terminal moves from the source visited route optimization area to the target route optimization area; The bearer processing unit is configured to delete the route optimized bearer created by the terminal in the route optimization area of the source visited after the notification unit obtains the notification of deleting the route optimized bearer.

The processing device of the route optimization bearer may be set in the network element with the mobility management function in the route optimization area of the source visited area, and the notification of the deleted route optimization bearer obtained by the message sending and receiving unit may be the mobility management function of the target route optimization area. The network element issued.

The processing device of the route optimization bearer may be set in the MME or the SGSN of the source-destination routing optimization area, and the bearer processing unit may include: a requesting unit, configured to request the S-GW to delete the route optimized bearer of the source-destined routing optimization area, or request The GGSN of the source visited route optimization area deletes the route optimized PDP context.

The processing device of the route optimization bearer may be set in the P-GW of the route optimization area of the source visited area, and the notification of the deleted route optimized bearer obtained by the message receiving unit may be the route of the source visited route optimization area. The processing device of the route optimization bearer may be set in the GGSN of the route optimization area of the source visited area, and the notification of the deleted route optimization bearer obtained by the message receiving unit may be sent by the SGSN of the source visited route optimization area.

In the foregoing apparatus, if the messaging unit receives the notification of deleting the route optimization bearer, the bearer processing unit may delete the route optimization bearer, so that the service data transmission across the route optimization area does not occur, thereby saving the route between the optimized areas. Transmission resources.

The method and apparatus for processing a route optimization bearer according to an embodiment of the present invention are described in detail below with reference to the accompanying drawings.

As shown in FIG. 1 , a method for processing a route optimized bearer is applicable to a scenario in which a terminal routes a bearer from a source, including:

Step S101: The network element with the mobility management function of the source-destination route optimization area determines that the terminal moves from the source visited route optimization area to the target route optimization area, or the source-destination route optimization area has the mobility management function network element. Determining the retargeting target The network element with the mobility management function is not in the source visited route optimization area, or the network having the mobility management function of the source visited route optimization area. Step S102: Mobility of the source visited route optimization area The network element of the management function informs the source route in the route optimization area to create a route optimization bearer with the route optimization bearer.

The method shown in Figure 1 can be applied to an evolved network. The architecture of the evolved network is as shown in FIG. 2, including an evolved Evolved Universal Terrestrial Radio Access Network (E-UTRAN) for implementing all functions related to the evolved network radio; MME, responsible for control plane Mobility management, including user context and mobility state management, assigning Temporary Mobile Subscriber Identity (TMSI), etc.; S-GW is a user plane anchor between 3GPP access networks, terminating E-TURAN interface; The GW is a user plane anchor between the 3GPP access network and the non-3GPP access network, and has an interface with the PDN. The Home Subscriber Server (HSS) is used to store user subscription information. MME, S-GW, P-GW and HSS Usually used as a network element of the core network. If the method shown in FIG. 1 is applied to an evolved network, the network element with the mobility management function of the source visited route optimization area is the MME of the source visited route optimization area, and the source visited route optimization area is created between the terminal and the terminal. The network element with the route optimization bearer is the P-GW of the source route optimization area, and the network element of the target route optimization area that issues the notification of deleting the route optimization bearer is the MME of the target route optimization area.

The network element with the mobility management function in the route-optimized area of the source-destination route is notified to the source-deleted route optimization area. The MME may request the S-GW of the source visited route optimization area to delete the route optimized bearer, and then the S-GW of the source visited route optimization area requests the P-GW of the source route optimization area to delete the route optimized bearer.

The method shown in Figure 1 can be applied to a UMTS system or a GPRS system. The network architecture of UMTS/GPRS is shown in FIG. 3, including: Universal Terrestrial Radio Access Network (UTRAN), which usually includes multiple Radio Network Controllers (RNCs) and wireless transmission nodes ( NodeB), used to implement the wireless access function in the UMTS system; GSM/EDGE Radio Access Network (GERAN, GSM/EDGE Radio Access Network), usually including multiple base station controllers (BSCs) and base stations ( BS, Base Station), used to implement wireless access function in GPRS system; SGSN, used to implement routing forwarding, mobility management, session management and user information storage in GPRS/UMTS system; GGSN is used to connect external PDN; Home Location Register (HLR), used to store user subscription information about network services. The SGSN, GGSN, and HLR are usually used as core network elements (CN, Core Network). The architecture and flow of the GPRS system is described in the 3GPP TS 23.060 standard.

If the method shown in FIG. 1 is applied to the UMTS/GPRS system, the network element with the mobility management function of the source visited route optimization area is the SGSN of the source visited route optimization area, and the source visited route optimization area and the terminal The network element that creates the route optimization bearer is the GGSN of the source route optimization area, and the network element of the target route optimization area that issues the notification of deleting the route optimization bearer is the SGSN of the target route optimization area.

The network element with the mobility management function of the source-destination route optimization area informs the source route of the route optimization area and the network element with the route optimization bearer to delete the route optimization bearer. The GGSN of the source visited route optimization area of the source visited route GGSN deletes the route optimized PDP context.

In the method shown in FIG. 1, if the network element with mobility management function of the source visited route optimization area determines that the terminal moves from the source visited route optimization area to the target route optimization area, or the source visited route optimization area has The network element of the mobility management function determines that the relocation target has the mobility management function of the network element not in the source visited route optimization area, or the source visited route optimization area has mobility, and the source visited route optimization area has the movement The network element of the sexual management function informs the source routing optimization area to create a route optimization bearer between the terminal and the terminal to delete the route optimization bearer, so that the service data transmission across the route optimization area does not occur, thereby saving route optimization. Transmission resources between zones.

The method shown in Figure 1 can be implemented by a variety of forms of network elements.

One of the network elements with mobility management function is as shown in FIG. 4, and is applicable to the terminal moving from the source visited route optimization area to the target route optimization area, and the terminal creates a route optimization bearer in the source visited route optimization area. The network element with the mobility management function is set in the route of the source visited route optimization area, and includes: a detecting unit 401, configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area, or determines the retargeting target. The network element with the mobility management function is not in the source route optimization area; the notification unit 402 is configured to: after the detecting unit 401 determines that the terminal moves from the source visited route optimization area to the target route optimization area, or the detection unit determines the weight After the network element with the mobility management function of the target is not in the route optimization area of the source, the network element that deletes the route optimization bearer is created between the source route optimization area and the terminal. The network element with mobility management function to the target route optimization area or the source visited route optimization area determines that the relocation target has the mobility management function of the network element not in the source visited route optimization area, or the source visited route optimization The network element with the mobility management function of the area obtains the notification of deleting the route optimization bearer sent by the network element in the target route optimization area, and the notification unit notifies the network element of the route optimization area and the terminal to create the route optimized bearer between the source and the destination route optimization area. The route optimization bearer is deleted, so that the service data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

Another network element with mobility management function is shown in FIG. 5, which is suitable for the terminal to move from the source visited route optimization area to the target route optimization area, and the terminal creates a route excellent in the source visited route optimization area. And the notification unit 502 is configured to notify the source of the route optimization area according to the notification obtained by the obtaining unit 501, and the notification unit 502 is configured to notify the source of the route optimization area according to the notification obtained by the obtaining unit 501. An NE that deletes a route optimization bearer is created between the terminals.

In the network element shown in FIG. 5, if the obtaining unit obtains the notification of deleting the route optimization bearer sent by the network element of the target route optimization area, the notification unit notifies the source visited route optimization area that a route optimization bearer is created between the terminal and the terminal. The network element deletes the route optimization bearer, so that the service data transmission across the route optimization area does not occur, thereby saving the transmission resources between the route optimization areas.

It should be noted that the network element with mobility management function shown in FIG. 4 and FIG. 5 may refer to the MME in the evolved network, and may refer to the SGSN in the UMTS/GPRS system.

Another method for processing a route-optimized bearer is as shown in FIG. 6 , which is applicable to a scenario in which a terminal routes a bearer from a source, including:

Step S601: A network element that creates a route optimization bearer between the source-destination route optimization area and the terminal determines that the terminal moves from the source visited route optimization area to the target route optimization area, or between the source visited route optimization area and the terminal. The network element that has the route optimization bearer is configured to obtain the notification of deleting the route optimization bearer sent by other network elements in the source route optimization area;

Step S602: The network element deleting the route optimization bearer is created between the source and destination routing optimization areas and the terminal.

If the method shown in FIG. 6 is applied to the evolved network, the network element that creates the route optimization bearer between the source and the route optimization area and the terminal may refer to the P-GW of the source route optimization area, and issues the delete route optimization. The other network elements of the source visited route optimization area of the carried notification may refer to the S-GW of the source visited route optimization area.

If the method shown in FIG. 6 is applied to the UMTS system or the GPRS system, the network element that creates the route optimization bearer between the source and the route optimization area and the terminal may refer to the GGSN of the source route optimization area, and issues the delete route. Other network elements of the source visited route optimization area of the optimized bearer notification may refer to the SGSN of the source visited route optimization area.

In the method shown in FIG. 6, if the network element that creates the route optimization bearer between the source and the route optimization area and the terminal determines that the terminal moves from the source visited route optimization area to the target route optimization area, or The network element that creates the route optimization bearer between the source route optimization area and the terminal obtains the notification of the deleted route optimization bearer sent by other network elements in the source visited route optimization area, and the source visited the route optimization area and the terminal The network element with the route optimization bearer is deleted to delete the route optimization bearer, so that the service data transmission across the route optimization area does not occur, thereby saving the transmission resources between the route optimization areas.

The method shown in Figure 6 can be implemented by a variety of forms of network elements.

One of the network elements having the function of creating a routing bearer is as shown in FIG. 7 , and is applicable to the terminal moving from the source visited route optimization area to the target route optimization area, the terminal in the source visited route optimization area, and having the function of creating a route bearer. A scenario in which a network element with a routing optimization bearer is created and a network element with a routing bearer function is set in the route optimization area of the source visited area includes: a detecting unit 701, configured to determine that the terminal moves from the source visited route optimization area to The target routing optimization unit 702 is configured to delete the route optimization bearer after the determining unit 701 determines that the terminal moves from the source visited route optimization area to the target route optimization area. To the target route optimization area, the bearer processing unit deletes the route optimization bearer, so that the service data transmission of the cross-optimization area does not occur, thereby saving transmission resources between the route optimization areas.

Another network element having a routing bearer function is as shown in FIG. 8 , and is applicable to the terminal moving from the source visited route optimization area to the target route optimization area, the terminal in the source visited route optimization area, and having the function of creating a route bearer. A scenario in which a network element with a route optimization bearer is created between the network elements and the network element with the function of creating a route bearer is set in the route optimization area of the source visited area includes: an obtaining unit 801, configured to obtain a source call

802. The 802 is configured to delete the route optimization bearer according to the notification obtained by the obtaining unit 801.

In the network element shown in FIG. 8, if the obtaining unit obtains the notification of deleting the route optimized bearer sent by other network elements in the source-advanced route optimization area, the bearer processing unit deletes the route optimization bearer, so that cross-route optimization does not occur. The area's service data is transmitted, thereby saving transmission resources between the route optimization areas.

It should be noted that the network element having the function of creating a routing bearer shown in FIG. 7 and FIG. 8 may refer to a P-GW in an evolved network, and may be referred to as a GGSN in a UMTS/GPRS system.

In addition to the methods shown in FIG. 1 and FIG. 6, the embodiment of the present invention further provides a method for processing a route optimized bearer, which is applicable to a terminal moving from a source visited route optimization area to a target route optimization area. The terminal creates a route optimized bearer in the route optimization area of the source visited area, as shown in FIG. 9, and includes: Step S901: The network element with the mobility management function of the target route optimization area determines the route optimization area of the terminal from the source visited area. Move to the target route optimization area;

Step S902: The network element with the mobility management function of the target route optimization area notifies the network element with the mobility management function of the source route optimization area to delete the route optimization bearer, or initiates the deletion of the route optimized bearer and has switched to the target route optimization. The part of the zone is carried by the route.

If the method shown in FIG. 9 is applied to an evolved network, the network element having the mobility management function may refer to the MME.

The part of the route-optimized bearer that has been switched to the target route optimization area in the target route optimization area may include: the MME of the target route optimization area requests the S-GW of the target route optimization area The part of the route bearer that is switched to the target route optimization area is deleted; the S-GW of the target route optimization area deletes the part of the route bearer that is switched to the target route optimization area, and notifies the P-GW of the source visited route optimization area to delete the route optimized bearer. .

If the method shown in FIG. 9 is applied to a UMTS system or a GPRS system, the route optimization area may refer to a route optimization area, and the network element having mobility management function may refer to an SGSN.

The part of the route-optimized bearer that has been switched to the target route optimization area in the target route optimization area may include: the SGSN deletion of the target route optimization area has been switched to the target route optimization area. The GTP tunnel, and notifying the GGSN of the source visited route optimization area to delete the route-optimized PDP context.

In the method shown in FIG. 9, if the network element with mobility management function of the target route optimization area determines that the terminal moves from the source visited route optimization area to the target route optimization area, the target route optimization area has mobility management function. The network element notifies the network element with the mobility management function in the route optimization area of the source to delete the route optimization bearer, or initiates the part of the route bearer that has been switched to the target route optimization area in the deleted route optimization bearer, so that the crossover does not occur. The service data transmission in the route optimization area saves the transmission resources between the route optimization areas.

The method shown in Figure 9 can be implemented by a variety of forms of network elements.

One of the network elements with the mobility management function is as shown in FIG. 10, and is applicable to the terminal moving from the source visited route optimization area to the target route optimization area, and the terminal creates a route optimization bearer in the source visited route optimization area. The network element with mobility management function is set in the scenario in the target route optimization area. The method includes: a detecting unit 1001, configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area; and the notifying unit 1002 is configured to: after the detecting unit 1001 determines that the terminal moves from the source visited route optimization area to the target route optimization area The network element with the mobility management function of the route optimization area of the notification source is deleted from the route to optimize the bearer.

In the network element shown in FIG. 10, if the detecting unit 1001 determines that the terminal moves from the source visited route optimization area to the target route optimization area, the notifying unit 1002 notifies the network element with the mobility management function of the source visited route optimization area. The route optimization bearer is deleted, so that the service data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

Another network element with mobility management function is shown in FIG. 11 , and is applicable to the terminal moving from the source visited route optimization area to the target route optimization area, and the terminal creates a route optimization bearer in the source visited route optimization area and has The scenario in which the network element of the mobility management function is set in the target route optimization area includes: a detecting unit 1101, configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area; and the bearer processing unit 1102 is configured to detect The unit 1101 determines that the terminal moves from the source visited route optimization area to the target route optimization area, and initiates the part of the route bearer that has been switched to the target route optimization area in the deleted route optimized bearer.

In the network element shown in FIG. 11, if the detecting unit 1101 determines that the terminal moves from the source visited route optimization area to the target route optimization area, the bearer processing unit 1102 initiates the deletion of the route optimized bearer that has been switched to the target route optimization area. Part of the routing bearer, so that the service data transmission across the route optimization area does not occur, thereby saving the transmission resources between the route optimization areas.

It should be noted that the network element with mobility management function shown in FIG. 10 and FIG. 11 may refer to the MME in the evolved network, and may refer to the SGSN in the UMTS/GPRS system.

It should be noted that, if all the foregoing method embodiments and network element embodiments are applied or set in a play network, a UMTS system, or a GPRS system, the foregoing terminal may refer to a user equipment (UE,

User Equipment ). To make the embodiments of the present invention more clearly understood by those skilled in the art, several preferred embodiments are described below.

First preferred embodiment

For an evolved network, the UE is in an MME of a visited route optimization area (hereinafter referred to as a source MME) Attached, and created a route optimization bearer on the P-GW (hereinafter referred to as the source P-GW) of the source visited route optimization area, including the default bearer and the specific bearer. Of course, the UE can also create a non-route optimized bearer on the P-GW of the home route optimization area at the same time. If the MME of the source visited route optimization area (hereinafter referred to as the source MME) detects that the UE moves to another route optimization area (hereinafter referred to as a target route optimization area), the S-GW of the source visited route optimization area is notified (hereinafter referred to as Release the route optimization bearer of the UE for the source S-GW.

The way in which the source MME detects that the UE moves to another route optimization area is as follows:

1) The source MME receives the handover request message sent by the MME (hereinafter referred to as the target MME) of the other route optimization area in the TAU process, where the message carries the identifier of the route optimization area where the target MME is located, and the source MME according to the route of the target MME The identifier of the optimization area determines whether the target MME is in the route optimization area where the source MME is located.

2) The source MME obtains a specific identifier (for example, a target tracking area identifier TAI) in the TAU process or the Relocation process, and the source MME obtains the target MME corresponding to the specific identifier according to the mapping relationship between the specific identifier and the identifier of the route optimization area. The identifier of the route optimization area, and whether the target MME is in the route optimization area where the source MME is located.

The process of processing the route optimization bearer in the TAU process across the route optimization area is as shown in FIG. 12, and the specific steps are as follows:

After the UE detects the change of the tracking area across the route optimization area, the UE sends a TAU request message to the E-UTRAN (E-UTRAN in FIG. 12) in the target route optimization area, where the message carries the TAI of the source visited route optimization area. And Globally Unique Temporary Identity (GUTI).

The E-UTRAN sends a TAU request message to the MME in the target route optimization area (the target route optimization area in FIG. 12), and the message carries the GUTI of the source visited route optimization area. The GUTI packet includes an MME code, a Mobile Network Code (MNC) and a Mobile Country Code (MCC) of the MME, and the target route optimization area may retrieve the MME corresponding to the information included in the GUTI according to the GUTI.

The target MME determines, according to the GUTI of the source-destination routing optimization area, that the information included in the GUTI is the source MME, and sends a request context message to the source MME, where the message carries the identifier of the route optimization area where the target MME is located. Or add a new target TAI. S1204. The source MME detects that the target MME belongs to another route optimization area according to the identifier of the route optimization area where the target MME is located, or the mapping relationship between the TAI and the identifier of the route optimization area configured by the source MME according to the target TAI and the source MME. It is detected that the target MME belongs to another route optimization area, or the source MME obtains the mapping relationship between the identifier of the target MME (usually an IP address) and the identifier of the MME configured by the source MME and the identifier of the route optimization area, to obtain the target MME. The identifier of the route optimization area is detected, and it is detected that the target MME belongs to other route optimization areas.

At the same time, the target MME can be identified by the identifier of the UE (International Mobile Subscriber Identity (IMSI), Mobile International ISDN Number (MSISDN) or other network access identifiers of the UE. Obtaining the home route optimization area information of the UE, detecting that the UE is a roaming UE.

S1205a. The source MME returns a message requesting a context response to the target MME, where the message carries the IMSI of the UE, the authentication quintuple of the UE, the non-route optimized bearer context, the S-GW signaling plane address, and the tunnel endpoint identifier. (TEID, Tunnel End Indentifier) and other information.

S1205b. The target MME sends a request to the target S-GW to establish a non-route optimized bearer message. The target S-GW establishes a non-route optimized bearer context and notifies the P-GW located in the home route optimization area to establish a context of the non-route optimized bearer. The MME notifies the HSS in the location update message, and updates the information of the MME where the UE is stored in the HSS. In addition, the MME notifies the radio access network element to reserve the corresponding radio resource for the non-route optimized bearer of the UE, and the information such as the TEID allocated by the S-GW for the non-route optimized bearer.

S1206a. The source MME requests the source S-GW to deactivate all route optimization bearers of the UE. S1206b. The source S-GW requests the source P-GW to deactivate all route optimization bearers of the UE. S1206c. The source P-GW then initiates the process of deleting the route optimization bearer. The source P-GW sends a delete bearer message to the source S-GW. The source S-GW deletes the route optimization bearer context information of the user, and sends a delete bearer message to the source MME. The source MME deletes the route optimization bearer context information of the user, and notifies the radio access network element to delete the radio resource occupied by the route optimization bearer.

It should be noted that steps S1205a, S1205b, and S1206a, S1206b, and S1206c are independent of each other, and there is no order relationship.

In the flow shown in FIG. 12, if the source MME detects that the target MME belongs to another path By the optimization zone, the source MME requests the source S-GW to deactivate all the route optimization bearers of the UE, and the source S-GW requests the source P-GW to deactivate all the route optimization bearers of the UE, so that the cross-route optimization zone does not occur. Service data transmission, thereby saving transmission resources between route optimization areas.

The process of processing the route optimization bearer in the Relocation process across the route optimization area is shown in Figure 13. The specific steps are as follows:

51301. E-UTRAN (hereinafter referred to as source E-UTRAN) of the source visited route optimization area and E-UTRAN (hereinafter referred to as target E-UTRAN) of the target route optimization area trigger a relocation process across the route optimization area.

The source E-UTRAN sends a Handover Request message to the source MME, where the message carries the information of the target E-UTRAN (including the evolved base station in the target E-UTRAN).

(E-NodeB) identifies the TAI of the TA where the E-NodeB is located. The source MME obtains the information of the target route optimization area according to the TAI of the E-NodeB in the handover request message and the mapping relationship between the TAI configured by the source MME and the identifier of the route optimization area, or the source MME parses the target MME from the TAI. The identifier (usually an IP address), or the source MME obtains the information of the target route optimization area according to the mapping relationship between the MME identifier configured by the source MME and the identifier of the route optimization area.

If the source MME detects that the target MME is not in the route optimization area where the source MME is located, and the source MME finds that the UE is a roaming UE according to the identifier of the UE, and the UE establishes a route optimization bearer on the source P-GW, the source MME goes to the target. The MME sends a Relocation Request message, where the message carries the information of the target E-UTRAN, the non-route optimized bearer context information of the UE, the address of the source S-GW, and the TEID.

51304. The target MME sends a handover request message to the target E-UTRAN, and the target E-UTRAN reserves the air interface resource for the non-route optimized bearer of the UE.

51305. The target E-UTRAN returns a handover response message, indicating that the air interface resource reserved for the non-route optimized bearer reserved by the UE has been reserved.

S1306. The target MME sends a relocation response message to the source MME.

51307. The source MME sends a message for deleting the route optimized bearer to the source S-GW.

51308. The source S-GW sends a message for deleting the route optimized bearer to the source P-GW.

51309. The source P-GW initiates a process of deleting a route optimization bearer. This process is the same as the process described in S1206c of FIG. 12 in which the source P-GW initiates the deletion of the route optimization bearer. 51310. The source MME sends a handover command to the source E-UTRAN.

51311. The source E-UTRAN sends a handover command to the UE.

51312. The UE switches to the target route optimization area.

It should be noted that, after receiving the relocation response message of the target MME, the source MME immediately initiates a process of switching the non-route optimized bearer of the UE to the target route optimization area (including notifying the UE to switch to the target route optimization area). The source MME instructs the UE to switch to the radio access network of the target route optimization area. After receiving the handover confirmation message of the UE, the target radio access network element notifies the target MME that the UE has switched to the target route optimization area. The target MME sends a request to the target S-GW to establish a non-route optimization bearer message. The target S-GW establishes a non-route optimized bearer context, and notifies the P-GW located in the home route optimization area to establish a context of the non-route optimized bearer. After the S-GW establishes the route optimization bearer context, the target MME notifies the radio access network element S-GW of the TEID and other information allocated for the non-route optimization bearer. The target MME notifies the HSS in the location update message, and updates the information of the MME where the UE stored in the HSS is located.

In the process shown in FIG. 13, if the source MME detects that the target MME is not in the route optimization area where the source MME is located, the source MME sends a message for deleting the route optimized bearer to the source S-GW, and the source S-GW sends the delete route optimized bearer. The message is sent to the source P-GW, so that the service data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas. Second preferred embodiment

For the GPRS system, the UE attaches to the SGSN (hereinafter referred to as the source SGSN) of the source visited route optimization area, and creates a route optimized GPRS tunneling protocol on the GGSN of the source visited route optimization area (hereinafter referred to as the source GGSN). (GTP, GPRS Tunnel Protocol) Tunnels Because GTP tunnels are managed through PDP contexts, creating route-optimized GTP tunnels can also be described as creating route-optimized PDP contexts. Of course, the UE can also create a non-route optimized PDP context on the GGSN of the home route optimization area at the same time. If the source SGSN detects that the UE moves to the target route optimization area, the GGSN in the source route optimization area is notified to deactivate the route optimized PDP context of the UE.

The source SGSN detects that the UE moves to other route optimization areas as follows:

1) The source SGSN receives the RAU sent by the target SGSN of other route optimization areas in the RAU process. The request message carries the identifier of the route optimization area where the target SGSN is located. The source SGSN determines whether the target SGSN is in the route optimization area where the source SGSN is located according to the identifier of the route optimization area where the target SGSN is located.

2) The source SGSN obtains a specific identifier (for example, a target routing area identifier RAI or an SGSN identifier) in the RAU process or the Relocation process, and the source SGSN obtains a mapping relationship between the specific identifier configured by the source SGSN and the identifier of the route optimization area. The identifier of the route optimization area where the target SGSN is located corresponding to the specific identifier, and whether the target SGSN is in the route optimization area where the source SGSN is located.

The process of processing the route optimization bearer in the RAU process across the route optimization area is shown in Figure 14. The specific steps are as follows:

S 1401. After the UE moves to the target route optimization area, the target UTRAN/GERAN is used to target

The SGSN sends a RAU request message, and the message carries information such as the source RAI.

The target SGSN sends an SGSN Context Request message to the source SGSN, and the message carries the identifier of the target route optimization area, the identifier of the target SGSN, or the target RAI. After receiving the SGSN Context Request message, the source SGSN detects that the target SGSN belongs to another route optimization area according to the identifier of the target route optimization area in the message, or the source SGSN identifies the SGSN according to the identifier of the target SGSN and the source SGSN. Optimizing the mapping relationship of the identifiers of the area, obtaining the identifier of the route optimization area corresponding to the identifier of the target SGSN, thereby detecting that the target SGSN belongs to other route optimization areas, or the source SGSN and the route optimization area according to the target RAI and the source SGSN configuration. The mapping relationship of the identifiers, the target RAI is converted into the identifier of the route optimization area, thereby detecting that the target SGSN belongs to other route optimization areas. The source SGSN also determines whether the UE is a roaming UE by using the identity of the UE.

51403. If the UE is a roaming UE and the UE creates a route optimized PDP context on the source GGSN, the source SGSN sends a Delete PDP Context Request message to the source GGSN.

51404. The source GGSN deletes the PDP context and returns a Delete PDP Context Response message to the source SGSN.

The source SGSN returns an SGSN Context Response message to the target SGSN, where the message carries information about the non-route optimized PDP context created by the UE.

51406. The target SGSN sends an Update PDP Context Request message to the GGSN of the Home Route Optimization Area to request to update the PDP context of the GGSN, and the GTP between the source SGSN and the GGSN. The tunnel is switched between the target SGSN and the GGSN.

51407. The GGSN of the home route optimization area updates the information of the SGSN in the information of the PDP context to the information of the target SGSN, and returns an update PDP context response message to the target SGSN. The process of switching to the target route optimization area.

51408. The target SGSN returns a RAU accept message to the UE.

In the process shown in FIG. 14, if the source SGSN detects that the target SGSN belongs to another route optimization area, the source SGSN sends a delete PDP context request message to the source GGSN, and the source GGSN deletes the PDP context, so that the cross-route optimization area does not occur. The business data is transmitted, thereby saving transmission resources between the route optimization areas.

The process of processing the route optimization bearer in the Relocation process across the route optimization area is shown in Figure 15. The specific steps are as follows:

51501. UE and source UTRAN/GERAN decision relocation.

The source UTRAN/GERAN sends a relocation request message to the source SGSN, where the message carries the network element identifier of the target UTRAN/GERAN (for example, the RNC identifier of the UTRAN), the source.

The network element identifier of the route optimization area where the UTRAN/GERAN is located, and the radio resource control information used for relocation.

51503. If the source SGSN is configured with the mapping relationship between the network element identifier of the UTRAN/GERAN and the identifier of the route optimization area, the source SGSN may obtain the other network optimization area corresponding to the target SGSN of the target UTRAN/GERAN. The source SGSN detects that the UE belongs to the roaming UE according to the identity of the UE. The source SGSN detects that the UE creates a route-optimized PDP context on the source GGSN according to the address of the GGSN or the Access Point Name (APN, Access Point Name) in the PDP context of the UE. The source SGSN detects the target SGSN according to the network element identifier of the target UTRAN/GERAN. The source SGSN forwards the relocation request message to the target SGSN, where the relocation message carries the mobility management (MM, Mobile Management) context of the UE and the non-route optimized PDP context.

The target SGSN sends a relocation request message to the target UTRAN/GERAN, where the message carries the network element identifier of the source UTRAN/GERAN, the network element identifier of the target UTRAN/GERAN, and the radio resource control information used for relocation. 51505. The target UTRAN/GERAN allocates radio resources and returns a relocation response message to the target SGSN.

51506. The target SGSN returns a relocation response message to the source SGSN. If the source SGSN cannot obtain the identifier of the target route optimization area in step S1503, the identifier of the target route area may be carried in the relocation response message.

The source SGSN sends a relocation command message to the source UTRAN/GERAN, where the message carries the radio resource information that the target UTRAN/GERAN network element delivers to the source UTRAN/GERAN network element.

51508. The source UTRAN/GERAN instructs the terminal to reconfigure the radio resource, including notifying the terminal of radio resource information related to the network element of the target UTRAN/GERAN.

S1509. The source SGSN sends a delete PDP context request message to the source GGSN, which is used to delete the route optimized PDP context. This step and step S1507 are in no particular order.

51510. After the source GGSN deletes the route-optimized PDP context, it sends a delete PDP context response message to the source SGSN.

51511. The UE allocates a complete message to the radio resource on the target UTRAN/GERAN network element.

S1512. The target UTRAN/GERAN network element sends a relocation complete message to the target SGSN.

51513. The target SGSN sends a relocation complete message to the source SGSN.

51514. The source SGSN issues a release connection message to the source UTRAN/GERAN network element for releasing radio resources and connections.

51515. The network element of the source UTRAN/GERAN returns a release connection response message to the source SGSN. S1516. The source SGSN returns a relocation complete response message to the target SGSN.

51517. The target SGSN sends an update PDP context message to the GGSN of the home route optimization area, for updating the non-route optimized PDP context.

51518. The GGSN updates the information related to the SGSN in the PDP context, forwards the downlink service data of the UE to the target SGSN, and returns an update PDP context response message.

In the process shown in FIG. 15, if the source SGSN detects that the target SGSN belongs to another route optimization area, the source SGSN sends a delete PDP context request message to the source GGSN, and the source GGSN deletes the route optimized PDP context, so that cross-domain does not occur. The service data transmission in the route optimization area saves the transmission resources between the route optimization areas. Third preferred embodiment

For the evolved network, the UE is attached to the source MME, and a route optimized bearer is created on the source P-GW, including a default bearer and a specific bearer. Of course, the UE can also create a non-route optimized bearer on the P-GW of the home route optimization area at the same time. If the target MME detects that the UE moves to another route optimization area, the source MME is notified to release the route optimization bearer of the UE.

The target MME detects that the UE moves to other route optimization areas:

1) The target MME receives the request context response message sent by the MME of the other route optimization area in the TAU process, and the message carries the identifier of the other route optimization area. The target MME determines whether the MME of the other route optimization area is determined according to the identifier of the other route optimization area. In the route optimization area where the target MME is located.

2) Target The MME obtains a specific identifier (such as source TAI) in the TAU process or Relocation process. The target MME obtains the identifier of the route optimization area where the source MME corresponding to the specific identifier is located according to the mapping relationship between the specific identifier of the target MME and the identifier of the route optimization area, and determines whether the source MME is in the target route optimization area.

The process of processing the route optimization bearer in the TAU process across the route optimization area is as shown in FIG. 16, and the specific steps are as follows:

S1601. After discovering the change of the tracking area across the route optimization area, the UE sends a TAU request message to the E-UTRAN (E-UTRAN shown in FIG. 16) in the target route optimization area, where the message carries the source visited route optimization area. TAI and GUTI.

S1602. The E-UTRAN sends a TAU request message to the target MME, where the GUTL GUTI carrying the source-destination route optimization area includes the MME code, the MNC and the MCC of the MME, and the target MME may retrieve the information included in the GUTI according to the GUTI. Corresponding MME.

S1603a. The target MME sends a request context message to the source MME. S1603b. The source MME returns a message requesting a context response to the target MME, where the message carries the identifier of the route optimization area where the source MME is located, or newly carries the target TAI.

SI 604. The target MME detects that the source MME belongs to another route optimization area according to the identifier of the route optimization area where the source MME is located, or the mapping relationship between the TAI and the identifier of the route optimization area configured by the target MME according to the target TAI and the target MME. It is detected that the source MME belongs to another route optimization area, or the target MME is based on the identity of the source MME (usually an IP address) and the target. The mapping between the identifier of the MME configured by the MME and the identifier of the route optimization area obtains the identifier of the route optimization area where the source MME is located, and detects that the source MME belongs to another route optimization area.

S1605a. The target MME returns a request context acknowledgement message to the source MME to notify the source MME to release the route optimized bearer of the UE. S1605b. The source MME then initiates a setup and location update procedure for the non-route optimized bearer. This flow is the same as the flow in S1205b in Fig. 12.

S1606a. The source MME requests the source S-GW to deactivate all route optimization bearers of the UE.

S1606b. The source S-GW requests the source P-GW to deactivate all route optimization bearers of the UE.

S1606c. The source P-GW then initiates a process of deleting the route optimization bearer. The process is the same as in Figure 12.

The source P-GW in S1206c initiates the same process of deleting the route optimization bearer.

It should be noted that the source MME in step S1605b initiates the establishment of the non-route optimization bearer and the location update process is independent of the steps S1606a, SI 606b, and S1606c, and there is no order relationship.

In the process shown in FIG. 16, if the target MME detects that the source MME belongs to another route optimization area, the target MME returns a request context acknowledgement information to the source MME, and the source MME requests the source S-GW to deactivate all routes of the UE. Optimizing the bearer, the source S-GW requests the source P-GW to deactivate all the route optimized bearers of the UE, and the source P-GW subsequently initiates the process of deleting the route optimized bearer, so that the service data transmission across the route optimization area does not occur, thereby saving The transmission resources between the route optimization areas.

The process of processing the route optimization bearer in the Relocation process across the route optimization area is shown in Figure 17, and the specific steps are as follows:

51701. The source E-UTRAN and the target E-UTRAN decision trigger a relocation process across the route optimization region.

The source E-UTRAN sends a Handover Request message to the source MME, where the message carries the information of the target E-UTRAN (including the E-NodeB identifier in the E-UTRAN and the TAI of the TA where the E-NodeB is located).

The source MME sends a Relocation Request message to the target MME, where the message carries the target E-UTRAN information, the non-route optimized bearer context information of the UE, the address and TEID of the source S-GW, and the source E-UTRAN. Information (including the E-NodeB identity in E-UTRAN and the TAI of the TA where the E-NodeB is located). The target MME is based on the TA where the source E-UTRAN is located. The mapping relationship between the TAI and the TAI of the target MME and the identifier of the route optimization area is obtained, and the identifier of the source route optimization area is obtained. Alternatively, the target MME parses the identifier of the source MME (usually an IP address) from the TAI, and the target MME obtains the identifier of the source route optimization area according to the mapping relationship between the identifier of the MME configured by the target MME and the identifier of the route optimization area. The target MME detects that the source MME is not in the route optimization area where the target MME is located, and detects that the UE is a roaming UE according to the identifier of the UE (IMSI, MSISDN or other network access identifier of the UE), and detects that the UE is on the source P-GW. A route optimization bearer is established.

S1704. The target MME sends a handover request message to the target E-UTRAN, and the target E-UTRAN reserves the air interface resource for the non-route optimized bearer of the UE.

S1705. The target E-UTRAN returns a handover response message to the target MME, indicating that the air interface resource of the non-route optimized bearer reserved for the UE has been reserved.

51706. The target MME sends a relocation response message to the source MME to notify the source MME to release the route optimization bearer of the UE.

51707. The source MME sends a message for deleting the route optimized bearer to the source S-GW.

S1708. The source S-GW sends a message for deleting the route optimized bearer to the source P-GW.

51709. The source P-GW initiates a process of deleting the route optimized bearer. This process is the same as the process in which the source P-GW in S1206c in Figure 12 initiates the delete route optimization bearer.

51710. The source MME sends a handover command to the source E-UTRAN.

51711. The source E-UTRAN sends a handover command to the UE.

S1712. The UE switches to the target route optimization area.

It should be noted that, after receiving the relocation response message of the target MME, the source MME immediately initiates a process of switching the non-route optimized bearer of the UE to the target route optimization area (including notifying the UE to switch to the target route optimization area). This flow is the same as the flow in S1312 in Fig. 13.

In the process shown in FIG. 17, if the target MME detects that the source MME is not in the route optimization area where the target MME is located, the target MME sends a relocation response message to the source MME, and the source MME sends a message for deleting the route optimized bearer to the source S- GW, the source S-GW sends a message for deleting the route optimized bearer to the source P-GW, and the source P-GW initiates a process of deleting the route optimized bearer, so that the service data transmission across the route optimization area does not occur, thereby saving the route. Optimize transmission resources between zones. Fourth preferred embodiment

For the GPRS system, the UE attaches to the source SGSN and creates a route optimized PDP context on the source GGSN. Of course, the UE can also create a non-route optimized PDP context on the GGSN of the home route optimization area at the same time. If the target SGSN detects that the UE moves to the target route optimization area, the source GGSN is notified to deactivate the route optimized PDP context of the UE.

The way the target SGSN detects that the UE moves to other route optimization areas is as follows:

1) The target SGSN receives the context request response message sent by the SGSN of the other route optimization area in the RAU process, and the message carries the identifier of the route optimization area. The source SGSN determines whether the target SGSN is in the route optimization area where the source SGSN is located according to the identifier of the route optimization area where the target SGSN is located.

2) Target The SGSN obtains a specific identifier (such as the identity of the target RAI or SGSN) in the RAU process or the Relocation process. The target SGSN obtains the identifier of the source route optimization area corresponding to the specific identifier according to the mapping relationship between the specific identifier of the target SGSN and the identifier of the route optimization area, and determines whether the source SGSN is in the route optimization area where the target SGSN is located.

The process of processing the route optimization bearer in the RAU process across the route optimization area is shown in Figure 18, and the specific steps are as follows:

After the UE moves to the target route optimization area, the target UTRAN/GERAN sends a RAU request message to the target SGSN, where the message carries information such as the source RAI.

51802. The target SGSN sends an SGSN Context Request message to the source SGSN.

51803. If the UE is a roaming UE and a route optimized PDP context is created on the source GGSN, the source SGSN sends a Delete PDP Context Request message to the source GGSN.

51804. The source GGSN deletes the PDP context and returns a Delete PDP Context Response message to the source SGSN.

The source SGSN returns an SGSN Context Response message to the target SGSN, where the message carries the non-route optimized PDP context created by the UE, and the identifier of the source route optimization area, the identifier of the source SGSN, or the source RAI is newly added in the context. The target SGSN receives the SGSN context response message, and detects that the source SGSN belongs to another route optimization area according to the identifier of the source route optimization area in the message. Alternatively, the target SGSN is configured with a mapping relationship between the identifier of the SGSN and the identifier of the route optimization area, and the target SGSN obtains the identifier of the route optimization area corresponding to the identifier of the source SGSN, thereby detecting that the source SGSN belongs to another route optimization area. Or, the target SGSN is configured with the identifier of the RAI and the route optimization area. The mapping relationship between the target SGSN and the source SGSN is determined to belong to other route optimization areas. The target SGSN determines whether the UE is a roaming UE by using the identifier of the UE.

S1806. The target SGSN returns an SGSN Context Ack message to the source SGSN to inform the source SGSN to release the route optimization bearer of the UE.

S1807. The target SGSN sends an update PDP context request message to the GGSN of the home route optimization area, requesting to update the PDP context on the GGSN of the home route optimization area, and switching the GTP tunnel between the source SGSN and the GGSN to the target SGSN and the GGSN. between.

S1808. The GGSN of the home route optimization area updates the information of the SGSN in the corresponding PDP context as the information of the target SGSN, and returns an update PDP context response message to the target SGSN.

S1809. The target SGSN returns a RAU accept message to the UE through UTRAN/GERAN. The UE completes the process of switching to the target route optimization area.

In the process shown in FIG. 18, the target SGSN sends an SGSN Context Request message to the source SGSN. If the UE is a roaming UE and a route-optimized PDP context is created on the source GGSN, the source SGSN sends a Delete PDP Context Request to the source GGSN. The message, the source GGSN deletes the PDP context, so that the service data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

The process of processing the route optimization bearer in the Relocation process across the route optimization area is shown in Figure 19. The specific steps are as follows:

S1901. UE and source UTRAN/GERAN decision relocation.

S1902. The source UTRAN/GERAN sends a relocation request message to the source SGSN, where the message carries the network element identifier of the target UTRAN/GERAN (for example, the identifier of the RNC of the UTRAN), and the network element identifier of the route optimization area where the source UTRAN/GERAN is located, Relocated radio resource control information.

The source SGSN forwards the relocation request message to the target SGSN, where the message carries the MM context of the UE and the non-route optimized PDP context, and the message also carries the network element identifier of the source UTRAN/GERAN (for example, the RNC identifier of the UTRAN), the source. The network element of the route optimization area where UTRAN/GERAN is located is only i.

51904. The target SGSN sends a relocation request message to the target UTRAN/GERAN, where the message carries the network element identifier of the source UTRAN/GERAN, the network element identifier of the target UTRAN/GERAN, Radio resource control information for relocation.

51905. The target UTRAN/GERAN allocates radio resources and returns a relocation response message to the target SGSN.

51906. The target SGSN returns a relocation response message to the source SGSN to inform the source SGSN to release the route optimization bearer of the UE. If the source SGSN is unable to obtain the identifier of the route optimization area in which the target SGSN is located in step S1903, the relocation response message may carry the identifier of the route optimization area where the target SGSN is located. If the target SGSN is configured with a mapping relationship between the network element identifier of the source UTRAN/GERAN and the identifier of the route optimization area, the target SGSN may obtain the identifier of the source route optimization area corresponding to the network element identifier. The target SGSN detects that the source SGSN belongs to other route optimization areas. The target SGSN detects that the UE belongs to the roaming UE according to the identity of the UE. The source SGSN detects that the UE has a route-optimized PDP context on the source GGSN according to the address or APN of the GGSN in the PDP context of the UE. The target SGSN detects the source SGSN according to the network element identifier of the source UTRAN/GERAN.

The source SGSN sends a relocation command message to the source UTRAN/GERAN, where the message carries the radio resource information of the network element of the target UTRAN/GERAN and the network element of the source UTRAN/GERAN.

51908. The source UTRAN/GERAN instructs the terminal to reconfigure the radio resource, including notifying the terminal of the radio resource information related to the network element of the target UTRAN/GERAN.

51909. The source SGSN sends a Delete PDP Context Request message to the source GGSN to inform the source GGSN to delete the route optimized PDP context. This step and step S1907 are in no particular order.

S 1910. After the source GGSN deletes the route-optimized PDP context, it sends a delete PDP context response message to the source SGSN.

S 1911. The UE sends a radio resource configuration complete message to the target UTRAN/GERAN network element.

51912. The target UTRAN/GERAN network element sends a relocation complete message to the target SGSN.

51913. The target SGSN sends a relocation complete message to the source SGSN.

S1914. The source SGSN sends a release connection message to the source UTRAN/GERAN network element for releasing radio resources and connections.

51915. The network element of the source UTRAN/GERAN returns a release connection response message to the source SGSN.

51916. The source SGSN returns a relocation complete response message to the target SGSN.

51917. The target SGSN sends an update PDP context message to the home route optimization area. GGSN, used to update the non-route optimized PDP context. The information is forwarded to the target SGSN by the downlink service data of the UE, and returns an update PDP context response message.

In the process shown in FIG. 19, the target SGSN returns a relocation response message to the source SGSN to notify the source SGSN to release the route optimization bearer of the UE, and the source SGSN sends a delete PDP context request message to the source GGSN to notify the source GGSN to delete the route optimization. The PDP context, the source GGSN deletes the route-optimized PDP context, so that the service data transmission across the route optimization area does not occur, thereby saving transmission resources between the route optimization areas.

In addition to providing the above methods and apparatus, embodiments of the present invention also provide two regional communication networks.

A regional communication network includes: an access network and a core network; the access network provides a wireless access function, wherein the access network transmits control signaling and service data between the terminal and the core network; the core network is used for determining The terminal moves from the regional communication network where the core network itself is located to other regional communication networks or obtains the notification of deleting the route optimized bearer, and deletes the route optimized bearer created by the terminal in the regional communication network where the core network itself is located.

Another regional communication network includes: an access network and a core network; the access network provides a wireless access function, wherein the access network transmits control signaling and service data between the terminal and the core network; It is determined that the terminal moves from another regional communication network to the regional communication network where the core network itself is located, and the route optimization bearer created by the terminal in another regional communication network is deleted.

It should be noted that, in all the foregoing embodiments, if a route optimization area is a PLMN, the identifier of the route optimization area may refer to the identifier of the PLMN; if a route optimization area is an area within the PLMN, the route optimization The identifier of the area may refer to the result of combining the identifier of the PLMN with the extension item, where the extension item may be the identifier of the area.

In the prior art, after the terminal moves from the source route optimization area to the other route optimization area, the route optimization bearer created in the source route optimization area becomes a bearer across the route optimization area, and the mobile operator optimizes the cross-route. The bearer of the zone usually requires additional roaming charges, so the prior art will increase the user's cost burden. However, in all embodiments of the present invention, after the terminal moves from the source route optimization area to the other route optimization area, the route optimization bearer created in the source route optimization area is deleted, so that the terminal does not increase. Add user roaming charges.

In the prior art, after the terminal moves from the source route optimization area to the other route optimization area, the route optimization bearer created in the source route optimization area becomes a bearer across the route optimization area, which may result in between mobile operators. Billing confusion. However, in all the embodiments of the present invention, after the terminal moves from the source route optimization area to the other route optimization area, the route optimization bearer created in the source route optimization area is deleted, thereby avoiding charging between the mobile operators. confusion.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium, the program When executed, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.

Claims

Rights request

A method for processing a route optimization bearer, which is applicable to a scenario in which a terminal establishes a route optimization bearer from a source visited road, including:

Determining that the terminal moves from the source visited route optimization area to the target route optimization area, or obtains a notification of deleting a route optimized bearer;

Delete the route optimization bearer.

The method for processing a route optimization bearer according to claim 1, wherein determining that the terminal moves from the source visited route optimization area to the target route optimization area is specifically: the source visited route a network element with mobility management function of the optimization area, a network element with mobility management function of the target route optimization area, or a network element of the source visited route optimization area, which is configured with a route optimization bearer, determines the terminal from The source-destination route optimization area is moved to the target route optimization area; deleting the route optimization bearer is specifically: the network element with mobility management function of the source visited route optimization area, and the target route optimization area The network element with the mobility management function or the network element of the source visited route optimization area that has the route optimization bearer deletes the route optimization bearer.

The method for processing a route optimization bearer according to claim 2, wherein the network element having the mobility management function of the source visited route optimization area determines the route optimization area of the terminal from the source visited area. Moving to the target route optimization area specifically includes:

The network element with the mobility management function of the source-destination routing optimization area receives the handover request message sent by the network element with the mobility management function in the location update process, where the handover request message carries the target The identifier of the route optimization area where the network element of the mobility management function is located; the network element with the mobility management function of the source route optimization area according to the route optimization area where the network element with the mobility management function is located Determining whether the network element having the mobility management function of the target is in a route optimization area where the network element with mobility management function of the source visited route optimization area is located, if not, determining that the terminal is from the The source visited route optimization area moves to the target route optimization area.

The method for processing a route optimization bearer according to claim 2, wherein the network element with mobility management function of the source visited route optimization area determines the route optimization area of the terminal from the source visited area Moving to the target route optimization area specifically includes: The network element with the mobility management function of the source-destination route optimization area obtains a specific identifier in a location update process or a relocation process, and the specific identifier has a mapping relationship with the identifier of a route optimization area;

The network element with the mobility management function of the source-destination routing optimization area obtains the route of the network element with the mobility management function corresponding to the specific identifier according to the mapping relationship between the specific identifier and the identifier of the route optimization area. Determining an identifier of the area, and determining whether the network element with the mobility management function of the target is in a route optimization area where the network element with mobility management function of the source route optimization area is located, if not, determining the location The terminal moves from the source visited route optimization area to the target route optimization area.

The method for processing a route optimization bearer according to claim 1, wherein the obtaining the notification of deleting the route optimized bearer is specifically: the network element with the mobility management function of the source visited route optimization area or the The source-destination route optimization area is created by the network element with the route optimization bearer to obtain the notification of deleting the route optimization load;

Deleting the route optimization bearer is specifically: the network element with the mobility management function of the source-destination route optimization area or the network element with the route optimization bearer created by the source-destined route optimization area deleting the route optimization bearer .

The method for processing a route optimization bearer according to claim 2 or 5, wherein the deleting the route optimization bearer by the network element having the mobility management function in the source-destination route optimization area comprises: The mobility management entity MME of the source visited route optimization area requests the serving gateway S-GW of the source visited route optimization area to delete the route optimized bearer, or the service general packet radio service support of the source visited route optimization area The node SGSN requests the gateway general packet radio service support node GGSN of the source visited route optimization area to delete the route optimized packet data protocol PDP context.

The method for processing a route optimization bearer according to claim 2, wherein the network element having the mobility management function of the target route optimization area determines that the terminal moves from the source visited route optimization area to The target route optimization area specifically includes:

The network element with the mobility management function of the target route optimization area receives the request context response message sent by the network element with the mobility management function in the location update process, where the request context response message carries the source The identifier of the route optimization area where the network element of the mobility management function is located; The network element with the mobility management function of the target route optimization area determines, according to the identifier of the route optimization area where the network element having the mobility management function is located, whether the network element with the source mobility management function is in the If the route optimization area of the target routing optimization area with the mobility management function is located, if not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The network element with the mobility management function of the target route optimization area obtains a specific identifier in a location update process or a relocation process, and the specific identifier has a mapping relationship with the identifier of a route optimization area;

The network element with the mobility management function of the target route optimization area obtains the route optimization area where the source with the mobility management function is located corresponding to the specific identifier according to the mapping relationship between the specific identifier and the identifier of the route optimization area. And determining whether the network element with the mobility management function of the source is in a route optimization area where the network element with mobility management function of the target route optimization area is located, and if not, determining the terminal from the location The source visited route optimization area moves to the target route optimization area.

The method for processing a route optimization bearer according to claim 2, wherein the deleting the route optimization bearer by the network element having the mobility management function of the target route optimization area comprises: the target route optimization area The network element with the mobility management function notifies the network element with the mobility management function of the source visited route optimization area to delete the route optimization bearer, or the MME of the target route optimization area notifies the target route optimization area The S-GW deletes the part of the routing bearer that is switched to the target route optimization area.

The method for processing a route optimization bearer according to claim 5, wherein the notification that the network element that has the route optimization bearer to obtain the route optimization optimized bearer obtains the delete route optimized bearer is specifically: the source The packet data gateway P-GW of the visited route optimization area obtains the notification of deleting the route optimized bearer sent by the S-GW of the source visited route optimization area, or the GGSN of the source visited route optimization area obtains the source call The notification of the deleted route optimization bearer issued by the SGSN of the local route optimization area.

The method for processing a route optimization bearer according to claim 2 or 5, wherein the source-deleted route optimization area is configured with a route-optimized bearer, and the network element delete route optimization bearer specifically includes: the source visit The network route optimization area is created by the network element with the route optimization bearer to initiate the delete route optimization bearer.

A processing device for routing optimized bearers, which is characterized in that the terminal is configured to create a route optimized bearer from a source visited site, including:

The detecting unit is configured to determine that the terminal moves from the source visited route optimization area to the target route optimization area; after the target route optimization area is deleted, deleting the route optimized bearer created by the terminal in the source visited route optimization area.

The device for processing a route optimization bearer according to claim 12, wherein the processing device for routing optimized bearer is disposed in a network element having mobility management function in the route optimization region of the source visited location, The detection unit includes:

a message sending and receiving unit, configured to receive, in a location update process, a handover request message sent by a network element that has a mobility management function, where the handover request message carries a route optimization of a network element where the target has mobility management function Area identification;

a determining unit, configured to determine, according to the identifier of the route optimization area where the network element with the mobility management function is located, whether the network element with the mobility management function has mobility in the route optimization area of the source visited The routing optimization area in which the network element of the management function is located, if not, determines that the terminal moves from the source visited route optimization area to the target route optimization area.

a messaging unit, configured to obtain a specific identifier in a location update process or a relocation process, where the specific identifier has a mapping relationship with an identifier of a route optimization area;

a determining unit, configured to obtain, according to a mapping relationship between the specific identifier and the identifier of the route optimization area, an identifier of a route optimization area where the target network element having the mobility management function corresponding to the specific identifier is located, and determine that the target has a movement Whether the network element of the sexual management function is in the routing optimization area of the source visited The routing optimization area in which the network element having the mobility management function is located, if not, determines that the terminal moves from the source visited route optimization area to the target route optimization area.

The processing device of the route optimization bearer according to claim 12, 13 or 14, wherein the processing device of the route optimization bearer is disposed in an MME or an SGSN of the source visited route optimization area, The bearer processing unit includes: a requesting unit, configured to request the S-GW of the source visited route optimization area to delete the route optimized bearer, or request the GGSN of the source visited route optimization area to delete the route optimized PDP context.

The device for processing a route optimization bearer according to claim 12, wherein the processing device for routing optimized bearer is disposed in a network element having mobility management function in the target route optimization area, and the detecting The unit includes:

a message sending and receiving unit, configured to receive, in a location update process, a request context response message sent by a network element having a mobility management function, where the request context response message carries a network element where the source has a mobility management function The identifier of the route optimization area;

a determining unit, configured to determine, according to an identifier of a route optimization area where the network element having the mobility management function is located, whether the network element having the mobility management function has mobility management function in the target route optimization area In the route optimization area where the network element is located, if not, it is determined that the terminal moves from the source visited route optimization area to the target route optimization area.

The processing device for routing optimization bearers according to claim 12, wherein the processing device for routing optimization bearers is disposed in a network element with mobility management function in the target route optimization area, and the detecting The unit includes:

a determining unit, configured to obtain, according to a mapping relationship between the specific identifier and the identifier of the route optimization area, an identifier of a route optimization area where the source with the mobility management function corresponding to the specific identifier is located, and determine that the source has a movement Whether the network element of the sexual management function is in the route optimization area where the network element with the mobility management function of the target route optimization area is located, if not, determining that the terminal moves from the source visited route optimization area to the location The target route optimization area.

The processing device for the route optimization bearer according to claim 12, 16 or 17, wherein the processing device for routing optimized bearer is set in the MME of the target route optimization area, The bearer processing unit includes: a notification unit, configured to notify the MME of the source visited route optimization area to delete the route optimized bearer, or notify the S-GW of the target route optimization area to delete the switch to the target route The part of the routing that optimizes the zone.

The processing device of the route optimization bearer according to claim 12, wherein the processing device for the route optimization bearer is disposed in a network element in which the route optimization bearer is created in the route optimization region of the source visited place, The bearer processing unit includes: an initiating unit, configured to initiate a delete route optimization bearer.

20. A processing device for routing optimized bearers, comprising:

a message sending and receiving unit, configured to: when the terminal moves from the source visited route optimization area to the target route optimization area, obtain a notification for deleting the route optimized bearer;

And a bearer processing unit, configured to delete, after the message sending and receiving unit obtains the notification of deleting the route optimized bearer, the route optimized bearer created by the terminal in the source visited route optimization area.

The processing device for routing optimization bearers according to claim 20, wherein the processing device for routing optimization bearers is disposed in a network element having mobility management function in the source-advance route optimization region, The notification of deleting the route optimization bearer obtained by the message sending and receiving unit is sent by the network element with the mobility management function of the target route optimization area.

The processing device of the route optimization bearer according to claim 20 or 21, wherein the processing device of the route optimization bearer is disposed in an MME or an SGSN of the source-destination routing optimization area, and the bearer processing The unit includes: a requesting unit, configured to request the S-GW of the source visited route optimization area to delete the route optimized bearer, or request the GGSN of the source visited route optimization area to delete the route optimized PDP context.

The processing device of the route optimization bearer according to claim 20, wherein the processing device of the route optimization bearer is disposed in a P-GW of the source visited route optimization area, and the message receiving and receiving unit obtains The notification of the deleted route optimization bearer is sent by the S-GW of the source route optimization area; or

The processing device for the route optimization bearer is set in the GGSN of the source-destination route optimization area, and the notification of the deleted route optimization bearer obtained by the message receiving and dispatching unit is sent by the SGSN of the source visited route optimization area.

The processing device for routing optimization bearers according to claim 20 or 23, wherein the processing device for routing optimization bearers is configured to create a route in the route optimization region of the source visited area. In the network element of the optimized bearer, the bearer processing unit includes: an initiating unit, configured to initiate a delete route optimization bearer.