1. Context-Aware Interactive Content Adaptation Iqbal Mohomed, Jim Cai, Sina Chavoshi, Eyal de Lara Department of Computer Science University of Toronto MobiSys2006

2. Need for Content Adaptation Mobile Devices have limited resources Screen real-estate Networking Battery Life User Interface Memory Processing Capability

3. Factors to Consider Content Usage Semantics

4. Factors to Consider Content Usage Semantics Context

5. Web Server Adaptation Proxy URICA (EuroSys2006)

6. Web Server Adaptation Proxy URICA (EuroSys2006)

7. Web Server Adaptation Proxy URICA (EuroSys2006)

8. Web Server Adaptation Proxy URICA (EuroSys2006) Prediction

9. Web Server Adaptation Proxy URICA (EuroSys2006) Prediction

10. Web Server Adaptation Proxy URICA (EuroSys2006) Prediction

11. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

12. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

13. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

14. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

15. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

16. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

17. Web Server Adaptation Proxy URICA (EuroSys2006) Feedback Prediction

18. Predictions based on History

21. Multiple Usages Multiple Context Challenge: Ambiguity in Feedback

22. Multiple Usages Multiple Context Challenge: Ambiguity in Feedback

23. Content

24. Group based on Context Content

25. How? A lot of context can differ across users E.g., Display size, Network Connectivity, Location, etc. Influential context can vary across content and type of adaptation Cannot group users by fixed set of context characteristics Grouping based on all possible combinations of context is infeasible Results in many groups, each with few members Significant overhead maintaining many groups Long time until convergence of predictions within groups

26. Contributions User feedback is used to identify context that influences adaptation requirements Group users into communities based on influential context Predictions for each community are made on the restricted history of its users

27. Feedback-driven Context Selection (FCS) All users are grouped together initially System tracks adaptation history for different contexts We conduct a “profiling experiment” when there is sufficient history Would users have benefited if they were grouped separately based on some context? If so, split original group based on this context

28. Users123456 Desired Adaptation494589

29. Users123456 Desired Adaptation494589

30. Users123456 Desired Adaptation494589 To Split or Not to Split …

31. Users123456 Desired Adaptation494589 To Split or Not to Split …

32. Users123456 Desired Adaptation494589 Prediction Using Mean Policy To Split or Not to Split …

33. Prediction Using Mean Policy Users123456 Desired Adaptation494589 Distance From Prediction323212 To Split or Not to Split …

34. Prediction Using Mean Policy Users123456 Desired Adaptation494589 Distance From Prediction323212 Average Distance: 2.17 To Split or Not to Split …

35. Users134 Desired Adaptation445 Users256 Desired Adaptation989 To Split or Not to Split …

36. Users134 Desired Adaptation445 Users256 Desired Adaptation989 To Split or Not to Split …

37. Users134 Desired Adaptation445 Distance From Prediction001 Users256 Desired Adaptation989 Distance From Prediction010 To Split or Not to Split …

38. Users134 Desired Adaptation445 Distance From Prediction001 Users256 Desired Adaptation989 Distance From Prediction010 Average Distance: 0.33 To Split or Not to Split …

39. Users134 Desired Adaptation445 Distance From Prediction001 Users256 Desired Adaptation989 Distance From Prediction010 Overall Average Distance: 0.33 To Split or Not to Split …

40. Overall Average Distance: 0.33 Average Distance: 2.17 VS To Split or Not to Split …

41. Overall Average Distance: 0.33 Average Distance: 2.17 VS To Split or Not to Split … It Depends!

42. Initial Situation All Users in Same Community Storage Requirements

43. Prediction Histogram Storage Requirements

45. Context Grouping Histograms

46. Context A Context B Storage Requirements

47. Context A Context B Storage Requirements Number of Histograms: 1 + 5 = 6

48. Context A Context B Storage Requirements Number of Histograms: 1 + 5 = 6

49. Storage Requirements Prediction Histogram Context Grouping Histograms Context Grouping Histograms Context Grouping Histograms

50. Storage Requirements Context Grouping Histograms Context Grouping Histograms Context Grouping Histograms

51. Context B Storage Requirements

52. Context B Storage Requirements Number of Histograms: 3 + (2 x 3) = 9 Increase of 50%

53. Splitting Costs Memory Number of Histograms # Contexts# Context Values Before Any Splits After Initial Split Increase 33 55 10

54. Splitting Costs Memory Number of Histograms # Contexts# Context Values Before Any Splits After Initial Split Increase 33102111 55 10

55. Splitting Costs Memory Number of Histograms # Contexts# Context Values Before Any Splits After Initial Split Increase 33102111 552610579 10

56. Splitting Costs Memory Number of Histograms # Contexts# Context Values Before Any Splits After Initial Split Increase 33102111 552610579 10 101910809

57. Splitting Costs Memory Number of Histograms # Contexts# Context Values Before Any Splits After Initial Split Increase 33102111 552610579 10 101910809 Splitting Can Be Expensive!

58. Splitting Economically As long as space is available, splits can occur When system runs low on space, a score metric is used to rate splits Score is a function of: Performance gain of a split Access rate of object Space Usage Splits with the highest scores are allowed to exist Low score groups are merged together

59. Prototypes We developed two prototype systems: Page Layout Adaptation Prototype Adapts display size and layout of images on web pages for limited screen real-estate Fidelity Adaptation Prototype: Adapts image quality to save bandwidth consumption

60. User Studies Goal was to capture desired adaptation of users During study, prediction component of prototypes was disabled Users adapt content to accomplish a specified task Traces used to conduct profiling experiments offline

61. Context Varied Page Layout Adaptation Screen Size: SmartPhone, PDA, GBook Fidelity Adaptation Network Bandwidth: 56Kbps, 100Mbps Screen Size: PDA, Laptop Location: 3 locations

62. Screen Size can matter … Result from Page Layout Adaptation Experiment

63. Screen Size can matter … Grouping Users by Screen Size Improves Distance By 32% Splitting Probably Worthwhile

64. Screen Size can matter … or it may not! Result from Fidelity Adaptation Experiment

65. Screen Size can matter … or it may not! Grouping Users by Screen Size Improves Distance By 6% Splitting Probably Not Worthwhile

66. Conclusions Influence of context on adaptation requirements can vary based on the content being adapted, as well as type of adaptation being performed We provide a technique that uses feedback to automatically determines influential context We show that grouping users based on context can lead to significant improvements in overall performance

67. Future Work Ultimate Goal: System adapts content based on: Context, and Usage semantics We are extending technique to also take usage semantics into account when adapting content

68. Future Work Ultimate Goal: System adapts content based on: Context, and Usage semantics We are extending technique to also take usage semantics into account when adapting content Questions?