WO2008012223A1 - Mobility optimization based on ip prefix information in wlan ssid - Google Patents
Mobility optimization based on ip prefix information in wlan ssid Download PDFInfo
- Publication number
- WO2008012223A1 WO2008012223A1 PCT/EP2007/057297 EP2007057297W WO2008012223A1 WO 2008012223 A1 WO2008012223 A1 WO 2008012223A1 EP 2007057297 W EP2007057297 W EP 2007057297W WO 2008012223 A1 WO2008012223 A1 WO 2008012223A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- origssid
- connection
- name
- broadcast
- esclxprefix
- Prior art date
Links
- 238000005457 optimization Methods 0.000 title description 5
- 238000000034 method Methods 0.000 claims abstract description 24
- 238000000060 site-specific infrared dichroism spectroscopy Methods 0.000 claims description 12
- 239000000284 extract Substances 0.000 claims description 3
- 230000008901 benefit Effects 0.000 description 6
- 101000852224 Mus musculus THO complex subunit 5 homolog Proteins 0.000 description 3
- 102100036436 THO complex subunit 5 homolog Human genes 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 2
- 229910002515 CoAl Inorganic materials 0.000 description 1
- 239000003245 coal Substances 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000009499 grossing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- 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 invention concerns networks, mobile nodes and a method for handover.
- the base scenario generalized for two arbitrary access networks, is shown in Fig. 1 (base scenario for MIP based handover between 2 access networks) .
- the Mobile Node has radio connection with Access Points (AP) , either to one (single radio) or to more than one at a time (parallel radio) .
- AP Access Points
- AP Access Points
- AR Access Router
- the APs broadcast SSIDs (Service Set IDs) . This information (maximal 32 octets) is primarily an identification of the cell, but may also be used to logically link several of them together. We assume here a provisioning where one and the same SSID is used for all APs linked to one subnet of an AR.
- step 1 initially the MN is in radio contact with AP3 and IP enabled (depending on the details a local IP address and/or global IP address are configured)
- step 2 detect that access network 2 is available, e.g. by passive scanning
- step 3 associate with access network 2 via AP4 (this may include authentication and authorization, which is not discussed here)
- step 4 prepare L3 properties for the new access (i.e.
- a registration with a network entity e.g. HA
- the object is respectively achieved by the invention defined in the patent claims.
- the improvement described in this paper focuses on 3 aspects: -how to receive L3 information on L2 for the new access system, while keeping connectivity with the old one, -how to shorten the disruption time interval for the HO and -how to minimize the complexity of and effort for configuration for such a solution within the networks.
- Fig. 1 shows a base scenario for MIP based handover between 2 access networks.
- Fig. 2 shows possible information relationships between L2 and L3 in two access networks.
- Fig. 3 shows a message flow explanation for a message flow example .
- the main idea is to provide L3 information via L2 to the MN, so that it can timely prepare itself for the IP layer connectivity change with the HO.
- This description is limited to pure IPv6 deployments (MN, access networks and HA) . It optimizes the HO procedure towards WLAN.
- L3 of access system 1 has, or can be utilized to provide, information about L3 properties of access system 2 (present with FMIP, and with MNs parallel, active radio capability for both access systems) .
- L2 of access system 1 has information on L2 properties of access system 2 (present in 3GPP access systems) .
- L2 of access system 2 has information on its own L3 properties (this is the aim of the concept presented here) .
- L2 of access system 1 has information on L3 properties of access system 2 (currently not existent; it would e.g. be the case if a 3GPP access system knew IP prefixes of neighbouring WLANs) .
- L3 of access system 1 has information on L2 properties of access system 2 (present with FMIP)
- Figure 2 shows possible information relationships between L2 and L3 in two access networks. It is clear then that information provisioning across access systems (labels 1, 2 and 4) is much more difficult to achieve than between L3 and L2 of the same access system (label 3) .
- SSIDS which can be broadcast from access points (AP 1-6 in Fig.l) to Mobile Nodes MN which can extract also L3 information from them) which include (piggybacked) layer 3 information. 2 variants are explained:
- IPv6 address prefix of length of 64 bits 8 octetts is appended to the original SSID:
- the IP prefix can be readily used; together with a unique identifier for the mobile node there is no need to perform an additional request to the network.
- the SSID has the format :
- ⁇ escl> and ⁇ esc2> are escape characters, which can be defined arbitrarily.
- the MNs supporting this intended enhancement shall extract the information after ⁇ escl> or ⁇ esc2> and proceed accordingly. I.e. if a DNS name was appended, a DNS resolution is done in order to receive a valid IPv6 address prefix. If an explicit IPv6 address prefix was appended, it can be readily used. In both cases the information in front of ⁇ escl> or ⁇ esc2> is used exactly as SSIDs would be used without this enhancement (e.g. for display, selection, etc.) .
- This optimization assumes the possibility of parallel scanning on L2 of a second access system during an ongoing connection via the first one.
- the length restriction for SSIDs (32 octetts) limits the length of the original SSID (depending on which variant is chosen) .
- Escape characters ⁇ escl> and ⁇ esc2> need to be defined and must not be used in SSIDs otherwise.
- Terminals require a small change in the handling of SSIDs. Terminals need to support DNS (for above variant 2) - this may be considered a standard IP feature. The DNS query has to be handled in parallel with ongoing traffic in the old access system.
- FIG. 3 An Illustration of a message flow in Fig. 3 follows (with multihoming, multiple Care-of-Address & bicasting) .
- Fig. 3 shows a possible message flow based on it. Multihoming (with respect to local IP addresses) is assumed, and the multiple CoA and bicasting during the HO requires support of [7] .
- the home agent starts bicasting of downlink data.
- the MN stops L2 connectivity with the PAR and starts L2 connectivity with AR2 (additionally there might be access NW specific security procedures, which are not shown) .
- the MN sends a Neighbour Advertisement, which leads to establishment of L3 connectivity.
- IP packets are received within access system 2, at CoA2. 10.
- the MIP registration with the old CoAl is resolved.
- Bicasting of downlink packets is stopped at the HA.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The patent application concerns networks, mobile nodes and a method for handover of a first connection (Fig. 1, 'first connection C1') between a mobile node (Fig. 1, 'MN') and a first access point (Fig 1, 'AP 1') of a first access network (Fig. 1, 'access network AN1') to a second connection (Fig. 1, 'second connection C2') between the mobile node (Fig. 1, 'MN') and a second access point (Fig 1, 'AP 4') of a second access network (Fig. 1, 'access network AN 2'), wherein a broadcast message (Fig. 1,,,Broadcast',,,origSSID<esc1><prefix>,, /,,origSSID<esc2><DNS-name>') is sent by the second access point (Fig 1, 'AP 4') wherein the broadcast message (Fig. 1,,,Broadcast',,,origSSID<esc1><prefix>,, /,,origSSID<esc2><DNS-name>') comprises layer-3-information (Fig. 1,,,Broadcast',,,origSSID<esc1><prefix>,, /,,origSSID<esc2><DNS-name>') concerning the second connection (Fig. 1, 'second connection C2').
Description
Description
Mobility Optimization based on IP Prefix Information in WLAN SSID
The invention concerns networks, mobile nodes and a method for handover.
Seamless mobility between 3GPP and non-3GPP access systems is a target within 3GPP' s System Architecture Evolution (SAE). There it is generally agreed that handover (HO) solutions shall work on the IP layer (L3) , and in particular that the MIP set of protocols shall be used. In other forums high efforts have already been spent on the development of different variants and optimizations of MIP. The advantage of placing the HO functionality on L3 is thought to be its generality and independence from the details of the access technology (L2) .
On the other hand it is known that the optimal handover performance like e.g. in GSM/GPRS/ UMTS networks is achieved only at layer 2. In comparison, it must be stated for MIP that it had never been designed for HO' s, - some opportunities for optimization have not been taken, the (re) configuration of L3 properties during HOs is too time-consuming.
The base scenario, generalized for two arbitrary access networks, is shown in Fig. 1 (base scenario for MIP based handover between 2 access networks) .
The Mobile Node (MN) has radio connection with Access Points (AP) , either to one (single radio) or to more than one at a
time (parallel radio) . As long as it moves (arrow in Fig. 1) within the coverage of one access network it is connected on L2 also to the corresponding Access Router (AR) , which is the first IP router in uplink direction. The APs broadcast SSIDs (Service Set IDs) . This information (maximal 32 octets) is primarily an identification of the cell, but may also be used to logically link several of them together. We assume here a provisioning where one and the same SSID is used for all APs linked to one subnet of an AR.
For a normal IP based handover from access network 1 to access network 2, e.g. when moving from radio coverage by AP 3 to that of AP 4, the main steps are:
- step 1: initially the MN is in radio contact with AP3 and IP enabled (depending on the details a local IP address and/or global IP address are configured) step 2: detect that access network 2 is available, e.g. by passive scanning - step 3: associate with access network 2 via AP4 (this may include authentication and authorization, which is not discussed here) step 4: prepare L3 properties for the new access (i.e.
IP address [es] ); this could also be done - in an optimistic approach - before step 3 step 5: optional further authentication and authorization (on higher layers) may be done, but are not discussed further here step 6: depending on the details a registration with a network entity (e.g. HA) has to be done step 7: now the MN is reachable via the new IP address and data may be transferred
step 8: dissociate from access network 1 (depending on whether parallel radio capability of the MN this could also happen before step 3)
It is an object of the invention to provide an efficient handover of a connection between a mobile node and a first access point of a first access network to a connection between the mobile node and a second access point of a second access network. The object is respectively achieved by the invention defined in the patent claims.
An implementation of the invention can especially provide the following advantages:
1. speed up of L3 configuration before/during handovers; 2. resulting from item 1, smoothing of handovers;
3. simplicity in terminals and network (e.g. in comparison to alternatives like FMIP)
4. minimal signaling (none in variant 1, 1 DNS query in variant 2)
The improvement described in this paper focuses on 3 aspects: -how to receive L3 information on L2 for the new access system, while keeping connectivity with the old one, -how to shorten the disruption time interval for the HO and -how to minimize the complexity of and effort for configuration for such a solution within the networks.
Further details and advantages of the invention are set forth in the claims and in the following non-limiting description of an example, wherein in the enclosed drawing:
Fig. 1 shows a base scenario for MIP based handover between 2 access networks.
Fig. 2 shows possible information relationships between L2 and L3 in two access networks.
Fig. 3 shows a message flow explanation for a message flow example .
The main idea is to provide L3 information via L2 to the MN, so that it can timely prepare itself for the IP layer connectivity change with the HO.
This description is limited to pure IPv6 deployments (MN, access networks and HA) . It optimizes the HO procedure towards WLAN.
First the principal possibilities to do so are described. The arrows in fig. 2 indicate possible information exchange as listed:
1. L3 of access system 1 has, or can be utilized to provide, information about L3 properties of access system 2 (present with FMIP, and with MNs parallel, active radio capability for both access systems) . 2. L2 of access system 1 has information on L2 properties of access system 2 (present in 3GPP access systems) . 3. L2 of access system 2 has information on its own L3 properties (this is the aim of the concept presented here) . 4. L2 of access system 1 has information on L3 properties of access system 2 (currently not existent; it would e.g. be the case if a 3GPP access system knew IP prefixes of neighbouring WLANs) .
5. L3 of access system 1 has information on L2 properties of access system 2 (present with FMIP)
Figure 2 shows possible information relationships between L2 and L3 in two access networks.
It is clear then that information provisioning across access systems (labels 1, 2 and 4) is much more difficult to achieve than between L3 and L2 of the same access system (label 3) .
Detailed Solution :
The solution suggests constructing SSIDS (which can be broadcast from access points (AP 1-6 in Fig.l) to Mobile Nodes MN which can extract also L3 information from them) which include (piggybacked) layer 3 information. 2 variants are explained:
a) Variant 1: Inclusion of IPv6 Address Prefix in SSID
An IPv6 address prefix of length of 64 bits = 8 octetts is appended to the original SSID:
m~ n rτς ς τ n <fp q r 1 Advantage: the IP prefix can be readily used; together with a unique identifier for the mobile node there is no need to perform an additional request to the network.
Disadvantage: higher effort with later changes (e.g. changes with IP address ranges of ARs require new provisioning of the SSID to the APs) .
b) Variant 2: Usage of DNS info in SSID
The SSID has the format :
n-r-i rτςςτn<-pςp9><rnwς-
Advantage: more flexibility for changes in the access network (e.g. changes with IP address ranges of ARs require no new provisioning of the SSID to the APs) .
Disadvantage: another request to the network for resolution of DNS-name is necessary.
c) Common Aspects
<escl> and <esc2> are escape characters, which can be defined arbitrarily. The MNs supporting this intended enhancement shall extract the information after <escl> or <esc2> and proceed accordingly. I.e. if a DNS name was appended, a DNS resolution is done in order to receive a valid IPv6 address prefix. If an explicit IPv6 address prefix was appended, it can be readily used. In both cases the information in front of <escl> or <esc2> is used exactly as SSIDs would be used without this enhancement (e.g. for display, selection, etc.) .
d) Limitations
This optimization assumes the possibility of parallel scanning on L2 of a second access system during an ongoing connection via the first one.
The length restriction for SSIDs (32 octetts) limits the length of the original SSID (depending on which variant is chosen) .
Escape characters <escl> and <esc2> need to be defined and must not be used in SSIDs otherwise.
This enhancements puts some requirements on the provisioning of WLAN APs. The administration of several or many WLAN APs with the necessary SSID information may be done conveniently via CAPWAP [8] .
e) Terminal impacts
Terminals require a small change in the handling of SSIDs. Terminals need to support DNS (for above variant 2) - this may be considered a standard IP feature. The DNS query has to be handled in parallel with ongoing traffic in the old access system.
An Illustration of a message flow in Fig. 3 follows (with multihoming, multiple Care-of-Address & bicasting) . For showing the benefit of this approach Fig. 3 shows a possible message flow based on it. Multihoming (with respect to local IP addresses) is assumed, and the multiple CoA and bicasting during the HO requires support of [7] .
Message Flow Explanation (Fig. 3) :
1. Mobile IPv6 procedure, with Binding Unique Identifier sub-option according to [7]
2. Detection of the new link, with L3 information. This is the feature described in sections above .
3. The new/envisaged Care-of-Address CoA2 is built. 4. Mobile Node sends a Binding Update message which contains the Home Address HA, the CoA2 and Binding Unique Identification number 2 (BID2) .
5. The home agent starts bicasting of downlink data.
6. Due to the fact that the MN has not yet been L3 configured, packets are dropped at the NAR.
7. The MN stops L2 connectivity with the PAR and starts L2 connectivity with AR2 (additionally there might be access NW specific security procedures, which are not shown) .
8. The MN sends a Neighbour Advertisement, which leads to establishment of L3 connectivity.
9. From now on IP packets are received within access system 2, at CoA2. 10. The MIP registration with the old CoAl is resolved. 11. Bicasting of downlink packets is stopped at the HA.
In this example, even without parallel active radio, only a minimal interruption time between steps 7 and 9 occurs.
Abbreviations
AP Access Point
3GPP Third Generation Partnership Project
HA Home Agent MIP Mobile IP
MN Mobile Node
SAE System Architecture Evolution
SSID Service Set ID
UE User Equipment NAR Next Access Router
PAR Previous Access Router
References
[1] 3GPP TS 33.234 V6.5.1 (2005-06), "3G Security; Wireless Local Area Network (WLAN) Interworking Security"
[2] 3GPP TS 23.234 V6.5.0 (2005-06), "3GPP System to Wireless Local Area Network (WLAN) Interworking; System description"
[3] 3GPP TS 29.234 V6.3.0 (2005-06), "3GPP system to Wireless Local Area Network (WLAN) Interworking; Stage 3"
[4] C. Kaufman (ed.), "Internet Key Exchange (IKEv2) Protocol", draft-ietf-ipsec-ikev2-17.txt, September 2004
[5] S. Kent, R. Atkinson, "IP Encapsulating Security Payload (ESP)", RFC 2406, November 1998
[6] S. Kent, R. Atkinson, "Security Architecture for the Internet Protocol", RFC 2401, November 1998 [7] R. Wakikawa, T. Ernst and K. Nagami, "Multiple Care-of Addresses
Registration", draft-wakikawa-mobileip-multiplecoa-05, February 2006
[8] P. Calhoun et.al. (eds.), "CAPWAP Protocol Specification", draft-ietf- capwap-protocol-specification-01
Claims
1. Method for handover of a first connection (Fig. 1, "first connection Cl") between a mobile node (Fig. 1, "MN") and a first access point (Fig 1, "AP 1") of a first access network (Fig. 1, "access network ANl") to a second connection (Fig. 1, "second connection C2") between the mobile node (Fig. 1, "MN") and a second access point (Fig 1, "AP 4") of a second access network (Fig. 1, "access network AN 2"), wherein a broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") sent by the second access point (Fig 1, "AP 4") comprises layer-3- information (Fig. 1, "origSSID<esclxprefix>" / "origSSID<esc2xDNS-name>") concerning the second connection (Fig. 1, "second connection C2") .
2. Method according to claim 1, characterized in that a mobile node (Fig. 1, "MN") extracts information from the broadcast message and uses it for a connection (Fig. 1, "second connection C2") after a handover.
3. Method according to any of the preceding claims, characterized in that the layer-3-information is sent in a broadcast message by an access point to mobile nodes (Fig. 1, "MN") for informing the mobile nodes (Fig. 1, "MN") that a connection (Fig. 1, "second connection C2") via the access point (Fig 1, "AP 4") is possible.
4. Method according to any of the preceding claims, characterized in that the layer-3-information is sent in a SSID message broadcast (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") by an access point (Fig 1, "AP 4") to mobile nodes (Fig. 1, "MN") for informing the mobile nodes (Fig. 1, "MN") that a connection (Fig. 1, "second connection C2") via the access point (Fig 1, "AP 4") is possible.
5. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises IP address information (Fig. 1, "Broadcast origSSID<esclxprefix>") regarding an IP address for the second connection (Fig. 1, "second connection C2"), especially an IPv6 Address of the mobile mode (Fig. 1, "MN") or of the access point (Fig. 1, "AP 4") .
6. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises an IP address prefix (Fig. 1, "origSSID<esclxprefix>") .
7. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises an identifier of the mobile node (Fig. 1, "MN"), especially a unique identifier (Fig. 1, "origSSID<esc2><DNS- name>") .
8. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises DNS information or domain name service information.
9. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises a DNS-name.
10. Method according to any of the preceding claims, characterized in that the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises further characters (<escl>, <esc2>) indicating that a DNS-name or IP address prefix follows the further characters .
11. Method according to any of the preceding claims, characterized in that a mobile node (Fig. 1, "MN") receiving the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") uses information in the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") for communication over the second connection (Fig. 1, "second connection C2") .
12. Method according to any of the preceding claims, characterized in that a mobile node (Fig. 1, "MN") receiving the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, /
,,origSSID<esc2xDNS-name>") uses information in the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") for communication over the second connection (Fig. 1, "second connection C2") .
13. Method according to any of the preceding claims, characterized in that if the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises a DNS name, a DNS resolution is done in order to receive a valid IPv6 address prefix.
14. Method according to any of the preceding claims, characterized in that if the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises an IPv6 address prefix, the IPv6 address prefix is used for the second connection (Fig. 1, "second connection C2") .
15. Method according to any of the preceding claims, characterized in that the DNS name represents the DNS name of a network component (Fig 1, "AP 4") of the second connection (Fig. 1, "second connection C2"), especially of an access point (Fig 1, "AP 4") of the second connection (Fig. 1, "second connection C2") .
16. Method according to any of the preceding claims, characterized in that the IPv6 address prefix is an IPv6 address prefix of a network component of the second connection (Fig. 1, "second connection C2"), especially of an access point of the second connection (Fig. 1, "second connection C2") .
17. Mobile network implementing a method according to any of the preceding claims .
18. Mobile network access point (Fig. 1, "AP 4"), for handover of a first connection between a mobile node (Fig. 1, "MN") and a first access point (Fig 1, "AP 1") of a first access network (Fig. 1, "access network AN 1") to a second connection (Fig. 1, "second connection C2") between the mobile node (MN) and a second access point (Fig 1, "AP 4") of a second access network (access network 2), wherein the access point (Fig. 1, "AP 4") comprises a sender or access to a sender for sending a broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, /
,,origSSID<esc2xDNS-name>") wherein the broadcast message (Fig. 1, ,,Broadcast", ,,origSSID<esclxprefix>,, / ,,origSSID<esc2xDNS-name>") comprises layer-3-information (Fig. 1, "origSSID<esclxprefix>", "origSSID<esc2><DNS- name>") concerning the second connection (Fig. 1, "second connection C2") .
19. Mobile node (Fig. 1, "MN") implementing a method according to any of the preceding method claims.
20. Mobile node (Fig. 1, "MN")
-for handover of a first connection between a mobile node (Fig. 1, "MN") and a first access point (Fig 1, "AP 1") of a first access network (Fig. 1, "access network 1") to a second connection (Fig. 1, "second connection C2") between the mobile node (Fig. 1, "MN") and a second access point (Fig 1, "AP 4") of a second access network (Fig. 1, "access network AN 2"), -with a receiver for receiving a broadcast message (Fig. 1, "broadcast" ) comprising layer-3-information (Fig. 1, "origSSID<esclxprefix>, origSSID<esc2xDNS-name>") concerning the second connection (Fig. 1, "second connection r?" i -with an extracting device for extracting layer-3-information (Fig. 1, "origSSID<esclxprefix>, origSSID<esc2xDNS-name>") concerning the second connection (Fig. 1, "second connection
-with a receiver and/or a sender using extracted layer-3- information (Fig. 1, origSSID<esclxprefix>, origSSID<esc2xDNS-name>") for sending or receiving information via the second connection (Fig. 1, "second connection C2") after a handover to the second connection (Fig. 1, "second connection C2") .
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP06015821.9 | 2006-07-28 | ||
EP06015821A EP1906593A1 (en) | 2006-07-28 | 2006-07-28 | Mobility optimisation based on IP prefix information in WLAN SSID |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008012223A1 true WO2008012223A1 (en) | 2008-01-31 |
Family
ID=37387388
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2007/057297 WO2008012223A1 (en) | 2006-07-28 | 2007-07-16 | Mobility optimization based on ip prefix information in wlan ssid |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP1906593A1 (en) |
WO (1) | WO2008012223A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009114025A1 (en) * | 2008-03-13 | 2009-09-17 | Qualcomm Incorporated | Supporting communications in a wireless network using an ip address |
EP2148539A1 (en) * | 2008-07-23 | 2010-01-27 | Fujitsu Limited | Communication system, base transceiver station, mobile station, and data transfer method for performing a handover between first and second base transceiver stations |
CN104184668A (en) * | 2014-07-29 | 2014-12-03 | 小米科技有限责任公司 | Networking method, networking device, router and third-party device of Internet of things |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2348570A (en) * | 1999-03-31 | 2000-10-04 | Ericsson Telefon Ab L M | Routing prefix allocation for mobile internet access |
WO2001063956A1 (en) * | 2000-02-21 | 2001-08-30 | Eads Defence And Security Networks | Wireless access point of an ip network, and corresponding mobility management method |
US20030216140A1 (en) * | 2002-05-17 | 2003-11-20 | Georg Chambert | Universal identification system for access points of wireless access networks |
US6657981B1 (en) * | 2000-01-17 | 2003-12-02 | Accton Technology Corporation | System and method using packet filters for wireless network communication |
WO2005008969A1 (en) * | 2003-07-14 | 2005-01-27 | Matsushita Electric Industrial Co. Ltd. | Method for reducing hand-off latency in mobile networks |
-
2006
- 2006-07-28 EP EP06015821A patent/EP1906593A1/en not_active Withdrawn
-
2007
- 2007-07-16 WO PCT/EP2007/057297 patent/WO2008012223A1/en active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2348570A (en) * | 1999-03-31 | 2000-10-04 | Ericsson Telefon Ab L M | Routing prefix allocation for mobile internet access |
US6657981B1 (en) * | 2000-01-17 | 2003-12-02 | Accton Technology Corporation | System and method using packet filters for wireless network communication |
WO2001063956A1 (en) * | 2000-02-21 | 2001-08-30 | Eads Defence And Security Networks | Wireless access point of an ip network, and corresponding mobility management method |
US20030216140A1 (en) * | 2002-05-17 | 2003-11-20 | Georg Chambert | Universal identification system for access points of wireless access networks |
WO2005008969A1 (en) * | 2003-07-14 | 2005-01-27 | Matsushita Electric Industrial Co. Ltd. | Method for reducing hand-off latency in mobile networks |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2009114025A1 (en) * | 2008-03-13 | 2009-09-17 | Qualcomm Incorporated | Supporting communications in a wireless network using an ip address |
CN101960883A (en) * | 2008-03-13 | 2011-01-26 | 高通股份有限公司 | Supporting communications in a wireless network using an ip address |
CN101960883B (en) * | 2008-03-13 | 2013-08-14 | 高通股份有限公司 | Supporting communications in wireless network using ip address |
US9025563B2 (en) | 2008-03-13 | 2015-05-05 | Qualcomm Incorporated | Supporting communications in a wireless network using an IP address |
EP2148539A1 (en) * | 2008-07-23 | 2010-01-27 | Fujitsu Limited | Communication system, base transceiver station, mobile station, and data transfer method for performing a handover between first and second base transceiver stations |
CN104184668A (en) * | 2014-07-29 | 2014-12-03 | 小米科技有限责任公司 | Networking method, networking device, router and third-party device of Internet of things |
Also Published As
Publication number | Publication date |
---|---|
EP1906593A1 (en) | 2008-04-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103442347B (en) | Mobile node, home agent and redirect method | |
Jang et al. | Mobile IPv6 fast handovers over IEEE 802.16 e networks | |
US8780800B2 (en) | Optimized home link detection | |
CN101601255B (en) | Lightweight mobility architecture | |
EP2353271B1 (en) | Secure tunnel establishment upon attachment or handover to an access network | |
FI114840B (en) | Change of Responsibility | |
KR101221610B1 (en) | Apparatus and Method for Supporting Fast Mobility IP with Link Identifier Prefix in Wireless Communication System | |
EP1645157B1 (en) | Enhanced fast handover procedures | |
EP2090064B1 (en) | Methods and apparatus for implementing proxy mobile ip in foreign agent care-of address mode | |
US20060126565A1 (en) | Method and system for interworking of cellular networks and wireless local area networks | |
KR100958657B1 (en) | Method and System for fast Handover between different network | |
US20110063997A1 (en) | Interworking between wimax and 3gpp networks | |
US8442006B2 (en) | Wireless LAN mobility | |
WO2006052563A2 (en) | Wireless communication method and system for implementing media independent handover between technologically diversified access networks | |
EP1883254B1 (en) | Access router device, mobility control system, and mobility control method | |
EP1906593A1 (en) | Mobility optimisation based on IP prefix information in WLAN SSID | |
US8619701B2 (en) | Method of facilitating handoff for CDMA networks using IP protocols | |
EP1838065A1 (en) | Apparatus & method for assuring MIPv6 functionality after handover | |
US20100070617A1 (en) | IP address assignment for access to IP services via WiMAX or 3GPP access network | |
Yokota et al. | Mobile IPv6 fast handovers for 3G CDMA networks | |
Wozniak et al. | Comparative analysis of IP-based mobility protocols and fast handover algorithms in IEEE 802.11 based WLANs | |
Yoon et al. | New Approach for Reducing DAD delay using Link Layer Assistance in Mobile IPv6 | |
Damic | Comparison and evaluation of network-based IP mobility management schemes | |
Jang et al. | RFC 5270: Mobile IPv6 Fast Handovers over IEEE 802.16 e Networks | |
Damic | Introducing L3 network-based mobility management for mobility-unaware IP hosts |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07787565 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07787565 Country of ref document: EP Kind code of ref document: A1 |