English subtitles

← Name concept cs348 unit7

Get Embed Code
1 Language

Showing Revision 1 created 04/13/2013 by Cogi-Admin.

  1. In a UVC we have one or more agent lists, and we can control using constraints
  2. how many agents we want. However, this is a homogenous list, so each agent is
  3. of the same type, which makes it very hard or impossible to configure
  4. individual properties of the agents or of one of the sub-components inside the
  5. agent. Let's have a look at some examples. In this example, I want to configure
  6. or control the delay in the packet receiver unit, so if we had a list of
  7. agents, like this, we could use a key for each constrain, to individually
  8. control the response delay range for each agent. So, in this instance, the
  9. issue can be solved. Here is another example. So, here is a packet sequence
  10. definition, the main packet sequence. Now, if you had more than one active
  11. Ingress agent, then this sequence would apply to all of them. So here, we
  12. cannot control individually what kind of traffic is generated. The solution is
  13. to add a name field to the agent which is of an enumerated type. We would also
  14. add the name fields to all these sub-components. And push the value down from
  15. the agent to these name fields down here. This now enables us to do
  16. subtype-specific extensions and modifications. For example, if we had a
  17. specific agent which was called OUTIF1, then we could extend the OUTIF1
  18. receiver to set the response delay. We can use the same mechanism also for
  19. sequences. So if we had a sequencer which is of this name, and the sequence
  20. would also have the name, we could say, well the INIF1 sequence should have
  21. this behavior. So this name concept is very powerful, since it enables us to
  22. individually control and configure the agent and the sub components. And this
  23. kind of concept is used all over the UVCs.