关于TS36.321中定时器 not running和expires这两种状态的区别

longtime1987

3GPP协议TS36.321中经常会说到定时器 not running和expires这两种状态，感觉协议里面有些地方比较让人费解：

if no UL-SCH resourcesare available for a transmission in this TTI:

-     if the UE has no valid PUCCH resource for SR configured in any TTI:initiate a Random Access procedure (see subclause 5.1) and cancel all pendingSRs;

-     else if the UE has a valid PUCCH resource for SR configured forthis TTI and if this TTIis not part of a  measurement gapand if[url=]sr-ProhibitTimer is not running:[/url]

-     if SR_COUNTER < [url=]dsr-TransMax[/url]:

-     increment SR_COUNTER by 1;

[url=]-     instructthe physical layer to signal the SR on PUCCH;[/url]

-     start the sr-ProhibitTimer.

[url=]-     else:[/url]

-     notify RRC to release PUCCH/SRS;

-     clear any configured downlink assignments and uplink grants; [ml5]

-     initiate a Random Access procedure (see subclause 5.1) andcancel all pending SRs.

[url=]
[/url]

SR上报这里的[url=]sr-ProhibitTimer is not running到底包不包括[/url][url=]sr-ProhibitTimer  [/url]expires呢，R9协议里面感觉没写清楚，一种理解是将这里理解为[url=]sr-ProhibitTimer 处于stopped状态，一种理解是将这里理解为[/url]expires。

如果是第一种理解的话，那么这里只有当[url=]sr-ProhibitTimer 停止之后才会触发SR的重传，如果是第二种理解的话，那么当[/url][url=]sr-ProhibitTimer  [/url]expires之后就会触发SR重传。

是否stopped和expires应当理解为相同呢？

---