WO2012101513A1

WO2012101513A1 - Mobility management method and device for ipv6 over low power wireless personal area network

Info

Publication number: WO2012101513A1
Application number: PCT/IB2012/000154
Authority: WO
Inventors: Shuigen Yang; Jun Zheng; Fanxiang Bin; Zheng LIANG; Chunyan Yao; Haibo Wen
Original assignee: Alcatel Lucent
Priority date: 2011-01-30
Filing date: 2012-01-04
Publication date: 2012-08-02
Also published as: CN102625278A

Abstract

This invention discloses a mobility management method for IPv6 over Low power Wireless Personal Area Network, comprising: receiving a compressed binding update message; performing a binding update according to said compressed binding update message; and decompressing said compressed binding update message and sending said decompressed binding update message to a home agent. This invention also discloses a mobility management device for IPv6 over Low power Wireless Personal Area Network, comprising: means for receiving a compressed binding update message; means for performing a binding update according to said compressed binding update message; and means for decompressing said compressed binding update message and sending said decompressed binding update message to a home agent. The compressed binding update message and binding acknowledgement message can reduce the size of binding messages, whereby reducing the signaling overhead for position updates and improving the network mobility efficiency for IPv6 over Low power Wireless Personal Area Network.

Description

Mobility Management Method and Device for IPv6 over Low power Wireless Personal Area Network

Field of the Invention

This invention relates to communication technical field, and in particular, relates to a mobility management method and device for IPv6 over Low power Wireless Personal Area Network.

Technological Background

At present, sensor networks are widely used in many civilian application areas, including environment and habitat monitoring, agricultural monitoring, industrial control and automation, healthcare applications, home automation, intelligent traffic control, etc., and lead an advanced e-Life. According to research and report of the IDATE, the related market size of the global sensor network will reach 200 billion Euros in 2010 with a fifty percent annual growth rate. Due to the huge benefit, many research institutes, vendor companies and network operators invest huge funds into the sensor network market, such as Vodafone, AT&T, T-Mobile, Verizon Wireless, China Mobile, China Telecom and China Unicom, etc.

In order to fully realize a ubiquitous sensor network environment, the sensor networks need to be connected to the Internet, wherein, IPv6 is the best solution. Accordingly, the Internet Engineering Task Force (IETF) specially set up a working group based on IPv6 over Low power Wireless Personal Area Network (6L0WPAN) to define the transmission solution of IPv6 packets over IEEE 802.15.4 link. With the proposed 6L0WPAN dispatch, the IPv6 header can be compressed from 40 bytes to 2 bytes. 6L0WPAN is envisioned to play a major role in the future ubiquitous sensor network. With 6L0WPAN, external hosts in the Internet will be able to directly communicate with the sensor nodes in 6L0WPAN, and vice versa. Furthermore, 6L0WPAN can enhance the mobility management of sensor networks, and thereby bring in new appl ications, such as health care applications. In this case, the 6L0WPAN sensor networks embedded in the patient can also transmit the sensed data (e.g., pulse rate, temperature) to a monitoring server, even when the patient is moving.

The 6L0WPAN sensor nodes are usually characterized by low data rates, low power consumption and low costs. Typically, in order to provide the mobility management for the 6L0WPAN sensor nodes, the existing mobile IPv6 based Network Mobility (NEMO) protocol can be employed. When NEMO is employed in the 6L0WPAN sensor network, sensor nodes can maintain the session continuity with the communication nodes resided in the Internet through the 6L0WPAN Mobile Router (MR), even though not all the 6L0WPAN sensor nodes are equipped with the mobile IPv6 protocol. F ig .1 is a schematic d iagram of the 6L0WPAN sensor network mobil ity management scenarios, including two typical scenarios. Wherein, HA stands for Home Agent, AR stands for Access Router, MR stands for Mobile Router and may represent 6L0WPAN Mobile Router here, and GW stands for Gateway and may represent 6L0WPAN Gateway here. Furthermore, the senor network also comprises sensor nodes which could represent 6L0WPAN sensor nodes here.

As shown in Fig .1 , the first 6L0WPAN sensor network mobility management scenario is that the egress interface of the 6L0WPAN MR uses an IEEE 802.11 protocol for communication. In this scenario, the 6L0WPAN MR can directly connects to the IPv6 Internet and employ a NEMO protocol to provide the network mobility management for 6L0WPAN. The 6L0WPAN MR is merely required to convert communication protocols between IEEE 802.11 and IEEE 802.15.4.

The NEMO protocol is a mobile IPv6 based network mobility management protocol which may maintain the session continuity for all the mobile nodes within the network. When the MR moves to an external link away from the home link, it obtains a new IPv6 address, called care-of address, and sends a Binding Update (BU) message to its Home Agent (HA). Upon receipt of the BU message sent from the MR, the HA creates a cache entry binding the MR's home add ress with the care-of address, and replies with a Binding Acknowledgement (BA) message. When a communication node sends packets to a mobile network node, the packets are firstly routed to the HA, and then tunneled to the MR's care-of address. After that, the MR decapsulates the packets and forwards them to the mobile network node.

In the NEMO protocol, the BU and BA messages are extended mobile IPv6 messages, both of which are based on IPv6 mobility header. In addition, the MR uses a destination option header to issue its home address. Fig.2 is a schematic diagram of the IPv6 mobility header format. The IPv6 mobility header includes IPv6 header field, Payload proto field, Header len field, MH type field, Reserved field, Checksum field and Message data field. Fig.3 is a schematic diagram of the BU message format in the NEMO protocol. The BU message format comprises Sequence number field, Ά field, Ή' field, 'L' field, 'K' field, M field, 'R' field, 'P' field, Reserved field, Lifetime field and Mobility Network prefix options field. Fig.4 is a schematic diagram of the BA message format in the NEMO protocol. Said BA message format includes: Status field, 'K' field, 'R' field, 'P' field, Reserved field, Lifetime field and Mobility Network prefix options field.

As shown in Fig .1 , the second 6L0WPAN sensor network mobility management scenario is that the 6L0WPAN MR moves and connects to another 6L0WPAN sensor network (e.g . connects with the GW of another 6L0WPAN sensor network) through the egress interface and takes care of the network mobility for 6L0WPAN through the ingress interface. That is, the egress and ingress interfaces of the M R both employ an IEEE 802.15.4 protocol for communication. In this scenario, the existing NEMO protocol cannot effectively support the mobility management for the 6L0WPAN sensor network due to the following reasons:

1 . To support mobility management, the 6L0WPAN MR needs to send a BU message to the HA and receive a BA message from the HA. Both the BU and BA messages are based on IPv6 mobility header. However, the existing 6L0WPAN only defines the fragmentation header format and the mesh routing header format. However, these messages are incapable of supporting the mobility management for the 6L0WPAN sensor network. 2. The 6L0WPAN uses the 6L0WPAN dispatch in LoWPAN_HC1 (HC stands for Header Compression) to compress the IPv6 header from 40 to 2 bytes. Nevertheless, the existing LoWPAN_HC1 could merely support the following four headers: the not compressed next header, represented by 00; the User Datagram Protocol (UDP) packet header, represented by 01 ; the Internet Control Message Protocol (ICMP) packet header, represented by 10; and the Transmission Control Protocol (TCP) packet header, represented by 11 . Therefore, the existing structure of the 6LoWPAN_HC1 header format has no appropriate space to compress the mobility headers required for the BU and BA messages. 3. Since IEEE 802.15.4 only supports a maximum physical layer packet size of 127 bytes (containing 25 bytes of physical layer frame system overhead, 21 bytes of link layer security imposes further system overhead, and at least 11 bytes of Media Access Control (MAC) frame system overhead), so it can only support IPv6 packets of less than 70 bytes. However, in the traditional NEMO protocols, the BU message has a length of minimal 80 bytes of IPv6 packets and the BA message has a length of minimal 60 bytes of IPv6 packets, which are too heavy for IEEE 802.15.4. Therefore, when the 6L0WPAN MR moves to another 6L0WPAN sensor network, a mobile management method for the 6L0WPAN sensor network suitable for IEEE 802.15.4 link needs to be provided.

Summary of the Invention

In order to solve the above problems, this invention provides a method of mobility management for IPv6 over Low power Wireless Personal Area Network, characterized in:

receiving a compressed binding update message;

performing a binding update according to said compressed binding update message; and

decompressing said compressed binding update message and sending said decompressed binding update message to a home agent.

According to a preferred embodiment of the invention, after sending said decompressed binding update message to the home agent, performing a binding update on the home agent based on said decompressed binding update message. According to a preferred embodiment of the invention, receiving a binding acknowledgement message sent by said home agent, compressing said binding acknowledgement message and sending said compressed binding acknowledgement message to a mobile router.

According to a preferred embodiment of the invention , before receiving said compressed binding update message, further comprising: authenticating the mobile router through an authentication, authorization and accounting (AAA) server.

According to a preferred embodiment of the invention, before receiving said compressed binding update message , further comprising: receiving an association request message sent by the mob ile router and send an association response to the mobile router.

According to a preferred embodiment of the invention, said compressed binding update message is sent by the mobile router.

According to a preferred embodiment of the invention, said compressed binding update message comprises: Lifetime, Sequence number, Checksum, Home address and Mobile network prefix.

According to a preferred embodiment of the invention, said compressed binding acknowledge message comprises: Lifetime, Sequence number and Checksum.

The invention provides a device of mobility management for IPv6 over Low power Wireless Personal Area Network, characterized in:

means for receiving a compressed binding update message; means for performing a binding update according to said compressed binding update message; and

means for decompressing said compressed binding update message and sending said decompressed binding update message to a home agent.

In comparison with the prior art (a network mobility protocol based solution), the invention produces the following beneficial effects:

1 . Since the existing NEMO protocol uses the standard IPv6 mobility header to send binding update and binding acknowledgement messages while the existing structure of 6L0WPAN has no space to compress the IPv6 mobility header, the NEMO basic support protocol could not effectively support the 6L0WPAN sensor network when the sensor network moves to another 6L0WPAN sensor network. In contrast, this invention compresses the mobility headers for binding update and binding acknowledgement messages in the 6L0WPAN sensor network, including the 6LoWPAN_MH dispatch format and the compressed binding update message and binding acknowledgement message format. With the proposed 6LoWPAN_MH dispatch and related messages, network mobility can be well applied to the 6L0WPAN sensor network, and can significantly improve the network mobility efficiency for 6L0WPAN.

2. Since IEEE 802.15.4 only supports a maximum physical layer packet size of 127 bytes and leaves less than 70 bytes for IPv6 data, the traditional binding update message (with a length of minimal 80 bytes of IPv6 data) and binding acknowledgement message (with a length of minimal 60 bytes of IPv6 data) in the N EMO protocol are too heavy for the 6L0WPAN sensor networks. In contrast, in this invention, the compressed binding update message has a length of 32 bytes (1 byte of 6LoWPAN_MH dispatch, 1 byte of LoWPAN_HC1 dispatch, 1 byte of IPv6 header, 0.5 byte of 6LoWPAN_MH header and 28.5 bytes of binding update), and the compressed binding acknowledgement message has a length of 8 bytes (1 byte of 6LoWPAN_MH dispatch, 1 byte of LoWPAN_HC1 dispatch, 1 byte of IPv6 header, 0.5 byte of 6LoWPAN_MH header, and 4.5 bytes of binding acknowledgement). Therefore, the proposed compressed binding update message and binding acknowledgement message can reduce the length of binding messages, and thus cut the signaling overhead for position updates. The method proposed by this invention can generate a prominent technical effect than the traditional NEMO based protocol .

Brief Description of the Drawings

By referring to the following figures, the exemplary embodiment of the invention will be interpreted more comprehensively.

Fig.1 is a schematic diagram of the 6L0WPAN sensor network mobil ity management scenarios;

Fig.2 is a schematic diagram of the IPv6 mobility header format; Fig.3 is a schematic diagram of the BU message format in the NEMO protocol;

Fig.4 is a schematic diagram of the BA message format in the NEMO protocol;

Fig.5 is a sequence chart of a mobility management method according to a embodiment of the invention;

Fig.6 is a flow chart of a mobility management method according to a embodiment of the invention; Fig.7 is a schematic diagram of a header format supporting the BU message according to a embodiment of the invention;

Fig.8 is a schematic diagram of a header format supporting the BA message according to a embodiment of the invention;

Fig.9 is a schematic diagram of a format of the compressed BU message according to a embodiment of the invention;

Fig.10 is a schematic diagram of a format of the compressed BA message according to a embodiment of the invention;

Detailed Description

The exemplary modes of carrying out the invention are introduced in the following part by referring to the figures; however, this invention may be implemented in various forms, not limited to the embodiments described herein. These embodiments are provided for extensively and comprehensively disclosing the invention, and for sufficiently conveying the extent of the invention to those skilled in the art. In the figures, identical units/elements are represented by a uniform figure sign.

Unless otherwise specified, the terms (including technical terms) here shall be interpreted according to general understandings of technicians in the related art. In addition, it is understandable that terms defined by commonly-used dictionaries shall be not be interpreted as having an idealized or overformal significance, but shall be interpreted as having a consistent meaning with the context of its related art.

In order to explain the modes of carrying out the invention more clearly, 6L0WPAN is taken as an example for instruction. It should be appreciated by those skilled in the art that the invention could be applied to other sensor networks.

Fig.5 is a sequence chart of a mobility management method according to a embodiment of the invention. Fig.5 relates to a 6L0WPAN MR, a 6L0WPAN GW, an AAA server and a HA.

First of all, the 6L0WPAN GW in the sensor network periodically sends beacons containing the Personal Area Network (PAN) ID to the Mobile Router. Each 6L0WPAN GW has a unique PAN ID in the sensor network, and the beacon follows a standardized IEEE 802.15.4 beacon frame format.

Once receiving the beacon, the 6L0WPAN MR checks the PAN ID and determines whether it has moved to a new sensor network or not.

If the 6L0WPAN MR moves to another sensor network, it sends an association request message to the 6L0WPAN GW which receives the beacon from the association request message. The association request message indicates to the 6L0WPAN GW that the 6L0WPAN MR is new to the sensor network and wishes to associate with the sensor network. The association request message has a standardized IEEE 802.15.4 MAC command frame format.

When the association request message reaches the 6L0WPAN GW, the 6L0WPAN GW creates a binding entry for the 6L0WPAN MR, and stores the binding entry in a memory, such as ROM or PROM and flash memory device. The 6L0WPAN GW sends an association response message to the 6L0WPAN MR, the message having a standardized IEEE 802.15.4 MAC command frame format. Subsequently, the 6L0WPAN MR performs an authentication to the AAA server through the 6L0WPAN GW. If the authentication fails, the binding update request of the 6L0WPAN MR is then refused.

If the authentication succeeds, the 6L0WPAN MR creates a compressed BU message based on the format of compressing IPv6 mobility header and destination option header according to the embodiment of the invention, and then sends the message to the 6L0WPAN GW. The source and destination addresses of the IPv6 header are the 6L0WPAN MR's care-of address and the HAs IPv6 address, respectively.

The 6L0WPAN GW firstly performs a binding update according to the compressed BU message, namely, updating the address information of the 6L0WPAN MR in the 6L0WPAN GW, then decompresses the compressed BU message and sends the decompressed BU message to the HA. The decompressed BU message is a standard ized BU message, wh ile the compressed BU message is a BU message obtained after adjusting the standardized BU message according to the embodiment of the invention.

Alternatively, the 6L0WPAN GW firstly decompresses the compressed BU message, performs a binding update according to the decompressed BU message, namely, updating the MR's address information in the GW, and then sends the decompressed BU message to the HA.

Upon receiving the standardized BU message, the HA performs a binding update. The HA updates the home address of the 6L0WPAN MR and binds the mobility network prefix in the cache entry.

Next, the HA sends the standardized BA message to the 6L0WPAN GW, and the 6L0WPAN GW decompresses the standardized BA message to obtain a compressed BA message. The 6L0WPAN GW sends the compressed BA message to the 6L0WPAN MR. In this way, a bi-directional tunnel is established between the HA and the 6L0WPAN MR's care-of address.

Fig.6 is a flow chart of a mobility management method according to a embodiment of the invention, but it merely illustrates a part of steps of the mobility management method.

Step 1 : sending a beacon. The 6L0WPAN GW sends a beacon to the 6L0WPAN MR, the beacon including a PAN ID.

Step 2: receiving an association request. The 6L0WPAN GW receives an association request sent by the 6L0WPAN MR.

Step 3: sending an association response. The 6L0WPAN GW sends an association response to the 6L0WPAN MR.

Step 4: authenticating the MR through the AAA server. The 6L0WPAN MR sends an authentication request to the 6L0WPAN GW which forwards the authentication request to the AAA server. The AAA server performs an authentication, sends an authentication success message to the 6L0WPAN GW if the authentication succeeds and sends an authentication failure message to the 6L0WPAN GW if the authentication fails. The 6L0WPAN GW forwards the authentication success/authentication failure message to the 6L0WPAN MR.

If the authentication fails, the 6L0WPAN GW refuses the binding update request of the 6L0WPAN MR; and if the authentication succeeds, step 5 is performed. Step 5: receiving the compressed BU message. The 6L0WPAN GW receives the compressed BU message from MR.

Step 6: performing a binding update according the compressed BU message. The 6L0WPAN GW performs a binding update according to the compressed BU message, namely, updating the address information of the 6L0WPAN MR in the 6L0WPAN GW.

Step 7: decompressing the compressed BU message and sending the decompressed BU message. The 6L0WPAN GW decompresses the compressed BU message and sends the decompressed BU message to the HA.

Alternatively, steps 6 and 7 could be: decompressing the compressed BU message and performing a binding update according to the decompressed BU message. The 6L0WPAN GW performs a binding update according to the decompressed BU message, namely, updating the address information of the 6L0WPAN MR in the 6L0WPAN GW, and then sends the decompressed BU message to the HA. Step 8: performing a binding update to the HA. A binding update is performed on the HA according to the decompressed BU message.

Step 9: sending a BA message. The HA sends a standardized BA message to the 6L0WPAN GW.

Step 10: compressing the standardized BA message. The 6L0WPAN GW compresses the standardized BA message and obtains a compressed BA message. Step 11 : sending the compressed BA message. The 6L0WPAN GW sends the compressed BA message to the 6L0WPAN MR.

In the case, a bi-directional tunnel is established between the HA and the 6L0WPAN MR's care-of address.

The following part is an introduction of message format according to the embodiment of the invention.

The current 6L0WPAN message format does not support BU and BA messages. The embodiment of the invention defines a new method to compress the BU and BA messages in 6L0WPAN sensor networks, and proposes a lightweight network mobility management method for 6LoWPAN when the 6L0WPAN MR moves and connects to another 6L0WPAN sensor network:

1 . A new 6L0WPAN dispatch header pattern, 6LoWPAN_MH, is used to add a compressed IPv6 mobility header to a dispatch. The pattern number of 6L0WPAN MH is 01000100. 2. When the 6LoWPAN_MH is included, the next header bits (bit 5 and 6) in the LoWPAN_HC1 header have a different meaning: 00 means the next header is the proposed 6LoWPAN_MH; other values, such as 01 , 1 0 and 1 1 , are reserved for future extension. The 6LoWPAN_MH header includes 4 bits. The first bit (bit 0) value determines whether the following header is a BU message or a BA message: 0 indicates the BU message, while 1 indicates the BA message.

3. To support the compressed BU message, the 6LoWPAN_MH header contains 4 bits: BU (binding update), A (acknowledgement), H (home registration), and R (mobile router). 4. To support the compressed BA message, the 6LoWPAN_MH header contains 4 bits: BA (binding acknowledgement), R (mobile router), and status (2 bits).

5. The compressed BU message contains the following fields: lifetime (4 bits), sequence number (16 bits), checksum (16 bits), home address (128 bits), and mobile network prefix (64 bits). 6. The compressed BA message contains the following fields: lifetime (4 bits), sequence number (16 bits), and checksum (16 bits).

Fig.7 is a schematic diagram of a header format supporting the BU message according to an embodiment of the invention. When the value of the bit 0 of the 6LoWPAN_MH header is 0, the following header is a BU message. For the BU message, the remained 3 bits of 6LoWPAN_MH header can be summarized as follows:

^■ A: Acknowledgement (bit 1 ): This bit is set by the 6L0WPAN MR to send a request to the receiving node that a BA message should be returned by it upon receipt of the BU message.

^■ H: Home registration (bit 2): This bit is set by the 6L0WPAN MR to request the receiving node to act as the 6L0WPAN MR's home agent.

^■ R: Mobile router (bit 3): This bit is set by the 6L0WPAN MR to indicate that the BU is from a mobile router. Fig.8 is a schematic diagram of a header format supporting the BA message according to an embodiment of the invention. When the value of the bit 0 of the 6LoWPAN_MH header is 1 , the following header is a BA message. For the BA message, the remained 3 bits of 6LoWPAN_MH header can be summarized as follows:

^■ R: Mobile router (bit 1 ): This bit is set to indicate that the home agent which processed the binding update supports mobile routers. It is set to 1 only if the corresponding BU message had the R bit set to 1 .

^■ Status (bit 2 and 3): This bit indicates the configuration of the binding update.

■ 00: BU accepted successfully

■ 01 : No home agent for this node

■ 10: Expired home nonce index

■ 11 : Sequence number out of window

Fig.9 is a schematic diagram of a format of the compressed BU message according to an embodiment of the invention. In the traditional NEMO protocols, two IPv6 extension headers are included in the BU message sent by the MR to its home agent: destination option header for informing the home address, and mobility header for encapsulating the BU message. To reduce the signaling overhead for position updates, this invention integrates the destination option header and the mobility header to generate a compressed BU message. The compressed BU message includes the following fields:

^■ Lifetime (4 bits): This field indicates the remaining time of the BU message.

When the Lifetime is zero, the HA must delete the binding cache entry in relation to the 6L0WPAN MR. ^■ Sequence number (16 bits): This field is used by the receiving node to sequence the binding update messages and by the 6L0WPAN MR to match a returned BA message with this BU message. ^■ Checksum (16 bits): This field contains the checksum of the BU message.

Home address (128 bits): This field contains the home address of the

6L0WPAN MR. It is used by the 6L0WPAN MR to inform the home address it is using, when there are several home addresses.

^■ Mobile network prefix (64 bits): This field contains the mobile network prefix of the 6L0WPAN MR.

Fig.10 is a schematic diagram of a format of the compressed BA message according to an embodiment of the invention. Similarly, the compressed BA message includes the following fields:

^■ Lifetime (4 bits): This field indicates the remaining time for reserving the entry in relation to the 6L0WPAN MR.

^■ Sequence number (16 bits): This field is copied from the sequence number field in the BU message. It is used by the 6L0WPAN MR to match the BA message with the BU message. ^■ Checksum (16 bits): This field contains the checksum of the BA message.

Therefore, the length of binding messages is reduced by the compressed BU message and BA message, whereby the signaling overhead for position updates is reduced. The compressed binding update message has a length of 32 bytes (1 byte of 6LoWPAN_MH dispatch, 1 byte of LoWPAN_HC1 dispatch, 1 byte of IPv6 header, 0.5 byte of 6LoWPAN_MH header and 28.5 bytes of binding update), and the compressed binding acknowledgement message has a length of 8 bytes (1 byte of 6LoWPAN_MH dispatch, 1 byte of LoWPAN_HC1 dispatch, 1 byte of IPv6 header, 0.5 byte of 6LoWPAN_MH header, and 4.5 bytes of binding acknowledgement). In the previous text, the invention has been described through a reference to a small amount of embodiments. Nevertheless, those skilled in the art are all aware that, as defined by the attached claims, other embodiments than the above ones equally fall into the extent of the invention. Commonly, all the terms used in the claims should be interpreted in line with their usual meanings in the art, unless otherwise explicitly defined. All the references to "a/said/the (apparatus, assembly, etc.)" shall be openly explained as at least one embod iment of said apparatus, assembly, etc., unless otherwise clearly specified. None of the steps of any of the methods disclosed herein are required to be executed in an open and accurate order, unless otherwise clarified.

Claims

Claims: What is claimed is:

1 . A method, characterized in that, comprising:

receiving a compressed binding update message;

2. The method according to claim 1 , characterized in that, after sending said decompressed binding update message to the home agent, performing a binding update on the home agent based on said decompressed binding update message.

3. The method according to claim 1 or 2, characterized in that, receiving a binding acknowledgement message sent by said home agent, compressing said binding acknowledgement message and send ing said compressed binding acknowledgement message to a mobile router.

4. The method according to claim 1 , characterized in that, before receiving said compressed binding update message, further comprising: authenticating the mobile router through an authentication, authorization and accounting server.

5. The method according to claim 1 , characterized in that, before receiving said compressed binding update message, further comprising: receiving an association request sent by the mobile router and send an association response to the mobile router.

6. The method according to claim 1 , characterized in that, said compressed binding update message is sent by the mobile router.

7. The method according to claim 1 , characterized in that, said compressed binding update message comprising: Lifetime, Sequence number, Checksum, Home address and Mobile network prefix.

8. The method according to claim 3, characterized in that, said compressed binding acknowledge message comprising: Lifetime, Sequence number and Checksum.

9. A device, characterized in that, comprising:

means for receiving a compressed binding update message;

means for performing a binding update according to said compressed binding update message; and

10. The device according to claim 9, characterized in that, further comprising a means for performing a binding update on the home agent based on said decompressed binding update message.

11 . The device according to claim 9 or 10, characterized in that, further comprising means for receiving a binding acknowledgement message sent by said home agent, compressing said binding acknowledgement message and sending said compressed binding acknowledgement message to a mobile router.

12. The device according to claim 9, characterized in that, further comprising means for authenticating the mobile router through an authentication, authorization and accounting server.

13. The device according to claim 9, characterized in that, further comprising means for receiving an association request sent by the mobile router and send an association response to the mobile router.

14. The device according to claim 9, characterized in that, said compressed binding update message is sent by the mobile router.

15. The device according to claim 9, characterized in that, said compressed binding update message comprising: Lifetime, Sequence number, Checksum, Home address and Mobile network prefix.

16. The device according to claim 11 , characterized in that, said compressed binding acknowledge message comprising: Lifetime, Sequence number and Checksum.