Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 1 of 8
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 1 of 8
`
`EXHIBIT D
`
`EXHIBIT D
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 1 of 8
`
`EXHIBIT D
`
`EXHIBIT D
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 2 of 8
`
`U.S. Patent No.
`9,635,108
`[pre] A method for
`sharing content,
`comprising:
`
`Exhibit D
`Infringing Products and Services
`
`To the extent the preamble is limiting, Lime operates a scooter
`sharing service Lime that allows users to unlock and ride Lime’s
`fleet of e-scooters and powered bikes via smartphone app. The
`scooters collect various information such as location and battery
`information/operational range. The data collected by the e-
`scooter is uploaded to a cloud computing server and then shared
`with a user or rider through a mobile application.
`
`1
`
`a server, configured to
`communicate to a first
`and second client;
`
`Lime’s mobile application necessarily requires a server
`communicating data between the scooter (first client) and the
`mobile device of the rider (second client).
`
`receiving, at a server,
`from a first client, a
`shared content, and a
`unique identifier
`generated by a
`computer application
`running on the first
`client or server, for the
`shared content;
`
`Lime’s server receives from a scooter shared content such as
`data collected by the on-board electronics of the scooter
`including GPS data, battery information, trip start and end times.
`As shown below, some scooters are marked as “GPS Tracked”
`indicating the availability of shared GPS data.
`
`The collected data is received by the server with a unique
`identifier that is associated with the scooter.
`
`1 https://play.google.com/store/apps/details?id=com.limebike&hl=en
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 3 of 8
`
`Each scooter and collected data can be associated with a unique
`identifier as a QR code or a 6 digit vehicle code.
`
`The QR code and the 6 digit vehicle code are displayed on the
`handle bars of the scooter.
`
`wherein the unique
`identifier comprises
`one of: a QR code, bar
`code, RFID tag,
`hexadecimal number,
`alphanumeric key,
`ASCII key, or
`UNICODE string;
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 4 of 8
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 4 of 8
`
`
`
`
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 5 of 8
`
`receiving, at the second
`client, the unique
`identifier, from the first
`client;
`
`When a rider requests to ride a Lime scooter, the rider scans the
`unique identifier located on the scooter using the Lime mobile
`app.
`
`2
`
`2 https://www.li.me/help
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 6 of 8
`
`The unique identifier can be received via QR code scan or by
`entering the vehicle ID associated with the scooter.
`
`wherein the second
`client receives the
`unique identifier via:
`Bluetooth, Bluetooth
`Low Energy, NFC,
`Barcode or QR code
`scan, RFID tag scan, or
`communication from a
`first user of the first
`client to a second user
`of the second client;
`
`determining, at the
`server, that the second
`client is within a
`
`Lime’s server determines the rider is within a predefined
`distance or is at the scooter location when the rider is able to
`scan the QR code and transmit the identifier to the server.
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 7 of 8
`
`Lime’s cloud computing server determines that the scooter is
`within a predefined distance from the rider via QR code scan.
`
`predefined distance
`from the first client by
`receiving location
`information from the
`first or second client;
`Wherein the server
`determines that the first
`client is within a
`predefined distance
`from the second via:
`Bluetooth proximity,
`Bluetooth Low Energy
`proximity, NFC,
`Barcode or QR code
`scan, Ultrasonic sound,
`IP address triangulation
`of the clients, RFID
`scan, communication
`from a first user of the
`first client to a second
`user of the second
`client, or by
`determining that the
`location of the first
`client is within the
`same area as the
`location of the second
`client;
`
`notifying, the second
`client of the shared
`content responsive to
`the determination;
`
`Upon “unlocking the ride,” the app updates the user interface to
`notify the rider that data collected and shared by the scooter is
`available to the rider. For example, the UI below begins showing
`the ride duration, ride length, and scooter battery levels in form
`of operation range left.
`
`
`
`Case 6:21-cv-00321 Document 1-4 Filed 04/01/21 Page 8 of 8
`
`receiving, at the server,
`a request from a second
`client, the request
`comprising the unique
`identifier
`determining, at the
`server, that the unique
`identifier is associated
`with the shared
`content; and
`sending the shared
`content to the second
`client responsive to
`that determination.
`
`As the rider continues the ride, the mobile device requests real-
`time data collected shared by the scooter. The mobile device
`requests data from the scooter that the rider is riding by using the
`unique identifier associated with the scooter.
`
`The server determines that the scooter identified by the unique
`identifier (the scooter the rider is using) has uploaded data such
`as updated battery information or GPS data.
`
`The server sends the new information and the mobile device
`updates the user interface to reflect the real-time data, for
`example by updating the battery information.
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
