Presentation is loading. Please wait.

Presentation is loading. Please wait.

IEEE 802.15-07-0771r0 Submission July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks.

Similar presentations


Presentation on theme: "IEEE 802.15-07-0771r0 Submission July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks."— Presentation transcript:

1 IEEE r0 Submission July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Slide 1 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: [IEEE WPAN Mesh Networks] Date Submitted: [July, 2007] Source: [Rui Zhang*, Hakyung Jung**, Eunjoo Lee ***, Myung Lee*] Company [*CUNY, ** SNU, *** ETRI ] Address [Electrical Engineering, Steinman Hall, 140 th St & Convent Ave, New York, NY 10031, USA] Voice:[ ], FAX: [ ], Re: [] Abstract:[This proposal discusses Portability issue arising in IEEE WPAN Mesh] Purpose:[This proposal is provided for the discussion for IEEE WPAN Mesh] Notice:This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release:The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P

2 IEEE r0 SubmissionSlide 2 IEEE WPAN Portability Proposal Rui Zhang*, Hakyung Jung**, Eunjoo. Lee***, Myung Lee* * CUNY, ** SNU, *** ETRI July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

3 IEEE r0 SubmissionSlide 3 Objectives To propose a leaf node portability based on the current IEEE draft. Proposed leaf node portability includes following features: –Automatic portability detection –Compatible with current IEEE address scheme –Compatible with current IEEE routing scheme July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

4 IEEE r0 SubmissionSlide 4 Proposal Outline Step1: Detect the problem Step2: Carry out the MESH rejoin procedure –Step2-1: Active scanning –Step2-2: Select new parent & Association request (Portable DEV) –Step2-3: Address allocation & Association response (Potential Parent) Step3: Inform relevant nodes of the portable node’s movement Step4: Update the link-state table July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

5 IEEE r0 SubmissionSlide 5 Step1: Detect the problem July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

6 IEEE r0 SubmissionSlide 6 Detection the link failure by ACK missing Optionally, use of absence of periodic Hello exchanges depending on the frequency of Hello interval Data Ack X Data No Ack Detection by leaf node Step1: Detect the problem July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

7 IEEE r0 SubmissionSlide 7 Data Ack X Data No Ack Detection by parent Step1: Detect the problem July 2007 R. Zhang, H. Jung, E. Lee, M. Lee The same detection method as before. Note: If the parents detect the problem, it will trigger the link failure process (probe). - The parent broadcasts link failure and relevant nodes change NB list and connectivity matrix - If any node sends packet to the portable node before it report its new address, relevant nodes will send back route error message to the sender.

8 IEEE r0 SubmissionSlide 8 Step 2: Carry out the MESH rejoin procedure July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

9 IEEE r0 SubmissionSlide 9 Step2-1: Active scanning - Initiates the MESH rejoin procedure. - Performs ‘active scanning’ - Beacon frame contain coordinator status. Step 2: Carry out the MESH rejoin procedure July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

10 IEEE r0 SubmissionSlide 10 Step 2: Carry out the MESH rejoin procedure Potential parent with insufficient capability Potential parent with sufficient capability Beacon (w/ capable status) Portable device Beacon (w/ incapable status) Additional information in beacon payload can prevent the portable device from selecting an incapable device as a suitable parent July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

11 IEEE r0 SubmissionSlide 11 Step 2: Carry out the MESH rejoin procedure Step2-2: Select new parent & Association request (Portable DEV) - Choose the suitable parent address Note: “suitable parent” is regarded as implementation issue Rejoining to previously joined parent can be advantageous - Initiate MAC association procedure. July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

12 IEEE r0 SubmissionSlide 12 Step 2: Carry out the MESH rejoin procedure July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Step2-3: Address allocation & Association response -The MDEV that received MAC Association Request command determines whether it has knowledge of requesting device If yes, allocate the previously assigned short address If no, assign new short address - Association Response with new short address for portable device. - If the attempt to rejoin was unsuccessful, trigger the rejoin procedure with the second best potential parents from step2-2.

13 IEEE r0 SubmissionSlide 13 Step 2: Carry out the MESH rejoin procedure Potential parent with insufficient capability Potential parent with sufficient capability Beacon (w/ capable status) Portable device Beacon (w/ incapable status) The Associate response will contain the short address for the portable device July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Associate Request (Rejoin) Associate Response (Rejoin)

14 IEEE r0 SubmissionSlide 14 Step 3: Inform relevant nodes of the node’s movement Note: We have two different approaches to inform the portability. Centralized: we should inform old parents and network coordinator(NC) of the portable device rejoin. Distributed: we only need to inform old parents of the portable device rejoin. July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

15 IEEE r0 SubmissionSlide 15 Unicast Rejoin-Notify to the old parent and NC ① Portable device IEEE address ② Portable device new short address ③ Portable device previous short address NC updates the Address Mapping Table –NC shall maintain Address Mapping Table, which stores a mapping between IEEE address and short address of devices Step 3: Centralized: Inform the old parent and NC of the rejoin July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

16 IEEE r0 SubmissionSlide 16 On receipt of Rejoin-Notify, the old parent will broadcast Move Notify containing the old and new short address. On receipt of Move-Notify, the devices change the status of corresponding entry in neighbor list to “Moved” state and update the connectivity matrix Step 3: Centralized: Inform the old parent and NC of the rejoin July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

17 IEEE r0 Submission May 2005 Zheng, Liu, Zhu, Wong, LeeSlide 17 After that, Once there is a packet for the portable device. – Any device having information of “moved node” will indicate this error by replying Route Error to the originating sender – On receipt of Route Error, the originating sender will query NC about new short address – On receipt of query, the NC will respond the new short address to the originating sender Step 3: Centralized: Inform the old parent and NC of the rejoin

18 IEEE r0 Submission18 1. Move X Portable device 2.Rejoin Notify 4. Move Notify Data Sender Data Pan Coordinator 3. Update Address Mapping Table Addr Request and response Step 3: Centralized: Inform the old parent and NC of the rejoin July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Associate exchange Route Error

19 IEEE r0 SubmissionSlide 19 Step 3: Distributed: Inform the old parent rejoin Compared with centralized approach, the distributed approach has several differences as follows: Do not use network coordinator for keeping the address mapping table. The move notify contain both the new/old short address of portable device. Data will be re-routing when it arrives at nodes which receive the move-notify. July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

20 IEEE r0 SubmissionSlide Move X Pan Coordinator Portable device 2.Rejoin Notify 3. Move Notify Data Sender Data Addr Resp Data Step 3: Distributed: Inform the old parent rejoin July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Associate exchange

21 IEEE r0 SubmissionSlide 21 Step 4: Update the link-state table July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

22 IEEE r0 SubmissionSlide 22 Step 4: Update the link-state table Update the link-state table : New parent broadcasts Hello message to notify the neighbors of its link-state change July 2007 R. Zhang, H. Jung, E. Lee, M. Lee

23 IEEE r0 Submission May 2005 Zheng, Liu, Zhu, Wong, LeeSlide 23 Right now the implementation is in progress. Thanks Q & A


Download ppt "IEEE 802.15-07-0771r0 Submission July 2007 R. Zhang, H. Jung, E. Lee, M. Lee Slide 1 Project: IEEE P802.15 Working Group for Wireless Personal Area Networks."

Similar presentations


Ads by Google