<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.nsnam.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=File%3ALte-ue-meas-racing-condition.png</id>
	<title>File:Lte-ue-meas-racing-condition.png - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://www.nsnam.org/mediawiki/index.php?action=history&amp;feed=atom&amp;title=File%3ALte-ue-meas-racing-condition.png"/>
	<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=File:Lte-ue-meas-racing-condition.png&amp;action=history"/>
	<updated>2026-05-02T15:22:31Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.8</generator>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=File:Lte-ue-meas-racing-condition.png&amp;diff=8027&amp;oldid=prev</id>
		<title>Buherman: Timeline diagram explaining the possible racing condition in LTE module's UE measurements function. The first case depicts normal scenario when racing condition does not happen, i.e., when report interval is less than 200 ms. The second case depicts th...</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=File:Lte-ue-meas-racing-condition.png&amp;diff=8027&amp;oldid=prev"/>
		<updated>2013-10-06T18:29:58Z</updated>

		<summary type="html">&lt;p&gt;Timeline diagram explaining the possible racing condition in LTE module&amp;#039;s UE measurements function. The first case depicts normal scenario when racing condition does not happen, i.e., when report interval is less than 200 ms. The second case depicts th...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Timeline diagram explaining the possible racing condition in LTE module's UE measurements function. The first case depicts normal scenario when racing condition does not happen, i.e., when report interval is less than 200 ms. The second case depicts the scenario when report interval is greater than 200 ms, which causes measurement reporting to use an old measurement. The third case is the proposed solution by adding a small delay to every measurement reporting.&lt;/div&gt;</summary>
		<author><name>Buherman</name></author>
	</entry>
</feed>