\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={Secure Cloud Architecture for Preserving Privacy in Cloud Computing using OTP/WTP},
 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{2013-05-15 (revised: 15 May 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-05-15}
\title{Secure Cloud Architecture for Preserving Privacy in Cloud Computing using OTP/WTP}
\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]{Sandeep  Sharma}

             \author[2]{Navdeep Kaur  Khiva}

             \affil[1]{  Pune University}

\renewcommand\Authands{ and }

\date{\small \em Received: 8 April 2013 Accepted: 4 May 2013 Published: 15 May 2013}

\maketitle


\begin{abstract}
        


The main objective of the proposed architecture is preserving the privacy of the information ensuring that this information cannot be misused. In this paper we have proposed secure cloud architecture to address the user privacy problem in a cloud. By using OTP and WTP in cloud computing system, our proposed architecture achieves better goal of preserving the privacy of a user.

\end{abstract}


\keywords{}

\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*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
loud computing is an On-demand self-service Internet infrastructure where a customer can pay and use only what is needed, managed by an API. The SP plays an active role in transmitting information across the cloud. Privacy for the information through authentication is being considered important. \hyperref[b5]{[5]} People can only enjoy the full benefits of Cloud computing if there can address the very real privacy and security concerns that come along with storing sensitive personal information in databases and software scattered around the Internet. There are many service provider in the internet, can call each service as a cloud, each cloud service will exchange data with other cloud, so when the data is exchanged between the clouds, there exist the problem of disclosure of privacy. So the privacy disclosure problem about individual or company is inevitably exposed when releasing or sharing data in the cloud service. Privacy is an important issue for cloud computing, both in terms of legal compliance and user trust, and needs to be considered at every phase of design. \hyperref[b6]{[6]} Privacy means that the person to be free from all interference. Privacy control allows the person to maintain a degree of intimacy. \hyperref[b1]{[2]} Privacy is the protection for the truthful use of personal information of cloud user. Privacy breaches may create a lot of troubles to cloud users.\par
As more and more sensitive data are shared and stored in the cloud, data security and privacy have been considered as a thorniest problem that may impede the growth of cloud computing. Since all the resources are provided over the Internet, the cloud becomes a single point of access for all the users. The different scenarios are: Authors ? ? : Dept of CSE, GNDU, GT Rd, Off NH1, Amritsar(PB)-143005, India. E-mails : sandeep\textunderscore gndu@yahoo.com, navdeep07khiva@gmail.com a) From the perspective of Individuals connecting to the cloud: \hyperref[b4]{[4]} Maximizing individual user control, creating anonymous services for individual users, creating facilities for the use of multiple identities and limiting identity information and authentication to high level transactions are the privacy issues which have to be guaranteed for an individual to feel that the privacy of information submitted to the cloud is ensured. b) From the perspective of Cloud computing service providers: \hyperref[b4]{[4]} Providing facilities for maintaining anonymity of personal information, encryption of data if it contains personal information, compartmentalizing data processing and storage, controlling unique identifiers, managing explicitly the privacy and security requirements between the cloud service providers are the major privacy issues from the point of view of the cloud service provider. 
\section[{II.}]{II.} 
\section[{Earlier Approach}]{Earlier Approach}\par
The user might give his/her identity of proof certificate \hyperref[b0]{[1]} willingly to a person of his/her trust.\par
? There might be a case where there is a breach of trust. Hence your secure key lies in the unauthorized person. ? There might be a case where proof of identity is stolen.\par
In both the cases, the IOP is in the unauthorized person and there might be a case of illegal intrusion.\par
If IOP certificate is with the unauthorized person, it could be misused to any extent which may prove to be harmful. The personal information and data is now available to the intruder and could be accessed at his/her wish. This information or data could be used in an unethical manner which might harm the credibility of the user.\par
A careful analysis of literature on the variants and methodologies of privacy preserving in cloud computing reveals the following: Some of the variants of privacy problem are yet to be explored. It includes the problems of misuse of the proof of identity (POI) certificate if fallen into unauthorized person. So this leads us to draft out a scheme or method so that if POI certificate is with unauthorized person, he/she cannot take advantage of it by making some changes to sign in process.  
\section[{Year}]{Year}\par
In a cloud network, once the user has finished with the sign up process, he/she is provided with the POI certificate using which he/she could sign in and access the information as required. But here arises a problem that what would happen if this POI certificate falls in wrong hands. So here comes an objective to make the sign in process secure enough to prevent an intrusion and keeping the sign in process simple enough to the user as per his/her need. 
\section[{III.}]{III.} 
\section[{Proposed Architecture}]{Proposed Architecture}\par
The architecture consists of four main components: the third party website, the cloud Service Provider, the User, and the third party database. ? A non frequent user uses OTP (one time password) and always gets the new password for each access and hence providing security with each access. ? A frequent user go for WTP(weekly time password) so that the user need not change the password on each access rather weekly. The user sign up process starts with user sign up interface where the user enters its personal and protected information. This information moves for verification to the user database. Once verified, the user proceeds to deciding the type of usability and accordingly the security whether it's an OTP or WTP. The users make their choice depending upon their frequency of sign in and whether to go for OTP or WTP. Once the choice has been made, an OTP/WTP database is updated and their respective OTP/WTP is conveyed securely via E-mail. This password can be used by user to sign in. 
\section[{b) User Accessing Cloud Services}]{b) User Accessing Cloud Services}\par
To access cloud services the users sign in using digital signature or by using OTP/WTP. Request is generated to cloud regarding the access. The CSPs accepts the requests and verifies the certificate and OTP/WTP from user database and proceeds. Any discrepancy regarding the mismatch of certificate and OTP/WTP, user again needs to provide the sign in information. Once OTP/WTP is verified, they check its validity. If OTP/WTP is valid and if the user is authenticated and then an ok signal is sent to the third party service which allow user to use the service. If authentication fails, a new OTP/WTP is generated and sent to the user through e-mail and mobile, and again make a request to access the CSPs. A one-time password (OTP) is a password that is valid for only one login session or transaction. OTPs avoid a number of shortcomings that are associated with traditional (static) passwords. The most important shortcoming that is addressed by OTPs is that, in contrast to static passwords, they are not vulnerable to replay attacks. This means that a potential intruder who manages to record an OTP that was already used to log into a service or to conduct a transaction will not be able to abuse it, since it will be no longer valid. On the downside, OTPs are difficult for human beings to memorize. Therefore they require additional technology to work. 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology} 
\section[{c) Hospital Management System}]{c) Hospital Management System}\par
In this scenario, two sites are built: one is Medical Health Service/National Health Service (MHS/NHS) and another is the Laboratory Service (LS).\par
The actual scenario and its working is explained below: 1. First of all, the patients go to meet the doctor for the treatment. Doctor checks them and asks for some tests which are done by the Laboratory.\par
3. Admin logs in and adds the personal information of the patient into the database given by the patient and sends the NHSId to their respective e-mail. 4. Then an employee of the laboratory logs in and adds the patient's tests report into the database of LS. After that an employee of laboratory gives the PatientId (PId) to the patient.  An OTP (one-time password) is a password that is valid for only one login session or transaction. \hyperref[b5]{[5]} WTP (weekly-time password) is a password valid for a week.\par
A non frequent user uses OTP and always gets the new password for each access and hence providing security with each access.\par
Frequent users go for WTP so that the user need not change the password on each access rather weekly. 6. Patient logs in to the LS by entering the NHSId, PId and password and gets the test reports.\par
IV. 
\section[{Experimental Results}]{Experimental Results}\par
To test this architecture we have built a National Health Service cloud with secure authentication.\par
As the admin logs in, he will create the clients account and enter his details which were given by the patient and then patient gets the National Health Service Id (NHSId) on their respective e-mail.\par
The employee of the laboratory then logs into the laboratory service (LS). He will enter the test results of the patient and give one ID of the LS as PatientId (PId) to the patient.\par
Patient will log in to the National Health Service to generate their type of usability i.e. OTP or WTP. After getting the NHSId, PatientId and the password which was send on mail can logs into the LS and see the test reports.\par
V. 
\section[{Conclusion and Future Work}]{Conclusion and Future Work}\par
Data privacy is one of the biggest challenges in Cloud Computing. By the introduction of the OTP/ WTP password protection schemes, the privacy of the user will now be assured to a great extent. The OTP provides a user new password each time and WTP provides the task for a frequent user to use OTP so he/she would opt for WTP.\par
In future, this proposed model could be used to get the secure cloud computing environment which would be a great enhancement in the privacy preservation.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_1}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_2}Figure 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_3}VolumeB}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-5.png}
\caption{\label{fig_4}Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-6.png}
\caption{\label{fig_5}5 .}\end{figure}
   			\footnote{© 2013 Global Journals Inc. (US)} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Wang and Baochun]{b1}\label{b1} 	 		\textit{},  		 			B Wang 		,  		 			Baochun 		.  		 	 
\bibitem[Wang et al.]{b6}\label{b6} 	 		\textit{},  		 			W 		,  		 			Jian; Y Wang 		,  		 			; J Shuo 		,  		 			Jiajin Le 		.  		 	 
\bibitem[Wikipedia-One-Time_Password]{b8}\label{b8} 	 		\textit{},  		 			Wikipedia-One-Time\textunderscore Password 		.  		 	 
\bibitem[Yassin et al. ()]{b3}\label{b3} 	 		‘A Practical Privacy-preserving Password Authentication Scheme for Cloud Computing’.  		 			A A Yassin 		,  		 			H Jin 		,  		 			A Ibrahim 		,  		 			W Qiang 		,  		 			D Zou 		.  		 \xref{http://dx.doi.org/10.1109/IPDPSW.2012.148}{10.1109/IPDPSW.2012.148}.  	 	 		\textit{IEEE 26th International Parallel and Distributed Processing Symposium Workshops \& PhD Forum},  				2012. 2012. IEEE.  	 
\bibitem[Wang ()]{b2}\label{b2} 	 		‘Oruta: Privacy-Preserving Public Auditing for Shared Data in the Cloud’.  		 			H L Wang 		.  		 10.1109/ CLOUD.2012.46.  	 	 		\textit{IEEE Fifth International Conference on Cloud Computing},  				2012. 2012. IEEE.  	 
\bibitem[Syed ()]{b4}\label{b4} 	 		‘PccP: A Model for Preserving Cloud Computing Privacy’.  		 			M R Syed 		,  		 			F 		,  		 			Mohammad 		.  	 	 		\textit{2012 International Conference on Data Science \& Engineering (ICDSE)},  				2012. IEEE.  	 
\bibitem[Jayalatchumy et al. ()]{b5}\label{b5} 	 		‘Preserving Privacy through Data Control in a Cloud Computing Architecture using Discretion Algorithm’.  		 			D Jayalatchumy 		,  		 			D Ramkumar 		,  		 			Kadhirvelu 		.  		 \xref{http://dx.doi.org/10.1109/ICETET.2010.103}{10.1109/ICETET.2010.103}.  	 	 		\textit{Third International Conference on Emerging Trends in Engineering and Technology},  				2010.  	 
\bibitem[Bertino et al. ()]{b0}\label{b0} 	 		‘Privacypreserving Digital Identity Management for Cloud Computing’.  		 			E Bertino 		,  		 			F Paci 		,  		 			R Ferrini 		.  	 	 		\textit{IEEE Computer Society Technical Committee on Data Engineering}  		2009.  	 
\bibitem[Providing Privacy Preserving in cloud computing IEEE ()]{b7}\label{b7} 	 		‘Providing Privacy Preserving in cloud computing’.  	 	 		\textit{IEEE}  		2009. 2009. 2009.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
