Multicast Routing in Proxy Mobile IPv6 via LMA Mediation
Solution Overview
Problem
Current Proxy Mobile IPv6 (PMIPv6) protocols lack support for multicast routing, which is essential for providing IP wireless broadband services such as mobile IPTV, content broadcasting, and gaming, as mobile access gateways (MAGs) are not configured to handle multicast routing.
Innovation Solution
The system enables multicast routing in PMIPv6 by configuring the MAG to receive tunneled multicast packets from the Local Mobility Anchor (LMA), decapsulate them, and forward the packets to mobile nodes (MNs), allowing MNs to subscribe to multicast groups and maintain multicast states, with the LMA duplicating and encapsulating packets for each subscriber, and redirecting them through bi-directional tunnels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MAG is configured to support multicast routing, then multicast services can be provided to mobile users, but device complexity increases
Solution Approach 1:
The LMA acts as an intermediary that performs multicast routing functions on behalf of the MAG. The LMA receives multicast packets from the network, duplicates them for multiple MNs, encapsulates them in PMIPv6 tunnel packets, and forwards them through the MAG to the mobile nodes. This mediator approach allows the MAG to provide multicast services without needing complex multicast routing configuration.
Solution Approach 2:
The LMA creates copies of multicast packets for each subscribing MN and encapsulates each copy in a separate PMIPv6 tunnel packet. This copying mechanism enables one-to-many delivery through the tunnel interface, allowing the MAG to forward multiple encapsulated copies without needing to understand multicast routing itself.
2Ease of operation
If PMIPv6 protocol is used for mobility management, then mobile nodes can avoid handling their own mobility, but multicast routing support is lost
Solution Approach 1:
The patent merges multicast routing functionality with the PMIPv6 protocol framework by extending the tunneling mechanism. Multicast packets are encapsulated in PMIPv6 tunnel packets using the same infrastructure that handles unicast mobility management. This merging allows the PMIPv6 system to provide both automated mobility management and multicast routing support through a unified protocol extension.
Solution Approach 2:
The PMIPv6 tunnel interface and encapsulation mechanism are made multi-functional, serving both traditional unicast mobility management and the new multicast routing function. The same tunnel interface that handles regular PMIPv6 traffic is also used to carry encapsulated multicast packets, allowing one system to perform multiple functions without requiring separate dedicated infrastructure.
3Reliability
If multicast packets are tunneled through PMIPv6 infrastructure, then seamless multicast services during handover are achieved, but packet structure complexity increases
Solution Approach 1:
The LMA performs preliminary actions by pre-duplicating multicast packets for all subscribing MNs and pre-encapsulating them in PMIPv6 tunnel packets before handover occurs. When an MN moves to a new MAG, the LMA has already prepared the encapsulated packets and can immediately redirect them through the new tunnel, ensuring seamless service continuity without requiring complex real-time packet restructuring during handover.
Data Source
AI summary
An apparatus comprising a mobile access gateway (MAG) configured to receive a tunneled multicast packet from a local mobility anchor (LMA), decapsulate the tunneled multicast packet, and forward the multicast packet to a mobile node (MN). A network component comprising at least one processor configured to implement a method comprising receiving a request message tunneled by a MAG for a MN, wherein the request message indicates that the MN wants to join a multicast group, decapsulating the tunneled message, connecting to a router for the multicast group, receiving a multicast packet from the router, and sending a tunneled multicast packet to the MN via the MAG, wherein the tunneled multicast packet has at least three Internet Protocol (IP) layer or layer 3 headers.