1 / 9

The limitation in current NEMO scenario -Problem Statement

The limitation in current NEMO scenario -Problem Statement. draft-zhao-nemo-limitations-ps-00.txt John.zhao (Huawei technology shanghai R&D) Ke lin (Shanghai jiao tong university) Wen tao zhong (Shanghai jiao tong university) 2007-12-01. Index. Problems and solutions MR loop

nadine
Télécharger la présentation

The limitation in current NEMO scenario -Problem Statement

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The limitation in current NEMO scenario -Problem Statement draft-zhao-nemo-limitations-ps-00.txt John.zhao(Huawei technology shanghai R&D) Ke lin (Shanghai jiao tong university) Wen tao zhong (Shanghai jiao tong university) 2007-12-01

  2. Index • Problems and solutions • MR loop • Entry point selection • PMIP related • Conclusions and suggestion • Future plan • Next step • References

  3. Problem 1 ---- MR loop Problem: The MR may establish the route loop each other. Suggestion: We need to distinguish the MR.

  4. Problem 2 ---- entry point selection Problem: The mobile entities(MR or MN) need to select a more stable entry point as the selection to visit the internet. Suggestion: Let the mobile learn some more information about the upper level router.

  5. Dst=LFN’s prefix + node ID CN’s Addr Src Dst Payload Dst=LFN’s prefix + node ID Dst=LFN’s prefix + node ID Src Src Dst Dst Src Src Dst Dst Payload Payload CN’s Addr CN’s Addr LMA’s Addr MAG’s Addr MR’s CoA MR’s HoA Dst=LFN’s prefix + node ID Src Dst Payload CN’s Addr Scenarios of PMIP related • The network is PMIPv6 enabled. (MIPv4 is similar) • MR bootstrapping in this PMIPv6 network. • MR didn’t run the NEMO protocol(RFC3963) and network use PMIP to management its mobility. • We use the root MR as the example, and others is similar.But if nested MR occurred, RO is suggested to promote the efficiency. ? LMA/HA needs the binding info for the LFN’s prefix as the following: MRIDMR’s HoAMR’s CoALFN’s Prefix

  6. Problems and requirements of PMIP related • 1)How to forward the packets destinated to the nodes under the MR? • MAG send the PBU included with the LFN’s prefix to LMA/HA. • 2)Where to find the LFN’s prefix of that MR? • Policy server • Getting it/them from that MR • 3)When does the MAG send the PBU? • When the MR enter into the PMIPv6 domain. • 4)How does the MAG know this is a MR but not a MN? • Policy server • Getting it/them from that MR

  7. solution PBU(with LFN’s prefix) Really? I need help you binding your LFN’s prefix in LMA/HA. This is a MR (Optional includeing with the LFN’s prefix)

  8. Conclusions and suggestion • Conclusions: • Mobile router is difference to mobile node in pmip scenario and need to be learnt by pmip domain; • If can mobile router know each other and the distinguish with those fixed routers, it maybe useful for the best route path selection and the access to the internet. • Suggestion: • We suggest that we can extend current router discovery messages to achieve these goals.

  9. Next step • Agree to these problems? • Agree to these solutions? • We need to provide this details as above? • If true, if this draft can be accepted in mext? • Other suggestions?

More Related