throbber

`
`
`
`3B2
`
`US00977470
`
`a2) United States Patent
`US 9,774,703 B2
`(10) Patent No.:
`MeNulty Sep. 26, 2017
`
`(45) Date of Patent:
`
`(54)
`
`APPARATUS, METHOD AND SYSTEM FOR
`A TUNNELING CLIENT ACCESS POINT
`
`(71)
`
`Applicant: IOENGINE LLC, Norwalk, CT (US)
`
`(72)
`
`Inventor: Scott MeNulty, Rowayton, CT (US)
`
`(73)
`
`Assignee:
`
`IOENGINE, LLC, Norwalk, CT (US)
`
`C*)
`
`Notice:
`
`Subject to anydisclaimer, the termofthis
`patent is extended or adjusted under 35
`US.C. 154(b) by 86 days.
`
`(21)
`
`Appl. No.: 14/721,540
`
`(22)
`
`Filed:
`
`May 26, 2015
`Prior Publication Data
`
`(65)
`
`(63)
`
`(51)
`
`(52)
`
`(58)
`
`US 2015/0334208 Al
`
`Nov. 19, 2015
`
`Related U.S. Application Data
`
`Continuation of application No. 13/960,514, filed on
`Aug. 6, 2013, now Pat. No. 9,059,969, which is a
`continuation of application No. 12/950,321, filed on
`Nov. 19, 2010, now Pat. No. 8,539,047, which is a
`(Continued)
`
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`(2006.01)
`
`TInt. CL.
`GU6F15/16
`GO6F 15/177
`HO4L 29/06
`HO4L 29/08
`HO4L 9/32
`GO6l’ 13/00
`US. CL.
`CPC vices HO4L 67/42 (2013.01); HO4L 9/3226
`(2013.01); HO4E 9/3247 (2013.01); HO4L
`63/0272 (2013.01); HO4E. 63/0428 (2013.01);
`HOAL 65/4069 (2013.01); HO4L 67/04
`(2013.01); HO4L 67/141 (2013.01); HO4L
`2209/56 (2013.01); HO4L 2209/76 (2013.01);
`HOAL 2209/80 (2013.01)
`Field of Classification Search
`CPC veiceeeneeee HO4L 2209/76; HO4L 2209/80; HO4L
`
`63/0272; HO4L 63/0428; HO4L 67/04;
`HO4T, 67/141; HO4T. 67/42; HOA4T,
`2209/56; HO4L 65/4069; HO4L 9/3226;
`HO04L 9/3247
`USPC 0... 709/203, 217, 219, 220, 249; 711/115;
`713/150
`See application file for complete search history.
`
`References Cited
`
`U.S. PALEN'T DOCUMENTS
`
`6,928,463 B1*
`
`6,986,030 B2
`7,051,157 B2
`
`8/2005 Tene wee HO4L 12/2856
`370/356
`1/2006 Shmueli et al.
`§/2006 James
`
`(Continued)
`
`OTITER PUBLICATIONS
`
`Microsoft Computer Dictionary, Fifth Fdition, 2002, pp. 362, 437,
`458, 565, and 572,
`DefendantInteractive Media Corp. d/b/a Kanguru SolutionsInitial
`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 — Alina N Boutah
`(74) Attorney, Agent, or Firm — Locke Lord LLP
`
`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.
`execule 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
`
`
`
`
`
`
`
`Fdrive backend
`it
`Redundancy server
`
`120
`
`hy ea
`
`it
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`7,546,340
`
`B2*
`
`6/2009
`
`7,979,700
`8,595,488
`8,612,511
`2002/0044663
`2002/0046292
`
`2002/0065872
`2002/0080090
`
`2002/0194499
`
`2003/0058274
`
`2004/0039932
`2005/0197859
`
`2005/0198221
`
`2006/0052085
`
`2007/0038870
`
`B2
`B2
`B2*
`
`>>-PFPP
`
`>
`
`7/2011
`11/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
`
`Terasawa .........0.. GO6F 1/1626
`709/203
`
`Elazar ctal.
`Elazar etal.
`Friedrich ......... GO05B 19/409
`709/203
`
`Kinget al.
`Tennison ...
`
`
`
`O4T, 12/5692
`709/238
`
`Genske etal.
`Borgstom ow... GO8C 17/02
`345/11
`Audebert ........ HO04L 63/0853
`726/35
`Hillee HO4L 63/0272
`715/751
`
`Llazar et al.
`Wilson wien G06Q 50/22
`705/2
`Manchester
`........ HO4L 41/0213
`709/220
`Gregrio
`Rodriguez ......... HO4L 12/2859
`455/411
`Clesinger ... HO4L 63/0428
`713/193
`
`
`
`US 9,774,703 B2
`Page 2
`
`Related U.S. 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”, www.peworld.com, May
`2002, pp. 14-17.
`Miranda
`Instant Messenger.
`https://web.archive.org/web/
`2003 1228092924/http:/www.miranda-im.org,
`Copyright
`2000-
`2003 Miranda IM, 2 pages
`Miranda Instant Messenger(2), “About Miranda IM”, https://web.
`archive.org/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:Wwww.miranda-im.org, Copyright
`2000-2003 Miranda IM,2 pages.
`Jon L. Jacoby, Welcome to M-Systems DiskOnKeySite, https://
`web/archive.org/web/2002 12020829 1 4/http://www.diskonkey.com/
`prod_dok.asp, 2 pages.
`Jon L. Jacoby, Welcome to M-Systems DiskOnKey Site, “Product
`& Solutions”, https://web/archive.org/web/2002 12020829 14/http://
`www.diskonkey.com/prod_dok.asp, 1 page.
`Jon L. Jacoby, M-Systems Flash Disk Pioneers, “Using MyKey”,
`Copyright 2003 M-Systems Flash Disk Pioneers, Ltd., 23 pages.
`Expert Report by Vijay Madiselli, Ph.D., Joengine, LLC v. Inter-
`active Media Corp., C.A. No. 14-1571 (D.Del.) and. Joengine, LLC
`v. Imation Corp., C.A. No. 14-1572 (D.Del.) Jul. 1, 2016 (141
`pages).
`Rebuttal Expert Report of Dr. Kevin Butler Regarding the Validity
`of U.S. Pat. No. 8,539,047, loengine, LLC v, Interactive Media
`Corp., C.A. No. 14-1571 (D.Del.) and foengine, LLC v. Imation
`Corp., C.A. No. 14-1572 (D.Del.) Jul. 22, 2016 (78 pages).
`
`* cited by examiner
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 1 of 10
`
`US 9,774,703 B2
`
`
`
`
`
` BALUpAi0S=TieTiONonAOEiarBOROMUNUODmyoAUOTDOAUNGAUOS[UOTOOUnLLO|
`
`
`
`S1GAIBSPSSUDIN—~pocriYUOs]
`
`
`
`BASTBALD
`
`£61Sth
`
`|By
`
`|O21
`
`
`
`PUROBAUD
`
`
`
`JehuesAgunpunpey
`
`
`
`PeNey?SoePUSHINGBALip4
`
`
`
`Ona)Sbos01S
`
`SOL
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`
`
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 2 of 10
`
`US 9,774,703 B2
`
`Engage Tunneling \
`
`Chent Aceess Paint
`
`|
`
`c=208
`i
`enna
`
`—
`|
`
`~ Logie using Access Terminal
`
`TCAP Takes User Input from
`
`(ICAP) 201
`
` “Log in My Account
`Login using Access Terminal
`{AT} as a periphero! controller
`
`
`204
`
`
`ss/sterdeta, 200
`
`
`
`| Access/store data programe |
`
`
`240
`| Shutdown/store on TCAP
`<< Terminate? 235
`
`
`_ {TerminateTCAP1/0\
`Unmount TCAP 245
`\ driver on AT 250]
`Be ner sere nee canes ane “ene ee er
`
`Fig. 2
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 3 of 10
`
`US 9,774,703 B2
`
`
`
`
`Engege TCAP wilh Access
`Jerninat (e.g, vie BY,
`
`
`WA, US8, ete.) 205
`
`
`CAP powers up 310
`
`YOAP loads/eccesses aperating
`aystem 315
`
`PTCAP provides memary space to
`|
`Access Tarmuinal
`(AT) 320
`
`
`
`
`
`
`
`
`
`"capotQS°
`HOMESiOetonein
`~
`
`
`at342
`“Ae,
`Rye .
`
`despiteeve
`
`User engages Tae memory fo
`
`issue instruction signals {e4.,
`
`axasules @ ICAP application &
`doubla~clicking mounted TAPS
`340
`
`
`
`|
`AY executes inetructions from
`
`CAP marory fo provide [0
`|e Baint
`(TEAR) 304
`agage Tunneling Chant
`for TRAP a8,
`
`AT eecesses/mounts the TOAP
`meresy space 325
`
`
`
`
`
`Execution
`388
`
`
`Fig. 3
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`| | | | | | | | | | | | | | | | | | | | | | |
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 4 of 10
`
`US 9,774,703 B2
`
` Display Emar
`
`
`
`flaploy Ervor Message
`
`
`Mexsage (2.9. plaose on
`
`Message [e.g.. please go
`oniing ts Fegisteyor login again}
`online te register or login}
`435
`
`
`
`registration welcame
`}
`screen 409
`
`
`sarcaeseoteroecovetvaneted
`
`,
`
`
`
`
`
`{_-
`
`i
`'
`User Provides
`
`: Ragistration.information i
`
`Bevereeseeaneae
`
`Se a aet
`poe ne ee
`;
`Synekwonize 475
`Bae ne eens pee ne men an nae
`
` _
`
`
`
`Olseley Eeror Hessage
`
`Provide Options (e.g,
`
`
`{o.g.,
`information incomplete,
`anine (dimmed Wf not online}/US8
`
`
`pisase re-enter; User adets,
`
`as
`atorage} 453
`
`
`
`please shaase different
`
`RAH, ear.AQ
`
`aa ~
`<<”Syrcteine on and
`“wo affefine storage? oe
`
`a ANa
`
`
`
`
`i Provide TRAP offing |
`ICAP options
`Provide all
`| opens feg.. run
`fag. ran program, order
`program} 460
`
`
`
`grink, grint documents, ate.)
` ‘Afow user S “ef - Alow unex fo ascass/
`
`
`
`execute/store data
`
`
`grams on TAI
`\off-iine {a.g., decryet) 468
`
`
`
`axccute/store date/
`programs co TOA and
`at remote server (2.9,
`deerypt) 485
`
`Fig. 4
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 5 of 10
`
`US 9,774,703 B2
`
`
`
`
` 5 Sn
`“T
`
`ENS)
`.
`a
`tieSAtaling " #
`;i
`please wait
`
`Please install
`
`x
`
`:
`ee
`—
`SGOT 05 OS)
`(ee eee
`ee
`aa
`Se
`Lubes] * ‘a
`Drag & Drop
`; 580
`
`
`
`
`2ES cESi
`
`' ‘
`
`
` S.
`s Neo
`|
`SERN ENA oh Butter WEF
`S (ee‘
`:
`_
`Y st
`eed OS
`cme
`fad si
`
`
`
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 6 of 10
`
`US 9,774,703 B2
`
`desktoptool
`849
`SERRA
`ain
`Kommol
`SeenREO
`
`
`
`
`
`
`
`5O8b hsRee
`PODPPEPOPUPOTOOODPD abeLoanpestitteiS
`
`
`
`
`whe
`
`DOP
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 7 of 10
`
`me
`
`NSfe
`“ay
`contd,
`\
`rporate
`
`US 9,774,703 B2
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 8 of 10
`
`
`
`US 9,774,703 B2
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 9 of 10
`
`US 9,774,703 B2
`
` e Device
`
`
`i Crentograntic
`“<‘SerigheralSS
`
`
`
`i Progessar Interfaes
`“~ Pees)
`
`
` input Sutput mr
`
`interface (1/0)
`
`
`gop
`Netwark ats2 |
`erasers _“OperatingSystem(O53 Hod is18
`
`:fa
`
`PAS
`
`ChantisHy/AL
`Us
`833
`wacerts)§a
`
`
`Comemanication
`
`
`
`
` FCAPSModute 335
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`U.S. Patent
`
`Sep. 26, 2017
`
`Sheet 10 of 10
`
`US 9,774,703 B2
`
`computer Systemization 1002
`
`cCommunicates
`Network 1Q13/
`a
`-Y
`
`Oryptagraghic
`{Processor Iterfare |)
`
`interface Bue
`100?
`
`poveeeteeennnn |
`‘Network interface:
`::5ae
`140
`LeAAERWRRY weee
`
`;
`
`Storage interface
`Gog
`
`tevetceste
`
`writes|:;
`
`“Operating Gystem (08) Module HS
`
`Soeeenmmcnnne
`
`eetecneces
`
`3 SEE aror
`Bef Shan satsetaesatam astans anise!
`Swner Proto10601)"
`"Ark 1082
`" “RonveyInfinformotisn1888
`mn mene
`sat
`FunnsliJing Client doueas Point Pee
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-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 TUNNELING CLIENT ACCESS POINT
`
`This application is a continuation of U.S. application Ser.
`No. 13/960,514, filed Aug. 6, 2013, which is a continuation
`of U.S. application Ser. No. 12/950,321, filed Nov. 19, 2010,
`now U.S. Pat. No. 8,539,047, which is a continuation of U.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 systemto transmit and
`process data comprising a portable device in communication
`with a terminal and a communications nctwork 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 andfacilitates 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; memorystorage 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.
`Information technology systems provide interfaces that
`allow uscrs to access and operate various system compo-
`hents.
`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 speedometersfacilitate the access, operation, and
`display of automobile resources, functionality, and status.
`Computer interaction interface elements such as check
`boxes, cursors, menus, scrollers, and windows(callectively
`and commonlyreferred 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 commonlycalled user inter-
`faces. Graphical user interfaces (GUIs) such as the Apple
`Macintosh Operating System’s Aqua, Microsoft’s Windows
`XP, or Unix’s X-Windowsprovide a baseline and means of
`accessing and displaying information, graphically, to users.
`Networks
`
`10
`
`2°
`
`w a
`
`40
`
`ay So
`
`a a
`
`60
`
`65
`
`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
`thal 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 gencrally to a computer, other device, software,
`or combination thereof that is capable of processing and
`making, requests and obtaining and processing any responses
`fromservers across a communications network. A computer,
`other device, software, or combination thereof that facili-
`tates, processes information and requests, and/or furthers the
`passage ofinformation 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 nade specifically
`tasked with furthering the passage of information from a
`source to a destination is commonlycalled a “router.” ‘There
`are many forms of networks such as Local Area Networks
`(LANs), 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
`mayaccess and interoperate with one another.
`
`SUMMARY
`
`Althoughall 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 compuling solution, are bulky,
`provide uncomfortably small user interfaces, and require too
`much powerto maintain their data. Current PDA designs are
`complicated and. cast 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 amount 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 grealer memory footprints,
`draws less power, and provides security for data on the
`device. As such, the disclosed tunneling client access point
`(CAP) is very easy to use; at most it requires the user to
`simply plug the device into any cxisting and available
`desktop or laptop computer, through which, the TCAP can
`make use of a traditional user interface and input/output
`(/O)peripherals, while the TCAPitself, 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 casy and secure manner that was
`unavailable in the priorart.
`In accordance with certain aspects of the disclosure, the
`above-identified problems of limited computing devices are
`overcomeand 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 terminal, executing processing instructions from the
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`

`

`4
`runtime environments, which allows the TCAPto 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 I'CAP. Once the ICAP 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 TCAPserver
`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
`113, ¢ (e.g., a local area network (LAN)). In such an
`embodiment, a backend server 110 mayoffloadthe 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 efficient manner.
`In such an
`embodiment, the back-cnd servers may be connected to the
`front-end servers through a communications network 1136
`(c.g., wide areca network (WAN)). The backendservers 110,
`115 may be connected to the remote storage 105 through a
`communications network 113c as well (e.g., a high speed
`LAN,liber-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/orthe servers’ storage facilities 105. In
`these ways, the TCAP “tunnels” data through an AT. The
`data may he provided through the AT’s I/O for the user to
`observe without it actually residing on the Al. Also, the
`TCAP maytunnel data through an AT across a communi-
`calions network to access remote servers withoul requiring
`its own more complicated set of peripherals and I/O.
`TCAPand 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 ''CAP into an AIvia the
`AT’s USB port. Thereafter the user is presented with a login
`Topology
`prompt 205 on the AT’s display mechanism, e.g., on a video
`FIG. 1 illustrates embodiments for a topology between a
`monitor. After a user successfully logs in (for example by
`tunneling client access point (TCAP) (see FIG. 10 for more
`providing a user name and password) 204, the TCAP can
`details on the TCAP) and TCAP server (TCAPS) (see FIG.
`then accept user inputs from the AT andits peripherals (the
`9 for more details on the TCAPS). In this embodiment, a
`TCAPcan then also provide output to the user via the AT’s
`user 133a may plug-in a TCAP into any numberof access
`peripherals).
`terminals 127 located anywhere. Access terminals (ATs)
`The user may employ the AT’s input peripherals as user
`may be any number of computing devices such as servers,
`input devices that control actions on the TCAP. Depending
`workstations, desktop computers, laptops, portable digital
`on the user’s actions 215, the TCAP can be used by the AT
`assistants (PDAs), and/or the like. The type ofAT used is not
`as a storage device from whichit can access and store data
`important other than the device should provide a compatible
`and programs 225. For example, if the user takes the action
`mechanism of engagement to the TCAP 130 and provide an
`
`operating environment for the user to engage the I'CAP of openingafile from the T'CAP’s memory, e.g., by double
`through the AT. In one embodiment, the TCAP provides a
`clicking on an icon when the TCAP is mounted as a USB
`universal serial bus (USB) connector through which it may
`drive on the AT,
`then the AT may treat
`the TCAP as a
`plug into an AT. In other embodiment,
`the TCAP may
`memory device and retrieve information from the TCAP
`225. If the user’s action 215 is one that
`is directed at
`employ Bluetooth, WiFi and/or other wireless connectivity
`protocols to connect with ATs that are also so equipped. In
`executing on the TCAP 215, then the AT will not be involved
`one embodiment,
`the AT provides Java and/or Windows
`in any execution. For example, if the user drops an icon
`
`The accompanying, drawings illustrate various non-limit-
`ing, example,
`inventive aspects in accordance with the
`present disclosure:
`FIG. 1 is of a flow diagram illustrating embodimentsof a
`tunneling client access point (TCAP);
`FIG. 2 is of a flow diagram illustrating embodimentsof a
`system of tunneling client access point and access terminal
`interaction;
`FIG. 3 is of a flow diagram illustrating embodiments of
`engaging the tunneling clicnt access point to an access
`terminal interaction;
`FIG. 4 is of a flow diagram illustrating embodiments of
`accessing the tunneling client access point and server
`through an access terminal;
`FIGS. 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;
`FIG. 9 is of a black diagram illustrating embodiments of
`a tunneling client access point server controller;
`FIG. 10 is of a block diagramillustrating embodiments of
`a tunneling client access point controller;
`The leading numberof each reference numberwithin the
`drawings indicates the first figure in which that reference
`numberis introduced. As such, reference number 101 is first
`introduced in FIG. 1. Reference number 201 is first intro-
`duced in FIG. 2, etc.
`
`
`
`DETAILED DESCRIPTION
`
`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 tun-
`neling storage processor is disclosed. The apparatus has a
`memory and a processor disposed in communication with
`the memary, 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, configured 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
`
`ra co
`
`
`
`w °
`
`w a
`
`40
`
`wv So
`
`a a
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-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
`
`No a
`
`w a
`
`40
`
`5
`6
`After being engaged 305, the TCAP will then poweron.
`representing a graphics file onto a drag-and-drop location
`In an embodiment requiring a direct connection, e.g., USB,
`visually representing the TCAP,thenthefile may be copied
`simply plugging the TCAPinto the AT provides power. Ina
`to the TCAP where it will process and spool the file for
`wireless embodiment,
`the (CAP may be on in a lower
`sending, the graphics file to be printed at a remote location.
`powered. state or otherwise turned on by cngaging the
`In such a case, all of the requirements to process and spool
`connect button as discussed above. In such an embodiment,
`the file are handled by the TCAP’s processor and the AT
`the TCAP can employ various on-board power sources (see
`would only be used as a mechanism for user input and output
`FIG. 10 for more details on the TCAP). The TCAP then may
`and as a conduil through which the TCAP maysend files.
`load its own operating system 315. The operating system can
`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 10 provide for interaction with the AT. In one embodiment, a
`ATis used to display the status of any actions 230. At any
`Java runtime is executed on the TCAP, and Java applets
`time the user mayselect to terminate TCAPrelated facilities
`communicate with the AT through Java APIs. In another
`executing either on the AT, a backend server, on the TCAP
`embodiment, a driver is loaded onto the AT, and the on-
`itself, and/or the like 235. In one embodiment, the user may
`TCAPJava operating system applets communicate to and
`select a quit option that is displayed on the Al”s screen. In 15
`throughthe ATvia the driver running on the Al, wherein the
`another embodiment, the user may simply disengage the
`driver provides an API through and to which messages may
`‘TCAPtrom the Al’ by severing the connection(e.g., turning
`be sent.
`poweroff, physically pulling the device off the AT, turning
`After engaging with the AT, the TCAP can provide its
`olf wireless transmissions, and/or the like). It should be
`memory space to the AT 320. In one embodiment,
`the
`noted that such abrupt severing may result in the loss of data, 20 TCAP’s memory is mapped and mountedas a virtual disk
`file corruption, etc. if the TCAP has not saved data that is on
`drive 125 storage 325. In this manner, the TCAP may be
`the AT or on some remote server, however, if the TCAPis
`accessed and manipulated as a standard storage device
`employing flash like memory,
`its contents should remain
`through the AT’s operating system. Further, the TCAP and
`intact.
`in some cases the AT can determine if the AT is capable of
`If there is no instruction signal to terminate the TCAP
`accessing program instructions
`stored in the TCAP’s
`235, execution will continue and the TCAP will continue to
`memory 330. In one embodiment, the AT’s operating system
`take and look for input from the user. Of course if the TCAP
`looks to auto-run a specified file from any drive as it mounts.
`has been set to perform certain actions, those actions will
`In such an embodiment, the '}CAP’s primary interface may
`continue to execute, and the TCAP may respond to remote
`be specified in such a boot sequence. For example, under
`servers when il is communicating with them through the AT.
`windows, an aulorun.intfile can specify the opening of a
`Whenthe user issues a terminate signal 235, then the TCAP
`program from the
`TCAP
`by
`the
`AT:
`eg,
`OPEN=TCAP.EXE.
`will shut down by saving any data to the TCAPthatis in the
`AT’s memory and then terminating any programs executing
`Many operating systems are capable ofat least accessing
`on both the AT and TCAPthat were executed by and/or from
`the TCAP as a USB memorydrive 330 and mounting its
`the TCAP240. If no activities are taking place on the TCAP
`contents as a drive, which usually becomes accessible infile
`and all the data is written back to the TCAP 240, then the
`browsing window 125. If the TCAP docs not mount, the
`‘CAP may optionally unmount itself from the Al’s file-
`A1L’s operating, system will usually generate an error inform-
`system 245. At this point, if there is a TCAP I/O driver
`ing the user of a mounting problem.If the AT is not capable
`execuling on the AT,
`that driver may be terminated as
`of executing instruction [rom the TCAP, a determination is
`triggered by the absence of the TCAP at a mountpoint 250.
`made if an appropriate driver is loaded on the AT to access
`Alier the TCAPis unmounted and/or the TCAP I/O driveris
`the TCAP 335. In one embodiment, the TCAP can check to
`terminated, it is safe to disengage the TCAP from the AT.
`see if an API is running on the AT. For example, the TCAP
`TCAP and AT Interaction
`provide an executable to be launched, e.g., as specified
`FIG. 3 illustrates embodiments engaging the tunneling
`through autorun.inf, and can establish communications
`client access point
`to an access terminal
`interaction.
`through its connection to the AT, e.g., employing TCP/IP
`Examples of engaging the TCAP 301 with an AT were
`communications over the USB port. In such an embodiment,
`discussed above in FIG. 1 127, 130, 133a and FIG. 2 201.
`the TCAP can ping the AT for the program, and if an
`n one embodiment, theCAP 130 is engaged with an
`acknowledgement is received, the ‘CAP has determined
`access terminal 327, 305. As mentioned in FIG. 1, the TCAP
`that proper drivers and APIs exist. If no such API exists, the
`TCAP may launcha driver installation program for the AT
`as through an autorun.inf. In an alternative embodiment, if
`nothing happens, a user may double click onto aninstaller
`program that is stored on the mounted TCAP 342, 340. It
`should be noted, that although the TCAP’s memory space
`maybe mounted, certain areas of the TCAP maybe inac-
`cessible until there is an authorization. For example, certain
`areas and content on the TCAP may be encrypted. It should
`be noted that any such access terminal modulesthat drive AT
`and ‘CAP interaction may be saved onto the ‘'CAP by
`copying the module to a mounted TCAP. Nevertheless, if the
`AYis capable of accessing program instructions in ‘CAP
`memory 330, a TCAPdriveris 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 AT’s I/O and
`allowing the user to interface with TCAP facilities 345. It
`should be noted that some ATs maynot be able to mountthe
`
`nisms. In one embodiment, the TCAP has a USB connector
`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
`employmultiple communications mechanisms. It should be
`noted, with some wireless mechanismslike Bluctooth and
`WiFi, simply coming into proximity with an AI that is
`configured for such wireless communication may result in
`the 1}CAP engaging with and establish a communications
`link with the AT.
`In one embodiment,
`the TCAP has a
`“connect” button that will allow such otherwise aulomati-
`cally engaging interactions take place only if the “connect”
`button is engaged bya user. Such an implementation may
`provide greater security for users (see FIG. 10 for more
`details on the TCAP).
`
` is capable of engaging with ATs using a number of mecha-
`
`ay So
`5
`
`a a
`
`60
`
`PayPal Inc. v. IOENGINE, LLC
`IPR2019-00906 (US 9,059,969)
`Exhibit 2034
`
`PayPal Inc. v

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket