Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/14—Backbone network devices
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections
• • 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]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/02—Terminal devices
  • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
  • H04W88/18—Service support devices; Network management devices
  • H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy

Definitions

• the present invention generally relates to mobile communication networks and systems.
• a mobile terminal also called Mobile Station MS, or User Equipment UE
• mobile services such as in particular 3GPP services
• mobile services such as in particular 3GPP services
• 3GPP services There are different types of mobile services such as in particular Circuit Switched (CS) services and Packet Switched (PS) services
• the CN comprises different domains such as in particular a CS domain and a PS domain.
• CS Circuit Switched
• PS Packet Switched
• Mobile services have traditionally been delivered to Mobile Stations via an Access Network corresponding to a Radio Access Network RAN, allowing relatively high mobility but at relatively high cost for the users.
• RAN Typical examples of RAN are GERAN (GSM/EDGE Radio Access Network, where EDGE stands for Enhanced Data rates for GSM Evolution, and GSM stands for Global System for Mobile communications) and UTRAN (UMTS Terrestrial Radio Access Network, where UMTS stands for Universal Mobile Telecommunication System).
• GSM/EDGE Radio Access Network where EDGE stands for Enhanced Data rates for GSM Evolution, and GSM stands for Global System for Mobile communications
• UTRAN UMTS Terrestrial Radio Access Network, where UMTS stands for Universal Mobile Telecommunication System.
• GERAN GSM/EDGE Radio Access Network
• UTRAN UMTS Terrestrial Radio Access Network
• G Generic Access
• UMA Unlicensed Mobile Access
• Generic Access is an extension of GSM/GPRS mobile services into the customer's premises that is achieved by tunnelling certain GSM/GPRS protocols between the customer's premises and the Core Network over broadband IP network, and relaying them through an unlicensed radio link inside the customer's permises.
• GAN includes a Generic Access Network Controller (GANC).
• GANC Generic Access Network Controller
• a Generic IP Access network provides connectivity between the MS and the GANC.
• a single interface, 1he Up interface, is defined between the GANC and the MS.
• the GANC appears to the CN as a BSS (Base Station Subsystem) of GERAN. It includes a Security Gateway (SEGW) that terminates secure remote access tunnels from the MS, providing mutual authentication, encryption and data integrity for signalling, voice and data traffic.
• SEGW Security Gateway
• the GANG is interconnected with the CN via the standardized interfaces (i.e. A-interface and Gb-interface) defined for GERAN A/Gb mode.
• the PS Domain Control Plane GAN protocol architecture is recalled in figure 2 taken back from 3GPP TS 43.318.
• the PS Domain User Plane GAN protocol architecture is recalled in figure 3 taken back from 3GPP TS 43.318.
• the PS domain MS architecture is recalled in figure 4 taken back from 3GPP TS 43.318.
• the present invention more particularly relates to enhancements to Generic
• E-GAN Enhanced Generic Access Network
• HIS One Tunnel Mode where HSI stands for High Speed Internet
• E-GAN protocol architecture is recalled in figure 5 for PS Domain User Plane. Protocols at the Up-interface between MS and E-GANC include, from higher to lower layers: - GRE,
• Protocols at the Gn-interface between E-GANC and GGSN include, from higher to lower layers:
• Protocols at the MS-GGSN interface include:
• Protocols at the interface between MS and an Application Server include:
• GRE Generic Routing Encapsulation, a description of which can be found in particular in RFC 2890 published by IETF (Internet Engineering Task Force).
• Protocols at the Up-interface between MS and E-GANC include, from higher to lower layers:
• Protocols at the Gn-interface between E-GANC and GGSN include, from higher to lower layers:
• the Session Management (3GPP TS 24.008) SM protocol is enhanced (W- SM) with some information related to the GRE tunnel management (exchange of the keys IE used in the GRE tunnel).
• the present invention addresses the problem of seamless mobility between UMA (enhanced Generic Access or HSI One Tunnel mode) and GPRS/UMTS.
• UMA enhanced Generic Access or HSI One Tunnel mode
• GPRS/UMTS GPRS/UMTS
• a solution that could be used to provide the seamless mobility is inter-system Gn mobility as defined in 3GPP TS 24.008 and 29.060.
• the inter-system mobility defines how to transfer a MS from a GPRS/UMTS system to an other.
• the two systems exchange information about the PDP contexts activated by the MS.
• This information are mainly radio related information, location information (RAI) and MS identifier (P-TMSI, TLLI)
• RAI location information
• P-TMSI MS identifier
• the RNC and the BSS nodes are impacted by the mobility in order not to loose traffic.
• the equivalent of these nodes on the Wifi side are the Wifi access points which have not the RNC and BSS feature for mobility. It is not conceivable to request the Wifi access points to integrate such features because they are not 3GPP defined nodes. The consequence is that some traffic could be lost.
• MIP Mobile IP Protocol
• Mobile IP is specified by IETF. It is recalled that Mobile IP allows a MN (Mobile Node) to maintain connectivity to an external PDN using a single and unchanging address (its home address) even when the link layer point of attachment is changing.
• MN Mobile Node
• IP address the Care Of Address COA in Colocated mode or with the Foreign Agent Adress in FA mode
• the HA intercepts packets addressed to the MN's home address and tunnels these packets to the COA.
• GGSN With MIP, GGSN would require FA feature. However, some GGSN do not have this feature, and it is not foreseen to implement any new feature on them.
• HA nodes should be deployed in the access networks. These nodes would be bottlenenecks for traffic. Operators are currently asking to reduce the number of nodes and this solution adds one.
• MIP requires to implement a MIP client in the MS. Any way our solution also requires a specific client. This is not an issue. But the problem with the MIP solution is that a MIP client should be instanciated for each APN. This is memory and CPU consuming. It is an object of the present invention to solve part or all of such problems, or to avoid part or all of such drawbacks.
• a Proxy-Gn entity for mobility between UMA access and GPRS/UMTS access said Proxy-Gn entity anchoring a PDP context for a Mobile Station MS whatever the access type UMA or GPRS/UMTS for this MS, said anchored PDP context having three terminations, two access terminations and one network termination:
• - GPRS/UMTS access termination which receives GTP control messages from a SGSN
• - UMA access termination which receives Session Management requests from the MS
• - Network termination which is the termination towards a GGSN, and which owns the IP address allocated to the MS.
• a Proxy-Gn entity for mobility between UMA access and GPRS/UMTS access said Proxy-Gn entity anchoring a PDP context for a Mobile Station MS whatever the access type UMA or GPRS/UMTS for this MS, said Proxy-Gn entity exchanging information with the MS, by inserting said information in containers in the Protocol Configuration Options PCO Information Element IE of signalling messages.
• a Mobile Station MS comprising a UMA Multi-Access Client introduced between its Application layer and Non Access Stratum layer, such that:
• the Service Access Points SAPs between the Application layer and the UMA Multi-Access Client correspond to the SAPs SMREG-SAP, and SN-SAP(xn) for GPRS or RABl -SAP... RABn-SAP for UMTS, of GPRS/UMTS MS protocol architecture,
• the Service Access Points SAPs between the UMA Multi-Access Client and the SM and SNDCP layers correspond to the SAPs SMREG-SAP, and SN-SAP(xn) for GPRS or RABI -SAP... RABn-SAP for UMTS, of GPRS/UMTS MS protocol architecture,
• WSMREG-SAP Service Access Point
• Unlicensed Access, IP transport, and IPSec layers of UMA MS protocol architecture - ⁇ Service Access Point WRAB-SAP is introduced, for User Plane, between the UMA Multi-Access Client and a GRE layer introduced above the Unlicensed Access, IP transport, and IPSec layers of UMA MS protocol architecture.
• a Mobile Station MS comprising a UMA Multi Access Client introduced above its Non Access Stratum layer, said UMA Multi Access Client exchanging information with a Proxy-Gn entity anchoring a PDP context for the MS whatever the access type UMA or GPRS/UMTS for this MS, by inserting said information in containers in the Protocol Configuration Options PCO Information Element IE of signalling messages.
• figure 1 is intended to recall GA architecture
• figure 2 is intended to recall the PS domain control plane GAN protocol architecture
• figure 3 is intended to recall the PS domain user plane GAN protocol architecture
• fugure 4 is intended to recall the PS domain GA MS architecture
• figure 5 is intended to illustrate the PS domain user plane E-GAN protocol architecture
• figure 6 is intended to illustrate the PS domain control plane E-GAN protocol architecture
• figure 7 is intended to illustrate a solution using MIP
• figure 8 is intended to illustrate a 2G MS protocol architecture according to the present invention
• figure 9 is intended to illustrate a 3G MS protocol architecture according to the present invention
• figure 10 is intended to illustrate an E-GANC architecture according to the present invention
• - figure 1 1 is intended to illustrate an example of system architecture using the present invention
• figure 12 is intended to illustrate a logical PDP context according to the present invention
• figure 13 is intended to illustrate a procedure for PDP context activation on GPRS access, according to the present invention
• figure 14 is
• figure 20 is intended to illustrate a third example of a procedure for PDP context de-activation on GPRS side, according to the present invention
• - figure 21 is intended to illustrate a first example of a procedure for PDP context de-activation on Wifi (UMA) side
• figure 22 is intended to illustrate a second example of a procedure for PDP context de-activation on Wifi (UMA) side
• figure 23 is intended to illustrate a third example of a procedure for PDP context de-activation on Wifi (UMA) side, according to the present invention.
• a protocol architecture for a handset (or MS) according to the present invention is illustrated in figure 8 for a 2G/1T MS, and in figure 9 for a 3G/1T MS (where IT stands for "One Tunnel HSI mode").
• UMA Multi-Access Client A specific client, called UMA Multi-Access Client is introduced above the Non Access Stratum of the handset. This is the same client for 2G and 3G handset.
• the SM and SNDCP layers (of the protocol architecture for 2G/GPRS or 3G/UMTS as specified in particular in 3GPP TS 24.007) see the UMA Multi-Access Client as an application.
• the Service Access Points SAPs between the SM, SNDCP layers and the UMA Multi-Access Client are the SAPs as specified in 3GPP TS 24.007, i.e. : SMREG-SAP, and SN-SAP(xn) for 2G or RABl -SAP... RABn-SAP for 3G.
• a Service Access Point WSMREG-SAP is introduced between UDP layer (of the protocol architecture of 1 T/UMA) and the Multi-Access Client, for Control Plane.
• a Service Access Point WRAB-SAP is introduced between GRE layer (of the protocol architecture of 1T/UMA) and the Multi-Access Client, for User Plane.
• FIG. 10 An architecture for a E-GANC according to the present invention is illustrated in figure 10.
• the E-GANC comprises the following entities: SGW (Security Gateway), W- SM entity, Proxy-Gn entity.
• SGW Security Gateway
• W- SM entity W- SM entity
• Proxy-Gn entity Proxy-Gn entity.
• IPSec tunnel different flows inside this IPSec tunnel include W-SM signalling (Control Plane) and GRE tunnel (User Plane),
• W-SM' Control Plane
• GRE User Plane
• - W-SM and GGSN communicate using GTP-U (User Plane).
• GTP-U User Plane
• - MS and SGSN communicate using SM (Control Plane) and PDCP or
• FIG. 1 1 An example of system architecture using the present invention is illustrated in figure 1 1 .
• the system comprises:
• MS Mobile Station
• GSM BSC 3GPP RAN
• UMTS RNC 3GPP RAN
• GAN comprises:
• CN comprises: - Voice Core Network (CN part handling CS services), comprising MSC nodes connected to 3GPP RAN and to GANC-CS via A-interface, Packet Core Network (CN part handling PS services), comprising GGSN nodes (connected to other networks or subnetworks, such as PDN or IMS (IP Multimedia Subsystem) and SGSN nodes connected to 3GPP RAN via Gb-interface and lu-ps interface,
• CN part handling CS services comprising MSC nodes connected to 3GPP RAN and to GANC-CS via A-interface
• Packet Core Network CN part handling PS services
• GGSN nodes connected to other networks or subnetworks, such as PDN or IMS (IP Multimedia Subsystem)
• IMS IP Multimedia Subsystem
• HLR Home Location Register
• - on 2G/GPRS or 3G/UMTS access interface between MS and GSM BSC or UMTS RNC - interface Gb between GSM BSC and SGSN or lu-ps interface between UMTS RNC and SGSN - interface Gn between SGSN and EGANC-PS.
• the mobility is based on the UMA Multi-access Client of the MS and the Proxy-Gn function of the E-GANC.
• the Proxy-Gn is the anchor of the PDP context.
• the present invention proposes to have in the E-GANC an anchor of the PDP context in the control plane whatever the access type is, as illustrated in figure 12.
• the E-GANC handles a logical PDP context per MS PDP context.
• the logical PDP context has 3 terminations: 2 access and 1 network terminations:
• PDP context in the E-GANC exchange some information by inserting them in the Protocol Configuration Options PCO Information Element IE of the signaling messages :
• o SM messages 3GPP TS 24.008) between MS and SGSN o Gn messages (3GPP TS 29.060) betwwen SGSN and Proxy- Gn .
• Wifi (UMA) side o W-SM messages.
• Information are carried in the PCO IE as new containers. New container identifiers are defined: o GN_ADDR: contains the IP address of the Proxy-Gn anchoring the
• PDP context o MOBILITYJNFO contains the preferred or requested access mode on which to switch the traffic.
• the access node When a MS first activates a PDP context, the access node (SGSN / W-SM of the E-GANC) chooses a Proxy-Gn according to its own criteria.
• the Proxy-Gn may delegate to an other Proxy-Gn the activation request for load reasons.
• the Proxy-Gn that anchors the PDP context sets its IP address in a new specific container inside the Protocol Configuration Options field of the activation response: GN_ADDR.
• Protocol Configuration Options field is up-warded unchanged up to the MS, so the MS UMA Multi-access Client learns the IP address of the Proxy-Gn for this PDP context.
• the MS UMA Multi-access Client When activating the same PDP context on an other access type, the MS UMA Multi-access Client sets the IP address of the Proxy-Gn for this PDP context in the GN_ADDR container of the Protocol Configuration Options field of the activation request. This field is interpreted by the E-GANC in order to forward the request to the relevant Proxy-Gn.
• An other container MOBiLITYJNFO within the Protocol Configuration Options field is used for driving the mobility from one access to an other.
• This container can be sent either in the Activate PDP context or/and the Modify PDP context. That container contains the preferred or requested access.
• the current Radio Access in use is 2G (or 3G), the UMA Multi-access Client forwards the PDP context activation towards the SM layer.
• This PDP context has not yet been activated on any access, and so: no GN__ADDR container is set in the Protocol Configuration Options field, 2)
• the SM layer of the MS requests a PDP context activation,
• the SGSN has to forward the PDP context activation request as a Gn create PDP context request.
• the destination IP address of this request is found thanks to a DNS query on the APN.
• This APN has so to be specific for LJMA MS with mobility.
• the SGSN retrieves a list of Proxy-Gn IP addresses.
• the Proxy-Gn receives the PDP context creation request without GN_ADDR container within the PCO information. It resolves the APN to find out a GGSN IP address, and forwards the request to the GGSN: a.
• the IP address and TEID for GTP-C are those of the Proxy-Gn; b.
• the IP address and TEID for GTP-U are ihose provided by the SGSN.
• the GGSN creates the PDP context and returns back the create PDP context response containing: the IP address allocated for the MS on this APN (if that field was empty in the request) - a TEID and an IP address for control plan, a TEID and an IP address for user plan, eventually some Protocol Configuration Options,
• the GGSN may now forward downlink traffic towards the SGSN. 6)
• the Proxy-Gn sends back the create PDP context response but: replaces the control TEID and IP address of the GGSN by its own control TEID and IP address, creates a Protocol Configuration Options field or appends to the existing
• Protocol Configuration Options field a GN_ADDR container set with Proxy-Gn IP address.
• the SGSN sends back to the MS the activate PDP accept with the Protocol Configuration Options as received.
• the SM layer of the MS receives the PDP activate response, and upwards to the UMA Multi-access Client of the MS a confirmation.
• the UMA Multi-Access Client learns from the Protocol Configuration Options field the address of the Proxy-Gn that is the anchor for the MS in the PS domain.
• the Application requests the activation of a PDP context.
• the UMA Multi-access Client selects a GRE tunnel key for the user plane (downlink traffic), since there is no anchor for the MS, the PDP context activation is submitted to the E-GANC (W- SM layer) without GN_ADDR container (within PCO IE).
• the IP address of the W- SM entity is the IP address that has been returned to the MS at the IPSec tunnel set-up time.
• the W-SM performs the User Authorization for that APN (transaction with the AAA server on Wm interface).
• the W-SM selects a key for the GRE tunnel for the uplink traffic and a TEID (downlink) for the Gn side. Then it sends a create PDP context request to its local Proxy-Gn.
• the Proxy-Gn receives the PDP context creation request without GN_ADDR container in the PCO IE, so it selects itself as the anchor point for all PDP contexts coming from that MS. It resolves the APN to find out a GGSN IP address, and forwards the request to the GGSN.
• Proxy-Gn may forward the request to another Proxy-Gn.
• the GGSN creates the PDP context and returns back the create PDP context response containing: - the IP address allocated for the MS on this APN, a TEID and an IP address for control plan, a TEID and an IP address for user plan, eventually some Protocol Configuration Options,
• Proxy-Gn sends back the create PDP context response but: replaces the control TEID and IP address of the GGSN by its own control TEID and IP address, creates a Protocol Configuration Options field or appends to the existing Protocol Configuration Options field a GN_ADDR container set to its IP address.
• the W-SM sends back to the MS the activate PDP context accept with the Protocol Configuration Options as received as well as its GRE tunnel key.
• the UMA Multi-access Client of the MS learns from the Protocol Configuration Options of the response the IP address of the Proxy-Gn that anchors the MS in the PS domain.
• the MS formats a W-activate PDP request: the Protocol Configuration Options field contains the GN_ADDR container set to the value of the IP address of the Proxy-Gn handling the PDP context.
• the Protocol Configuration Options field contains the MOBILITYJNFO container indicating that Wifi should be used for user plane.
• the GRE tunnel key is chosen by the UMA Multi-access Client and set in the request.
• the MS sends the request to the W-SM IP address that was previously given by the SGW when the IPSec tunnel has been set up.
• the W-SM entity of the E-GANC receives the PDP context activation request, gets the IP address of the Proxy-Gn (GN_ADDR of PCO IE) and sends a PDP context create request toward this Proxy-Gn keeping the PCO IE unchanged.
• the Proxy-Gn retrieves the PDP context (based on IMSI and NSAPI values). Since the MOBILITYJNFO container indicates that Wifi must be used for user plane, the Proxy-Gn updates the GGSN with the user plane IP address and TEID given by the W-SM. Note : if the MOBILITYJNFO container is not present, the Proxy-Gn creates the UMA access termination (internal PDP context), but does not request an update PDP context towards the GGSN.
• the GGSN updates the user plan with the new TEID and IP address and responds to the Proxy-Gn.
• the traffic now flows down on the Wifi side.
• the Proxy-Gn sends back to the W-SM the GGSN IP address and TEID to use for uplink traffic as well as the Proxy-Gn IP address and TEID to use for control plane, ⁇ )
• the W-SM returns back the W-activate PDP context response adding its GRE key for uplink traffic.
• the UPMAC layer forwards user traffic (SN-SAP and SN-RAB) on the Wifi side by encapsulating these user frames in the GRE tunnel with the key provided by the EGANC. Switching from Wifi/UMA access to GPRS access when PDP context present on Wifi/UMA side only (figure 16) Initial conditions:
• the MS is under GPRS coverage.
• the current radio access is Wifi and the MS is going to move to GPRS.
• the PDP context has already been activated on UMA side but not on GPRS side.
• the LJMA Multi-Access Client of the MS requests PDP context activation to the SM layer: the Protocol Configuration Options field contains the GN_ADDR container set to the value of the IP address of the Proxy-Gn handling the PDP context.
• Protocol Configuration Options field contains the MOBI UTYJ N FO container indicating that GPRS/UMTS should be used for user plane.
• the SM layer of the MS sends to the SGSN a PDP context activation request with the received PCO.
• the SGSN has to forward the PDP context activation request as a Gn create PDP context request.
• the destination IP address of this request is found thanks to a DNS query on the APN.
• This APN has so to be specific for UMA MS with mobility.
• the SGSN retrieves a list of Proxy-Gn IP addresses.
• the Proxy-Gn chosen by the SGSN receives the PDP context activation request , gets the IP address of the Proxy-Gn (GN_ADDR of PCO IE) and sends a PDP context create request toward this Proxy-Gn keeping the PCO IE unchanged.
• the Proxy-Gn previously chosen on Wifi side retrieves the PDP context (based on IMSI and NSAPI values). Since the MOBILITYJNFO container indicates that GPRS(UMTS) must be used for user plane, the Proxy-Gn updates the GGSN with the user plane IP address and TEID provided by the SGSN. ⁇ ) The GGSN updates the user plan with the new TEID and IP address and responds to the Proxy-Gn. The user traffic now flows down directly to the
• the Proxy-Gn returns back to the SGSN the GGSN IP address and TEID to use for uplink traffic as well as the Proxy-Gn IP address and TEID to use for control plane.
• the SGSN sends back to the MS the PDP context activate response 9)
• the SM layer of the MS upwards to the UMA Multi-Access Client the activation success.
• the uplink user traffic is submitted by the UPMAC client to the SN-SAP (GPRS) or RAB-SAP (UMTS)
• the MS is under GPRS coverage.
• the current radio access is Wifi and the MS is going to move to GPRS.
• the Protocol Configuration Options field contains the GN_ADDR container set to the value of the IP address of the Proxy-Gn handling the PDP context.
• the Protocol Configuration Options field contains the MO BILITYJ N FO container indicating that GPRS/UMTS should be used for user plane.
• the SM layer of the MS sends to the SGSN a PDP context modification request with the received PCO.
• the SGSN sends an update PDP context request to the IP address that it has register to the GTP-C control plane (IP address of the Proxy-Gn).
• the Proxy- retrieves the PDP context (based on TEID). Since the MOBILITYJNFO container indicates that GPRS(UMTS) must be used for user plane, the Proxy-Gn updates the GGSN with the user plane IP address and TEID provided by the SGSN. Note : some other information may be changed, see 29.060 for details.
• the GGSN updates the user plan with the new TEID and IP address and responds to the Proxy-Gn.
• the user traffic now flows down directly to the SGSN.
• the Proxy-Gn returns back to the SGSN the GGSN IP address and TEID to use for uplink traffic as well as the Proxy-Gn IP address and TEID to use for control plane.
• the information related to the user plane are those of the GGSN if it provides new ones.
• the information are still the information related to the Proxy-Gn.
• the PDP context can be teardown by
• the UPMAC of the MS has to teardown the PDP context on any access where it has been activated.
• the SGSN may request a teardown of all or some of the PDP contexts previously activated for a MS.
• the Proxy-Gn When a PDP context is deactivated on both sides, the Proxy-Gn do not immediately request a PDP deletion to the GGSN but starts a timer waiting for MS reconnection. This gives some time to the MS in order to re-connect on the same APN in case it quickly recover radio access. The MS must try to reconnect its PDP context setting in the Protocol Configuration Options of its requests the IP address of the Proxy-Gn as defined in paragraphs Switching from one access to another.
• the Proxy- Gn If the timer expires on the Proxy-Gn without any PDP reconnection, the Proxy- Gn request a PDP context deletion to the GGSN and frees all resources allocated for this PDP context.
• De-activation on GPRS side - Wifi/UMA access is set up and active (figure 1 8) 1 )
• the SGSN sends ⁇ Delete PDP context request to the Proxy-Gn. This request is either triggered by ⁇ PDP context deactivation request sent from the MS, or by fault detection from the SGSN for this MS.
• Proxy-Gn deletes the UMTS/GPRS termination of the PDP context and responds to the SGSN.
• the SGSN sends a Delete PDP context request to the Proxy-Gn. This request is either triggered by a PDP context deactivation request sent from the MS, or by fault detection from the SGSN for this MS
• Proxy-Gn deletes the UMTS/GPRS termination of the PDP context and responds to the SGSN. Since the Wifi path is set up, it updates the GGSN with the user plan IP address and TEID of the SGW. The downlink traffic now flows on Wifi side. De-activation on GPRS side - Wifi/UMA access is not set up (figure 20)
• the SGSN sends a Delete PDP context request to the Proxy-Gn. This request is either triggered by a PDP context deactivation request sent from the MS, or by fault detection from the SGSN for this MS
• the Proxy-Gn deletes the UMTS/GPRS termination of the PDP context and responds to the SGSN.
• the Proxy-Gn starts a timer waiting for a re-connection of this PDP context.
• the Proxy-Gn timer expires for this PDP context and no reconnection has occurred.
• the Proxy-Gn deletes the PDP context on the GGSN and frees all its associated resources. De-activation on Wifi/UMA side - GPRS access is set up and active
• the W-SM sends a Delete PDP context request to the Proxy-Gn. This request is either triggered by a PDP context deactivation request sent from the MS UPMAC, or by an IPSec tunnel teardown for this MS. 2)
• the Proxy-Gn deletes the UMA termination of the PDP context and responds to the W-SM.
• De-activation on Wifi/UMA side - GPRS access is set up and standby (figure 22) 1 )
• the W-SM sends ⁇ Delete PDP context request to the Proxy-Gn. This request is either triggered by ⁇ PDP context deactivation request sent from the MS UPMAC, or by an IPSec tunnel teardown for this MS
• the Proxy-Gn deletes the UMA termination of the PDP context and responds to the SGW. Since the GPRS path is set up, it updates the GGSN with the user plan IP address and TEID of the SGSN. The downlink traffic flows on GPRS side. De-activation on Wifi/UMA side - GPRS access is not set up (figure 23)
• the SGW sends a Delete PDP context request to the Proxy-Gn. This request is either triggered by a PDP context deactivation request sent from the MS, or by an IPSec tunnel teardown for this MS.
• the Proxy-Gn deletes the UMA termination of the PDP context and responds to the SGW.
• the Proxy-Gn starts a timer waiting for a re-connection of this PDP context.
• the Proxy-Gn timer expires for this PDP context and no reconnection has occurred.
• the Proxy-Gn deletes the PDP context on the GGSN and frees all its associated resources.
• the present invention in particular has the following advantages: • Easier to implement

Landscapes

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

Applications Claiming Priority (2)

Publications (1)

Family

ID=39314410

Family Applications (1)

Country Status (2)

Families Citing this family (3)

Family Cites Families (2)

• 2007
  • 2007-09-11 WO PCT/IB2007/003460 patent/WO2008047231A2/en active Application Filing
  • 2007-09-11 EP EP07848877A patent/EP2100419A2/de not_active Withdrawn

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events