`USOO9774703B2
`
`(12) United States Patent
`(10) Patent No.:
`US 9,774,703 B2
`(45) Date of Patent:
`McNulty
`Sep. 26, 2017
`
`(54) APPARATUS, METHOD AND SYSTEM FOR
`A TUNNELING CLIENT ACCESS POINT
`
`(7]) Applicant: IOENGINE LLC, Norwalk, CT (US)
`
`Inventor: Scott McNulty, Rowayton, CT (US)
`(72)
`(73) Assignee:
`IOENGINE, LLC, Norwalk, CT (US)
`
`( * ) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 86 days.
`
`(56)
`
`(2]) App]. No.: 14/721,540
`
`(22) Filed:
`
`May 25, 2015
`
`(65)
`
`Prior Publication Data
`
`63/0272; H04L 63/0428; H04L 67/04;
`H04L 67/141; H041. 67/42; F1041.
`2209/56; H04L 65/4069; H04L 9/3226;
`H04L 9/3247
`.
`I
`.
`USPC """" 709/203’ 217’ 219’ 220’ 249’ 77111511556
`See application file for complete search history.
`
`References Cited
`US. PAl'lz'N'l' DOCUMENTS
`
`6,928,463 B1 *
`
`6,986,030 B2
`7,051,157 B2
`
`8/2005 Tene .................. H04L 12/2856
`370/356
`
`1/2006 Shinueli et a1.
`5/2006 James
`(Continued)
`
`Us 2015/0334208 A1
`
`Nov, 19, 2015
`
`OTHER PUBLICATIONS
`
`Related US, Application Data
`_
`.
`.
`.
`,
`.
`(63) Continuation 0f application NO‘ 1:3/960’3 14’ filed on
`Aug 6: 2013: HOW Pat N0~ 9:039:969, Whlch IS a
`continuation of application No. 12/950,321, filed on
`NOV. 19, 2010, HOW Pat. NO. 8,539,047, Which is a
`(Continued)
`
`(51)
`
`Int. Cl.
`GO6F 15/16
`G06F 15/177
`H04L 29/06
`H04L 29/08
`
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`
`(200601)
`(200601)
`
`H04L 9/32
`60617 13/00
`(52) U-S- CL
`CPC ~~~~~~~~~~~~ H04L 67/42 (2013-01); H04L 9/3226
`(2013-01)? 1104L 9/3247 (2013-01)? 1104L
`63/0272 (2013-01); H04L 63/0428 (2013-01);
`H04L 65/4069 (201301); H04L 67/04
`(2013-003 H04L 67/141 (2013-01); H04L
`2209/56 (2013-01); H04L 22 09/76 (2013-01);
`H04L 2209/80 (2013.01)
`(58) Field of Classification Search
`CPC ............. H04L 2209/76; H04L 2209/80; H04L
`
`Microsoft Computer Dictionary, Fifth Edition, 2002, pp. 362, 437,
`458. 565. and 572.
`Defendant Interactive Media Corp. d/b/a Kanguru Solutions Initial
`Invalidity Contentions to Plaintiff IOENGINE, dated Jul. 14, 2015,
`255 pages
`Imation’s Initial Invalidity Contentions, dated Jul. 14, 2015, 248
`Pages~
`
`(Continued)
`
`Primary Examiner 7 Alina N Boutah
`(74) Attorney, Agent, or Firm 7 Locke Lord LLP
`
`(57)
`
`ABSTRACT
`
`The disclosure details the implementation of an apparatus,
`method, and system comprising a portable device configured
`to communicate with a terminal and a network server, and
`execute stored program code in response to user interaction
`with an interactive user interface. The portable device con-
`tains stored program code configured to render an interactive
`user interface on a terminal output component to enable the
`user the control processing activity on the portable device
`and access data and programs from the portable device and
`a network server.
`
`129 Claims, 10 Drawing Sheets
`
`
`
`
`
`mm“fl
`113:
`”‘9
`mwwmcw amr:
`mm. front mdi
`120
`l
`
`Q7
`End-0
`PM“ Hum
`127
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US 9,774,703 B2
`Page 2
`
`Related US. Application Data
`
`continuation of application No. 10/807,731, filed on
`Mar. 23, 2004, now Pat. No. 7,861,006.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`OTHER PUBLICATIONS
`Scott Spanbauer, “Mighty Mini Media”, vwwzpcworldcom, May
`2002, pp, 14-17.
`https1//web.archive.org/web/
`Miranda
`Instant Messenger.
`20031228092924/http:/VVW\V.miranda-irn.org, Copyright
`2000-
`2003 Miranda IM, 2 pages
`Miranda Instant Messenger (2), “About Miranda 1M”, https://web.
`archiVeorg/Web/2003 1228092924/http:/Www.miranda-im. org.
`Copyright 2000-2003 Miranda IM, 2 pages.
`Miranda Instant Messenger (3), “Screenshots”, https://Web.archive.
`org/web/2003 1228092924/http:/\va.1niranda-im.org, Copyright
`2000-2003 Miranda 1M, 2 pages.
`Jon L. Jacoby, welcome to M-Systems DiskOnKey Site, httpsz//
`web/archive. org/web/2002 12020 82914/http://www.diskon1<ey.com/
`prodidokasp, 2 pages.
`Jon L. Jacoby, Welcome to M-Systems DiskOnKey Site, “Product
`& Solutions”, https://web/archive.org/web/20021202082914/http://
`wwwdiskonkey.corn/prodidok.asp, 1 page.
`.1011 L. Jacoby, M-Systems flash Disk Pioneers. “Using MyKey”,
`Copyright 2003 M-Systerns Flash Disk Pioneers. Ltd.. 23 pages.
`Expert Report by Vij ay Madiselli, Ph.D.. Ioengme, LLC V. Inter—
`active filedia Corp, CA. No. 14-1571 (D.Del.) and Ioengine, LL C
`v. Imulion Corp. C.A. No. 14-1572 (:D.Del.) Jul. 1. 2016 (141
`pages).
`Rebuttal Expert Report of Dr Kevin Butler Regarding the Validity
`of US. Pat. No. $539,047, Ioengine, LLC V. Interactive iMedia
`Corp, CA. No. 14-1571 (D.De1.) and Ioengine, LLC V. Imatl'on
`Corp, CA. No. 14-1572 (D.Del.) Jul. 22, 2016 (78 pages).
`
`* cited by examiner
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`Terasawa ............ G061: 1/ 1626
`709/203
`
`Elazar ct a1.
`Elazar et a1.
`Friedrich ............. GOSB 19/409
`709/203
`
`King et a1.
`Tcnnison
`
`04 . 12/5692
`709/238
`
`Hill
`
`Rodriguez ..........
`
`Elazar et a1.
`\Vilson ................... G06Q 50/22
`705/2
`Manchester
`........ l 01 2 41/0213
`709/220
`Gregrio
`l~01 2 12/2859
`455/411
`Ciesinger ............ 1* 01 2 63/0428
`713/193
`
`
`Genske et al.
`Borgstrorn ............. G08C 17/02
`345/1.1
`Audebert
`............ 1* 01 2 63/0853
`726/35
`..................... f 04 2 63/0272
`715/751
`
`
`
`
`
`
`
`B2*
`
`B2
`B2
`B2 *
`
`6/2009
`
`7/2011
`1 1/2013
`12/2013
`
`4/2002
`4/2002
`
`5/2002
`6/2002
`
`*
`
`12/2002
`
`3/2003
`
`2/2004
`9/2005
`
`"‘
`
`9/2005
`
`3/2006
`
`2/2007
`
`
`
`AA A
`
`A AA A
`
`7,546,340
`
`7,979,700
`8,595,488
`8,612,511
`2002/0044663
`2002/0046292
`
`2002/0065872
`2002/00 80090
`
`2002/0 194499
`
`2003/0058274
`
`2004/0039932
`2005/0197859
`
`2005/0198221
`
`2006/0052085
`
`2007/0038870
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`779,SU
`
`2B3
`
`0euwan
`
`mM,.Mam.“
`
`1fiat?“guamwfiigfim_w§$3“$3
`
`S331’:‘1-xi;Ex.u.§
`
`
`
`
`
`
`
`
`\3:3“may£3£3
`
`.swvWPWgmgmmmfifiauwwwakax.mawmvwm3§§3mamfimmmmfiELMm.‘.V.3333:33$me333$imEm.”‘
`
`$43$333&3@3333
`..WNW.m3
`
`
`
`wafiufi3%»
`
`xAmQ314%MW§@333$33
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 2 0f 10
`
`US 9,774,703 B2
`
`
`
`fwmgmg I
`Efi§€$§$
`{iiix‘mi'
`Acmss 9am:
`($3?) &
`
`
`
`
`flag in My Account
`
`‘3
`
`mm““"3 2:35
`
`“mmmmwgmm
`
`
`
`awifi- gsifgg fiassfi Tm§m3
`
`{AT} {1% a: mfi§§m§ cwimfiw :
`$34
`
`
`i%3¥¥ 33%; mmw Ywmgrxaé
`m MRS $33? maxi; §r§m
`
`
`-
`
`swvn»:
`Exmuéa an mp 233
`
`
`=
`kmew stwe this gas: mm 5
`angmfsemg: 2%WWW
`
`
`§ Smirémmfs‘tnm 322: EA?
`
`‘
`3%
`
`
`
`» N». »w “I .“m ”mm,“ m m- m- M
`x?
`
`“'1
`
`
`£f§ ‘-
`_
`-. fmma:
`:
`1.3mm: my gag
`
`
`
`. five: at}- flggwfifi _'
`imWWWN2mmm_j
`
`Fig, 2
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 3 0f 10
`
`US 9,774,703 B2
`
`
`
`
`TCAP mm 12:} 33$?
`
`
`{wage T1223.” with Mews
`“fermimi {33, Via ST,
`‘
`
`
`W193, 3338 aka} fifiS
`
`
`
`map Eaadsg‘ficcssgas immafifig
`system if};
`
`
`
`
`m
`C}
`’
`‘
`>1{ifx‘é‘p3;: F
`'v
`
`
`
`$22.;
`{sexessé insiwciiarss k}
`'
`mg3&2
`‘
`,
`WEE summery?
`.
`
`
`
`degmgtaa?axe
`
`
`
` haw engagas
`
`max? mama: t0
`§ssa¢ iaskucfica signais fag
`
`axmuiss £2 YEA? aWWW é:
`dauhls‘wiiwrag mtmnw IMi
`ESQ
`
`
` :
`
`SE” exewiea Eastmztm km
`W mgmory is gmzve‘fie 3333
`
`m ms: mistsw
`
`7w fiafideg mm! Emma is
`‘
`3mm: ¥sm3m3 {A3} 5233
`
`
`
`g} "
`‘
`$25
`
`A? amassasfmms 113% ”$8335?
`mm? 3mm 33-5
`
`
`
`fliwé
`
`Egfiga fmr‘zsiéa
`
`mafia 33$:ml: {TEKP} 3a: Fig, :5
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 4 0f 10
`
`US 9,774,703 B2
`
`
`
`D‘mpiey‘ Em
`yaw»
`"wastage jag“, Mg gt:
`WWW
`g {laminae
`
`Mm tats regtgberrm img'm again}
`E
`gag
`43a
`
`
`
`__
`
`mm: gm- Wage
`
`
`Massage {2.9. W 93-
`mike m Pewter a: min}
`
`m»mm..,~m..m}
`
`
`
`
`
`Use: 883“ 43.9
`
`_
`
`regsuufian Name I‘
`amen fl
`
`
`
`
`
`
`
`
`
`
`
`
`istwad‘?
`
`'
`
`
`$3 am: {
`«$3
`
`
`
`
`
`_
`9mm thimfi {ex},
`mm {fiimmé if he: aniim}fi§$8
`
`T
`simoga) fig
`
`
`
`:3 AT W? fi‘
`
`“figfifigfifiggfi =
`”wag“; EEK-3
`
`I mow, user E} accm‘
`
`“msfsme m:
`
`
`-
`mamma on 1'ng
`~efiw§m$ {533“ Mt} £35
`
`
`
`
`
`:3
`
`
`‘
`£3593” mam -
`
`
`gagiskafiw Newman
`
`
`
`WSW Ermr Vessage
`
`{as},
`iafmnatéen immgsieée,
`Wage rewméer; {fag Mam,
`
`péwsa gamma mm“:
`' mums, fling-fl
`
`
` :.~-----------4%»
`
`rhwwmwwm*MMWMfi
`3z
`i
`
`E
`
`E
`“WWW“,
`
`V“\\.V\_a§§b~im aim?
`3;?"
`
`
`
`Frame ail my epfims
`{ex}. rm pragmm, Mar
`‘0
`Mata, grim Mummix. cm}
`
`486
`
`
`flaw mag to amass,”
`
`@xmutefsficm deteg'
`Wizms an my: and
`93$ {meta mm: {9.9,
`
`MG ‘3.
`.
`
`
`
`
`
`Fig. 4
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 5 0f 10
`
`US 9,774,703 B2
`
`I
`
`Ptease lnstail
`
`W “'3‘
`
`please wait
`Installing,
`
`,
`
`3‘,
`
`$333
`'W3mwwm.
`
`' 5333f}
`“33W...“
`
`
` r
`
`
`
`w §§§§s§¥m~i§
`3$3?.§
`, W23
`3 {A $333,...w 3:
`3W“::,WW “rm 3 Drag&Droll
`VII,
`
`
`‘
`‘v Welcome Scott
`“ti?
`
`s
`{\
`
`533 '
`
`
`
`3; ‘33:?“
`
`I???
`
`'-<:§:€&K“‘W‘f{v3'i
`
`
`
`
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 6 0f 10
`
`US 9,774,703 B2
`
`
`wammxn: W“,
`
`\\\\\\\\\\\\\\\\\\\\\\\u«\“Vs“mww
`WW“;
`$43
`
`
`33mm m
`
` 5r,”/r/l/”a”;x1/zk»r;”7))!7’7);
`
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 7 0f 10
`
`US 9,774,703 B2
`
`k
`
`f
`f{3 m
`Carggm‘fis
`\{fid
`g"
`MT.
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 8 0f 10
`
`US 9,774,703 B2
`
`
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 9 0f 10
`
`US 9,774,703 B2
`
`Cnmgniar S'S‘temiwfiim 5&2
`
`
`
`
`Crygfifigmgfific
`
`
`mmffis} f}
`{mammal-ma;I
`a“gamma}: “5
`‘3 Weizmg Mame»?
`
`
`
`
`
`
` MIKE’S Mamie: i335
`“w“....W
`
`mm {Batubaw $3155
`
`
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US. Patent
`
`Sep. 26, 2017
`
`Sheet 10 of 10
`
`US 9,774,703 B2
`
`
`
`
` z Crwmgmphk: \
`Precwwr immune ;
`
`
`
`
` f;Sammmmfim ‘\
`WW744;
`<\mmm gm;
`gm gQéméngmag
`
`
`Mafia”: fins
`
`
`‘0“ “m“ M _. .m
` w». “M“,
`\
`
`.
`i
`
`
`
`iféefiwork Nefiwag
`, m .
`1w.-‘nmu“ mm\\ »-\\~\\\-.\
`
`2
`
`.‘m ,
`
`
`
`
`
`
`
` if”.$wmmmmzrmijmuwm~w :
`
` *3 Méflé ‘. 8303‘
`
`-
`mm“
`k§§wmmaw¢u§nxmmfifl
`aw me 1%}: M R353
`mmmmmm...
`‘mm. . uwwvx» win
`w
`{Zonvgyy Wamafim‘; m
`
`Luww‘xuwwuw‘\\
`Turimiimg flight M8833 Pam-2 Silk?
`
` im‘. m (5%.. E3323
`
`
`
`WEE
`
`
`wmnzx
`
`3mm
`
`
`Qmmfirg SSyste-m {GSBMWWW:ms “ '
`'
`
`
`Pragramss
`3mm?
`
`Eggs:
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US 9,774,703 B2
`
`1
`APPARATUS, METHOD AND SYSTEM FOR
`A 'I'UNNELING CLIENT ACCESS POINT
`
`This application is a continuation of US. application Ser.
`No. 13/060,514, filed Aug. 6, 2013, which is a continuation
`ofU.S. application Ser. No. 12/950,321, filed Nov. 19, 2010,
`now US. Pat. No. 8,539,047, which is a continuation ofU.S.
`application Ser. No. 10/807,731, filed on Mar. 23, 2003, now
`US Pat. No. 7,861,006.
`
`FIELD
`
`The present invention is directed generally to an appara—
`tus, method, and system of accessing data, and more par-
`ticularly, to an apparatus, method and system to transmit and
`process data comprising a portable device in communication
`with a terminal and a communications network comprising
`a plurality of communications network nodes.
`BACKGROUND
`
`Portable Computing and Storage
`Computing devices have been becoming smaller over
`time. Currently, some of the smallest computing devices are
`in the form of personal digital assistants (PDAs). Such
`devices usually come with a touch screen, an input stylus
`and/or mini keyboard, and battery source. These devices,
`typically, have storage capacities around 64 MB. Examples
`of these devices include Palm’s Palm Pilot.
`Information Technology Systems
`Typically, users, which may be people and/or other sys-
`tems, engage information technology systems (e.g., com—
`monly computers) to facilitate information processing. In
`turn, computers employ processors to process information;
`such processors are often referred to as central processing
`units (CPU). A common form of processor is referred to as
`a microprocessor. A computer operating system, which,
`typically,
`is software executed by CPU on a computer,
`enables and facilitates users to access and operate computer
`information technology and resources, Common resources
`employed in information technology systems include: input
`and output mechanisms through which data may pass into
`and out of a computer; memory storage into which data may
`be saved; and processors by which information may be
`processed. Often information technology systems are used
`to collect data for later retrieval, analysis, and manipulation,
`commonly, which is facilitated through database software.
`lnforrnation technology systems provide interfaces that
`allow users to access and operate various system compo-
`nents.
`User Interface
`The function of computer interfaces in some respects is
`similar to automobile operation interfaces. Automobile
`operation interface elements such as steering wheels, gear—
`shifts, and speedometers facilitate the access, operation, and
`display of automobile resources, functionality, and status.
`Computer interaction interface elements such as check
`boxes, cursors, menus, scrollers, and windows (collectively
`and commonly referred to as widgets) similarly facilitate the
`access, operation, and display of data and computer hard-
`ware and operating system resources,
`functionality, and
`status. Operation interfaces are commonly called user inter-
`faces. Graphical user interfaces (GUIs) such as the Apple
`Macintosh Operating System’s Aqua, Microsoft’s Windows
`XP, or Unix‘s X—Windows provide a baseline and means of
`accessing and displaying information, graphically, to users.
`Networks
`
`10
`
`15
`
`Lu v.
`
`40
`
`u. v.
`
`60
`
`63
`
`2
`to comprise of the
`Networks are commonly thought
`interconnection and interoperation of clients, servers, and
`intermediary nodes in a graph topology. It should be noted
`that the term “server” as used herein refers generally to a
`computer, other device, software, or combination thereof
`that processes and responds to the requests of remote users
`across a communications network. Servers serve their infor-
`mation to requesting “clients.” The term “client” as used
`herein refers generally to a computer, other device, software,
`or combination thereof that is capable of processing and
`making requests and obtaining and processing any responses
`from servers across a communications network. A computer,
`other device, software, or combination thereof that facili-
`tates, processes information and requests, and/or furthers the
`passage of information from a source user to a destination
`user is commonly referred to as a "node.” Networks are
`generally thought to facilitate the transfer of information
`from source points to destinations. A node specifically
`tasked with furthering the passage of information from a
`source to a destination is commonly called a “router.” There
`are many forms of networks such as Local Area Networks
`@ANs), Pico networks, Wide Area Networks (WANs),
`Wireless Networks (WLANs), etc. For example, the Internet
`is generally accepted as being an interconnection of a
`multitude of networks whereby remote clients and servers
`may access and interoperate with one another.
`
`SUMMARY
`
`Although all of the aforementioned portable computing
`systems exist, no effective solution to securely access,
`execute, and process data is available in an extremely
`compact
`form. Currently, PDAs, which are considered
`among the smallest portable computing solution, are bulky,
`provide uncomfortably small user interfaces, and require too
`much power to maintain their data. Current PDA designs are
`complicated and cost a lot because they require great pro-
`cessing resources to provide custom user interfaces and
`operating systems. Further, current PDAs are generally
`limited in the amotmt of data they can store or access. No
`solution exists that allows users to employ traditional large
`user interfaces they are already comfortable with, provides
`greater portability, provides greater memory footprints,
`draws less power, and provides security for data on the
`device. As such, the disclosed tunneling client access point
`(TCAP) is very easy to use; at most it requires the user to
`simply plug the device into any existing and available
`desktop or laptop computer, through which, the TCAP can
`make use of a traditional user interface and input/output
`(I/O) peripherals, while the TCAP itself, otherwise, provides
`storage, execution, and/or processing resources. Thus, the
`TCAP requires no power source to maintain its data and
`allows for a highly portable “thumb” footprint. Also, by
`providing the equivalent of a plug—n—play virtual private
`network (VPN), the TCAP provides certain kinds of access-
`ing of remote data in an easy and secure manner that was
`unavailable in the prior art.
`In accordance with certain aspects of the disclosure, the
`above-identified problems of limited computing devices are
`overcome and a technical advance is achieved in the art of
`portable computing and data access. An exemplary tunnel—
`ing client access point (TCAP) includes a method to dispose
`a portable storage device in communication with a terminal.
`The method includes providing the memory for access on
`the temiinal, executing processing instructions from the
`
`PayPal Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US 9,774,703 B2
`
`3
`memory on the terminal to access the terminal, communi—
`cating through a conduit, and processing the processing
`instructions.
`In accordance with another embodiment, a portable tim-
`neling storage processor is disclosed. The apparatus has a
`memory and a processor disposed in communication with
`the memory, and configured to issue a plurality of processing
`instructions stored in the memory. Also, the apparatus has a
`conduit for external communications disposed in commu-
`nication with the processor, conligured to issue a plurality of
`communication instructions as provided by the processor,
`configured to issue the communication instructions as sig—
`nals to engage in communications with other devices having
`compatible conduits, and configured to receive signals
`issued from the compatible conduits.
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`10
`
`15
`
`
`
`The accompanying drawings illustrate various non-limit-
`ing, example,
`inventive aspects in accordance Willi
`the
`present disclosure:
`:IG. 1 is of a flow diagram illustrating embodiments of a
`tunneling client access point (TCAP);
`:IG. 2 is of a flow diagram illustrating embodiments of a
`system of tunneling client access point and access terminal
`interaction;
`41G. 3 is of a flow diagram illustrating embodiments of
`engaging the tunneling client access point to an access
`terminal interaction;
`3IG. 4 is of a flow diagram illustrating embodiments of “
`accessing the tunneling client access point and server
`through an access terminal;
`jIGS. 5—8 is of a flow diagram illustrating embodiments
`of facilities, programs, and/or services that the tunneling
`client access point and server may provide to the user as
`accessed through an access terminal;
`3IG. 9 is of a block diagram illustrating embodiments of
`a tunneling client access point server controller;
`jIG. 10 is of a block diagram illustrating embodiments of
`a tunneling client access point controller;
`The leading number of each reference number within the
`drawings indicates the first figure in which that reference
`number is introduced. As such, reference number 101 is first
`introduced in FIG. 1. Reference number 201 is first intro—
`duced in FIG. 2, etc.
`
`Lu v.
`
`40
`
`DETAILED DESCRIPTION
`
`Topology
`FIG. 1 illustrates embodiments for a topology between a .
`tunneling client access point (TCAP) (see FIG. 10 for more
`details on the TCAP) and TCAP server (TCAPS) (see FIG.
`9 for more details on the TCAPS). In this embodiment, a
`user 133a may plug—in a TCAP into any number of access
`terminals 127 located anywhere. Access terminals (ATS)
`may be any number of computing devices such as servers,
`workstations, desktop computers, laptops, portable digital
`assistants G’DAs), and/or the like. The type ofAT used is not
`important other than the device should provide a compatible
`mechanism of engagement to the TCAP 130 and provide an
`operating envirormient for the user to engage the TCAP
`through the AT. In one embodiment, the TCAP provides a
`universal serial bus (USB) connector through which it may
`plug into an AT. In other embodiment,
`the TCAP may
`employ Bluetooth, WiFi and/or other wireless connectivity
`protocols to connect with ATs that are also so equipped. In
`one embodiment,
`the AT provides Java and/or Windows
`
`u. v.
`
`60
`
`4
`runtime environments, which allows the TCAP to interact
`with the input/output mechanisms of the AT. See FIG. 9 for
`more details and embodiments on the types of connections
`that may be employed by the TCAP. Once the TCAP has
`engaged with an AT, it can provide the user with access to
`its storage and processing facilities.
`If the AT is connected to a communication network 113,
`the TCAP may then communicate beyond the AT. In one
`embodiment, the TCAP can provide extended storage and/or
`processing resources by engaging servers 110, 115, 120,
`which have access to and can provide extended storage 105
`to the TCAP through the AT. In one embodiment, a single
`server and storage device may provide such TCAP server
`support. In another embodiment, server support is provided
`over a communications network, e.g., the Internet, by an
`array of front-end load-balancing servers 120. These servers
`can provide access to storage facilities within the servers or
`to remote storage 105 across a communications network
`113b,
`C‘ (e.g., a local area network (LAN)). In such an
`embodiment, a backend server 110 may offload the front-end
`server with regard to data access to provide greater through—
`put. For purposes of load balancing and/or redundancy. a
`backup server 115 may be similarly situated to provide for
`access and backup in an eflicient manner.
`In such an
`embodiment, the back-end servers may be connected to the
`front-end servers through a communications network 1131)
`(e.g., wide area network (WAN)). The backend servers 110,
`115 may be connected to the remote storage 105 through a
`communications network 1136 as well (e.g., a high speed
`LAN, fiber-channel, and/or the like).
`Thus, to the user 133a, the contents of the TCAP 130
`appear on the AT as being contained on the TCAP 125 even
`though much of the contents may actually reside on the
`servers 115, 120 and/or the servers’ storage facilities 105. In
`these ways, the TCAP “tunnels” data through an AT. The
`data may be provided through the AT’s l/O for the user to
`observe without it actually residing on the AT. Also, the
`“CAP may tunnel data through an AT across a communi-
`cations network to access remote servers without requiring
`its own more complicated set of peripherals and I/O.
`“CAP and AT Interaction
`FIG. 2 illustrates embodiments for a system of tunneling
`client access point (TCAP) (see FIG. 10 for more details on
`the TCAP) and access terminal interaction. FIG. 2 provides
`an overview for TCAP and AT interaction and subsequent
`figures will provide greater detail on elements of the inter-
`action. In this embodiment, a user engages the TCAP 201.
`For example, the user may plug the TCAP into an AT via the
`ATS USB port. Thereafter the user is presented with a login
`prompt 205 on the ATS display mechanism, e.g., on a video
`monitor. After a user successfully logs in (for example by
`providing a user name and password) 204, the TCAP can
`then accept user inputs from the AT and its peripherals (the
`TCAP can then also provide output to the user via the ATS
`peripherals).
`The user may employ the ATS input peripherals as user
`input devices that control actions 011 the TCAP. Depending
`on the user’s actions 215, the TCAP can be used by the AT
`as a storage device from which it can access and store data
`and programs 225. For example, if the user takes the action
`of opening a file from the TCAP’s memory, e.g., by double
`clicking on an icon when the TCAP is mounted as a USB
`drive on the AT,
`then the AT may treat
`the TCAP as a
`memory device and retrieve information from the TCAP
`225. If the user’s action 215 is one that
`is directed at
`executing on the TCAP 215. then the AT will not be involved
`in any execution. For example, if the user drops an icon
`
`
`
`PayPaI Inc. v. IOENGINE, LLC
`
`|PR2019—00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`US 9,774,703 B2
`
`5
`representing a graphics file onto a drag—and—drop location
`visually representing the TCAP, then the file may be copied
`to the TCAP where it will process and spool the file for
`sending the graphics file to be printed at a remote location.
`In such a case, all of the requirements to process and spool
`the file are handled by the TCAP’s processor and the AT
`would only be used as a mechanism for user input and output
`and as a conduit through which the TCAP may send liles.
`Regardless of if there is an action 215 to execute on the
`TCAP 220 or to access or store data on the TCAP 225, the
`AT is used to display the status of any actions 230. At any
`time the user may select to terminate TCAP related facilities
`executing either 011 the AT, a backend server, on the TCAP
`itself, and/or the like 2.35 In one embodiment, the user may
`select a quit option that is displayed 011 the Al"s screen. In
`another embodiment, the user may simply disengage the
`TCAP from the AT by severing the connection (e.g., turning
`power off, physically pulling the device off the AT, turning
`011' Wireless transmissions, and/or the like). It should be
`noted that such abrupt severing may result in the loss of data,
`file corruption, etc. if the TCAP has not saved data that is on
`the AT or on some remote server. however, if the TCAP is
`employing flash like memory,
`its contents should remain
`intact.
`If there is no instruction signal to terminate the TCAP
`235, execution will continue and the TCAP will continue to
`take and look for input from the USCI'. Of course if the TCAP
`has been set to perform certain actions, those actions will
`continue to execute, and the TCAP may respond to remote
`servers when it is communicating with them through the AT.
`When the user issues a terminate signal 235, then the TCAP
`will shut down by saving any data to the TCAP that is in the
`ATS memory and then terminating any programs executing
`on both the AT and TCAP that were executed by and/or from
`the TCAP 240. If no activities are taking place on the TCAP
`and all the data is written back to thc TCAP 240, then the
`TCAP may optionally umnount itself from the Al’s file-
`system 245, At this point, if there is a TCAP I/O driver
`executing on the AT,
`that driver may be terminated as
`triggered by the absence of the TCAP at a mount point 250.
`Alter the TCAP is unmounted and/or the TCAP I/O driver is
`terminated, it is safe to disengage the TCAP from the AT.
`TCAP and AT Interaction
`FIG. 3 illustrates embodiments engaging the tunneling
`client access point
`to an access terminal
`interaction.
`Examples of engaging the TCAP 301 with an AT were
`discussed abovein FIG 1 127, 130,133a and FIG 2 201
`11 one embodiment, the TCAP 130 is engaged with an
`access terminal 327, 305 As mentionedin FIG 1, the TCAP
`
` is capable of engaging with ATs using a number of mecha-
`
`nisms In one embodiment, the TCAP has a USB c01mector
`'or plugging into an AT, which acts as a conduit for power
`and data transfer. In another embodiment. the TCAP may
`use Bluetooth to establish a wireless connection with a
`number of ATS. In another embodiment.
`the TCAP may
`employ WiFi. In yet another embodiment, the TCAP may
`employ multiple communications mechanisms. It should be
`noted, with some wireless mechanisms like Bluetooth and
`WiFi. simply coming into proximity with an AT that is
`configured for such wireless communication may result in
`the TCAP engaging with and establish a communications
`link with the AT.
`In one embodiment,
`the TCAP has a
`“connect” button that will allow such otherwise automati—
`cally engaging interactions take place only if the “connect”
`button is engaged by a user. Such an implementation may
`provide greater security for users (see FIG. 10 for more
`details on the TCAP).
`
`6
`After being engaged 305, the TCAP will then power on.
`In an embodiment requiring a direct connection, e. g., USB,
`simply plugging the TCAP into the AT provides power. In a
`wireless embodiment,
`the TCAP may be on in a lower
`powered state or otherwise turned on by engaging the
`connect button as discussed above. In such an embodiment,
`the TCAP can employ various on-board power sources (see
`FIG. 10 for more details on the TCAP). The TCAP then may
`load its own operating system 315. The operating system can
`provide for interaction with the AT. In one embodiment, a
`Java runtime is executed on the TCAP, and Java applets
`communicate with the AT through Java APIs. In another
`embodiment, a driver is loaded onto the AT, and the on-
`TCAP Java operating system applets communicate to and
`through the AT via the driver running 011 the AT, wherein the
`driver provides anAPI through and to which messages may
`be sent.
`After engaging with the AT, the TCAP can provide its
`memory space to the AT 320. In one embodiment,
`the
`TCAP’s memory is mapped and mounted as a virtual disk
`drive 125 storage 325. In this manner, the TCAP may be
`accessed and manipulated as a standard storage device
`through the ATS operating system. Further, the TCAP and
`in some cases the AT can determine if the AT is capable of
`accessing program instructions
`stored in the TCAP’s
`memory 330. In one embodiment, the ATS operating system
`looks to auto-run a specified file from any drive as it mounts.
`In such an embodiment, the TCAP’s primary interface may
`be specified in such a boot sequence. For example, under
`windows, an autorun.inl' lile can specify the opening of a
`program from the
`TCAP
`by
`the
`AT;
`e.g.,
`OPEN:TCAP.EXE.
`Many operating systems are capable of at least accessing
`the TCAP as a USB memory drive 3.30 and mounting its
`contents as a drive, which usually becomes accessible in file
`browsing window 125. If the TCAP does not mount, the
`AT’s operating system will usually generate an error inform-
`ing the USCI' of a mounting problem, If the AT is not capable
`of executing instruction from the TCAP, a determination is
`made if an appropriate driver is loaded on the AT to access
`the TCAP 335. In one embodiment, the TCAP can check to
`see if an API is running on the AT. For example, the TCAP
`provide an executable to be launched, e.g., as specified
`through autoruninf, and can establish communications
`through its connection to the AT, e.g., employing TCP/IP
`communications over the USB port. In such an embodiment,
`the TCAP can ping the AT for the program, and if an
`acknowledgement is received, the TCAP has determined
`that proper drivers and APIs exist. If no such API exists, the
`TCAP may launch a driver installation program for the AT
`as through an autoruninf, In an alternative embodiment, if
`nothing happens, a user may double click onto an installer
`program that is stored on the mounted TCAP 342, 340. It
`should be noted, that although the TCAP‘s memory space
`may be mounted, certain areas of the TCAP may be inac-
`cessible until there is an authorization. For example, certain
`areas and content 011 the TCAP may be encrypted. It should
`be noted that any such access terminal modules that drive AT
`and TCAP interaction may be saved onto the TCAP by
`copying the module to a mounted TCAP, Nevertheless, if the
`AT is capable of accessing program instructions in TCAP
`memory 330, a TCAP driver is loaded on the AT 335, and/or
`the user engages a program in the TCAP memory 340, then
`the AT can execute program instructions from the TCAP’s
`memory, which allows the TCAP to use the ATS I/O and
`allowing the user to interface with TCAP facilities 345. It
`should be noted that some ATs may not be able to mount the
`
`10
`
`15
`
`Lu v.
`
`40
`
`.
`
`u. v.
`
`60
`
`Pa