\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={An Approach to Establishing Simultaneous Server-Side Connections for NFC/Bluetooth Enabled Quiz Management Systems},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2020-01-15 (revised: 15 January 2020)}
\def\TheID{10.34257/GJCSTAVOL20IS1PG1\makeatother }
\def\TheDate{2020-01-15}
\title{An Approach to Establishing Simultaneous Server-Side Connections for NFC/Bluetooth Enabled Quiz Management Systems}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Jedidiah  Aqui}

             \author[2]{Michael  Hosein}

\renewcommand\Authands{ and }

\date{\small \em Received: 7 December 2019 Accepted: 4 January 2020 Published: 15 January 2020}

\maketitle


\begin{abstract}
        


Near Field Communication is a set of communication protocols for communication between two electronic devices over a distance of 4cm or less and Bluetooth is a wireless technology standard used for exchanging data between fixed and mobile devices over short distances using UHF radio waves in the industrial, scientific and medical radio bands, from 2.402 GHz to 2.480GHz, and building personal area networks(PANs). Both these protocols facilitate wireless/ internet less communication between devices that have the capabilities. This paper seeks to further expand the concept and usage of these protocols via the examination of modifications made to a Quiz Management System. The Quiz Management System, which is a solution to further advance the notion of a smart classroom setup within the context of short-range wireless technologies has already seen iterations developed on both the NFC and Bluetooth side of things.

\end{abstract}


\keywords{quiz management system, smart classroom, protocol, bluetooth, NFC, UHF}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\begin{textblock*}{10cm}(1.05cm,3cm)
{{\textit{CrossRef DOI of original article:}} \underline{10.34257/GJCSTAVOL20IS1PG1}}
\end{textblock*}\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ith the advent of a global pandemic, societies at large have witnessed the shutting down of numerous institutions of gathering and socializing. Many of those institutions consist of churches, sporting events, entertainment events, schools, etcetera. In light of these shutdowns, governments the world over, were forced to adapt and facilitate numerous activities that were once viewed as "in person" or "attendance mandatory" activities via the internet and its many online portals. The area in which this project seeks to primarily address, is the educational institutions (Schools).\par
The use of online classes is not a new topic of discussion or concept as far as technological advances in the educational sphere is concerned. Numerous papers and contributions have been made with respect to online classes/sessions \hyperref[b9]{(Kulkarni et al., 2013 and}\hyperref[b5]{Frydenberg, 2007)} and  {\ref (Grandon, Alshare, and Kwun,2005)}.Additionally, what is quite notable in the midst of an ongoing pandemic is the vast migration of many institutions to the use of Online platforms to host their classes, meetings, seminars etcetera. The fastpaced transformation of these institutions to technological platforms all encompass aspects of what is being termed the "new normal". But one must also take into consideration the latter phases of the "new normal", which would encompass a steady and careful re-engagement of the former way of life at least to a substantial extent. With a re-engagement of the former, one can expect institutions of learning to begin the process of re-opening and facilitating in-person knowledge transfer activities such as classes, lectures, tutorials, etcetera as safely as possible. With safety being of paramount priority, one can expect all necessary guidelines as far as social distancing dictates, to be enforced.\par
To address the adaptation to the latter phase of the "new normal" the option of a smart classroom approach would be explored and further elaborated upon. (According to Shalini, December 2018) A smart classroom is where the concept of blended learning is considered to be blooming, it isa technologically enhanced environment that enables teaching and learning opportunities on a different level. Within the context of a smart classroom, the use of the Quiz Management System(QMS) would come into play. To generalize, the QMS is a system that is geared towards facilitating the distribution of quizzes and/or quiz material by the teacher(server) as well as subsequent retrieval of quiz material by students (clients) for grading and redistribution.\par
The QMS itself is a step in the right direction as it brings the notion of leveraging Bluetooth/NFC technology to further promote or simulate a smartclassroom setup. The QMS captured functionality that allowed students to submit their work and review the marked material and it also allowed the teachers(server)to select the quiz material to distribute, collect the quiz material for marking and perform analytics on the data obtained before subsequently distributing the marked material. Its merits cannot be overlooked as it fostered contactless communication from client to server devices and vice versa. However, there were some limitations in the developed model that were noted.\par
A key limitation of the QMS was its inability to support a large number of simultaneous connections on the server side. Consider the work done by (M.Hosein and L.Bigram, 2013). Theirs was a Bluetooth Quizzing Application in Android called Blue Q. The developed application was able to simulate much of the QMS's core functionality via the use of the Bluetooth protocol, however it was only able to facilitate simultaneous connections to a maximum of 5 devices, the authors further postulate that future work on the developed application could entail the supporting of more simultaneously Bluetooth connections on the server side. Additionally, in the studies done by  {\ref (Mohammed Salah Abood, Mahamod Ismail, and RosdiadeeNordin, 2017)}. The authors were able to develop and further add to the work of the Bluetooth application formerly mentioned by utilizing XML to structure messages passed between both client and server. Furthermore, in their work, the authors developed a solution using Near Field Communication Technology (NFC) as the main protocol for transferring information from Client(student) to Server(Teacher). However as was the case in the first iteration of the application, this was also a system developed on the basis of one to one communication between Client and Server devices.\par
This problem can further be grasped by adding some context. For example, if the QMS was to deployed in a classroom of 5-6 persons, sharing course content to students and also receiving course content/solutions from students(client), would be considered a relatively simple task that can be performed in a short timeframe, however in the context of a University classroom that may house well over 100-200+ students in a session. Distributing course contents(quizzes) and receiving student feedback can pose quite a challenge, as one must now consider the amount of time it takes to fully conduct this activity from the Server to each individual Client, given that there are no anomalies to hinder the process with each student.\par
An additional level of analysis is also required in establishing which of the two protocols (NFC or Bluetooth) should the testing of multiple server-side connections be executed with. In retrospect, whilst these developed models did in fact have a substantial impact in promoting a smart classroom setup using Bluetooth and NFC technology, the identified gaps would serve as an indication as to the slow adoption of the "smartclassroom" concept which sees the utilization of these protocols for distributing information. It is not so much so as to how to develop NFC/Bluetooth solutions to compliment the idea of a smart classroom setup, but is a matter of how do we increase the efficiency and practicality of these systems to gain further support from Universities the world over, in the midst of a pandemic. This project entails the resolution of these core problems as an iterative step to the already developed Quiz management system. By addressing these problems, the feasibility of a safe smart classroom environment in the "new normal" period can be further bolstered and gain support. 
\section[{II.}]{II.} 
\section[{Literature Review}]{Literature Review}\par
In This Chapter, we would not only be exploring the research work and implementations conducted as it relates to similar quizzing applications. But we will also be exploring the work done as it pertains to the concepts of Bluetooth connections to multiple devices as well as identify the merits and limitations of each of the discussed material.\par
(Mohammed, Mahamod, and Nordin, 2016) presented an NFC-based classroom tool known as the 'Quiz management system'. The solution (QMS) was able to further advance the notion of a smart classroom setup within the context of short-range wireless technologies. As it pertains to this system, one would recognize the function of two key actors, one being the Student (Client) and the other being the Server(Teacher).For the sake of simplicity we would refer to the Student/Client device as Participant1 and the Server/teacher device as Participant 2. The core functions of each actor are as follows:\par
Participant 1: Is the Client/Student who would do the requesting of quizzes as well as the submission of quizzes for correction.\par
The key activities are captured in the below bullet point listing 1. Interacting with the UI of the application 2. Quiz handout activity 3. Answer Collection Activity 4. Quiz Submission Activity 5. Results Activity Participant 2: Is the Server/Teacher who would be responsible for distributing the quizzes via his/her interface. The Server/Teacher would also be privy to additional functionality as opposed to the client and thus, can be viewed as a super-user within the context of the system.\par
The key activities are captured in the below bullet point listing 1. Interacting with the UI of the application 2. Input activity 3. Quiz reception activity 4. Quiz performance activity 
\section[{Answer submission activity}]{Answer submission activity}\par
The roles of 'Participant 1' and 'Participant 1' can now be observed within the context of the QMS System via the below general architecture diagram in (Figure  {\ref 2}.1):\par
Another system was also developed by \hyperref[b12]{(Michael and Laura, 2013)} which was a Bluetooth quizzing application for the android platform was developed. This system was quite similar to the formerly mentioned NFC solution with one of the major differences being the choice of protocol for communication and sharing of data. The protocol utilized was the Bluetooth protocol. The designed solution addresses the below problems directly:\par
1. Low attendance rate 2. Low pass rates 3. Poor Learning curve of students 4. Time consuming nature of a paper-based quizzing system The solution Blue Q consisted of 2 main components, which were the 'Server Side' and the 'Client Side' these components were implemented on the Android Operating System. The proposed system encompassed several key functions/features to facilitate the distribution and receiving of course content (quiz material). The core functions are as follows: In the work of (Brian, 2014) a low-level vantage point of establishing Bluetooth connections amongst android devices is explored and segments of code provided to further solidify the concepts. This paper was able to shed light on many of the concepts that were required for developing our solution as well as the limitations of the selected protocol for communicating data(Bluetooth).The author postulates that the Android device will be communicating with a Bluetooth module connected to an Arduino Uno microcontroller as shown in Figure \hyperref[fig_1]{4} below. The author focused primarily on the establishment of Bluetooth connections between two devices and delved further into the issues commonly experienced throughout the process of turning on Bluetooth, establishing a connection between devices, multi-threading and transferring data. Security'. Pertaining to work done with respect to NFC applications, aspects of NFC that were currently being applied in the field of short-range applications were highlighted. The focus was made to the usage of NFC chips with mobile phones. In the work done, the author made mention of the three main operating models of NFC, with the primary focus in the interest of this paper, being related to the "peer to peer communication" operating model(O.M.). It was noted that in this O.M. only two devices at a time could have exchanged the data at the link layer level.\par
And finally, in the work done by (Zimbric, Oct 2012) the focus was on pairing multiple devices to a Bluetooth accessory. The concept was very similar to the work done on this thesis however, the approach was very different as pairing was done based on device profiles for example 'hand-held' device or 'wireless headphones'. Furthermore, this approach primarily focused on the Bluetooth accessory as opposed to the device in which it would have been interacting with. The goal was to have the accessory connected to two devices at a time where by functions could have been executed. 
\section[{III.}]{III.} 
\section[{Application Details}]{Application Details}\par
There were 3 main approaches employed in the proposed solution to solve the initially identified problems. They are detailed below: Approach 1: Version 2 (multi-channel -Identical UUIDs) This approach explored the route of adding additional RFCOMM channels that are associated with the same UUID. It mimicked the concepts of Client/Server TCP/UDP communications (Lei \hyperref[b10]{Wang et al.,2000)}having the server socket wait for connection from a client socket, whilst a listening socket is activated for receiving new connections and mapping unto the server socket. In this concept, if we were to assign maximum of2 channels per UUID, we would accomplish simultaneous connections for data transfer to 2 x 8 client devices at a time. The below Sequence Diagram Shows the flow of events in Approach 1-Version 2: By merit of how RFCOMM works it is stated that it would support a total of 60 simultaneous connections based on the UUIDs assigned to each of those channels. This UUID is what the client uses to firstly identify the channel it wishes to connect to via its SDP call, then a connection is established, but since RFCOMM is a serial communication protocol, it would only allow 1 connection at a time per channel, there is no multiplexing unless you switch from a serial protocol to a parallel protocol. Going further into this, the proposed modification could see the sharing of UUIDs for 2 channels at a time, 2 channels being the upper limit. Given that all the necessary provisions are made available, and the user has the optimum storage and processing power to host 60simultaneous connections, this method of dual channeling per UUID could possibly push the amount of simultaneous connections to "120"total. Now this is of course the perceived amount of simultaneous connections, however it would still be recorded as 60, since half the figure represents Unique (UUIDs) and the other a replication.\par
But that is observing from a holistic point of view in accordance with the protocol's specifications. As we apply this logic to the presented solution, we can now seek to address the inefficiency of having limited amount of channels used at any given time for material to be distributed by the server device or submitted by the client device. Consider the current application's limit of 8 channels per server device. That alludes to the point that there are 8 UUIDs that are hardcoded into the lowlevel code of the server device by which the RFCOMM channels can be accessed by. The solution being proposed now assigns a total of 2 channels per UUID. This therefore raises the amount of allowable connections to the server by +8 giving a total of 16 connections at a time per server device. The below figure shows the results of sharing UUIDs as more than the maximum limit of 8 devices were able to connect. If in its strictest sense the server device must maintain 8 channels irrespective of UUIDs. Then a queue for each channel with an allocation of 1 allotment for a client device would be established, since the UUID would refer to the channel number in which the service is being provided, the queue would be able to guarantee that a connection has already been made with the channel, however it is currently in use and thus, once completed it will become available.\par
This guarantee stands on the basis that based on the UUID both the client devices would be treated as one device attempting to access the same service. However, it would all come down to which device connects first. Connecting to the server first would be based on which of the 2 devices is nearer, with the device closest, being successful in connecting to the channel and being able to access the channel and the device furthest from the server being successful in connecting to the server but placed into queue. The below figure shows the results of queuing clients with the samw UUID. This functionality ensures that the client will receive the quiz content without having to re-attempt connecting to the server multiple times. Thus, this method is a viable option for improving the efficiency of Approach 1. Approach 2 -Delegate Function() Approach 2: Given that the server device is mainly responsible for the distribution of quizzing materials and can only supply material to up to 8 devices at a time. The proposed solution would see the modification of the existing system to include the 'delegation' functionality. The delegation functionality works as such: Server Device connects to 8/100 devices at a time, given that the assumed sample/classroom size is 100 students. Then in an effort to increase the efficiency of the system, the Server device can select one of the connected client devices and elevate their privileges or rather give/delegate new functionality to allow the distribution of quiz material. Assuming that the selected client device is able to support the same amount of connections as the server device, this therefore means that a total of 16/100 devices can connect to receive quiz material at a time. If the number of client devices 'n' that is given Server privileges increases, then the rate in which quiz material can be distributed would take on the form of an exponential curve, thereby increasing the efficiency of the Bluetooth quizzing system. This approach when compared to the first approach has some immediate advantages: It does not affect the performance of the original hosting device but rather acts as an extension of its functions. What must be taken into consideration is the UUID generator function in which random UUIDs are generated and are hardcoded as the UUID's assigned to the available channels for clients to access their services. This method must ensure that the function delegate() is triggered upon the original Server Device selection of the option to Delegate. As it is an extension of Blue q the interface would consist of the below options. In theory this additional functionality can be likened unto a wi-fi peerto peer network as was postulated by developer.android.com, October2020. It is important to recall that the core concept of a peer-topeer network is to partition tasks or workloads between pairs. In this concept peers are equally privileged, similar to the work done by  {\ref (SewookJung et al., 2007)}. However, in this modification of the system, the server device, determines the functions to send to the client device and thus plays an integral role in determining the amount of privileges a selected client device is afforded.\par
The below Sequence Diagram Shows the flow of events in Approach 1-Version 2: From the above results it can be observed that whilst all approaches when compared to the previous QMS did offer more simultaneous connections, the 'Delegate' approach proved to be the most efficient and scalable method as it was able to support a far greater number of simultaneous connections within approximately the same time as the other proposed solutions. A total of 64 connections versus 16 connections of the other approaches can be supported by the 'Delegate' approach. A further breakdown on the testing methodology, results and technical analysis can be viewed in the conference paper: "A Technical review of the testing methodologies for QMS Simultaneous Server-Side connections" V. 
\section[{Conclusion}]{Conclusion}\par
In Conclusion, three solutions/approaches were developed and implemented to solve the problem of lack of popularity or usage of Bluetooth/NFC Quizzing systems within the context of a University Ambient.\par
These three solutions, saw the usage of the concepts of sharing UUIDs to achieve a greater level of connectivity to the server device as well as the concept of delegating responsibilities from the server device to the client device in an effort to distribute channel sharing load, thus making even more RFCOMM channels available and elevating the privileges of selected clients.\par
The test results of all approaches were reviewed in an effort to gauge the performance of each of the proposed and developed approaches versus the previous BlueQ system. From the stated results it was shown that the delegate approach proved to be the most meritorious in terms of performance and scalability when compared to the other implemented approaches. Some of the future work of this paper, would see a similar implementation with the usage of the NFC Protocol. It would also see further work being done in attempting to make the modified QMS a cross-platform entity and not only an 'android specific' solution. Additional work can also be done to further the security aspects surrounding the sharing of UUIDs\begin{figure}[htbp]
\noindent\textbf{13}\includegraphics[]{image-2.png}
\caption{\label{fig_0}1 .Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 5 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{61}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 6 :Approach 1 -}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{7}\includegraphics[]{image-6.png}
\caption{\label{fig_4}Figure 7 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{8}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Figure 8 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{9}\includegraphics[]{image-8.png}
\caption{\label{fig_6}Figure 9 :}\end{figure}
 			\footnote{© 2020 Global Journals} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Jung ()]{b17}\label{b17} 	 		\textit{},  		 			Sewook Jung 		.  	 	 		\textit{Pervasive and Mobile Computing}  		2007. 3 p. .  	 
\bibitem[Michael and Laura ()]{b12}\label{b12} 	 		‘An Educational Bluetooth Quizzing Application in Android’.  		 			Hosein Michael 		,  		 			Bigram Laura 		.  		 IJWMN) 5.6.  	 	 		\textit{International Journal of Wireless Mobile Networks}  		2013.  	 
\bibitem[Mcdermott-Wells ()]{b11}\label{b11} 	 		‘Bluetooth scatternet models’.  		 			P Mcdermott-Wells 		.  	 	 		\textit{IEEE Potentials23}  		2005. 5 p. .  	 
\bibitem[Create P2P connections with Wi-Fi Direct (2020)]{b4}\label{b4} 	 		 developer.android.com.  		\textit{Create P2P connections with Wi-Fi Direct},  				October 2020.  	 
\bibitem[Aneesh et al. (2012)]{b1}\label{b1} 	 		\textit{Design and implementation of Bluetooth MAC core with RFCOMM on FPGA},  		 			R Aneesh 		,  		 			Sreekumari 		,  		 			Jiju 		.  		Dec 2012.  	 
\bibitem[Davidrajuh (2009)]{b3}\label{b3} 	 		‘Evaluating performance of a Bluetooth based classroom tool’.  		 			Reggie Davidrajuh 		.  	 	 		\textit{International Journal of Mobile Learning and Organization}  		January 2009.  	 
\bibitem[Grandon et al. (2005)]{b6}\label{b6} 	 		‘Factors Influencing Student Intention to Adopt Online Classes: A Cross-Cultural Study’.  		 			Elizabeth E Grandon 		,  		 			Obyung Khaled Alshare 		,  		 			Kwun 		.  	 	 		\textit{J. Comput. Sci. Coll}  		 1937-4771.  		Apr. 2005. 20 p. .  	 
\bibitem[Hongwei ()]{b7}\label{b7} 	 		 			Du Hongwei 		.  	 	 		\textit{NFC Technology: Today and Tomorrow},  				2013.  	 	 (and Communication 2.4.) 
\bibitem[Graham (ed.) (2012)]{b20}\label{b20} 	 		\textit{Methods and Devices for automatic multiple paring of Bluetooth devices},  		 			Adams Mark GrahamJr 		.  		Zimbric Frederick J. (Gurnee, IL US) Walsh Michael G. (ed.)  		Oct 2012. Johnsburg IL US; Hoschton GA US.  	 
\bibitem[Mohammed et al. ()]{b14}\label{b14} 	 		 			Salah Mohammed 		,  		 			Ismail Abood 		,  		 			Rosdiadee Mahamod 		,  		 			Nordin 		.  		\textit{A Quiz Management System Based on P2P Near-Field Communication On Android Platform for Smart Class Environments},  				2016.  	 
\bibitem[Wang ()]{b10}\label{b10} 	 		‘Multipath source routing in wireless ad hoc networks’.  		 			Lei Wang 		.  	 	 		\textit{Conference Proceedings. Navigating to a New Era (Cat. No.00TH8492)},  				2000. 2000. 1 p. .  	 
\bibitem[Naser Hossein, Motlagh (ed.) (2012)]{b15}\label{b15} 	 		\textit{Near Field Communication (NFC) A Technical Overview},  		Naser Hossein, Motlagh (ed.)  		May 2012.  		 			University of Vasa Faculty of Technology Telecommunication Engeineering -Research Gate 		 	 
\bibitem[Ajay (2019)]{b0}\label{b0} 	 		\textit{NFC vs. Bluetooth: A Detailed Comparison},  		 			Goyal Ajay 		.  		May 2019.  	 	 (In: endivesoftware.com) 
\bibitem[Kulkarni (2013)]{b9}\label{b9} 	 		‘Peer and Self Assessment in Massive Online Classes’.  		 			Chinmay Kulkarni 		.  	 	 		\textit{ACM Trans. Comput.-Hum. Interact}  		 1073- 0516.  		Dec. 2013. 20  (6) .  	 
\bibitem[Miklos ()]{b13}\label{b13} 	 		‘Performance aspects of Bluetooth scatternet formation’.  		 			G Miklos 		.  	 	 		\textit{First Annual Workshop on Mobile and Ad Hoc Networking and Computing. MobiHOC (Cat. No.00EX444)},  				2000. 2000. p. .  	 
\bibitem[Frydenberg ()]{b5}\label{b5} 	 		‘Persistence in University Continuing Education Online Classes’.  		 			Jia Frydenberg 		.  	 	 		\textit{he International Review of Research in Open and Distributed Learning}  		2007. 8  (3) .  	 
\bibitem[Ratna ()]{b19}\label{b19} 	 		\textit{Phones compatible with NFC in},  		 			Sneh Ratna 		,  		 			Choudhary 		.  		March 2020. 2019.  	 
\bibitem[Brian et al. ()]{b2}\label{b2} 	 		‘Sending and Receiving Data via Bluetooth with an Android Device’.  		 			Wirsing ; Brian 		,  		 			Bär 		,  		 			Guido Henning 		,  		 			Rößling 		.  	 	 		\textit{Erik Tews, and Elmar Lecher},  				2014. 2006.  	 
\bibitem[Robert (2019)]{b16}\label{b16} 	 		\textit{What is NFC and how does it work},  		 			Triggs Robert 		.  		 androidauthority.com.  		June 2019.  	 
\bibitem[Ken and Jeff ()]{b8}\label{b8} 	 		\textit{What is Scrum?},  		 			Schwaber Ken 		,  		 			Sutherland Jeff 		.  		2013.  	 
\bibitem[Shalini (2018)]{b18}\label{b18} 	 		\textit{What's a Smart Classroom and Why Do You Need It},  		 			Khemka Shalini 		.  		December 2018.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
