1 / 3

Enhancing Mobile Network Path Discovery: A Proxy-Based Approach for QoS NSIS

This draft proposes a concrete procedure for pre-CRN discovery aimed at facilitating fast state installation by establishing a new path before the mobile node (MN) transitions. The solution employs a QoS-aware proxy that retrieves current flow and session IDs from the MN. It exchanges messages with the correspondent node (CN) to gather information on overlapping paths, thereby identifying the Candidate Resource Node (CRN) for both uplink and downlink. Key open issues include integration with QoS-NSLP, potential enhancement functionalities, compatibility with NTLP/GIMPS, interactions with mobility protocols, and security considerations.

emerald-mills
Download Presentation

Enhancing Mobile Network Path Discovery: A Proxy-Based Approach for QoS NSIS

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. Pre CRN discovery from proxy on candidate new path draft-sanda-nsis-mobility-qos-proxy-01.txt Takako Sanda and Toyoki Ue 2-Mar. 2004

  2. Message (flow ID, session ID) Oldpath mQNE mQNE mQNE mQNE Oldpath OAR NAR Proxy Short Summary [Goal] • Proposing one concrete procedure of pre CRN discovery for fast state installation (establish new path before MN actually moves) [Solution] • Utilizing Proxy (QoS NSIS-aware NAR) • Proxy receives current flow ID and session ID from MN, which are currently used between MN and CN • The proxy exchanges messages with CN, which containing the session ID and flow ID pair to gather overlapping paths information • By analyzing the overlapping paths information, the proxy knows CRN (for both uplink and downlink) ExpectedNew path

  3. Open issues • How it works with QoS-NSLP ? • Would it be possible to add some functionalities to QUERY or RESPONSE or NOTIFY? • How it works with NTLP/GIMPS? • How it works with mobility protocols? • Security? Thank You!

More Related