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

RE: [802.21] Network Controlled Handover and IS



Hi Reijo,

Please find my comments below.

Regards,
Ulises

-----Original Message-----
From: Reijo Salminen [mailto:reijo.salminen@SEESTA.COM] 
Sent: Tuesday, August 30, 2005 2:03 AM
To: STDS-802-21@listserv.ieee.org
Subject: Re: [802.21] Network Controlled Handover and IS

-----Original Message-----
From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of
stefano.faccin@nokia.com
Sent: 25. elokuuta 2005 9:55
To: STDS-802-21@listserv.ieee.org
Subject: RE: Re: [802.21] Network Controlled Handover and IS

Junghoon,

-----Original Message-----
From: ext Junghoon Jee [mailto:jhjee@etri.re.kr]
Sent: Wednesday, August 24, 2005 11:29
To: Faccin Stefano (Nokia-NRC/Dallas); STDS-802-21@LISTSERV.IEEE.ORG
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.


[[Stefano] ]  I surely don't disagree that there are challenges.
however,
there are at present requirements coming from some 3GPP operators to
enable
such network controlled handoffs, and I believe 802.21 should enable
them.
If one wants to use them or not, that's up to the manufactures and
operators. If we do not enable the scenarios for which we have
requirements,
we risk to restrict 802.21 applicability to the real world.

[Reijo] In
21-05-0344-00-0000-Aug25_2005_3GPPRequrements_Telecom_MoM.doc
2.1.2 and 2.4.1 is stated "Note that 3GPP has stopped work on scenarios
4
and higher". I'm a bit puzzled with with the requirement situation at
3GPP,
I hope the situation will be clarified eg in the next 3GPP-adhoc.

[UO] The statement just means that there aren't explicit working groups
addressing these scenarios in the same way that other scenarios were
addressed (e.g., Scenario 3). However there are other groups (e.g., SA)
addressing inter-technology handovers under different umbrellas (e.g.,
Long Term Evolution and Voice Call Continuity). I will include this as a
discussion topic for our coming teleconference.


BR Reijo