Inter-Mobility Support in Controlled 6LoWPAN Networks Zinonos, Z. and Vassiliou, V., GLOBECOM...

Inter-Mobility Support in Controlled 6LoWPAN Networks

Zinonos, Z. and Vassiliou, V., GLOBECOM Workshops, 2010 IEEE

Outline

2

Abstract Two types of mobility Intra-PAN (micro-mobility) Inter-PAN (macro-mobility) Evaluation Conclusion

Abstract

3

This paper propose a new mobility management protocol for 6LoWPAN uses the technology of Proxy Agents and aims to enhance the

handoff time by predicting or rapidly responding to a handover event.

Supportive in mobility scenarios in order to reduce the number of signaling between the MN and the Home Agent.

Two types of mobility Intra-PAN (micro-mobility)

Device movement within a single Wireless PAN domain. The sensor node moves within the domain without losing the

connectivity with the Sink node. Inter-PAN (macro-mobility)

Device movement between multiple Wireless PAN domains. Sensor nodes move between different sensor networks, each

one with its Sink node responsible to configure and manage all the aggregated devices.

The IPv6 prefix of the network is changed.

4

Intra and Inter PAN mobility

HA1 HA2

Backbonerouter

Internet

PAN 1

PAN 2

Proxy

Mobility Node

Intra-PAN

Inter-PAN

5

Intra-PAN mobility scenario

1. 6LoWPAN PAs located in the same network will advertise the same prefix.

2. The address of the MN inside the same network is not changed.

3. All the data from/to the MN are not routed via the PA but from the other neighbors nodes based on the routing protocol that is used.

4. The proxy node and MN exchange packets when the MN is bootstrapping.

6

Intra-PAN mobility procedure

7

Inter-PAN mobility scenario

1. 6LoWPAN proxy agents located in different networks will advertise different prefixes.

2. Home Agents have direct access between them.

3. The address of the MN when is moving between different PANs is changed.

4. The parent proxies have all the necessary information to perform the Duplicate Address Detection (DAD) procedure on behalf of the MN.

5. The Home Agents are responsible to create the 16-bit address of the MN that will be used to route packets inside the 6LoWPAN network.

8

Inter-PAN mobility scenario (cont.)

6. The Home Agents will maintain a binding table where the Global IPv6 address, the Care-of Address, the 16-bit address, the parent proxy address and a timestamp is stored as shown in Table I.

9

Inter-PAN mobility procedure

FCBU = Fast Binding UpdateFCBA = Fast Binding AcknowledgementBU=Binding UpdateBA= Binding AcknowledgementProxy Conf = Proxy confirmation

10

Inter-PAN mobility procedure (cont.)

11

HA1 HA2

Backbonerouter

Internet

PAN 1

PAN 2

Proxy

Mobility Node

1. RSSI

2. join3. FCBU

4. BU

5. BA

6. FCBA

7. joinACK

MN mode state

12

The proxies must be configured to send advertisements to their serving MNs in a predefined interval (every second) so that to guarantee that the node mobility can be detected.

MN will be aware of that interval.

Evaluation

13

The general handover delay for all the protocols can analytically be computed as:

D = DL2 + DBS + DREG + DPROC (1)

DL2 Link Layer Establishment Delay

DBS Bootstrapping (ND (DND) and DAD (DDAD) )

DREG BU/Registration Delay

DPROC Processing and queuing delay

Evaluation

14

The total transmit bytes are equal to trigger bytes + FCBU bytes + JoinAck bytes = 103 bytes.

The total received bytes are equal toTotal = #joins ∗ 37bytes + FCBAckbytes

+ProxyConfbytes = 109bytes (2)

Evaluation

15

MN signaling cost

Conclusion This paper proposed a mobility model that promises soft

handoffs and controlled disconnections between different PANs.

The model is based on the involvement of a proxy node that is responsible to handle, on behalf of the MN, the mobility-related messages.

This work has performed a detailed decomposition and analysis of the handover delay and has shown the validity and applicability of the proposed solution.

16

每周一句

17

in order to = to In order to support a network-based solution we introduce

an entity called 6LoWPAN proxy agent (PA). This means that it must be pre-configured to wait for a specific

time interval before sending a Join Ack message in order to make sure that all possible Join messages arrive.

so as to for the purpose of

Thanks for listening.