# US 2004/0081086 A1 · Method for redirecting packet data traffic to an alternative access point/router

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0081086 A1
- Document ID: US20040081086A1
- Status: Published application
- Kind: A1
- Application number: 10/466,253
- Filed: 2003-07-15
- Published: 2004-04-29
- Earliest claimed: 2001-01-16
- Inventors: Lassi Hippelainen; Otso Auterinen
- Web page: https://patentgrep.com/patent/US20040081086A1

## CPC

- H04W 24/04: Arrangements for maintaining operational condition
- H04W 88/14: Backbone network devices
- H04W 88/16: Gateway arrangements
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The invention relates to a method of protecting a data link (1-10, 1-20) established via an access point (GGSN1, GGSN2, ROUTER1, ROUTER2) to a mobile subscriber node (MN). The invention further includes the steps in which: (i) a monitoring network element (HA) observes the operation of the data link (1-10, 1-20); and (ii) in case the operation of the data link (1-10, 1-20) becomes unsuitable for communication, the monitoring network element (HA) starts to set up an alternative data link (1-10, 1-20) via an alternative access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

## Claims

### Claim 1

A method of protecting a data link (1-10, 1-20) established via an access point (GGSN1, GGSN2, ROUTER1, ROUTER2) to a mobile subscriber node (MN), characterized by the following steps:
(i) a monitoring network element (HA) monitors the operation of the data link (1-10, 1-20);
(ii) in case the operation of the data link (1-10, 1-20) becomes unsuitable for communication, the monitoring network element (HA) starts to set up an alternative data link (1-10, 1-20) via an alternative access point (GGSN1, GGSN2, ROUTER1, ROUTER2); and
(iii) after the alternative data link has been set up, the mobile subscriber node (MN) completes a Mobile IP handover to it.

### Claim 2 (depends on 1)

A method as claimed in claim 1, characterized in that the access point (GGSN1, GGSN2, ROUTER1, ROUTER2) provides access to a wireless network.

### Claim 3 (depends on 2)

A method as claimed in claim 2, characterized in that the wireless network is a radio access network, WLAN or Bluetooth network.

### Claim 4 (depends on 3)

A method as claimed in claim 3, characterized in that the access point (GGSN1, GGSN2, ROUTER1, ROUTER2) is an access point, e.g. a GGSN element of a GRPS data link, of said access network.

### Claim 5

A method as claimed in any one of the preceding claims, characterized by the observation of the data link (1-10, 1-20) involves the monitoring of the state of the access point (GGSN1, GGSN2, ROUTER1, Router2).

### Claim 6

A method as claimed in any one of the preceding claims, characterized by the fact that the operation of said data link (1-10, 1-20) becomes unsuitable for communication if
the data link (1-10, 1-20) is in malfunction; and/or
the data link (1-10, 1-20) is no longer fulfilling satisfying quality requirements; and/or
access point (GGSN1, GGSN2, ROUTER1, ROUTER2) is no longer in operational state.

### Claim 7

A method as claimed in any one of the preceding claims, characterized by
the monitoring element (HA) storing state data on the network element to be monitored, the data being related to the link(s) to be protected, and
the state data being transferred from the monitoring network element (HA) to the alternative access point along with a rerouting request.

### Claim 8

A method as claimed in any one of the preceding claims, characterized by the monitoring network element (HA) being an element outside the access network.

### Claim 9

A method as claimed in any one of the preceding claims, characterized by the link being an IP data link and the monitoring network element (HA) being a network element participating in the mobility management of the mobile node on the IP protocol level.

### Claim 10 (depends on 9)

A method as claimed in claim 9, characterized by the data link (1-10, 1-20) being a data link that uses the Mobile IP mobility management protocol.

### Claim 11 (depends on 9, 10)

A method as claimed in claim 9 or 10, characterized by the monitoring network element (HA) being the home agent (HA) of the Internet home network of the mobile node (MN).

### Claim 12

A method as claimed in any one of the preceding claims, characterized by the monitoring network element (HA) monitoring the activity of the access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

### Claim 13 (depends on 12)

A method as claimed in claim 12, characterized by the home agent (HA) of the Internet home network of the mobile node (MN) monitoring Mobile IP registration messages arriving via the access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

### Claim 14 (depends on 12)

A method as claimed in claim 12, characterized by the home agent (HA) of the Internet home network of the mobile node (MN) sending inquiry messages and waiting for replies, and the home agent (HA) of the Internet home network of the mobile node (MN) assuming the access point (GGSN1, GGSN2, ROUTER1, ROUTER2) failed and directing the data link (1-10, 1-20) to use the alternative link (1-10, 1-20) in case it receives no reply.

### Claim 15

A network element (HA) monitoring the Internet data link of a mobile node, characterized in that
(i) the monitoring network element (HA) is arranged to observe the operation of a data link (1-10, 1-20)
(ii) in case the operation of the data link (1-10, 1-20) becomes unsuitable for communication, the monitoring network element (HA) starts to set up an alternative data link (1-10, 1-20) via an alternative access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

### Claim 16 (depends on 15)

A network element as claimed in claim 15, characterized in that
the monitoring element (HA) is arranged to store state data on the network element to be observed, the data being related to the link(s) to be protected, and
the state data are transferred from the monitoring network (HA) element to the alternative access point (GGSN1, GGSN2, ROUTER1, ROUTER2) along with a rerouting request.

### Claim 17 (depends on 15, 16)

A network element as claimed in claim 15 or 16, characterized in that the monitoring network (HA) element is an element outside the access network.

### Claim 18 (depends on 15, 16, 17)

A network element as claimed in claim 15, 16 or 17, characterized in that the monitoring network element (HA) is a network element participating in the mobility management of the mobile node on the IP protocol level.

### Claim 19 (depends on 15)

A network element as claimed in claim 15, characterized in that the data link (1-10, 1-20) is a data link that uses the Mobile IP mobility management protocol.

### Claim 20

A network element as claimed in claims. 15 to 18, characterized in that the monitoring network element (HA) is the home agent (HA) of the Internet home network of the mobile node (MN).

### Claim 21 (depends on 15, 16, 17, 18, 19, 20)

A network element as claimed in claims 15 to 20, characterized in that the monitoring network element (HA) monitors the activity of the access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

### Claim 22 (depends on 20)

A network element as claimed in claim 20, characterized in that the home agent (HA) of the Internet home network of the mobile node (MN) monitors Mobile IP registration messages arriving via the access point (GGSN1, GGSN2, ROUTER1, ROUTER2).

### Claim 23 (depends on 22)

A network element as claimed in claim 22, characterized in that the home agent (HA) of the Internet home network of the mobile node (MN) sends inquiry messages and waits for replies, and the home agent (HA) of the Internet home network of the mobile node (MN) assumes the access point (GGSN1, GGSN2, ROUTER1, ROUTER2) failed and directs the data link (1-10, 1-20) to use the alternative link (1-10, 1-20) in case it receives no reply.

### Claim 24

An access network comprising at least one centralized router or gateway (GGSN1, GGSN2, ROUTER1, ROUTER2) via which an IP data link.
(1-10, 1-20) is set up from an outside data network to a mobile subscriber node (MN), characterized in that
said router or gateway is arranged to send state data associated with the link to an outside network element that monitors the operation of the router or gateway to protect said IP data link, and
said router or gateway is responsive to a set-up request that is sent by said network element and comprises data on a data link that was set up via another router or gateway to a mobile node but failed, for setting up an IP data link from said router or gateway to said mobile node on the basis of said received data.

### Claim 25 (depends on 24)

An access network as claimed in claim 24, characterized in that said router or gateway is arranged to send to said outside network element data on alternative protective routers or gateways in the same or a different access network.

### Claim 26 (depends on 24, 25)

An access network as claimed in claim 24 or 25, characterized in that said router or gateway is arranged to send a reply message in response to said monitoring message sent by the outside element.

### Claim 27 (depends on 24, 25, 26)

An access network as claimed in claim 24, 25 or 26, characterized in that said gateway is a gateway node in a packet radio network.

### Claim 28 (depends on 24, 25, 26, 27)

An access network as claimed in claim 24 to 27, characterized in that the access point (GGSN1, GGSN2, ROUTER1, ROUTER2) provides access to a wireless network.
