{"id":258,"date":"2017-08-17T08:24:46","date_gmt":"2017-08-17T06:24:46","guid":{"rendered":"http:\/\/project.inria.fr\/acqua\/?page_id=258"},"modified":"2017-09-20T16:17:57","modified_gmt":"2017-09-20T14:17:57","slug":"introduction-to-acqua-beta","status":"publish","type":"page","link":"https:\/\/project.inria.fr\/acqua\/introduction-to-acqua-beta\/","title":{"rendered":"Introduction to ACQUA Beta"},"content":{"rendered":"

The following guide has the purpose to introduce you the\u00a0ACQUA beta<\/em> application, how it works and how you can interact with it.<\/p>\n

NOTE<\/strong>: being under development ACQUA is subject to frequent changes and will be improved constantly. For this reason all kind of feedback are encouraged.<\/p>\n

Index<\/h2>\n
    \n
  1. Context<\/a>\n
      \n
    1. Goal<\/a><\/li>\n
    2. QoE predictions<\/a><\/li>\n
    3. Feedback<\/a><\/li>\n<\/ol>\n<\/li>\n
    4. Quickstart<\/a>\n
        \n
      1. UI and Navigation<\/a><\/li>\n
      2. QoE predictions<\/a><\/li>\n
      3. Feedback<\/a><\/li>\n
      4. Settings and Customisation<\/a><\/li>\n<\/ol>\n<\/li>\n
      5. FAQ<\/a><\/li>\n
      6. Contacts<\/a><\/li>\n<\/ol>\n

        Context<\/h2>\n

        Goal<\/h3>\n

        ACQUA has a twofold goal:<\/p>\n

          \n
        1. provide<\/strong> Quality of Experience (QoE) predictions of common applications,<\/li>\n
        2. collect<\/strong> feedback and network measurements to enhance point 1).<\/li>\n<\/ol>\n

          Secondarily ACQUA provides statistics about: your current connectivity (such as delay, throughput and losses over your communication medium), how your connectivity affects your applications during your day.<\/p>\n

          In general ACQUA aims to provide awareness of your connectivity with a simple metric (the user Quality of Experience per application) suitable to non-technical users.<\/p>\n

          QoE predictions<\/h3>\n

          Why?<\/strong><\/p>\n

          Quality of Experience (QoE) predictions are used to show how applications are affected by your connectivity.<\/p>\n

          How?<\/strong><\/p>\n

          By running network measurements our application is able to predict, via Decision Trees, how an application will behave. Our models are currently calibrated via controlled experimentation. For more details please refer to\u00a0What is ACQUA?<\/a><\/p>\n

          Feedback<\/h3>\n

          Why?<\/strong><\/p>\n

          In order to extend our application and support more predictions we need data. Support for crowdsourcing is a central part of ACQUA. It has been therefore integrated in our application to extend it.<\/p>\n

          How?<\/strong><\/p>\n

          Quality of Experience (QoE) feedback can be provided anytime by users, i.e., you can rate how you application behaves to improve our models. We will match the current network conditions to your rating to improve or create new models!<\/p>\n

          Quickstart<\/h2>\n

          Here is a simple guide of how the functionalities of ACQUA appear in the application.<\/p>\n

          UI and Navigation<\/h3>\n

          \"\"<\/a><\/p>\n

          [ACQUA’s home screen]<\/em><\/p>\n

           <\/p>\n

          QoE predictions<\/h3>\n

          The Quality of Experience (QoE) is represented by the standard MOS scale (ranging from 1 to 5).<\/p>\n

          The following meter shows how each quality level is represented in the home view (worst to best):<\/p>\n

          \"\"<\/a><\/p>\n

          This meter is common to each application supported by our application.<\/p>\n

          The rating is relative to the normal application behaviour:<\/p>\n

            \n
          1. nothing works<\/em>, the application is not usable at all due to the lack of connectivity (e.g., cannot load anything). The usability is completely compromised and the application cannot be used at all;<\/li>\n
          2. bad usability<\/em>, the application works with major disruption (e.g., frequent communication errors, non-tolerable delays are experienced). The usability of the application is seriously compromised and frustrating;<\/li>\n
          3. average usability<\/em>, the application is usable with clear but tolerable delays (e.g., long buffering before playing a video). The usability is acceptable but a bit frustrating.<\/li>\n
          4. good usability<\/em>, the application suffer of minor issues (e.g., slightly long delays, video interrupts for a few seconds). The usability is fine and not frustrating, only slightly less fluid than in perfect conditions.<\/li>\n
          5. perfect usability<\/em>, the network didn’t affect the expected usage of the application (e.g., smooth playback of a video). The application works at its best.<\/li>\n<\/ol>\n

            Feedback<\/h3>\n

            Step 1. The Contribution button.<\/h4>\n

            Feedback can be provided to rate the behaviour of an application at any time by tapping the Contribution button.<\/p>\n

            \"\"<\/a><\/em>[Starting a Contribution]<\/em><\/p>\n

            You can also start a contribution by pressing the same button in a QoE tab. This will skip the step 2. as the contribution will refer to the application showed in that tab.<\/p>\n

            Step 2. Application selection.<\/h4>\n

            You can rate applications that are not yet supported in the predictions.<\/em><\/p>\n

            \"\"<\/a><\/p>\n

            [Selecting an Application]<\/em><\/p>\n

            Step 3. Rating.<\/h4>\n

            Finally we can rate our experience. The rating follows a standard (MOS) ranging from 1 (worst) to 5 (best). Each value corresponds to the one shown in the predictions (see QoE predictions).<\/p>\n

            Specific aspects of an application can be rated (e.g., search a content, upload an image, make a video call).<\/p>\n

            NOTE<\/strong>: the provided rating (on a 1 to 5 scale) must be relative to the normal application behaviour:<\/p>\n

              \n
            1. nothing works<\/em>, the application is not usable at all due to the lack of connectivity (e.g., cannot load anything). The usability is completely compromised and the application cannot be used at all;<\/li>\n
            2. bad usability<\/em>, the application works with major disruption (e.g., frequent communication errors, non-tolerable delays are experienced). The usability of the application is seriously compromised and frustrating;<\/li>\n
            3. average usability<\/em>, the application is usable with clear but tolerable delays (e.g., long buffering before playing a video). The usability is acceptable but a bit frustrating.<\/li>\n
            4. good usability<\/em>, the application suffer of minor issues (e.g., slightly long delays, video interrupts for a few seconds). The usability is fine and not frustrating, only slightly less fluid than in perfect conditions.<\/li>\n
            5. perfect usability<\/em>, the network didn’t affect the expected usage of the application (e.g., smooth playback of a video). The application works at its best.<\/li>\n<\/ol>\n

              \"\"<\/a><\/p>\n

              [Rating and Submitting a feedback]<\/em><\/p>\n

              Setting and Customisation<\/h3>\n

              The home screen can be customised by adding \/ removing tabs in the home screen.<\/p>\n

              To add a tab simply press the + icon and add the tab from the list.<\/p>\n

              To remove a tab slide it to the right or left of the screen.<\/p>\n

              To modify the order of the tabs simply drag and drop them (some mobile-specific bugs have to be fixed).<\/p>\n

              \"\"<\/a><\/p>\n

              [Example of Customisation of the Home Screen]<\/em><\/p>\n

              FAQ<\/h2>\n