WO2011130920A1 - 本地路由实现方法及***、网络设备 - Google Patents

本地路由实现方法及***、网络设备 Download PDF

Info

Publication number
WO2011130920A1
WO2011130920A1 PCT/CN2010/072130 CN2010072130W WO2011130920A1 WO 2011130920 A1 WO2011130920 A1 WO 2011130920A1 CN 2010072130 W CN2010072130 W CN 2010072130W WO 2011130920 A1 WO2011130920 A1 WO 2011130920A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
address
service flow
gateway
base station
Prior art date
Application number
PCT/CN2010/072130
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 华为技术有限公司
Priority to PCT/CN2010/072130 priority Critical patent/WO2011130920A1/zh
Priority to CN201080001610.3A priority patent/CN102365845B/zh
Priority to PCT/CN2010/076243 priority patent/WO2011130983A1/zh
Priority to CN201410766775.XA priority patent/CN104602220B/zh
Publication of WO2011130920A1 publication Critical patent/WO2011130920A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/08—Mobility data transfer
    • H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a local routing implementation method and system, and a network device. Background technique
  • Wired Worldwide Interoperability for Microwave Access
  • IEEE802.16 wireless access technology provides users with high-speed data transmission capabilities, and has received extensive attention.
  • the uplink sent by the terminal is transmitted to the serving gateway (Serving GW) via the base station (Base Station, BS for short), and then transmitted to the anchor gateway (Anchor GW). ), and finally transmitted to the external network through the home agent (HA); the downlink message is routed from the external network to the terminal through the bearer path in the opposite direction.
  • the communication peer of the end user is another mobile terminal, if the two terminals are located under the same serving gateway (Serving GW), the message between the two terminals still needs to be first sent from the serving gateway (Serving GW M). The HA is then returned from the HA to the serving gateway (Serving GW) and sent to the target terminal. Therefore, the message transmission path between the two terminals overlaps from the serving gateway (Serving GW) to the HA.
  • the MSC maps the integrated service digital network (ISDN) telephone number of the call peer end carried by the terminal to the pair.
  • ISDN integrated service digital network
  • IMSI International mobile subscriber identity
  • BSS Base Station Subsystem
  • the inventor finds that when the terminal in the WiMAX network initiates the service, the serving gateway device is not able to determine whether the peer is located in the local network under the gateway device according to the MSID of the terminal, so in the prior art, The local triggering technique cannot be applied to WiMAX networks for local route triggering. Summary of the invention
  • the purpose of the embodiments of the present invention is to provide a local routing implementation method and system, and a network device, which reduce packet transmission delay and reduce the core network transmission load.
  • the embodiment of the invention provides a local routing implementation method, including:
  • the service flow bearer signaling includes service flow information provided by the terminal and an IP address of a peer end that communicates with the terminal;
  • the terminal and the peer are located under the same local route execution device according to the IP address of the terminal and the IP address of the peer, performing a local routing operation on the corresponding message of the service flow.
  • the embodiment of the invention provides a network device, including:
  • An acquiring module configured to acquire an Internet Protocol IP address of the terminal in a process of terminal handover;
  • a receiving module configured to receive a service flow bearer signaling, where the service flow bearer signaling includes service flow information provided by the terminal And an IP address of the peer that communicates with the terminal;
  • a routing module configured to perform a local routing operation on the packet corresponding to the service flow, if the terminal and the peer are located under the network device according to the IP address of the terminal and the IP address of the peer .
  • the embodiment of the invention provides a local routing implementation method, including:
  • the anchoring gateway receives the service flow bearer signaling initiated by the serving gateway or the base station according to the service flow information provided by the terminal, and the opposite end transmits the service flow, and the opposite end is the terminal device that communicates with the terminal, the service
  • the flow bearer signaling carries the IP address of the peer end;
  • the anchor gateway determines that the terminal and the peer end are located under the same local route execution device according to the IP address of the peer end and the acquired IP address of the terminal, the anchor gateway is The service flow performs a local route authorization, and notifies the local route execution device to perform local routing on the message corresponding to the service flow.
  • the embodiment of the invention provides a network device, including:
  • a receiving module configured to receive a service flow bearer signaling initiated by the terminal and forwarded by the original serving gateway, and the peer end is a terminal device that communicates with the terminal, where the service flow bearer signal The order carries the IP address of the opposite end;
  • an authorization module configured to perform local routing authorization on the service flow, if it is determined that the terminal and the peer end are located under the network device according to the IP address of the peer end and the obtained IP address of the terminal;
  • the notification module is configured to notify the network device to perform local routing on the packet corresponding to the service flow.
  • the embodiment of the invention provides a local routing implementation method, including:
  • the anchoring gateway receives the service flow bearer signaling initiated by the serving gateway according to the service flow information provided by the terminal, and the peer end is a terminal device that communicates with the terminal, and the service flow bearer signal The order carries the IP address of the opposite end;
  • the anchor gateway determines that the terminal and the peer are located under the serving gateway according to the IP address of the peer and the obtained IP address of the terminal, sending a local routing indication to the serving gateway, The serving gateway determines, according to the local routing indication, whether the packet corresponding to the service flow can be locally routed by the base station under the serving gateway.
  • the embodiment of the invention provides a local routing implementation system, including: an anchor gateway, a service gateway, Base station
  • the anchor gateway receives the service flow bearer signaling initiated by the serving gateway according to the service flow information provided by the terminal, and the peer end is a terminal device that communicates with the terminal,
  • the service flow bearer signaling carries the IP address of the peer end;
  • the anchor gateway determines that the terminal and the peer are located under the serving gateway according to the IP address of the peer and the obtained IP address of the terminal, sending a local routing indication to the serving gateway, And causing, by the serving gateway, to determine, according to the local routing indication, whether a packet corresponding to the service flow can be locally routed by the base station under the serving gateway.
  • the local routing implementation method, system, and network device provided by the embodiment of the present invention, if the terminal and the peer end are located under the same local routing execution device according to the IP address of the terminal and the IP address of the peer end, the corresponding report to the service flow
  • the local routing operation is performed, and the corresponding message of the service flow is transmitted to the peer end through the local route, and the packet corresponding to the service flow is routed to the HA through the local routing execution device, and then transmitted to the HA.
  • the external network reduces the delay of the transmission of packets corresponding to the service flow between the network elements and reduces the transmission load of the core network.
  • FIG. 1 is a structural diagram of a network system to which an embodiment of the present invention is applied;
  • FIG. 2 is a schematic flowchart of an embodiment of a method for implementing local routing according to the present invention
  • FIG. 3 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention.
  • FIG. 4 is a signaling flowchart applicable to the embodiment shown in FIG. 3;
  • FIG. 5 is a schematic flowchart diagram of another embodiment of a method for implementing local routing according to the present invention.
  • FIG. 6 is a signaling flowchart applicable to the embodiment shown in FIG. 5;
  • Figure ⁇ is a schematic structural diagram of an embodiment of a network device of the present invention.
  • FIG. 8 is a schematic structural diagram of still another embodiment of a network device according to the present invention.
  • FIG. 9 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention.
  • FIG. 10 is a signaling flowchart applicable to the embodiment shown in FIG. 9;
  • FIG. 11 is a schematic structural diagram of still another embodiment of a network device according to the present invention.
  • FIG. 12 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention.
  • FIG. 13 is a signaling flowchart applicable to the embodiment shown in FIG. 12;
  • FIG. 14 is a schematic structural diagram of an embodiment of a local routing implementation system according to the present invention. detailed description
  • FIG. 1 is a network system architecture diagram of an embodiment of the present invention.
  • the terminal before a terminal switches from the original base station 11 to the target base station 17, the terminal sends the packet to the anchor through the original base station 11 and the original serving gateway 12.
  • the gateway 13 and the anchor gateway 13 send the message to the HA 14 and transmit it to the external network 15 through the HA 14 to implement information exchange between the terminal and the external network.
  • the terminal After the terminal switches from the original base station 11 to the target base station 17, the terminal passes the target.
  • the base station 17 and the target serving gateway 16 send the message to the anchor gateway 13.
  • the anchor gateway 13 then sends the message to the HA 14 and transmits it to the external network 15 through the HA 14, thereby realizing the information exchange between the terminal and the external network.
  • the anchor gateway 13 is an anchor point of the transmission path of the terminal when the terminal is switched, and the anchor point can acquire the IP address of the terminal when the terminal initially accesses the network; the original service gateway 12 is before the terminal is switched.
  • the serving gateway corresponding to the original base station 11 and the target serving gateway 16 are the serving gateways corresponding to the target base station 17 after the terminal handover; further, if the terminal initially accesses the network under the original base station 11, the original serving gateway 12 and the anchoring Gateway 13 can be the same gateway device.
  • the system architecture shown in Figure 1 is only an illustrative illustration. It does not constitute a limitation on the applicable scenarios of the embodiments of the present invention.
  • FIG. 2 is a schematic flowchart of an embodiment of a method for implementing local routing according to the present invention. As shown in FIG. 2, the embodiment includes the following steps:
  • Step 201 Obtain an IP address of the terminal in a process of switching the terminal.
  • Step 202 Receive service flow bearer signaling, where the service flow bearer signaling includes service flow information provided by the terminal and an IP address of the peer end that communicates with the terminal;
  • the service flow bearer signaling may be initiated by the terminal, or may be initiated by the base station according to the service flow information provided by the terminal.
  • Step 203 If it is determined that the terminal and the peer end are located under the same local route execution device according to the IP address of the terminal and the IP address of the peer end, perform local route operation on the packet corresponding to the service flow.
  • the actual network architecture of the local routing execution may be a base station or a serving gateway.
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the peer end are located under the same local route execution device according to the IP address of the terminal and the IP address of the peer end, perform local execution on the corresponding message flow of the service flow.
  • the routing operation is implemented to transmit the corresponding message of the service flow to the peer end through the local route, because the device corresponding to the service flow is routed to the HA through the local route execution device, and then transmitted to the external network. Therefore, the delay of the transmission of the message corresponding to the service flow between the network elements is reduced, and the transmission load of the core network is reduced.
  • FIG. 3 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention.
  • an example is obtained by taking an IP address of the original service gateway before the terminal handover in the terminal handover process as an example, where
  • the network device in the embodiment of the present invention may be specifically a serving gateway (Serving ASN-GW) or a base station after the terminal is switched; as shown in FIG. 3, and described in conjunction with the system architecture diagram shown in FIG. 1, the embodiment includes the following steps. :
  • Step 301 Receive a handover confirmation message that carries the IP address of the terminal from the original serving gateway.
  • the handover confirmation message that carries the IP address of the terminal from the original serving gateway may be a handover indication message sent by the original base station after receiving the terminal. After forwarding to the original service gateway, the original base station receives The handover indication message from the terminal may be a MOB_HO_IND message, and the original base station sends a handover confirmation message carrying the IP address of the terminal to the original target service gateway according to the handover indication message, and further, carries the terminal with the terminal
  • the handover confirmation message of the IP address may be a HO-Cnf message.
  • the original serving gateway carries the handover confirmation message of the IP address of the terminal.
  • the target service gateway After being sent to the target service gateway, the target service gateway also needs to forward the handover confirmation message carrying the IP address of the terminal to the target base station.
  • the target entity of the embodiment of the present invention is the target service gateway after the terminal handover, the target service gateway is in the target.
  • the serving gateway may determine whether to forward the handover confirmation message to the target base station according to actual needs. If the target serving gateway forwards the handover confirmation message to the target base station, the target service gateway may further determine whether the IP address of the terminal needs to be carried in the Switch the confirmation message.
  • Step 302 Obtain an IP address of the terminal from the handover confirmation message.
  • the IP address of the terminal carrying the IP address of the terminal carries the IP address of the terminal.
  • the handover confirmation message acquires the IP address of the terminal.
  • Step 303 Receive a service flow bearer signaling initiated by the terminal and a peer-to-peer transport service flow, where the peer end is a terminal device that communicates with the terminal, and the service flow bearer signaling carries the IP address of the peer end. ;
  • the service flow bearer signaling may be initiated by the terminal, or may be initiated by the base station according to the service flow information provided by the terminal. If the main body of the embodiment of the present invention is the target base station, the service flow bearer signaling may be initiated by the terminal and sent to the terminal.
  • the target base station if the subject of the embodiment of the present invention is the target serving gateway, may be initiated and sent by the target base station according to the service flow information provided by the terminal to the target serving gateway; further, after the terminal switches from the original base station to the target base station,
  • the service flow carrying signaling can implement a new bearer between the target base station and the target serving gateway or modify the existing bearer, so that the target base station and the target serving gateway transmit the service flow initiated by the terminal to the opposite end; for example:
  • the terminal sends a dynamic service increase request (DSA-REQ) message to create a new bearer, or the terminal sends a dynamic service modification request (DSC-REQ) message to modify the existing bearer.
  • DSA-REQ dynamic service increase request
  • DSC-REQ dynamic service modification request
  • Step 304 If it is determined that the terminal and the peer end are located under the same local route execution device according to the IP address of the terminal and the IP address of the peer end, send a path registration request message to the anchor gateway, indicating that the anchor gateway registers the request message according to the path. Authorize the service flow;
  • the target base station or the target serving gateway may be specifically configured as the target base station, and the target base station sends the path registration request message to the anchor gateway through the target serving gateway. If the execution subject is the target service gateway, the target service gateway directly sends a path registration request message to the anchor gateway; the path registration request (Path_Reg_Req) message may carry indication information for performing local routing, indicating the anchor gateway Authorize the service flow for the service flow.
  • Step 305 Receive a response message of completing the service authorization returned by the anchor gateway.
  • the target base station receives the response message of the completed service authorization returned by the anchor gateway through the target serving gateway, and if the subject of the embodiment of the present invention is the target service gateway, the target The service gateway directly receives the response message of completing the service authorization returned by the anchor gateway;
  • Step 306 Route the packet corresponding to the service flow to the opposite end according to the response message of the completion service authorization.
  • the IP address of the peer end is located under the same local route execution device, and the corresponding message flow corresponding to the terminal is routed to the device through the local route execution device according to the IP address of the peer end.
  • the peer end thus realizing the local route of the packet corresponding to the service flow.
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the opposite end are located under the same target serving gateway or the target base station according to the IP address of the terminal and the IP address of the opposite end, the target serving gateway or the target base station will The packet corresponding to the service flow is locally routed, and the packet corresponding to the service flow is transmitted to the peer end through the local route, because the packet corresponding to the service flow is avoided through the target service gateway or the target base station. Transfer to the external network after HA Therefore, the delay of the transmission of the message corresponding to the service flow between the network elements is reduced, and the transmission load of the core network is reduced.
  • the IP address of the terminal is obtained by the authenticator of the access network where the terminal is located in the process of the terminal handover.
  • the process of obtaining the IP address of the terminal may be specifically:
  • the target service gateway sends a context request message to the authenticator for requesting acquisition of the IP address of the terminal;
  • the target serving gateway acquires the IP address of the terminal from the context response message carrying the IP address of the terminal.
  • the process of obtaining the IP address of the terminal may be:
  • the target base station sends a context request message for requesting acquisition of the IP address of the terminal to the authenticator through the target serving gateway;
  • the target base station obtains the IP address of the terminal from the context response message carrying the IP address of the terminal by the target serving gateway.
  • FIG. 4 is a signaling flowchart applicable to the embodiment shown in FIG. 3.
  • the serving service gateway (Serving ASN-GW) switches to the terminal before the terminal handover process.
  • the service gateway obtains the IP address of the terminal.
  • the original service gateway is the service gateway before the terminal handover
  • the target service gateway is the service gateway after the terminal handover
  • the anchor gateway (Anchor GW) transmits the service flow from the service gateway to the outside through the HA. Network;
  • this embodiment includes the following steps:
  • Step 401 The terminal sends a handover indication message to the original base station, where the handover indication message is used to indicate that the original base station needs to switch the bearer service to the target base station (New BS);
  • the handover indication message may specifically be a terminal handover indication (MOB_HO_IND) message.
  • Step 402 The original base station sends a handover confirmation (HO_Cnf) message to the target base station, and confirms that the terminal will switch from the original base station to the target base station; specifically, the original serving base station (Old Serving GW) passes the original serving gateway and the target serving gateway (New Serving GW) sends the handover confirmation message (HO_Cnf) to the target base station after the terminal handover, and the original base station or the original serving gateway includes the IP address of the terminal in the handover confirmation message; the serving service gateway (Serving GW) or the target base station Obtaining an IP address of the terminal by using the handover confirmation message (HO_Cnf);
  • Step 403 The target base station returns a handover response (HO_Ack) message to the original base station (Old BS), where the handover response message may be forwarded to the original base station via a serving service gateway (Serving GW) and an original serving gateway (Old Serving GW);
  • HO_Ack handover response
  • Serving GW serving service gateway
  • Old Serving GW original serving gateway
  • Step 404 The target base station acquires a context message of the terminal from an authenticator ( Authenticator );
  • the context message may be a security key (Key) or the like, and the context message may be forwarded to the target base station by using a serving GW (Serving GW);
  • Key a security key
  • Server GW serving GW
  • Step 405 The terminal re-enters the network under the target base station.
  • Step 406 The target base station establishes a bearer with the anchor gateway by using the target serving gateway, and is configured to transmit a service flow currently initiated by the terminal.
  • the packet corresponding to the service flow initiated by the terminal is forwarded to the external network through the anchor gateway.
  • Step 407 The target base station updates a Cipher-based Message Authentication Code (CMAC) key (Key) for the air interface authentication to the authenticator (Authenticator);
  • CMAC Cipher-based Message Authentication Code
  • Step 408 The target base station sends a handover completion (HO_Complete) message to the original base station, indicating that the original base station handover is complete; wherein the handover completion message may be forwarded to the original base station by using the target service gateway and the original service gateway;
  • HO_Complete handover completion
  • Step 409 The original base station returns a handover response (HO_Ack) message to the target base station, and clears the context message of the terminal in the original base station, where the context message may be: a user key, bearer information, etc., where the handover response message may pass
  • HO_Ack handover response
  • the context message may be: a user key, bearer information, etc.
  • the handover response message may pass
  • the original service gateway and the target service gateway are forwarded to the target base station;
  • the original base station can be switched to the target base station, and the target service gateway or the target base station acquires the IP address of the terminal.
  • the terminal initiates the service flow carrying message.
  • the command can be used to establish a new bearer or modify an existing bearer to transmit a packet related to the service flow.
  • the service flow bearer signaling can be different messages for different network elements.
  • the service flow bearer signaling may be a dynamic service add request (DSA-REQ) message, which may be used to establish a new bearer or a dynamic service modification request (DSC-REQ) message, for modifying an existing bearer.
  • DSA-REQ dynamic service add request
  • DSC-REQ dynamic service modification request
  • the service flow bearer signaling may be a Path Registration Request (Path_Reg_req) message or a Path Modify Request (Path_Mod_req) message, and the foregoing message is also applicable to the present invention.
  • Path_Reg_req Path Registration Request
  • Path_Mod_req Path Modify Request
  • Step 410 The terminal sends a dynamic service increase request (DSA-REQ) message to the target base station, indicating that the target base station establishes a new bearer, where the DSA-REQ message carries the IP quintuple information of the service flow (Packet classification) Rule), the IP quintuple information specifically includes a source IP address, a destination IP address, a source port number, a destination port number, and a protocol type of the service flow;
  • DSA-REQ dynamic service increase request
  • Step 411 The target base station returns a dynamic service establishment response (DSX-RVD) message to the terminal, Indicates that the dynamic service increase request (DSA-REQ) message is received;
  • DSX-RVD dynamic service establishment response
  • DSA-REQ dynamic service increase request
  • Step 412 The target base station sends a path registration request (Path_Reg_Req) message to the target serving gateway, and is used to request to establish a new bearer, where the path registration request message carries the IP quintuple information of the service flow;
  • Path_Reg_Req path registration request
  • Step 413 If the target serving gateway (Serving GW) determines that the peer end of the service flow is located under the target monthly service gateway according to the destination IP address in the IP quintuple information of the service flow and the IP address of the terminal, The message corresponding to the service flow may be transmitted to the peer end by using a local route.
  • Step 415 The target serving gateway performs resource authorization on the new bearer that the terminal indicates to the target base station in step 410, so that the anchor gateway can authorize the local route according to the indication information of the local route obtained in step 414;
  • the target serving gateway may implement the local routing authorization by sending an authorization request to the authenticator in the access network; the anchoring gateway returns a response message to the target base station through the target serving gateway, thereby establishing the new bearer;
  • Step 416 The target serving gateway transmits the packet corresponding to the service flow to the peer end by using the local route on the new bearer.
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the peer end are located under the target serving gateway according to the IP address of the terminal and the IP address of the peer end carried by the service flow bearer signaling, the target serving gateway will be from the terminal.
  • the packet corresponding to the service flow is transmitted to the peer end by performing a local routing operation, thereby reducing the traffic flow by avoiding routing the corresponding traffic of the service flow to the HA through the anchor gateway and then transmitting the packet to the external network.
  • the delay of the corresponding packet transmission between the network elements reduces the transmission load of the core network.
  • the above process is exemplified by the local service route executed by the target service gateway. If the local route is performed for the target base station, the target base station obtains the IP address of the terminal through the handover confirmation message, and if the IP quintuple information of the service flow is obtained. The destination IP address and the IP address of the terminal determine that the opposite end of the service flow is located under the target base station, and then determine that the service flow can be transmitted to the local route through the local route.
  • the target base station and the network element device such as the authenticator, refer to the interaction between the target service gateway and the authenticator, and details are not described herein.
  • FIG. 5 is a schematic flowchart of another embodiment of a method for implementing local routing according to the present invention.
  • an example is provided for obtaining an IP address of a terminal by an authenticator of an access network where a terminal is located in a terminal handover process, where The network device that performs the embodiment of the present invention may be specifically a serving gateway (Serving ASN-GW) after the terminal is switched or a base station after the terminal is switched.
  • the embodiment of the present invention uses a base station as an example for example, as shown in FIG. 5, Embodiments of the present invention include the following steps:
  • Step 501 The target base station after the handover sends a context request message for requesting the IP address of the terminal to the authenticator.
  • the context request message may be forwarded to the authenticator through the target service gateway.
  • Step 502 The target base station receives a context response message that is sent by the authenticator according to the context request message and carries an IP address of the terminal.
  • the context response message may be forwarded to the authenticator through the target service gateway.
  • the context response message may specifically be a Context_Rsp message.
  • Step 503 The target base station receives the service flow bearer signaling initiated by the terminal and the peer end transport service flow, where the peer end is a terminal device that communicates with the terminal, and the service flow bearer signaling carries the IP address of the opposite end;
  • the service flow carrying signaling can implement a new bearer between the target base station and the target serving gateway, or modify the existing bearer, thereby passing the target base station and the target service.
  • the gateway transmits the service flow initiated by the terminal to the peer end; for example: the terminal sends a dynamic service increase request (DSA-REQ) message to create a new bearer, or the terminal sends a dynamic service modification request (DSC-REQ) message to modify the current Some bearers, through the new bearer or modified bearer, realize the transmission of the service flow initiated by the terminal.
  • DSA-REQ dynamic service increase request
  • DSC-REQ dynamic service modification request
  • Step 504 If the target base station determines that the terminal and the opposite end are located under the target base station according to the IP address of the terminal and the IP address of the opposite end, the target base station sends indication information for performing local routing to the anchor gateway.
  • the indication information of the local routing may be carried in the path modification request.
  • the anchoring gateway performs service authorization on the service flow according to the indication information of the local routing.
  • Step 505 The target base station receives a response message that is returned by the anchoring gateway according to the indication information of the local routing.
  • Step 506 The target base station routes the packet corresponding to the service flow from the terminal to the opposite end according to the response message.
  • the target service gateway since the IP address of the peer is also located under the target serving gateway, the target service gateway routes the service flow initiated by the terminal to the peer through the target service gateway according to the IP address of the peer end, thereby implementing Local route of the packet corresponding to the service flow by the target base station.
  • the local route implementation method provided by the embodiment of the present invention, if the target base station determines the IP address of the target base station and the opposite end as the target base station according to the IP address of the terminal and the IP address of the opposite end carried by the service flow bearer signaling, the target base station will be from the terminal.
  • the corresponding report of the service flow is routed to the peer end, and the corresponding message of the service flow is reduced by routing the corresponding message corresponding to the service flow to the HA through the anchor gateway, thereby reducing the corresponding report of the service flow.
  • the delay of transmission between the network elements reduces the transmission load of the core network.
  • FIG. 6 is a signaling flowchart applicable to the embodiment shown in FIG.
  • the target base station acquires the IP address of the terminal from the base station before the terminal handover in the terminal handover process.
  • the original base station is the base station before the terminal handover
  • the target base station is the base station after the terminal handover
  • the anchor GW transmits the service flow from the target base station to the core network through the HA.
  • the embodiment includes the following steps:
  • Step 601 The terminal sends a handover indication message to the original base station, where the handover indication message is used to indicate that the original base station needs to switch the bearer service to the target base station (Target BS );
  • the handover indication message may specifically be a terminal handover indication (MOB_HO_IND) message.
  • Step 602 The original base station sends a handover confirmation (HO_Cnf) message to the target base station, confirming that the terminal will handover from the original base station to the target base station; and the target base station returns a handover response (HO Ack) to the original base station.
  • HO_Cnf handover confirmation
  • HO Ack handover response
  • the handover confirmation message may be sent to the target base station by using the original serving gateway and the target serving gateway; the handover response message may be forwarded to the terminal by the target serving gateway and the original serving gateway; Step 603: The target base station sends a context request to the target serving gateway.
  • a Context-Req message configured to request, by an authenticator in the access network, context information of the terminal, where the context request message optionally carries indication information for acquiring an IP address of the terminal, by using a target service gateway ( Serving GW ) forwarded to the authenticator ( Authenticator );
  • Step 604 The authenticator returns a context response (Context_Rsp) message to the target base station by using the target serving gateway, where the context response message carries the IP address of the terminal, and the target serving gateway forwards the IP address to the target base station;
  • Context_Rsp context response
  • the message, the target service gateway and the target base station can obtain the IP address of the terminal;
  • Step 605 The terminal re-enters the network under the target base station.
  • Step 606 The target base station establishes a bearer with the anchor gateway by using the target serving gateway, and is configured to transmit a service flow currently initiated by the terminal.
  • the service flow initiated by the terminal is forwarded to the core network through the anchor gateway by establishing a bearer between the target base station, the target service gateway, and the anchor gateway.
  • Step 607 The target base station updates the CMAC key (Key) information used for air interface authentication to the authenticator (Authenticator);
  • Step 608 The target base station sends a handover completion (HO_Complete) message to the original base station, indicating that the original base station handover is completed; wherein the handover completion message may be forwarded to the original base station by using the target service gateway and the original service gateway;
  • HO_Complete handover completion
  • Step 609 The original base station returns a handover response (HO_Ack) message to the target base station, and clears the context message of the terminal at the original base station.
  • the handover response message may be forwarded to the target base station by using the original serving gateway and the target serving gateway;
  • the message stores the user key, bearer information, and so on.
  • the original base station can be switched to the target base station, and
  • the target service gateway or the target base station obtains the IP address of the terminal; when the terminal initiates a new service flow, the terminal can establish a new bearer or modify an existing bearer by initiating the service flow bearer signaling, and implement the transmission and the service flow.
  • the service flow bearer signaling may be a dynamic service add request (DSA-REQ) message, used to establish a new bearer, or may be a dynamic service modification request (DSC-REQ),
  • DSA-REQ dynamic service add request
  • DSC-REQ dynamic service modification request
  • Step 610 The terminal sends a dynamic service modification request (DSC-REQ) message to the target base station, instructing the target base station to modify the existing bearer, to reuse the existing bearer to transmit a new service flow.
  • DSC-REQ dynamic service modification request
  • the IP quintuple information of the service flow is carried in the dynamic service modification request message.
  • the IP quintuple information includes a source IP address, a destination IP address, a source port number, and a destination port number of the service flow. agreement type.
  • Step 611 The target base station returns a dynamic service modification response (DSX-RVD) message to the terminal, indicating that the dynamic service modification request (DSC-REQ) message is received.
  • DSX-RVD dynamic service modification response
  • DSC-REQ dynamic service modification request
  • Step 612 The target base station determines, according to the destination IP address in the IP quintuple in the service flow and the IP address of the terminal, that the peer end of the service flow is located under the target base station;
  • Step 613 The target base station sends a Path Modify Request (Path_Mod_Req) message to the target serving gateway, and is used to request to modify the existing bearer.
  • the path modification request message carries the indication information for performing the local route.
  • Step 614 The target service gateway sends the path modification request to the anchor gateway.
  • Step 615 The anchor gateway performs resource authorization on the existing bearer, and the anchor gateway may further authorize the local route according to the indication information of the local routing.
  • the anchor gateway returns a response message to the target base station by using the target serving gateway.
  • Step 616 The target base station sends a service packet corresponding to the service flow on the modified existing bearer. Transmitting the peer through a local route;
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the peer end are the IP addresses of the target base station according to the IP address of the terminal and the IP address of the peer carried by the service flow bearer signaling, the target service gateway will come from the terminal.
  • the message corresponding to the service flow is transmitted to the peer end by performing a local route. Since the packet corresponding to the service flow is routed to the HA through the anchor gateway, and then transmitted to the external network, the service flow is reduced.
  • the delay of the corresponding 4 ⁇ text transmission between the network elements reduces the transmission load of the core network.
  • the handover procedure of the terminal described in the foregoing embodiment of FIG. 2 to FIG. 6 is only an example of the embodiment of the present invention, so that the target service gateway or the target base station can obtain the IP address of the terminal through the handover process of the terminal.
  • the method for obtaining the message and the order of obtaining the message are all the implementation methods of the embodiments of the present invention, and the embodiments of the present invention are only described for convenience.
  • FIG. 7 is a schematic structural diagram of an embodiment of a network device according to the present invention.
  • the network device in the embodiment of the present invention may be a service gateway or a base station.
  • the embodiment includes: an obtaining module 71 and a receiving module 72. , routing module 73;
  • the obtaining module 71 acquires the Internet Protocol IP address of the terminal in the process of the terminal handover; the receiving module 72 receives the service flow bearer signaling, where the service flow bearer signaling includes the service flow information provided by the terminal and The IP address of the peer that the terminal performs communication; if it is determined that the terminal and the peer are located under the network device according to the IP address of the terminal and the IP address of the peer, the routing module 73 processes the service flow. The corresponding message performs a local routing operation.
  • the routing module 73 performs a local routing operation on the packet corresponding to the service flow.
  • the packet corresponding to the service flow is transmitted to the peer end through the local route, and the packet corresponding to the service flow is routed to the HA through the network device, and then transmitted to the external network, thereby reducing the traffic flow. Delay in transmission of corresponding packets between network elements, The core network transmission load is low.
  • FIG. 8 is a schematic structural diagram of another embodiment of a network device according to the present invention.
  • the network device in the embodiment of the present invention may be a service gateway or a base station.
  • the embodiment includes: an obtaining module 81 and a receiving module. 82, routing module 83;
  • the obtaining module 81 acquires the Internet Protocol IP address of the terminal in the process of the terminal switching; the receiving module 82 receives the service flow bearer signaling, where the service flow bearer signaling includes the service flow information provided by the terminal and The IP address of the peer that the terminal performs communication; if it is determined that the terminal and the peer are located under the network device according to the IP address of the terminal and the IP address of the peer, the routing module 83 processes the service flow. The corresponding message performs a local routing operation.
  • the obtaining module 81 may further include: a first obtaining unit 811 and/or a second obtaining unit 812; wherein the first acquiring unit 811 acquires the terminal from the original serving gateway before the terminal switching in the terminal switching process The second obtaining unit 812 acquires the IP address of the terminal to the authenticator of the access network where the terminal is located in the terminal handover process.
  • the first obtaining unit 811 may further include: a first receiving subunit 8111, a first obtaining subunit 8112; wherein, the first receiving subunit 8111 receives a handover confirmation from the original serving gateway that carries the IP address of the terminal.
  • the first acquisition sub-unit 8112 obtains the IP address of the terminal from the handover confirmation message.
  • the second obtaining unit 812 may further include: a sending subunit 8121, a second receiving subunit 8122, and a second obtaining subunit 8123; wherein, the sending subunit 8121 sends an identifier to the authenticator to request to acquire the terminal. a context request message of the IP address; the second receiving subunit 8122 acquires an IP address of the terminal from the context response message carrying the IP address of the terminal; the second obtaining subunit 8123 carries the Obtaining the IP address of the terminal in a context response message of the IP address of the terminal.
  • the routing module 83 may further include: a sending unit 831, a routing unit 832; wherein, the sending unit 831 sends a path registration request message to the anchor gateway, instructing the anchor gateway to perform the service according to the path registration request message. Streaming for service authorization, and receiving the anchor gateway Returning a reply message for completing the service authorization; routing unit 832 routes the corresponding message from the terminal to the peer.
  • the network device determines that the terminal and the peer end are IP addresses of the network device according to the IP address of the terminal and the IP address of the peer end carried by the service flow bearer signaling, and the routing module 83 will be from the terminal.
  • the packet corresponding to the service flow is routed to the peer end. Since the packet corresponding to the service flow is routed to the HA through the network device and then transmitted to the core network, the packet corresponding to the service flow is reduced. The delay between transmissions between network elements reduces the core network transmission load.
  • FIG. 9 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention. As shown in FIG. 9, the embodiment of the present invention includes the following steps:
  • Step 901 The anchor gateway receives the service flow bearer signaling initiated by the serving gateway or the base station according to the service flow information provided by the terminal, and the peer end transmits the service flow, where the peer end is a terminal device that communicates with the terminal, and the service
  • the flow bearer signaling carries the IP address of the peer end;
  • Step 902 If the anchor gateway determines that the terminal and the peer end are located under the same local route execution device according to the IP address of the peer end and the IP address of the acquired terminal, the anchor gateway locally routes the service flow. Authorize, and notify the local route execution device to perform a local routing operation on the message corresponding to the service flow.
  • the actual network architecture of the local routing execution may be a base station or a serving gateway.
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the peer end are located under the same local route execution device, according to the IP address of the peer end and the IP address of the obtained terminal, the local route execution device is instructed to perform the service The packet corresponding to the flow performs a local routing operation. Since the packet corresponding to the service flow is routed to the HA through the anchor gateway and then transmitted to the external network, the packet corresponding to the service flow is reduced. The delay between transmissions between the elements reduces the core network transmission load.
  • the anchoring gateway performs local routing authorization on the service flow, which may be:
  • the anchoring gateway sends a resource request message to the authenticator, where the resource request message includes the terminal The requested service flow for establishing a bearer and an indication of local routing authorization for the service flow; the anchor gateway receiving a resource response message returned by the authenticator according to the indication of performing local routing authorization on the service flow,
  • the resource response message carries an authorization result that the authenticator authorizes the service flow, so that the local route execution device performs local routing on the service flow according to the authorization result.
  • the packet corresponding to the service flow initiated by the terminal is routed to the HA and then transmitted to the core network, thereby reducing the delay of the transmission between the network elements corresponding to the service flow, and reducing the delay.
  • the core network transmission load is reduced.
  • FIG. 10 is a signaling flow chart applicable to the embodiment shown in FIG.
  • the terminal when the terminal initiates a new service, the terminal initiates the service flow bearer signaling, and the service flow bearer signaling may be a new bearer, or may modify an existing bearer.
  • the embodiment For transmitting the service-related >3 ⁇ 4 text; as shown in FIG. 10, the embodiment includes the following steps:
  • Step 1001 The terminal sends a dynamic service increase request (DSA-REQ) message to the base station, instructing the base station to establish a new bearer.
  • DSA-REQ dynamic service increase request
  • the dynamic service increase request message carries the IP quintuple information of the service flow initiated by the terminal, where the IP quintuple information specifically includes the source IP address, the destination IP address, the source port number, the destination port number, and the destination port number of the service flow. agreement type;
  • Step 1002 The base station returns a dynamic service establishment response (DSA-RVD) message to the terminal, indicating that the dynamic service increase request (DSA-REQ) message is received;
  • DSA-RVD dynamic service establishment response
  • DSA-REQ dynamic service increase request
  • Step 1003 The base station sends a path registration request (Path_Reg_Req) message to the serving gateway, requesting to establish a new bearer, where the Path_Reg_Req message carries the IP quintuple information of the service flow;
  • Step 1004 The serving gateway sends the path registration request (Path_Reg_Req) message to the anchor gateway, where the path registration request (Path_Reg_Req) message carries the IP quintuple of the service flow.
  • Step 1005 The anchor gateway (Anchor GW) detects, according to the destination IP address in the IP quintuple information and the IP address of the terminal that the anchor gateway has acquired, whether the peer is also located in the serving gateway (Serving GW) of the sending request. If yes, it is judged that local routing can be performed at the serving gateway (Serving GW);
  • the anchoring gateway determines whether the local routing can be performed at the base station; the anchoring gateway (Anchor GW) needs to further obtain the bearer information of the peer end, and the bearer information is specific.
  • the device may be a bearer identifier, an IP quintuple, or the like, where the bearer identifier indicates that the base station performs local routing on the packet corresponding to the service flow on the designated service flow bearer;
  • Step 1006 The anchor gateway (Anchor GW) performs resource authorization on the dynamic service increase request by using an authenticator in the access network.
  • the anchor gateway can also authorize the local route; specifically, the anchor gateway sends a resource request message to the authenticator, where the resource request message includes the service flow of the bearer established by the terminal and the pair And the resource response message returned by the identifier according to the indication of the local authorization of the service flow, where the resource response message carries an authorization result that the authenticator authorizes the service flow.
  • Step 1007 The anchor gateway (Anchor GW) returns a Path Registration Response (Path_Reg_Rsp) message to the serving gateway, where the path registration response message carries a local route at the serving gateway or the base station (Serving GW/BS)
  • the indication information of the local route includes at least one of the following information: an indication of a local route, a service flow information for performing local routing, and bearer information of the peer end (for example: bearer identifier, IP quintuple information);
  • Step 1008 The serving gateway (Serving GW) returns the path registration response (Path_Reg_Rsp) message to the base station, where the path registration response message optionally carries the indication information for performing local routing.
  • the path registration response message optionally carries the indication information for performing local routing.
  • Step 1009 The base station returns a dynamic service increase request response (DSA-RSP) message to the terminal.
  • Step 1010 The terminal returns a dynamic service increase request acknowledgement (DSA-ACK) message to the base station.
  • Step 1011 The base station returns a path registration confirmation (Path_Reg_Ack) message to the serving gateway (Serving GW).
  • Step 1012 The serving gateway returns a path registration response (Path_Reg_Rsp) message to the anchor gateway, indicating that the loading is completed.
  • Step 1013 The anchor GW sends a resource reservation response (RR_Ack) message to the authenticator (Authenticator), indicating that the resource authorization is completed.
  • RR_Ack resource reservation response
  • Step 1014 The serving gateway performs local routing operation on the corresponding service flow on the bearer according to the indication information of the local routing of the anchor GW.
  • the base station performs a local routing operation on the corresponding service flow on the bearer according to the indication information of the local routing of the anchor gateway (Anchor GW).
  • the local routing implementation method provided by the embodiment of the present invention indicates that the terminal and the peer end are located under the same base station or serving gateway according to the IP address of the peer end carried by the service flow bearer signaling and the IP address of the acquired terminal.
  • the network device routes the report corresponding to the service flow from the terminal to the peer end, thereby avoiding that the packet corresponding to the service flow is routed to the HA through the anchor gateway, and then transmitted to the external network, thereby reducing
  • the delay of the transmission of packets corresponding to the service flow between the network elements reduces the transmission load of the core network.
  • FIG. 11 is a schematic structural diagram of still another embodiment of a network device according to the present invention. As shown in FIG. 11, the embodiment includes: a receiving module 111, an authorization module 112, and a notification module 113;
  • the receiving module 111 receives the service flow bearer signaling initiated by the terminal and forwarded by the original serving gateway, and the peer end is a terminal device that communicates with the terminal, and the service flow bearer signal
  • the command carries the IP address of the peer end; if it is determined that the terminal and the peer end are located under the same local route execution device according to the IP address of the peer end and the obtained IP address of the terminal, the authorization is performed.
  • the module 112 performs local routing authorization on the service flow, and the notification module 113 notifies the local routing execution device to locally route the packet corresponding to the service flow.
  • the actual network architecture of the local routing execution may be a base station or a serving gateway.
  • the network device provided by the embodiment of the present invention, if the terminal and the peer are located under the same local route execution device, according to the IP address of the peer and the IP address of the obtained terminal, the authorization module 112 locally authorizes the service flow.
  • the operation is performed to enable the local routing execution device to locally route the packet corresponding to the service flow, thereby reducing the service by avoiding that the packet corresponding to the service flow is routed to the HA through the anchor gateway and then transmitted to the external network.
  • the delay of the transmission of packets corresponding to the flow between the network elements reduces the transmission load of the core network.
  • the authorization module 112 may further include: a sending unit, a receiving unit, where the sending unit sends a resource request message to the authenticator, where the resource request message includes the And the receiving unit receives an indication of the service flow of the bearer and the local routing authorization of the service flow; the receiving unit receives the resource response message returned by the authenticator according to the indication of performing local routing authorization on the service flow,
  • the resource response message carries an authorization result that the authenticator authorizes the service flow, so that the local route execution device performs local routing on the service flow according to the authorization result.
  • FIG. 12 is a schematic flowchart of still another embodiment of a method for implementing local routing according to the present invention. As shown in FIG. 12, the embodiment of the present invention includes the following steps:
  • Step 121 Receive a service flow bearer signaling initiated by the serving gateway according to the service flow information provided by the terminal, and the peer end is a terminal device that communicates with the terminal, where the service flow bearer signaling carries The IP address of the peer;
  • Step 122 If the terminal and the peer are located under the serving gateway according to the IP address of the peer and the IP address of the obtained terminal, send a local routing indication to the serving gateway, so that the serving gateway determines whether the service can be performed according to the local routing indication.
  • the packets corresponding to the flow are locally routed by the base station under the serving gateway.
  • the local routing implementation method provided by the embodiment of the present invention if the terminal and the peer end are located under the service gateway according to the IP address of the peer end and the IP address of the obtained terminal, send a local route indication to the serving gateway, which is avoided by The anchor gateway routes the packet corresponding to the service flow to the HA After being transmitted to the external network, the delay of the transmission of the message corresponding to the service flow between the network elements is reduced, and the transmission load of the core network is reduced.
  • the method may further include:
  • the serving gateway determines that the base station can perform a local routing indication according to the local routing indication, the serving gateway instructs the base station to perform a local routing operation on a message corresponding to the service flow.
  • FIG. 13 is a signaling flowchart applicable to the embodiment shown in FIG. 12.
  • the terminal when a terminal initiates a new service, the terminal initiates service flow bearer signaling, and the service flow bearer signaling may be specifically established.
  • the new bearer may also be configured to modify an existing bearer, and the service flow bearer is used to transmit the related information of the service.
  • the embodiment includes the following steps:
  • Step 1301 The terminal base station sends a dynamic service increase request (DSA-REQ) message, instructing the base station to establish a new bearer; and the dynamic service increase request message carries the IP quintuple information of the service flow;
  • DSA-REQ dynamic service increase request
  • Step 1302 The base station returns a dynamic service establishment response (DSA-RVD) message to the terminal, indicating that the dynamic service increase request (DSA-REQ) message is received;
  • DSA-RVD dynamic service establishment response
  • DSA-REQ dynamic service increase request
  • Step 1303 The base station sends a path registration request (Path_Reg_Req) message to the serving gateway to request to establish a new bearer.
  • the path registration request message carries the IP quintuple information of the service flow, and the IP quintuple The information includes the source IP address, destination IP address, source port number, destination port number, and protocol type of the service flow.
  • Step 1304 The serving gateway sends a path registration request (Path_Reg_Req) message to the anchor gateway, where the path registration request (Path_Reg_Req) message carries the IP quintuple information of the service flow;
  • Step 1305 The anchor gateway (Anchor GW) detects, according to the destination IP address in the IP quintuple information and the IP address of the terminal that the anchor gateway has acquired, whether the peer is also located in the serving gateway (Serving GW) of the sending request. Next; if yes, local routing can be performed at the Serving GW; Step 1306: The anchor gateway performs resource authorization on the path registration request message. In addition, the anchor gateway may also authorize the local route.
  • Step 1307 The anchor gateway returns a Path Registration Response (Path_Reg_Rsp) message to the serving gateway, where the Path Registration Response (Path_Reg_Rsp) message carries indication information for performing local routing, where the local routing is performed.
  • the indication information may include at least one of the following: a local route indication, service flow information for performing local routing, a peer identifier, and bearer information of the peer end (for example: bearer identifier, IP quintuple information);
  • Step 1308 The serving gateway detects, according to the destination IP address in the IP quintuple information, whether the peer end communicating with the terminal is located under the same base station, and if yes, performing local routing at the base station, and continuing to step 1309; if not, The serving gateway performs the local routing, and performs step 1313.
  • the serving gateway may also map the bearer identifier corresponding to the peer end at the base station, and indicate that the local route is performed on the service flow bearer specified by the target base station by using the bearer identifier.
  • Step 1309 The serving gateway returns a path registration response (Path_Reg_Rsp) message to the base station, where the path registration response (Path_Reg_Rsp) message carries indication information for performing local routing;
  • Step 1310 The base station returns a dynamic service increase response (DSA-RSP) message to the terminal.
  • Step 1311 The terminal sends a dynamic service increase acknowledgement (DSA-ACK) message to the base station.
  • Step 1312 The base station returns a path registration confirmation to the service gateway (Path— Reg-Ack) message;
  • Step 1313 The Serving GW returns a Path Registration Response (Path_Reg_Rsp) message to the Anchor GW to indicate that the anchor gateway bearer setup is complete;
  • Step 1314 The anchor GW sends a resource reservation response (RR_Ack) message to the authenticator (Authenticator), indicating that the resource authorization is completed.
  • RR_Ack resource reservation response
  • Step 1315 The serving gateway or the base station (Serving GW/BS) performs a local routing operation on the bearer corresponding to the corresponding service flow according to the indication information of the local route sent by the anchor GW.
  • the local route implementation method provided by the embodiment of the present invention is carried according to the service flow bearer signaling.
  • the IP address of the peer end and the IP address of the acquired terminal determine that the terminal and the peer end are the same service gateway or the IP address under the base station, and the anchor gateway instructs the target service gateway to correspond to the service flow from the terminal.
  • FIG. 14 is a schematic structural diagram of an embodiment of a local routing implementation system according to the present invention. As shown in FIG. 14, the embodiment includes: an anchor gateway 141, a serving gateway 142, and a base station 143;
  • the anchor gateway 141 receives the service flow bearer signaling initiated by the serving gateway 142 according to the service flow information provided by the terminal, and the peer end is the terminal device that communicates with the terminal,
  • the service flow bearer signaling carries the IP address of the peer end;
  • the anchor gateway 141 determines that the terminal and the peer are located under the serving gateway 142 according to the IP address of the peer and the obtained IP address of the terminal, sending a local routing indication to the serving gateway 142, so that the serving gateway is enabled.
  • the 142 determines, according to the local routing indication, whether the packet corresponding to the service flow can be localized by the base station 143 under the serving gateway 142.
  • the local routing implementation system determines that the terminal and the peer end are the serving gateway 142 according to the IP address of the peer end carried by the service flow bearer signaling and the IP address of the acquired terminal, and the anchor gateway 141
  • the service gateway 142 sends a local route indication, and the packet corresponding to the service flow is reduced between the network elements by avoiding the routing of the traffic corresponding to the service flow to the HA through the network device.
  • the delay of transmission reduces the transmission load of the core network.
  • the serving gateway 142 determines that the base station 143 can perform the local routing indication according to the local routing indication, the serving gateway 142 instructs the base station 143 to correspond to the service flow. The message is locally routed. If the serving gateway 142 determines that the serving gateway 142 performs local routing according to the local routing indication, the serving gateway 142 performs local routing on the packet corresponding to the service flow.
  • IPv4 protocol protocol is the IPv4 protocol address.
  • IPv6 protocol address is the IPv6 protocol address or network prefix.
  • IPv6 protocol address does not form a limitation on the embodiment of the present invention.
  • IP address specified in the various protocols that can implement the local routing in the embodiment of the present invention is the IP address described in the embodiment of the present invention.
  • the message transmission path is output from the target service gateway, the anchor gateway, and the HA to the core network, so The transmission path overlap occurs between the service gateway, the anchor gateway, and the HA, that is, the packet between the terminal and the peer still needs to be transmitted from the target service gateway to the HA first, and then returned to the target service gateway via the HA and sent. Give the opposite end.
  • the destination is sent to the peer end, thereby reducing the delay of transmission of the message between the network elements and reducing the load of the core network transmission; or, when the terminal and the opposite end of the communication are located under the same target base station
  • the message transmission path is output from the target base station, the target service gateway, the anchor gateway, and the HA to the core network. Therefore, the transmission path overlap occurs between the target base station, the target service gateway, the anchor gateway, and the HA, that is, the terminal and the pair
  • the message between the ends still needs to be transmitted from the target base station to the HA first, and then returned to the target base station via the HA and sent to the opposite end.
  • the target base station may also use the local routing technology to send the packets sent by the terminal to the peer end, and then reduce the delay of the transmission between the network elements and reduce the transmission of the core network. load.
  • the foregoing embodiment of the present invention is exemplified by the WiMAX network as an example.
  • the WiMAX does not limit the embodiment of the present invention, and the local route is triggered according to the IP address of the terminal and the IP address of the peer communicating with the terminal, thereby reducing
  • the delays of the transmission of the packets between the network elements are all applicable to the network system described in the embodiments of the present invention.
  • the foregoing program may be stored in a computer readable storage medium, and when executed, the program includes The foregoing steps of the method embodiment; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

Landscapes

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

Description

本地路由实现方法及***、 网络设备
技术领域
本发明实施例涉及通信技术领域，尤其是一种本地路由实现方法及***、 网络设备。 背景技术
移动通信网络正致力于为用户提供更高的分组传输能力， 以满足移动用 户对快速增长的数据业务的需求。 基于 IEEE802.16无线接入技术的移动微波 接入全球互通 ( Worldwide Interoperability for Microwave Access , 简 称 ： WiMAX )网络， 能够为用户提供高速的数据传输能力， 因此受到了广泛的关 注。
在移动 WiMAX网络中， 当终端与外部网络通信时， 终端发送的上行才艮 文， 经过基站（ Base Station, 简称： BS )传递到服务网关 （ Serving GW ) , 再传递到锚定网关（ Anchor GW ) , 最后经过家乡代理（ Home Agent, 简称： HA )传送到外部网络中； 下行报文则从外部网络经过反方向的承载路径路由 至终端。 当终端用户的通信对端为另一个移动终端时， 如果两个终端位于同 一个服务网关（Serving GW ) 下， 两个终端之间的报文仍然需要首先从服务 网关（ Serving GW M专输到 HA ,然后再从 HA返回给该服务网关（ Serving GW ) 并发送给目标终端， 因此，两个终端之间的报文传输路径从服务网关 ( Serving GW )到 HA之间发生了重叠。
为了解决上述路径重叠问题， 在现有的 3GPP网络中， 终端在与 MSC建 立呼叫时， MSC将终端携带的呼叫对端的综合业务数字网（ Integrated Services Digital Network, 简称: ISDN ) 电话号码映射到对端的国际移动用户识别码 ( international mobile subscriber identity, 简称： IMSI ) , 然后才艮据记录的终 端上下文， 判断呼叫对端所在基站子***（Base Station Subsystem, 简称： BSS )是否与主叫终端所在的 BSS相同， 如果相同则通知 BSS在两者之间进 行语音的本地交换。
发明人在实施本发明的过程中发现， 位于 WiMAX网络中的终端在发起 业务时， 服务网关设备并不能够根据终端的 MSID判断对端是否位于该网关 设备下的本地网络， 因此现有技术中的本地触发技术并不能应用于 WiMAX 网络中进行本地路由触发。 发明内容
本发明实施例的目的在于提供一种本地路由实现方法及***、网络设备， 减少报文传输时延， 降低核心网传输负载。
本发明实施例提供一种本地路由实现方法， 包括：
在终端切换的过程中获取所述终端的因特网协议 IP地址；
接收业务流承载信令， 所述业务流承载信令中包括所述终端提供的业务 流信息以及与所述终端进行通信的对端的 IP地址；
若根据所述终端的 IP地址与所述对端的 IP地址判断所述终端与所述对 端位于同一个本地路由执行设备下， 则对所述业务流相对应的 4艮文执行本地 路由操作。
本发明实施例提供一种网络设备， 包括：
获取模块，用于在终端切换的过程中获取所述终端的因特网协议 IP地址； 接收模块， 用于接收业务流承载信令， 所述业务流承载信令中包括所述 终端提供的业务流信息以及与所述终端进行通信的对端的 IP地址；
路由模块， 用于若根据所述终端的 IP地址与所述对端的 IP地址判断所 述终端与所述对端位于该网络设备下， 则对所述业务流相对应的报文执行本 地路由操作。 本发明实施例提供一种本地路由实现方法， 包括：
锚定网关接收由服务网关或基站根据终端提供的业务流信息发起的与对 端传输该业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端 设备， 所述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于同一个本地路由执行设备下， 则所述锚定网 关对所述业务流进行本地路由授权， 并通知该本地路由执行设备对所述业务 流相对应的报文执行本地路由。
本发明实施例提供一种网络设备， 包括：
接收模块， 用于接收由终端发起的通过原服务网关转发的与对端传输业 务流的业务流承载信令， 所述对端为与所述终端进行通信的终端设备， 所述 业务流承载信令中携带有所述对端的 IP地址；
授权模块， 用于若根据所述对端的 IP地址与已获取到的所述终端的 IP 地址判断所述终端与所述对端位于该网络设备下， 则对所述业务流进行本地 路由授权；
通知模块， 用于通知该网络设备对所述业务流相对应的报文进行本地路 由。
本发明实施例提供一种本地路由实现方法， 包括：
锚定网关接收由服务网关根据终端提供的业务流信息发起的与对端传输 业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端设备， 所 述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于该服务网关下， 向所述服务网关发送本地路 由指示， 使所述服务网关根据所述本地路由指示判断是否可以对所述业务流 相对应的报文在所述服务网关下的基站进行本地路由。
本发明实施例提供一种本地路由实现***， 包括： 锚定网关、 服务网关、 基站；
所述锚定网关接收由所述服务网关根据终端提供的业务流信息发起的与 对端传输业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端 设备， 所述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于所述服务网关下， 向所述服务网关发送本地 路由指示， 使所述服务网关根据所述本地路由指示判断是否可以对所述业务 流相对应的报文在所述服务网关下的所述基站进行本地路由。
本发明实施例提供的本地路由实现方法及***、 网络设备， 若根据终端 的 IP地址与对端的 IP地址判断出终端与对端位于同一个本地路由执行设备 下， 则对业务流相对应的报文执行本地路由操作， 实现了将业务流相对应的 才艮文通过本地路由传输至该对端， 由于避免了通过本地路由执行设备将该业 务流相对应的报文路由至 HA后再传送至外部网络， 因此减少了业务流相对 应的报文在网元之间传输的时延， 降低了核心网传输负载。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例所适用的网络***架构图；
图 2为本发明本地路由实现方法一个实施例的流程示意图；
图 3为本发明本地路由实现方法又一个实施例的流程示意图；
图 4为图 3所示实施例所适用的信令流程图；
图 5为本发明本地路由实现方法另一个实施例的流程示意图；
图 6为图 5所示实施例所适用的信令流程图； 图 Ί为本发明网络设备一个实施例的结构示意图；
图 8为本发明网络设备又一个实施例的结构示意图；
图 9为本发明本地路由实现方法再一个实施例的流程示意图；
图 10为图 9所示实施例所适用的信令流程图；
图 11为本发明网络设备再一个实施例的结构示意图；
图 12为本发明本地路由实现方法还一个实施例的流程示意图;
图 13为图 12所示实施例所适用的信令流程图；
图 14为本发明本地路由实现***实施例的结构示意图。 具体实施方式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
图 1为本发明实施例所适用的网络***架构图， 如图 1所示， 在终端从 原基站 11切换到目标基站 17前， 终端通过原基站 11、 原服务网关 12将报 文发送给锚定网关 13 , 锚定网关 13再将报文发送至 HA14, 通过 HA14传送 至外部网络 15, 从而实现终端与外部网络的信息交换； 在终端从原基站 11 切换到目标基站 17后， 终端通过目标基站 17、 目标服务网关 16将报文发送 给锚定网关 13 , 锚定网关 13再将报文发送至 HA14, 通过 HA14传送至外部 网络 15 , 从而实现终端与外部网络的信息交换。 本发明实施例中， 锚定网关 13为终端在切换时 ^艮文传输路径的锚定点， 该锚定点在终端初始接入网络时 能够获取终端的 IP地址； 原服务网关 12为终端切换前与原基站 11相对应的 服务网关， 目标服务网关 16为终端切换后的与目标基站 17相对应的服务网 关； 进一步地， 若终端在原基站 11下初始接入网络， 则原服务网关 12与锚 定网关 13可以为同一个网关设备。图 1所示的***架构仅为一个示例性说明 并不能构成对本发明实施例所适用场景的限制。
图 2为本发明本地路由实现方法一个实施例的流程示意图，如图 2所示， 本实施例包括如下步骤：
步骤 201、 在终端切换的过程中获取终端的 IP地址；
步骤 202、 接收业务流承载信令， 其中， 业务流承载信令中包括终端提 供的业务流信息以及与终端进行通信的对端的 IP地址；
其中， 业务流承载信令可以由终端发起， 也可以由基站根据终端提供的 业务流信息发起。
步骤 203、若根据该终端的 IP地址与该对端的 IP地址判断该终端与该对 端位于同一个本地路由执行设备下， 则对该业务流相对应的报文执行本地路 由操作。
其中，本地路由执行设^据实际的网络架构可以为基站或者服务网关。 本发明实施例提供的本地路由实现方法， 若根据终端的 IP地址与对端的 IP地址判断出终端与对端位于同一个本地路由执行设备下， 则对该业务流相 对应的 4艮文执行本地路由操作， 实现了将业务流相对应的 ^艮文通过本地路由 传输至该对端， 由于避免了通过本地路由执行设备将该业务流相对应的报文 路由至 HA后再传送至外部网络， 因此减少了业务流相对应的报文在网元之 间传输的时延， 降低了核心网传输负载。
图 3为本发明本地路由实现方法又一个实施例的流程示意图， 本实施例 以在终端切换过程中向终端切换前的原服务网关获取该终端的 IP地址为例进 行示例性说明， 其中， 执行本发明实施例的网络设备具体可以为终端切换后 的服务网关（ Serving ASN-GW )或基站； 如图 3所示， 并结合图 1所示的系 统架构图进行说明， 本实施例包括如下步骤：
步骤 301、接收来自原服务网关的携带有终端的 IP地址的切换确认消息； 其中， 来自原服务网关的携带有终端的 IP地址的切换确认消息可以是原 基站在接收到终端发送的切换指示消息后转发给原服务网关的， 原基站接收 到的来自终端的切换指示消息具体可以为 MOB— HO— IND消息， 原基站根据 该切换指示消息向原目标服务网关发送携带有该终端的 IP地址的切换确认消 息， 进一步地， 携带有该终端的 IP地址的切换确认消息具体可以为 HO—Cnf 消息； 在具体实现时， 若执行本发明实施例的主体为终端切换后的目标基站， 则原服务网关将携带有终端的 IP 地址的切换确认消息发送给目标服务网关 后， 目标服务网关还需要将该携带有终端的 IP地址的切换确认消息转发给该 目标基站， 若执行本发明实施例的主体为终端切换后的目标服务网关， 则在 目标服务网关可以根据实际需要确定是否向目标基站转发给切换确认消息， 若目标服务网关向目标基站转发该切换确认消息， 则目标服务网关还可以根 据实际情况确定是否需要将终端的 IP地址携带在该切换确认消息中。
步骤 302、 从该切换确认消息中获取该终端的 IP地址；
其中， 由于携带有终端的 IP地址的切换确认消息中携带有该终端的 IP 地址， 因此不论执行本发明实施例的主体为目标服务网关还是目标基站， 均 可以通过该携带有终端的 IP地址的切换确认消息获取到终端的 IP地址。
步骤 303、 接收由该终端发起的与对端传输业务流的业务流承载信令， 其中， 对端为与该终端进行通信的终端设备， 该业务流承载信令中携带有该 对端的 IP地址；
其中， 业务流承载信令可以由终端发起， 也可以由基站根据终端提供的 业务流信息发起， 若执行本发明实施例的主体为目标基站， 则业务流承载信 令可以由终端发起并发送给该目标基站， 若执行本发明实施例的主体为目标 服务网关， 则可以由目标基站根据终端提供的业务流信息发起并发送给目标 服务网关； 进一步地， 在终端从原基站切换至目标基站后， 通过该业务流承 载信令可以实现目标基站与目标服务网关之间建立新的承载或者修改现有的 承载， 从而通过目标基站、 目标服务网关向对端传输该终端发起的业务流； 例如： 终端发送动态业务增加请求（DSA-REQ ) 消息以新建一个新的承载， 或者， 终端发送动态业务修改请求（DSC-REQ ) 消息以修改现有的承载， 通 过新的承载或者修改后的承载， 从而实现传输该终端发起的业务流。
步骤 304、若根据终端的 IP地址与对端的 IP地址判断该终端与该对端位 于同一个本地路由执行设备下， 向锚定网关发送路径注册请求消息， 指示锚 定网关根据该路径注册请求消息对该业务流进行业务授权；
其中， 若该本地路由执行设备为本发明实施例的执行主体， 具体可以为 目标基站或者目标服务网关； 若执行主体为目标基站， 则目标基站通过目标 服务网关向锚定网关发送路径注册请求消息， 若执行主体为目标服务网关， 则目标服务网关直接向锚定网关发送路径注册请求消息； 该路径注册请求 ( Path— Reg— Req ) 消息可以携带有进行本地路由的指示信息， 指示锚定网关 对该业务流进行业务授权。
步骤 305、 接收该锚定网关返回的完成业务授权的应答消息；
其中， 若执行本发明实施例的主体为目标基站， 则目标基站通过目标服 务网关接收来自锚定网关返回的完成业务授权的应答消息， 若执行本发明实 施例的主体为目标服务网关， 则目标服务网关直接接收锚定网关返回的完成 业务授权的应答消息；
步骤 306、 根据该完成业务授权的应答消息将该业务流相对应的报文路 由至该对端；
上述步骤 304 ~步骤 306中， 由于该对端的 IP地址也位于同一个本地路 由执行设备下， 将终端发起的业务流相对应的^艮文根据对端的 IP地址通过该 本地路由执行设备路由至该对端， 从而实现了业务流相对应的报文的本地路 由。
本发明实施例提供的本地路由实现方法， 若根据该终端的 IP地址与该对 端的 IP地址判断出终端与对端位于同一个目标服务网关或者目标基站下， 则 目标服务网关或者目标基站将该业务流相对应的报文进行本地路由， 实现了 将业务流相对应的报文通过本地路由传输至该对端， 由于避免了通过目标服 务网关或者目标基站将该业务流相对应的报文路由至 HA后再传送至外部网 络， 因此减少了业务流相对应的报文在网元之间传输的时延， 降低了核心网 传输负载。
在上述图 3所示实施例的步骤 301和步骤 302还可以替换地为： 在终端 切换过程中向终端所在的接入网络的鉴权器获取终端的 IP地址， 具体可以通 过如下过程获取终端的 IP地址：
向鉴权器发送用于请求获取终端的 IP地址的上下文请求消息；
接收鉴权器根据上下文请求消息返回的携带有所述终端的 IP地址的上下 文响应消息；
从携带有该终端的 IP地址的上下文响应消息中获取所述终端的 IP地址。 具体地， 若执行主体为目标服务网关， 则上述获取终端的 IP地址的过程 具体可以为：
目标服务网关向鉴权器发送用于请求获取所述终端的 IP地址的上下文请 求消息；
目标服务网关接收所述鉴权器根据所述上下文请求消息返回的携带有所 述终端的 IP地址的上下文响应消息；
目标服务网关从所述携带有所述终端的 IP地址的上下文响应消息中获取 所述终端的 IP地址。
可替换地， 若执行主体为目标基站， 则上述获取终端的 IP地址的过程具 体可以为：
目标基站通过目标服务网关向鉴权器发送用于请求获取所述终端的 IP地 址的上下文请求消息；
目标基站通过所述目标服务网关接收所述鉴权器根据所述上下文请求消 息返回的携带有所述终端的 IP地址的上下文响应消息；
目标基站通过所述目标服务网关从所述携带有所述终端的 IP地址的上下 文响应消息中获取所述终端的 IP地址。
为了更清楚的理解图 3所示实施例的技术方案， 下面结合图 4所示的信 令流程图进行示例性说明； 图 4为图 3所示实施例所适用的信令流程图， 本 实施例中， 目标服务网关（ Serving ASN-GW )在终端切换过程中向终端切换 前的原服务网关获取该终端的 IP地址，原服务网关为终端切换前的服务网关， 目标服务网关为终端切换后的服务网关， 锚定网关 （Anchor GW )将来自服 务网关的业务流通过 HA传输至外部网络； 如图 4所示， 本实施例包括如下 步骤：
步骤 401、 终端向原基站发送切换指示消息， 该切换指示消息用于指示 原基站该终端要将承载业务切换到目标基站 （New BS ) ；
其中， 切换指示消息具体可以为终端切换指示 （MOB— HO— IND ) 消息。 步骤 402、 原基站向目标基站发送切换确认（HO— Cnf) 消息， 确认终端 将从原基站切换到目标基站； 具体地， 原服务基站 （Old Serving GW )通过 原服务网关及目标服务网关 （ New Serving GW ) 向终端切换后的目标基站发 送该切换确认消息 （HO— Cnf ) , 原基站或原服务网关将终端的 IP地址包含 在该切换确认消息中； 目标服务网关 （ Serving GW )或目标基站通过该切换 确认消息 ( HO— Cnf )获取该终端的 IP地址；
步骤 403、 目标基站向原基站（ Old BS )返回切换响应（ HO_Ack )消息， 其中，切换响应消息可以经由目标服务网关（ Serving GW )和原服务网关（ Old Serving GW )转发给原基站；
步骤 404、 目标基站从鉴权器（ Authenticator )获取该终端的上下文消息 ( Context retrieval ) ；
其中， 该上下文消息具体可以为安全密钥（Key )等， 并且该上下文消息 可以通过目标服务网关（ Serving GW )转发给目标基站；
步骤 405、 终端在目标基站下重新进入网络；
步骤 406、 目标基站通过目标服务网关与锚定网关建立承载， 用于传输 终端当前发起的业务流；
其中， 通过在目标基站、 目标服务网关、 锚定网关之间建立承载， 使终 端发起的业务流相对应的报文通过锚定网关转发给外部网络。
步骤 407、 目标基站向鉴权器（ Authenticator )更新用于空口鉴权的基于 密文的消息认证码 ( Cipher-based Message Authentication Code ,简称： CMAC ) 密钥 （Key ) ；
步骤 408、 目标基站向原基站发送切换完成（ HO— Complete )消息， 指示 原基站切换完成； 其中， 该切换完成消息可以通过目标服务网关、 原服务网 关转发给原基站；
步骤 409、 原基站向目标基站返回切换应答（HO— Ack )消息， 并清除终 端在原基站的上下文消息， 该上下文消息具体可以为： 用户密钥、 承载信息 等； 其中， 该切换应答消息可以通过原服务网关、 目标服务网关转发给目标 基站；
通过上述步骤 401〜步骤 409, 即可实现原基站到目标基站的切换， 并使 目标服务网关或者目标基站获取到终端的 IP地址；当终端发起新的业务流时， 终端通过发起业务流承载信令可以建立一个新的承载或者修改一个现有的承 载， 实现传输与该业务流相关的报文； 具体地， 该业务流承载信令对于不同 的网元可以为不同消息， 对于终端来说， 该业务流承载信令可以为动态业务 增加请求（DSA-REQ ) 消息， 用于建立一个新的承载， 也可以为动态业务修 改请求（DSC-REQ ) 消息， 用于修改一个现有的承载。 具体地， 对于基站或 服务网关来说， 该业务流承载信令可以为路径注册请求（ Path— Reg— req )消息 或路径修改请求（ Path— Mod— req ) 消息， 上述消息同样适用于本发明的其它 实施例。 下面以建立新的承载为例通过步骤 410 ~步骤 416进行示例性说明。
步骤 410、 终端向目标基站发送动态业务增加请求（DSA-REQ ) 消息， 指示目标基站建立新的承载； 其中， 在该 DSA-REQ消息中携带有该业务流 的 IP五元组信息 （Packet classification rule ) , 该 IP五元组信息具体包括了 业务流的源 IP地址、 目的 IP地址、 源端口号、 目的端口号、 协议类型；
步骤 411、 目标基站向终端返回动态业务建立应答 ( DSX-RVD ) 消息， 表示接收到该动态业务增加请求 ( DSA-REQ ) 消息；
步骤 412、 目标基站向目标服务网关发送路径注册请求（ Path— Reg— Req ) 消息， 用于请求建立新的承载， 其中， 该路径注册请求消息中携带有业务流 的 IP五元组信息；
步骤 413、 若目标服务网关 ( Serving GW )根据业务流的 IP五元组信息 中的目的 IP地址和该终端的 IP地址判断出该业务流的对端位于该目标月良务 网关下， 则确定可以将该业务流相对应的 文通过本地路由传输至对端； 步骤 414、 目标服务网关向锚定网关发送路径注册请求 ( Path— Reg— Req ) 消息， 其中， 该路径注册请求消息中携带有进行本地路由的指示信息；
步骤 415、 目标服务网关对步骤 410 中终端指示目标基站进行的该新的 承载进行资源授权， 使得锚定网关可以根据步骤 414中获取到的进行本地路 由的指示信息对本地路由进行授权； 进一步地， 目标服务网关可以通过向接 入网络中的鉴权器发送授权请求实现本地路由授权； 锚定网关通过目标服务 网关向目标基站返回应答消息， 实现建立该新的承载；
步骤 416、 目标服务网关在该新的承载上将业务流相对应的报文通过本 地路由传输至对端。
本发明实施例提供的本地路由实现方法， 若根据终端的 IP地址与业务流 承载信令携带的对端的 IP地址判断出终端与对端位于目标服务网关下， 则目 标服务网关将来自该终端的业务流相对应的报文通过执行本地路由操作传输 至该对端， 由于避免了通过锚定网关将该业务流相对应的 ^艮文路由至 HA后 再传送至外部网络， 因此减少了业务流相对应的报文在网元之间传输的时延， 降低了核心网传输负载。
上述流程以目标服务网关执行本地路由为例进行示例性说明， 若为目标 基站执行本地路由， 目标基站通过切换确认消息获取到该终端的 IP地址， 若 才艮据业务流的 IP五元组信息中的目的 IP地址和该终端的 IP地址判断出该业 务流的对端位于该目标基站下， 则确定可以将该业务流通过本地路由传输至 对端， 对于目标基站与鉴权器等网元设备的交互， 可以参考前述目标服务网 关与鉴权器的交互， 在此不再贅述。
图 5为本发明本地路由实现方法另一个实施例的流程示意图， 本实施例 以在终端切换过程中向终端所在的接入网络的鉴权器获取终端的 IP地址为例 进行示例性说明， 其中， 执行本发明实施例的网络设备具体可以为终端切换 后的服务网关（ Serving ASN-GW )或者终端切换后的基站； 本发明实施例以 基站为例进行示例性说明， 如图 5所示， 本发明实施例包括如下步骤：
步骤 501、 切换后的目标基站向鉴权器发送用于请求获取终端的 IP地址 的上下文请求消息；该上下文请求消息可以通过目标服务网关转发给鉴权器； 其中， 该上下文请求消息具体可以为 Context— Req消息；
步骤 502、 目标基站接收该鉴权器根据该上下文请求消息返回的携带有 该终端的 IP地址的上下文响应消息； 该上下文响应消息可以通过目标 Λ良务网 关转发给鉴权器；
其中， 上下文响应消息具体可以为 Context— Rsp消息。
步骤 503、 目标基站接收由该终端发起的与对端传输业务流的业务流承 载信令， 其中， 对端为与终端进行通信的终端设备， 业务流承载信令中携带 有对端的 IP地址；
其中， 在终端从原基站切换至目标基站后， 通过该业务流承载信令可以 实现目标基站与目标服务网关之间建立新的承载或者修改现有的承载， 从而 通过目标基站、 目标 Λ良务网关向对端传输该终端发起的业务流； 例如： 终端 发送动态业务增加请求（DSA-REQ ) 消息以新建一个新的承载， 或者， 终端 发送动态业务修改请求（DSC-REQ ) 消息以修改现有的承载， 通过新的承载 或者修改后的承载， 从而实现传输该终端发起的业务流。
步骤 504、若目标基站根据终端的 IP地址与对端的 IP地址判断该终端与 该对端位于该目标基站下， 目标基站向锚定网关发送进行本地路由的指示信 息； 其中， 该进行本地路由的指示信息可以携带在路径修改请求
( Path— Mod— Req ) 消息中； 可选地， 锚定网关根据该进行本地路由的指示信 息对业务流进行业务授权。
步骤 505、 目标基站接收锚定网关根据该进行本地路由的指示信息返回 的应答消息；
步骤 506、 目标基站根据应答消息将来自终端的业务流相对应的报文路 由至对端。
上述步骤 504 ~步骤 506中， 由于该对端的 IP地址也位于该目标服务网 关下， 目标服务网关将终端发起的业务流根据对端的 IP地址通过该目标服务 网关路由至该对端，从而实现了目标基站对业务流相对应的报文的本地路由。
本发明实施例提供的本地路由实现方法， 若目标基站据终端的 IP地址与 业务流承载信令携带的对端的 IP地址确定终端与对端为目标基站下的 IP地 址， 则将来自该终端的业务流相对应的报文本地路由至该对端， 由于避免了 通过锚定网关将该业务流相对应的 4艮文路由至 HA后再传送至核心网， 因此 减少了业务流相对应的报文在网元之间传输的时延，降低了核心网传输负载。
为了更清楚的理解图 5所示实施例的技术方案， 下面结合图 6所示的信 令流程图进行示例性说明； 图 6为图 5所示实施例所适用的信令流程图， 本 实施例以目标基站（Target BS )在终端切换过程中向终端切换前的基站获取 该终端的 IP地址， 本实施例中， 原基站为终端切换前的基站， 目标基站为终 端切换后的基站， 锚定网关（ Anchor GW )将来自目标基站的业务流通过 HA 传输至核心网； 如图 6所示， 本实施例包括如下步骤：
步骤 601、 终端向原基站发送切换指示消息， 该切换指示消息用于指示 原基站该终端要将承载业务切换到目标基站 （ Target BS ) ；
其中， 切换指示消息具体可以为终端切换指示 （MOB— HO— IND ) 消息。 步骤 602、 原基站向目标基站发送切换确认（HO— Cnf) 消息， 确认终端 将从原基站切换到目标基站； 目标基站向原基站返回切换响应（ HO Ack )消 息；
其中， 该切换确认消息可以通过原服务网关、 目标服务网关发送给目标 基站； 该切换响应消息可以通过目标服务网关、 原服务网关转发送给终端； 步骤 603、 目标基站向目标服务网关发送上下文请求（ Context— Req ) 消 息， 用于向接入网络中的鉴权器请求获取该终端的上下文信息； 该上下文请 求消息可选地携带有用于获取终端的 IP地址的指示信息， 通过目标服务网关 ( Serving GW )转发给该鉴权器（ Authenticator ) ；
步骤 604、 鉴权器通过目标服务网关向目标基站返回上下文响应 ( Context— Rsp )消息， 其中， 该上下文响应消息携带有终端的 IP地址， 目标 服务网关转发 IP地址给目标基站； 通过该上下文响应消息， 目标服务网关和 目标基站均可获取到该终端的 IP地址；
步骤 605、 终端在目标基站下重新进入网络；
步骤 606、 目标基站通过目标服务网关与锚定网关建立承载， 用于传输 终端当前发起的业务流；
其中， 通过在目标基站、 目标服务网关、 锚定网关之间建立承载， 使终 端发起的业务流通过锚定网关转发给核心网。
步骤 607、目标基站向鉴权器（ Authenticator )更新用于空口鉴权的 CMAC 密钥 （Key )信息；
步骤 608、 目标基站向原基站发送切换完成（HO— Complete )消息， 指示 原基站切换完成； 其中， 该切换完成消息可以通过目标服务网关、 原服务网 关转发给原基站；
步骤 609、 原基站向目标基站返回切换应答（HO— Ack )消息， 并清除终 端在原基站的上下文消息； 其中， 该切换应答消息可以通过原服务网关、 目 标服务网关转发给目标基站； 通过该上下文消息存储了用户密钥、 承载信息 等。
通过上述步骤 601〜步骤 609, 即可实现原基站到目标基站的切换， 并使 目标服务网关或者目标基站获取到终端的 IP地址；当终端发起新的业务流时， 终端通过发起业务流承载信令可以建立一个新的承载或者修改一个现有的承 载， 实现传输与该业务流相关的报文； 具体地， 该业务流承载信令具体可以 为动态业务增加请求（DSA-REQ ) 消息， 用于建立一个新的承载， 也可以为 动态业务修改请求（DSC-REQ ) , 用于修改一个现有的承载， 由于通过建立 新的承载已经在图 4所示实施例中进行示例性说明， 下面通过步骤 610 ~步 骤 616以修改一个现有的承载为例进行示例性说明。
步骤 610、 终端向目标基站发送动态业务修改请求（DSC-REQ ) 消息， 指示目标基站修改现有的承载， 以重用该现有的承载传输新的业务流；
其中， 在该动态业务修改请求消息中携带有该业务流的 IP五元组信息； 该 IP五元组信息具体包括了业务流的源 IP地址、 目的 IP地址、 源端口号、 目的端口号、 协议类型。
步骤 611、 目标基站向终端返回动态业务修改响应 （DSX-RVD ) 消息， 表示接收到该动态业务修改请求（ DSC-REQ ) 消息；
步骤 612、 目标基站根据业务流中的 IP五元组中的目的 IP地址以及该终 端的 IP地址判断出该业务流的对端位于该目标基站下；
步骤 613、 目标基站向目标服务网关发送路径修改请求（ Path— Mod— Req ) 消息， 用于请求修改现有的承载； 其中， 该路径修改请求消息携带有进行本 地路由的指示信息；
步骤 614、 目 标服务网关向锚定网关发送该路径修改请求
( Path— Mod— Req ) 消息； 其中， 该路径修改请求消息携带有进行本地路由的 指示信息；
步骤 615、 锚定网关对该现有的承载进行资源授权， 并且锚定网关还可 以根据该进行本地路由的指示信息对本地路由进行授权； 锚定网关通过目标 服务网关向目标基站返回应答消息， 实现对现有的承载进行修改；
步骤 616、 目标基站在该修改后的现有的承载上将业务流相对应的报文 通过本地路由传输对端；
本发明实施例提供的本地路由实现方法， 若根据终端的 IP地址与业务流 承载信令携带的对端的 IP地址确定终端与对端为目标基站下的 IP地址， 则 目标服务网关将来自该终端的业务流相对应的报文通过执行本地路由传输至 该对端， 由于避免了通过锚定网关将该业务流相对应的报文路由至 HA后再 传送至外部网络， 因此减少了业务流相对应的 4艮文在网元之间传输的时延， 降低了核心网传输负载。
需要说明的是， 上述图 2〜图 6所示实施例所描述的终端的切换流程仅 为本发明实施例的示例， 只要使得目标服务网关或者目标基站能够通过终端 的切换流程获取终端的 IP地址， 若获取消息的种类以及获取消息的顺序有所 地址， 均为本发明实施例所述的实现方法， 本发明实施例仅为描述方便不再 贅述。
图 7为本发明网络设备一个实施例的结构示意图， 本发明实施例的网络 设备具体可以为服务网关， 也可以为基站； 如图 7所示， 本实施例包括： 获 取模块 71、 接收模块 72、 路由模块 73;
其中， 获取模块 71 在终端切换的过程中获取所述终端的因特网协议 IP 地址； 接收模块 72接收业务流承载信令， 所述业务流承载信令中包括所述终 端提供的业务流信息以及与所述终端进行通信的对端的 IP地址； 若根据所述 终端的 IP地址与所述对端的 IP地址判断所述终端与所述对端位于该网络设 备下， 则路由模块 73对所述业务流相对应的报文执行本地路由操作。
本发明实施例提供的网络设备， 若根据终端的 IP地址与对端的 IP地址 判断出终端与对端位于该网络设备下，则路由模块 73对该业务流相对应的报 文执行本地路由操作， 实现了将业务流相对应的报文通过本地路由传输至该 对端， 由于避免了通过网络设备将该业务流相对应的报文路由至 HA后再传 送至外部网络， 因此减少了业务流相对应的报文在网元之间传输的时延， 降 低了核心网传输负载。
图 8为本发明网络设备又一个实施例的结构示意图， 本发明实施例的网 络设备具体可以为服务网关， 也可以为基站； 如图 8所示， 本实施例包括： 获取模块 81、 接收模块 82、 路由模块 83;
其中， 获取模块 81 在终端切换的过程中获取所述终端的因特网协议 IP 地址； 接收模块 82接收业务流承载信令， 所述业务流承载信令中包括所述终 端提供的业务流信息以及与所述终端进行通信的对端的 IP地址； 若根据所述 终端的 IP地址与所述对端的 IP地址判断所述终端与所述对端位于该网络设 备下， 则路由模块 83对所述业务流相对应的报文执行本地路由操作。
进一步地， 获取模块 81还可以包括： 第一获取单元 811和 /或第二获取 单元 812; 其中， 第一获取单元 811在终端切换过程中向所述终端切换前的 原服务网关获取所述终端的 IP地址； 第二获取单元 812在终端切换过程中向 所述终端所在的接入网络的鉴权器获取所述终端的 IP地址。
进一步地， 第一获取单元 811还可以包括： 第一接收子单元 8111、 第一 获取子单元 8112; 其中， 第一接收子单元 8111接收来自原服务网关的携带 有该终端的 IP地址的切换确认消息； 第一获取子单元 8112从所述切换确认 消息中获取所述终端的 IP地址。
进一步地， 第二获取单元 812还可以包括： 发送子单元 8121、 第二接收 子单元 8122、 第二获取子单元 8123; 其中， 发送子单元 8121向鉴权器发送 用于请求获取所述终端的 IP地址的上下文请求消息； 第二接收子单元 8122 从所述携带有所述终端的 IP地址的上下文响应消息中获取所述终端的 IP地 址； 第二获取子单元 8123从所述携带有所述终端的 IP地址的上下文响应消 息中获取所述终端的 IP地址。
进一步地， 路由模块 83还可以包括： 发送单元 831、 路由单元 832; 其 中， 发送单元 831向锚定网关发送路径注册请求消息， 指示所述锚定网关根 据所述路径注册请求消息对所述业务流进行业务授权， 并接收所述锚定网关 返回的完成业务授权的应答消息； 路由单元 832将来自所述终端的业务流相 对应的 ^艮文路由至所述对端。
本发明实施例提供的网络设备， 若根据终端的 IP地址与业务流承载信令 携带的对端的 IP地址确定终端与对端为该网络设备下的 IP地址， 则路由模 块 83将来自该终端的业务流相对应的报文本地路由至该对端， 由于避免了通 过网络设备将该业务流相对应的报文路由至 HA后再传送至核心网， 因此减 少了业务流相对应的报文在网元之间传输的时延， 降低了核心网传输负载。
图 9为本发明本地路由实现方法再一个实施例的流程示意图， 如图 9所 示， 本发明实施例包括如下步骤：
步骤 901、 锚定网关接收由服务网关或基站根据终端提供的业务流信息 发起的与对端传输该业务流的业务流承载信令， 其中， 该对端为与终端进行 通信的终端设备， 业务流承载信令中携带有对端的 IP地址；
步骤 902、若锚定网关根据该对端的 IP地址与已获取到的终端的 IP地址 判断该终端与该对端位于同一个本地路由执行设备下， 则该锚定网关对该业 务流进行本地路由授权， 并通知该本地路由执行设备对该业务流相对应的报 文执行本地路由操作。
其中，本地路由执行设^据实际的网络架构可以为基站或者服务网关。 本发明实施例提供的本地路由实现方法， 若根据对端的 IP地址与已获取 到的终端的 IP地址确定终端与对端位于同一个本地路由执行设备下， 则指示 该本地路由执行设备对该业务流相对应的报文执行本地路由操作， 由于避免 了通过该锚定网关将该业务流相对应的报文路由至 HA后再传送至外部网络， 因此减少了业务流相对应的报文在网元之间传输的时延， 降低了核心网传输 负载。
进一步地， 在上述图 9所示实施例的步骤 902中， 锚定网关对业务流进 行本地路由授权具体可以为：
锚定网关向鉴权器发送资源请求消息， 所述资源请求消息包括所述终端 所请求的建立承载的业务流以及对所述业务流进行本地路由授权的指示； 锚定网关接收所述鉴权器根据所述对所述业务流进行本地路由授权的指 示返回的资源应答消息 , 所述资源应答消息携带有所述鉴权器对所述业务流 进行授权的授权结果， 使所述本地路由执行设备根据所述授权结果对所述业 务流执行本地路由。
通过上述过程， 避免了将该终端发起的业务流相对应的报文路由至 HA 后再传送至核心网， 因此减少了业务流相对应的 4艮文在网元之间传输的时延， 降低了核心网传输负载。
为了更清楚的理解图 9所示实施例的技术方案，下面结合图 10所示的信 令流程图进行示例性说明； 图 10为图 9所示实施例所适用的信令流程图， 本 实施例中， 当终端发起一个新的业务时， 终端发起业务流承载信令， 该业务 流承载信令具体可以为建立一个新的承载， 还可以为修改一个现有的承载， 该业务流承载用于传输该业务相关的>¾文； 如图 10所示， 本实施例包括如下 步骤：
步骤 1001、 终端向基站发送动态业务增加请求（DSA-REQ )消息， 指示 基站建立新的承载；
在上述动态业务增加请求消息中携带有终端发起的业务流的 IP五元组信 息， 该 IP五元组信息具体包括了业务流的源 IP地址、 目的 IP地址、 源端口 号、 目的端口号、 协议类型；
步骤 1002、基站向终端返回动态业务建立应答（DSA-RVD )消息， 表示 接收到该动态业务增加请求（DSA-REQ ) 消息；
步骤 1003、 基站向服务网关发送路径注册请求（ Path— Reg— Req ) 消息， 请求建立一个新的承载， 其中， 该 Path— Reg— Req消息携带有业务流的 IP五 元组信息；
步骤 1004、 服务网关向锚定网关发送该路径注册请求（ Path— Reg— Req ) 消息， 其中， 该路径注册请求（ Path— Reg— Req )消息携带业务流的 IP五元组 信息；
步骤 1005、 锚定网关（ Anchor GW )根据 IP五元组信息中的目的 IP地 址以及锚定网关已获取到的终端的 IP地址检测该对端是否也位于该发送请求 的服务网关（ Serving GW )下；如果是，则判断可以在该服务网关（ Serving GW ) 处执行本地路由；
或者， 若执行本地路由的执行主体为服务网关下的基站， 则锚定网关判 断是否可以在基站处执行本地路由； 锚定网关 （Anchor GW )还需要进一步 获取对端的承载信息， 该承载信息具体可以为承载标识、 IP五元组等， 其中， 通过承载标识指示基站在指定的业务流承载上对业务流相对应的报文执行本 地路由；
步骤 1006、 锚定网关（Anchor GW )通过接入网络中的鉴权器对该动态 业务增加请求进行资源授权；
进一步地， 锚定网关 （Anchor GW )还可以对本地路由进行授权； 具体 地， 锚定网关向鉴权器发送资源请求消息， 其中， 资源请求消息包括终端所 请求的建立承载的业务流以及对所述业务流进行本地授权的指示； 接收鉴权 器根据对该业务流进行本地授权的指示返回的资源应答消息， 其中， 资源应 答消息携带有鉴权器对业务流进行授权的授权结果。
步骤 1007、 锚定网关 （Anchor GW ) 向服务网关返回路径注册响应 ( Path— Reg— Rsp ) 消息； 其中， 该路径注册响应消息携带有在服务网关或者 基站（ Serving GW/BS )处进行本地路由的指示信息， 该进行本地路由的指示 信息包括至少如下一种信息： 本地路由的指示、执行本地路由的业务流信息、 对端的承载信息 （例如： 承载标识、 IP五元组信息） ；
步骤 1008、 服务网关 （ Serving GW ) 向基站返回该路径注册响应 ( Path— Reg— Rsp ) 消息， 其中， 该路径注册响应消息可选地携带有进行本地 路由的指示信息；
步骤 1009、 基站向终端返回动态业务增加请求响应 （DSA-RSP ) 消息； 步骤 1010、 终端向基站返回动态业务增加请求确认（DSA-ACK ) 消息； 步骤 1011、 基站向服务网关 （ Serving GW ) 返回路径注册确认 ( Path— Reg— Ack ) 消息；
步骤 1012、 服务网关向锚定网关返回路径注册响应 （ Path— Reg— Rsp ) 消 息， 指示 7|载建立完成；
步骤 1013、 锚定网关（ Anchor GW )向鉴权器（ Authenticator )发送资源 预留响应 （RR— Ack ) 消息， 指示资源授权完成；
步骤 1014、 服务网关根据锚定网关（ Anchor GW ) 的进行本地路由的指 示信息在该承载上对相应的业务流进行本地路由操作；
或者， 若执行本地路由的执行主体为服务网关下的基站， 则基站根据锚 定网关（Anchor GW ) 的进行本地路由的指示信息在该承载上对相应的业务 流进行本地路由操作。
本发明实施例提供的本地路由实现方法， 若根据业务流承载信令携带的 对端的 IP地址与已获取到的终端的 IP地址确定终端与对端位于同一个基站 或者服务网关下， 则指示该网络设备将来自该终端的业务流相对应的报文本 地路由至该对端， 由于避免了通过该锚定网关将该业务流相对应的报文路由 至 HA后再传送至外部网络， 因此减少了业务流相对应的报文在网元之间传 输的时延， 降低了核心网传输负载。
图 11为本发明网络设备再一个实施例的结构示意图， 如图 11所示， 本 是实施例包括： 接收模块 111、 授权模块 112、 通知模块 113;
其中， 接收模块 111接收由终端发起的通过原服务网关转发的与对端传 输业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端设备， 所述业务流承载信令中携带有所述对端的 IP地址； 若根据所述对端的 IP地 址与已获取到的所述终端的 IP地址判断所述终端与所述对端位于同一个本地 路由执行设备下， 则授权模块 112对所述业务流进行本地路由授权， 通知模 块 113通知该本地路由执行设备对所述业务流相对应的报文进行本地路由。 其中，本地路由执行设^据实际的网络架构可以为基站或者服务网关。 本发明实施例提供的网络设备， 若根据对端的 IP地址与已获取到的终端 的 IP地址确定终端与对端位于同一个本地路由执行设备下， 则授权模块 112 对所述业务流进行本地授权操作， 使本地路由执行设备对该业务流相对应的 报文进行本地路由， 由于避免了通过锚定网关将该业务流相对应的报文路由 至 HA后再传送至外部网络， 因此减少了业务流相对应的报文在网元之间传 输的时延， 降低了核心网传输负载。
进一步地，在上述图 11所示实施例的基石出上，授权模块 112还可以包括： 发送单元、 接收单元； 其中， 发送单元向鉴权器发送资源请求消息， 所述资 源请求消息包括所述终端所请求的建立承载的业务流以及对所述业务流进行 本地路由授权的指示； 接收单元接收所述鉴权器根据所述对所述业务流进行 本地路由授权的指示返回的资源应答消息， 所述资源应答消息携带有所述鉴 权器对所述业务流进行授权的授权结果， 使所述本地路由执行设备根据所述 授权结果对所述业务流执行本地路由。
图 12为本发明本地路由实现方法还一个实施例的流程示意图， 如图 12 所示， 本发明实施例包括如下步骤：
步骤 121、 接收由服务网关根据终端提供的业务流信息发起的与对端传 输业务流的业务流承载信令， 其中， 对端为与终端进行通信的终端设备， 业 务流承载信令中携带有对端的 IP地址；
步骤 122、若根据对端的 IP地址与已获取到的终端的 IP地址判断终端与 对端位于该服务网关下， 向服务网关发送本地路由指示， 使服务网关根据本 地路由指示判断是否可以对该业务流相对应的报文在所述服务网关下的基站 进行本地路由。
本发明实施例提供的本地路由实现方法， 若根据对端的 IP地址与已获取 到的终端的 IP地址判断终端与对端位于该服务网关下， 则向服务网关发送本 地路由指示，由于避免了通过该锚定网关将该业务流相对应的报文路由至 HA 后再传送至外部网络， 因此减少了业务流相对应的报文在网元之间传输的时 延， 降低了核心网传输负载。
进一步地， 在上述图 12所示实施例的基石出上， 还可以包括：
若所述服务网关根据所述本地路由指示确定所述基站能够进行本地路由 指示， 则所述服务网关指示所述基站对所述业务流相对应的报文执行本地路 由的操作。
图 13为图 12所示实施例所适用的信令流程图， 本实施例中， 当终端发 起一个新的业务时， 终端发起业务流承载信令， 该业务流承载信令具体可以 为建立一个新的承载， 还可以为修改一个现有的承载， 该业务流承载用于传 输该业务相关的^艮文； 如图 13所示， 本实施例包括如下步骤：
步骤 1301、 终端基站发送动态业务增加请求（DSA-REQ )消息， 指示基 站建立新的承载； 在上述动态业务增加请求消息中携带有该业务流的 IP五元 组信息；
步骤 1302、基站向终端返回动态业务建立应答（DSA-RVD )消息， 表示 接收到该动态业务增加请求（DSA-REQ ) 消息；
步骤 1303、 基站向服务网关发送路径注册请求（ Path— Reg— Req ) 消息， 请求建立一个新的承载； 其中， 该路径注册请求消息携带有业务流的 IP五元 组信息， 该 IP五元组信息具体包括了业务流的源 IP地址、 目的 IP地址、 源 端口号、 目的端口号、 协议类型；
步骤 1304、 服务网关向锚定网关发送路径注册请求（ Path— Reg— Req ) 消 息； 其中， 该路径注册请求（Path— Reg— Req )消息携带有业务流的 IP五元组 信息；
步骤 1305、 锚定网关（ Anchor GW )根据 IP五元组信息中的目的 IP地 址以及锚定网关已获取到的终端的 IP地址检测该对端是否也位于该发送请求 的服务网关（ Serving GW )下； 如果是， 则可以在该服务网关（ Serving GW ) 处执行本地路由； 步骤 1306、 锚定网关对该路径注册请求消息进行资源授权； 此外， 锚定网关还可以对本地路由进行授权；
步骤 1307、 锚定网关向服务网关返回路径注册响应 （ Path— Reg— Rsp ) 消 息； 其中， 该路径注册响应 （ Path— Reg— Rsp ) 消息携带有进行本地路由的指 示信息， 该进行本地路由的指示信息可以包括以下至少一种： 本地路由指示、 执行本地路由的业务流信息、 对端标识、 对端的承载信息（例如： 承载标识、 IP五元组信息） ；
步骤 1308、 服务网关根据 IP五元组信息中的目的 IP地址检测与终端通 信的对端是否位于同一个基站下， 如果是， 则在基站处执行本地路由， 继续 执行步骤 1309; 如果否， 则服务网关执行本地路由， 并执行步骤 1313; 此外， 服务网关还可以映射出对端在该基站处相对应的承载标识， 通过该承载标识 指示目标基站指定的业务流承载上执行本地路由；
步骤 1309、 服务网关向基站返回路径注册响应 （ Path— Reg— Rsp ) 消息， 其中， 该路径注册响应 （ Path— Reg— Rsp ) 消息携带有进行本地路由的指示信 息；
步骤 1310、 基站向终端返回动态业务增加响应 （DSA-RSP ) 消息； 步骤 1311、 终端向基站发送动态业务增加确认（DSA-ACK ) 消息； 步骤 1312、 基站向服务网关返回路径注册确认（ Path— Reg— Ack ) 消息； 步骤 1313、 服务网关（ Serving GW ) 向锚定网关（ Anchor GW )返回路 径注册响应 （ Path— Reg— Rsp ) 消息， 指示锚定网关承载建立完成；
步骤 1314、 锚定网关（ Anchor GW )向鉴权器（ Authenticator )发送资源 预留响应 （RR— Ack ) 消息， 指示资源授权完成；
步骤 1315、服务网关或者基站（ Serving GW/BS )根据锚定网关（ Anchor GW )发送的进行本地路由的指示信息在该承载上对相应的业务流相对应的报 文进行本地路由操作。
本发明实施例提供的本地路由实现方法， 若根据业务流承载信令携带的 对端的 IP地址与已获取到的终端的 IP地址确定终端与对端为同一个服务网 关或者基站下的 IP地址， 则锚定网关指示该目标服务网关将来自该终端的业 务流相对应的^艮文本地路由至该对端， 由于避免了通过该锚定网关将该业务 流相对应的 4艮文路由至 HA后再传送至外部网络， 因此减少了业务流相对应 的报文在网元之间传输的时延， 降低了核心网传输负载。
图 14为本发明本地路由实现***实施例的结构示意图， 如图 14示， 本 实施例包括： 本实施例包括： 锚定网关 141、 服务网关 142、 基站 143;
其中， 锚定网关 141接收由服务网关 142根据终端提供的业务流信息发 起的与对端传输业务流的业务流承载信令， 所述对端为与所述终端进行通信 的终端设备， 所述业务流承载信令中携带有所述对端的 IP地址；
若锚定网关 141根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于服务网关 142下， 向服务网关 142发送本地 路由指示， 使服务网关 142根据所述本地路由指示判断是否可以对所述业务 流相对应的报文在服务网关 142下的基站 143进行本地路。
本发明实施例提供的本地路由实现***， 若根据业务流承载信令携带 的对端的 IP地址与已获取到的终端的 IP地址确定终端与对端为服务网关 142下， 则锚定网关 141向服务网关 142发送本地路由指示， 由于避免了通 过该网络设备将该业务流相对应的 4艮文路由至 HA后再传送至核心网， 因 此减少了业务流相对应的报文在网元之间传输的时延， 降低了核心网传输 负载。
进一步地， 在上述图 14所示实施例的基石出上， 若服务网关 142根据所述 本地路由指示确定基站 143能够进行本地路由指示， 则服务网关 142指示基 站 143对所述业务流相对应的报文进行本地路由； 若服务网关 142根据所述 本地路由指示确定服务网关 142进行本地路由， 则服务网关 142对所述业务 流相对应的报文进行本地路由。
此外， 本发明实施例中的 IP 地址， 对于使用网际协议版本 4 ( Internet Protocol version 4, 简称： IPv4 )协议的场景， 为 IPv4协议地址； 对于使用网 际协议版本 6 ( Internet Protocol Version6, 简称： IPv6 )协议的场景， 为 IPv6 协议地址或网络前缀； 当然， 上述 IPv4协议地址以及 IPv6协议地址并不能 形成对本发明实施例的限制， 只要是通过本发明实施例均能够实现本地路由 的各种协议中规定的 IP地址均为本发明实施例所述的 IP地址。
通过本发明实施例， 例如在 WiMAX网络中， 当终端与通信的对端位于 同一个目标服务网关下时，报文传输路径从目标服务网关、锚定网关、 HA输 出至核心网，因此在目标服务网关、锚定网关、 HA之间会发生传输路径重叠， 即： 终端与对端之间的报文仍然需要首先从目标服务网关传输到 HA, 然后再 经 HA返回给该目标服务网关并发送给对端。 而通过上述本发明实施例， 目 送给对端， 从而减少报文在网元之间传输的时延、 降低核心网传输的负载； 或者， 当终端与通信的对端位于同一个目标基站下时， 报文传输路径从目标 基站、 目标服务网关、 锚定网关、 HA输出至核心网， 因此在目标基站、 目标 服务网关、锚定网关、 HA之间会发生传输路径重叠， 即： 终端与对端之间的 报文仍然需要首先从目标基站传输到 HA,然后再经 HA返回给该目标基站并 发送给对端。 而通过上述本发明实施例， 目标基站还可以采用本地路由技术 将终端发送的报文经过目标基站后发送给对端， 从而减少报文在网元之间传 输的时延、 降低核心网传输的负载。
上述本发明实施例仅以 WiMAX网络为例进行示例性说明， 但 WiMAX 并不能构成对本发明实施例的限制， 只要根据终端的 IP地址以及与终端进行 通信的对端的 IP地址触发本地路由， 从而减少报文在网元之间传输的时延， 均为本发明实施例所述适用的网络***。
所属领域的技术人员可以清楚地了解到， 为描述的方便和简洁， 上述描 述的***、 设备、 模块和单元的具体工作过程， 可以参考前述方法实施例中 的对应过程， 在此不再贅述。 本领域普通技术人员可以理解： 实现上述实施例的全部或部分步骤可以 通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读取存 储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述的存 储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介质。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求
1、 一种本地路由实现方法， 其特征在于， 包括：
在终端切换的过程中获取所述终端的因特网协议 IP地址；
接收业务流承载信令， 所述业务流承载信令中包括所述终端提供的业务 流信息以及与所述终端进行通信的对端的 IP地址；
若根据所述终端的 IP地址与所述对端的 IP地址判断所述终端与所述对 端位于同一个本地路由执行设备下， 则对所述业务流相对应的 4艮文执行本地 路由操作。
2、 根据权利要求 1所述的方法， 其特征在于， 所述在终端切换的过程中 获取所述终端的因特网协议 IP地址包括：
在终端切换过程中向所述终端切换前的原服务网关获取所述终端的 IP地 址； 或者，
在终端切换过程中向所述终端所在的接入网络的鉴权器获取所述终端的
IP地址。
3、 根据权利要求 2所述的方法， 其特征在于， 所述在终端切换过程中向 所述终端切换前的原服务网关获取所述终端的 IP地址包括：
接收来自原服务网关的携带有该终端的 IP地址的切换确认消息； 从所述切换确认消息中获取所述终端的 IP地址。
4、 根据权利要求 3所述的方法， 其特征在于， 所述本地路由执行设备为 目标月良务网关，
所述接收来自原服务网关的携带有该终端的 IP 地址的切换确认消息包 括：
所述目标服务网关接收原服务网关发送的携带有该终端的 IP地址的切换 确认消息；
所述从所述切换确认消息中获取所述终端的 IP地址包括：
所述目标服务网关从所述切换确认消息中获取所述终端的 IP地址。
5、 根据权利要求 3所述的方法， 其特征在于， 所述本地路由执行设备为 目标基站，
所述接收来自原服务网关的携带有该终端的 IP 地址的切换确认消息包 括：
所述目标基站接收经目标服务网关转发的来自原服务网关的携带有该终 端的 IP地址的切换确认消息；
所述从所述切换确认消息中获取所述终端的 IP地址包括：
所述目标基站从所述切换确认消息中获取所述终端的 IP地址。
6、 根据权利要求 2所述的方法， 其特征在于， 所述在终端切换过程中向 所述终端所在的接入网络的鉴权器获取所述终端的 IP地址包括：
向鉴权器发送用于请求获取所述终端的 IP地址的上下文请求消息； 接收所述鉴权器根据所述上下文请求消息返回的携带有所述终端的 IP地 址的上下文响应消息；
从所述携带有所述终端的 IP地址的上下文响应消息中获取所述终端的 IP 地址。
7、 根据权利要求 6所述的方法， 其特征在于， 所述本地路由执行设备为 目标月良务网关，
所述向鉴权器发送用于请求获取所述终端的 IP地址的上下文请求消息包 括：
所述目标服务网关向鉴权器发送用于请求获取所述终端的 IP地址的上下 文请求消息；
所述接收所述鉴权器根据所述上下文请求消息返回的携带有所述终端的 IP地址的上下文响应消息包括：
所述目标服务网关接收所述鉴权器根据所述上下文请求消息返回的携带 有所述终端的 IP地址的上下文响应消息；
所述从所述携带有所述终端的 IP地址的上下文响应消息中获取所述终端 的 IP地址包括：
所述目标服务网关从所述携带有所述终端的 IP地址的上下文响应消息中 获取所述终端的 IP地址。
8、 根据权利要求 6所述的方法， 其特征在于， 所述本地路由执行设备为 目标基站，
所述向鉴权器发送用于请求获取所述终端的 IP地址的上下文请求消息包 括：
所述目标基站通过目标服务网关向鉴权器发送用于请求获取所述终端的 IP地址的上下文请求消息；
所述接收所述鉴权器根据所述上下文请求消息返回的携带有所述终端的
IP地址的上下文响应消息包括：
所述目标基站通过所述目标服务网关接收所述鉴权器根据所述上下文请 求消息返回的携带有所述终端的 IP地址的上下文响应消息；
所述从所述携带有所述终端的 IP地址的上下文响应消息中获取所述终端 的 IP地址包括：
所述目标基站通过所述目标服务网关从所述携带有所述终端的 IP地址的 上下文响应消息中获取所述终端的 IP地址。
9、 根据权利要求 1 ~ 8任一所述的方法， 其特征在于， 所述对所述业务 流相对应的 4艮文执行本地路由操作包括：
向锚定网关发送路径注册请求消息，指示所述锚定网关根据所述路径注 册请求消息对所述业务流进行业务授权， 并接收所述锚定网关返回的完成业 务授权的应答消息；
将来自所述终端的业务流相对应的报文路由至所述对端。
10、 一种网络设备， 其特征在于， 包括：
获取模块，用于在终端切换的过程中获取所述终端的因特网协议 IP地址； 接收模块， 用于接收业务流承载信令， 所述业务流承载信令中包括所述 终端提供的业务流信息以及与所述终端进行通信的对端的 IP地址； 路由模块， 用于若根据所述终端的 IP地址与所述对端的 IP地址判断所 述终端与所述对端位于该网络设备下， 则对所述业务流相对应的报文执行本 地路由操作。
11、 根据权利要求 10所述的设备， 其特征在于， 所述获取模块包括： 获取所述终端的 IP地址； 和 /或，
第二获取单元， 用于在终端切换过程中向所述终端所在的接入网络的鉴 权器获取所述终端的 IP地址。
12、 根据权利要求 11所述的设备， 其特征在于，
所述第一获取单元包括：
第一接收子单元， 用于接收来自原服务网关的携带有该终端的 IP地址的 切换确认消息；
第一获取子单元， 用于从所述切换确认消息中获取所述终端的 IP地址； 所述第二获取单元包括：
发送子单元， 用于向鉴权器发送用于请求获取所述终端的 IP地址的上下 文请求消息；
第二接收子单元， 用于从所述携带有所述终端的 IP地址的上下文响应消 息中获取所述终端的 IP地址；
第二获取子单元， 用于从所述携带有所述终端的 IP地址的上下文响应消 息中获取所述终端的 IP地址。
13、 根据权利要求 10 ~ 12任一所述的设备， 其特征在于， 所述路由模块 包括：
发送单元， 用于向锚定网关发送路径注册请求消息， 指示所述锚定网关 根据所述路径注册请求消息对所述业务流进行业务授权， 并接收所述锚定网 关返回的完成业务授权的应答消息； 路由单元，用于将来自所述终端的业务流相对应的报文路由至所述对端。
14、 一种本地路由实现方法， 其特征在于， 包括：
锚定网关接收由服务网关或基站根据终端提供的业务流信息发起的与对 端传输该业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端 设备， 所述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于同一个本地路由执行设备下， 则所述锚定网 关对所述业务流进行本地路由授权， 并通知所述本地路由执行设备对所述业 务流相对应的报文执行本地路由。
15、 根据权利要求 14所述的方法， 其特征在于， 所述锚定网关对所述业 务流进行本地路由授权包括：
所述锚定网关向鉴权器发送资源请求消息， 所述资源请求消息包括所述 终端所请求的建立承载的业务流以及对所述业务流进行本地路由授权的指 示；
所述锚定网关接收所述鉴权器根据所述对所述业务流进行本地路由授权 的指示返回的资源应答消息， 所述资源应答消息携带有所述鉴权器对所述业 务流进行授权的授权结果， 使所述本地路由执行设备根据所述授权结果对所 述业务流执行本地路由。
16、 一种网络设备， 其特征在于， 包括：
接收模块， 用于接收由终端发起的通过原服务网关转发的与对端传输业 务流的业务流承载信令， 所述对端为与所述终端进行通信的终端设备， 所述 业务流承载信令中携带有所述对端的 IP地址；
授权模块， 用于若根据所述对端的 IP地址与已获取到的所述终端的 IP 地址判断所述终端与所述对端位于同一个本地路由执行设备下， 则对所述业 务流进行本地路由授权；
通知模块， 用于通知该本地路由执行设备对所述业务流相对应的报文进 行本地路由。
17、 根据权利要求 16所述的设备， 其特征在于， 所述授权模块包括： 发送单元， 用于向鉴权器发送资源请求消息， 所述资源请求消息包括所 述终端所请求的建立承载的业务流以及对所述业务流进行本地路由授权的指 示
接收单元， 用于接收所述鉴权器根据所述对所述业务流进行本地路由授 权的指示返回的资源应答消息 , 所述资源应答消息携带有所述鉴权器对所述 业务流进行授权的授权结果， 使所述本地路由执行设备根据所述授权结果对 所述业务流执行本地路由。
18、 一种本地路由实现方法， 其特征在于， 包括：
锚定网关接收由服务网关根据终端提供的业务流信息发起的与对端传输 业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端设备， 所 述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于该服务网关下， 向所述服务网关发送本地路 由指示， 使所述服务网关根据所述本地路由指示判断是否可以对所述业务流 相对应的报文在所述服务网关下的基站进行本地路由。
19、 根据权利要求 18所述的方法， 其特征在于， 还包括：
若所述服务网关根据所述本地路由指示确定所述基站能够进行本地路由 指示， 则所述服务网关指示所述基站对所述业务流相对应的报文进行本地路 由； 若所述服务网关根据所述本地路由指示确定该服务网关进行本地路由， 则所述服务网关对所述业务流相对应的报文进行本地路由。
20、 一种本地路由实现***， 其特征在于， 包括： 锚定网关、 服务网关、 基站；
所述锚定网关接收由所述服务网关根据终端提供的业务流信息发起的与 对端传输业务流的业务流承载信令， 所述对端为与所述终端进行通信的终端 设备， 所述业务流承载信令中携带有所述对端的 IP地址；
若所述锚定网关根据所述对端的 IP地址与已获取到的所述终端的 IP地 址判断所述终端与所述对端位于所述服务网关下， 向所述服务网关发送本地 路由指示， 使所述服务网关根据所述本地路由指示判断是否可以对所述业务 流相对应的报文在所述服务网关下的所述基站进行本地路由。
21、 根据权利要求 20所述的***， 其特征在于， 还包括：
若所述服务网关根据所述本地路由指示确定所述基站能够进行本地路由 指示， 则所述服务网关指示所述基站对所述业务流相对应的报文进行本地路 由； 若所述服务网关根据所述本地路由指示确定该服务网关进行本地路由， 则所述服务网关对所述业务流相对应的报文进行本地路由。
PCT/CN2010/072130 2010-04-23 2010-04-23 本地路由实现方法及***、网络设备 WO2011130920A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2010/072130 WO2011130920A1 (zh) 2010-04-23 2010-04-23 本地路由实现方法及***、网络设备
CN201080001610.3A CN102365845B (zh) 2010-04-23 2010-08-23 本地路由实现方法及***、网络设备
PCT/CN2010/076243 WO2011130983A1 (zh) 2010-04-23 2010-08-23 本地路由实现方法及***、网络设备
CN201410766775.XA CN104602220B (zh) 2010-04-23 2010-08-23 本地路由实现方法及***、网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2010/072130 WO2011130920A1 (zh) 2010-04-23 2010-04-23 本地路由实现方法及***、网络设备

Publications (1)

Publication Number Publication Date
WO2011130920A1 true WO2011130920A1 (zh) 2011-10-27

Family

ID=44833646

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/CN2010/072130 WO2011130920A1 (zh) 2010-04-23 2010-04-23 本地路由实现方法及***、网络设备
PCT/CN2010/076243 WO2011130983A1 (zh) 2010-04-23 2010-08-23 本地路由实现方法及***、网络设备

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076243 WO2011130983A1 (zh) 2010-04-23 2010-08-23 本地路由实现方法及***、网络设备

Country Status (1)

Country Link
WO (2) WO2011130920A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103428732A (zh) * 2012-05-25 2013-12-04 中兴通讯股份有限公司 路由优化方法及***、无线侧网元
WO2021168813A1 (zh) * 2020-02-28 2021-09-02 华为技术有限公司 通信方法和通信装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1520200A (zh) * 2003-01-09 2004-08-11 ��ʽ����Ntt����Ħ 移动通信***和移动通信***中使用的路由管理设备
WO2006118751A2 (en) * 2005-05-02 2006-11-09 Sbc Knowledge Ventures, L.P. Communication system and method of routing calls to a terminating end point
CN101577678A (zh) * 2008-05-07 2009-11-11 阿尔卡特朗讯公司 用于本地路由数据业务的网络设备和方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007288748A (ja) * 2006-04-20 2007-11-01 Yamaha Corp スイッチングハブ、ルータおよび仮想ｌａｎシステム
CN101106491A (zh) * 2006-07-11 2008-01-16 华为技术有限公司 微波接入全球互通网络中r3接口的迁移方法及其***
JP4773987B2 (ja) * 2007-02-01 2011-09-14 アラクサラネットワークス株式会社 端末所属切換システム
CN101400063A (zh) * 2007-09-29 2009-04-01 中兴通讯股份有限公司 一种网络侧协商网元ip能力的方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1520200A (zh) * 2003-01-09 2004-08-11 ��ʽ����Ntt����Ħ 移动通信***和移动通信***中使用的路由管理设备
WO2006118751A2 (en) * 2005-05-02 2006-11-09 Sbc Knowledge Ventures, L.P. Communication system and method of routing calls to a terminating end point
CN101577678A (zh) * 2008-05-07 2009-11-11 阿尔卡特朗讯公司 用于本地路由数据业务的网络设备和方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103428732A (zh) * 2012-05-25 2013-12-04 中兴通讯股份有限公司 路由优化方法及***、无线侧网元
CN103428732B (zh) * 2012-05-25 2018-09-28 中兴通讯股份有限公司 路由优化方法及***、无线侧网元
WO2021168813A1 (zh) * 2020-02-28 2021-09-02 华为技术有限公司 通信方法和通信装置

Also Published As

Publication number Publication date
WO2011130983A1 (zh) 2011-10-27

Similar Documents

Publication Publication Date Title
JP4669002B2 (ja) 異種ネットワークにおけるインターワーキングのための高速なコンテキスト確立
JP5421411B2 (ja) サービスノード
JP5221526B2 (ja) システム間ハンドオーバの場合に端末のｐｄｐコンテキストを転送する装置及び方法
TWI331859B (zh)
WO2011000318A1 (zh) 切换控制的方法和设备
WO2009062392A1 (fr) Procédé de transfert de système, système de communication et entité pcrf
WO2013086949A1 (zh) 一种通信方法及设备
WO2010105525A1 (zh) 一种切换的优化方法、切换装置和***
WO2011017979A1 (zh) 支持ip分流的通信***中资源管理方法与装置
WO2011047609A1 (zh) 一种实现切换预注册的方法及***
KR20090043306A (ko) 무선접속 시스템의 핸드오버 방법 및 이를 지원하는 게이트웨이
WO2011009353A1 (zh) 建立ip分流连接的实现方法和***
WO2011130920A1 (zh) 本地路由实现方法及***、网络设备
WO2009152757A1 (zh) 一种数据报文发送方法、装置及通信***
KR101037464B1 (ko) Ａｓｎ간 핸드오버 처리 방법 및 그 방법을 지원하는 ａｓｎ-ｇｗ
WO2016074454A1 (zh) 一种支持多pdn连接的优化切换的方法和相应网络节点
KR101372735B1 (ko) 네트워크 기반 이동성 관리 방법
WO2014071798A1 (zh) 管理分流连接的方法、无线侧网元及移动性管理实体
WO2011097988A1 (zh) 对本地ip数据进行管理的方法及移动通信***
WO2011147082A1 (zh) 本地路由授权的方法、装置和***
CN104602220A (zh) 本地路由实现方法及***、网络设备
WO2009146630A1 (zh) 实现本地传输的方法、***和设备
WO2011160527A1 (zh) 一种传递分流信息的方法及装置、***
WO2012174981A1 (zh) Ip分流连接的处理方法及装置
WO2012174962A1 (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: 10850054

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: 10850054

Country of ref document: EP

Kind code of ref document: A1