<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Time-utility_function</id>
	<title>Time-utility function - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://debianws.lexgopc.com/wiki143/index.php?action=history&amp;feed=atom&amp;title=Time-utility_function"/>
	<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Time-utility_function&amp;action=history"/>
	<updated>2026-05-04T16:30:29Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.1</generator>
	<entry>
		<id>http://debianws.lexgopc.com/wiki143/index.php?title=Time-utility_function&amp;diff=6255119&amp;oldid=prev</id>
		<title>imported&gt;BD2412: Clean up spacing around commas and other punctuation fixes, replaced: ,A → , A, ,c → , c</title>
		<link rel="alternate" type="text/html" href="http://debianws.lexgopc.com/wiki143/index.php?title=Time-utility_function&amp;diff=6255119&amp;oldid=prev"/>
		<updated>2025-03-19T02:28:12Z</updated>

		<summary type="html">&lt;p&gt;Clean up spacing around commas and other punctuation fixes, replaced: ,A → , A, ,c → , c&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;A &amp;#039;&amp;#039;&amp;#039;Time/Utility Function&amp;#039;&amp;#039;&amp;#039; (&amp;#039;&amp;#039;TUF&amp;#039;&amp;#039;), née &amp;#039;&amp;#039;Time/Value Function&amp;#039;&amp;#039;, specifies the application-specific &amp;#039;&amp;#039;utility&amp;#039;&amp;#039; that an &amp;#039;&amp;#039;action&amp;#039;&amp;#039; (e.g., computational task, mechanical movement) yields depending on its completion time.&amp;lt;ref name=&amp;quot;Jensen+ 85&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Jensen 93&amp;quot; /&amp;gt; TUFs and their utility interpretations (semantics), scales, and values are derived from application domain-specific subject matter knowledge. An example (but not the only) interpretation of utility is an action&amp;#039;s relative &amp;#039;&amp;#039;importance,&amp;#039;&amp;#039; which otherwise is independent of its &amp;#039;&amp;#039;timeliness&amp;#039;&amp;#039;. The traditional deadline represented as a TUF is a special case—a downward step of utility from 1 to 0 at the deadline time—e.g., timeliness without importance. A TUF is more general—it has a &amp;#039;&amp;#039;critical time,&amp;#039;&amp;#039; with application-specific shapes and utility values on each side, after which it does not increase. The various researcher and practitioner definitions of &amp;#039;&amp;#039;firm&amp;#039;&amp;#039; and &amp;#039;&amp;#039;soft&amp;#039;&amp;#039; real-time can also be represented as special cases of the TUF model. [[File:TUFs1 color 150% trimmed.png|thumb|Depiction of Example TUFs]]&lt;br /&gt;
&lt;br /&gt;
The optimality criterion for [[scheduling]] multiple TUF-constrained actions has historically in the literature been only maximal &amp;#039;&amp;#039;utility accrual&amp;#039;&amp;#039; (&amp;#039;&amp;#039;UA&amp;#039;&amp;#039;)—e.g., a (perhaps expected) weighted sum of the individual actions&amp;#039; completion utilities. This thus takes into account timeliness with respect to critical times. Additional criteria (e.g., energy, predictability), constraints (e.g., dependencies), system models, scheduling algorithms, and assurances have been added as the TUF/UA paradigm and its use cases have evolved. More expressively, TUF/UA allows accrued utility, timeliness, predictability, and other scheduling criteria and constraints to be traded off against one another for the schedule to yield situational &amp;#039;&amp;#039;application QoS&amp;#039;&amp;#039;{{efn|The term &amp;#039;&amp;#039;Quality of Service (QoS)&amp;#039;&amp;#039; initially arose in the context of communication networks but subsequently has commonly been applied at the application level.}}—as opposed to only timeliness per se. Instances of the TUF/UA paradigm have been employed in a wide variety of application domains, most frequently in military systems.&lt;br /&gt;
&lt;br /&gt;
==Time/Utility Functions==&lt;br /&gt;
&lt;br /&gt;
The TUF/UA paradigm was originally created to address certain action timeliness, predictability of timeliness, and &amp;#039;&amp;#039;application QoS&amp;#039;&amp;#039;-based scheduling needs of various military applications for which traditional real-time concepts and practices are not sufficiently expressive (e.g., for dynamically timeliness-critical systems not having deadlines) and load resilience (e.g., for systems subject to routine action overloads). An important common example class of such applications is missile defense (notionally&amp;lt;ref name=&amp;quot;Jensen 77&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Gouda+ 77&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Maynard+ 88 &amp;amp; 08&amp;quot; /&amp;gt;).&lt;br /&gt;
&lt;br /&gt;
Subsequently, numerous variations on the original TUF model, the TUF/UA paradigm&amp;#039;s system model, and thus scheduling techniques and algorithms, have been studied in the academic literature—e.g.,&amp;lt;ref name=&amp;quot;Ravindran+ 05&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Aldami+ 99&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Burns+ 00&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Prasad+ 03&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Chen+ 96&amp;quot; /&amp;gt;—and applied in civilian contexts.&lt;br /&gt;
&lt;br /&gt;
{{anchor|examples}}&lt;br /&gt;
Some examples of the latter include: cyber-physical systems,&amp;lt;ref name=&amp;quot;Tidwell+ 10&amp;quot; /&amp;gt; AI,&amp;lt;ref name=&amp;quot;Ronén+ 99&amp;quot; /&amp;gt; multi-robot systems,&amp;lt;ref name=&amp;quot;Barcís 20&amp;quot; /&amp;gt; drone scheduling,&amp;lt;ref name=&amp;quot;Shireen Seakhoa-King+ 19&amp;quot; /&amp;gt; autonomous robots,&amp;lt;ref name=&amp;quot;Baums 12&amp;quot; /&amp;gt; intelligent vehicle-to-cloud data transfers,&amp;lt;ref name=&amp;quot;Ibarz+ 20&amp;quot; /&amp;gt; industrial process control,&amp;lt;ref name=&amp;quot;Habets 19&amp;quot; /&amp;gt; transaction systems,&amp;lt;ref name=&amp;quot;Haritsa+ 93&amp;quot;/&amp;gt; high performance computing,&amp;lt;ref name=&amp;quot;Briceño+ 11&amp;quot; /&amp;gt; cloud systems,&amp;lt;ref name=&amp;quot;Tunc+ 16&amp;quot; /&amp;gt; heterogeneous clusters,&amp;lt;ref name=&amp;quot;Ravi+ 12&amp;quot; /&amp;gt; service-oriented computing,&amp;lt;ref name=&amp;quot;Young+ 06&amp;quot; /&amp;gt; networking,&amp;lt;ref name=&amp;quot;Wang+ 04&amp;quot; /&amp;gt; and memory management for real&amp;lt;ref name=&amp;quot;Cho+ 09&amp;quot; /&amp;gt; and virtual&amp;lt;ref name=&amp;quot;Feizabadi+ 07&amp;quot; /&amp;gt; machines. A steel mill example is briefly described in the Introduction of Clark&amp;#039;s Ph.D. thesis.&amp;lt;ref name=&amp;quot;Clark 90&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TUFs and their utility interpretations (semantics), scales, and values are derived from domain-specific subject matter knowledge.&amp;lt;ref name=&amp;quot;Clark+ 99&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Maynard+ 88 &amp;amp; 08&amp;quot; /&amp;gt; A historically frequent interpretation of utility is actions&amp;#039; relative &amp;#039;&amp;#039;importance.&amp;#039;&amp;#039;{{efn|&amp;#039;&amp;#039;Scheduling&amp;#039;&amp;#039; based on importance is not the same as greedy &amp;#039;&amp;#039;dispatching&amp;#039;&amp;#039; based on importance.}} A framework for á priori assigning static utility values subject to strong constraints on system models has been devised,&amp;lt;ref name=&amp;quot;Burns+ 00&amp;quot; /&amp;gt; but subsequent (like prior) TUF/UA research and development have preferred to depend on exploiting application-specificity rather than attempting to create more general frameworks. However, such frameworks and tools remain an important research topic.&lt;br /&gt;
&lt;br /&gt;
By traditional convention, a TUF is a [[concave function]], including linear ones. See the depiction of some example TUFs.&lt;br /&gt;
&lt;br /&gt;
TUF/UA papers in the research literature, with few exceptions, e.g.,&amp;lt;ref name=&amp;quot;Locke 86&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Ravindran+ 05&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Li 04&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Li+ 06&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Burns+ 00&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Chen+ 96&amp;quot; /&amp;gt; are for only either linear or piecewise linear&amp;lt;ref name=&amp;quot;Guo+ 16&amp;quot;/&amp;gt; (including conventional deadline-based) TUFs because they are easier to specify and schedule. In many cases, the TUFs are only [https://en.wiktionary.org/wiki/monotonic_decreasing#:~:text=English-,Adjective,contrast%20this%20with%20strictly%20decreasing monotonically decreasing].&lt;br /&gt;
&lt;br /&gt;
A [[constant function]] represents an action&amp;#039;s utility that is not related to the action&amp;#039;s completion time—for example, the action&amp;#039;s constant relative importance. This allows both time-dependent and time-independent actions to be scheduled coherently.&lt;br /&gt;
&lt;br /&gt;
A TUF has a global &amp;#039;&amp;#039;critical time&amp;#039;&amp;#039;, after which its utility does not increase. If a TUF never decreases, its global critical time is the first time when its maximum utility is reached. A constant TUF has an arbitrary critical time for the purpose of scheduling—such as the action&amp;#039;s release time, or the TUF&amp;#039;s termination time. The global critical time may be followed by local critical times&amp;lt;ref name=&amp;quot;Jensen 93&amp;quot; /&amp;gt;—for example, consider a TUF having a sequence of downward steps, perhaps to approximate a smooth downward curve.{{efn|This is more general than Locke&amp;#039;s introduction of the term &amp;#039;&amp;#039;critical time&amp;#039;&amp;#039; in Locke 86.}}&lt;br /&gt;
&lt;br /&gt;
TUF utility values are usually either integers or rational numbers.&lt;br /&gt;
&lt;br /&gt;
TUF utility may include negative values. (A TUF that has negative values in its range is not necessarily dropped from scheduling consideration or aborted during its operation—that decision depends on the scheduling algorithm.)&lt;br /&gt;
&lt;br /&gt;
A conventional deadline time (&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;d&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;) represented as a TUF is a special case—a downward step TUF{{efn|There is a discontinuity in either the function or its first or second derivative.}} having a unit penalty (i.e., having utility values &amp;#039;&amp;#039;1&amp;#039;&amp;#039; before and &amp;#039;&amp;#039;0&amp;#039;&amp;#039; after its critical time).&lt;br /&gt;
&lt;br /&gt;
More generally, a TUF allows downward (and upward) step functions to have any pre- and post-critical time utilities.&lt;br /&gt;
&lt;br /&gt;
[[Tardiness]]&amp;lt;ref name=&amp;quot;Erikson 14&amp;quot; /&amp;gt; represented as a TUF is a special case whose non-zero utility is the &amp;#039;&amp;#039;linear&amp;#039;&amp;#039; function &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;C&amp;#039;&amp;#039;&amp;#039; - &amp;#039;&amp;#039;&amp;#039;d&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;, where &amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039;C&amp;#039;&amp;#039;&amp;#039;&amp;#039;&amp;#039; is the action&amp;#039;s completion time—either current, expected, or believed.{{efn|For example, mathematical evidence theories such as [[Dempster-Shafer Theory]], [[imprecise probability]] theories, etc. may be used for certain system models having epistemic uncertainties.}} More generally, a TUF allows non-zero earliness and tardiness to be &amp;#039;&amp;#039;non-linear&amp;#039;&amp;#039;—e.g., increasing tardiness may result in non-linearly decreasing utility, such as when detecting a threat.&lt;br /&gt;
&lt;br /&gt;
Thus, TUFs provide a rich generalization of traditional action completion time constraints in [[real-time computing]].&lt;br /&gt;
&lt;br /&gt;
Alternatively, the TUF/UA paradigm can be employed to use timeliness with respect to the global critical time as a means to a utility accrual end—i.e., application-level Quality of Service (QoS)—instead of timeliness per se being an end in itself {{see below|[[#Utility Accrual Scheduling|below]]}}.&lt;br /&gt;
&lt;br /&gt;
A TUF (its shape and values) may be dynamically adapted by an application or its operational environment,&amp;lt;ref name=&amp;quot;Jensen 93&amp;quot; /&amp;gt; independently for any actions currently either waiting or operating.{{efn|&amp;#039;&amp;#039;Operating&amp;#039;&amp;#039; is used as the general case to include non-computational (e.g., mechatronic) actions as well as computational tasks that execute.}}&lt;br /&gt;
&lt;br /&gt;
These adaptations ordinarily occur at discrete events—e.g., at an application mode change such as for ballistic missile flight phases.&amp;lt;ref name=&amp;quot;Maynard+ 88 &amp;amp; 08&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Alternatively, these adaptations may occur continuously, such as for actions whose operational durations and TUFs are application-specific functions of when those actions are either released or begin operation. The operation durations may increase or decrease or both, and may be non-monotonic. This continuous case is called &amp;#039;&amp;#039;time-dependent scheduling&amp;#039;&amp;#039;.&amp;lt;ref name=&amp;quot;Gawiejnowicz 20a&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Glazebrook 92&amp;quot; /&amp;gt; Time-dependent scheduling was introduced for (but is not limited to) certain real-time military applications, such as radar tracking systems.&amp;lt;ref name=&amp;quot;Balli+ 07&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Ho+ 93&amp;quot; /&amp;gt;{{efn|Time-dependent scheduling (i.e., some actions&amp;#039; operation durations are functions of their starting times) is distinct from, and not limited to, real-time scheduling in the sense of actions having deadlines (or critical times).}}&lt;br /&gt;
&lt;br /&gt;
==Utility Accrual Scheduling==&lt;br /&gt;
&lt;br /&gt;
Multiple actions in a system may contend for access to sequentially exclusively{{efn|&amp;#039;&amp;#039;Sequentially exclusive&amp;#039;&amp;#039; is a special case of shared access, used here for simplicity without loss of generality.}} shared resources—physical ones such as processors, networks, exogenous application devices (sensors, actuators, etc.)—and logical ones such as synchronizers, data.&lt;br /&gt;
&lt;br /&gt;
The TUF/UA paradigm resolves each instance of this contention using an application-specific algorithmic technique that creates (or updates) a &amp;#039;&amp;#039;schedule&amp;#039;&amp;#039; at &amp;#039;&amp;#039;scheduling events&amp;#039;&amp;#039;—e.g., times (such as action arrival or completion) or states. The instance&amp;#039;s contending actions are dispatched for resource access sequentially in order from the front of the schedule. Thus, action UA sequencing is not greedy.{{efn|Some UA schedulers may remove an overload in a greedy manner—cf. §7.5.1 in Locke 86.}}&lt;br /&gt;
&lt;br /&gt;
The algorithmic technique creates a schedule based on one or more application-specific &amp;#039;&amp;#039;objectives&amp;#039;&amp;#039; (i.e., optimality criteria).&lt;br /&gt;
&lt;br /&gt;
The primary objective for scheduling actions having TUFs is maximal &amp;#039;&amp;#039;utility accrual&amp;#039;&amp;#039; (&amp;#039;&amp;#039;UA&amp;#039;&amp;#039;). The accrued utility is an application-specific polynomial sum of the schedule&amp;#039;s completed actions&amp;#039; utilities. When actions have one or more stochastic parameters (e.g., operation duration), the accrued utility is also stochastic (i.e., an expected polynomial sum).&lt;br /&gt;
&lt;br /&gt;
Utility and accrued utility are generic, their interpretations (semantics) and scales are application-specific.&amp;lt;ref name=&amp;quot;Clark+ 99&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
An action&amp;#039;s operation duration may be fixed and known at system configuration time. More generally, it may be either fixed or stochastic but not known (either with certainty or in expectation) until it either arrives or is released.&lt;br /&gt;
&lt;br /&gt;
An operation duration may be an application-specific function of the action&amp;#039;s operation starting time—it may increase or decrease or both, and may be non-monotonic. This case is called &amp;#039;&amp;#039;time-dependent scheduling&amp;#039;&amp;#039;.&amp;lt;ref name=&amp;quot;Gawiejnowicz 20a&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Glazebrook 92&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Balli+ 07&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;Ho+ 93&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
{{notelist|group=lower-alpha}}&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
{{reflist|refs=&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Jensen 77&amp;quot;&amp;gt;E. Douglas Jensen. Chapter 3 &amp;#039;&amp;#039;Radar Scheduling,&amp;#039;&amp;#039; Section 1 &amp;#039;&amp;#039;The Scheduling Problem&amp;#039;&amp;#039; in Gouda+ 77 (unclassified version).&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Gouda+ 77&amp;quot;&amp;gt;Mohamed G. Gouda, Yi-Wu Han, E. Douglas Jensen, Wesley D. Johnson, Richard Y. Kain (Editor). &amp;#039;&amp;#039;Distributed Data Processing Technology, Vol. IV, Applications of DDP Technology to BMD: Architectures and Algorithms,&amp;#039;&amp;#039; unclassified version, Defense Technical Information Center a047477, Honeywell Systems and Research Center, Minneapolis, MN, 1977.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Jensen+ 85&amp;quot;&amp;gt;E. Douglas Jensen, C. Douglas Locke, and Hideyuki Tokuda. &amp;#039;&amp;#039;A Time-Value Driven Scheduling Model for Real-Time Operating Systems,&amp;#039;&amp;#039; Proc. Symposium on Real-Time Systems, IEEE, 1985.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Jensen 93&amp;quot;&amp;gt;E. Douglas Jensen. &amp;#039;&amp;#039;A Timeliness Model for Asynchronous Decentralized Computer Systems,&amp;#039;&amp;#039; Proc. International Symposium on Autonomous Decentralized Systems, IEEE, 1993&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Tidwell+ 10&amp;quot;&amp;gt;Terry Tidwell, Robert Glaubius, Christopher D. Gill and William D. Smart. &amp;#039;&amp;#039;Optimizing Expected Time Utility in Cyber-Physical Systems Schedulers,&amp;#039;&amp;#039; Proc. IEEE Real-Time Systems Symposium, 2010.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Ronén+ 99&amp;quot;&amp;gt;Yagil Ronén, Daniel Mossé, and Martha E. Pollack. &amp;#039;&amp;#039;Value-Density Algorithms for the Deliberation-Scheduling Problem,&amp;#039;&amp;#039; ACM SIGART Bulletin, Volume 7 Issue 2, 1996.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Barcís 20&amp;quot;&amp;gt;Michał Barcís, Agata Barcís, and Hermann Hellwagner. &amp;#039;&amp;#039;An Evaluation Model for Information Distribution in Multi-Robot Systems,&amp;#039;&amp;#039; Sensors, January 2020.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Shireen Seakhoa-King+ 19&amp;quot;&amp;gt;Shireen Seakhoa-King, Paul Balaji, Nicolas Trama Alvarez, and William J. Knottenbelt. &amp;#039;&amp;#039;Revenue-Driven Scheduling in Drone Delivery Networks with Time-Sensitive Service Level Agreements,&amp;#039;&amp;#039; Proc. 12th EAI International Conference on Performance Evaluation Methodologies and Tools, ACM, 2019.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Ibarz+ 20&amp;quot;&amp;gt;Jean Ibarz, Michaël Lauer, Matthieu Roy, Jean-Charles Fabre, Olivier Flébus. &amp;#039;&amp;#039;Optimizing Vehicle-to-Cloud Data Transfers using Soft Real-Time Scheduling Concepts&amp;#039;&amp;#039;, Proc. 28th International Conference on Real-Time Networks and Systems, ACM, 2020.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Baums 12&amp;quot;&amp;gt;Aldis Baums. &amp;#039;&amp;#039;Automatic Control and Computer Sciences,&amp;#039;&amp;#039; Vol. 46, No. 6, Allerton Press, 2012.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Habets 19&amp;quot;&amp;gt;Rutger Habets. &amp;#039;&amp;#039;Improving the line performance of packaging line 41 at Heineken Zoeterwoude,&amp;#039;&amp;#039; Bachelor of Science project thesis, Industrial Engineering and Management, University of Twente, 2019.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Haritsa+ 93&amp;quot;&amp;gt;Jayant R. Haritsa, Jayant R., Michael J. Carey, and Miron Livney. &amp;#039;&amp;#039;Value-Based Scheduling in Real-Time Databases,&amp;#039;&amp;#039; VLDB Journal, 2 (2) 1993.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Briceño+ 11&amp;quot;&amp;gt;Luis Diego Briceño, Bhavesh Khemka, Howard Jay Siegel, Anthony A. Maciejewski, Christopher Groër, Gregory Koenig, Gene Okonski, and Steve Poole. &amp;#039;&amp;#039;Time Utility Functions for Modeling and Evaluating Resource Allocations in a Heterogeneous Computing System,&amp;#039;&amp;#039; Proc. IEEE International Symposium on Parallel and Distributed Processing, 2011.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Tunc+ 16&amp;quot;&amp;gt;Cihan Tunc, Nirmal Kumbhare, Ali Akoglu, Salim Hariri, Dylan Machovec, Howard Jay Siegel. &amp;#039;&amp;#039;Value of Service Based Task Scheduling for Cloud Computing Systems,&amp;#039;&amp;#039; Proc. International Conference on Cloud and Autonomic Computing, 2016.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Ravi+ 12&amp;quot;&amp;gt;Vignesh T. Ravi1, Michela Becchi2, Gagan Agrawal1, and Srimat Chakradhar. &amp;#039;&amp;#039;ValuePack: Value-Based Scheduling Framework for CPU-GPU Clusters,&amp;#039;&amp;#039; Proc. IEEE International Conference on High Performance Computing, Networking, Storage and Analysis, 2012.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Young+ 06&amp;quot;&amp;gt;Alvin AuYoung, Laura Grit, Janet Wiener, John Wilkes. &amp;#039;&amp;#039;Service contracts and aggregate utility functions,&amp;#039;&amp;#039; Proc. 15th IEEE International Symposium on High Performance Distributed Computing, 2006.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Wang+ 04&amp;quot;&amp;gt;Jinggang Wang and Binoy Ravindran. &amp;#039;&amp;#039;Time-Utility Function-Driven Switched Ethernet: Packet Scheduling Algorithm, Implementation, and Feasibility Analysis,&amp;#039;&amp;#039; IEEE Transactions on Parallel and Distributed Systems, vol. 15, no. 2, February 2004.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Cho+ 09&amp;quot;&amp;gt;Hyeonjoong Cho, Binoy Ravindran, Chewoo Na. &amp;#039;&amp;#039;Garbage Collector Scheduling in Dynamic, Multiprocessor Real-Time Systems,&amp;#039;&amp;#039; IEEE Transactions on Parallel and Distributed Systems 20(6), June 2009.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Feizabadi+ 07&amp;quot;&amp;gt;Shahrooz Feizabadi and Godmar Back. &amp;#039;&amp;#039;Garbage collection-aware utility accrual scheduling,&amp;#039;&amp;#039; Real-Time Systems Journal, July 2007, Volume 36, Issue 1–2, 2007.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Clark+ 99&amp;quot;&amp;gt;Raymond K. Clark, E. Douglas Jensen, Arkady Kanevsky, John Maurer, Paul Wallace, Tom Wheeler, Yun Zhang, Douglas M. Wells, Tom Lawrence, and Pat Hurley. &amp;#039;&amp;#039;An Adaptive, Distributed Airborne Tracking System,&amp;#039;&amp;#039; IEEE Parallel and Distributed Real-Time Systems, volume 1586 of LNCS, Springer-Verlag, 1999.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Maynard+ 88 &amp;amp; 08&amp;quot;&amp;gt;David P. Maynard, Samuel E. Shipman, Raymond K. Clark, J. Duane Northcutt, E. Douglas Jensen, Russell B. Kegley, Betsy A. Zimmerman, Peter J. Keleher. &amp;#039;&amp;#039;An Example Real-Time Battle Management Command and Control Application for Alpha,&amp;#039;&amp;#039; Section 8.2.1, Archons Project Technical Report, 1988, and public version 2008.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Locke 86&amp;quot;&amp;gt;C. Douglas Locke. &amp;#039;&amp;#039;Best-Effort Decision Making for Real-Time Scheduling,&amp;#039;&amp;#039; Ph.D. Thesis CMU-CS-86-134, Computer Science Department, Carnegie-Mellon University, 1986.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Ravindran+ 05&amp;quot;&amp;gt;Binoy Ravindran, E. Douglas Jensen, and Peng Li. &amp;#039;&amp;#039;On Recent Advances in Time/Utility Function Real-Time Scheduling and Resource Management,&amp;#039;&amp;#039; Proc. Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2005.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Li 04&amp;quot;&amp;gt;Peng Li. &amp;#039;&amp;#039;Utility Accrual Real-Time Scheduling: Models and Algorithms,&amp;#039;&amp;#039; Ph.D. dissertation, Virginia Polytechnic Institute and State University, 2004.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Aldami+ 99&amp;quot;&amp;gt;Saud A. Aldami and Alan Burns. &amp;#039;&amp;#039;Dynamic Value-Density for Scheduling Real-Time Systems,&amp;#039;&amp;#039; Proc. 11th Euromicro Conference on Real-Time Systems, IEEE, 1999.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Chen+ 96&amp;quot;&amp;gt;Ken Chen and Paul Muhlethaler. &amp;#039;&amp;#039;A Family of Scheduling Algorithms for Real-Time Systems Using Time Value Functions.&amp;#039;&amp;#039; Real-Time Systems, vol. 10 no. 3, Kluwer, 1996.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Balli+ 07&amp;quot;&amp;gt;Umut Balli, Haisang Wu, Binoy Ravindran, Jonathan Stephen Anderson, E. Douglas Jensen. &amp;#039;&amp;#039;Utility Accrual Real-Time Scheduling under Variable Cost Functions,&amp;#039;&amp;#039; IEEE Transactions on Computers, Volume 56, Number 3, March 2007.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Clark 90&amp;quot;&amp;gt;Raymond K. Clark. &amp;#039;&amp;#039;Scheduling Dependent Real-Time Activities,&amp;#039;&amp;#039; Ph.D. Dissertation, CMU-CS-90-155, Computer Science Department, Carnegie Mellon Univ., 1990.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Li+ 06&amp;quot;&amp;gt;Peng Li, Haisang Wu, Binoy Ravindran, and E. Douglas Jensen. &amp;#039;&amp;#039;A Utility Accrual Scheduling Algorithm for Real-Time Activities with Mutual Exclusion Resource Constraints,&amp;#039;&amp;#039; IEEE Transactions on Computers, vol. 55, no. 4, April 2006.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Burns+ 00&amp;quot;&amp;gt;Alan Burns, D. Prasad, A. Bondavalli, F. Di Giandomenico, K. Ramamritham, J. Stankovic, L. Strigini. &amp;#039;&amp;#039;The meaning and role of value in scheduling flexible real-time systems,&amp;#039;&amp;#039; Journal of Systems Architecture, Elsivier, 2000.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Prasad+ 03&amp;quot;&amp;gt;Divya Prasad, Alan Burns, and Martin Atkins. &amp;#039;&amp;#039;The Valid Use of Utility in Adaptive Real-Time Systems.&amp;#039;&amp;#039; Real-Time Systems, Kluwer, 2003.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Guo+ 16&amp;quot;&amp;gt;Zhishan Guo and Sanjoy Buruah. &amp;#039;&amp;#039;A Neurodynamic Approach for Real-Time Scheduling via Maximizing Piecewise Linear Utility&amp;#039;&amp;#039;, IEEE Transactions on Neural Networks and Learning Systems, vol. 27 no. 2, February 2016.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Erikson 14&amp;quot;&amp;gt;Jeremy P. Erickson. &amp;#039;&amp;#039;Managing Tardiness Bounds and Overload in Soft Real-Time Systems&amp;#039;&amp;#039;, Ph.D. dissertation, University of North Carolina, 2014.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Gawiejnowicz 20a&amp;quot;&amp;gt;Stanislaw Gawiejnowicz. &amp;#039;&amp;#039;A review of four decades of time-dependent scheduling: main results, new topics, and open problems,&amp;#039;&amp;#039; Journal of Scheduling 23, 3–47, Springer, 2020.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Glazebrook 92&amp;quot;&amp;gt;K. D. Glazebrook. &amp;#039;&amp;#039;Single-machine scheduling of stochastic jobs subject to deterioration or delay,&amp;#039;&amp;#039; Naval Research Logistics 39, no. 5, Wiley, 1992.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref name=&amp;quot;Ho+ 93&amp;quot;&amp;gt;Kevin I-J. Ho, Joseph Y-T. Leung and W-D. Wei. &amp;#039;&amp;#039;Complexity of scheduling tasks with time-dependent execution times,&amp;#039;&amp;#039; Information Processing Letters 48 (1993), no. 6,  Elsevier, 20 December 1993.&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&amp;lt;ref name=&amp;quot;Theys+ 01&amp;quot;&amp;gt;Michael D. Theys, Howard Jay Siegel, and Edwin K. P. Chong. &amp;#039;&amp;#039;Heuristics for Scheduling Data Requests Using Collective Communications in a Distributed Communication Network,&amp;#039;&amp;#039; Journal of Parallel and Distributed Computing 61, 1337- 1366, 2001.&amp;lt;/ref&amp;gt;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
==External links==&lt;br /&gt;
* [https://www.real-time.org Real-Time for the Real World.]&lt;br /&gt;
* [https://www.ssrg.ece.vt.edu/allpapers.php 2006-2009, Systems Software Research Group, Binoy Ravindran, ECE, Virginia Tech.]&lt;br /&gt;
* [https://www.stern.nyu.edu/om/faculty/pinedo/schedtheory/book5/index.html Michael L. Pindo, &amp;#039;&amp;#039;Scheduling: Theory, Algorithms, and Systems,&amp;#039;&amp;#039; 5th ed., 2015.]&lt;br /&gt;
* [https://www.springer.com/us/book/9783662593615?gclid=Cj0KCQjwsuP5BRCoARIsAPtX_wHOG2nAkt8eTSFJbhNa4VXlQBt_xhirlmE-ECUV5cnq8nPqgH6gpJUaAuGaEALw_wcB Stanislaw Gawiejnowicz, &amp;#039;&amp;#039;Models and Algorithms of Time-Dependent Scheduling&amp;#039;&amp;#039;], 2nd ed., eBook {{ISBN|978-3-662-59362-2}}, Springer, 2020.&lt;br /&gt;
* [https://www.academia.edu/15210217/Fifty_years_of_scheduling_a_survey_of_milestones?auto=download&amp;amp;email_work_card=download-paper Chris N. Potts and Vitaly A. Strusevich, &amp;#039;&amp;#039;Fifty Years of Scheduling: A Survey of Milestones&amp;#039;&amp;#039; (2009)]&lt;br /&gt;
* [https://www.springer.com/journal/10951 Journal of scheduling.]&lt;br /&gt;
* [http://www.schedulingconference.org/ Multidisciplinary International Conference on Scheduling.]&lt;br /&gt;
* [https://www.researchgate.net/project/The-Third-International-Workshop-on-Dynamic-Scheduling-Problems-IWDSP-2020 International Workshop on Dynamic Scheduling Problems.]&lt;br /&gt;
&lt;br /&gt;
{{DEFAULTSORT:Time-Utility Function}}&lt;br /&gt;
[[Category:Real-time computing]]&lt;br /&gt;
[[Category:Optimal scheduling]]&lt;br /&gt;
[[Category:Quality of service]]&lt;br /&gt;
[[Category:Software performance management]]&lt;/div&gt;</summary>
		<author><name>imported&gt;BD2412</name></author>
	</entry>
</feed>