throbber
Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 1 of 24 PageID #: 24142
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`MAXELL, LTD.,
`
`v.
`
`APPLE INC.,
`
`Plaintiff,
`
`Defendant.
`
`Case No. 5:19-cv-00036-RWS
`
`JURY TRIAL DEMANDED
`
`MAXELL, LTD.’S OPPOSITION TO APPLE INC.’S MOTION FOR PARTIAL
`SUMMARY JUDGMENT OF SUBJECT MATTER INELIGIBILITY UNDER
`35 U.S.C. § 101 FOR U.S. PATENT NOS. 6,748,317, 6,430,498, AND 6,580,999
`
`PUBLIC VERSION
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 2 of 24 PageID #: 24143
`
`
`
`
`
`Table of Contents
`
`PAGE
`
`I.
`II.
`III.
`
`IV.
`
`RESPONSE TO STATEMENTS OF ISSUES AND UNDISPUTED FACTS ................ 2
`LEGAL STANDARDS ..................................................................................................... 3
`ARGUMENT ..................................................................................................................... 3
`A.
`Claim 1 of the ’317 Patent is Not a Representative Claim .................................... 4
`B.
`The Challenged Claims are Valid at Alice Step-One ............................................ 5
`1.
`Claims 1 and 17 of the ’317 Patent (“Walking Navigation Claims”) ........ 7
`2.
`Claim 3 of the ’999 Patent (“Locate a Friend Claim”) .............................. 9
`3.
`Claim 3 (“Walking Navigation and Display Orientation Claim”)
`and Claim 13 (“Locate a Friend and Display Orientation Claim”)
`of the ’498 Patent ..................................................................................... 10
`The Challenged Claims are Valid at Alice Step-Two .......................................... 12
`C.
`CONCLUSION ................................................................................................................ 15
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 3 of 24 PageID #: 24144
`
`
`
`
`
`TABLE OF AUTHORITIES
`
`
`
`Page(s)
`
`Cases
`
`Alice Corp. Pty. Ltd. v. CLS Bank Int’l,
`573 U.S. 208 (2014) ...................................................................................................................3
`
`Berkheimer v. HP Inc.,
`881 F.3d 1360 (Fed. Cir. 2018)..........................................................................................13, 14
`
`Cellspin Soft, Inc. v. Fitbit, Inc.,
`927 F.3d 1306 (Fed. Cir. 2019)..................................................................................................3
`
`Core Wireless Licensing S.A.R.L. v. LG Elecs., Inc.,
`880 F.3d 1356 (Fed. Cir. 2018)..............................................................................................3, 7
`
`CXT Sys. v. Acad., Ltd.,
`No. 2:18-CV-00171, 2019 U.S. Dist. LEXIS 51915 (E.D. Tex. March 19,
`2019) ..................................................................................................................................4, 5, 9
`
`Data Engine Techs. LLC v. Google LLC,
`906 F.3d 999 (Fed. Cir. 2018)......................................................................................7, 8, 9, 11
`
`DDR Holdings, LLC v. Hotels.com, L.P.,
`773 F.3d 1245 (Fed. Cir. 2014)............................................................................................1, 12
`
`Enfish, LLC v. Microsoft Corp.,
`822 F.3d 1327 (Fed. Cir. 2016)..........................................................................................2, 3, 5
`
`GREE, Inc. v. Supercell Oy,
`No. 2:19-CV-00161, 2020 U.S. Dist. LEXIS 14412 (E.D. Tex. Jan. 29, 2020) ....................4, 5
`
`IDB Ventures, LLC v. Charlotte Russe Holdings, Inc.,
`No. 2:17-CV-660, 2018 U.S. Dist. LEXIS 186215 (E.D. Tex. Oct. 31, 2018) .........................7
`
`McRO, Inc. v. Bandai Namco Games Am. Inc.,
`837 F.3d 1299 (Fed. Cir. 2016)..................................................................................................3
`
`PPS Data, LLC v. Jack Henry & Assocs.,
`404 F. Supp. 3d 1021 (E.D. Tex. 2019) .....................................................................................4
`
`Uniloc USA, Inc. v. LG Elecs. USA, Inc.,
`957 F.3d 1303 (Fed. Cir. 2020)..................................................................................................7
`
`X One, Inc., v. Uber Technologies, Inc.,
`239 F. Supp. 3d 1174 (N.D. Cal. 2017) ...................................................................................12
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 4 of 24 PageID #: 24145
`
`
`
`
`
`Statutes
`
`35 U.S.C. § 101 ................................................................................................................................3
`
`35 U.S.C. § 282(a) ...........................................................................................................................4
`
`ii
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 5 of 24 PageID #: 24146
`
`
`
`
`
`APPENDIX 1: CLAIM LANGUAGE AT ISSUE
`
`U.S. Patent No. 6,748,317
`
`1. A portable terminal, comprising:
`a device for getting location information denoting a [p]resent place of said portable
`terminal;
`a device for getting a direction information denoting an orientation of said portable
`terminal;
`an input device for inputting a destination; and
`a display, wherein
`said display displays positions of said destination and said present place, and a
`relation of said direction and a direction from said present place to said
`destination, and
`said display changes according to a change of said direction of said portable
`terminal orientation for walking navigation.
`
`15. A portable terminal with walking navigation according to claim 1, further comprising:
`a device for retrieving a route from said present place to said destination,
`wherein said display displays said route and displays a direction of movement by the
`arrow.
`
`17. A portable terminal with walking navigation according to claim 15,
`wherein said display displays said route with a bent line using symbols denoting starting
`and ending points and displays symbols denoting said present place on said route.
`
`U.S. Patent No 6,430,498
`
`1. A portable terminal with the function of walking navigation, comprising
`a device for getting location information denoting a present place of said portable
`terminal; and
`a device for getting direction information denoting an orientation of said portable
`terminal,
`wherein a direction and a distance of a destination from said present place are denoted
`with an orientation and a length of a line that is distinguished between starting and
`ending points to supply route guidance information as said walking navigation
`information.
`
`3. A portable terminal with the function of walking navigation according to claim 1,
`wherein said device for getting direction information gets orientation information of a
`display of said portable terminal.
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 6 of 24 PageID #: 24147
`
`
`
`
`
`10. A portable terminal with the function of walking navigation, comprising
`a device for getting location information denoting a present place of said portable
`terminal; and
`a device for getting direction information denoting an orientation of said portable
`terminal,
`wherein location of a user is of said portable terminal is determined according to said
`location information and said direction information,
`wherein location of a partner of the user is determined according to a location
`information from the partner's portable terminal, and
`wherein a full route from said starting point to said destination is shown with a bent line
`that is distinguished between starting and ending points and said present place is
`shown with a symbol on said line to supply said route guidance information as
`said walking navigation information.
`
`13. The portable terminal with said function of walking navigation according to claim 10,
`wherein said device for getting direction information gets orientation information of a
`display of said portable terminal.
`
`U.S. Patent No 6,580,999
`
`1. A portable terminal with the function of walking navigation, comprising:
`a device for getting location information denoting a present place of said portable
`terminal;
`a device for getting direction information denoting an orientation of said portable
`terminal; and
`a device for getting the location information of another portable terminal,
`wherein a direction from said present place to the location of said another portable
`terminal is displayed with the distance information between said locations to
`supply route guidance information as said walking navigation information.
`
`3. A portable terminal with the function of walking navigation according to claim 1;
`wherein said direction from said present place to the location of said another portable
`terminal is displayed using the symbols denoting the said present location and
`said location of another portable terminal.
`
`ii
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 7 of 24 PageID #: 24148
`
`
`
`
`Apple’s motion is an attempt to erase a genuine invention, something even Apple’s own
`
`expert admits could not be done before the asserted patents came along. According to Dr.
`
`Paradiso (Apple’s expert on the subject), in or around 1999—a decade before the first iPhone
`
`with GPS—engineers at Nokia, MIT, and Microsoft were experimenting with ways to improve
`
`the ability of cellular phones to calculate location accurately. Ex. A (Paradiso Claim
`
`Construction Dep. Tr.) at 38:9-18, 39:16-40:11 (discussing shortcomings of Nokia phones with
`
`GPS, Microsoft radar, and the system Dr. Paradiso was developing at MIT). As confirmed by Dr.
`
`Paradiso, this was because “GPS was very limited use”; cellular positioning and GPS positioning
`
`“quite often didn’t even work [indoors], so not even being accurate, they just wouldn’t work;”
`
`and “[o]utdoors there were challenges [with GPS positioning systems]”; “radio location—ultra-
`
`wideband was in its infancy and still very flaky”; and Microsoft’s radar “was still very flaky in
`
`terms of how well you knew where someone was.” Ex. A (Paradiso CC Dep. Tr.) at 38:9-18,
`
`40:19-24, 39:16-40:11. Providing accurate location information to a portable terminal was “a
`
`problem specifically arising in the realm of [mobile/GPS] networks.” DDR Holdings, LLC v.
`
`Hotels.com, L.P., 773 F.3d 1245, 1257 (Fed. Cir. 2014).
`
`To overcome these challenges, the inventors of U.S. Patent Nos. 6,748,317 (the “’317
`
`Patent”), 6,430,498 (the “’498 Patent”), and 6,580,999 (the “’999 Patent”) (collectively, the
`
`“Navigation Patents”) proposed various solutions. These solutions included novel arrangements
`
`of hardware1 such as a “device for getting location information” being included with “a device
`
`for getting direction information denoting an orientation” and/or “an input device,” “a device for
`
`1 Dr. Paradiso agreed that the various claims require specific combinations of hardware. See Ex.
`B (Paradiso Claim Construction Decl. (Oct. 4, 2019)) at ¶ 31 (“to achieve the goal of walking
`navigation, a POSITA would have understood, consistent with the disclosures in the
`specification, that a combination of GPS and some means of indoor location determination,
`likely an infrared sensor, would be required”).
`
`1
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 8 of 24 PageID #: 24149
`
`
`
`
`retrieving a route” or a “device for getting the location information of another portable terminal.”
`
`Using these new arrangements of hardware, a portable terminal could generate and display novel
`
`user interfaces and thus was an improved navigation device that facilitated walking navigation
`
`by overcoming the accuracy challenges of devices using GPS or cellular-location of that time.
`
`Apple argues that the inventors of the Navigation Patents should never have been granted
`
`these patents at all—not because the claimed solutions already existed or because they might
`
`have been obvious—but because the solutions are ineligible for patenting. But Apple improperly
`
`groups all of the Navigation Patents together and relies on generalizations of the patents entirely
`
`untethered to claim language to make the flawed argument that: “[t]he asserted claims are
`
`directed to presenting navigation and location information to a walking user.” Mot. at 6. Such a
`
`characterization misses the claim language, which shows that the inventors proposed specific
`
`“implementation[s] of a solution to [the] problem” of accurately facilitating walking
`
`navigation—namely by claiming specific devices in an unconventional arrangement that together
`
`could be used to generate novel user interfaces. See Enfish, LLC v. Microsoft Corp., 822 F.3d
`
`1327, 1339 (Fed. Cir. 2016).
`
`The challenged claims are not directed to the high-level abstraction that Apple identifies,
`
`but rather are directed to practical improvements to devices carrying out navigation functionality.
`
`Thus, the Navigation Patents are not categorically excluded from patent protection as Apple
`
`contends, and the Court should deny Apple’s Motion for Partial Summary Judgment of Subject
`
`Matter Ineligibility under 35 U.S.C. § 101.
`
`I.
`
`RESPONSE TO STATEMENTS OF ISSUES AND UNDISPUTED FACTS
`
`Maxell agrees with Apple’s Statement of Issues. Mot. at 1. The parties’ factual disputes
`
`are numerous and best addressed in the context of the Section 101 inquiry below. But in general,
`
`looking to Apple’s “Statement of Undisputed Material Facts,” Maxell disputes (A) Apple’s
`2
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 9 of 24 PageID #: 24150
`
`
`
`
`summary of the Navigation Patents (Mot. at 1-3); (B) what the “asserted claims are directed to”
`
`(Mot. at 3); (C) that Claim 1 of the ’317 Patent is representative (Mot. at 3); (D) Apple’s
`
`summary of the “State of the Known Art” (Mot. at 4-5); and (E) that the jury in the ZTE
`
`litigation “resolved” a factual dispute about whether elements of the ’317 Patent were “well-
`
`understood, routine, and conventional” (Mot. at 5).
`
`II.
`
`LEGAL STANDARDS
`
`Section 101 of the Patent Act defines the scope of patentable subject matter eligibility
`
`broadly. 35 U.S.C. § 101. The Federal Circuit has been explicit that software inventions fall
`
`squarely within this definition of eligibility. Enfish, 822 F.3d at 1335; see also Core Wireless
`
`Licensing S.A.R.L. v. LG Elecs., Inc., 880 F.3d 1356, 1362 (Fed. Cir. 2018) (finding eligible “an
`
`improved user interface for computing devices”).
`
`The Supreme Court has set forth the well-known Alice test to determine whether a patent
`
`merely claims an abstract idea and is thus patent ineligible. Enfish, 822 F.3d at 1334 (citing Alice
`
`Corp. Pty. Ltd. v. CLS Bank Int'l, 573 U.S. 208, 217-18 (2014)). At step-one, Courts consider the
`
`claims in their entirety to ascertain whether “their character as a whole is directed to excluded
`
`subject matter.” Enfish, 822 F.3d at 1335. Courts “must be careful to avoid oversimplifying the
`
`claims by looking at them generally and failing to account for the specific requirements of the
`
`claims.” McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1313 (Fed. Cir. 2016).
`
`If the claims are directed to excluded subject matter, step-two determines whether the
`
`claims provide an “inventive concept.” Alice, 573 U.S. at 217-18. This is a factual inquiry. See
`
`Cellspin Soft, Inc. v. Fitbit, Inc., 927 F.3d 1306, 1318 (Fed. Cir. 2019) (citing Berkheimer v. HP
`
`Inc., 881 F.3d 1360 (Fed. Cir. 2018)). A claim will be eligible at step-two if it recites “concrete
`
`improvements in the recited computer technology.” Enfish, 822 F.3d at 1339.
`
`III.
`
`ARGUMENT
`
`3
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 10 of 24 PageID #: 24151
`
`
`
`
`A.
`
`Claim 1 of the ’317 Patent is Not a Representative Claim
`
`“Each claim of a patent [] shall be presumed valid independently of the validity of other
`
`claims.” 35 U.S.C. § 282(a). The burden of showing that all challenged claims should be
`
`evaluated according to a representative claim belongs to Apple, a burden that Apple fails to
`
`carry. See PPS Data, LLC v. Jack Henry & Assocs., 404 F. Supp. 3d 1021, 1030-31 (E.D. Tex.
`
`2019) (“when a defendant seeks to invalidate multiple claims based only on allegations relating
`
`to a subset of those claims, the defendant must justify treating that subset as representative of the
`
`other claims”); accord. GREE, Inc. v. Supercell Oy, No. 2:19-CV-00161, 2020 U.S. Dist. LEXIS
`
`14412, *4-5 (E.D. Tex. Jan. 29, 2020); CXT Sys. v. Acad., Ltd., No. 2:18-CV-00171, 2019 U.S.
`
`Dist. LEXIS 51915, *13-15 (E.D. Tex. March 19, 2019).
`
`“In all cases, the representativeness inquiry must be ‘directly tethered to the claim
`
`language.’” PPS Data, 404 F. Supp. 3d. at 1031. “[A] claim is not representative merely because
`
`it generally deals with the same subject matter as the other asserted claims,” and “[i]n general,
`
`claims in one patent will not represent claims in another patent because patents must contain
`
`distinct inventions.” Id. Only if a defendant meets its burden of showing “a prima facie case
`
`demonstrating representativeness” (which Apple has not done) is a patent owner required to
`
`“identify limitations that are present in the asserted claims but that are not represented by the
`
`allegedly representative claim.” Id.; see also id. at 1032 (“if the plaintiff identifies legally
`
`distinctive limitations, then any claims which contain those limitations are excluded from the
`
`scope of the relief sought by the defendant”). “[I]n close cases, courts should err on the side of
`
`finding a claim is not representative.” Id. at 1033.
`
`As an initial (and dispositive) matter, Apple does not make “a prima facie case
`
`demonstrating representativeness” of Claim 1 of the ’317 Patent. Apple merely makes the
`
`conclusory statements that “[t]he ’317 Patent, Claim 1 is representative” and that “[t]he other
`4
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 11 of 24 PageID #: 24152
`
`
`
`
`asserted claims recite only minor variations.” Mot. at 3. Apple makes no attempt to tether its
`
`statement to the claim language of the challenged claims, address Claim 3 of the ’498 Patent
`
`(another asserted claim) at all, or explain why it contends that any “variations” are supposedly
`
`“minor.” Id. Such conclusory statements are insufficient for Apple to carry its burden. See CXT
`
`Sys., 2019 U.S. Dist. LEXIS 51915 at *14 (“Defendant does not provide any further support for
`
`its conclusory statement that the other claims of the patent are substantially and substantively
`
`similar to Claim 16”); GREE, 2020 U.S. Dist. LEXIS 14412 *5 (“Supercell does not explain
`
`why… or how the Court could conclude that ‘there are no legally relevant distinctions’”).
`
`There are substantial and legally relevant distinctions between the challenged claims of
`
`the ’317 Patent, the ’498 Patent, and the ’999 Patent, which will be addressed according to the
`
`Alice framework below. Accordingly, the use of a representative claim is not appropriate.
`
`B.
`
`The Challenged Claims are Valid at Alice Step-One
`
`None of the challenged claims are directed to an abstract idea. Rather, while the specifics
`
`vary between the claims, as explained above, each is directed to a mobile device comprising a
`
`particular combination of components that together constitute a “concrete improvement[] in the
`
`recited… technology,” such as “a specific improvement to the way [mobile devices] operate.”
`
`Enfish, 822 F.3d at 1334, 1336.
`
`For each of the Navigation Patents, the inventors set out “to provide a portable terminal
`
`with the function of walking navigation, which can supply location information easier for the
`
`user to understand during walking with use of a narrow screen.” ’317 Patent at 2:52-55. At the
`
`time, existing mapping applications had shortcomings that made them suboptimal for use on a
`
`mobile device. For example, such applications were frequently “optimized on the assumption
`
`that the maps can be displayed at a resolution… of personal computers” rather than the small
`
`screens of the day’s mobile devices. Id. at 1:47-49. Thus, the mapping applications were “not
`5
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 12 of 24 PageID #: 24153
`
`
`
`
`always easy for walkers to understand” on small screens, or provided information in a format
`
`that was “too wide to obtain detailed information” or on a “plurality of pages.” Id. at 2:5-11.
`
`These challenges were also acknowledged by engineers at Georgia Tech at that time.2
`
`The limited hardware of the day’s mobile devices also provided hurdles. For example, the
`
`inventors noted that “character information is often supplied as contents” on the screens of the
`
`mobile devices, but “when the user wants to know such a spatial position as a place and a route,”
`
`text-based displays would not work well. Id. at 2:26-31; see also Ex. A (Paradiso CC Dep. Tr.) at
`
`44:17-23 (“one of the things the patent[s] talk[] about, very definitely,” is “enabling the
`
`navigation information to be displayed on a small-sized screen in a manner easily understood to
`
`the user/walker”). Moreover, there was an input problem: the portable devices were “just
`
`provided with some button keys including dialing buttons used as input devices, so they will not
`
`[be] able to cope with inputs of complicated retrieving conditions.” ’317 Patent at 2:32-36. Even
`
`Apple’s expert acknowledged that limited hardware presented challenges for map displays. See
`
`Ex. D (Paradiso Inv. Rep.) at ¶ 269 (“At the time in the late 1990s, the capabilities of portable
`
`computer displays, memories, and processors were more limited. Presenting full map displays
`
`with routes could not be done effectively or feasibly, particularly in lower cost portable
`
`devices”); Ex. A (Paradiso CC Dep. Tr.) at 38:9-18, 40:19-24, 39:16-40:11 (discussing problems
`
`with the then-prevalent mobile devices that used GPS or cellular services alone).
`
`The inventors’ ideas thus got around these problems by equipping a mobile device with a
`
`device for getting its location as well as its orientation, paired with new user interfaces. Id. at
`
`2:62-3:4. This provides a specific solution—even Apple’s expert testified that “if you really look
`
`2 See Ex. C, (“Cyberguide: A Mobile Context-Aware Tour Guide”) (APL-MAXELL_00713087)
`at 17 (it was “computationally overwhelming to manage the display” and “it was difficult to
`control the display of the decorations” on a map in a portable device) (emphasis added).
`
`6
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 13 of 24 PageID #: 24154
`
`
`
`
`at what this device is, the patent gives a very clear, clear description of it.” Ex. A (Paradiso CC
`
`Dep. Tr.) at 67:3-18. Thus, the inventors made it “possible to realize [] user-friendly interface[s]
`
`that enable[] the user to understand displayed items intuitively.” ’317 Patent at 3:16-18. By
`
`providing for particular hardware with functionality that is combined with features of various
`
`user interfaces, each of the ’317 Patent, ’498 Patent, and ’999 Patent are “directed to a specific
`
`asserted improvement to the functionality of the [portable terminal] system itself.” Uniloc USA,
`
`Inc. v. LG Elecs. USA, Inc., 957 F.3d 1303, 1309 (Fed. Cir. 2020).
`
`1.
`
`Claims 1 and 17 of the ’317 Patent (“Walking Navigation Claims”)
`
`Claims 1 and 17 of the ’317 Patent are “generally directed to providing a portable
`
`terminal with specific devices that provide a pedestrian with navigation information about his/her
`
`walk including, for example, route information, destination symbol, starting point symbol, and
`
`present place identification.” Ex. E (Inf. Rep. of Dr. Rosenberg) at ¶ 59.
`
`Indeed, the claim language (see Appendix 1) confirms that these claims are patent
`
`eligible because they recite particular hardware and “require a specific, structured graphical user
`
`interface paired with a prescribed functionality directly related to the graphical user interface’s
`
`structure that is addressed to and resolves a specifically identified problem in the prior state of
`
`the art.” Data Engine Techs. LLC v. Google LLC, 906 F.3d 999, 1009-10 (Fed. Cir. 2018); Core
`
`Wireless, 880 F.3d at 1362 (the asserted claims “are directed to an improved user interface for
`
`computing devices, not to the abstract idea of an index”); IDB Ventures, LLC v. Charlotte Russe
`
`Holdings, Inc., No. 2:17-CV-660, 2018 U.S. Dist. LEXIS 186215, *6-10 (E.D. Tex. Oct. 31,
`
`2018) (“the Federal Circuit has applied that principle in finding specific user interfaces in
`
`computer-related inventions to be patent-eligible and not abstract”).3
`
`3 Apple’s chosen precedents about “navigation,” such as Rothschild v. Geotab USA (see Mot. at
`10-11), are inapposite. Not one of the cases that Apple cites addressed patents that “require[d]
`7
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 14 of 24 PageID #: 24155
`
`
`
`
`The “specific, structured graphical user interface” required by Claims 1 and 17 of the
`
`’317 Patent is such that the display:
`
`
`
`
`
`
`
`
`“displays positions of said destination and said present place, and a relation of said
`direction and a direction from said present place to said destination” (Claims 1 and 17);
`“changes according to a change of said direction of said portable terminal orientation
`for walking navigation” (Claims 1 and 17);
`“displays said route and displays a direction of movement by the arrow” (Claim 17);
`“displays said route with a bent line using symbols denoting starting and ending points
`and displays symbols denoting said present place on said route” (Claim 17).
`
`As construed by the Court, these interface requirements are “paired with a prescribed
`
`functionality directly related to the graphical user interface’s structure,” specifically the
`
`functionality of the following hardware required to perform specific, Court-construed functions:
`
`
`
`“a wireless or cellular antenna, a GPS, a PHS, or the like; a data receiver; and a CPU for
`analyzing received data; or equivalents thereof” with a function of “getting a location
`information denoting a present place of said portable terminal” (Claims 1 and 17) (see
`Dkt. 235 at 15);
`“a compass, gyroscope, and/or sensor such as a clinometer in conjunction with a CPU,
`or equivalents thereof” with a function of “getting a direction information denoting an
`orientation of said portable terminal” (Claims 1 and 17) (see Dkt. 235 at 7-8);
`“an input device for inputting a destination” (Claims 1 and 17); and
`“CPU 71 and device for data communication 76 of a portable telephone and a Personal
`Handyphone System (PHS) terminal (Figure 10, ’317 Patent at 9:40–50); or equivalents
`thereof” with a function of “retrieving a route from said present place to said
`destination” (Claim 17) (see Dkt. 235 at 18).
`For example, displaying the position of the destination, present place, and their relation requires,
`
`
`
`
`
`
`and is thus paired with, the functionality of a device for “getting location information” of the
`
`present place, a device for “inputting a destination,” and a device for “retrieving a route”
`
`between the two. And for the display to change according to the direction of the portable
`
`terminal orientation, it requires, and is thus paired with, the functionality of a device for “getting
`
`specific, structured graphical user interface paired with a prescribed functionality directly related
`to the graphical user interface’s structure that is addressed to and resolves a specifically
`identified problem in the prior state of the art.” Data Engine Techs., 906 F.3d at 1009-10.
`8
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 15 of 24 PageID #: 24156
`
`
`
`
`a direction information denoting an orientation of said portable terminal.”
`
`Thus, this combination of functionality paired with specific features of a graphical user
`
`interface solves the problems identified by the inventors in the prior art, such as the poor
`
`accuracy and performance of then-existing navigation applications, which is patent eligible. Data
`
`Engine Techs., 906 F.3d at 1009-10; see also CXT Sys., 2019 U.S. Dist. LEXIS 51915 at *13 (a
`
`user interface requiring that “two different display regions with specific information are
`
`presented in the display and [are] simultaneously visible” was patent eligible because it was
`
`“directed to a technology-based solution to a problem that existed with message boards at the
`
`time of the invention”). Accordingly, Claims 1 and 17 of the ’317 Patent are patent eligible.
`
`2.
`
`Claim 3 of the ’999 Patent (“Locate a Friend Claim”)
`
`Claim 3 of the ’999 Patent is “directed to providing a portable terminal with specific
`
`devices that provide a pedestrian with location information about another portable terminal that
`
`may, for example, be owned by his friend.” Ex. E (Inf. Rep. of Dr. Rosenberg) at ¶ 60.
`
`Indeed, as with Claims 1 and 17 of the ’317 Patent, Claim 3 of the ’999 Patent is directed
`
`to a patent eligible device, which includes a “specific, structured graphical user interface paired
`
`with a prescribed functionality directly related to the graphical user interface’s structure.” Data
`
`Engine Techs., 906 F.3d at 1009-10. Specifically, the claimed device enables a graphical user
`
`interface to display direction and distance information to another, specified portable terminal, as
`
`well as a visual representation of the user’s location as well as the other device’s location. ’999
`
`Patent at 10:38-51, 10:56-61.
`
`Thus, the “specific, structured graphical user interface” required by Claim 3 of the ’999
`
`Patent is such that the claim requires the display of:
`
`
`
`“a direction from said present place to the location of said another portable terminal”
`[which] “is displayed with the distance information between said locations to supply
`route guidance information as said walking navigation information”;
`9
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 16 of 24 PageID #: 24157
`
`
`
`
`
`
`“wherein said direction from said present place to the location of said another portable
`terminal is displayed using the symbols denoting the said present location and said
`location of another portable terminal.”
`
`As construed by the Court, these interface requirements are also “paired with a prescribed
`
`functionality directly related to the graphical user interface’s structure,” specifically the hardware
`
`construed by the Court as a part of means-plus-functions claim elements, with functionality that
`
`enables the distinct user interface functionality claimed by Claim 3. Dkt. 235 at 7-8, 15, 18 (e.g.,
`
`GPS, data receiver, CPU, compass/gyroscope, device for data communication, with specified
`
`functions required to implement the claimed user interfaces).
`
`For example, displaying the direction to another user’s portable terminal using distance
`
`information and a visual representation of the user’s location as well as the other device’s
`
`location requires, and thus is paired with, the hardware requirements specified by the claims
`
`including a CPU and a device for data communication of a portable telephone and a PHS.
`
`Thus, this combination of functionality paired with specific features of a graphical user
`
`interface solves the problems identified by the inventors in the prior art relating to getting the
`
`location of a friend’s device or getting the location of a user’s own device. Accordingly, Claim 3
`
`of the ’999 Patent is also patent eligible at Alice step-one.
`
`3.
`
`Claim 3 (“Walking Navigation and Display Orientation Claim”) and
`Claim 13 (“Locate a Friend and Display Orientation Claim”) of the ’498
`Patent
`
`Claim 3 of the ’498 Patent is “generally directed to providing a portable terminal with
`
`specific devices that provide a pedestrian with navigation information about his/her walk
`
`including, for example, route information, starting and ending points and lines providing
`
`navigation information.” Ex. E (Inf. Rep. of Dr. Rosenberg) at ¶ 61. And Claim 13 of the ’498
`
`Patent is “generally directed to providing a portable terminal with specific devices that provide a
`
`pedestrian with location information about another portable terminal and also providing a full
`
`10
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 438 Filed 07/24/20 Page 17 of 24 PageID #: 24158
`
`
`
`
`route from the st

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