Defining Virtual Channels
In the OSRA-NET project we have to use Virtual Links over a physical nertwork:
Two different options are being evaluated to describe Virtual Links in the TASTE Deployment View:
- Add a Device per Virtual Link and configure each of them with an ASN.1 type associated to the driver.
We can manage this option with the SCM to TASTE tool. We have successfully tested it.
The main drawback is that the TASTE Ellidiss GUI is not able to manage it correctly, so the TASTE GUI should not be used to visualize the TASTE Deployment View.
- Add one driver and bus. Then, add the VL properties to the TASTE Function Connections mapped on the TASTE Bus.
This solution reflects the hardware topology better than option 1, but we have to check its feasibility.
Is it possible to add properties to a message binded to a bus?
I would like to ask you if this situation has been studied and which solution you see as feasible/elegant/in line with the TASTE filosofy. I attach a document with a detailed description of the different options and the problems found while investigating it.