IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx Title: Suggestion about link parameters report Date Submitted: Jan 10, 2007 Presented at IEEE session #18 in London, UK Authors or Source(s): Junxiang Guo, Yan Peng Abstract: This contribution proposes suggestion about delay trigger of link parameters report event.

IEEE presentation release statements This document has been prepared to assist the IEEE Working Group. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

Problem Currently when a QoS parameter value has crossed specified threshold level the link layer will immediately send a Link_parameters_report.indication to the MIH layer. This will cause problems, as occasionally a QoS parameter value maybe crosses threhold for a very tiny period but restores to normal level immediately, then the link layer will send a Link_parameters_report.indication event and cause the higher layer to take an action. In this case QoS value crossing threshold is only an occasional accident but it causes an unnecessary higher layer action, sometimes leads to frequent handover, in fact link layer need not report this event at all.

Problem The below example figure illustrates the current problem: a kind of QoS parameter value crossed ExecuteActionThreshold and then restored to below this threshold level in a tiny period of 10 ms, in fact this is an occasional accident which occurs now and again, indeed it should not cause link parameters report.

Solution How to avoid the aforementioned problem? We can add a time to delay the trigger of the link parameters report event. The below example figure illustrates this point. When add this trigger time, as the crossing event lasts a time short than the trigger time, the link layer will not report an unnecessary link parameters report event.

Suggestion Semantics of service primitive The primitive parameters are as follows: Link_Configure_Thresholds.request ( LinkParameterList ) Name TypeValid RangeDescription LinkParameterListListN/AA list of following set of parameters: LinkParameterType, InitiateActionThreshold, RollbackActionThreshold, ExecuteActionThreshold TriggerTime LinkParameterTypeA pair of {LinkType:Param­Type}. Examples: {Generic:Link Speed}, {Generic:Link Bit Error Rate}, {Generic:Link Frame Loss Rate before retransmission}, {Generic:Link Signal Strength}, {Generic:Link SINR}, {GPRS:BLER}, {GPRS:RxLevNCell} N/AParameters for which thresholds may be set InitiateAction­ThresholdThreshold values are dependent on parameter for which they are being set. N/AThreshold value which may cause MIH Users to start “setup” type activ­ities in response to actual parameter values crossing this threshold. RollbackAction­ThresholdThreshold values are dependent on parameter for which they are being set. N/AThreshold value which may cause MIH Users to cancel or rollback the above setup type operation if the actual parameter values retreat to this threshold. ExecuteAction­ThresholdThreshold values are dependent on parameter for which they are being set. N/AThreshold value which may cause MIH Users to execute taking appro­priate action if the actual parameter values cross this threshold. TriggerTimeInteger (0-5000) msIf changes in link parameters have crossed specified threshold levels and last for a period of time(TriggerTime), then link layer will trigger the Link_parameters_report.indication event. TriggerTime is passed from MIH user to MIH by configuration command and then MIH pass it to link layer.

Suggestion Add a description in as below: Link_Parameters_Report.indication Function Link_Parameters_Report indicates changes in link parameters have crossed specified threshold levels and last a period of specified time. This may include link layer parameters such as Speed of the link, QoS, BER, etc. The threshold level for each such parameter may have to be configured through a separate command to link layer.

Thank you!