1 / 35

AVC: The Access Grid Venue Customizer

AVC: The Access Grid Venue Customizer. A joint R&D project by NRC, SFU/Westgrid, CRC. Andrew Patrick, NRC Canada Brian Corrie, SFU/Westgrid. Outline. Why build a venue customizer? How we built AVC Issues and next steps Optional : How to run AVC (tutorial). Quality of Experience (QoE).

opal
Download Presentation

AVC: The Access Grid Venue Customizer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. AVC: The Access Grid Venue Customizer A joint R&D project by NRC, SFU/Westgrid, CRC Andrew Patrick, NRC Canada Brian Corrie, SFU/Westgrid

  2. Outline • Why build a venue customizer? • How we built AVC • Issues and next steps • Optional: How to run AVC (tutorial)

  3. Quality of Experience (QoE) • Quality of Experience • Measure of human experience, not technology • Making it work • Task: What is the user trying to do? • Need: What is needed to accomplish the task? • Services: What services meet the needs?

  4. Bringing QoE to Collaborative Environments • Information about the research behind AVC can be found in the following papers: • Corrie, B., Wong, H., Zimmerman, T., Marsh, S., Patrick, A.S., Singer, J., Emond, B., & Noël, S. (2003). Towards quality of experience in advanced collaborative environments. Paper presented at the Third Annual Workshop on Advanced Collaborative Environments, June 22, Seattle. (NRC 46521) • Patrick, A.S., Singer, J., Corrie, B., Noël, S., El Khatib, K., Emond, B., Zimmerman, T., & Marsh, S. (2004). A QoE Sensitive Architecture for Advanced Collaborative Environments. Paper presented at the First International Conference on Quality of Service in Heterogeneous Wired/Wireless Networks (QSHINE 2004), Oct. 18-20, Dallas, TX.

  5. Quality of Experience and Access Grid • Identifying tasks and needs • What is the user trying to accomplish? • Create task-specific AG venues • Populate venue with services that meet needs • Services are ranked based on importance to task • Deploying task specific AG services • Configure node services appropriate to the task • Start/stop/configure node services “auto-magically”

  6. AG Venue Customizer (AVC)The AVC Process AVC User Download task Configure services Change Task VideoService VideoService VisService VisService AudioService AudioService Add Shared App AVC Manager Choose task Choose bandwidth Store Task and Services

  7. AVC Features • Set of common tasks provided • Services configured based on CSCW research • User customizable tasks available • Users can add their own tasks • Controls node services through venue client • Works on multi-machine nodes • Adapts services based on bandwidth • Adaptation sensitive to task

  8. AVC Effects • control the launching and settings of AG node services • currently controls audio service via RAT parameters • audio encoding (L16, PCM, DVI, GSM) • audio sampling rate ( 16 kHz, …) • silence suppression (off, …) • lecture mode (off, …) • currently controls video service via VIC parameters • frame rate (24, …) • video size (normal, …) • video encoding (H.261, …) • bandwidth (64 – 4096) • max bandwidth (256 – 4096) • quantization quality (71 – 100)

  9. AVC Uses Typical uses for AVC are: • configure an important business meeting for the highest possible audio and video quality when all participants have high bandwidth • configure a distance education event where some students will have limited bandwidth to give relatively high priority to video (because of the visual materials being used in the lesson), and relatively low priority to audio • scale a meeting to take into account the minimum bandwidth available to the participants (e.g., someone is connecting from home)

  10. AVC in the AG Architecture AVC GUI Venue retrieves or saves matrix settings displays sends request interacts Venue DataStore AVC Controller VenueClientUI VenueClient responses requests or saves matrix settings gets matrix settings AGNodeService Venue Server Local DataStore AGService SOAP Proxy AVC Audio Service(s) AVC Video Service(s)

  11. Inside AVC • “DefaultSettings.ini” file defines the starting point • later, personal settings saved in “settings.ini” file (e.g., custom tasks, user properties) • current venue settings are stored on the venue server (application data store) • definitions for settings come from “settings.ini” file

  12. “The Matrix” • settings file contains “the matrix” – the heart of AVC

  13. Service Parameter Definitions • definition for each quality level for each service [auditory8] audiosilence = 0 audiofrequency = 16K streamname = Quality 8 audiolecture = 0 audioprimary = L16 [visual6] maxbw = 1800 update_note = 0 Quality 6 framerate = 24 videosize = normal bandwidth = 1024 defaultformat = h261 transmitonstartup = true quality = 81 Custom node services needed for more parameter control

  14. AVC Class Diagram AVC QoEApplicationDescription GUIApplication ManagerFrame UserFrame VenueDetailsDialog LocalDetailsDialog AboutDialog Version

  15. Developing AVC • AVC.py – collection of utility methods • access venue client functions • get client & server proxy • start & stop services via proxies • read venue data • read/write local & remote files & data • QoEApplicationDescription • handle “the matrix” • GUI code • initially built with Boa Constructor

  16. Future Work • implement control of other node/shared services • shared work spaces • presentation spaces • turn-taking support • decision support • privacy controls • meta-communications • what do quality settings mean for these services?

  17. Testing • concept testing • are customized venues better than default venues? • can users describe their tasks? • can we determine the needs for these tasks? • is the matrix correct? • usability testing • installation • integration • ease-of-use

  18. Issues and Limitations • need better media services • limited quality ranges • unstable with non-standard settings • video other than h.261, normal size • audio sampling other than 16 kHz • connects to first unicast bridge only • Boa Constructor/wxPython compatibility issues • task and service level definitions should be centrally stored on the data store and maintainable • need an event mechanism when a manager changes a venue customization • should return to AG service defaults when AVC quits (currently must re-start Venue Client)

  19. Node Services/Shared Apps • Node Services vs. Shared Apps • Shared Apps • Venue controlled • Can add features based on purpose, not based on node • Venue, not node based • Can’t start up shared apps on other machines in a node • Node services • Node, not machine based • Node controlled, not venue controlled • Need a way to configure services from venue

  20. The AVC Team • At the National Research Council of Canada, Ottawa • Andrew Patrick • Kenneth Emig • Janice Singer • Bruno Emond • Khalil El Khatib • Stephen Marsh • Siraj Sabihuddin (student programmer) • Changhua Wu (student programmer) • At Simon Fraser University, Vancouver • Brian Corrie • Todd Zimmerman • At the Communications Research Center, Ottawa • Sylvie Noel • For more information about AVC contact: Andrew.Patrick@nrc-cnrc.gc.ca

  21. Backup: Usage Tutorial

  22. Installing AVC • AVC home page: http://iit130033.iit.nrc.ca/AVC/index.html • installing the shared application: • download AVC shared application (AVCv0.3.zip) • unzip to a temporary folder • install as usual: agpm –f AVC.app

  23. AVC Node Services • download AVC Node Services (Windows and/or Linux) • unzip to temporary folder • copy service zip files to NodeServices location • e.g., AVCAudioService.zip  C:\Program Files\AGTk-2.3\NodeServices • configure your node to use the services using the ServiceManager

  24. Store an AVC Configuration • can make AVC node services the default, or store a custom node configuration

  25. Creating AVC Sessions • Start an application session • or join an existing session

  26. Launching the AVC Shared App • default is User Mode • right-click to select Manager Mode

  27. AVC: Manager Mode

  28. Choose A Task • select category and specific task

  29. Select Bandwidth Scaling • four bandwidth levels defined • scaling retains task characteristics (i.e., relative priority of services)

  30. Customizing Tasks • select File -> Customize • load existing task settings or start from scratch

  31. Saving New Tasks • give it a name and save it • will appear under a “custom” task category

  32. Help Information • Manager and User manuals included in shared application

  33. gives control over AG services can switch to Manager mode AVC: User Mode

  34. view the current settings View Venue Settings

  35. AVC User Properties • set preference for unicast or multicast • set personal information

More Related