\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={Development of a Portable IP-Based Remote Controlled System for Mobile Robot},
 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{2021-07-15 (revised: 15 July 2021)}
\def\TheID{10.34257/GJCSTDVOL21IS1PG21\makeatother }
\def\TheDate{2021-07-15}
\title{Development of a Portable IP-Based Remote Controlled System for Mobile Robot}
\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]{Daramola O.  A.}

             \author[2]{Obe  O.}

             \author[3]{Oriolowo  A.}

             \affil[1]{  Federal University Of Technology}

\renewcommand\Authands{ and }

\date{\small \em Received: 11 June 2021 Accepted: 2 July 2021 Published: 15 July 2021}

\maketitle


\begin{abstract}
        


The use of Mobile Robots to interact with objects in remote locations has proved to be useful in areas not easily accessible or too dangerous for humans. Various means have been used to remotely operate or control Mobile Robots. These range from wired connection to Wireless connection like radio frequency signal and more recently internet controlled Mobile Robot using the TCP/IP protocol stack. However, the problem of remote control dependence on the Mobile Robot Platform or configuration has made it difficult to switch controllers between Mobile Robots. In this work, a portable IPbased remote control system has been designed and implemented to remove the constraint imposed by the Mobile Robot's platform in choosing the control interface. The system developed was built on three loosely coupled components working together to ensure a high degree of Control interface portability. The Mobile Robot Gateway component was used to receive and send data from the Mobile Robot

\end{abstract}


\keywords{mobile robot, remote control, command hub, rest architecture, TCP/IP, IP-based}

\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/GJCSTDVOL21IS1PG21}}
\end{textblock*}\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
obile robots were defined by \hyperref[b29]{Posadas et al (2008)} as physical agents that move and interact continuously while embedded in a dynamic environment. A mobile robot is also described as a situated and embodied agent endowed with mobility \hyperref[b23]{(Obe and Dumitrache, 2012)}. Control of mobile robots is categorized into three types namely, autonomous control, semi-autonomous control, and Tele operation. Autonomous control implements various control algorithms that control mobile robots in their environment without human intervention. Semiautonomous control allows a user to instruct the mobile robot on what to do but the robot decides how the task is carried out. This mode of control is supervisory. In a Tele operated control, the mobile robot is entirely controlled by the user. Oxford dictionary (2015) defines "remote control" as the control of a machine or apparatus from a distance utilizing radio or infrared signals transmitted from a device. Teleoperation is often used in place of Remote control in research or technical environments. Teleoperation means controlling or doing work at a distance \hyperref[b37]{(Wichmann et al, 2014)}. The meaning of the distance, however, can vary. The distance can be physical, such as an operator controlling a robot at a remote location. The distance could also be a change in scale, for example, a surgeon using teleoperation to conduct surgery at the microscopic level. In 2014, Wichmann et al. reported that teleoperation systems are designed using a master-slave system model where the control system depends heavily on the mobile robot platform.\par
Various communication technologies have been used to achieve teleoperation for a mobile robot. These technologies include Bluetooth, Infrared, WIFI, GSM, Internet of Things (IoT) \hyperref[b7]{(Chikurtev, 2019)}, and Internet \hyperref[b20]{(Luimula et al., 2007)}. While some of these technologies impose a constraint on the range of operation, GSM and the Internet have proven to overcome such barriers \hyperref[b8]{(Chin et al, 2003}\hyperref[b3]{, Ankit, 2014} {\ref and Juang\&Juang, 2016)}. The Internet which is based on TCP/IP enables connectivity of billions of devices worldwide, giving access to communication, data, pictures, videos, and even real images of distant environments \hyperref[b34]{(Siegwart and Saucy, 1999)}. The advancement in the development of internet applications has made it the ideal testing ground for sophisticated new applications, such as video-conferencing and remote control systems \hyperref[b25]{(Oboe \& Fiorini, 1997)}. However, only a few examples of real physical interaction with distant places are available at the moment. \hyperref[b12]{Goodrich and Schultz (2007)} defined two categories of interaction, remote and proximate. Remote interaction refers to the situation where the human and the robot are separated spatially or even temporally (i.e., Opportunity Mars rover), while with proximate interaction the humans and the robots are collocated.\par
This research work aims at creating a portable IP-based remote-controlled system for mobile robot interaction. According to \hyperref[b15]{James (1997)}, a software unit is portable (exhibits portability) across a class of environments to the degree that the cost to transport and adapt it to a new environment in the class is less than the cost of re-development. Portability in general terms is the usability of an object or component of the system in multiple environments without any modification in the internal structure.\par
Internet Protocol (IP) is a protocol in the Internet Layer of Transport Control Protocol/Internet Protocol (TCP/IP) model. It hides the underlying physical network by creating a virtual network view \hyperref[b21]{(Lydia et al, 2006)}. It is an unreliable, best-effort, and connectionless packet delivery protocol. Best-effort means that the packets sent by IP might be lost, arrive out of order, or even be duplicated. IP was designed with the assumption that a higher layer of the protocol will address these anomalies. According to \hyperref[b21]{Lydia et al., (2006)}, one of the reasons for using a connectionless network protocol was to minimize the dependency on specific computing centers that used hierarchical connection-oriented networks. Available remote control systems require specialized hardware and software that are heavily dependent on the mobile robot's platform or architecture. In this work, an architecture is proposed to eliminate the dependency of the remote control system on the robot's platform.\par
There are issues with existing mobile robot remote control systems which include but are not limited to, operation range, portability, and the multi-interface option of the system. Various researchers have addressed some of these problems, however, the problem of switching a remote control system from one mobile robot to another with little or no reconfiguration has not been dealt with. In \hyperref[b8]{Chin et al. (2003)}, a Real-Time Remote Control Architecture Using Mobile Communication was proposed. GPS, GSM, and GIS were applied in the development of real-time communication for remote data transfer which solved the range of operation problems, but the system lacked portability. \hyperref[b16]{Jose et al. (2004)} illustrated a Java/Matlab-Based Environment for Remote Control System Laboratories. Matlab/Simulink and the Quanser Win Con environment were used to develop a control system using the HTTP server to process client requests. The client program is a java applet written in Java. The range of operation issue was eliminated by the architecture but failed to address portability and multi-interface options. In Mobile Robot Temperature Sensing Application via Bluetooth, Abdullah and Poh (2011) developed a control system using the KC-21 Bluetooth module and PIC16F877A microcontroller for remote temperature sensing. The system has a limited range of operations. \hyperref[b3]{Ankit et al. (2014)} in Controlling of Remote Robot through mobile phone using DTMF Signal, developed a remote control system using microcontroller, CDMA modem, and DTMF signal. The system lacks portability and multi-interface options. \hyperref[b2]{Almali et al. (2015)} developed a Wireless Remote control for Mobile robots operating in dangerous or narrow places for human beings. A 433MHz RF transceiver module was used to establish a connection between the mobile robot and the computer controlling it. The system has a limited operating range and also lacked portability.\par
This research work addresses the issue of portability and multi-interface options for mobile robot remote control systems. This will facilitate the use of one remote control system with a multi-interface for different mobile robots on several platforms, this will give room for using a robust interface for the control system at a particular time. 
\section[{II.}]{II.} 
\section[{Related Literature}]{Related Literature}\par
Oboe and Fiorini, 1998 in "A design and control environment for internet-based telerobotics describe the environment for the design, simulation, and control of internet-based force-reflecting telerobotics using a segment of the network to connect the master to the slave. Simulation of the complete telerobotic system and emulation using a planar force-reflecting master and a virtual slave uses a MatLab-Simulink program interfaced with a set of dedicated routines for internet modeling. The issues in the variable time-delay system were addressed by using the delay parameters acquired from the network probe to design the controller. However, the work does not address multiple interfaces that could be used as the master or controller. \hyperref[b19]{Lung et al., 2002}; designed an internet-based human-assisted robotic controller system but the security of the web page was not considered as anyone that stumbles on the web application can control the robot. \hyperref[b8]{Chin et al., 2003} adopted the use of G3 (global positioning system (GPS), global system for mobile (GSM), and geographic information system (GIS)) system in developing realtime communication and remote control systems for robot real-time remote control, navigation, and surveillance. The designed system is not portable as it was only implemented on a Windows platform. Visual Basic, which is the choice of programming language, is not supported on other operating systems. \hyperref[b16]{Jose et al., 2004}; developed a Java/Matlab-Based Environment for Remote Control System Laboratories, illustrated with an Inverted Pendulum -a novel environment that provides 24-hours-a-day access to a Web-based lab for the remote control of different didactic setups. A detailed description of an environment for the teleoperation of real Lab via the Internet, was achieved however, the design cannot be replicated on robots with different platforms due to the heavy dependence on Matlab/Simulink.\par
Abdullah \& Poh, 2011; Mobile Robot Temperature Sensing Application via Bluetooth developed a Bluetooth-based control system for remote measurement of temperature from the robot's surrounding environment. The range of operation is limited to ten \hyperref[b9]{(10)}   
\section[{Method a) System Overview}]{Method a) System Overview}\par
The proposed portable IP-based remote control system for Mobile Robots is aimed at solving two basic problems usually encountered with common Mobile Robot remote control systems. The first problem is the communication range between the Mobile Robot and its remote control interface. This range limit is entirely dependent on how far the communication link can transmit or receive data sent from both ends (usually 10 Meters for Bluetooth, 100 Meters for WIFI). The second problem is the portability of control interfaces with different platforms to provide different user interfaces that can be used to control different Mobile Robots. To solve the above-mentioned problems, the new system is divided into three functional parts namely: Command hub, Control Interface, and Mobile Robot Gateway. 
\section[{b) System Architecture}]{b) System Architecture}\par
Figure \hyperref[fig_2]{1} shows the entire architecture of the Mobile Robot Remote Controlled System. The system components run separately on different devices, performing different roles in achieving the overall goal of the system. The components are also loosely coupled to ease upgrade and maintenance without affecting the operation of the other ones. 
\section[{i. Command Hub Design}]{i. Command Hub Design}\par
The Command Hub is at the center of the entire Remote control system for mobile robots. It is one of the three components required to develop the full system as shown in figure  {\ref 2}   The control interface component in the system is the one that interacts with the user and based on the operation performed on it, it will create and send an appropriate HTTP request to the command hub respectively. The control interface performs two basic functions. The first function is to take users' actions and transform them into a valid HTTP request required by the command hub. The second function is getting telemetry data from the command hub to create visual feedback for the users. The structure of this component is therefore organized along with its functions. Two modules are provided, one to constantly fetch new or updated data from the command hub to update the telemetry view of the mobile robot's vitals while the other module handles user interactions with the control interface and makes appropriate HTTP requests to the command hub.\par
Different Control Interfaces are designed based on the two modules explained earlier to expand the choice of control for each Mobile Robot in the system. Available control interface includes:\par
Cross-Platform Mobile Interface: This type of interface is meant for users that prefer to control their Mobile robots from a smartphone. The interface wasdesigned with Apache Cordova, HTML 5, CSS 3, and JavaScript. This ensures that the resulting interface can be used on Windows Phone, Android Phone, and iPhone as well.\par
Web Application Interface: This type of interface is available to users that want to control their Mobile Robots through a web browser. The web browser is used to access Web applications deployed alongside the command hub to provide the control interface. This Control interface is designed with ASP.Net MVC 4, HTML 5, CSS 3, and JavaScript. A variety of web browsers are supported.\par
Desktop Interface: In this type of control interface, the traditional Desktop application is used to provide the interface to the users. C\# programming language is used to develop this interface. 
\section[{iii. Mobile Robot Gateway Design}]{iii. Mobile Robot Gateway Design}\par
This is the component that interfaces directly with the Mobile Robot. It plays a major role in connecting the robot to the remote control interface through the command hub. There are two different types of Mobile Robot Gateway namely, Internal Mobile Robot Gateway and External Mobile Robot Gateway. The internal Mobile Robot Gateway runs locally on the robot's operating system. This type of Gateway is only supported by Mobile Robots capable of running scripts, executable programs and whose hardware supports networking and direct connectivity to the Internet. The Gateway is implemented as part of the required software running locally on the robot's platform. The Gateway runs directly on the Mobile Robot's control board as shown by Robot 2 in figure \hyperref[fig_2]{1}. External Mobile Robot Gateway does not run on the robot platform, it runs on a remote computer connected to the Mobile Robot through Bluetooth or a WIFI device. This type of Gateway is meant for Mobile Robots that do not have shields or devices to directly connect to the Internet thereby using the remote computer's Internet connectivity for its operation. In the case of External Mobile Robot Gateway, a remote computer connected to the Internet is placed within the communication range of the Mobile Robot, the computer shares its internet connection with the Mobile Robot. The Gateway is also executed on the remote computer to serve as the conduit through which communication is established with the control interface via the command hub. Robot 1 in figure 1 makes use of the External Mobile Robot Gateway. 
\section[{Gateway Operation Circle}]{Gateway Operation Circle}\par
The Mobile Robot Gateway operates in a circle of three operations namely Sense/Listen, Think, and Act. Figure \hyperref[fig_5]{4} shows the interaction of Gateway operations in a single circle.\par
? Sense/Listen Operation:-in this operation, the Gateway awaits new commands from the command hub through an active Web Socket if available or through an HTTP request to the REST API exposed by the command hub. If the Mobile Robot is in autonomous or semi-autonomous mode, values from the proximity sensors are fetched by the Gateway. Any data acquired from this operation is then passed on to the THINK operation in the circle. ? Think -analysis of data passed from the Sense/Listen operation is carried out during this operation. It is mainly responsible for command interpretation and conversion into a simpler form that could be handled on the Mobile Robot easily.\par
After the interpretation and conversion task has been carried out, the result is sent to the ACT operation to take necessary action. ? Act: -this part is responsible for generating the control sequence based on the input received from the THINK operation. It determines the destination of the resulting control sequence (i.e. Mobile Robot or Command hub). The control sequence now determines the behavior the Mobile Robot will exhibit. This operation is also responsible for sending telemetry data to the command hub. After this operation is carried out, control is returned to the Sense/Listen operation iv. Command Design One of the roles of the Command Hub is the generation of commands to be sent to the Mobile Robot. These commands are generated based on the interaction of the users with the control Interface. Each action performed by the user on the control interface corresponds to a specific command meant for the Mobile Robot to execute. When an action is performed on the control interface, a request is sent to the REST API (Application Programming Interface) exposed by the Command Hub. The Command Hub now maps the request to the corresponding command to be generated and sent to the Mobile Robot. For example, if the user presses the "Move Forward" Button on the Control Interface, an HTTP POST request is sent to http://Command-Hub-DomainName/api/move/1, then "f" command is generated and sent to the Mobile Robot. The "Command-Hub-DomainName" is the domain name of the server hosting the Command Hub. Table \hyperref[tab_0]{1} shows the comprehensive list of all Uri, HTTP verbs, and associated commands mapped to them. 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
Volume XXI Issue I Version I   At the hardware level, two robots were designed to validate the workability of the remote control system whose architecture was shown in figure \hyperref[fig_2]{1}. These Mobile Robots have different platforms and configurations each of which corresponds to the two types of Mobile Robots in figure \hyperref[fig_2]{1}. The Mobile Robots are: SleekBot V1: This was designed to use Arduino Nano R3 as its main control board. All other actuators and sensors are connected to the main control board. In this configuration, a Bluetooth module is used to communicate with an external Mobile Robot Gateway.\par
Figure \hyperref[fig_6]{6} shows the breadboard schematics of the robot's hardware configuration.\par
SleekBot V2: This is the second Mobile Robot, it was designed to use Raspberry Pi 2 Model B as its main control board while Arduino Nano R3 was used as a slave control board. In this configuration, a USB camera with a two degree of freedom is connected to the mainboard and Internal Mobile Robot Gateway was used because the main control board is capable of running executable programs and it is also capable of connecting to the internet directly. Figure  {\ref 7} shows the breadboard schematics of SleekBot V2.  
\section[{Result and Discussion}]{Result and Discussion} 
\section[{a) System Implementation}]{a) System Implementation}\par
The system was implemented in three stages, each stage corresponds to the deployment of each component that made up the system. For web interface users, the system provides a landing page where navigation to other modules is accessed. Figure \hyperref[fig_7]{8} shows the home page layout.  
\section[{i. Mobile Robot Gateway Stage}]{i. Mobile Robot Gateway Stage}\par
Two types of Mobile Robot Gateway were implemented. The specific implementation used was determined by the robot's ability to connect directly to the internet. In a scenario where the Mobile Robot can connect directly to the internet, a python program was used to implement the Gateway. The second implementation was used when the Mobile Robot connects to the internet through another computer. A desktop application written in C\# was used to implement the Gateway on the computer with internet connectivity. 
\section[{ii. Command Hub Stage}]{ii. Command Hub Stage}\par
At this stage of implementation, a web API written in C\# was used to implement a REST-Based service that acts as the command hub for the system. The service was deployed to Internet Information Service (IIS) with MS SQL Server 2012 to act as the backend storage for the system.  
\section[{User Registration}]{User Registration}\par
This module is used to register all users making use of the control platform. All valid users of the system need to be authenticated before they are granted access to control any mobile robot remotely. Figure  {\ref 9} shows the user registration interface for web interface users while figure \hyperref[fig_9]{10} shows the registration interface for mobile users.  
\section[{User Login}]{User Login}\par
This module is used for authenticating all users making use of the system. All users must pass through this module to use the system. Figure \hyperref[fig_10]{11} and figure \hyperref[fig_2]{12} show the login user interface (UI) for web and mobile users.  
\section[{Main Menu}]{Main Menu}\par
The main menu provides navigation to important modules the user can use to perform different tasks in the system. Figure \hyperref[fig_11]{13} shows the main menu for mobile interface users   
\section[{Mobile Robot Registration}]{Mobile Robot Registration}\par
To make use of any robot on the platform, the user needs to register the robot. Figure \hyperref[fig_12]{14} shows the interface dedicated to the registration. After registration, all registered Mobile Robots by the user is displayed in the Mobile Robot List as shown in figure \hyperref[fig_13]{15}.  
\section[{Settings}]{Settings}\par
The settings module is used to configure the parameters required for the interface to work properly. Figure \hyperref[fig_6]{16} shows a settings Interface for mobile Users 
\section[{Remote Control Interface}]{Remote Control Interface}\par
This interface provides the necessary widget to remotely control mobile robots. Actions performed on this interface translate to a command to be executed on the mobile robot. Figure \hyperref[fig_2]{17} and figure \hyperref[fig_7]{18} show the remote control interface for web and mobile interface users.    
\section[{Conclusion}]{Conclusion}\par
The goal of this research work to develop a portable IP-based multi-interface remote-controlled system for mobile robots was achieved. The system offers the use of a single remote control device across different mobile robots and the use of a multi-interface for a single mobile robot.\par
The solution architecture is based on three loosely coupled components performing various tasks at different levels to collectively achieve a single aim of having a portable control system. At the core of the system is a REST-based web service handling communication between the user interface and the mobile robot. Various programming languages were used at different levels to achieve the overall goal of the system. A cross-platform mobile application, Web application, and the desktop client was developed to serve as the system's user interface. Implementation of the system was carried out on three different mobile robots based on different platforms. The system was evaluated based on the time complexity of the algorithm used in its components. The result shows that the system time of execution is linear (O (n)).\par
The system developed is not without its weakness, hence the need to improve some parts that are currently inefficient in its mode of operation. These include:\par
1 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-3.png}
\caption{\label{fig_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-6.png}
\caption{\label{fig_4}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-7.png}
\caption{\label{fig_5}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{6}\includegraphics[]{image-8.png}
\caption{\label{fig_6}Figure 6 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{8}\includegraphics[]{image-9.png}
\caption{\label{fig_7}Figure 8 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-10.png}
\caption{\label{fig_8}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{10}\includegraphics[]{image-11.png}
\caption{\label{fig_9}Figure 10 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{11}\includegraphics[]{image-12.png}
\caption{\label{fig_10}Figure 11 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{13}\includegraphics[]{image-13.png}
\caption{\label{fig_11}Figure 13 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{14}\includegraphics[]{image-14.png}
\caption{\label{fig_12}Figure 14 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{15}\includegraphics[]{image-15.png}
\caption{\label{fig_13}Figure 15 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1718}\includegraphics[]{image-16.png}
\caption{\label{fig_14}Figure 17 :Figure 18 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-17.png}
\caption{\label{fig_15}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.250188679245283\textwidth}P{0.08018867924528303\textwidth}P{0.07377358490566037\textwidth}P{0.44584905660377355\textwidth}}
URI\tabcellsep HTTP VERB\tabcellsep COMMAND\tabcellsep DESCRIPTION\\
/api/move\tabcellsep GET\tabcellsep W\tabcellsep Get Wheels State\\
/api/move/1\tabcellsep POST\tabcellsep F\tabcellsep Move forward\\
/api/move/2\tabcellsep POST\tabcellsep b\tabcellsep Move Backward\\
/api/move/3\tabcellsep POST\tabcellsep r\tabcellsep Move Right\\
/api/move/4\tabcellsep POST\tabcellsep l\tabcellsep Move Left\\
/api/move/5\tabcellsep POST\tabcellsep s\tabcellsep Stop\\
/api/speed\tabcellsep GET\tabcellsep v\tabcellsep Get Robot Speed\\
/api/speed/value\tabcellsep POST\tabcellsep v,value\tabcellsep Set Robot Speed to value\\
/api/leds\tabcellsep GET\tabcellsep d\tabcellsep Get all LED Status\\
/api/leds/id\tabcellsep GET\tabcellsep d,id\tabcellsep Get the Status of LED id\\
/api/leds/id/status\tabcellsep POST\tabcellsep d,id,status\tabcellsep Set the state of LED id with status\\
/api/servo\tabcellsep GET\tabcellsep c\tabcellsep Get Status of all Servo\\
/api/servo/id\tabcellsep GET\tabcellsep c,id\tabcellsep Get state of Servo id\\
/api/servo/id/pos\tabcellsep POST\tabcellsep c,id,pos\tabcellsep Set the position of Servo id to position\\
/api/motor\tabcellsep GET\tabcellsep m\tabcellsep Get the state of all Motor\\
/api/motor/id\tabcellsep GET\tabcellsep m,id\tabcellsep Get state of motor id\\
/api/motor/id/pwm\tabcellsep POST\tabcellsep m,id,PWM\tabcellsep Set the PWM signal of Motor id\\
/api/prox\tabcellsep GET\tabcellsep p\tabcellsep Get state of all proximity sensor\\
/api/prox/id\tabcellsep GET\tabcellsep p, id\tabcellsep Get state of proximity sensor id\end{longtable} \par
  {\small\itshape [Note: v. Mobile Robot Design and Configuration]} 
\caption{\label{tab_0}Table 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.85\textwidth}}
Raspberry Pi 2 Model B: this is a credit card\\
size computer capable of running a trim-down version of\\
the Linux operating system. It has a quad-core\\
processor with a clock speed of 900 MHz, 1 GB RAM,\\
and 40 GPIO (General-purpose Input Output) pins. This\\
was used with Arduino Nano R3 to develop SleekBot V2\\
Mobile Robot\\
ePuck Mobile Robot: this a differential drive\\
educational mobile robot based on a dsPIC30F6014A\\
microcontroller chip running at 60 MHz clock speed. It\\
has 8 KB RAM, 144 KB flash Memory, 3D\\
accelerometer, VGA camera, 8 infra-red sensors,\\
Bluetooth for wireless communication with a computer,\\
speaker and LED. It was used as one of the Mobile\\
Robots used in testing the workability of the developed\\
remote control system.\\
Software\\
Programming Languages: C, C\#, Python, JavaScript\\
Interface Design: HTML 5, CSS 3, Win form\\
Backend: MS SQL Server 2012\\
Framework: .Net Framework, Apache Cordova, Ionic\\
Framework\\
Web Server: Internet Information Service (IIS) 8\\
ii. User Interface Documentation\\
Home Page\end{longtable} \par
  {\small\itshape [Note: b) Implementation Toolsi.]} 
\caption{\label{tab_1}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{P{0.7689833200953138\textwidth}P{0.08101667990468626\textwidth}}
\multicolumn{2}{l}{Get Command from Command Hub}\\
\multicolumn{2}{l}{If Command != null}\\
\multicolumn{2}{l}{Map command to the Mobile Robot Kinematics}\\
\multicolumn{2}{l}{Execute Command}\\
End If\tabcellsep \\
End While\tabcellsep \\
\multicolumn{2}{l}{While Interrupt NOT available}\\
\multicolumn{2}{l}{Get Mobile Robot Status}\\
\multicolumn{2}{l}{Send Status to Command Hub}\\
End While\tabcellsep \\
\multicolumn{2}{l}{Time Complexity of Mobile Robot Gateway algorithm}\\
Number of Operation\tabcellsep \\
c) System Evaluation\tabcellsep \\
Algorithm for Command Hub\tabcellsep \\
Initialize Command Hub\tabcellsep \\
\multicolumn{2}{l}{While interrupt NOT available}\\
\multicolumn{2}{l}{Get HTTP request from client}\\
\multicolumn{2}{l}{Map request to command controller}\\
\multicolumn{2}{l}{Construct response message}\\
\multicolumn{2}{l}{Return response message}\\
End While\tabcellsep \\
\multicolumn{2}{l}{Time Complexity of Command Hub algorithm}\\
Number of Operation\tabcellsep = 1 + 1 + N(1 + 1 + 1+ 1)\\
\tabcellsep = 2 + N(4)\\
\tabcellsep = 2 + 4N\\
Number of Operation\tabcellsep = 2 + 4N\\
\multicolumn{2}{l}{In Big O notation, the algorithm executes in linear time i.eO(n)}\\
Algorithm for Command Interface\tabcellsep \\
\multicolumn{2}{l}{Initialize Command Interface}\\
While UserAction != null\tabcellsep \\
\multicolumn{2}{l}{Construct command object}\\
\multicolumn{2}{l}{Send command object to Command Hub using HTTP Request}\\
\multicolumn{2}{l}{Get Response for the HTTP Request}\\
\multicolumn{2}{l}{If Response != null}\\
\multicolumn{2}{l}{Process Response}\\
\multicolumn{2}{l}{Update Interface}\\
End If\tabcellsep \\
End While\tabcellsep \\
\multicolumn{2}{l}{While Interrupt NOT available}\\
\multicolumn{2}{l}{Get Status from Command Hub}\\
Update Interface\tabcellsep \\
End While\tabcellsep \\
\multicolumn{2}{l}{Time Complexity of Command Interface algorithm}\\
Number of Operation\tabcellsep = 1 + 1 + N(1 + 1 + 1+ 1 + 1) + N(1 +1)\\
\tabcellsep = 2 + N(5) + N(2)\\
\tabcellsep = 2 + 4N + 2N\\
\multicolumn{2}{l}{Number of Operation = 2 + Mobile Robot Gateway Algorithm}\\
Initialize Gateway\tabcellsep \\
\multicolumn{2}{l}{While new Command IS available}\end{longtable} \par
 
\caption{\label{tab_2}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{} \par 
\begin{longtable}{}
\end{longtable} \par
 
\caption{\label{tab_3}}\end{figure}
 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[). remote controldefinition of remote control in English from the Oxford dictionary Oxford dictionary (2015)]{b26}\label{b26} 	 		‘). remote controldefinition of remote control in English from the Oxford dictionary’.  		 \url{http://www.oxforddictionaries.com/definition/english/remote-control}  	 	 		\textit{Oxford dictionary},  				2015. June 13.  	 
\bibitem[Oboe and Fiorini ()]{b24}\label{b24} 	 		‘A design and control environment for internet-based telerobotics’.  		 			R Oboe 		,  		 			P Fiorini 		.  	 	 		\textit{International Journal of robotics research}  		1998. 17  (4)  p. .  	 
\bibitem[Jose et al. ()]{b16}\label{b16} 	 		‘A Java/Matlab-Based Environment for Remote Control System Laboratories: Illustrated With an Inverted Pendulum’.  		 			S Jose 		,  		 			D Sebastián 		,  		 			P Rafael 		,  		 			M Fernando 		.  	 	 		\textit{IEEE transactions on education}  		2004. 47.  	 
\bibitem[Royakkers and Van-Est ()]{b33}\label{b33} 	 		‘A literature review on new robotics: automation from love to war’.  		 			L Royakkers 		,  		 			R Van-Est 		.  	 	 		\textit{International journal of social robotics}  		2015. 7  (5)  p. .  	 
\bibitem[Lambèr and Rinie ()]{b18}\label{b18} 	 		‘A Literature Review on New Robotics: Automation from Love to War’.  		 			R Lambèr 		,  		 			V E Rinie 		.  	 	 		\textit{International Journal of Social Robotics}  		2015. 2015. p. 295.  	 
\bibitem[Chin et al. (2003)]{b8}\label{b8} 	 		‘A Real-Time Remote Control Architecture Using Mobile Communication’.  		 			E L Chin 		,  		 			L Chih-Ching 		,  		 			H An-Sang 		,  		 			W Chih-Chen 		.  	 	 		\textit{IEEE transactions on instrumentation and measurement}  		2003. August 2003. 52  (4) .  	 
\bibitem[Gates ()]{b11}\label{b11} 	 		‘A robot in every home. The leader of the PC revolution predicts that the next hot field will be robotics’.  		 			B Gates 		.  	 	 		\textit{Sci Am}  		2007. 296 p. .  	 
\bibitem[Pravin and Shalini ()]{b30}\label{b30} 	 		‘Accelerometer Based Hand Gesture Controlled Robot’.  		 			V Pravin 		,  		 			T Shalini 		.  	 	 		\textit{International Journal of Science and Research (IJSR)}  		2013. p. .  	 
\bibitem[Obe and Dumitrache ()]{b23}\label{b23} 	 		‘Adaptive Neuro-Fuzzy Controller with Genetic Training for Mobile Robot Control’.  		 			O O Obe 		,  		 			I Dumitrache 		.  	 	 		\textit{International Journal of Computer Communications and Control}  		2012. 7  (1)  p. .  	 
\bibitem[Posadas et al. ()]{b29}\label{b29} 	 		‘Agent-based distributed architecture for mobile robot control’.  		 			J L Posadas 		,  		 			J L Poza 		,  		 			J E Simo 		,  		 			G Benet 		,  		 			F Blanes 		.  	 	 		\textit{Engineering Applications of Artificial Intelligence}  		2008. 2008. 21 p. .  	 
\bibitem[Alliance for Telecommunications Solutions ATIS ()]{b4}\label{b4} 	 		‘Alliance for Telecommunications Solutions’.  		 \url{http://www.atis.org/tg2k/\textunderscore bot.html}  	 	 		\textit{ATIS}  		2001.  	 	 (Telecom glossary "bot) 
\bibitem[Turkle ()]{b36}\label{b36} 	 		\textit{Alone together. Basic Books},  		 			S Turkle 		.  		2011. New York, Why.  	 
\bibitem[Lung et al. ()]{b19}\label{b19} 	 		‘An Experiment in Internet-Based’.  		 			N Lung 		,  		 			S N Wyatt 		,  		 			L Vincenzo 		.  	 	 		\textit{Proceedings. ICRA'02. IEEE International Conference},  				 (ICRA'02. IEEE International Conference)  		2002. 2002. 2 p. .  	 
\bibitem[James ()]{b15}\label{b15} 	 		\textit{Bringing Portability to the Software Process},  		 			D M James 		.  		1997.  		 			West Virginia University, Dept. of Statistics and Computer Science 		 	 
\bibitem[Ankit et al. (2014)]{b3}\label{b3} 	 		‘Controlling of Remote Robot through mobile phone using DTMF Signal’.  		 			J Ankit 		,  		 			Y Hemant 		,  		 			K Y Raj 		,  		 			S Rajendra 		.  	 	 		\textit{International Journal of Science, Engineering and Technology Research}  		2014. April 2014. 3  (4) .  	 
\bibitem[Dutta and Zielinska ()]{b9}\label{b9} 	 		 			V Dutta 		,  		 			T Zielinska 		.  		 arXiv:1505.07593.  		\textit{Networking technologies for robotic applications},  				2015.  	 	 (arXiv preprint) 
\bibitem[Hockstein et al. ()]{b14}\label{b14} 	 		‘History of robots: from science fiction to surgical robotics’.  		 			N G Hockstein 		,  		 			C G Gourin 		,  		 			R A Faust 		,  		 			D J Terris 		.  	 	 		\textit{Journal of robotic surgery}  		2007. 1  (2)  p. .  	 
\bibitem[Harris ()]{b13}\label{b13} 	 		\textit{How Robots Work. How Stuff Works},  		 			T Harris 		.  		 \url{http://science.howstuffworks.com/robot.htm}  		2007.  	 
\bibitem[Goodrich and Schultz ()]{b12}\label{b12} 	 		‘Humanrobot interaction: a survey’.  		 			M A Goodrich 		,  		 			A C Schultz 		.  	 	 		\textit{Foundations and Trends in Human-Computer Interaction}  		2007. 1  (3)  p. .  	 
\bibitem[Luimula et al. ()]{b20}\label{b20} 	 		‘Improving the Remote Control of a Mobile Robot Using Positioning and Ubiquitous Techniques’.  		 			M Luimula 		,  		 			K Saaskilahti 		,  		 			T Partala 		,  		 			S Pieska 		,  		 			J Alaspaa 		,  		 			A Lof 		.  		 \xref{http://dx.doi.org/10.1109/COASE.2007.4341744}{10.1109/COASE.2007.4341744}.  	 	 		\textit{2007 IEEE International Conference on Automation Science and Engineering},  				 (Scottsdale, AZ)  		2007. 2007. p. .  	 
\bibitem[Robotiq ()]{b32}\label{b32} 	 		\textit{Industrial Robots: 5 Most Popular Applications},  		 			Robotiq 		.  		 \url{http://blog.robotiq.com/bid/52886/Industrial-robots-5-most-popular-applications}  		2014.  	 
\bibitem[Siegwart and Saucy (1999)]{b34}\label{b34} 	 		‘Interacting with mobile robots on the web’.  		 			R Siegwart 		,  		 			P Saucy 		.  	 	 		\textit{IEEE International Conference on Robotics and Automation (ICRA)},  				1999. May.  	 
\bibitem[Bekker ()]{b6}\label{b6} 	 		\textit{Introduction to Terrain Vehicle Systems},  		 			M G Bekker 		.  		1969. Ann Arbor: University of Michigan Press.  	 
\bibitem[Sparrow (2007)]{b35}\label{b35} 	 		‘Killer robots’.  		 			R Sparrow 		.  		 \url{http://www.pantheon.org/articles/t/talos.html}  	 	 		\textit{Talos Encyclopedia Mythica}  		2007. April 29. 2016. 24  (1)  p. .  	 	 (J ApplPhilos) 
\bibitem[Robin ()]{b31}\label{b31} 	 		\textit{Massachusetts Institute of Technology},  		 			R M Robin 		.  		2000.  	 	 (Introduction to AI Robotics) 
\bibitem[Abdullah and Poh (2011)]{b0}\label{b0} 	 		‘Mobile Robot Temperature Sensing Application via Bluetooth’.  		 			M F L Abdullah 		,  		 			L M Poh 		.  	 	 		\textit{International Journal of Smart Home}  		2011. July 2011. 5  (3) .  	 
\bibitem[Oboe and Fiorini ()]{b25}\label{b25} 	 		 			R Oboe 		,  		 			P Fiorini 		.  		\textit{Internet-Based Telerobotics Problems and Approaches: Advanced Robotics, 1997. ICAR '97. Proceedings., 8th International Conference},  				1997.  	 
\bibitem[Bekker ()]{b5}\label{b5} 	 		\textit{Off-The-Road Locomotion},  		 			M G Bekker 		.  		1960. Ann Arbor: University of Michigan Press.  	 
\bibitem[Esteller-Curto et al. ()]{b10}\label{b10} 	 		‘Proposal of a REST-based architecture server to control a robot’.  		 			R Esteller-Curto 		,  		 			E Cervera 		,  		 			A P Del Pobil 		,  		 			R Marin 		.  	 	 		\textit{Innovative Mobile and Internet Services in Ubiquitous Computing (IMIS)},  				2012. 2012. p. .  	 	 (Sixth International Conference) 
\bibitem[Juang and &juang ()]{b17}\label{b17} 	 		‘Remote control of a mobile robot for indoor patrol’.  		 			S Y Juang 		,  		 			J G \&juang 		.  		 \xref{http://dx.doi.org/10.3390/app6030082}{10.3390/app6030082}.  		 \url{https://doi.org/10.3390/app6030082}  	 	 		\textit{Applied Sciences}  		2016. 6  (3)  p. 82.  	 
\bibitem[Polk ()]{b28}\label{b28} 	 		\textit{RoboNexus 2005 robot exhibition virtual tour. Robonexus Exhibition},  		 			I Polk 		.  		 \url{http://www.virtuar.com/click/2005/robonexus/index.htm}  		2005. 2005.  	 
\bibitem[Dictionary ()]{b27}\label{b27} 	 		\textit{Robot -definition of a robot in English from the Oxford dictionary},  		 			Oxford Dictionary 		.  		 \url{http://www.oxforddictionaries.com/definition/english/robot}  		2016.  	 
\bibitem[Nicholas ()]{b22}\label{b22} 	 		\textit{Robots in space},  		 			W Nicholas 		.  		 \url{http://www.universetoday.com/43750/robots-in-space}  		2009.  	 
\bibitem[Lydia et al. ()]{b21}\label{b21} 	 		\textit{TCP/IP Tutorial and Technical Overview. International Technical Support Organization},  		 			P Lydia 		,  		 			T B David 		,  		 			D Chuck 		,  		 			F Jason 		,  		 			L Wei 		,  		 			M Carolyn 		,  		 			R Nicolas 		.  		2006.  	 
\bibitem[Chikurtev et al. ()]{b7}\label{b7} 	 		‘The communication system for remote control of service robots’.  		 			D Chikurtev 		,  		 			I Rangelov 		,  		 			K Yovchev 		,  		 			N \&chivarov 		.  		 \xref{http://dx.doi.org/10.1016/j.ifacol.2019.12.470}{10.1016/j.ifacol.2019.12.470}.  		 \url{https://doi.org/10.1016/j.ifacol.2019.12.470}  	 	 		\textit{IFAC-PapersOnLine}  		2019. 52  (25)  p. .  	 
\bibitem[Wichmann et al. ()]{b37}\label{b37} 	 		‘The integration of mobile (tele) robotics and wireless sensor networks-A survey’.  		 			A Wichmann 		,  		 			B D Okkalioglu 		,  		 			T Korkmaz 		.  	 	 		\textit{Computer Communications}  		2014. 51 p. .  	 
\bibitem[Adamides et al. ()]{b1}\label{b1} 	 		‘User interface considerations for telerobotics: The case of an agricultural robot sprayer’.  		 			G Adamides 		,  		 			C Katsanos 		,  		 			G Christou 		,  		 			M Xenos 		,  		 			G Papadavid 		,  		 			T Hadzilacos 		.  	 	 		\textit{Second International Conference on Remote Sensing and Geoinformation of the Environment (RSCy2014) (pp. 92291W-92291W). International Society for Optics and Photonics},  				2014.  	 
\bibitem[Zunt ()]{b38}\label{b38} 	 		\textit{Who did actually invent the word "robot" and what does it mean? The Karel Capek website},  		 			D Zunt 		.  		 \url{http://capek.misto.cz/english/robot.html}  		2007.  	 
\bibitem[Almali et al. ()]{b2}\label{b2} 	 		‘Wireless remote control of a mobile robot’.  		 			M N Almali 		,  		 			K Gürçam 		,  		 			A Bayram 		.  	 	 		\textit{International Journal of Scientific Research in Information Systems and Engineering}  		2015. IJSRISE.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
