ETSI's Bug Tracker - Ext Pack: Perf & Real Time Testing (ES 202 782)
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0006310 | Ext Pack: Perf & Real Time Testing (ES 202 782) | New Feature | public | 11-09-2012 16:27 | 26-12-2013 12:24

Reporter | Georg Janker |
Assigned To | Jens Grabowski |
Priority | normal | Severity | major | Reproducibility | N/A
Status | closed | Resolution | fixed |
Platform |  | OS |  | OS Version |
Product Version |  |
Target Version | v1.2.1 (published 2014-06) | Fixed in Version |  |
Clause Reference(s) | N/A
Source (company - Author) | RUETZ SYSTEM SOLUTIONS GmbH - Georg Janker
TS version |

Summary | 0006310: Change Request for Extension Package Performance and Realtime Testing
Description | For realtime ports we propose to augment the sending communication operations with a timestamp assignment clause similar to the TimestampSpec for receiving communication operations.
Steps To Reproduce |

Additional Information

Time-measurements for realtime testing are always time-critical and thus
should be as precise as possible. Only the test-adapter can know when a
message actually has been sent to the SUT (if it wasn't told to send at
a specified point in time).
Measuring on the level of the TE leaves an unspecified gap between
measuring time and actual sending time (messages need to be encoded and
might be transported through several layers of adaptation, often even to
a different embedded component on a different node from the TE where the
embedded SUT resides) which distorts the measurements unnecessarily,
yielding imprecise results.
Thus, neither
send_timestamp := now;
p.send(X);
nor
p.send(X);
send_timestamp := now
does the problem justice in lots of cases.
Therefore, we propose the following syntax (and analogous versions for
all other sending operations):
p.send(<template>) [to <receiver>] -> timestamp <float_variable>
To allow the implementation of this behavior, we propose to
change the timestamp parameter of the tri-sending-functions to INOUT.
In case of unspecified timestamp for sending, a negative timestamp value
shall be given to the paramter when calling the tri-function.
In that case, after the call, the timestamp shall contain the actual
sending timestamp.
In case that a positive timestamp was given when calling the tri-function,
the value of the parameter shall be the same afterwards, if the sending
operation was successful.
This should avoid any backward compatibility issues regarding the interface
if there are any concerns by the current implementers/providers of that
interface.
Alternatively, a second version with only an out timestamp parameter instead
of the in timestamp parameter could be introduced for all sending operation
tri functions. This would probably make sense at least on the language
mapping level, i.e. to use overloading in Java/C++/C# and add a differently
named function for the C mapping.

Tags | No tags attached.
Relationships |
Attached Files | CR6310.doc (389,632) 25-11-2013 16:15 http://oldforge.etsi.org/mantis/file_download.php?file_id=2938&type=bug

Issue History
Date Modified | Username | Field | Change
11-09-2012 16:27 | Georg Janker | New Issue |
11-09-2012 16:27 | Georg Janker | Clause Reference(s) | => N/A
11-09-2012 16:27 | Georg Janker | Source (company - Author) | => RUETZ SYSTEM SOLUTIONS GmbH - Georg Janker
19-09-2012 15:24 | Gyorgy Rethy | Project | TTCN-3 Change Requests => Ext Pack: Perf & Real Time Testing (ES 202 782)
10-12-2012 13:29 | Gyorgy Rethy | Status | new => assigned
10-12-2012 13:29 | Gyorgy Rethy | Assigned To | => Jens Grabowski
10-12-2012 16:43 | Gyorgy Rethy | Target Version | => v1.2.1 (published 2014-06)
08-10-2013 16:25 | Jens Grabowski | Note Added: 0011707 |
08-10-2013 16:26 | Jens Grabowski | Assigned To | Jens Grabowski => Jacob Wieland - Spirent
25-11-2013 16:15 | Jacob Wieland - Spirent | File Added: CR6310.doc |
25-11-2013 16:19 | Jacob Wieland - Spirent | Note Added: 0011829 |
25-11-2013 16:19 | Jacob Wieland - Spirent | Assigned To | Jacob Wieland - Spirent => Jens Grabowski
25-11-2013 16:19 | Jacob Wieland - Spirent | Status | assigned => confirmed
26-12-2013 12:24 | Jens Grabowski | Status | confirmed => closed
26-12-2013 12:24 | Jens Grabowski | Resolution | open => fixed

Notes

(0011707)
Jens Grabowski
08-10-2013 16:25

Assigned to Jacob according to STF discussion today.

(0011829)
Jacob Wieland - Spirent
25-11-2013 16:19

please review proposal