This week sees us wrap up Traffic Management on all timescales, and thence on to Systems tool box of design rules, plus a couple of worked examples of specialised network protocol stacks, (see also data centres, discussed a couple of lectures back).
The last couple of problems to re-enforce ideas, that you could look at by end of term next week are
1/ look at a day in the life of a video session - think about all the stages and different protocols and uses that might be involved in getting a session setup, any guarantees of performance, and the flow of packets (and what happens if routing changed during a session, or one end or the other or even both are mobile users). what about multicast? what about multipath? and load balancing?
2/ design a peer-to-peer specialised file sharing network for users for in-flight entertainment. instead of a server and a bunch of thin clients in the seat backs in front of passengers, everyone brings their own device and content, and everyone can browse and retrieve or play content from anyone else's device(s).
If you'r interested in entrepreneurship, a business case would be that the airline gets to data mine/run analytics on passengers content preferences and can re-link it to their source/destination of travel and seat price paid, and sell that data to content creators in lieu of payment for copyrighted content.
But what is the network topology? like a data center maybe (c.f. Clos switches)? or other? wired v. wireless? probably assume wire as people will want power at least.
Not in this course, but obviously security of such a system might be a consideration:-)
No comments:
Post a Comment