throbber
Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 1 of 11 PAGEID #: 76
`Case: 1:20-CV-00578—MWM Doc #: 1-3 Filed: 07/24/20 Page: 1 of 11 PAGEID #: 76
`
`EXHIBIT C
`
`EXHIBIT C
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 2 of 11 PAGEID #: 77
`
`Runkeeper (“The Accused Product”)
`The accused product discloses a computer-readable storage medium (e.g., the memory of a smartphone) storing
`content that, if executed by computing system having a processor (e.g., the processor of the smartphone), causes the
`computing system (e.g., Runkeeper’s computing system) to perform a method comprising receiving a set of
`connections between geographical localities (e.g., First Locality and Second Locality), each connection connecting
`one geographical locality (e.g., First Locality) to one other geographical locality (e.g., Second Locality) with no
`intermediate geographical localities along the connection.
`
`Charted Claims:
`Method: 13
`Non-Method:
`US8560238
`13. A computer-
`readable storage
`medium storing content
`that, if executed by
`computing system
`having a processor,
`causes the computing
`system to perform a
`method comprising:
`receiving a set of
`connections between
`geographical localities,
`each connection
`connecting one
`geographical locality to
`one other geographical
`locality with no
`intermediate
`geographical localities
`along the connection;
`
`https://runkeeper.com/
`
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 3 of 11 PAGEID #: 78
`
`https://runkeeper.com/
`
`
`
`
`https://runkeeper.com/search/routes
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 4 of 11 PAGEID #: 79
`
`receiving a request to
`provide a path from a
`first geographical
`locality to a second
`geographical locality;
`
`https://runkeeper.com/user/TaushaTaylor/route/1628796
`
`The accused product discloses receiving a request to provide a path from a first geographical locality (e.g., First
`Locality) to a second geographical locality (e.g., Second Locality).
`
`As soon as Runkeeper’s user request popular route in a particular area, for example Chicago, the accused product
`provides path between first geographical locality and second geographical locality.
`
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 5 of 11 PAGEID #: 80
`
`https://runkeeper.com/
`
`
`https://runkeeper.com/
`
`
`
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 6 of 11 PAGEID #: 81
`
`https://runkeeper.com/search/routes
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 7 of 11 PAGEID #: 82
`
`https://runkeeper.com/user/TaushaTaylor/route/1628796
`
`The accused product discloses determining, based at least in part on the received set of connections, a plurality of
`paths (e.g., multiple paths) from the first geographical locality (e.g., First Locality) to the second geographical locality
`(e.g., Second Locality), wherein a first path (e.g., highlighted in blue colour) includes a third geographical locality but
`does not include a fourth geographical locality and wherein the second path (e.g., highlighted in green colour) includes
`the fourth geographical locality but does not include the third geographical locality.
`
`
`
`
`determining, based at
`least in part on the
`received set of
`connections, a plurality
`of paths from the first
`geographical locality to
`the second
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 8 of 11 PAGEID #: 83
`
`As shown below, third geographical and fourth geographical localities are different possible routes such as direct
`freehand route and popular route. Also, third and fourth geographical locality are segments among the first and second
`paths, respectively, that are not included in the other paths. For instance, the location marked in green is included in
`the second path, but not in the first path.
`
`
`geographical locality,
`wherein a first path
`includes a third
`geographical locality
`but does not include a
`fourth geographical
`locality and wherein
`the second path
`includes the fourth
`geographical locality
`but does not include the
`third geographical
`locality; and
`
`https://runkeeper.com/search/routes
`
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 9 of 11 PAGEID #: 84
`
`https://runkeeper.com/user/TaushaTaylor/route/1628796
`The accused product discloses identifying, by the processor (e.g., the processor of the smartphone), a path (e.g., first
`path) between the first geographical locality (e.g., First Locality) and the second geographical locality (e.g., Second
`Locality) based at least in part on a popularity rating for the third geographical locality and a popularity rating for the
`fourth geographical locality.
`
`As shown below, the accused product identifies the popularity of different geographical localities between first
`geographical location and second geographical location and suggests the popular one.
`
`
`
`
`identifying, by the
`processor, a path
`between the first
`geographical locality
`and the second
`geographical locality
`based at least in part on
`a popularity rating for
`the third geographical
`locality and a
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 10 of 11 PAGEID #: 85
`
`popularity rating for the
`fourth geographical
`locality.
`
`https://runkeeper.com/search/routes
`
`
`
`
`

`

`Case: 1:20-cv-00578-MWM Doc #: 1-3 Filed: 07/24/20 Page: 11 of 11 PAGEID #: 86
`
`
`
`https://runkeeper.com/user/TaushaTaylor/route/1628796
`
`
`
`

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