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

Re: [802.21] [Mipshop] Re: Architectural Considerations for Handover InformationServices (was: Re: CARD Discussion Query Discussion)

Apparently, we still have very different ideas in mind when we talk about IS
concerning what it is. A lot of discussions so far concerns how it should be
supported. Peretz, I think you pointed out the consequence that we can only
disagree about the assumption of IS.

How IS is to be used and should be supported depends on what information IS
is dealing with. If we do not have consensus on the nature/type/purpose of
information to be coped with in IS, I don't see how 802.21 can produce a
requirement on IS and how  MIPSHOP knows what it is doing for IS.

Cheers,
Hong-Yon


> From: Peretz Feder <pfeder@LUCENT.COM>
> Organization: Lucent Technologies
> Reply-To: Peretz Feder <pfeder@LUCENT.COM>
> Date: Thu, 20 Oct 2005 01:03:18 -0400
> To: <STDS-802-21@LISTSERV.IEEE.ORG>
> Subject: Re: [802.21] [Mipshop] Re: Architectural Considerations for Handover
> InformationServices (was: Re: CARD Discussion Query Discussion)
> 
> On 10/18/2005 6:11 PM, Qiaobing Xie wrote:
>> Yoshihiro Ohba wrote:
>> ...
>> 
>>> - In reality, 3GPP2 has XML-based method (e.g., XCAP) in its
>>> dependency list.
>> 
>> 
>> If I remember it right XCAP/XML is used there for maintaining the
>> address book/buddy list that sort of things. I can imagine that sort of
>> events only happen at most no more than a few times a day for any given
>> user and probably only happen when the user is NOT in a call. In
>> contrast, IS query/response likely will be part of the h/o call flow...
> 
> You are assuming IS is a dynamic information that can influence Handover per
> the
> IS query response. Many .21 members do not agree with this position. IS should
> be treated as static information that is provided to the HO decision entity in
> advance.
> 
>> 
>> regards,
>> -Qiaobing
>> 
>> 
>>> Yoshihiro Ohba
>>> 
>>> 
>>> 
>>