RE: [802.21] [Mipshop] Re: Architectural Considerations for Handover InformationServices (was: Re: CARD Discussion Query Discussion)
> -----Original Message-----
> From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of
> Peretz Feder
> Sent: Thursday, October 20, 2005 12:21 PM
> To: Subir Das
> Cc: 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/20/2005 1:16 PM, Subir Das wrote:
> > Peretz,
> > I agree with your view. We do not expect that such information will
> change
> > with real time and during handover. Also as you have mentioned, we
are
> > enabling
> > handover decision process with the IS. The major part of this
handover
> > process
> > such as policy, network selection , etc, are out of scope.
>
> Subir: Yes out of scope, but can still be delivered by the service
> provider as an IS element.
> The 802.21 spec will enable such mechanism through IS info
> exchange.
>
[Vivek G Gupta]
Really?
Information Service is mostly about a query response type mechanism.
Not sure if policies fit that model, that's more of a push model from
server.
Also how do you define policy as an info element?
We can always leave blobs of data as info elements (vendor specific) and
they can be downloaded as and when required.
But not sure if such a thing really helps in handovers.
Are there no other existing mechanisms to download such things? Not just
policies, but code updates and any other plugins, device configuration,
etc. type of information?
BR,
-Vivek