1. Multiplayer games on networks potential and tradeoffs

2. COSC 4126 network games Brief history of real-time networking approximately... 1980’s (US) military simulations 1990’s distributive / collaborative virtual environments 2000’s multiplayer games but 1980 1990 2000 MUD Amaze Doom Ultima Online Battle.net

3. COSC 4126 network games Analyzing constraints on network games*  design constraints at three levels physical: cabling and hardware - bandwidth, latency, processing logical: architectures for communication (e.g., peer-to-peer, client/server), data and control (e.g., centralized, distributed, replicated) application: interpretation (data meaning), integrity control (legal state), transferring (computation shared among nodes) *Smed, Kaukoranta & Hakonen, 2003

4. COSC 4126 network games Resource management – physical and logical influence on experience  resource requirements in distributed application: f(info sent, info received, processing rate)  IPE Information Principle Equation: Singal &Zyda, 1999 M : number of messages H : average number of destination nodes B : bandwidth required for message to one destination T : delay P : number of processor cycles to receive, process a message

5. COSC 4126 network games IPE  product is a measure of “quality of experience”  reducing a factor reduces resource requirements but also reduces experience  factors can be traded off against each other

6. COSC 4126 network games IPE example M : number of messages H : average number of destination nodes B : bandwidth required for message to one destination T : delay P : number of processor cycles to receive, process a message  packet aggregation M decreased B increased P increased T increased design question – is tradeoff valuable?

7. COSC 4126 network games Quality of experience in networked game  consistency: similarity of view to actual data in the nodes of the network – “absolute consistency” is perfect data view match among nodes  responsiveness: – delay for an update event to be applied to game data  in database applications – consistency takes precedence over responsiveness  in game applications – responsiveness is more important and consistency may be compromised

8. COSC 4126 network games Data and control architectures centralizeddistributedreplicated process relay data storenetwork

9. COSC 4126 network games Consistency, responsiveness and architecture  high consistency  processes on remote nodes tightly coupled  high responsiveness  processes loosely coupled

10. COSC 4126 network games Relay local input global output global input local output network node  2 – way relay assures consistency in combination with distributed or centralized architecture BUT responsiveness is vulnerable to network

11. COSC 4126 network games Relay  short-circuit relay assures high responsiveness but local data can become inconsistent with other nodes local input global output global input local output network node

12. COSC 4126 network games Resolving inconsistencies  games require responsiveness  inconsistencies will occur  mechanism for resolving inconsistencies must be provided

13. COSC 4126 network games Application level influence on experience  scalability – adapting to resource changes  persistence – effect of players leaving and entering  collaboration – consistency and sharing

14. COSC 4126 network games Scalability  game server issues allocation of non-player computation among nodes  parallelism & concurrent computation model  each node burdens network but increases computation power ( H up, P down)

15. COSC 4126 network games Persistence  relationship of node to application initializing state of node when player joins on-going consistency maintaining state when node leaves game abrupt disruption – reallocation of responsibilities

16. COSC 4126 network games Collaboration  teams acting together communication among team members  prioritized messages / dedicated channel ‘interest management’ based on application-based closeness or ‘collaboration distance’

17. COSC 4126 network games Reducing resource requirements  Architecture level packet compression  internal – data compression within packet suits UDP  external – data compression bsed on assumed receiver state packet aggregation  merging removes some headers but adds delay to data waiting for packetizing timeout or quorum-based aggregation tradeoffs

18. COSC 4126 network games Reducing resource requirements  Application level interest management  premise – most packets only of interest to minority of nodes  transmit only to those, not all nodes  nodes ‘express interest’ in subset of information  M down, B down, P up

19. COSC 4126 network games Interest management  area of interest – ‘aura’ application based – correlates to sensory capabilities of node system (typically character) aura = focus(perception) + nimbus(perceptibility) when focus intersects nimbus, nodes communicate

20. COSC 4126 network games Nimbus and Focus  Smed et al, 2003

21. COSC 4126 network games Interest management  area of interest – ‘aura’ ‘subscription manager’ server manages state, interest info for each node subscription manager receives messages about state and retransmits to interested nodes nodes submit changes of state and interest to the subscription manager

22. COSC 4126 network games Improving responsiveness  e.g., with less frequent packets due to aggregation  game state extrapolation techniques to continue response without input ‘dead reckoning’ based on predicting state changes and correcting when info arrives

23. COSC 4126 network games dead reckoning example  Smed et al, 2003 based on recent positions, compute velocity, maybe acceleration and extrapolate when update arrives, plot ‘smooth’ convergence