RE: [802.21] Event subscription with specific threshold.
Alice/Nada/Kenichi,
Thanks much for raising these issues and we need to sort this out.
Here are some thoughts on way forward:
1] Link Action:
Is a MIH_LINK_SAP primitive and sets the local link state.
(May need to remove/clarify LINK_NO_ACTION and DATA_FORWARDING_REQUEST
options here....)
2] Link_Configure_Threshold:
Is again a MIH_LINK_SAP primitive and sets thresholds for link
parameters. When these thresholds are crossed Link_Parameter_Report
specifies which parameters have crossed these thresholds. This has got
nothing to do with other link layer indications.
These parameters are specified in Nada/Qiaobing contribution
21-07-105-01.
3] MIH_Link_Configure
Is a MIH_SAP primitive and is not very well defined.
This is currently a superset of functionality in both (Link_Action +
Link_Configure_Threshold).
Kenichi's proposal of splitting this into:
MIH_Link_Action and MIH_Link_Configure_Threshold seems like a good one.
4] Are link layer triggers (Link_Going_Down/Link_Down ) configurable..?
Individual link layer technologies may define these and wherever
applicable we leave these to specific implementations.
Hope this clarifies:
Kind Regards
-Vivek
> -----Original Message-----
> From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of
Yuu-
> Heng Alice Cheng
> Sent: Thursday, May 10, 2007 1:37 PM
> To: STDS-802-21@listserv.ieee.org
> Subject: Re: [802.21] Event subscription with specific threshold.
>
> Nada,
>
> Thank you so much for the prompt response. I think the contribution
> benefits the draft with regards to the parameters definition.
>
> Additional thoughts beyond the parameters are:
>
> - If "the MIH_Configure_Link will lead to generating a Link_Action
> and/or Link_Configure_Threshold," should MIH_Configure_Link be split
> as MIH_Link_Action and MIH_Link_Configure_Threshold ?
>
> - The MIH_Configure_Link with only the "LinkConfigureParameters" is
> actually an event subscription command. And this subscription will
lead
> to the event MIH_Link_Parameters_Report to report ONLY the parameters
> that were configured via the MIH_Configure_Link call. Is that correct?
>
> - Does MIH_Link_Going_Down or Going_Up need be a configurable
trigger?
> I guess if the service require to have customized Link_Going_Down
> can be achieved by MIH_Configure_Threshold of an RSSI signal strength
to
> received a MIH_Link_Parameters report.
>
>
>
>
> Thanks,
> Alice
>
> On Thu, 10 May 2007 12:41:11 -0400
> Nada Golmie <nada.golmie@nist.gov> wrote:
> > Alice,
> >
> > Please take a look at contribution 21-07-105. I believe it should
> > address some of your concern.
> >
> > Yuu-Heng Alice Cheng wrote:
> > > Hi All,
> > >
> > > While reading the draft and hearing some explainations, I am
confused
> > > about the relationship Link_Configure_Threshold, Link_Action,
> MIH_Configure_Link
> > > with the MIH_Event_Subscribe.
> > >
> > > Base on the current draft following is my understanding.
> > >
> > > Link_Configure_Threshold is a command to determine what condition
to
> > > trigger Link_Parameters_Report when a threshold is reached. There
is
> no
> > > periodically reports.
> > >
> > >
> > A timer interval was added in Table 32 in order to generate
> > Link_Parameter_Report.indication.
> >
> > > Link_Action is a command for setting a Link. (No QoS Params
settings)
> > >
> > >
> > That is still the case.
> > > Mih_Configure_Link is a command for
> > > - setting a link, which MIHF in turns invoke Link_Action with
the
> > > content of "Operation mode" in the parameter
> > > - and configure event threshold, which MIHF in turns invoke
> > > Link_Configure_Threshold using "QoS params list". Later MIHF will
> > > translate the Link_Parameters_Report to MIH_Link_Parameters_Report
to
> > > whomever subscribed via MIH_Event_Subscribe.
> > >
> > >
> > The MIH_Configure_Link will lead to generating a Link_Action and/or
> > Link_Configure_Threshold. It
> > has both link measurement info and link state info.
> > > Besides the MIH_Link_Parameters_Report event, all the other event
> > > triggers are deterministic. For example, when to trigger
> MIH_Link_Going_Down
> > > is determined by MIHF and not by Mih_Configure_Link.
> > >
> > >
> > The MIH_Link_Going_Down is triggered by a
Link_Going_Down.indication.
> > There are no mechanisms
> > to configure a Link_Down/Link_Going_Down events.
> >
> > Hope this helps.
> >
> > -Nada
> >
> > > There were some discussion and proposals by others in Draft 4 but
> wasn't
> > > well received and understood by the group.
> > >
> > > In the contribution of #145 for Link Configure, Kenichi propose to
> split
> > > tthe MIH_Configure_Link to be more easy to understand.
> > >
> > > I would like to ask for comments and suggestions.
> > >
> > > Thanks,
> > > Alice
> > >
> > >
> > >
> >
> > --
> > Nada Golmie, Ph.D.
> > Manager, High Speed Network Technologies Group
> > National Institute of Standards and Technology
> > 100 Bureau Dr. Stop 8920
> > Gaithersburg, MD 20899
> > Email: nada@nist.gov
> > Phone: (301) 975-4190
> > Fax: (301) 590-0932
> > Web: http://w3.antd.nist.gov
> >
> >
>
> --
> Yuu-Heng Alice Cheng <yhcheng{at}research.telcordia.com>
> Senior Research Scientist, Applied Research, Telcordia Technologies.
> One Telcordia Drive, RRC-1G310, Piscataway, NJ 08854
> Phone: +1 732-699-2185 Fax: +1 732-336-7016
> http://www.argreenhouse.com/~yhcheng