Re: [multimob] Comments on draft-deng-multimob-pmip6-requirement-01.txt

Hi,hui

    Forget to post the reply in maillist. See following comments.
    You are right. They are all need MN to send the request to join to
trigger the receive of multicast except the CMMB , I'm not sure. But it is
because we didn't have other methods to be used before. Currently, some
system just like IEEE802.16 is discussing about this kind of support via
layer-2, once it is ready, then the joinging in layer-3 can be omitted. In
another side, the DVB-H is another case, since it havn't the uplink , so
even mobile node want to send the joining request, but the request can't be
sent to network. It is a kind of "uni-direction link". I think it is useful
for operator to push some feature service within its domian .
    How about it?

    Best Rgds,
Thanks,

john.zhao

  _____  

Hi, John,

Sorry for my late reply, here you are suggesting that we would better
include network preconfigured multicast service which need infrastrucutre
support.

What I could remind is that normally such kind of service will be provided
by MBMS, BCMCS, especially mobile TV service they also could be based on
dedicated TV mechanism like CMMB.

thanks for your discussion.

-Hui

2008/10/24 John.zhao <john.zhao@huawei.com>

Hello,Hui and all

    One comments on section 3.1 about "R2 - The mobile node is responsible
for initially subscribing to the multicast group(s)." . To some network
control multicast service, this subscribtion info can be got from policy
store or pre-configuration on MAG. I don't object MN can't initiate the
subscribtion,but the subscribtion is no need rely on the request come from
MN only. With only MN initiated subscription of multicast group(s),the
operator's network will:
 1.1)No network originated service support. All of any kind of multicast
service will be initiated from MN.But in fact, there are still some typical
service should be managed from network side.From the point of view of the MN
it is like a TV broadcast model. It is worth to handle this case too because
it may corresponds to DVB-H mobile TV service use-case.
 1.2)Cost additional wireless resource in wireless situation. Without it ,
we can save more resource not only during handover but also in network entry
progress. Espically, it is useful to those static multicast tree scenario.
    From the architecture perspective, the support of network management is
the base of MN management. Since other signal flow will be the same except
MAG need have the ability to deal with additional MLD report sent from MN.So
it is no more additional cost on current design but bring a better
scability.

    In detail, the progress of the management of multicast service by
network just like the following:
 When the MN just attachs to a MAG, the MAG will get the MN's profile and
will know some pre-configured multicast services need to be established,
then it will ask LMA to provide the respective service, in this case, the
method used to communicate to LMA from MAG can be either PMIP signals or MLD
report(join) messages etc. LMA will check about this request and do the
decision based on it's acknowledges about it.
     During handover, it will be very like current design. The CXT is expect
to provide necessary multicast infomation and if need, a 3-rd party policy
store is required. 

    On summary, considering and allowing network administrativly
subscription didn't impact on anything current we have considered and in
addition , it can bring a scalability to current requirement of proxy
multicast mobility.

    Best Rgds,
Thanks,

john.zhao