![]() |
Notice! The role of this model answer is instructional only. The answers might not cover everything in detail that the questions asks. The answers give you the content of the answer and idea what it should be. The things that are important in the grading of the homework have been emphasized. If there is a mistake in the model answer in your opinion, please let the course staff know!
Each sub-question is 2 points. If you use 24000bps per weight as the
assumed condition. You will
be decreased 1 point for the whole question if the following answers are
right according to your assumption.
The traffic matrix of this network looks like this (traffic in packets/sec):
| - | A | B | C | D | E | F |
| A | - | 8 | 6 | 3 | 4 | 1 |
| B | 8 | - | 6 | 2 | 2 | 1 |
| C | 6 | 6 | - | 9 | 8 | 5 |
| D | 3 | 2 | 9 | - | 8 | 5 |
| E | 4 | 2 | 8 | 8 | - | 7 |
| F | 1 | 1 | 5 | 5 | 7 | - |
The traffic and routing matrix is as following:
| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
| A | -- | 8 AB | 6 AC | 3 ACD | 4 AE | 1 ACDF |
| B | 8 BA | -- | 6 BC | 2 BCD | 2 BAE | 1 BCDF |
| C | 6 CA | 6 CB | -- | 9 CD | 8 CDE | 5 CDF |
| D | 3 DCA | 2 DCB | 9 DC | -- | 8 DE | 5 DF |
| E | 4 EA | 2 EAB | 8 EDC | 8 ED | -- | 7 EDF |
| F | 1 FDCA | 1 FDCB | 5 FDC | 5 FD | 7 FDE | -- |
| i | Line | Actual traffic | Capacity | T | Weight |
|---|---|---|---|---|---|
| 1 | AB | 10 | 15 | 200 | 0.094 |
| 2 | AC | 6+3+1=10 | 15 | 200 | 0.094 |
| 3 | AE | 4+2=6 | 10 | 250 | 0.056 |
| 4 | BC | 6+2+1=9 | 10 | 1000 | 0.085 |
| 5 | CD | 3+1+2+1+9+8+5=29 | 30 | 1000 | 0.274 |
| 6 | DE | 8+8+7=23 | 30 | 142.86 | 0.216 |
| 7 | DF | 1+1+5+5+7=19 | 30 | 90.91 | 0.179 |
| Total | -- | 106 | -- | -- | 1 |
| A | B | C | D | E | F | |
|---|---|---|---|---|---|---|
| A | -- | AB | AC | AED | AE | AEDF |
| B | BA | -- | BAC | BAED | BAE | BAEDF |
| C | CA | CAB | -- | CAED | CAE | CAEDF |
| D | DEA | DEAB | DEAC | -- | DE | DF |
| E | EA | EAB | EAC | ED | -- | EDF |
| F | FDEA | FDEAB | FDEAC | FD | FDE | -- |
Each question is 1 point.
UDP is a way for applications to send the raw IP datagrams without establishing a connection. It is used for unreliable transmission, in which the prompt delivery is more important than accurate delivery. In some situations, the subnet doesn't support the connection-oriented service, so we can only use UDP as the transport protocol.
The plain IP is not enough. IP is a host-to-host protocol that delivers a packet from one physical device to another. But the receiver won't know which upper application it should put the packets in. UDP is port-to-port communication. It adds both source port and destination port, checksum error control and length information to the data from the upper layer. Souce port and destination port will identify the end points of within the souce and destination machine.
The solution for two-army-problem is to add the timer in both sender and recerver. After sender sends disconect request (DR) to the receiver, it starts a timer. Then after the receiver gets the DR, it also starts a timer, then sends back the DR. When the sender receives the DR, it releases connection and sends ACK back. When receiver gets the ACK, it releases the connection. Any error occurring during the procedure will lead to the timer out. In such case, the connection will also be released.
Each question is 2 point. Error in calculation will be decreased 0.5 point. Error in concept will be given 0 point.

If you use Token generate----waiting in queuing line-----overflow
in token queuing line----transmission as order, then the answer should
be:
For Leak Bucket:
| Time interval | Arrival | Queuing | Lost |
|---|---|---|---|
| 0-1 | 5 | 0 | 0 |
| 1-2 | 7 | 0 | 0 |
| 2-3 | 3 | 0 | 0 |
| 3-4 | 10 | 0 | 0 |
| 4-5 | 16 | 6 | 0 |
| 5-6 | 7 | 3 | 0 |
| 6-7 | 20 | 13 | 0 |
| 7-8 | 18 | 15 | 6 |
| 8-9 | 25 | 15 | 15 |
| 9-10 | 12 | 15 | 2 |
| 10-11 | 7 | 12 | 0 |
| 11-12 | 3 | 5 | 0 |
| 12-13 | 1 | 0 | 0 |
For Token Bucket (Infinite):
| Time interval | Arrival | Token left | queuing | Lost |
|---|---|---|---|---|
| 0-1 | 5 | 5 | 0 | 0 |
| 1-2 | 7 | 8 | 0 | 0 |
| 2-3 | 3 | 12 | 0 | 0 |
| 3-4 | 10 | 5 | 0 | 0 |
| 4-5 | 16 | 0 | 1 | 0 |
| 5-6 | 7 | 2 | 0 | 0 |
| 6-7 | 20 | 0 | 8 | 0 |
| 7-8 | 18 | 0 | 16 | 0 |
| 8-9 | 25 | 0 | 31 | 0 |
| 9-10 | 12 | 0 | 33 | 0 |
| 10-11 | 7 | 0 | 30 | 0 |
| 11-12 | 3 | 0 | 23 | 0 |
| 12-13 | 1 | 0 | 14 | 0 |
For Token bucket(Finite):
| Time interval | Arrival | Token left | queuing | Lost |
|---|---|---|---|---|
| 0-1 | 5 | 5 | 0 | 0 |
| 1-2 | 7 | 8 | 0 | 0 |
| 2-3 | 3 | 12 | 0 | 0 |
| 3-4 | 10 | 5 | 0 | 0 |
| 4-5 | 16 | 0 | 1 | 0 |
| 5-6 | 7 | 2 | 0 | 0 |
| 6-7 | 20 | 0 | 8 | 0 |
| 7-8 | 18 | 0 | 15 | 1 |
| 8-9 | 25 | 0 | 15 | 15 |
| 9-10 | 12 | 0 | 15 | 2 |
| 10-11 | 7 | 0 | 12 | 0 |
| 11-12 | 3 | 0 | 5 | 0 |
| 12-13 | 1 | 4 | 0 | 0 |
| Methods | Percentage of lost | Mean rate | Mean queuing delay |
|---|---|---|---|
| Leak Bucket | 17.2% | 8.54 | 1.31 |
| Token Bucket(Finite) | 13.4% | 8.92 | 1.16 |
| Token Bucket(Infinite) | 0 | 9.23 | 1.82 |
If you use token generate-----token used in transmission----waiting in
token queuing line---overflow in token queuing line as the order, the
answer should
be:
For Leak Bucket:
| Time interval | Arrival | Queuing | Lost |
|---|---|---|---|
| 0-1 | 5 | 0 | 0 |
| 1-2 | 7 | 0 | 0 |
| 2-3 | 3 | 0 | 0 |
| 3-4 | 10 | 0 | 0 |
| 4-5 | 16 | 6 | 0 |
| 5-6 | 7 | 3 | 0 |
| 6-7 | 20 | 13 | 0 |
| 7-8 | 18 | 15 | 6 |
| 8-9 | 25 | 15 | 15 |
| 9-10 | 12 | 15 | 2 |
| 10-11 | 7 | 12 | 0 |
| 11-12 | 3 | 5 | 0 |
| 12-13 | 1 | 0 | 0 |
For Token Bucket (Infinite):
| Time interval | Arrival | Token left | queuing | Lost |
|---|---|---|---|---|
| 0-1 | 5 | 5 | 0 | 0 |
| 1-2 | 7 | 8 | 0 | 0 |
| 2-3 | 3 | 15 | 0 | 0 |
| 3-4 | 10 | 15 | 0 | 0 |
| 4-5 | 16 | 9 | 0 | 0 |
| 5-6 | 7 | 12 | 0 | 0 |
| 6-7 | 20 | 2 | 0 | 0 |
| 7-8 | 18 | 0 | 6 | 0 |
| 8-9 | 25 | 0 | 21 | 0 |
| 9-10 | 12 | 0 | 23 | 0 |
| 10-11 | 7 | 0 | 20 | 0 |
| 11-12 | 3 | 0 | 13 | 0 |
| 12-13 | 1 | 0 | 4 | 0 |
For Token bucket(Finite):
| Time interval | Arrival | Token left | queuing | Lost |
|---|---|---|---|---|
| 0-1 | 5 | 5 | 0 | 0 |
| 1-2 | 7 | 8 | 0 | 0 |
| 2-3 | 3 | 15 | 0 | 0 |
| 3-4 | 10 | 15 | 0 | 0 |
| 4-5 | 16 | 9 | 0 | 0 |
| 5-6 | 7 | 12 | 0 | 0 |
| 6-7 | 20 | 2 | 0 | 0 |
| 7-8 | 18 | 0 | 6 | 0 |
| 8-9 | 25 | 0 | 15 | 6 |
| 9-10 | 12 | 0 | 15 | 2 |
| 10-11 | 7 | 0 | 12 | 0 |
| 11-12 | 3 | 0 | 5 | 0 |
| 12-13 | 1 | 0 | 0 | 0 |
| Methods | Percentage of lost | Mean rate | Mean queuing delay |
|---|---|---|---|
| Leak Bucket | 17.2% | 8.54 | 1.31 |
| Token Bucket(Finite) | 6% | 9.7 | 1.3 |
| Token Bucket(Infinite) | 0 | 10 | 1.74 |
Mean transmission rate = Total packet transmitted/total time
Mean delay = [Total of (Each packet * its waiting time)]/total packets
have exited in the queuing line.
We accept all these two methods.