Question: In an MBMS architecture, when a GGSN uses IP multicast for distribution and an RNC rejects it, how does the GGSN handle payload distribution to that RNC?
Option 1: The GGSN repeats the IP multicast attempt until the RNC accepts.
Option 2: The GGSN bypasses the RNC and only sends the payload to accepting RNCs.
Option 3: The GGSN provides legacy MBMS payload distribution via SGSNs using point-to-point GTP-tunnels, removing synchronization protocol elements before forwarding.
Option 4: The GGSN terminates the entire MBMS session due to the rejection.
Explanation: This is correct because when an RNC rejects IP multicast distribution in an MBMS setup, the GGSN must adapt to ensure the RNC still receives the payload. The GGSN uses legacy MBMS payload distribution methods (via point-to-point GTP-tunnels through SGSNs) for those rejecting RNCs, removing synchronization protocol elements before forwarding to maintain compatibility.