| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hello，Sanjib
I agree your idea using MIH messages to
carry some MMP(mobility management protocol) information during handover
procedure. But the implementation method you proposed may exist some problems.
From the chart we can see MN can generate the NCoA from the available prefix
info obtained from IS Server, then MN sends these configured NCoAs to all
candidate NARs existed in each candidate networks to make Duplicate Address
Detection. After duplicity checking, PAR in serving network will create the
tunnel with these candidate NARs for sending the packets. So these steps such as
NCoA configuration、duplicity checking and tunnel building work with all
candidate networks, that will increase the spending of network resources.
I suggest whether we can do these works after network decision, namely once the target network is chosen, MN can generate the NCoA only for target NCoA in target network, and sends this NCoA to the target NAR by MIH_MN_HO_Commit.request and MIH_N2N_HO_Commit.request messages. Target NAR will make duplicity checking after receiving these messages, and return the result of DAD to PAR in serving network. Then PAR will create the tunnel with the target NAR. This will save network resources and enhance the efficiency of handover. regards,
Jing
Liu **********************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure,reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! ********************************************************************** |