Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: Re: [802.21] Network Controlled Handover and IS



I must agree with Junghoon Jee. It simplifies matters tremendously, and decreases non-productive management and control messaging on the air interface dramatically, to have the MS play a more intrinsic role in inter-technology handover decision (mobility policy engine locus of control).
 
Thanks,
Phillip Barber
Huawei
 
----- Original Message -----
Sent: Wednesday, August 24, 2005 11:28 AM
Subject: RE: Re: [802.21] Network Controlled Handover and IS

Hi Vivek and Stefano,
 
[Vivek G Gupta]
Many of the existing media specific technologies already do this in some form. For example 802.11k provides access to link layer measurements like Bit Rate, BER, etc. that you mention above. Other media specific technologies also have a provision for something similar.
Given that, do we need any additional methods/primitives or capabilities from 802.21 for above?

[[Stefano] ]  I think the answer is completely depending on the use scenarios. Let's assume a 3GPP network operator owns multiple accesses, such as 802.11 and 802.16 in addition to the 3GPP specific access networks. Let's assume the operator is interested in having network controlled HO e.g. for load sharing or other reasons that require stricter control that the one granted by simply controlling the policies in the terminal used to decide HO between technologies. In such case, it may be difficult in practical implementations to have an MME function in the network that relies on existing L2 technology-specific to collect the information. it pretty much implies a tight IW of the various radio interfaces/ANs at L2, that may not be that easy to implement nor that acceptable to 3GPP operators/vendors. In such scenario, using 802.21 at "L3 and above" to allow reporting of information to the MIHF in an MME that is used to control inter-technology HO may be an easy and clean way to!
  go. I see this as a very relevant scenario for "L3 and above" MIH.
=>
[Junghoon]
I tend to agree about the scenario that Stefano mentioned as a general application of MIH.
However, I have some concern regarding the network-initiated inter-technology handover.
To support not one or two mobile terminals, overloading of MIH _handover_ control entity by enormous MIH events and commands...
IMO, it would be better to let a mobile terminal have a brain about inter-technology handover decision.