Tasks in Real Time systems

Last Updated : 31 Aug, 2023

The system is subjected to real-time, i.e. response should be guaranteed within a specified timing constraint or system should meet the specified deadline. For example flight control systems, real-time monitors, etc.

There are four types of tasks in real-time systems:

Periodic tasks
Dynamic tasks
Critical task
Non-critical task

Periodic Tasks: In periodic tasks, jobs are released at regular intervals. A periodic task is one that repeats itself after a fixed time interval. A periodic task is denoted by four tuples: T_i = < Φ_i, P_i, e_i, D_i >
Where,
- Φ_i - is the phase of the task. Phase is the release time of the first job in the task. If the phase is not mentioned then the release time of the first job is assumed to be zero.
- P_i - is the period of the task i.e. the time interval between the release times of two consecutive jobs.
- e_i - is the execution time of the task.
- D_i - is the relative deadline of the task.

For example: Consider the task T_i with period = 5 and execution time = 3
Phase is not given so, assume the release time of the first job as zero. So the job of this task is first released at t = 0 then it executes for 3s and then the next job is released at t = 5 which executes for 3s and then the next job is released at t = 10. So jobs are released at t = 5k where k = 0, 1, . . ., n

Interval real time

Hyper period of a set of periodic tasks is the least common multiple of periods of all the tasks in that set. For example, two tasks T₁ and T₂ having period 4 and 5 respectively will have a hyper period, H = lcm(p1, p2) = lcm(4, 5) = 20. The hyper period is the time after which pattern of job release times starts to repeat.

Dynamic Tasks: It is a sequential program that is invoked by the occurrence of an event. An event may be generated by the processes external to the system or by processes internal to the system. Dynamically arriving tasks can be categorized on their criticality and knowledge about their occurrence times.
1. Aperiodic Tasks: In this type of task, jobs are released at arbitrary time intervals i.e. randomly. Aperiodic tasks have soft deadlines or no deadlines.
2. Sporadic Tasks: They are similar to aperiodic tasks i.e. they repeat at random instances. The only difference is that sporadic tasks have hard deadlines. A sporadic task is denoted by three tuples: T_i =(e_i, g_i, D_i)
  Where
  e_i - the execution time of the task.
  g_i - the minimum separation between the occurrence of two consecutive instances of the task.
  D_i - the relative deadline of the task.

Critical Tasks:

Critical Tasks are those whose opportune executions are basic. In the event that cutoff times are missed, calamities happen.

For instance, life-emotionally supportive networks and the steadiness control of airplane. On the off chance that basic errands are executed at a higher recurrence, it is fundamental.

Non-critical Tasks:

Non-critical Tasks are genuine times assignments. As the name infers, they are not basic to the application. Be that as it may, they can manage time, changing information, and consequently they are futile on the off chance that not finished inside a cutoff time. The objective of booking these assignments is to expand the level of occupations effectively executed inside their cutoff times.

Jitter: Sometimes actual release time of a job is not known. Only know that r_i is in a range [ r_i-, r_i+ ]. This range is known as release time jitter. Here r_i- is how early a job can be released and r_i+ is how late a job can be released. Only the range [ e_i-, e_i+ ] of the execution time of a job is known. Here e_i- is the minimum amount of time required by a job to complete its execution and e_i+ is the maximum amount of time required by a job to complete its execution.

Precedence Constraint of Jobs: Jobs in a task are independent if they can be executed in any order. If there is a specific order in which jobs in a task have to be executed then jobs are said to have precedence constraints. For representing precedence constraints of jobs a partial order relation < is used. This is called precedence relation. A job J_i is a predecessor of job J_j if J_i < J_j i.e. J_j cannot begin its execution until J_i completes. J_i is an immediate predecessor of J_j if J_i < J_j and there is no other job J_k such that J_i < J_k < J_j. J_i and J_j are independent if neither J_i < J_j nor J_j < J_i is true.
An efficient way to represent precedence constraints is by using a directed graph G = (J, <) where J is the set of jobs. This graph is known as the precedence graph. Jobs are represented by vertices of the graph and precedence constraints are represented using directed edges. If there is a directed edge from J_i to J_j then it means that J_i is the immediate predecessor of J_j. For example: Consider a task T having 5 jobs J₁, J₂, J₃, J₄, and J₅ such that J₂ and J₅ cannot begin their execution until J₁ completes and there are no other constraints.

The precedence constraints for this example are:
J₁ < J₂ and J₁ < J₅

Precedence graph

Set representation of precedence graph:

< (1) = { }
< (2) = {1}
< (3) = { }
< (4) = { }
< (5) = {1}

Consider another example where a precedence graph is given and you have to find precedence constraints

precedence graph another example

From the above graph, we derive the following precedence constraints:

J₁ < J₂
J₂ < J₃
J₂ < J₄
J₃ < J₄

FAQ:

What are some common examples of real-time systems?
Industries like aviation, healthcare, manufacturing, and telecommunications make use of real-time systems. The employed systems incorporate flight control applications, real-time monitors in healthcare facilities, industrial control systems, and real-time communication systems.

What is the difference between aperiodic and sporadic tasks?
Tasks that are aperiodic are not released on a regular schedule, whereas sporadic tasks are released at irregular but anticipated intervals. Aperiodic tasks may have lenient or nonexistent deadlines, while sporadic tasks are required to meet strict deadlines.

What is jitter in real-time systems?
The time release or execution of a task can be affected by a fluctuation known as Jitter. This phenomenon can be triggered by multiple factors including network delays, software errors, or hardware limitations. Struggling to manage Jitter can have a tremendous effect on real-time systems, so precise timing control is crucial.

How are precedence constraints represented in real-time systems?
Precedence constraints are represented using a directed graph called a precedence graph. Each job is represented by a vertex, and the precedence constraints are represented by directed edges between vertices. If there is a directed edge from job A to job B, it means that A must complete before B can begin.

What is the hyper period of a set of periodic tasks?
The hyper period of a set of periodic tasks is the least common multiple of their periods. It is the smallest time after which the pattern of job release times for all tasks in the set repeats. The hyper period is an important parameter in real-time scheduling, as it determines the scheduling cycle for the tasks.

Tasks in Real Time systems

priyanka dahiya

Improve

Article Tags :

Software Engineering

Tasks in Real Time systems

Similar Reads