Re: [802.21] MIH commands for handover
Hello Jing
I agree with u...but the flow which
I sent in my last mail was, considering that
the target N/W has been selected by
the MN. so whenever the candidate
query is sent by MN, it already has
decided the target n/w. this is just a initial level
of thought which I tried to share with
you all....who got good knowledge on it...
But this thought process wont work good
if the MN got more than 2 L2 interface, then
it needs to send the list of target
networks in the candidate query & once it receives
the response, it has to commit to one
of them using candidate commit request, & that
time the PAR can initiate the tunneling
mechanism.
In this scenario, we may need to change
the commit request parameters...
well I got a flow for reactive mode
as well...please comment on this
Explanation of above depicted
flow:
As explained in Predictive mode.
MIH_MN_HO_Candidate_Query.Request
should be sent to NAR with New CoA & source address same as NCoA &
Candidate Network Address as NAR’s IP address. This will indicate the
NAR about Reactive Mode handover.
Once the NAR receives this request
message it should verify the NCoA for duplicity. If the address is found
duplicate, NAR should find out a new address & update it in received
MIH_MN_HO_Candidate_Query.Request .
After address verification, the
same request packet should be sent to PAR. PAR’s address would be received
from MIH_MN_HO_Complete.Request.
When PAR receives MIH_MN_HO_Candidate_Query.Request,
it must check the CandidateNwAddr with SourceIP of the received packet.
This tells the handover is Reactive.
PAR should initiate tunnel creation
(end points PAR to MN) using MN’s confirmed NCoA.
PAR should send the MIH_MN_HO_Candidate_Query.Response
to NAR over tunnel. This response will carry the confirmed NCoA of MN.
NAR starts sending packets to MN.
Once MN gets the MIH_MN_HO_Candidate_Query.Response message, it will get
the confirmed NCoA.
thanks & regards
Sanjib
______________________________________________________________________