1 / 7

Multicast Handover Techniques: Protocol Choices and Context Transfer in IETF82 Discussion

This document presents insights from the IETF82 Multimob Working Group meeting held on November 15, 2011, in Taipei. It discusses various techniques for improving multicast handovers, including early joining of new multicast access groups, proactive context transfer, immediate delivery of multicast packets after handover, and buffering strategies in new multicast access gateways. The challenges of managing duplicated packets, latency issues, and the interplay between unicast and multicast handovers are examined. This discussion aims to streamline protocols for efficient communication in mobile networks.

lyn
Télécharger la présentation

Multicast Handover Techniques: Protocol Choices and Context Transfer in IETF82 Discussion

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. Multicast handover discussion Marco Liebsch IETF82, Taipei Multimob WG 15th November 2011

  2. …meant as input to the discussion towards finding a good choice for a protocol base

  3. Techniques on the table • Early and/or fast join of the new MAG to the MC group to receive relevant content • Proactive transfer of group and source context from pMAG to nMAG • 2 approaches: inter-MAG CTX transfer or CTX transfer via LMA • Immediate delivery of MC packets from new MAG to MN after handover • Proactive transfer of MN information may not help • MC router must wait until signal from MN received • Attach can trigger a Query from nMAG • Forwarding of MC data from pMAG to nMAG • Avoid missing MC packets

  4. Forwarding of MC data from pMAG • Can help to avoid missing MC packets in case.. • nMAG has not joined the MC group before • high latency in nMAG joining the MC group • nMAG buffers forwarded MC packets • client can buffer all packets after delivery when attached to nMAG • client plays buffered packets without dropping them • Real time data?

  5. Forwarding of MC data from pMAG • For further consideration.. • How to treat duplicated packets on the nMAG? • Forwarded and received on MC channel • Which ones to forward? • Default client may use only small buffer • Default client may drop delayed packets • If not, it continues playing them with permanent delay • Reordering • Solve it on Client or on nMAG? • Don’t address it? • If forwarding is optional, who decides using it? • Dynamic protocol component? • Static setting by means of Administration / Operator?

  6. nMAG joining the MC group • Alignment of Unicast and Multicast handover has been mentioned as requirement • However, most important seems a common handover target (nMAG) • Beside that, Unicast and Multicast states.. • can be established at different timing • State about MC group to join can be established on nMAG before unicast state (most time critical) • can be established using different protocols • CTX approach may depend on available security associations • Inter-MAG vs. transfer via LMA… both have pros and cons

  7. Impact on MC Router operation • nMAG joins MC group and sources based on CTX transfer mechanisms • nMAG may send MC Query to MN immediately after attach • How much is the impact on standard MC Router operations?

More Related