SightPlusPlus-AVINA-Website/implementation.html at main · UCL-SightPlusPlus/SightPlusPlus-AVINA-Website · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
<!doctype html>
<html lang="en">
<head>
  <!-- Required meta tags -->
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <meta http-equiv="X-UA-Compatible" content="IE=edge">
  <!-- Font Awesome icons (free version)-->
  <script src="https://use.fontawesome.com/releases/v5.15.3/js/all.js" crossorigin="anonymous"></script>
  <!-- Bootstrap CSS -->
  <link href="https://cdn.jsdelivr.net/npm/bootstrap@5.1.0/dist/css/bootstrap.min.css" rel="stylesheet" integrity="sha384-KyZXEAg3QhqLMpG8r+8fhAXLRk2vvoC2f3B09zVXn8CA5QIVfZOJ3BCsw2P0p/We" crossorigin="anonymous">
  <link rel="stylesheet" type="text/css" href="css/style.css" />
  <title>AVINA website</title>
</head>
<body>
<nav class="navbar fixed-top navbar-expand-sm navbar-light bg-light">
  <div class="container">
    <span class="navbar-brand mb-0 h1">AVINA</span>
    <button
            type="button"
            data-bs-toggle="collapse"
            data-bs-target="#navbar"
            aria-controls="navbar"
            aria-expanded="false"
            aria-label="Toggle navigation"
            class="navbar-toggler"
    >
      <span class="navbar-toggler-icon"></span>
    </button>
    <div class="collapse navbar-collapse" id="navbar">
      <ul class="navbar-nav ms-auto ">
        <li class="nav-item active">
          <a href="index.html" class="nav-link">Home</a>
        </li>
        <li class="nav-item active">
          <a href="overview.html" class="nav-link">Overview</a>
        </li>
        <li class="nav-item active">
          <a href="#" class="nav-link">Implementation</a>
        </li>
        <li class="nav-item active">
          <a href="test.html" class="nav-link">Testing</a>
        </li>
        <li class="nav-item active">
          <a href="installation.html" class="nav-link">Installation</a>
        </li>
        <li class="nav-item active">
          <a href="team.html" class="nav-link">Team</a>
        </li>
        <li class="nav-item active">
          <a href="https://github.com/UCL-SightPlusPlus" class="nav-link">
            <i class="fab fa-github" style="width:25px; height:25px;"></i>
          </a>
        </li>
      </ul>
    </div>
  </div>
</nav>
<!-- Main Content-->
<div class="container mt-5 head">
  <div class="text-center">
    <div id="implementation" style="margin-bottom: 5%;">
      <h2 class="fw-light">Implementation</h2>
      <div class="container text mt-5" style="width: 70%;">
        <p>
          This is a functional view of the AVINA and its three systems. We’ll go into detail about them below.
        </p>

        <img class="card-img-top" src="images/DevDia.png" alt="development view">
        <hr>

        <h4 class="fw-light">App</h4>
        <div align="center"><img src="images/AppDia.png" alt="app view" align="middle" width="40%" height="40%"></div>
        <br>
        <p>When the app is running, it uses the ‘Server Connectivity Handler’ to scan for AVINA enabled locations. Once it comes in range of one, it will send a ‘AVINA Location Found Notification’ to the user, which one pressed will take them to the app’s main screen. </p>
        <p>Once connected, the ‘User Locator’ is used to find the which area the user’s in at the location, which is done by searching for Bluetooth beacon signals. Once a signal is discovered by the app, it will use the location server’s app interface to find which area this Bluetooth beacon signal belong to.</p>
        <p>Whenever the user asks a question through voice command (or text field), the question is sent through a ‘Transcriber’ to convert the speech into text, and then into a ‘Translator’ to turn the speech into English, since that language the server requires. This question is then sent to the location server’s app interface to get an answer.</p>
        <p>When the answer is received from the server, the ‘Question Handler’ first sends it to the ‘Translator’ to translate it into the user’s device’s set language; this text is then sent to the ‘Speech Synthesizer’ to read it outload to the user.</p>
        <hr>
        <h4 class="fw-light">Location Server</h4>
        <div align="center"><img src="images/location_view.png" alt="app view" align="middle" width="50%" height="50%"></div>
        <br>
        <p>When the location server is set up, it has two interfaces that are used to send and receive information.</p>
        <p>The ‘Camera (NUC) Interface’ is used to receive events from the cameras and then store them in the ‘Building Event Database’ for later use. The cameras are identified by their ID which were set up within the ‘Device Database’. </p>
        <p>When a person asks a question, the textual question is sent through the interface and received by the ‘Question Handler.’
          The handler will then search for keywords within the question and see if it contains certain words (e.g., ‘chair’, ‘queue’) and will then decide whether to get information from the ‘Room Event Finder’
          (information specific for the room the user is in) or if it should send the question to the Azure QnA chatbot.
          Regardless, a response will be returned, and the handler will use the ‘Sentence Generator’ to make the response into an actual sentence meant to be heard by the user.
          This sentence will then be sent to the ‘AVINA App Interface’ and to the user’s phone where it is read out to them. </p>
        <hr>

        <h4 class="fw-light">Organisation Server</h4>
        <div align="center"><img src="images/organisation_view.png" alt="app view" align="middle" width="50%" height="50%"></div>
        <br>

        <p>An organisation will set up this server in their head office to monitor branches. They’ll get a code which they share with their branches. At which point, profiles will be added to the server’s home page.</p>
        <p>Periodically, the locations servers will send the current devices being used via the ‘Location Server Profile Interface’ This is information is then handled by the ‘Profile Handler’ and stored in the ‘Profile Database’
          The IT administrator of the organisation will then be able to view these devices the through the ‘Server Profile Page’ by selecting a specific branch location. </p>


      </div>
    </div>

  </div>
  <!-- Footer-->
  <footer class="border-top">
    <img src="images/logos.png" style="width: 500px; height: 58.5px; display: block; margin: auto;" class="mt-3 mb-3">
    <div class="small text-center text-muted fst-italic">Copyright &copy; AVINA 2021</div>
  </footer>
  <script src="https://cdn.jsdelivr.net/npm/bootstrap@5.1.0/dist/js/bootstrap.bundle.min.js" integrity="sha384-U1DAWAznBHeqEIlVSCgzq+c9gqGAJn5c/t99JyeKa9xxaYpSvHU5awsuZVVFIhvj" crossorigin="anonymous"></script>

</body>
</html>