WO2010132700A1 - Session suspend and resume using a transient binding option messaging - Google Patents

Session suspend and resume using a transient binding option messaging Download PDF

Info

Publication number
WO2010132700A1
WO2010132700A1 PCT/US2010/034785 US2010034785W WO2010132700A1 WO 2010132700 A1 WO2010132700 A1 WO 2010132700A1 US 2010034785 W US2010034785 W US 2010034785W WO 2010132700 A1 WO2010132700 A1 WO 2010132700A1
Authority
WO
WIPO (PCT)
Prior art keywords
foreign
mobile node
mobility anchor
local mobility
access gateway
Prior art date
Application number
PCT/US2010/034785
Other languages
French (fr)
Inventor
Ahmad S. Muhanna
Michael Brown
Mohamed Khalil
Original Assignee
Nortel Networks Limited
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
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=43085334&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=WO2010132700(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Nortel Networks Limited filed Critical Nortel Networks Limited
Priority to EP10775557.1A priority Critical patent/EP2430856A4/en
Priority to RU2011150404/07A priority patent/RU2527488C2/en
Priority to JP2012511021A priority patent/JP5508522B2/en
Priority to US13/138,985 priority patent/US9253815B2/en
Priority to BRPI1010599-9A priority patent/BRPI1010599B1/en
Priority to KR1020117029694A priority patent/KR101389590B1/en
Priority to CA2761668A priority patent/CA2761668C/en
Priority to CN201080032448.1A priority patent/CN102484823B/en
Publication of WO2010132700A1 publication Critical patent/WO2010132700A1/en
Priority to HK12112154.3A priority patent/HK1171603A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/20Manipulation of established connections
    • H04W76/28Discontinuous transmission [DTX]; Discontinuous reception [DRX]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/04Interfaces between hierarchically different network devices
    • H04W92/14Interfaces between hierarchically different network devices between access point controllers and backbone network device
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/02Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023Buffering or recovering information during reselection

Definitions

  • IP-based mobile systems provide for communication between at least one mobile node and a wireless communication network.
  • the term “mobile node” includes a mobile communication unit (e.g., mobile terminal, "smart phones,” nomadic devices such as laptop PCs with wireless connectivity, as described in greater detail below).
  • the wireless communication system includes a home network and a foreign network.
  • the mobile node may change its point of attachment to the Internet through these networks, but the mobile node will always be associated with a single home network for IP addressing purposes.
  • the home network includes a home agent and the foreign network includes a foreign agent ⁇ both of which control the routing of information packets into and out of their network.
  • the mobile node, home agent and foreign agent may be called different names depending on the nomenclature used on any particular network configuration or communication system.
  • a “mobile node” encompasses PC's having cabled (e.g., telephone line ("twisted pair"), Ethernet cable, optical cable, and so on) connectivity to the wireless network, as well as wireless connectivity directly to the cellular network, as can be experienced by various makes and models of mobile terminals ("cell phones") having various features and functionality, such as Internet access, e-mail, messaging services, and the like.
  • Mobile nodes are sometimes called a user equipment, mobile unit, mobile terminal, mobile device, or similar names depending on the nomenclature adopted by particular system providers.
  • correspondence node which may be mobile or fixed, that may be located on the network for communicating with the mobile node.
  • a home agent may also be referred to as a Local Mobility Anchor, Home Mobility Manager, Home Location Register, and a foreign agent may be referred to as a Mobile Access Gateway, Serving Mobility Manager, Visited Location Register, and Visiting Serving Entity.
  • the terms mobile node, home agent and foreign agent are not meant to be restrictively defined, but could include other mobile communication units or supervisory routing devices located on the home or foreign networks.
  • Foreign networks can also be called serving networks.
  • Foreign agents and home agents periodically broadcast an agent advertisement to all nodes on the local network associated with that agent.
  • An agent advertisement is a message from the agent on a network that may be issued under the Mobile IP protocol (RFC 2002) or any other type of communications protocol.
  • This advertisement should include information that is required to uniquely identify a mobility agent (e.g. a home agent, a foreign agent, etc.) to a mobile node.
  • Mobile nodes examine the agent advertisement and determine whether they are connected to the home network or a foreign network.
  • the mobile node will always be associated with its home network and sub-network for IP addressing purposes and will have information routed to it by routers located on the home and foreign network. If the mobile node is located on its home network, information packets will be routed to the mobile node according to the standard addressing and routing scheme. If the mobile node is visiting a foreign network, however, the mobile node obtains appropriate information from the agent advertisement, and transmits a registration request message (sometimes called a binding update request) to its home agent through the foreign agent. The registration request message will include a care- of address for the mobile node.
  • a registration reply message (also called a binding update acknowledge message) may be sent to the mobile node by the home agent to confirm that the registration process has been successfully completed.
  • the mobile node keeps the home agent informed as to its location on foreign networks by registering a "care-of address" with the home agent.
  • the registered care-of address identifies the foreign network where the mobile node is located, and the home agent uses this registered care-of address to forward information packets to the foreign network for subsequent transfer onto the mobile node. If the home agent receives an information packet addressed to the mobile node while the mobile node is located on a foreign network, the home agent will transmit the information packet to the mobile node's current location on the foreign network using the applicable care-of address. That is, this information packet containing the care-of address will then be forwarded and routed to the mobile node on the foreign network by a router on the foreign network according to the care-of address.
  • Multiple interfaces may be supported on a single or multiple foreign networks, which can include the different communication access types 802.1 Id, 802. Hg, HRPD, WiFi, WiMax, CDMA, or LTE apart from the circuit-switched type of telephone communication access types.
  • Problems can be encountered when the mobile node becomes coupled to different access types on a single or multiple networks, or when hand-over procedures are performed from one access type to another access type.
  • problems are sometimes encountered with the registration of the care of addressing with the home agent or local mobility anchor.
  • problems can arise with hand-off procedure for a communication when the home agent or local mobility anchor may drop packets or bill for dropped packets, which can disrupt transmissions and cause billing discrepancies, (e.g. billing the subscriber for packets that were never received).
  • This invention provides for accurate hand-over procedures and billing of transmission packets through a new method and system for suspending and resuming downlink communication transmissions.
  • the invention addresses the situation where a mobile node is transitioned to a new foreign network or a second access type on the same foreign network (multiple access types are supported on the foreign network), but the new foreign network does not support downlink transmissions to the mobile node. It is primary objective of this invention to provide sufficient information from the local mobility agent so the mobility access gateway (or foreign agent) can optimize the resource usage on the network and can accurately bill the subscriber for received transmission packets, as opposed to billing the subscriber for dropped packets that are never received by the mobile node.
  • the present invention uses a Transient Binding Option message with a suspend/resume flag setting sent to the local mobility anchor from the foreign agent that was supporting downlink transmissions to the mobile node.
  • a transient binding option is proposed for creating a transient Binding Cache Entry (BCE) state at the home agent/local mobility anchor during an inter-MAG (Mobile Access Gateway) handover, which will suspend down-link traffic from the home agent/local mobility anchor until the transient BCE (suspend) state is cleared by the foreign agent previously supporting downlink transmissions.
  • BCE Transient Binding Cache Entry
  • the present invention can be implemented using a new protocol application or modified messages from prior registration applications. BRIEF DESCRIPTION OF THE DRAWINGS
  • Fig. 1 is a mobile IP-based communication system as used in the present invention showing 3GPP and non-3 GPP networks;
  • Fig. 2 shows a call flow diagram using the transient binding update messages and the expanded binding revocation trigger messages.
  • the overall architecture of the IP-based mobile system is shown with a mobile mode 125, a home network 110 and foreign networks 130 and 150, respectively.
  • the home network 110 has a home agent or local mobility anchor 113.
  • the local mobility anchor 113 is coupled to the mobility access gateway (SGW) 155 on foreign network 130 by communication link 1 12, and local mobility anchor 113 is coupled to the mobility access gateway 135 on foreign network 130 by communication link 115.
  • SGW mobility access gateway
  • the mobility access gateway (SGW) 155 is coupled to MME 165 by communication link 166, Serving GPRS Support Node (SGSN) 168 by communication link 169, and EUTRAN server 170 by communication link 171.
  • the Mobility Management Entry MME 165 is also coupled to the Serving GPRS Support Node (SGSN) 168 by communication link 174 and the Evolved Universal Terrestrial Radio Access Network EUTRAN server 170 by communication link 175.
  • the home network 110 is coupled to the Internet 200 by link 201 and the Internet 200 is coupled to a foreign network FN 205 by communication link 206, which is coupled to a correspondent node (CN) 210 by link 207.
  • CN correspondent node
  • the mobility access gateway 155 is coupled to the mobile node 125 through the radio access system comprised of the base station transceiver 139 coupled to the antenna/transmitter 137 through the wireless communication link 127.
  • the mobility access gateway 135 is coupled to the mobile node 125 through the radio access system comprised of the base station transceiver 141 coupled to the antenna/transmitter 140 through the wireless communication link 157.
  • the mobility access gateway 135 is coupled the mobile node 125 using a second communication access type, such as a non-3GPP access type or circuit switched (CS) access, which is supported by the interface 141 and communication link 157 or CS interface 153 through communication links 152 and 154.
  • a second communication access type such as a non-3GPP access type or circuit switched (CS) access
  • Mobile node 125 is shown electronically coupled to the foreign networks 130 and 150 via the wireless communication link 159 and 158, respectively.
  • the mobile node 125 can communicate with any transceiver or access network coupled to a foreign network. That is, communications links 159 and 158 are radio transmitted links, but these links can be composed of any connection between two or more nodes on a network or users on networks or administrative domains.
  • the terms Local Mobility Anchor, home agent, and foreign agent may be as defined in the 3-GPP protocols defined by 3GPP TS23.402, but these agents are not restricted to a single protocol or system.
  • the term home agent as used in this application, can refer to a home mobility manager, home location register, home serving entity, or any other agent at a home network 110 having the responsibility to manage mobility-related functionality for a mobile node 125.
  • the term mobility access gateway as used in this application, can refer to a foreign agent, serving mobility manager, visited location register, visiting serving entity, or any other agent on a foreign network having the responsibility to manage mobility-related functionality for a mobile node 125.
  • the interface connections between the home agent LMA 113 and the foreign agent (MAG SGW) 155 may be defined by the S5 or S8 connections in the TS23.402 standard, and the connections between the home agent LMA 1 13 and the foreign agent (MAG SGW) 135 may be defined by the S2a and S2b connections described in the TS23.402 standard.
  • the mobile node 125 is identified by a permanent IP address. While the mobile node 125 is coupled to its home network 110, the mobile node 125 receives information packets like any other fixed node on the home network 110. When mobile, the mobile node 125 can also locate itself on foreign network, such as network 130 or 150. When located on foreign network 130 or 150, the home network 110 sends data communications to the mobile node 125 by "tunneling" the communications to the foreign network 130 or 150.
  • the mobile node 125 keeps the local mobility anchor 113 informed of its current location, or foreign network association, by registering a care-of address with the local mobility anchor 113. Essentially, the care-of address represents the foreign network where the mobile node 125 is currently located. If the local mobility anchor 113 receives an information packet addressed to the mobile node 125 while the mobile node 125 is located on a foreign network 130, the local mobility anchor 113 will "tunnel" the information packet to foreign network 130 for subsequent transmission to mobile node 125.
  • the foreign agent 155 participates in informing the local mobility anchor 113 of the mobile node 125 current care-of address.
  • the foreign agent 155 also receives information packets for the mobile node 125 after the information packets have been forwarded to the foreign agent 155 by the local mobility anchor 113.
  • the foreign agent 155 serves as a default router for out-going information packets generated by the mobile node 125 while connected to the foreign network 130.
  • the transfer of the communication packets from the home network 110 to the mobile node 125 is called downlink traffic, while the transfer of out-going communication packets from the mobile node 125 is called uplink traffic.
  • the mobile node 125 participates in informing the local mobility anchor 113 of its current location and requests connections to the associated foreign network.
  • the mobile node 125 transitions to connecting to a different access type on the foreign network or a wholly different foreign network (handover)
  • the mobile node 125 obtains appropriate information regarding the address of the foreign network and/or the foreign agent from an agent advertisement.
  • MME 165 will inform the foreign agent (MAG SGW) 155 that the mobile node is no longer coupled to the foreign network 130. In that situation, all downlink traffic from the foreign agent (MAG SGW) will be dropped because the mobile node 125 is no longer coupled to the foreign network 130.
  • the home agent (LMA) 113 on the home network 110 may continue to transmit downlink traffic to the foreign agent (MAG SGW) 115 because the home network has not been notified of the transition of the mobile node to the foreign network 150. As such, downlink traffic will continue to flow from the home network 110, and the subscriber will be billed for that downlink traffic even though the downlink traffic is dropped and is not delivered to the mobile node 125.
  • the billing count on the home network 1 10 will not match the billing count on the foreign network 150 in this situation because the home network 110 will bill for all downlink traffic sent to the foreign network 150 but the foreign agent LMA 155 will not bill for that downlink traffic to the mobile node 125 because that traffic was dropped and not delivered, which leads to a billing irregularity that will need to be reconciled,
  • the Transient Binding Option message 301 is prepared by the foreign agent (MAG SGW) 155 after receiving a notice message 300 from the MME 165 with an indication that the mobile node 125 has moved to a foreign network 150.
  • the foreign network may not support downlink traffic transmission to the mobile node 125 because of the particular access type supported on the foreign network 150. If the home network 110 continues to transmit downlink traffic to the mobile node 125 through the foreign network 130, the communications will be dropped and the billing irregularities will arise between the billing counts on the home agent LMA 113 and the billing counts on the foreign agent (MAG SGW) 155.
  • the Transient Binding Option message 301 is sent from the foreign agent (MAG SGW) 155 to the home agent LMA 113 with a suspend/resume flag set to the "Suspend" setting.
  • the "Suspend" setting of the suspend/resume flag may be valued at "1.”
  • the home agent LMA 113 receives the suspend/resume flag in the Transient Binding Option message 301, the home agent suspends the transmission of downlink traffic for the specified session with the mobile node 125. This suspension of downlink traffic continues until the foreign agent (MAG SGW) 155 transmits a second Transient Binding Option message 305 to the home agent LMA 113 with a suspend/resume flag set to the "Resume” setting.
  • the mobile node 125 may be re-connected to the foreign network 130, so the downlink traffic can continue to be transmitted to the mobile node 125 through the foreign agent (MAG SGW) 155 on foreign network 130 or when the mobile node 125 is coupled to a foreign network 150 that supports an access type that will allow downlink communication transmissions.
  • the invention eliminates the billing inconsistencies and reduces the amount of dropped transmissions to the mobile node 125.
  • the Transient Binding Option message can create a BCE state at the home agent LMA 113 during the inter-MAG handover.
  • the Transient Binding Option message 301 may use a flag setting in a Proxy Binding Update message or other messages depending on the vendor specific extensions available and the access types used by the networks.
  • the Transient Binding Option message 301 should be sent from the same foreign agent (MAG SGW) 155 that is servicing downlink traffic to the mobile node 125.
  • the home agent LMA 113 When the home agent LMA 113 receives a Transient Binding Option message 301 from the same foreign agent (MAG SGW) 155 that is servicing downlink traffic, the home agent LMA 113 will determine that the downlink traffic is not subject to any handover to the foreign network 150 and the home agent LMA 113 will maintain the "Suspend" state. Upon the transmission of a "Resume” flag in a Transient Binding Option message 305 to the LMA 113, the downlink traffic shall resume transmission.
  • MAG SGW foreign agent

Landscapes

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

Abstract

The present invention uses a message with a suspend/resume flag setting sent to the local mobility anchor from the foreign agent that was supporting downlink transmissions to the mobile node. Namely, a transient binding option is proposed for creating a transient BCE state at the home agent/local mobility anchor during an inter-MAG handover, which will suspend down-link traffic from the home agent/local mobility anchor until the transient BCE (suspend) state is cleared by the foreign agent previously supporting downlink transmissions. After the transient BCE (suspend) state is cleared, the downlink traffic from the home agent/local mobility anchor can resume with forwarding of downlink traffic to the mobile node through the foreign agent. The present invention can be implemented using a new protocol application or modified messages from prior registration applications.

Description

SESSION SUSPEND AND RESUME USING A TRANSIENT BINDING OPTION MESSAGING
RELATED APPLICATION DATA
[0001] This application is related to Provisional Patent Application Serial No. 61/177,794 filed on May 13, 2009, and priority is claimed for this earlier filing under 35 U.S.C. § 119(e). The Provisional Patent Application is also incorporated by reference into this utility patent application. TECHNICAL FIELD OF THE INVENTION
[0002] A method and system that suspends and resumes a wireless communication session using a new flag, option or message transmission. BACKGROUND OF THE INVENTION
[0Θ03] IP-based mobile systems provide for communication between at least one mobile node and a wireless communication network. The term "mobile node" includes a mobile communication unit (e.g., mobile terminal, "smart phones," nomadic devices such as laptop PCs with wireless connectivity, as described in greater detail below). Among other elements, the wireless communication system includes a home network and a foreign network. The mobile node may change its point of attachment to the Internet through these networks, but the mobile node will always be associated with a single home network for IP addressing purposes. The home network includes a home agent and the foreign network includes a foreign agent ~ both of which control the routing of information packets into and out of their network.
[0004] The mobile node, home agent and foreign agent may be called different names depending on the nomenclature used on any particular network configuration or communication system. For instance, a "mobile node" encompasses PC's having cabled (e.g., telephone line ("twisted pair"), Ethernet cable, optical cable, and so on) connectivity to the wireless network, as well as wireless connectivity directly to the cellular network, as can be experienced by various makes and models of mobile terminals ("cell phones") having various features and functionality, such as Internet access, e-mail, messaging services, and the like. Mobile nodes are sometimes called a user equipment, mobile unit, mobile terminal, mobile device, or similar names depending on the nomenclature adopted by particular system providers. Generally, there is also a correspondence node, which may be mobile or fixed, that may be located on the network for communicating with the mobile node.
[0005] A home agent may also be referred to as a Local Mobility Anchor, Home Mobility Manager, Home Location Register, and a foreign agent may be referred to as a Mobile Access Gateway, Serving Mobility Manager, Visited Location Register, and Visiting Serving Entity. The terms mobile node, home agent and foreign agent are not meant to be restrictively defined, but could include other mobile communication units or supervisory routing devices located on the home or foreign networks. Foreign networks can also be called serving networks. Registering The Mobile Node
[0006] Foreign agents and home agents periodically broadcast an agent advertisement to all nodes on the local network associated with that agent. An agent advertisement is a message from the agent on a network that may be issued under the Mobile IP protocol (RFC 2002) or any other type of communications protocol. This advertisement should include information that is required to uniquely identify a mobility agent (e.g. a home agent, a foreign agent, etc.) to a mobile node. Mobile nodes examine the agent advertisement and determine whether they are connected to the home network or a foreign network.
[0007] The mobile node will always be associated with its home network and sub-network for IP addressing purposes and will have information routed to it by routers located on the home and foreign network. If the mobile node is located on its home network, information packets will be routed to the mobile node according to the standard addressing and routing scheme. If the mobile node is visiting a foreign network, however, the mobile node obtains appropriate information from the agent advertisement, and transmits a registration request message (sometimes called a binding update request) to its home agent through the foreign agent. The registration request message will include a care- of address for the mobile node. A registration reply message (also called a binding update acknowledge message) may be sent to the mobile node by the home agent to confirm that the registration process has been successfully completed.
[0008] The mobile node keeps the home agent informed as to its location on foreign networks by registering a "care-of address" with the home agent. The registered care-of address identifies the foreign network where the mobile node is located, and the home agent uses this registered care-of address to forward information packets to the foreign network for subsequent transfer onto the mobile node. If the home agent receives an information packet addressed to the mobile node while the mobile node is located on a foreign network, the home agent will transmit the information packet to the mobile node's current location on the foreign network using the applicable care-of address. That is, this information packet containing the care-of address will then be forwarded and routed to the mobile node on the foreign network by a router on the foreign network according to the care-of address.
[0009] Multiple interfaces may be supported on a single or multiple foreign networks, which can include the different communication access types 802.1 Id, 802. Hg, HRPD, WiFi, WiMax, CDMA, or LTE apart from the circuit-switched type of telephone communication access types. Problems can be encountered when the mobile node becomes coupled to different access types on a single or multiple networks, or when hand-over procedures are performed from one access type to another access type. When mobile nodes move from one foreign network to another foreign network, problems are sometimes encountered with the registration of the care of addressing with the home agent or local mobility anchor. For instance, problems can arise with hand-off procedure for a communication when the home agent or local mobility anchor may drop packets or bill for dropped packets, which can disrupt transmissions and cause billing discrepancies, (e.g. billing the subscriber for packets that were never received). SUMMARY OF THE INVENTION
[0010] This invention provides for accurate hand-over procedures and billing of transmission packets through a new method and system for suspending and resuming downlink communication transmissions. The invention addresses the situation where a mobile node is transitioned to a new foreign network or a second access type on the same foreign network (multiple access types are supported on the foreign network), but the new foreign network does not support downlink transmissions to the mobile node. It is primary objective of this invention to provide sufficient information from the local mobility agent so the mobility access gateway (or foreign agent) can optimize the resource usage on the network and can accurately bill the subscriber for received transmission packets, as opposed to billing the subscriber for dropped packets that are never received by the mobile node.
[0011] The present invention uses a Transient Binding Option message with a suspend/resume flag setting sent to the local mobility anchor from the foreign agent that was supporting downlink transmissions to the mobile node. Namely, a transient binding option is proposed for creating a transient Binding Cache Entry (BCE) state at the home agent/local mobility anchor during an inter-MAG (Mobile Access Gateway) handover, which will suspend down-link traffic from the home agent/local mobility anchor until the transient BCE (suspend) state is cleared by the foreign agent previously supporting downlink transmissions. After the transient BCE (suspend) state is cleared, the downlink traffic from the home agent/local mobility anchor can resume with forwarding of downlink traffic to the mobile node through the foreign agent. The present invention can be implemented using a new protocol application or modified messages from prior registration applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The objects and features of the invention will become more readily understood from the following detailed description and appended claims when read in conjunction with the accompanying drawings in which like numerals represent like elements and in which:
[0013] Fig. 1 is a mobile IP-based communication system as used in the present invention showing 3GPP and non-3 GPP networks;
[0014] Fig. 2 shows a call flow diagram using the transient binding update messages and the expanded binding revocation trigger messages.
[0015] The objects and features of the invention will become more readily understood from the following detailed description and appended claims when read in conjunction with the accompanying drawings in which like numerals represent like element. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] In Figure 1, the overall architecture of the IP-based mobile system is shown with a mobile mode 125, a home network 110 and foreign networks 130 and 150, respectively. As shown in Figure 1, the home network 110 has a home agent or local mobility anchor 113. The local mobility anchor 113 is coupled to the mobility access gateway (SGW) 155 on foreign network 130 by communication link 1 12, and local mobility anchor 113 is coupled to the mobility access gateway 135 on foreign network 130 by communication link 115.
[0017] The mobility access gateway (SGW) 155 is coupled to MME 165 by communication link 166, Serving GPRS Support Node (SGSN) 168 by communication link 169, and EUTRAN server 170 by communication link 171. The Mobility Management Entry MME 165 is also coupled to the Serving GPRS Support Node (SGSN) 168 by communication link 174 and the Evolved Universal Terrestrial Radio Access Network EUTRAN server 170 by communication link 175. The home network 110 is coupled to the Internet 200 by link 201 and the Internet 200 is coupled to a foreign network FN 205 by communication link 206, which is coupled to a correspondent node (CN) 210 by link 207.
[0018] The mobility access gateway 155 is coupled to the mobile node 125 through the radio access system comprised of the base station transceiver 139 coupled to the antenna/transmitter 137 through the wireless communication link 127. The mobility access gateway 135 is coupled to the mobile node 125 through the radio access system comprised of the base station transceiver 141 coupled to the antenna/transmitter 140 through the wireless communication link 157. The mobility access gateway 135 is coupled the mobile node 125 using a second communication access type, such as a non-3GPP access type or circuit switched (CS) access, which is supported by the interface 141 and communication link 157 or CS interface 153 through communication links 152 and 154.
[0019] Mobile node 125 is shown electronically coupled to the foreign networks 130 and 150 via the wireless communication link 159 and 158, respectively. The mobile node 125, however, can communicate with any transceiver or access network coupled to a foreign network. That is, communications links 159 and 158 are radio transmitted links, but these links can be composed of any connection between two or more nodes on a network or users on networks or administrative domains.
[0020] The terms Local Mobility Anchor, home agent, and foreign agent may be as defined in the 3-GPP protocols defined by 3GPP TS23.402, but these agents are not restricted to a single protocol or system. In fact, the term home agent, as used in this application, can refer to a home mobility manager, home location register, home serving entity, or any other agent at a home network 110 having the responsibility to manage mobility-related functionality for a mobile node 125. Likewise, the term mobility access gateway, as used in this application, can refer to a foreign agent, serving mobility manager, visited location register, visiting serving entity, or any other agent on a foreign network having the responsibility to manage mobility-related functionality for a mobile node 125. The interface connections between the home agent LMA 113 and the foreign agent (MAG SGW) 155 may be defined by the S5 or S8 connections in the TS23.402 standard, and the connections between the home agent LMA 1 13 and the foreign agent (MAG SGW) 135 may be defined by the S2a and S2b connections described in the TS23.402 standard. [0021] In the mobile IP communications system shown in Figure 1, the mobile node 125 is identified by a permanent IP address. While the mobile node 125 is coupled to its home network 110, the mobile node 125 receives information packets like any other fixed node on the home network 110. When mobile, the mobile node 125 can also locate itself on foreign network, such as network 130 or 150. When located on foreign network 130 or 150, the home network 110 sends data communications to the mobile node 125 by "tunneling" the communications to the foreign network 130 or 150.
[0022] The mobile node 125 keeps the local mobility anchor 113 informed of its current location, or foreign network association, by registering a care-of address with the local mobility anchor 113. Essentially, the care-of address represents the foreign network where the mobile node 125 is currently located. If the local mobility anchor 113 receives an information packet addressed to the mobile node 125 while the mobile node 125 is located on a foreign network 130, the local mobility anchor 113 will "tunnel" the information packet to foreign network 130 for subsequent transmission to mobile node 125.
[0023] The foreign agent 155 participates in informing the local mobility anchor 113 of the mobile node 125 current care-of address. The foreign agent 155 also receives information packets for the mobile node 125 after the information packets have been forwarded to the foreign agent 155 by the local mobility anchor 113. Moreover, the foreign agent 155 serves as a default router for out-going information packets generated by the mobile node 125 while connected to the foreign network 130. The transfer of the communication packets from the home network 110 to the mobile node 125 is called downlink traffic, while the transfer of out-going communication packets from the mobile node 125 is called uplink traffic.
[0024] The mobile node 125 participates in informing the local mobility anchor 113 of its current location and requests connections to the associated foreign network. When the mobile node 125 transitions to connecting to a different access type on the foreign network or a wholly different foreign network (handover), the mobile node 125 obtains appropriate information regarding the address of the foreign network and/or the foreign agent from an agent advertisement.
[0025] When the mobile node 125 transitions to the foreign network 150, the
MME 165 will inform the foreign agent (MAG SGW) 155 that the mobile node is no longer coupled to the foreign network 130. In that situation, all downlink traffic from the foreign agent (MAG SGW) will be dropped because the mobile node 125 is no longer coupled to the foreign network 130. The home agent (LMA) 113 on the home network 110, however, may continue to transmit downlink traffic to the foreign agent (MAG SGW) 115 because the home network has not been notified of the transition of the mobile node to the foreign network 150. As such, downlink traffic will continue to flow from the home network 110, and the subscriber will be billed for that downlink traffic even though the downlink traffic is dropped and is not delivered to the mobile node 125. Further, the billing count on the home network 1 10 will not match the billing count on the foreign network 150 in this situation because the home network 110 will bill for all downlink traffic sent to the foreign network 150 but the foreign agent LMA 155 will not bill for that downlink traffic to the mobile node 125 because that traffic was dropped and not delivered, which leads to a billing irregularity that will need to be reconciled,
[0026] The invention solves this problem situation by using a Transient
Binding Option message 301 shown in Figure 2. The Transient Binding Option message 301 is prepared by the foreign agent (MAG SGW) 155 after receiving a notice message 300 from the MME 165 with an indication that the mobile node 125 has moved to a foreign network 150. In this situation, the foreign network may not support downlink traffic transmission to the mobile node 125 because of the particular access type supported on the foreign network 150. If the home network 110 continues to transmit downlink traffic to the mobile node 125 through the foreign network 130, the communications will be dropped and the billing irregularities will arise between the billing counts on the home agent LMA 113 and the billing counts on the foreign agent (MAG SGW) 155.
[0027] The Transient Binding Option message 301 is sent from the foreign agent (MAG SGW) 155 to the home agent LMA 113 with a suspend/resume flag set to the "Suspend" setting. In this instance, the "Suspend" setting of the suspend/resume flag may be valued at "1." When the home agent LMA 113 receives the suspend/resume flag in the Transient Binding Option message 301, the home agent suspends the transmission of downlink traffic for the specified session with the mobile node 125. This suspension of downlink traffic continues until the foreign agent (MAG SGW) 155 transmits a second Transient Binding Option message 305 to the home agent LMA 113 with a suspend/resume flag set to the "Resume" setting. In that instance, the mobile node 125 may be re-connected to the foreign network 130, so the downlink traffic can continue to be transmitted to the mobile node 125 through the foreign agent (MAG SGW) 155 on foreign network 130 or when the mobile node 125 is coupled to a foreign network 150 that supports an access type that will allow downlink communication transmissions. The invention eliminates the billing inconsistencies and reduces the amount of dropped transmissions to the mobile node 125.
[0028] The Transient Binding Option message can create a BCE state at the home agent LMA 113 during the inter-MAG handover. The Transient Binding Option message 301 may use a flag setting in a Proxy Binding Update message or other messages depending on the vendor specific extensions available and the access types used by the networks. The Transient Binding Option message 301 should be sent from the same foreign agent (MAG SGW) 155 that is servicing downlink traffic to the mobile node 125. When the home agent LMA 113 receives a Transient Binding Option message 301 from the same foreign agent (MAG SGW) 155 that is servicing downlink traffic, the home agent LMA 113 will determine that the downlink traffic is not subject to any handover to the foreign network 150 and the home agent LMA 113 will maintain the "Suspend" state. Upon the transmission of a "Resume" flag in a Transient Binding Option message 305 to the LMA 113, the downlink traffic shall resume transmission.
[0029] While preferred embodiments of the invention have been shown and described, modifications thereof can be made by one skilled in the art without departing from the spirit and teachings of the invention. The embodiments described herein are exemplary only, and are not intended to be limiting. Many variations and modifications of the invention disclosed herein are possible and are within the scope of the invention.
[0030] Having described the invention, we claim:

Claims

CLAIMS:
1. A method for suspension and resumption of communication transmission to a mobile node comprising the steps of: receiving a first message at a local mobility anchor from a first foreign access gateway on a first foreign network, said first message having a suspend setting, said first foreign access gateway controlling downlink transmissions to the mobile node from the local mobility anchor under a 3GPP transmission protocol, said first message prepared in response to the movement of the mobile node to a second foreign network that does not support downlink communication transmissions to the mobile node; suspending at the local mobility anchor further downlink transmissions from the local mobility anchor to the mobile node in response to receiving the first message from the first foreign access gateway controlling downlink transmissions to the mobile node; receiving a second message at the local mobility anchor from said first foreign access gateway on the first foreign network, said second message having a resume setting, said first foreign access gateway controlling downlink transmissions to the mobile node from the local mobility anchor; and, resuming at the local mobility anchor downlink transmissions from the local mobility anchor to the mobile node in response to receiving the second message from the first foreign access gateway controlling downlink transmissions to the mobile node.
2, The method of Claim 1 wherein the local mobility anchor receives a first message prepared by the first foreign access gateway in response to a notification from mobility manager that the mobile node has changed its foreign network connection to the second foreign network.
3. The method of Claim 2 wherein the mobility manager is a Mobility Management Entity.
4, The method of Claim 1 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S 5 connection in the TS23.402 standard.
5. The method of Claim 1 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S8 connection in the TS23.402 standard.
6. The method of Claim 1 wherein the interface connection between the local mobility anchor and the second foreign network are defined by the S2a or S2b connection in the TS23.402 standard.
7. A method for controlling communication transmissions to a mobile node comprising the steps of: receiving a first message at a local mobility anchor from a first foreign access gateway on a first foreign network, said first message having a suspend setting, said first foreign access gateway controlling downlink transmissions to the mobile node from the local mobility anchor, said first message prepared in response to the movement of the mobile node to a second foreign network that does not support downlink communication transmissions to the mobile node; suspending at the local mobility anchor further downlink transmissions from the local mobility anchor to the mobile node in response to receiving the first message from the first foreign access gateway controlling downlink transmissions to the mobile node; receiving a second message at the local mobility anchor from said first foreign access gateway on a first foreign network, said second message having a resume setting; and, resuming at the local mobility anchor downlink transmissions from the local mobility anchor to the mobile node in response to receiving the second message from the first foreign access gateway controlling downlink transmissions to the mobile node.
8. The method of Claim 7 wherein the local mobility anchor receives said first message prepared by the first foreign access gateway in response to a notification from mobility manager that the mobile node has changed its foreign network connection to the second foreign network.
9. The method of Claim 8 wherein the mobility manager is a Mobility Management Entity.
10. The method of Claim 7 wherein said first foreign access gateway controls downlink transmissions to the mobile node from the local mobility anchor under 3GPP protocols.
11. The method of Claim 7 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S 5 connection in the TS23.402 standard.
12. The method of Claim 7 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S8 connection in the TS23.402 standard.
13. The method of Claim 7 wherein the interface connection between the local mobility anchor and the second foreign network are defined by the S2a or S2b connection in the TS23.402 standard.
14. A communications network comprising: a home network having a local mobility anchor coupled to a first foreign network, said first foreign network having a first foreign access gateway that is connected to a mobile node, said first foreign access gateway supports downlink transmissions from the local mobility anchor to the mobile node coupled to the first foreign network, said local mobility anchor suspends downlink transmissions to the mobile node through the first foreign access gateway in response to receiving a first message having a suspend setting from said first foreign access gateway on the first foreign network, said first message being prepared by the first foreign access gateway in response to the movement of the mobile node to a second foreign network that does not support downlink communication transmissions to the mobile node; and, said local mobility anchor resumes downlink transmission from the local mobility anchor to the mobile node after receiving a second message having a resume setting from said first foreign access gateway on the first foreign network.
15. The method of Claim 14 wherein the first message is prepared by the first foreign access gateway in response to a notification from mobility manager that the mobile node has changed its foreign network connection to the second foreign network.
16. The method of Claim 15 wherein the mobility manager is a Mobility Management Entity.
17. The method of Claim 14 wherein said first foreign access gateway controls downlink transmissions to the mobile node from the local mobility anchor under 3GPP protocols.
18. The method of Claim 14 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S5 connection in the TS23.402 standard.
19. The method of Claim 14 wherein the interface connection between the local mobility anchor and the first foreign access gateway are defined by the S8 connection in the TS23.402 standard.
20. The method of Claim 14 wherein the interface connection between the local mobility anchor and the second foreign network are defined by the S2a or S2b connection in the TS23.402 standard.
PCT/US2010/034785 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging WO2010132700A1 (en)

Priority Applications (9)

Application Number Priority Date Filing Date Title
EP10775557.1A EP2430856A4 (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging
RU2011150404/07A RU2527488C2 (en) 2009-05-13 2010-05-13 Method of controlling transmission of messages to mobile node (versions) and communication network
JP2012511021A JP5508522B2 (en) 2009-05-13 2010-05-13 Suspending and resuming a session using temporary binding option messaging
US13/138,985 US9253815B2 (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging
BRPI1010599-9A BRPI1010599B1 (en) 2009-05-13 2010-05-13 method for pausing and resuming communication transmission to a mobile node, method for controlling communication transmissions to a mobile node and communications network
KR1020117029694A KR101389590B1 (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging
CA2761668A CA2761668C (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging
CN201080032448.1A CN102484823B (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging
HK12112154.3A HK1171603A1 (en) 2009-05-13 2012-11-27 Session suspend and resume using a transient binding option messaging

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US17779409P 2009-05-13 2009-05-13
US61/177,794 2009-05-13

Publications (1)

Publication Number Publication Date
WO2010132700A1 true WO2010132700A1 (en) 2010-11-18

Family

ID=43085334

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2010/034785 WO2010132700A1 (en) 2009-05-13 2010-05-13 Session suspend and resume using a transient binding option messaging

Country Status (10)

Country Link
US (1) US9253815B2 (en)
EP (1) EP2430856A4 (en)
JP (1) JP5508522B2 (en)
KR (1) KR101389590B1 (en)
CN (3) CN104994598B (en)
BR (1) BRPI1010599B1 (en)
CA (1) CA2761668C (en)
HK (1) HK1171603A1 (en)
RU (1) RU2527488C2 (en)
WO (1) WO2010132700A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111194535B (en) * 2017-10-09 2023-06-06 瑞典爱立信有限公司 Main node, auxiliary node and method executed therein

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7039404B2 (en) * 2002-06-27 2006-05-02 Intel Corporation Continuous mobility across wireless networks by integrating mobile IP and GPRS mobility agents
US20080102749A1 (en) * 2005-02-16 2008-05-01 Matsushita Electric Industrial Co., Ltd. Providing Information On The Individual Bearers' Relationships To Mobile Terminals Receiving A Multicast Or Broadcast Service
US20080130637A1 (en) * 2004-11-18 2008-06-05 Nishi Kant Maintaining Consistent Network Connections While Moving Through Wireless Networks
US7392036B2 (en) * 2002-03-01 2008-06-24 Nokia Corporation Monitoring and reporting service failures during handoff situations for adjusting subscriber billing
US20080259876A1 (en) * 2007-04-20 2008-10-23 Telefonaktiebolaget Lm Ericsson (Publ) Dormant session management associated with handover
US7471634B1 (en) * 2002-08-02 2008-12-30 Nortel Networks Limited Method for generation of a single accounting stream during heterogeneous access network mobility

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3229859B2 (en) * 1998-06-30 2001-11-19 エルジー電子株式会社 Subscriber location information management method in mobile communication system
ATE325519T1 (en) 2002-10-17 2006-06-15 Motorola Inc METHOD AND DEVICE FOR TRANSFERRING A SUBSCRIBER TERMINAL BETWEEN CELLULAR COMMUNICATION NETWORKS
US6993335B2 (en) * 2002-11-15 2006-01-31 Motorola, Inc. Apparatus and method for mobile/IP handoff between a plurality of access technologies
JP2004363730A (en) * 2003-06-02 2004-12-24 Mitsubishi Electric Corp Inter-system handover system, and mobile terminal and system
US7675885B2 (en) 2003-12-03 2010-03-09 Qualcomm Incorporated Methods and apparatus for CDMA2000/GPRS roaming
US7586847B2 (en) * 2004-03-31 2009-09-08 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for network imposed packet data flow control
US7668141B2 (en) 2004-07-06 2010-02-23 Motorola, Inc. Method and apparatus for managing packet data loss in a wireless network
US20060274672A1 (en) * 2005-06-06 2006-12-07 Narayanan Venkitaraman System and method for reducing unnecessary traffic in a network
WO2008020787A1 (en) * 2006-08-16 2008-02-21 Telefonaktiebolaget L M Ericsson (Publ) Ggsn proxy for one tunnel solution
ATE441273T1 (en) * 2006-10-13 2009-09-15 Research In Motion Ltd SYSTEM AND METHOD FOR TERMINating LOWER PRIORITY IP CONNECTIONS
US8533301B2 (en) 2007-09-19 2013-09-10 Nec Europe Ltd. Method for controlling proxy binding of a mobile node
US8413243B2 (en) * 2008-02-08 2013-04-02 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
US20110085489A1 (en) * 2008-06-10 2011-04-14 Gunar Rydnell Sae application for mbms
US8868087B2 (en) * 2008-10-20 2014-10-21 Qualcomm Incorporated Radio access technology interworking

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7392036B2 (en) * 2002-03-01 2008-06-24 Nokia Corporation Monitoring and reporting service failures during handoff situations for adjusting subscriber billing
US7039404B2 (en) * 2002-06-27 2006-05-02 Intel Corporation Continuous mobility across wireless networks by integrating mobile IP and GPRS mobility agents
US7471634B1 (en) * 2002-08-02 2008-12-30 Nortel Networks Limited Method for generation of a single accounting stream during heterogeneous access network mobility
US20080130637A1 (en) * 2004-11-18 2008-06-05 Nishi Kant Maintaining Consistent Network Connections While Moving Through Wireless Networks
US20080102749A1 (en) * 2005-02-16 2008-05-01 Matsushita Electric Industrial Co., Ltd. Providing Information On The Individual Bearers' Relationships To Mobile Terminals Receiving A Multicast Or Broadcast Service
US20080259876A1 (en) * 2007-04-20 2008-10-23 Telefonaktiebolaget Lm Ericsson (Publ) Dormant session management associated with handover

Also Published As

Publication number Publication date
HK1171603A1 (en) 2013-03-28
CN104994598B (en) 2018-09-04
BRPI1010599B1 (en) 2021-03-16
CN104994597B (en) 2018-09-04
CA2761668A1 (en) 2010-11-18
CN102484823A (en) 2012-05-30
RU2527488C2 (en) 2014-09-10
JP5508522B2 (en) 2014-06-04
KR101389590B1 (en) 2014-04-29
CN104994598A (en) 2015-10-21
EP2430856A1 (en) 2012-03-21
CN104994597A (en) 2015-10-21
BRPI1010599A2 (en) 2016-04-05
CN102484823B (en) 2015-07-01
RU2011150404A (en) 2013-06-27
US9253815B2 (en) 2016-02-02
CA2761668C (en) 2017-04-25
JP2012527192A (en) 2012-11-01
EP2430856A4 (en) 2015-08-05
KR20120027337A (en) 2012-03-21
US20120129526A1 (en) 2012-05-24

Similar Documents

Publication Publication Date Title
US9813948B2 (en) Support for continuity of tunnel communications for mobile nodes having multiple care of addressing
US8477729B2 (en) Support for multi-homing protocols using transient registration and expanded binding revocation messages
RU2530694C2 (en) Method (versions) and system providing information exchange with mobile node
US8582534B2 (en) Support for multi-homing protocols
CA2761668C (en) Session suspend and resume using a transient binding option messaging

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201080032448.1

Country of ref document: CN

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

Ref document number: 10775557

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012511021

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2761668

Country of ref document: CA

Ref document number: 8222/CHENP/2011

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20117029694

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2011150404

Country of ref document: RU

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2010775557

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 13138985

Country of ref document: US

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: PI1010599

Country of ref document: BR

ENP Entry into the national phase

Ref document number: PI1010599

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20111116