throbber
Case 6:21-cv-00569-ADA Document 244-56 Filed 07/21/23 Page 1 of 2
`
`THE SYNCRONIZATION
`
`•
`
`•
`
`•
`•
`
`•
`
`•
`
`•
`
`•
`
`The handheld device 101 connects to the server 105 through the internet.
`
`The server 105 links the handheld device 101 with an associated database 102 which is unique
`for that device.
`
`If the HD does not have an associated database one is create for it.
`The EDD 103 connects to the server 105 through the internet
`
`The server links EDD 103 with its own database 104.
`
`If the device does not have an associated database. A unique marker is assigned to the EDD and
`store in that devices memory and an associated database is created.
`
`The HD initiates a connection request to a EDD database 104,
`o The handheld request is trigger automatically to the default EDDdatabase 104
`o
`or to another database 104 selected by the user, using the input on the hand held
`device.
`
`If the handled database 102 is authorized to connect with the device database 104 a connection
`between the two is established.
`
`DISPLAYING INFORMATION HANDHELD
`
`The handheld device requests a webpage from the 105 server. The Webpage loads in the handheld 101
`and waits for a request from the user. The user type in a request or clicks on a button that makes a
`request to the server 105. Server 105 then makes a request to other web servers on the internet 106.
`The web servers 106 send data back to the server 105. The server 105 combines the various data
`structure files in to one file, places a marker identifying which element and the server it came from and
`thenformats the appropriate elements in to a displayable code and then sends that information to the
`handheld device 101.
`
`SEND THE CODES
`
`A request is made on the handheld devices 101 and is sent to the server 105. The server checks the
`code for a marker indicating the server that originated that data and loads the translator 107. The server
`than sends request to the 102 database. The 102 database copies the request to the 104 database.
`
`RETIREVE THE CODES
`
`The enhanced display device checks the database104 on regular intervals. If a new command is posted
`the display device executes that command.
`
`THE COMMANDS
`
`The command can trigger local actions, play, stopping the file. Or it can trigger an outside request to get
`a file.
`If a trigger is for outside the command contains the file name and the server it's on. The display
`device connects to the appropriate server on the internet 106 and retrieves the data file.
`
`CONFIDENTIAL
`
`TS-00904846
`
`Touchstream v. Google
`6:21-cv-00569-ADA
`D 637.001
`
`

`

`Case 6:21-cv-00569-ADA Document 244-56 Filed 07/21/23 Page 2 of 2
`
`1. Handheld device (HHD) 101 connects to server 105.
`2. A database 102 is either opened or created for HHD 101
`3.
`Internet Connected Display (ICD) 103 connects to server 105.
`4. A database 104 is either opened or created for ICD 103.
`5.
`If authorized a connection is made between the databases 102 and 104.
`6. A user submits a request through HHD 101 to server 105 for a data list of video information.
`7. Server 105 searches outside servers 106 for video information.
`8. Server 105 aggregates all the data list and compiles it in to one data list and sends that list to
`HHD 101
`9. A user submits an action from the list displayed on HHD 101. The action request is sent to the
`database 102 on the server 105.
`10. The action is then transferred from database 102 to 104.
`11. The action is transferred from the database 104 to ICD 103
`12. ICD 103 then executes the action locally or connects to an outside server to retrieve a specific
`data stream.
`13. ICD 103 communicates it's status at regular intervals to the server 105
`
`CONFIDENTIAL
`
`TS-0090484 7
`
`Touchstream v. Google
`6:21-cv-00569-ADA
`D 637.002
`
`

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