ETSI's Bug Tracker - Part 06: TTCN-3 Control Interface
View Issue Details

ID | Project | Category | View Status | Date Submitted | Last Update
0001164 | Part 06: TTCN-3 Control Interface | Technical | public | 25-04-2007 15:39 | 04-12-2007 17:16

Reporter | Mateusz Pusz |
Assigned To | Ina Schieferdecker |
Priority | normal | Severity | minor | Reproducibility | always
Status | closed | Resolution | no change required |
Platform |  | OS |  | OS Version |
Product Version | v3.1.1 (published 2005-06) |
Target Version | v3.3.1 (published 2008-04) | Fixed in Version |  |
Clause Reference(s) | 11.4.1.1, 11.4.4.1
Source (company - Author) | Mateusz Pusz, Intel

Summary | 0001164: tciReset procedure

Description

Figures 24 and 27 defines that tciStopTestComponent() is called by TCI_CH_Provided when tciResetReq() is received. It should be called only when
tciStopTestComponentReq(). If there are running components when reset is received TE should stop them locally before reset.
Figures should be modified in one of following ways:
1. Call tciStopTestComponentReq() explicitly before calling tciResetReq()
2. Do not call tciStopTestComponent() at all (it will be done locally on TEs)

Steps To Reproduce |

Additional Information

1. To perform such an operation CH does not need to monitor only active connections but also should be aware what test components are still alive. So it needs to duplicate what TE already does.
2. Description of tciStopTestComponent() says that it is run only when tciStopTestComponentReq() is received by CH.
3. tciStopTestComponentReq() is not used on any figure in specification
4. tciResetReq() is ment to "transmit the reset request to all involeved TEs" according to its descritpion and not to perform stop call to running test components.

Tags | No tags attached.
Relationships |
Attached Files |

Issue History
Date Modified | Username | Field | Change
25-04-2007 15:39 | Mateusz Pusz | New Issue |
25-04-2007 15:39 | Mateusz Pusz | Clause Reference(s) | => 11.4.1.1, 11.4.4.1
25-04-2007 15:39 | Mateusz Pusz | Source (company - Author) | => Mateusz Pusz, Intel
15-06-2007 19:09 | Stephan Schulz | Status | new => assigned
15-06-2007 19:09 | Stephan Schulz | Assigned To | => Ina Schieferdecker
18-10-2007 12:29 | Ina Schieferdecker | Target Version | => Edition 3.3.1 (not yet published)
04-12-2007 17:15 | Ina Schieferdecker | Note Added: 0004294 |
04-12-2007 17:16 | Ina Schieferdecker | Status | assigned => closed
04-12-2007 17:16 | Ina Schieferdecker | Resolution | open => no change required

Notes

(0004294)
Ina Schieferdecker
04-12-2007 17:15

tciStopTestComponentReq() is not used in a figure of the specification as no case with an explicit myComponent.stop statement is shown.
In such cases, the request is given to the CH which knows where the test component is being located, i.e. in which TE. The CH invokes then on the TE the respective tciStopTestComponent().
Figure 24 is about terminating a test case or control, which is initiated by the tciResetReq(). This implies two things: the stopping of all test components and the resetting of all TEs. As the CH however keeps track of the status of all test components during a test run, it knows where to stop test components and has to issue the corresponding tciStopTestComponent() to those TEs where test components have to be stopped. First, the test components are stopped, then the TEs are resetted.
Figure 27 is about terminating a test case after error - it is basically the same sequencing: tciResetReq() initiates the termination, then all test components are being stopped in the respective TEs (the CH knows which TEs to invoke with a tciStopTestComponent()) and finally all TEs are being resetted.
To sum up: tciStopTestComponentReq() is an invocation on the CH in order to forward the tciStopTestComponent() to the correct TE. If however CH has the control, it can issue tciStopTestComponent() directly.