- You will create a simulation model for 5G, where 2 traffic classes are used: eMBB and URLLC.
- More about traffic classes can be found here
- Your simulation model should contain separate queues for eMBB traffic and for URLLC traffic
- The radio resources (the radio channels, or PRBs) are common for the 2 traffic classes
- There will be a scheduler for eMBB traffic, with a scheduling cycle = 1ms
- There will be another scheduler for URLLC traffic, with a scheduling cycle of 0.1 ms
- The amount of URLLC traffic is much smaller than the eMBB traffic
- When an URLLC packet arrives in a URLLC queue, it will be scheduled by the URLLC
scheduler even if the 1 ms scheduling cycle has already begun
- If the are free radio channels (free PRBs), the URLLC traffic can be scheduled in these
free PRBs
- If all channels are occupied by eMBB traffic, the URLLC packets will be scheduled in
occupied PRBs, OVER the used PRBs
- Which means that the eMBB blocks overwritten by URLLC blocks must be retransmitted.
- So, when a data block from an eMBB queue is scheduled to depart towards the destination,
only a copy of it is sent, and the data block is kept (maybe into another queue) until the end of
this scheduling cycle (or, which is the same, until the beginning of the next scheduling
cycle)
- If the eMBB block has been overwritten by one or more URLLC data blocks, the eMBB block
has to be retransmitted (with high priority !)
- If, however, no URLLC block has been sent over the eMBB block, then the eMBB block can
be dropped.
A good description of the problem is given in the introduction of
this paper . Username: mcs ; passwd: mcs05