Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
  • H04W76/12—Setup of transport tunnels
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W48/00—Access restriction; Network selection; Access point selection
  • H04W48/17—Selecting a data network PoA [Point of Attachment]
• • 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 present invention relates in general to the field of mobile communications and, more particularly, to network initiated mobility management for mobile terminals.
• IP Internet Protocol
• POP Internet Protocol point of presence
• Another reason for the need of a local IP point of presence is to use localized content, where the localization could be based on the IP address.
• Another example of this is local multicast services.
• IP mobility solutions namely Mobile IP (RFC 3344, IP Mobility Support for IPv4; RFC3775, Mobility Support in IPv6)
• RFC 3344 IP Mobility Support for IPv4
• RFC3775 Mobility Support in IPv6
• SAE System Architecture Evolution
• GPRS General Packet Radio Service
• PDP packet data protocol
• the mobile terminal when the mobile terminal roams to a new network, it may perform a new attach and subsequently a new PDP context activation procedure which can allocate a local IP point of presence (i.e., local IP address) in the visited network. This typically occurs when the mobile terminal moves to a new network operator. But according to the discussion above, there is also a need to allocate a local IP point of presence, which is initiated by the network, even when the mobile terminal remains in the same network. This need is especially high in networks that span over a large geographical area, e.g. USA or China.
• MlPv ⁇ Mobile Internet Protocol version 6
• MlPv ⁇ Mobile Internet Protocol version 6
• the policy enforcement point is changed in an ongoing flow which may compromise charging and policy control enforcement.
• Policy and charging enforcement becomes more complicated because the network has to process more headers, i.e. those associated with Mobile IP.
• moving the enforcement point could also require that the Policy Control and Charging Rules Function (PCRF) node is moved which introduces a lot of complexity, namely the transfer of context from the old to the new PCRF, and selection of the current PCRF becomes difficult.
• PCRF Policy Control and Charging Rules Function
• MIPv ⁇ would require that the terminal implements the corresponding MlPv ⁇ protocol mechanisms which are assumed to be complex.
• the correspondent nodes are also required to support MIPv ⁇ route optimization. That means that the MlPv ⁇ approach works only for IPv6 compatible networks.
• the present invention provides a system, apparatus and method wherein the network initiates a PDP context activation for a second PDP context using a new IP address that can be used for new transport sessions whenever one or more operator configured criteria apply.
• the present invention can be used to: (1) route ongoing and new communication sessions from the old network device associated with the old IP address through a new network device associated with the new IP address using the old IP address; (2) route ongoing communication sessions from the old network device through the new network device using the old IP address, and new communication sessions directly through the new network device; or (3) route ongoing communication sessions from the old network device through the new network device without using the new IP address, and new communication sessions directly through the new network device.
• the UE can initiate the second Primary PDP context set up based on (specific) location information received in the broadcast information received from the base stations or initiated from a PDN GW/Serv. GW.
• the present invention allows the Third Generation Partnership Project (3GPP) core network to take control over the Gateway GPRS Support Node/Packet Data Network Gateway (GGSN/PDN GW) handover process to provide smooth handovers in the network for local breakout.
• 3GPP Third Generation Partnership Project
• GGSN/PDN GW Gateway GPRS Support Node/Packet Data Network Gateway
• PCP Policy Control and Charging
• this PDP context can also be used for IP-based mobility protocols such as Mobile IP (with or without route optimization), MIPv4, MlPv ⁇ , or Roam-IP.
• IP-based mobility protocols such as Mobile IP (with or without route optimization), MIPv4, MlPv ⁇ , or Roam-IP.
• a first embodiment of the present invention provides a method for creating a second network address for a mobile terminal having a first network address within a communications network.
• the second network address for the mobile terminal is created whenever one or more network operator criteria are satisfied.
• the second network address is provided to the mobile terminal and one or more network devices such that the second network address is used for one or more new communication sessions with the mobile terminal.
• a second embodiment of the present invention provides a method for creating a second network address for a mobile terminal having a first network address within a communications network.
• the network determines whether one or more network operator criteria associated with a mobile terminal have been satisfied. If the network operator criteria have been satisfied, the second network address for the mobile terminal is created, one or more use-based parameters are defined for the first and second network addresses, the second network address is registered with a network database, the second network address is provided to the mobile terminal and one or more applicable network devices and correspondent nodes, and the first and second network addresses are used and removed in accordance with the defined use-based parameters.
• a third embodiment of the present invention provides a network node for creating a second network address for a mobile terminal having a first network address within a communications network.
• the network node includes a communications interface communicably coupled to the mobile terminal and one or more network devices and a processor communicably coupled to the communications interface.
• the processor is configured to create the second network address for the mobile terminal whenever one or more network operator criteria are satisfied and provide the second network address to the mobile terminal and one or more network devices via the communications interface such that the second network address is used for one or more new communication sessions with the mobile terminal.
• a fourth embodiment of the present invention provides a system having a communications network and a mobile termination.
• the communications network has at least one network node and one or more network devices.
• the mobile terminal is communicably coupled to the network node and has a first network address.
• the network node has a processor configured to create a second network address for the mobile terminal whenever one or more network operator criteria are satisfied and provide the second network address to the mobile terminal and at least one of the network devices such that the second network address is used for one or more new communication sessions with the mobile terminal.
• FIGURE 1 is a flow chart illustrating a method for creating a second network address for a mobile terminal having a first network address within a communications network in accordance with a first embodiment of the present invention
• FIGURE 2 is a flow chart illustrating a method for creating a second network address for a mobile terminal having a first network address within a communications network in accordance with a second embodiment of the present invention.
• FIGURES 3A, 3B and 3C show a system and network nodes operating in accordance with various embodiments of the present invention.
• the present invention provides a system, apparatus and method wherein the network initiates a PDP context activation for a second PDP context using a new IP address that can be used for new transport sessions whenever one or more operator configured criteria apply.
• the present invention can be used to: (1) route ongoing and new communication sessions from the old network device associated with the old IP address through a new network device associated with the new IP address using the old IP address; (2) route ongoing communication sessions from the old network device through the new network device using the old IP address, and new communication sessions directly through the new network device; or (3) route ongoing communication sessions from the old network device through the new network device without using the new IP address, and new communication sessions directly through the new network device.
• the UE can initiate the second Primary PDP context set up based on (specific) location information received in the broadcast information received from the base stations or initiated from a PDN GW/Serv. GW.
• the present invention allows the Third Generation Partnership Project (3GPP) core network to take control over the Gateway GPRS Support Node/Packet Data Network Gateway (GGSN/PDN GW) handover process to provide smooth handovers in the network for local breakout.
• 3GPP Third Generation Partnership Project
• GGSN/PDN GW Gateway GPRS Support Node/Packet Data Network Gateway
• PCP Policy Control and Charging
• this PDP context can also be used for IP- based mobility protocols such as Mobile IP (with or without route optimization, MIPv4 (see RFC 3344, IP Mobility Support for IPv4) or MIPv6 (see RFC3775, Mobility Support in IPv6) or Roam-IP (see Z. R. Turanyi, Cs. Szab ⁇ , E. Kail, A. G. Valk ⁇ , "Global Internet Roaming with ROAMIP,” ACM Mobile Computing arid Communications Review (MCCR), Vol. 4, No. 3, p. 58-68., July 2001; Zoltan Turanyi, Andras G.
• MIPv4 see RFC 3344, IP Mobility Support for IPv4
• MIPv6 see RFC3775, Mobility Support in IPv6
• Roam-IP see Z. R. Turanyi, Cs. Szab ⁇ , E. Kail, A. G. Valk ⁇ , "Global Internet Roaming with ROAMIP," ACM Mobile Computing arid Communications Review (MCCR), Vol. 4,
• Roam-IP is a global mobility architecture that uses application layer solutions for global reachability and reuses transparent tunneling mechanisms to ensure session continuity.
• the present invention and Roam-IP on application layer solutions for reachability. As discussed in the references cited above, most applications have their own registration mechanisms which eliminate the need to provide reachability at a permanent IP address (which is a feature of Mobile IP).
• While Roam-IP provides solutions for how to maintain session continuity even when the user hands over from one network to another, it does not consider how a local IP point of presence can be provided in a mobile network spanning a large coverage area.
• the present invention can be regarded as being complementary to Roam-IP such that a network operator may use both the present invention and Roam-IP, or any one of them.
• FIGURE 1 a flow chart illustrating a method 100 for creating a second network address for a mobile terminal having a first network address within a communications network in accordance with a first embodiment of the present invention is shown.
• the second network address for the mobile terminal is created whenever one or more network operator criteria are satisfied in block 102.
• the first and second network addresses can be an Internet Protocol (IP) point of presence, identifier or combination of data that can be used to properly route traffic to the mobile terminal.
• IP Internet Protocol
• the mobile terminal also referred to as user equipment (UE), can be a phone, personal data assistant (PDA), computer or other mobile communications device.
• PDA personal data assistant
• the one or more network operator criteria may include a movement of the mobile terminal within a home public land mobile network (PLMN) or to a new visited PLMN, a traffic type associated with the first network address, a traffic quality associated with the first network address, a traffic quantity associated with the first network address, a determination that the first network address is not local enough for the one or more new communication sessions or a combination thereof.
• the second network address can be created by initiating a packet data protocol (PDP) context activation by a network node or the mobile terminal.
• PDP packet data protocol
• the mobile station initiates the PDP context activation after receiving a specific location information in a broadcast from a base station or initiated from a PDN GW/Serv. GW.
• the network instructs the mobile terminal to initiate the PDP context activation. Thereafter, the second network address is provided to the mobile terminal and one or more network devices such that the second network address is used for one or more new communication sessions with the mobile terminal in block 104.
• the one or more network devices may include a database, a correspondent node, a Gateway General Packet Radio Service Support Node (GGSN) or a PDN GW/Serv. GW.
• GGSN Gateway General Packet Radio Service Support Node
• PDN GW/Serv. GW PDN GW/Serv.
• the use of the second network address and continued use of the first network address can fixed or dynamically determined by the network operator.
• the network operator is free to configure the present invention to determine how and when both ongoing and new communication sessions should be routed to the mobile terminal via the first network address, the second network address or a combination thereof.
• the first network address can be mandatory for one or more ongoing communication sessions, optional for the one or more ongoing communication sessions, or used only for one or more specific applications.
• the second network address can be mandatory for the one or more new communication sessions, optional for the one or more new communication sessions, or used only for one or more specific applications.
• the second network address can also be used for tunneling traffic from the first network address, a network node (e.g., a Gateway General Packet Radio Service Support Node (GGSN) or a Packet Data Network Gateway/Serving Gateway (PDN GW/Serv. GW)), or an anchor point to the second network address.
• a network node e.g., a Gateway General Packet Radio Service Support Node (GGSN) or a Packet Data Network Gateway/Serving Gateway (PDN GW/Serv. GW)
• PDN GW/Serv. GW Packet Data Network Gateway/Serving Gateway
• the second network address will be typically maintained as long as the mobile terminal is connected to the communications network, until the mobile terminal moves to a new communications network or until a specified period of time has elapsed.
• the second network address can be used for a local breakout of Internet Protocol (IP) traffic or with one or more IP-based mobility protocols (e.g., Mobile IP with route optimization, Mobile IP without route optimization, MIPv4, MIPv ⁇ , Roam IP or a combination thereof).
• IP Internet Protocol
• IP-based mobility protocols e.g., Mobile IP with route optimization, Mobile IP without route optimization, MIPv4, MIPv ⁇ , Roam IP or a combination thereof.
• the use-based parameters define how and when the first and second network addresses with be used with ongoing and new communication sessions, and when they will be removed.
• the application of the use-based parameters can be fixed or dynamically determined by the network operator.
• the first network address can be mandatory for one or more ongoing communication sessions, optional for the one or more ongoing communication sessions, or used only for one or more specific applications.
• the second network address can be mandatory for the one or more new communication sessions, optional for the one or more new communication sessions, or used only for one or more specific applications.
• the second network address can also be used for tunneling traffic from the first network address, a network node, or an anchor point to the second network address.
• the first network address will be removed after a specified period of time, a traffic threshold is reached or a combination thereof.
• the second network address will be typically maintained as long as the mobile terminal is connected to the communications network, until the mobile terminal moves to a new communications network or until a specified period of time has elapsed.
• the second network address is registered with a network database in block 210 and provided to the mobile terminal and one or more applicable network devices and correspondent nodes in block 212. Thereafter, the first and second network addresses are used and removed in accordance with the defined use-based parameters in block 214.
• the present invention provides support in the 3GPP core network for local breakout solutions by initiating a PDP context activation procedure for a local IP point of presence.
• a PDP context activation procedure for a local IP point of presence.
• the same mechanisms can be used both within a home PLMN and in the roaming case when the user moves to a new visited PLMN.
• a tunneling mechanism is in place which tunnels traffic to and from the existing IP point of presence where the existing IP address is allocated.
• the trigger for the activation of the new PDP context is the mobility of the user, which may be both mobility within the same PLMN, or roaming to a new PLMN
• the selection of "home PDN GW” (or GGSN, since this can be applied on 2G and 3G GPRS also) is decided by the local Serving GPRS Support node (SGSN)/MME and the domain name service (DNS) configuration for access point names (APN).
• SGSN Serving GPRS Support node
• DNS domain name service
• the new SAE system may use new mechanisms for the selection of a PDN GW/Serv.
• GW node in the MME other than the current DNS lookup mechanism.
• the APN name needs to be available at the new SGSN (either retrieved from the SGSN context response (for legacy it is hidden in the PDP context, for new messages this info must be available), or alternatively from the UE) in order to support the present invention with handovers between operators (handovers between operators are rarely or maybe never used today). If the APN name is available, then the local GGSN/PDN GW or SGSN/MME can decide whether new PDP contexts shall be allocated locally or traffic shall be tunneled to the old GGSN/PDN GW. It is not required to support this between PLMNs but by using the same tunneling solution between PLMNs and within PLMNs it is possible to support that scenario also.
• the network initiates a PDP context activation of another PDP context with a new IP address (using the standard network requested PDP context activation procedure, in 3GPP 23.0606, or an evolution thereof), when the old GGSN or PDN GW is not considered to be local enough for the traffic.
• This is defined by operator configured criteria.
• the MME/SGSN may or may not change as a result of the change in the PDN GW/Serv. GW /GGSN.
• the new PDP context may be used for new transport sessions, i.e. all new connections to different applications, p-2-c or p-2-p based.
• the new IP address may also be used for tunneling of traffic from another node, such as the previous GGSN or PDN GW/Serv. GW, or from any anchor point.
• the tunneling protocol/solution may be Mobile IPv4, Mobile IPv6 or any other mobility protocol using the new IP address as tunnel end-point.
• the system includes a communications network 300 and a mobile terminal 302.
• the communications network 300 has at least one region (e.g., Region A and Region B), at least one network node (e.g., PDN GW/Serv. GW home address 304, PDN GW/Serv. GW foreign address 306 or other network node) and one or more network devices (not shown).
• the mobile terminal 302 is communicably coupled to the network node 304 and has a first network address 308.
• the applicable network node has a processor configured to create a second network address 310 for the mobile terminal 300 whenever one or more network operator criteria are satisfied and provide the second network address 310 to the mobile terminal 302 and at least one of the network devices (e.g., PDN GW/Serv.
• the network node also includes a communications interface communicably coupled to the mobile terminal 302 and one or more network devices.
• FIGURE 3A 1 a tunneling protocol/solution for Mobile IPv4 using the present invention is shown.
• the ongoing communication session (path 314) prior to initiation of the second network address 310 is between the mobile terminal 302, the home PDN GW/Serv. GW 304 and the correspondent node 312.
• the ongoing communication session and any new communication sessions (path 316) are routed from the home PDN GW/Serv. GW 304 and through the foreign PDN GW/Serv. GW 306 (care-of address) using the second network address 310.
• Triangular routing 318 is possible with MIPv4, but it optimizes the uplink only and makes firewall configuration and policy enforcement very difficult.
• the ongoing communication session (path 314) prior to initiation of the second network address 310 is between the mobile terminal 302, the home PDN GW/Serv. GW 304 and the correspondent node 312.
• the ongoing communication session is routed from the home PDN GW/Serv. GW 304 and through the foreign PDN GW/Serv.
• GW 306 care-of address
• the second network address 310 path 316
• any new communication sessions path 320
• GW 306 (care-of address) using the second network address 310 are optimally routed by MIPv6 directly through the foreign PDN GW/Serv.
• the ongoing communication session (path 314) prior to initiation of the second network address 310 is between the mobile terminal 302, the home PDN GW/Serv. GW 304 and the correspondent node 312.
• the ongoing communication session is routed from the home PDN GW/Serv. GW 304 through the foreign PDN GW/Serv. GW 306 (care-of address) without using the second network address 310 (path 322), and any new communication sessions (path 324) are routed directly through the foreign PDN GW/Serv. GW 306 (care-of address) using the second network address 310.
• the Gn/Gp interface between SGSN and GGSN (alternatively that the inter PDN GW/Serv. GW interface in SAE/LTE) is used for traffic to/from the old IP address 308 for already ongoing communications.
• the UE 302 shall use the new IP address 310 allocated from the new GGSN or PDN GW. This can be achieved e.g., by having different routing costs or by having explicit support for this mechanism in the UE 302 TCP/IP stack.
• the network can then include mechanism, either timer based or traffic measurement based, that eventually removes the old IP address 308 through the GGSN initiated delete of PDP context (or evolved version thereof).
• the new IP address 310 in the new GGSN or PDN GW for SAE is kept as long as the UE 302 is still connected to the network, or until the UE 302 moves to the next location where a Local Breakout (LBO) is needed.
• LBO Local Breakout
• the network may provide additional information on how the new address should be used, i.e., whether to use it for all applications or only specific ones, whether it is mandatory or optional to use it, whether Mobile IP can be used with the address (without or with route optimization) whether the other addresses will be deleted, and so on. Note that it is possible that some of the traffic is using the local IP address while the rest of the traffic is using the IP address from the original IP point of presence, e.g., in the roaming scenario it may be possible that the home operator allows only some of the traffic to be local (e.g., only emergency traffic or only internet traffic is allowed to be broken out locally).
• the UE can initiate the second Primary PDP context activation based on (specific) location information received in the broadcast information received from the base stations or initiated from a PDN GW/Serv. GW.
• the location information is either based on the Routing/tracking area (or similar, e.g., using some bits of the routing/tracking area identifier) but then the UE needs to know at which RA change the new primary PDP context shall be set up.
• the more realistic approach seems to be that an additional information is added to the broadcast message with some identity of the regions where a local GGSN/PDN GW close to the base station can be selected.
• the mobile terminal can take advantage of the new IP address in several ways.
• an IP application starts a new transport session, it asks for a new socket connection from the operating system of the terminal.
• the operating system assigns an IP address for the socket connection. Thereby the operating system has control over which IP address is being used by new connections. Whenever a new, local IP address is assigned to the terminal, new connections can start using this new address.
• IP address can be registered in a server together with an application- level id.
• the allocation of a new IP address can trigger such a registration process, making user that the application will start using the new IP address.
• IP address could in theory be problematic for applications in some rare cases, most applications can handle the loss of connectivity at an old IP address and automatically re-establish connectivity at a new IP address. Note that this is needed not only for local breakout, but also to handle cases when network connectivity may go up and down. Furthermore, many network operators, e.g. broadband operators do not allow users to keep the same IP address for extended periods of time (e.g., more than a day), which is another reason why applications already today need to prepare for a change of the IP address.

Applications Claiming Priority (3)

Publications (1)

Family

ID=38474139

Family Applications (1)

Country Status (4)

Families Citing this family (39)

Family Cites Families (9)

• 2007
  • 2007-04-25 CN CN2007800147377A patent/CN101427546B/zh active Active
  • 2007-04-25 EP EP07734398A patent/EP2011307A1/de not_active Withdrawn
  • 2007-04-25 WO PCT/IB2007/001080 patent/WO2007129167A1/en active Application Filing
  • 2007-04-25 US US11/739,950 patent/US8447302B2/en active Active

Non-Patent Citations (5)

Also Published As

Similar Documents

Legal Events