[go: up one dir, main page]

WO2010031317A1 - 路由优化承载的处理方法和装置 - Google Patents

路由优化承载的处理方法和装置 Download PDF

Info

Publication number
WO2010031317A1
WO2010031317A1 PCT/CN2009/073880 CN2009073880W WO2010031317A1 WO 2010031317 A1 WO2010031317 A1 WO 2010031317A1 CN 2009073880 W CN2009073880 W CN 2009073880W WO 2010031317 A1 WO2010031317 A1 WO 2010031317A1
Authority
WO
WIPO (PCT)
Prior art keywords
route optimization
source
area
bearer
optimization area
Prior art date
Application number
PCT/CN2009/073880
Other languages
English (en)
French (fr)
Inventor
胡伟华
张进
吴问付
朱志明
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2010031317A1 publication Critical patent/WO2010031317A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • H04W8/082Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W80/00Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • the present invention relates to wireless communication technologies, and in particular, to a method and apparatus for processing a route optimization bearer. Background technique
  • a Public Land Mobile Network 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).
  • 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.
  • WWW web browsing
  • VoIP voice over IP
  • IM instant messaging
  • video services and data download services.
  • Different PLMNs generally have different charging standards and provide different access services.
  • 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.
  • a route optimization area an area including at least one radio access network and at least one core network is collectively referred to as a route optimization area.
  • 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.
  • the terminal 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.
  • the 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
  • a visited route optimization area 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.
  • the backbone transmission network is usually connected. Under normal circumstances, the backbone transmission network is expensive and expensive to use.
  • the terminal 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:
  • 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.
  • the bandwidth of the transmission resources between the occupied route optimization areas will be particularly large.
  • 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.
  • 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.
  • FIG. 1 is a flowchart of a method for processing a route optimized bearer according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of an architecture of an evolved network
  • FIG. 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. 11 is a schematic structural diagram of another network element with mobility management function according to an embodiment of the present invention.
  • FIG. 12 is a tracking area update in a cross-route optimization area according to a first preferred embodiment of the present invention.
  • FIG. 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
  • FIG. 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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) ).
  • S-GW Serving Gateway
  • GGSN Gateway General Packet Radio Service Support 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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 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
  • 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
  • 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
  • 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
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • CN Core Network
  • 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
  • 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.
  • 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.
  • FIG. 5 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.
  • 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.
  • 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.
  • 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.
  • FIG. 6 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.
  • 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.
  • 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.
  • 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.
  • 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
  • the 802 is configured to delete the route optimization bearer according to the notification obtained by the obtaining unit 801.
  • 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.
  • 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.
  • 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.
  • 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. .
  • the route optimization area may refer to a route optimization area
  • 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 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.
  • 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.
  • FIG. 11 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.
  • 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.
  • 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.
  • the foregoing terminal may refer to a user equipment (UE,
  • 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.
  • a route optimization bearer on the P-GW hereinafter referred to as the source P-GW
  • the UE can also create a non-route optimized bearer on the P-GW of the home route optimization area at the same time.
  • the MME of the source visited route optimization area 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:
  • 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.
  • 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.
  • a specific identifier for example, a target tracking area identifier TAI
  • TAI target tracking area identifier
  • the UE 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).
  • E-UTRAN E-UTRAN in FIG. 12
  • GUI Globally Unique Temporary Identity
  • 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.
  • MNC Mobile Network Code
  • MCC Mobile Country Code
  • 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.
  • 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.
  • 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.
  • IMSI International Mobile Subscriber Identity
  • MSISDN Mobile International ISDN Number
  • 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.
  • TEID Tunnel End Indentifier
  • 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.
  • 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.
  • 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.
  • steps S1205a, S1205b, and S1206a, S1206b, and S1206c are independent of each other, and there is no order relationship.
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • 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.
  • the target MME sends a relocation response message to the source MME.
  • 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.
  • 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.
  • the source E-UTRAN sends a handover command to the UE.
  • the UE switches to the target route optimization area.
  • the source MME 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.
  • the target radio access network element 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.
  • the target MME 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.
  • 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.
  • 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
  • GTP tunnels are managed through PDP contexts
  • creating route-optimized GTP tunnels can also be described as creating route-optimized PDP contexts.
  • 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:
  • 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.
  • 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 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.
  • the source SGSN 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.
  • the source SGSN sends a Delete PDP Context Request message to the source GGSN.
  • 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.
  • 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.
  • 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.
  • the target SGSN returns a RAU accept message to the UE.
  • 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 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 target UTRAN/GERAN for example, the RNC identifier of the UTRAN
  • 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.
  • MM mobility management
  • 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.
  • 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.
  • 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.
  • 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.
  • the source GGSN After the source GGSN deletes the route-optimized PDP context, it sends a delete PDP context response message to the source SGSN.
  • the UE allocates a complete message to the radio resource on the target UTRAN/GERAN network element.
  • the target UTRAN/GERAN network element sends a relocation complete message to the target SGSN.
  • the target SGSN sends a relocation complete message to the source SGSN.
  • the source SGSN issues a release connection message to the source UTRAN/GERAN network element for releasing radio resources and connections.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a route optimized bearer is created on the source P-GW, including a default bearer and a specific bearer.
  • 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:
  • 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.
  • 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 UE 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the source MME requests the source S-GW to deactivate all route optimization bearers of the UE.
  • the source S-GW requests the source P-GW to deactivate all route optimization bearers of the UE.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the source MME sends a handover command to the source E-UTRAN.
  • the source E-UTRAN sends a handover command to the UE.
  • the UE switches to the target route optimization area.
  • the source MME 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.
  • 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
  • the UE attaches to the source SGSN and creates a route optimized PDP context on the source GGSN.
  • 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:
  • 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.
  • 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 target UTRAN/GERAN 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.
  • the target SGSN sends an SGSN Context Request message to the source SGSN.
  • the source SGSN sends a Delete PDP Context Request message to the source GGSN.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 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 network element identifier of the target UTRAN/GERAN for example, the identifier of the RNC of the UTRAN
  • 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.
  • 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.
  • the target UTRAN/GERAN allocates radio resources and returns a relocation response message to the target SGSN.
  • 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.
  • 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.
  • 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.
  • the source GGSN After the source GGSN deletes the route-optimized PDP context, it sends a delete PDP context response message to the source SGSN.
  • the UE sends a radio resource configuration complete message to the target UTRAN/GERAN network element.
  • the target UTRAN/GERAN network element sends a relocation complete message to the target SGSN.
  • the target SGSN sends a relocation complete message to the source SGSN.
  • the source SGSN sends a release connection message to the source UTRAN/GERAN network element for releasing radio resources and connections.
  • the network element of the source UTRAN/GERAN returns a release connection response message to the source SGSN.
  • the source SGSN returns a relocation complete response message to the target SGSN.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the route optimization bearer created in the source route optimization area is deleted, so that the terminal does not increase. Add user roaming charges.
  • 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.
  • the route optimization bearer created in the source route optimization area is deleted, thereby avoiding charging between the mobile operators. confusion.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

路由优化承载的处理方法和装置
本申请要求于 2008 年 9 月 22 日提交中国专利局、 申请号为 200810211456.7、 发明名称为"路由优化承载的处理方法、 装置"的中国专利申 请的优先权, 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术, 尤其涉及路由优化承载的处理方法和装置。 背景技术
目前, 一个公共陆地移动网络( PLMN, Public Land Mobile Network )通 常包括至少一个无线接入网络和至少一个核心网。 PLMN之间由骨干传输网连 接。 核心网中的一个网元提供接入外部分组数据网络 ( PDN , Packet Data Network )的服务。 PDN可以是互联网( Internet )、虚拟私有网络( VPN, Virtual Private Network )、 IP多媒体子系统( IMS, IP Multimedia Subsystem )等形式 的分组数据网络。 PDN用于提供网页浏览( WWW )、互联网电话(VoIP, Voice over IP )、 即时通讯(IM )、 视频服务、 数据下载服务等 IP数据业务。 不同的 PLMN之间一般会有不同的计费标准, 还会提供不同的接入服务。 如果一个 PLMN的范围过大, 那么 PLMN又可以分为多个不同的区域, 每个区域都包 括至少一个无线接入网络和至少一个核心网。这些区域之间一般也会有不同的 计费标准, 也会提供不同的接入服务。 这些区域之间也由骨干传输网连接。 为 下文描述方便,这里将包括至少一个无线接入网络和至少一个核心网的区域统 称为路由优化区。 例如, 一个 PLMN可以称为一个路由优化区, PLMN包括 的上述一个区域也可以称为一个路由优化区, 也就是说, 一个 PLMN可以包 括至少一个路由优化区。一个路由优化区可以是一个国家的移动网络所覆盖的 区域, 也可以是一个国家的移动网络中一个包括无线接入网和核心网的区域。
在现有技术中, 当一个终端在其归属的路由优化区(一般情况下, 归属地 是指使用终端的用户与运营商签约并开通移动服务的地点) 中需要使用 PDN 提供的数据业务时,这个终端会在其归属的路由优化区中建立用于传输业务数 据的承载, 这样, 这个终端就可以通过这条承载与 PDN之间传输业务数据。 当这个终端移动到另一个路由优化区(一般称为拜访地路由优化区)时, 如果 这个终端需要与 PDN之间传输业务数据, 在通常情况下, 终端会建立经过拜 访地路由优化区的无线接入网、拜访地路由优化区的核心网和归属地路由优化 区的核心网的用于传输业务数据的承载,并通过归属地路由优化区的核心网接 入 PDN。 这种承载被称为非路由优化的承载。 在路由优化区之间, 通常使用 骨干传输网相连。 通常情况下, 骨干传输网的造价较高, 使用费用昂贵。 当终 端需要使用从拜访地路由优化区的核心网接入的 PDN所提供的数据业务时, 这个终端可以只在拜访地路由优化区中建立用于传输业务数据的路由优化承 载(即, 从拜访地路由优化区的核心网接入 PDN ) , 这样, 这个终端就可以 通过路由优化承载与从拜访地路由优化区的核心网接入的 PDN之间传输业务 数据,而无需再使用原来在其归属的路由优化区中建立的承载来与其归属的路 由优化区传输业务数据, 节省了连接各路由优化区的骨干传输网的网络资源, 并降低了使用跨路由优化区的漫游业务的资费。
本发明的发明人在实现本发明的过程中发现: 在现有技术中, 当终端从拜 访地路由优化区移动到另一个路由优化区时,如果这个终端已经在拜访地路由 优化区建立了路由优化承载,则这个终端会将原来的拜访地路由优化区建立的 路由优化承载切换到上述另一个路由优化区,并且该承载通过上述另一个路由 优化区的无线接入网、 核心网连接到上述拜访地路由优化区 , 并接入 PDN传 样的终端的数量特别多时, 占用的路由优化区之间的传输资源带宽就会特别 大。
发明内容
本发明实施例提供路由优化承载的处理方法和装置,用以当在一个拜访地 路由优化区内建立了路由优化承载的终端从拜访地路由优化区移动到另一个 路由优化区、 且终端需要与 PDN之间传输业务数据时, 节省路由优化区之间 的传输资源。
一种路由优化承载的处理方法,适用于终端从源拜访地路由优化区移动到
Figure imgf000004_0001
建有路由优化承 载的场景, 包括: 确定所述终端从所述源拜访地路由优化区移动到所述目标路 由优化区, 或者获得删除路由优化承载的通知; 删除所述路由优化承载。
一种路由优化承载的处理装置,适用于终端从源拜访地路由优化区移动到 载的场景, 包括: 检测单元, 用于确定终端从源拜访地路由优化区移动到目标 路由优化区; 承载处理单元, 用于在所述检测单元确定终端从源拜访地路由优 化区移动到目标路由优化区后,删除所述终端在所述源拜访地路由优化区创建 的路由优化承载。
一种路由优化承载的处理装置, 包括: 消息收发单元, 用于当终端从源拜 访地路由优化区移动到目标路由优化区时, 获得删除路由优化承载的通知; 承 载处理单元, 用于在所述消息收发单元获得删除路由优化承载的通知后,删除 所述终端在所述源拜访地路由优化区创建的路由优化承载。
在本发明的实施例中,如果确定在源拜访地路由优化区内建立了路由优化 承载的终端从所述源拜访地路由优化区移动到目标路由优化区后,则可以删除 路由优化承载, 这样就不会发生跨路由优化区的业务数据传输,从而节省了路 由优化区之间的传输资源。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施 例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地, 下面描述 中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲, 在不付 出创造性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例的一种路由优化承载的处理方法的流程图;
图 2为演进网络的架构示意图;
图 3为通用移动陆地业务 ( UMTS , Universal Mobile Terrestrial Service ) I 通用分组无线业务( GPRS, General Packet Radio Service )的网络架构示意图; 图 4为本发明实施例的一种具有移动性管理功能的网元的结构示意图; 图 5为本发明实施例的另一种具有移动性管理功能的网元的结构示意图; 图 6为本发明实施例的另一种路由优化承载的处理方法的流程图; 图 7为本发明实施例的一种具有创建路由承载功能的网元的结构示意图; 图 8 为本发明实施例的另一种具有创建路由承载功能的网元的结构示意 图;
图 9为本发明实施例的另一种路由优化承载的处理方法的流程图; 图 10 为本发明实施例的另一种具有移动性管理功能的网元的结构示意 图;
图 11 为本发明实施例的另一种具有移动性管理功能的网元的结构示意 图;
图 12 为本发明第一个优选实施例的在跨路由优化区的跟踪区域更新
( TAU, Trace Area Update ) 流程中处理路由优化承载的流程图;
图 13为本发明第一个优选实施例的在跨路由优化区的重定位( Relocation ) 流程中处理路由优化承载的流程图;
图 14为本发明第二个优选实施例的在跨路由优化区的 TAU流程中处理路 由优化承载的流程图;
图 15为本发明第二个优选实施例的在跨路由优化区的 Relocation流程中 处理路由优化承载的流程图;
图 16为本发明第三个优选实施例的在跨路由优化区的 TAU流程中处理路 由优化承载的流程图;
图 17为本发明第三个优选实施例的在跨路由优化区的 Relocation流程中 处理路由优化承载的流程图;
图 18为本发明第四个优选实施例的在跨路由优化区的 TAU流程中处理路 由优化承载的流程图;
图 19为本发明第四个优选实施例的在跨路由优化区的 Relocation流程中 处理路由优化承载的流程图。
具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清 楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而不是 全部的实施例。基于本发明中的实施例, 本领域普通技术人员在没有作出创造 性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
首先对本发明实施例的一种路由优化承载的处理方法及装置进行说明。 一种路由优化承载的处理方法,适用于终端从源拜访地路由优化区移动到
Figure imgf000006_0001
建有路由优化承 载的场景, 包括: 确定所述终端从所述源拜访地路由优化区移动到所述目标路 由优化区, 或者获得删除路由优化承载的通知; 删除所述路由优化承载。 在本发明实施例中, 源拜访地路由优化区的具有移动性管理功能的网元、 目标路由优化区的具有移动性管理功能的网元或源拜访地路由优化区的创建 有路由优化承载的网元可以确定终端从源拜访地路由优化区移动到目标路由 优化区; 源拜访地路由优化区的具有移动性管理功能的网元、 目标路由优化区 的具有移动性管理功能的网元或源拜访地路由优化区的创建有路由优化承载 的网元可以删除路由优化承载。 如是源 PLMN的移动性管理网元(MME, Mobility Management Entity )或服 务通用分组无线业务支持节点( SGSN, Serving GPRS Supporting Node ) , 目标 路由优化区的具有移动性管理功能的网元例如是目标 PLMN 的 MME 或 SGSN, 源拜访地路由优化区的创建有路由优化承载的网元例如是源 PLMN的 服务网关 (S-GW , Serving Gateway ) 或网关通用分组无线业务支持节点 ( GGSN, Gateway GPRS Supporting Node )。
源拜访地路由优化区的具有移动性管理功能的网元确定终端从源拜访地 路由优化区移动到目标路由优化区具体可以包括:源拜访地路由优化区的具有 移动性管理功能的网元在位置更新流程中收到目标具有移动性管理功能的网 元发出的切换请求消息,切换请求消息中携带目标具有移动性管理功能的网元 所在的路由优化区的标识;源拜访地路由优化区的具有移动性管理功能的网元 根据目标具有移动性管理功能的网元所在的路由优化区的标识判断目标具有 移动性管理功能的网元是否在源拜访地路由优化区的具有移动性管理功能的 网元所在的路由优化区内,如果不是, 则确定终端从源拜访地路由优化区移动 到目标路由优化区。这里及下文的目标具有移动性管理功能的网元位于终端移 动到的目标路由优化区内, 目标具有移动性管理功能的网元例如是目标 MME 或目标 SGSN。
源拜访地路由优化区的具有移动性管理功能的网元确定终端从源拜访地 路由优化区移动到目标路由优化区具体可以包括:源拜访地路由优化区的具有 移动性管理功能的网元在位置更新流程或者重定位流程中获取特定标识 ,特定 标识与一个路由优化区的标识之间具有映射关系;源拜访地路由优化区的具有 移动性管理功能的网元根据特定标识与路由优化区的标识之间的映射关系,获 得与特定标识对应的目标具有移动性管理功能的网元所在的路由优化区的标 识,并判断目标具有移动性管理功能的网元是否在源拜访地路由优化区的具有 移动性管理功能的网元所在的路由优化区内,如果不是, 则确定终端从源拜访 地路由优化区移动到目标路由优化区。
获得删除路由优化承载的通知具体可以为:源拜访地路由优化区的具有移 动性管理功能的网元或源拜访地路由优化区的创建有路由优化承载的网元获 得删除路由优化承载的通知; 删除路由优化承载具体为: 源拜访地路由优化区 的具有移动性管理功能的网元或源拜访地路由优化区的创建有路由优化承载 的网元删除路由优化承载。
源拜访地路由优化区的具有移动性管理功能的网元删除路由优化承载具 体可以包括: 源拜访地路由优化区的 MME请求源拜访地路由优化区的 S-GW 删除路由优化承载,或者源拜访地路由优化区的 SGSN请求源拜访地路由优化 区的 GGSN删除路由优化的分组数据协议上下文( PDP , Packet Data Protocol Context ) 。
目标路由优化区的具有移动性管理功能的网元确定终端从源拜访地路由 优化区移动到目标路由优化区具体可以包括: 目标路由优化区的具有移动性管 理功能的网元在位置更新流程中收到源具有移动性管理功能的网元发出的请 求上下文响应消息,请求上下文响应消息中携带源具有移动性管理功能的网元 所在的路由优化区的标识; 目标路由优化区的具有移动性管理功能的网元根据 源具有移动性管理功能的网元所在的路由优化区的标识判断源具有移动性管 理功能的网元是否在目标路由优化区的具有移动性管理功能的网元所在的路 由优化区内,如果不是, 则确定终端从源拜访地路由优化区移动到目标路由优 化区。
目标路由优化区的具有移动性管理功能的网元确定终端从源拜访地路由 优化区移动到目标路由优化区具体可以包括: 目标路由优化区的具有移动性管 理功能的网元在位置更新流程或者重定位流程中获取特定标识,特定标识与一 个路由优化区的标识之间具有映射关系; 目标路由优化区的具有移动性管理功 能的网元根据特定标识与路由优化区的标识之间的映射关系 ,获得与特定标识 对应的源具有移动性管理功能的网元所在的路由优化区的标识,并判断源具有 移动性管理功能的网元是否在目标路由优化区的具有移动性管理功能的网元 所在的路由优化区内,如果不是, 则确定终端从源拜访地路由优化区移动到目 标路由优化区。
目标路由优化区的具有移动性管理功能的网元删除路由优化承载具体可 以包括: 目标路由优化区的具有移动性管理功能的网元通知源拜访地路由优化 区的具有移动性管理功能的网元删除路由优化承载, 或者目标路由优化区的 MME通知目标路由优化区的 S-GW删除切换到目标路由优化区的那部分路由 承载。
源拜访地路由优化区的创建有路由优化承载的网元获得删除路由优化承 载的通知具体可以为: 源拜访地路由优化区的分组数据网络网关 ( P-GW, Packet Data Network Gateway )获得源拜访地路由优化区的 S-GW发出的删除 路由优化承载的通知, 或者源拜访地路由优化区的 GGSN获得源拜访地路由 优化区的 SGSN发出的删除路由优化承载的通知。
源拜访地路由优化区的创建有路由优化承载的网元删除路由优化承载具 体可以包括:源拜访地路由优化区的创建有路由优化承载的网元发起删除路由 优化承载。
在上述方法中,如果确定在源拜访地路由优化区内建立了路由优化承载的 终端从源拜访地路由优化区移动到目标路由优化区后,则可以删除路由优化承 载, 这样就不会发生跨路由优化区的业务数据传输,从而节省了路由优化区之 间的传输资源。
除上述路由优化承载的处理方法外,本发明实施例还提供了一种路由优化 承载的处理装置,适用于终端从源拜访地路由优化区移动到目标路由优化区且 终端在源拜访地路由优化区内创建有路由优化承载的场景, 包括: 检测单元, 用于确定终端从源拜访地路由优化区移动到目标路由优化区; 承载处理单元, 除终端在源拜访地路由优化区创建的路由优化承载。
路由优化承载的处理装置可以设置在源拜访地路由优化区的具有移动性 管理功能的网元中, 检测单元可以包括: 消息收发单元, 用于在位置更新流程 中收到目标具有移动性管理功能的网元发出的切换请求消息,切换请求消息中 携带目标具有移动性管理功能的网元所在的路由优化区的标识; 判断单元, 用 于根据目标具有移动性管理功能的网元所在的路由优化区的标识判断目标具 有移动性管理功能的网元是否在源拜访地路由优化区的具有移动性管理功能 的网元所在的路由优化区内,如果不是, 则确定终端从源拜访地路由优化区移 动到目标路由优化区。
路由优化承载的处理装置可以设置在源拜访地路由优化区的具有移动性 管理功能的网元中, 检测单元可以包括: 消息收发单元, 用于在位置更新流程 或者重定位流程中获取特定标识 ,特定标识与一个路由优化区的标识之间具有 映射关系;判断单元,用于根据特定标识与路由优化区的标识之间的映射关系 , 获得与特定标识对应的目标具有移动性管理功能的网元所在的路由优化区的 标识,并判断目标具有移动性管理功能的网元是否在源拜访地路由优化区的具 有移动性管理功能的网元所在的路由优化区内,如果不是, 则确定终端从源拜 访地路由优化区移动到目标路由优化区。
路由优化承载的处理装置可以设置在源拜访地路由优化区的 MME 或
SGSN中, 承载处理单元可以包括: 请求单元, 用于请求源拜访地路由优化区 的 S-GW删除路由优化承载, 或者请求源拜访地路由优化区的 GGSN删除路 由优化的 PDP上下文。
路由优化承载的处理装置可以设置在目标路由优化区的具有移动性管理 功能的网元中, 检测单元可以包括: 消息收发单元, 用于在位置更新流程中收 到源具有移动性管理功能的网元发出的请求上下文响应消息,请求上下文响应 消息中携带源具有移动性管理功能的网元所在的路由优化区的标识; 判断单 元,用于根据源具有移动性管理功能的网元所在的路由优化区的标识判断源具 有移动性管理功能的网元是否在目标路由优化区的具有移动性管理功能的网 元所在的路由优化区内, 如果不是, 则确定终端从源拜访地路由优化区移动到 目标路由优化区。
路由优化承载的处理装置可以设置在目标路由优化区的具有移动性管理 功能的网元中, 检测单元可以包括: 消息收发单元, 用于在位置更新流程或者 重定位流程中获取特定标识,特定标识与一个路由优化区的标识之间具有映射 关系; 判断单元, 用于根据特定标识与路由优化区的标识之间的映射关系, 获 得与特定标识对应的源具有移动性管理功能的网元所在的路由优化区的标识, 并判断源具有移动性管理功能的网元是否在目标路由优化区的具有移动性管 理功能的网元所在的路由优化区内,如果不是, 则确定终端从源拜访地路由优 化区移动到目标路由优化区。
路由优化承载的处理装置可以设置在目标路由优化区的 MME中,承载处 理单元可以包括: 通知单元, 用于通知源拜访地路由优化区的 MME删除路由 优化承载,或者通知目标路由优化区的 S-GW删除切换到目标路由优化区的那 部分路由承载。
路由优化承载的处理装置可以设置在源拜访地路由优化区的创建有路由 优化承载的网元中, 承载处理单元可以包括: 发起单元, 用于发起删除路由优 化承载。
在上述装置中,如果检测单元确定在源拜访地路由优化区内建立了路由优 化承载的终端从源拜访地路由优化区移动到目标路由优化区后,则承载处理单 元可以删除路由优化承载, 这样就不会发生跨路由优化区的业务数据传输,从 而节省了路由优化区之间的传输资源。
本发明实施例还提供了另一种路由优化承载的处理装置, 包括: 消息收发 单元, 用于当终端从源拜访地路由优化区移动到目标路由优化区时, 获得删除 路由优化承载的通知; 承载处理单元, 用于在消息收发单元获得删除路由优化 承载的通知后, 删除终端在源拜访地路由优化区创建的路由优化承载。
路由优化承载的处理装置可以设置在源拜访地路由优化区的具有移动性 管理功能的网元中,消息收发单元获得的删除路由优化承载的通知可以是目标 路由优化区的具有移动性管理功能的网元发出的。
路由优化承载的处理装置可以设置在源拜访地路由优化区的 MME 或 SGSN中, 承载处理单元可以包括: 请求单元, 用于请求源拜访地路由优化区 的 S-GW删除路由优化承载, 或者请求源拜访地路由优化区的 GGSN删除路 由优化的 PDP上下文。
路由优化承载的处理装置可以设置在源拜访地路由优化区的 P-GW中,消 息收发单元获得的删除路由优化承载的通知可以是源拜访地路由优化区的 S-GW发出的; 路由优化承载的处理装置可以设置在源拜访地路由优化区的 GGSN中,消息收发单元获得的删除路由优化承载的通知可以是源拜访地路由 优化区的 SGSN发出的。
路由优化承载的处理装置可以设置在源拜访地路由优化区的创建有路由 优化承载的网元中, 承载处理单元可以包括: 发起单元, 用于发起删除路由优 化承载。
在上述装置中,如果消息收发单元收到删除路由优化承载的通知, 则承载 处理单元可以删除路由优化承载,这样就不会发生跨路由优化区的业务数据传 输, 从而节省了路由优化区之间的传输资源。
下面结合附图,分别对本发明实施例的路由优化承载的处理方法及装置进 行详细说明。
如图 1所示, 一种路由优化承载的处理方法, 适用于终端从源拜访地路由 化承载的场景, 包括:
步骤 S101 : 源拜访地路由优化区的具有移动性管理功能的网元确定终端 从源拜访地路由优化区移动到目标路由优化区,或者源拜访地路由优化区的具 有移动性管理功能的网元确定重定位的目标具有移动性管理功能的网元不在 源拜访地路由优化区中,或者源拜访地路由优化区的具有移动性管理功能的网 步骤 S102: 源拜访地路由优化区的具有移动性管理功能的网元通知源拜 访地路由优化区的与终端之间创建有路由优化承载的网元删除路由优化承载。
图 1所示的方法可以应用于演进网络。 演进网络的架构如图 2所示, 包括 演进的通用陆地无线接入网 (E-UTRAN, Evolved Universal Terrestrial Radio Access Network ) , 用于实现所有与演进网络无线有关的功能; MME, 负责控 制面的移动性管理, 包括用户上下文和移动状态管理, 分配用户临时身份标识 ( TMSI, Temporary Mobile Subscriber Identity )等; S-GW是 3GPP接入网络 间的用户面锚点,终止 E-TURAN的接口; P-GW是 3GPP接入网络和非 3GPP 接入网络之间的用户面锚点, 与 PDN之间具有接口; 归属用户服务器(HSS, Home Subscriber Server )用于存储用户签约信息。 MME、 S-GW, P-GW和 HSS 通常作为核心网的网元。如果图 1所示的方法应用于演进网络, 则源拜访地路 由优化区的具有移动性管理功能的网元就是源拜访地路由优化区的 MME, 源 拜访地路由优化区的与终端之间创建有路由优化承载的网元就是源拜访地路 由优化区的 P-GW,发出删除路由优化承载的通知的目标路由优化区的网元就 是目标路由优化区的 MME。
源拜访地路由优化区的具有移动性管理功能的网元通知源拜访地路由优 化区的与终端之间创建有路由优化承载的网元删除路由优化承载具体可以包 括:源拜访地路由优化区的 MME可以请求源拜访地路由优化区的 S-GW删除 路由优化承载,再由源拜访地路由优化区的 S-GW请求源拜访地路由优化区的 P-GW删除路由优化承载。
图 1所示的方法可以应用于 UMTS系统或 GPRS系统。 UMTS/ GPRS的 网络架构如图 3所示,包括:通用陆地无线接入网( UTRAN, Universal Terrestrial Radio Access Network ), 通常包括多个无线网络控制器( RNC, Radio Network Controller )和无线传输节点( NodeB ), 用于实现 UMTS系统中的无线接入功 能; GSM/EDGE无线接入网 ( GERAN, GSM/EDGE Radio Access Network ), 通常包括多个基站控制器(BSC, Base Station Controller )和基站 (BS, Base Station ) , 用于实现 GPRS 系统中的无线接入功能; SGSN , 用于实现 GPRS/UMTS系统中的路由转发、 移动性管理、 会话管理以及用户信息存储等 功能; GGSN用于连接外部 PDN; 归属位置寄存器 (HLR, Home Location Register ), 用于存储用户关于网络业务的签约信息。 SGSN、 GGSN和 HLR通 常作为核心网(CN, Core Network )网元。 3GPP TS 23.060标准中描述了 GPRS 系统的架构和流程。
如果图 1所示的方法应用于 UMTS/GPRS系统,则源拜访地路由优化区的 具有移动性管理功能的网元就是源拜访地路由优化区的 SGSN, 源拜访地路由 优化区的与终端之间创建有路由优化承载的网元就是源拜访地路由优化区的 GGSN, 发出删除路由优化承载的通知的目标路由优化区的网元就是目标路由 优化区的 SGSN。
源拜访地路由优化区的具有移动性管理功能的网元通知源拜访地路由优 化区的与终端之间创建有路由优化承载的网元删除路由优化承载具体可以包 括: 源拜访地路由优化区的 SGSN请求源拜访地路由优化区的 GGSN删除路 由优化的 PDP上下文。
在图 1所示的方法中,如果源拜访地路由优化区的具有移动性管理功能的 网元确定终端从源拜访地路由优化区移动到目标路由优化区,或者源拜访地路 由优化区的具有移动性管理功能的网元确定重定位的目标具有移动性管理功 能的网元不在源拜访地路由优化区中,或者源拜访地路由优化区的具有移动性 则源拜访地路由优化区的具有移动性管理功能的网元通知源拜访地路由优化 区的与终端之间创建有路由优化承载的网元删除路由优化承载,这样就不会发 生跨路由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
图 1所示的方法可以由多种形式的网元来实现。
其中的一种具有移动性管理功能的网元如图 4所示,适用于终端从源拜访 地路由优化区移动到目标路由优化区、终端在源拜访地路由优化区内创建有路 由优化承载且具有移动性管理功能的网元设置在源拜访地路由优化区内的场 景, 包括: 检测单元 401 , 用于确定终端从源拜访地路由优化区移动到目标路 由优化区,或者确定重定位的目标具有移动性管理功能的网元不在源拜访地路 由优化区中; 通知单元 402 , 用于在检测单元 401确定终端从源拜访地路由优 化区移动到目标路由优化区后,或者在检测单元确定重定位的目标具有移动性 管理功能的网元不在源拜访地路由优化区中后,通知源拜访地路由优化区的与 终端之间创建有路由优化承载的网元删除路由优化承载。 到目标路由优化区,或者源拜访地路由优化区的具有移动性管理功能的网元确 定重定位的目标具有移动性管理功能的网元不在源拜访地路由优化区中,或者 源拜访地路由优化区的具有移动性管理功能的网元获得目标路由优化区的网 元发出的删除路由优化承载的通知 ,则通知单元通知源拜访地路由优化区的与 终端之间创建有路由优化承载的网元删除路由优化承载,这样就不会发生跨路 由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
另一种具有移动性管理功能的网元如图 5所示,适用于终端从源拜访地路 由优化区移动到目标路由优化区、终端在源拜访地路由优化区内创建有路由优 化承载且具有移动性管理功能的网元设置在源拜访地路由优化区内的场景,包 的通知; 通知单元 502 , 用于根据获得单元 501获得的通知, 通知源拜访地路 由优化区的与终端之间创建有路由优化承载的网元删除路由优化承载。
在图 5所示的网元中,如果获得单元获得目标路由优化区的网元发出的删 除路由优化承载的通知,则通知单元通知源拜访地路由优化区的与终端之间创 建有路由优化承载的网元删除路由优化承载,这样就不会发生跨路由优化区的 业务数据传输, 从而节省了路由优化区之间的传输资源。
需要说明的是,图 4和图 5所示的具有移动性管理功能的网元在演进网络 中可以是指 MME, 在 UMTS/GPRS系统中可以是指 SGSN。
另一种路由优化承载的处理方法如图 6所示,适用于终端从源拜访地路由 化承载的场景, 包括:
步骤 S601 : 源拜访地路由优化区的与终端之间创建有路由优化承载的网 元确定终端从源拜访地路由优化区移动到目标路由优化区,或者源拜访地路由 优化区的与终端之间创建有路由优化承载的网元获得源拜访地路由优化区的 其他网元发出的删除路由优化承载的通知;
步骤 S602: 源拜访地路由优化区的与终端之间创建有路由优化承载的网 元删除路由优化承载。
如果图 6所示的方法应用于演进网络,则源拜访地路由优化区的与终端之 间创建有路由优化承载的网元可以是指源拜访地路由优化区的 P-GW,发出删 除路由优化承载的通知的源拜访地路由优化区的其他网元可以是指源拜访地 路由优化区的 S-GW。
如果图 6所示的方法应用于 UMTS系统或 GPRS系统, 则源拜访地路由 优化区的与终端之间创建有路由优化承载的网元可以是指源拜访地路由优化 区的 GGSN,发出删除路由优化承载的通知的源拜访地路由优化区的其他网元 可以是指源拜访地路由优化区的 SGSN。
在图 6所示的方法中,如果源拜访地路由优化区的与终端之间创建有路由 优化承载的网元确定终端从源拜访地路由优化区移动到目标路由优化区,或者 源拜访地路由优化区的与终端之间创建有路由优化承载的网元获得源拜访地 路由优化区的其他网元发出的删除路由优化承载的通知,则源拜访地路由优化 区的与终端之间创建有路由优化承载的网元删除路由优化承载,这样就不会发 生跨路由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
图 6所示的方法可以由多种形式的网元来实现。
其中的一种具有创建路由承载功能的网元如图 7所示,适用于终端从源拜 访地路由优化区移动到目标路由优化区、终端在源拜访地路由优化区内与具有 创建路由承载功能的网元之间创建有路由优化承载、具有创建路由承载功能的 网元设置在源拜访地路由优化区内的场景, 包括: 检测单元 701 , 用于确定终 端从源拜访地路由优化区移动到目标路由优化区; 承载处理单元 702, 用于在 确定单元 701确定终端从源拜访地路由优化区移动到目标路由优化区后,删除 路由优化承载。 到目标路由优化区, 则承载处理单元删除路由优化承载, 这样就不会发生跨路 由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
另一种具有创建路由承载功能的网元如图 8所示,适用于终端从源拜访地 路由优化区移动到目标路由优化区、终端在源拜访地路由优化区内与具有创建 路由承载功能的网元之间创建有路由优化承载、具有创建路由承载功能的网元 设置在源拜访地路由优化区内的场景, 包括: 获得单元 801 , 用于获得源拜访
802, 用于根据获得单元 801获得的通知, 删除路由优化承载。
在图 8所示的网元中,如果获得单元获得源拜访地路由优化区的其他网元 发出的删除路由优化承载的通知, 则承载处理单元删除路由优化承载, 这样就 不会发生跨路由优化区的业务数据传输,从而节省了路由优化区之间的传输资 源。
需要说明的是,图 7和图 8所示的具有创建路由承载功能的网元在演进网 络中可以是指 P-GW, 在 UMTS/GPRS系统中可以是指 GGSN。
除图 1和图 6所示的方法外,本发明实施例还提供一种路由优化承载的处 理方法,这种方法适用于终端从源拜访地路由优化区移动到目标路由优化区且 终端在源拜访地路由优化区内创建有路由优化承载的场景,如图 9所示,包括: 步骤 S901 : 目标路由优化区的具有移动性管理功能的网元确定终端从源 拜访地路由优化区移动到目标路由优化区;
步骤 S902: 目标路由优化区的具有移动性管理功能的网元通知源拜访地 路由优化区的具有移动性管理功能的网元删除路由优化承载,或者发起删除路 由优化承载中已经切换到目标路由优化区的那部分路由承载。
如果图 9所示的方法应用于演进网络,则具有移动性管理功能的网元可以 是指 MME。
目标路由优化区的具有移动性管理功能的网元发起删除路由优化承载中 已经切换到目标路由优化区的那部分路由承载具体可以包括: 目标路由优化区 的 MME请求目标路由优化区的 S-GW删除切换到目标路由优化区的那部分路 由承载;目标路由优化区的 S-GW删除切换到目标路由优化区的那部分路由承 载, 并通知源拜访地路由优化区的 P-GW删除路由优化承载。
如果图 9所示的方法应用于 UMTS系统或 GPRS系统, 则路由优化区可 以是指路由优化区, 具有移动性管理功能的网元可以是指 SGSN。
目标路由优化区的具有移动性管理功能的网元发起删除路由优化承载中 已经切换到目标路由优化区的那部分路由承载具体可以包括: 目标路由优化区 的 SGSN删除已经切换到目标路由优化区的 GTP隧道, 并通知源拜访地路由 优化区的 GGSN删除路由优化的 PDP上下文。
在图 9所示的方法中,如果目标路由优化区的具有移动性管理功能的网元 确定终端从源拜访地路由优化区移动到目标路由优化区,则目标路由优化区的 具有移动性管理功能的网元通知源拜访地路由优化区的具有移动性管理功能 的网元删除路由优化承载,或者发起删除路由优化承载中已经切换到目标路由 优化区的那部分路由承载, 这样就不会发生跨路由优化区的业务数据传输,从 而节省了路由优化区之间的传输资源。
图 9所示的方法可以由多种形式的网元来实现。
其中的一种具有移动性管理功能的网元如图 10所示, 适用于终端从源拜 访地路由优化区移动到目标路由优化区、终端在源拜访地路由优化区内创建有 路由优化承载且具有移动性管理功能的网元设置在目标路由优化区内的场景, 包括: 检测单元 1001 , 用于确定终端从源拜访地路由优化区移动到目标路由 优化区; 通知单元 1002, 用于在检测单元 1001确定终端从源拜访地路由优化 区移动到目标路由优化区后,通知源拜访地路由优化区的具有移动性管理功能 的网元删除路由优化承载。
在图 10所示的网元中,如果检测单元 1001确定终端从源拜访地路由优化 区移动到目标路由优化区, 则通知单元 1002通知源拜访地路由优化区的具有 移动性管理功能的网元删除路由优化承载,这样就不会发生跨路由优化区的业 务数据传输, 从而节省了路由优化区之间的传输资源。
另一种具有移动性管理功能的网元如图 11所示, 适用于终端从源拜访地 路由优化区移动到目标路由优化区、终端在源拜访地路由优化区内创建有路由 优化承载且具有移动性管理功能的网元设置在目标路由优化区内的场景, 包 括: 检测单元 1101 , 用于确定终端从源拜访地路由优化区移动到目标路由优 化区; 承载处理单元 1102, 用于在检测单元 1101确定终端从源拜访地路由优 化区移动到目标路由优化区后,发起删除路由优化承载中已经切换到目标路由 优化区的那部分路由承载。
在图 11所示的网元中,如果检测单元 1101确定终端从源拜访地路由优化 区移动到目标路由优化区, 则承载处理单元 1102发起删除路由优化承载中已 经切换到目标路由优化区的那部分路由承载,这样就不会发生跨路由优化区的 业务数据传输, 从而节省了路由优化区之间的传输资源。
需要说明的是,图 10和图 11所示的具有移动性管理功能的网元在演进网 络中可以是指 MME, 在 UMTS/GPRS系统中可以是指 SGSN。
还需要说明的是,上述所有方法实施例和网元实施例如果应用或设置于演 进网络、 UMTS系统或 GPRS系统中, 则上述终端可以是指用户设备 ( UE,
User Equipment )。 为使本领域技术人员更加清楚的理解本发明实施例,下面再介绍几个优选 实施例。
第一个优选实施例
对于演进网络, UE在一个拜访地路由优化区的 MME(下文称为源 MME ) 上附着, 并在源拜访地路由优化区的 P-GW (下文称为源 P-GW )上创建了路 由优化承载, 包括缺省承载和特定承载。 当然, 这个 UE也可以同时在归属地 路由优化区的 P-GW 上创建非路由优化承载。 如果源拜访地路由优化区的 MME (下文称为源 MME )检测到 UE移动到其他路由优化区(下文称为目标 路由优化区 ), 则通知源拜访地路由优化区的 S-GW (下文称为源 S-GW )释放 UE的路由优化承载。
源 MME检测到 UE移动到其他路由优化区的方式如下:
1) 源 MME在 TAU流程中收到其他路由优化区的 MME (下文称为目标 MME )发出的切换请求消息, 消息中携带目标 MME所在的路由优化区的标 识 , 源 MME根据目标 MME所在的路由优化区的标识判断目标 MME是否在 源 MME所在的路由优化区内。
2) 源 MME在 TAU流程或者 Relocation流程中获取特定标识 (例如目标 跟踪区域标识 TAI ) , 源 MME才艮据特定标识与路由优化区的标识之间的映射 关系, 获得与特定标识对应的目标 MME所在的路由优化区的标识, 并判断目 标 MME是否在源 MME所在的路由优化区内。
在跨路由优化区的 TAU流程中处理路由优化承载的流程如图 12所示,具 体步骤如下:
51201. UE在发现跨路由优化区的跟踪区域变更后, 向目标路由优化区内 的 E-UTRAN (图 12中的 E-UTRAN )发送 TAU请求消息, 消息中携带源拜 访地路由优化区的 TAI和全球唯一临时标识( GUTI , Globally Unique Temporary Identity )。
51202. E-UTRAN向目标路由优化区内的 MME (图 12中的目标路由优化 区)发送 TAU请求消息, 消息中携带源拜访地路由优化区的 GUTI。 GUTI包 含有 MME编码、 MME的移动网络码(MNC, Mobile Network Code )和移动 国家码( MCC, Mobile Country Code ), 目标路由优化区可以根据 GUTI检索 到与 GUTI包含的这些信息对应的 MME。
51203.目标 MME根据源拜访地路由优化区的 GUTI, 确定出 GUTI包含 的信息对应的是源 MME, 并发送请求上下文消息给源 MME, 消息中新增携 带目标 MME所在的路由优化区的标识, 或者新增携带目标 TAI。 S 1204.源 MME根据目标 MME所在的路由优化区的标识检测出目标 MME 是属于其他的路由优化区, 或者, 源 MME根据目标 TAI以及源 MME配置的 TAI与路由优化区的标识的映射关系, 检测出目标 MME是属于其他的路由优 化区 , 或者, 源 MME根据目标 MME的标识(通常是 IP地址 )以及源 MME 配置的 MME的标识与路由优化区的标识的映射关系 ,得到目标 MME所在的 路由优化区的标识 , 并检测出目标 MME是属于其他的路由优化区。
同时, 目标 MME根据 UE 的标识(UE 的国际移动用户标识(IMSI, International Mobile Subscriber Identity )、 移动台国际 ISDN号码( MSISDN, Mobile Station International ISDN Number )或者其他网络接入标识, 由这些标 识就可以得到 UE的归属路由优化区信息 ), 检测出 UE为漫游 UE。
S1205a.源 MME向目标 MME返回请求上下文响应的消息, 消息中携带 UE的 IMSI、 UE的鉴权五元组(Authentication Quintets ), 非路由优化承载上 下文、 S-GW信令面地址、 隧道端点标识(TEID, Tunnel End Indentifier )等 信息。
S1205b.目标 MME向目标 S-GW发送请求建立非路由优化承载消息。 目 标 S-GW建立非路由优化承载上下文,并通知位于归属路由优化区的 P-GW建 立非路由优化承载的上下文。 MME在位置更新消息中通知 HSS, 更新 HSS 中保存的 UE所在的 MME的信息。 另夕卜, MME通知无线接入网络网元为 UE 的非路由优化承载保留相应的无线资源,以及 S-GW为非路由优化承载分配的 TEID等信息。
S1206a.源 MME向源 S-GW请求去激活 UE的所有路由优化承载。 S1206b. 源 S-GW请求源 P-GW去激活 UE的所有路由优化承载。 S1206c.源 P-GW随 后发起删除路由优化承载的流程。 源 P-GW发送删除承载消息给源 S-GW。 源 S-GW 删除用户的路由优化承载上下文信息, 并且发送删除承载消息给源 MME。 源 MME删除用户的路由优化承载上下文信息, 并通知无线接入网络 网元删除路由优化承载占用的无线资源。
需要说明的是, 步骤 S1205a、 S1205b和 S1206a、 S1206b 、 S1206c 是相 互独立的, 不存在顺序关系。
在图 12所示的流程中, 如果源 MME检测出目标 MME是属于其他的路 由优化区, 则源 MME向源 S-GW请求去激活 UE的所有路由优化承载, 源 S-GW请求源 P-GW去激活 UE的所有路由优化承载, 这样就不会发生跨路由 优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
在跨路由优化区的 Relocation流程中处理路由优化承载的流程如图 13所 示, 具体步骤如下:
51301.源拜访地路由优化区的 E-UTRAN (下文称为源 E-UTRAN )和目标 路由优化区的 E-UTRAN (下文称为目标 E-UTRAN ) 决策触发跨路由优化区 的重定位流程。
51302.源 E-UTRAN向源 MME发送切换请求( Handover Request ) 消息, 消息中携带有目标 E-UTRAN 的信息 (包含目标 E-UTRAN 中的演进基站
( E-NodeB )标识和 E-NodeB所在的 TA的 TAI )。 源 MME根据切换请求消息 中的 E-NodeB所在的 TAI以及源 MME配置的 TAI与路由优化区的标识的映 射关系, 得到目标路由优化区的信息, 或者, 源 MME从 TAI中解析得到目标 MME的标识(通常是 IP地址), 或者, 源 MME根据源 MME配置的 MME 标识与路由优化区的标识的映射关系, 得到目标路由优化区的信息。
51303.如果源 MME检测出目标 MME不在源 MME所在的路由优化区, 并且源 MME根据 UE的标识发现 UE为漫游 UE,并且 UE在源 P-GW上建立 了路由优化承载,则源 MME向目标 MME发送重定位请求( Relocation Request ) 消息, 消息中携带目标 E-UTRAN的信息、 UE的非路由优化承载上下文信息、 源 S-GW的地址和 TEID。
51304.目标 MME向目标 E-UTRAN发送切换请求消息 , 目标 E-UTRAN 为 UE的非路由优化承载保留空口资源。
51305.目标 E-UTRAN返回切换响应消息, 表明为 UE保留的非路由优化 承载的空口资源已经保留完成。
S1306.目标 MME发送重定位响应消息给源 MME。
51307.源 MME发送删除路由优化承载的消息给源 S-GW。
51308.源 S-GW发送删除路由优化承载的消息给源 P-GW。
51309.源 P-GW发起删除路由优化承载的流程。该流程和图 12中的 S1206c 中描述源 P-GW发起删除路由优化承载的过程相同。 51310.源 MME向源 E-UTRAN发送切换命令。
51311.源 E-UTRAN向 UE发送切换命令。
51312. UE切换到目标路由优化区。
需要说明的是, 源 MME收到目标 MME的重定位响应消息后, 立即发起 将 UE的非路由优化承载切换到目标路由优化区的流程 (包括通知 UE切换到 目标路由优化区)。 源 MME命令 UE切换到目标路由优化区的无线接入网络。 目标无线接入网络网元收到 UE的切换确认消息后, 通知目标 MME UE已经 切换到目标路由优化区。 目标 MME向目标 S-GW发送请求建立非路由优化承 载消息。 目标 S-GW建立非路由优化承载上下文,并通知位于归属路由优化区 的 P-GW建立非路由优化承载的上下文。目标 MME在 S-GW建立完成路由优 化承载上下文后, 通知无线接入网络网元 S-GW 为非路由优化承载分配的 TEID等信息。 目标 MME在位置更新消息中通知 HSS, 更新 HSS中保存的 UE所在的 MME的信息。
在图 13所示的流程中, 如果源 MME检测出目标 MME不在源 MME所 在的路由优化区, 则源 MME发送删除路由优化承载的消息给源 S-GW, 源 S-GW发送删除路由优化承载的消息给源 P-GW, 这样就不会发生跨路由优化 区的业务数据传输, 从而节省了路由优化区之间的传输资源。 第二个优选实施例
对于 GPRS系统, UE在源拜访地路由优化区的 SGSN (下文称为源 SGSN ) 上附着, 并在源拜访地路由优化区的 GGSN (下文称为源 GGSN )上创建了路 由优化的 GPRS 隧道协议(GTP, GPRS Tunnel Protocol )隧道, 由于 GTP隧道 是通过 PDP上下文来进行管理的, 所以, 创建路由优化的 GTP隧道也可以等同 描述为创建路由优化的 PDP上下文。 当然, UE也可以同时在归属地路由优化 区的 GGSN上创建非路由优化的 PDP上下文。如果源 SGSN检测到 UE移动到目 标路由优化区, 则通知源路由优化区内的 GGSN去激活 UE的路由优化的 PDP 上下文。
源 SGSN检测到 UE移动到其他路由优化区的方式如下:
1) 源 SGSN在 RAU流程中收到其他路由优化区的目标 SGSN发出的 RAU 请求消息,消息中携带目标 SGSN所在的路由优化区的标识,源 SGSN根据目 标 SGSN所在的路由优化区的标识判断目标 SGSN是否在源 SGSN所在的路 由优化区。
2) 源 SGSN在 RAU流程或者 Relocation流程中获取特定标识(例如目标 路由区域标识 RAI或者 SGSN的标识 ),源 SGSN根据源 SGSN配置的特定标 识与路由优化区的标识之间的映射关系 ,获得与特定标识对应的目标 SGSN所 在的路由优化区的标识,并判断目标 SGSN是否在源 SGSN所在的路由优化区。
在跨路由优化区的 RAU流程中处理路由优化承载的流程如图 14所示,具 体步骤如下:
S 1401.UE移动到目标路由优化区后, 通过目标 UTRAN/GERAN向目标
SGSN发送 RAU请求消息, 消息中携带源 RAI等信息。
51402.目标 SGSN向源 SGSN发送 SGSN上下文请求消息,消息中新增携 带目标路由优化区的标识、 目标 SGSN的标识或者目标 RAI的信息。源 SGSN 收到 SGSN上下文请求消息后,根据消息中的目标路由优化区的标识,检测到 目标 SGSN属于其他路由优化区, 或者, 源 SGSN根据目标 SGSN的标识以 及源 SGSN配置的 SGSN的标识与路由优化区的标识的映射关系,获得与目标 SGSN的标识相应的路由优化区的标识,从而检测到目标 SGSN属于其他路由 优化区, 或者, 源 SGSN根据目标 RAI以及源 SGSN配置的 RAI与路由优化 区的标识的映射关系, 将目标 RAI转换为路由优化区的标识, 从而检测到目 标 SGSN属于其他路由优化区。 源 SGSN还通过 UE的标识来判断 UE是否为 漫游 UE。
51403.如果 UE是漫游 UE,并且 UE在源 GGSN上创建了路由优化的 PDP 上下文, 则源 SGSN向源 GGSN发送删除 PDP上下文请求消息。
51404.源 GGSN删除 PDP上下文, 并向源 SGSN返回删除 PDP上下文响 应消息。
51405.源 SGSN向目标 SGSN返回 SGSN上下文响应消息, 消息中携带 UE创建的非路由优化的 PDP上下文的信息。
51406.目标 SGSN向归属地路由优化区的 GGSN发送更新 PDP上下文请 求消息,以请求更新 GGSN的 PDP上下文,将源 SGSN和 GGSN之间的 GTP 隧道切换到目标 SGSN和 GGSN之间。
51407.归属地路由优化区的 GGSN将 PDP上下文的信息中的 SGSN的信 息更新为目标 SGSN的信息,并向目标 SGSN返回更新 PDP上下文响应消息。 换到目标路由优化区的过程。
51408.目标 SGSN向 UE返回 RAU接受消息。
在图 14所示的流程中, 如果源 SGSN检测到目标 SGSN属于其他路由优 化区, 则源 SGSN向源 GGSN发送删除 PDP上下文请求消息, 源 GGSN删除 PDP上下文,这样就不会发生跨路由优化区的业务数据传输,从而节省了路由 优化区之间的传输资源。
在跨路由优化区的 Relocation流程中处理路由优化承载的流程如图 15所 示, 具体步骤如下:
51501. UE和源 UTRAN/GERAN决策重定位。
51502.源 UTRAN/GERAN向源 SGSN发送重定位请求消息, 消息中携带 目标 UTRAN/GERAN 的网元标识 (例如 UTRAN 的 RNC 标识)、 源
UTRAN/GERAN所在路由优化区的网元标识、 用于重定位的无线资源控制信 息。
51503.如果源 SGSN配置了 UTRAN/GERAN的网元标识和路由优化区的 标识的映射关系, 则源 SGSN可以获得与目标 UTRAN/GERAN的网元标识对 目标 SGSN属于其他路由优化区。 源 SGSN根据 UE的标识检测到 UE属于漫 游 UE。 源 SGSN根据 UE的 PDP上下文中的 GGSN的地址或者接入点名称 ( APN, Access Point Name )检测到 UE在源 GGSN上创建有路由优化的 PDP 上下文。 源 SGSN根据目标 UTRAN/GERAN的网元标识,检测到目标 SGSN。 源 SGSN将重定位请求消息转发给目标 SGSN, 重定位消息中携带 UE的移动 性管理(MM , Mobile Management )上下文和非路由优化的 PDP上下文。
51504.目标 SGSN向目标 UTRAN/GERAN发送重定位请求消息, 消息中 携带源 UTRAN/GERAN的网元标识、 目标 UTRAN/GERAN的网元标识、 用 于重定位的无线资源控制信息。 51505.目标 UTRAN/GERAN分配无线资源, 并向目标 SGSN返回重定位 响应消息。
51506.目标 SGSN向源 SGSN返回重定位响应消息。如果在步骤 S1503中 , 源 SGSN无法获得目标路由优化区的标识,则在重定位响应消息中可以携带目 标路由仂 区的标识。
51507.源 SGSN向源 UTRAN/GERAN发送重定位命令消息, 消息中携带 目标 UTRAN/GERAN网元传递给源 UTRAN/GERAN网元的无线资源信息。
51508.源 UTRAN/GERAN指示终端重新配置无线资源, 包括通知终端与 目标 UTRAN/GERAN的网元相关的无线资源信息。
S1509.源 SGSN发送删除 PDP上下文请求消息给源 GGSN, 用于删除路 由优化的 PDP上下文。 本步骤和步骤 S1507不分先后顺序。
51510.源 GGSN删除路由优化的 PDP上下文后, 发送删除 PDP上下文响 应消息给源 SGSN。
51511. UE向目标 UTRAN/GERAN网元上 无线资源配置完成消息。
S1512.目标 UTRAN/GERAN网元向目标 SGSN发送重定位完成消息。
51513.目标 SGSN向源 SGSN发送重定位完成消息。
51514.源 SGSN发出释放连接消息给源 UTRAN/GERAN的网元, 用于释 放无线资源和连接。
51515.源 UTRAN/GERAN的网元返回释放连接响应消息给源 SGSN。 S1516.源 SGSN向目标 SGSN返回重定位完成响应消息。
51517.目标 SGSN 发送更新 PDP 上下文消息给归属地路由优化区的 GGSN, 用于更新非路由优化的 PDP上下文
51518. GGSN更新 PDP上下文中的与 SGSN相关的信息,将 UE的下行业 务数据转发给目标 SGSN, 并返回更新 PDP上下文响应消息。
在图 15所示的流程中, 如果源 SGSN检测到目标 SGSN属于其他路由优 化区, 则源 SGSN发送删除 PDP上下文请求消息给源 GGSN, 源 GGSN删除 路由优化的 PDP上下文, 这样就不会发生跨路由优化区的业务数据传输, 从 而节省了路由优化区之间的传输资源。 第三个优选实施例
对于演进网络, UE在源 MME上附着, 并在源 P-GW上创建了路由优化 承载, 包括缺省承载和特定承载。 当然, UE也可以同时在归属地路由优化区 的 P-GW上创建非路由优化承载。如果目标 MME检测到 UE移动到其他路由 优化区, 则通知源 MME释放 UE的路由优化承载。
目标 MME检测到 UE移动到其他路由优化区的方法有:
1) 目标 MME在 TAU流程中收到其他路由优化区的 MME发出的请求上 下文响应消息, 消息中携带其他路由优化区的标识, 目标 MME根据其他路由 优化区的标识判断其他路由优化区的 MME是否在目标 MME所在的路由优化 区。
2) 目标 MME在 TAU流程或者 Relocation流程中获取特定标识(例如源 TAI )。 目标 MME根据目标 MME配置的特定标识与路由优化区的标识之间的 映射关系, 获得与特定标识对应的源 MME所在的路由优化区的标识, 并判断 源 MME是否在目标路由优化区。
在跨路由优化区的 TAU过程中处理路由优化承载的流程如图 16所示,具 体步骤如下:
S1601.UE在发现跨路由优化区的跟踪区域变更后, 向目标路由优化区内 的 E-UTRAN (图 16中所示的 E-UTRAN )发送 TAU请求消息, 消息中携带 源拜访地路由优化区的 TAI和 GUTI。
S 1602.E-UTRAN向目标 MME发送 TAU请求消息 , 消息中携带源拜访地 路由优化区的 GUTL GUTI包含有 MME编码、 MME的 MNC和 MCC, 目标 MME可以根据 GUTI检索到与 GUTI包含的这些信息对应的 MME。
S1603a.目标 MME向源 MME发送请求上下文消息。 S1603b.源 MME向 目标 MME返回请求上下文响应的消息, 消息中携带源 MME所在的路由优化 区的标识, 或者新增携带目标 TAI。
SI 604.目标 MME根据源 MME所在的路由优化区的标识检测出源 MME 是属于其他的路由优化区, 或者, 目标 MME根据目标 TAI以及目标 MME配 置的 TAI与路由优化区的标识的映射关系,检测出源 MME是属于其他的路由 优化区, 或者, 目标 MME根据源 MME的标识(通常是 IP地址) 以及目标 MME配置的 MME的标识与路由优化区的标识的映射关系 , 得到源 MME所 在的路由优化区的标识 , 并检测出源 MME是属于其他的路由优化区。
S 1605a.目标 MME向源 MME返回请求上下文确认信息 , 以通知源 MME 释放 UE的路由优化承载。 S1605b.源 MME随后发起非路由优化承载的建立和 位置更新流程。 该流程与图 12中的 S1205b中的流程相同。
S1606a.源 MME向源 S-GW请求去激活 UE的所有路由优化承载。
S1606b.源 S-GW请求源 P-GW去激活 UE的所有路由优化承载。
S1606c.源 P-GW随后发起删除路由优化承载的流程。该流程与图 12中的
S1206c中的源 P-GW发起删除路由优化承载流程相同。
需要指出的是, 步骤 S1605b中的源 MME发起非路由优化承载的建立和 位置更新流程与步骤 S1606a、 SI 606b 、 S1606c之间是相互独立的, 不存在 顺序关系。
在图 16所示的流程中, 如果目标 MME检测出源 MME是属于其他的路 由优化区, 则目标 MME向源 MME返回请求上下文确认信息 , 源 MME向源 S-GW请求去激活 UE的所有路由优化承载, 源 S-GW请求源 P-GW去激活 UE的所有路由优化承载, 源 P-GW随后发起删除路由优化承载的流程, 这样 就不会发生跨路由优化区的业务数据传输,从而节省了路由优化区之间的传输 资源。
在跨路由优化区的 Relocation流程中处理路由优化承载的流程如图 17所 示, 具体步骤如下:
51701.源 E-UTRAN和目标 E-UTRAN决策触发跨路由优化区的重定位流 程。
51702.源 E-UTRAN向源 MME发送切换请求( Handover Request ) 消息, 消息中携带有目标 E-UTRAN的信息 (包含 E-UTRAN中的 E-NodeB标识和 E-NodeB所在的 TA的 TAI )。
51703.源 MME向目标 MME发送重定位请求( Relocation Request )消息, 消息中携带有目标 E-UTRAN信息、 UE 的非路由优化承载上下文信息、 源 S-GW的地址和 TEID以及源 E-UTRAN的信息(包含 E-UTRAN中的 E-NodeB 标识和 E-NodeB所在的 TA的 TAI )。 目标 MME根据源 E-UTRAN所在的 TA 的 TAI和目标 MME配置的 TAI与路由优化区的标识之间的映射关系 ,得到源 路由优化区的标识。 或者, 目标 MME从 TAI中解析得到源 MME的标识(通 常是 IP地址), 目标 MME根据目标 MME配置的 MME的标识与路由优化区 的标识之间的映射关系得到源路由优化区的标识。 目标 MME检测到源 MME 不在目标 MME所在的路由优化区 ,并且根据 UE的标识( UE的 IMSI、 MSISDN 或者其他网络接入标识 )检测到 UE为漫游 UE, 并且检测到 UE在源 P-GW 上建立了路由优化承载。
S1704.目标 MME向目标 E-UTRAN发送切换请求消息 , 目标 E-UTRAN 为 UE的非路由优化承载保留空口资源。
S1705.目标 E-UTRAN向目标 MME返回切换响应消息, 表明为 UE保留 的非路由优化承载的空口资源已经保留完成。
51706.目标 MME发送重定位响应消息给源 MME, 以通知源 MME释放 UE的路由优化承载。
51707.源 MME发送删除路由优化承载的消息给源 S-GW。
S1708.源 S-GW发送删除路由优化承载的消息给源 P-GW。
51709.源 P-GW发起删除路由优化的承载的流程。 该流程和图 12 中的 S1206c中的源 P-GW发起删除路由优化承载的流程相同。
51710.源 MME向源 E-UTRAN发送切换命令。
51711.源 E-UTRAN向 UE发送切换命令。
S1712.UE切换到目标路由优化区。
需要说明的是, 源 MME收到目标 MME的重定位响应消息后, 立即发起 将 UE的非路由优化承载切换到目标路由优化区的流程 (包括通知 UE切换到 目标路由优化区)。 该流程和图 13中的 S1312中的流程相同。
在图 17所示的流程中, 如果目标 MME检测到源 MME不在目标 MME 所在的路由优化区, 则目标 MME发送重定位响应消息给源 MME, 源 MME 发送删除路由优化承载的消息给源 S-GW, 源 S-GW发送删除路由优化承载的 消息给源 P-GW, 源 P-GW发起删除路由优化的承载的流程, 这样就不会发生 跨路由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。 第四个优选实施例
对于 GPRS系统, UE在源 SGSN上附着, 并在源 GGSN上创建了路由优 化的 PDP上下文。 当然, UE也可以同时在归属地路由优化区的 GGSN上创 建非路由优化的 PDP上下文。 如果目标 SGSN检测到 UE移动到目标路由优 化区, 则通知源 GGSN去激活 UE的路由优化的 PDP上下文。
目标 SGSN检测到 UE移动到其他路由优化区的方式如下:
1 ) 目标 SGSN在 RAU流程中收到其他路由优化区的 SGSN发出的上下文 请求响应消息, 消息中携带有路由优化区的标识。 源 SGSN根据目标 SGSN 所在的路由优化区的标识判断目标 SGSN是否在源 SGSN所在的路由优化区。
2) 目标 SGSN在 RAU流程或者 Relocation流程中获取特定标识(例如目 标 RAI或者 SGSN的标识)。 目标 SGSN根据目标 SGSN配置的特定标识与路 由优化区的标识之间的映射关系, 获得与特定标识对应的源路由优化区的标 识, 并判断源 SGSN是否在目标 SGSN所在的路由优化区。
在跨路由优化区的 RAU流程中处理路由优化承载的流程如图 18所示,具 体步骤如下:
51801. UE移动到目标路由优化区后, 通过目标 UTRAN/GERAN向目标 SGSN发送 RAU请求消息, 消息中携带源 RAI等信息。
51802.目标 SGSN向源 SGSN发送 SGSN上下文请求消息。
51803.如果 UE是漫游 UE, 并且在源 GGSN上创建了路由优化的 PDP上 下文, 则源 SGSN向源 GGSN发送删除 PDP上下文请求消息。
51804.源 GGSN删除 PDP上下文, 并向源 SGSN返回删除 PDP上下文响 应消息。
51805.源 SGSN向目标 SGSN返回 SGSN上下文响应消息, 消息中携带 UE创建的非路由优化的 PDP上下文,上下文中新增携带源路由优化区的标识、 源 SGSN的标识或者源 RAI。 目标 SGSN收到 SGSN上下文响应消息, 根据 消息中的源路由优化区的标识, 检测到源 SGSN属于其他路由优化区。 或者, 目标 SGSN配置有 SGSN的标识与路由优化区的标识之间的映射关系, 目标 SGSN获得与源 SGSN的标识相应的路由优化区的标识, 从而检测到源 SGSN 属于其他路由优化区。 或者, 目标 SGSN配置有 RAI与路由优化区的标识之 间的映射关系,目标 SGSN将源 RAI映射为路由优化区的标识,检测到源 SGSN 属于其他路由优化区。 目标 SGSN通过 UE的标识判断 UE是否为漫游 UE。
S1806.目标 SGSN向源 SGSN返回 SGSN上下文确认消息,以通知源 SGSN 释放 UE的路由优化承载。
S1807.目标 SGSN向归属地路由优化区的 GGSN发送更新 PDP上下文请 求消息, 请求更新归属地路由优化区的 GGSN上的 PDP上下文, 将源 SGSN 和 GGSN之间的 GTP隧道切换到目标 SGSN和 GGSN之间。
S1808.归属地路由优化区的 GGSN更新相应的 PDP上下文中的 SGSN的 信息为目标 SGSN的信息, 并向目标 SGSN返回更新 PDP上下文响应消息。
S1809.目标 SGSN通过 UTRAN/GERAN向 UE返回 RAU接受消息。 UE 完成切换到目标路由优化区的过程。
在图 18所示的流程中, 目标 SGSN向源 SGSN发送 SGSN上下文请求消 息, 如果 UE是漫游 UE, 并且在源 GGSN上创建了路由优化的 PDP上下文, 则源 SGSN向源 GGSN发送删除 PDP上下文请求消息, 源 GGSN删除 PDP 上下文, 这样就不会发生跨路由优化区的业务数据传输,从而节省了路由优化 区之间的传输资源。
在跨路由优化区的 Relocation流程中处理路由优化承载的流程如图 19所 示, 具体步骤如下:
S1901.UE和源 UTRAN/GERAN决策重定位。
S1902.源 UTRAN/GERAN向源 SGSN发送重定位请求消息, 消息中携带 目标 UTRAN/GERAN 的网元标识 (例如 UTRAN 的 RNC 的标识)、 源 UTRAN/GERAN所在路由优化区的网元标识、 用于重定位的无线资源控制信 息。
51903.源 SGSN将重定位请求消息转发给目标 SGSN, 消息中携带 UE的 MM上下文和非路由优化的 PDP上下文,消息中还携带源 UTRAN/GERAN的 网元标识(例如 UTRAN的 RNC标识)、 源 UTRAN/GERAN所在路由优化区 的网元标 i只。
51904.目标 SGSN向目标 UTRAN/GERAN发出重定位请求消息, 消息中 携带源 UTRAN/GERAN的网元标识、 目标 UTRAN/GERAN的网元标识、 用 于重定位的无线资源控制信息。
51905.目标 UTRAN/GERAN分配无线资源, 并向目标 SGSN返回重定位 响应消息。
51906.目标 SGSN向源 SGSN返回重定位响应消息,以通知源 SGSN释放 UE的路由优化承载。 如果在步骤 S1903中, 源 SGSN无法获得目标 SGSN所 在的路由优化区的标识,则在重定位响应消息中可以携带目标 SGSN所在的路 由优化区的标识。 如果目标 SGSN配置了源 UTRAN/GERAN的网元标识与路 由优化区的标识之间的映射关系,则目标 SGSN可以获得与网元标识对应的源 路由优化区的标识。 目标 SGSN检测到源 SGSN属于其他路由优化区。 目标 SGSN根据 UE的标识检测到 UE属于漫游 UE。 源 SGSN根据 UE的 PDP上 下文中的 GGSN的地址或者 APN,检测到 UE在源 GGSN上有路由优化的 PDP 上下文。 目标 SGSN根据源 UTRAN/GERAN的网元标识, 检测到源 SGSN。
51907.源 SGSN向源 UTRAN/GERAN发送重定位命令消息, 消息中携带 目标 UTRAN/GERAN的网元传递给源 UTRAN/GERAN的网元的无线资源信 息。
51908.源 UTRAN/GERAN指示终端重新配置无线资源, 包括通知终端与 目标 UTRAN/GERAN的网元相关的无线资源信息。
51909.源 SGSN发送删除 PDP 上下文请求消息给源 GGSN, 以通知源 GGSN删除路由优化的 PDP上下文。 本步骤和步骤 S1907不分先后顺序。
S 1910.源 GGSN删除路由优化的 PDP上下文后, 发送删除 PDP上下文响 应消息给源 SGSN。
S 1911.UE向目标 UTRAN/GERAN的网元上艮无线资源配置完成消息。
51912.目标 UTRAN/GERAN的网元向目标 SGSN发送重定位完成消息。
51913.目标 SGSN向源 SGSN发送重定位完成消息。
S1914.源 SGSN发出释放连接消息给源 UTRAN/GERAN的网元, 用于释 放无线资源和连接。
51915.源 UTRAN/GERAN的网元返回释放连接响应消息给源 SGSN。
51916.源 SGSN向目标 SGSN返回重定位完成响应消息。
51917.目标 SGSN 发送更新 PDP 上下文消息给归属地路由优化区的 GGSN, 用于更新非路由优化的 PDP上下文。 信息, 将 UE的下行业务数据转发给目标 SGSN, 并返回更新 PDP上下文响应 消息。
在图 19所示的流程中, 目标 SGSN向源 SGSN返回重定位响应消息, 以 通知源 SGSN释放 UE的路由优化承载, 源 SGSN发送删除 PDP上下文请求 消息给源 GGSN, 以通知源 GGSN删除路由优化的 PDP上下文, 源 GGSN删 除路由优化的 PDP上下文, 这样就不会发生跨路由优化区的业务数据传输, 从而节省了路由优化区之间的传输资源。
除提供上述方法及装置外, 本发明实施例还提供了两种区域性的通信网 络。
一种区域性的通信网络包括:接入网及核心网;接入网提供无线接入功能, 其中,接入网传递终端与核心网之间的控制信令和业务数据; 核心网用于确定 终端从核心网自身所在的区域性的通信网络移动到其他区域性的通信网络或 者获得删除路由优化承载的通知,删除终端在核心网自身所在的区域性的通信 网络中创建的路由优化承载。
另一种区域性的通信网络包括: 接入网及核心网; 接入网提供无线接入功 能, 其中, 接入网传递终端与核心网之间的控制信令和业务数据; 核心网用于 确定终端从另一个区域性的通信网络移动到核心网自身所在的区域性的通信 网络, 删除终端在另一个区域性的通信网络中创建的路由优化承载。
需要说明的是, 在上述所有的实施例中, 如果一个路由优化区是一个 PLMN,那么路由优化区的标识可以是指 PLMN的标识; 如果一个路由优化区 是 PLMN内的一个区域, 那么路由优化区的标识可以是指 PLMN的标识与扩 展项结合后的结果, 其中, 扩展项可以是区域的标识。
在现有技术中, 当终端从源路由优化区移动到其他路由优化区后,在源路 由优化区内创建的路由优化承载会变为跨路由优化区的承载,由于移动运营商 对跨路由优化区的承载通常需要收取额外的漫游费用,所以现有技术会增加用 户的费用负担。但在本发明的所有实施例中, 当终端从源路由优化区移动到其 他路由优化区后, 删除在源路由优化区内创建的路由优化承载, 这样就不会增 加用户的漫游费用。
在现有技术中, 当终端从源路由优化区移动到其他路由优化区后,在源路 由优化区内创建的路由优化承载会变为跨路由优化区的承载,这样会导致移动 运营商之间计费的混乱。但在本发明的所有实施例中, 当终端从源路由优化区 移动到其他路由优化区后,删除在源路由优化区内创建的路由优化承载, 这样 就避免了移动运营商之间发生计费混乱。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程 , 是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于一计算 机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。 其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory, ROM )或随机存储记忆体(Random Access Memory, RAM )等。
以上所述仅是本发明的优选实施方式,应当指出,对于本技术领域的普通 技术人员来说, 在不脱离本发明原理的前提下, 还可以作出若干改进和润饰, 这些改进和润饰也应视为本发明的保护范围。

Claims

权 利 要 求
1.一种路由优化承载的处理方法, 其特征在于, 适用于终端从源拜访地路 建有路由优化承载的场景, 包括:
确定所述终端从所述源拜访地路由优化区移动到所述目标路由优化区,或 者获得删除路由优化承载的通知;
删除所述路由优化承载。
2.如权利要求 1所述的路由优化承载的处理方法, 其特征在于, 确定所述 终端从所述源拜访地路由优化区移动到所述目标路由优化区具体为:所述源拜 访地路由优化区的具有移动性管理功能的网元、所述目标路由优化区的具有移 动性管理功能的网元或所述源拜访地路由优化区的创建有路由优化承载的网 元确定所述终端从所述源拜访地路由优化区移动到所述目标路由优化区; 删除所述路由优化承载具体为:所述源拜访地路由优化区的具有移动性管 理功能的网元、所述目标路由优化区的具有移动性管理功能的网元或所述源拜 访地路由优化区的创建有路由优化承载的网元删除所述路由优化承载。
3.如权利要求 2所述的路由优化承载的处理方法, 其特征在于, 所述源拜 访地路由优化区的具有移动性管理功能的网元确定所述终端从所述源拜访地 路由优化区移动到所述目标路由优化区具体包括:
所述源拜访地路由优化区的具有移动性管理功能的网元在位置更新流程 中收到目标具有移动性管理功能的网元发出的切换请求消息,所述切换请求消 息中携带所述目标具有移动性管理功能的网元所在的路由优化区的标识; 所述源拜访地路由优化区的具有移动性管理功能的网元根据所述目标具 有移动性管理功能的网元所在的路由优化区的标识判断所述目标具有移动性 管理功能的网元是否在所述源拜访地路由优化区的具有移动性管理功能的网 元所在的路由优化区内, 如果不是, 则确定所述终端从所述源拜访地路由优化 区移动到所述目标路由优化区。
4.如权利要求 2所述的路由优化承载的处理方法, 其特征在于, 所述源拜 访地路由优化区的具有移动性管理功能的网元确定所述终端从所述源拜访地 路由优化区移动到所述目标路由优化区具体包括: 所述源拜访地路由优化区的具有移动性管理功能的网元在位置更新流程 或者重定位流程中获取特定标识,所述特定标识与一个路由优化区的标识之间 具有映射关系;
所述源拜访地路由优化区的具有移动性管理功能的网元根据特定标识与 路由优化区的标识之间的映射关系,获得与特定标识对应的目标具有移动性管 理功能的网元所在的路由优化区的标识,并判断所述目标具有移动性管理功能 的网元是否在所述源拜访地路由优化区的具有移动性管理功能的网元所在的 路由优化区内,如果不是, 则确定所述终端从所述源拜访地路由优化区移动到 所述目标路由优化区。
5.如权利要求 1所述的路由优化承载的处理方法, 其特征在于, 获得删除 路由优化承载的通知具体为:所述源拜访地路由优化区的具有移动性管理功能 的网元或所述源拜访地路由优化区的创建有路由优化承载的网元获得删除路 由优化 载的通知;
删除所述路由优化承载具体为:所述源拜访地路由优化区的具有移动性管 理功能的网元或所述源拜访地路由优化区的创建有路由优化承载的网元删除 所述路由优化承载。
6.如权利要求 2或 5所述的路由优化承载的处理方法, 其特征在于, 所述 源拜访地路由优化区的具有移动性管理功能的网元删除所述路由优化承载具 体包括: 所述源拜访地路由优化区的移动性管理实体 MME请求所述源拜访地 路由优化区的服务网关 S-GW删除所述路由优化承载,或者所述源拜访地路由 优化区的服务通用分组无线业务支持节点 SGSN请求所述源拜访地路由优化 区的网关通用分组无线业务支持节点 GGSN删除路由优化的分组数据协议 PDP上下文。
7.如权利要求 2所述的路由优化承载的处理方法, 其特征在于, 所述目标 路由优化区的具有移动性管理功能的网元确定所述终端从所述源拜访地路由 优化区移动到所述目标路由优化区具体包括:
所述目标路由优化区的具有移动性管理功能的网元在位置更新流程中收 到源具有移动性管理功能的网元发出的请求上下文响应消息,所述请求上下文 响应消息中携带所述源具有移动性管理功能的网元所在的路由优化区的标识; 所述目标路由优化区的具有移动性管理功能的网元根据所述源具有移动 性管理功能的网元所在的路由优化区的标识判断所述源具有移动性管理功能 的网元是否在所述目标路由优化区的具有移动性管理功能的网元所在的路由 优化区内, 如果不是, 则确定所述终端从所述源拜访地路由优化区移动到所述 目标路由优化区。
8.如权利要求 2所述的路由优化承载的处理方法, 其特征在于, 所述目标 路由优化区的具有移动性管理功能的网元确定所述终端从所述源拜访地路由 优化区移动到所述目标路由优化区具体包括:
所述目标路由优化区的具有移动性管理功能的网元在位置更新流程或者 重定位流程中获取特定标识 ,所述特定标识与一个路由优化区的标识之间具有 映射关系;
所述目标路由优化区的具有移动性管理功能的网元根据特定标识与路由 优化区的标识之间的映射关系,获得与特定标识对应的源具有移动性管理功能 的网元所在的路由优化区的标识,并判断所述源具有移动性管理功能的网元是 否在所述目标路由优化区的具有移动性管理功能的网元所在的路由优化区内, 如果不是,则确定所述终端从所述源拜访地路由优化区移动到所述目标路由优 化区。
9.如权利要求 2所述的路由优化承载的处理方法, 其特征在于, 所述目标 路由优化区的具有移动性管理功能的网元删除所述路由优化承载具体包括:所 述目标路由优化区的具有移动性管理功能的网元通知所述源拜访地路由优化 区的具有移动性管理功能的网元删除所述路由优化承载,或者所述目标路由优 化区的 MME通知所述目标路由优化区的 S-GW删除所述切换到所述目标路由 优化区的那部分路由承载。
10.如权利要求 5所述的路由优化承载的处理方法, 其特征在于, 所述源 拜访地路由优化区的创建有路由优化承载的网元获得删除路由优化承载的通 知具体为:所述源拜访地路由优化区的分组数据网关 P-GW获得所述源拜访地 路由优化区的 S-GW发出的删除路由优化承载的通知,或者所述源拜访地路由 优化区的 GGSN获得所述源拜访地路由优化区的 SGSN发出的删除路由优化 承载的通知。
11.如权利要求 2或 5所述的路由优化承载的处理方法, 其特征在于, 所 述源拜访地路由优化区的创建有路由优化承载的网元删除路由优化承载具体 包括:所述源拜访地路由优化区的创建有路由优化承载的网元发起删除路由优 化承载。
12.—种路由优化承载的处理装置, 其特征在于, 适用于终端从源拜访地 创建有路由优化承载的场景, 包括:
检测单元, 用于确定终端从源拜访地路由优化区移动到目标路由优化区; 到目标路由优化区后,删除所述终端在所述源拜访地路由优化区创建的路由优 化承载。
13.如权利要求 12所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述源拜访地路由优化区的具有移动性管理功 能的网元中, 所述检测单元包括:
消息收发单元,用于在位置更新流程中收到目标具有移动性管理功能的网 元发出的切换请求消息,所述切换请求消息中携带所述目标具有移动性管理功 能的网元所在的路由优化区的标识;
判断单元,用于根据所述目标具有移动性管理功能的网元所在的路由优化 区的标识判断所述目标具有移动性管理功能的网元是否在所述源拜访地路由 优化区的具有移动性管理功能的网元所在的路由优化区内,如果不是, 则确定 所述终端从所述源拜访地路由优化区移动到所述目标路由优化区。
14.如权利要求 12所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述源拜访地路由优化区的具有移动性管理功 能的网元中, 所述检测单元包括:
消息收发单元, 用于在位置更新流程或者重定位流程中获取特定标识, 所 述特定标识与一个路由优化区的标识之间具有映射关系;
判断单元, 用于根据特定标识与路由优化区的标识之间的映射关系, 获得 与特定标识对应的目标具有移动性管理功能的网元所在的路由优化区的标识, 并判断所述目标具有移动性管理功能的网元是否在所述源拜访地路由优化区 的具有移动性管理功能的网元所在的路由优化区内,如果不是, 则确定所述终 端从所述源拜访地路由优化区移动到所述目标路由优化区。
15.如权利要求 12、 13或 14所述的路由优化承载的处理装置, 其特征在 于,所述路由优化承载的处理装置设置在所述源拜访地路由优化区的 MME或 SGSN中, 所述承载处理单元包括: 请求单元, 用于请求所述源拜访地路由优 化区的 S-GW删除所述路由优化承载, 或者请求所述源拜访地路由优化区的 GGSN删除路由优化的 PDP上下文。
16.如权利要求 12所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述目标路由优化区的具有移动性管理功能的 网元中, 所述检测单元包括:
消息收发单元,用于在位置更新流程中收到源具有移动性管理功能的网元 发出的请求上下文响应消息,所述请求上下文响应消息中携带所述源具有移动 性管理功能的网元所在的路由优化区的标识;
判断单元,用于根据所述源具有移动性管理功能的网元所在的路由优化区 的标识判断所述源具有移动性管理功能的网元是否在所述目标路由优化区的 具有移动性管理功能的网元所在的路由优化区内, 如果不是, 则确定所述终端 从所述源拜访地路由优化区移动到所述目标路由优化区。
17.如权利要求 12所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述目标路由优化区的具有移动性管理功能的 网元中, 所述检测单元包括:
消息收发单元, 用于在位置更新流程或者重定位流程中获取特定标识, 所 述特定标识与一个路由优化区的标识之间具有映射关系;
判断单元, 用于根据特定标识与路由优化区的标识之间的映射关系, 获得 与特定标识对应的源具有移动性管理功能的网元所在的路由优化区的标识,并 判断所述源具有移动性管理功能的网元是否在所述目标路由优化区的具有移 动性管理功能的网元所在的路由优化区内,如果不是, 则确定所述终端从所述 源拜访地路由优化区移动到所述目标路由优化区。
18.如权利要求 12、 16或 17所述的路由优化承载的处理装置, 其特征在 于, 所述路由优化承载的处理装置设置在所述目标路由优化区的 MME中, 所 述承载处理单元包括: 通知单元, 用于通知所述源拜访地路由优化区的 MME 删除所述路由优化承载,或者通知所述目标路由优化区的 S-GW删除所述切换 到所述目标路由优化区的那部分路由承载。
19.如权利要求 12所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述源拜访地路由优化区的创建有路由优化承 载的网元中,所述承载处理单元包括:发起单元,用于发起删除路由优化承载。
20.—种路由优化承载的处理装置, 其特征在于, 包括:
消息收发单元,用于当终端从源拜访地路由优化区移动到目标路由优化区 时, 获得删除路由优化承载的通知;
承载处理单元, 用于在所述消息收发单元获得删除路由优化承载的通知 后, 删除所述终端在所述源拜访地路由优化区创建的路由优化承载。
21.如权利要求 20所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述源拜访地路由优化区的具有移动性管理功 能的网元中,所述消息收发单元获得的删除路由优化承载的通知是所述目标路 由优化区的具有移动性管理功能的网元发出的。
22.如权利要求 20或 21所述的路由优化承载的处理装置, 其特征在于, 所述路由优化承载的处理装置设置在所述源拜访地路由优化区的 MME 或 SGSN中, 所述承载处理单元包括: 请求单元, 用于请求所述源拜访地路由优 化区的 S-GW删除所述路由优化承载, 或者请求所述源拜访地路由优化区的 GGSN删除路由优化的 PDP上下文。
23.如权利要求 20所述的路由优化承载的处理装置, 其特征在于, 所述路 由优化承载的处理装置设置在所述源拜访地路由优化区的 P-GW中,所述消息 收发单元获得的删除路由优化承载的通知是所述源拜访地路由优化区的 S-GW发出的; 或者,
所述路由优化承载的处理装置设置在所述源拜访地路由优化区的 GGSN 中,所述消息收发单元获得的删除路由优化承载的通知是所述源拜访地路由优 化区的 SGSN发出的。
24.如权利要求 20或 23所述的路由优化承载的处理装置, 其特征在于, 所述路由优化承载的处理装置设置在所述源拜访地路由优化区的创建有路由 优化承载的网元中, 所述承载处理单元包括: 发起单元, 用于发起删除路由优 化承载。
PCT/CN2009/073880 2008-09-22 2009-09-11 路由优化承载的处理方法和装置 WO2010031317A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810211456.7 2008-09-22
CN2008102114567A CN101686522B (zh) 2008-09-22 2008-09-22 路由优化承载的处理方法、装置

Publications (1)

Publication Number Publication Date
WO2010031317A1 true WO2010031317A1 (zh) 2010-03-25

Family

ID=42039092

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073880 WO2010031317A1 (zh) 2008-09-22 2009-09-11 路由优化承载的处理方法和装置

Country Status (2)

Country Link
CN (1) CN101686522B (zh)
WO (1) WO2010031317A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1518392A (zh) * 2003-01-24 2004-08-04 ��ʽ����Ntt����Ħ 本地位置管理器、原籍位置管理器和移动通信系统
CN1870772A (zh) * 2005-10-14 2006-11-29 华为技术有限公司 一种承载路径优化方法
CN1964317A (zh) * 2005-11-08 2007-05-16 华为技术有限公司 一种无线接入网络中的路由优化方法和系统
WO2008084287A1 (en) * 2007-01-09 2008-07-17 Telefonaktiebolaget Lm Ericsson (Publ) Mechanism to uniquely identify and unify a user's set of packet bearer contexts in a mobile telecommunications network

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1697394A (zh) * 2004-05-12 2005-11-16 华为技术有限公司 多媒体广播/组播服务业务中路由区更新的方法
CN100370742C (zh) * 2004-05-12 2008-02-20 华为技术有限公司 一种多媒体广播/组播服务业务中路由区更新的方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1518392A (zh) * 2003-01-24 2004-08-04 ��ʽ����Ntt����Ħ 本地位置管理器、原籍位置管理器和移动通信系统
CN1870772A (zh) * 2005-10-14 2006-11-29 华为技术有限公司 一种承载路径优化方法
CN1964317A (zh) * 2005-11-08 2007-05-16 华为技术有限公司 一种无线接入网络中的路由优化方法和系统
WO2008084287A1 (en) * 2007-01-09 2008-07-17 Telefonaktiebolaget Lm Ericsson (Publ) Mechanism to uniquely identify and unify a user's set of packet bearer contexts in a mobile telecommunications network

Also Published As

Publication number Publication date
CN101686522B (zh) 2012-04-04
CN101686522A (zh) 2010-03-31

Similar Documents

Publication Publication Date Title
US11678240B2 (en) Method and system for transferring user equipment in mobile communication system
JP3373501B2 (ja) アクセスネットワークにおける移動エージェントの選択
JP5044020B2 (ja) Lteシステムにおいて、ユーザ静的ipアドレスのアドレッシングをサポートする方法、システムおよび装置
US9668293B2 (en) Relocation of mobility anchor for nomadic subscribers
US9769852B2 (en) Maintaining current cell location information in a cellular access network
US8855045B2 (en) Method and system for controlling establishment of local IP access
CN101677470B (zh) 服务请求的处理方法、装置及系统
EP2259657B1 (en) Method for indicating the bearer management of a serving gateway
CN101848443B (zh) 通信业务切换处理方法、网络系统与互通功能实体
CN104994575A (zh) 更新用户设备位置信息的方法
CN102111748B (zh) 本地ip连接建立方法及系统
WO2011023090A1 (zh) 家庭基站接入场景下寻呼的处理方法和装置
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
CN101867986B (zh) 一种csfb功能的激活方法及系统
JP2018508155A (ja) 通信システム
US20100111060A1 (en) Communication Of Information Between Devices In Communication Networks
WO2008154783A1 (fr) Procédé pour établir un tunnel à partir de sgsn vers la passerelle de service
WO2012130018A1 (zh) 一种ip分流连接移动性支持的方法及系统
WO2011076063A1 (zh) Lipa或sipto管理方法、装置和系统
WO2012051892A1 (zh) 一种数据路由控制方法及系统
WO2012028071A1 (zh) 一种查询本地网关的方法和系统
WO2011020418A1 (zh) 终端转为连接态时更改服务网关的连接激活方法及系统
US9271313B2 (en) Service frequency based 3GDT
WO2011134324A1 (zh) 一种数据分流的动态控制方法及系统
CN101998364B (zh) 一种对本地网际协议访问连接实施管理的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09814037

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09814037

Country of ref document: EP

Kind code of ref document: A1