throbber
Filed By: Vivek Ganti (vg@hkw-law.com) Reg. No. 71,368; and
`
`
`Sharad K. Bijanki (sb@hkw-law.com) Reg. No. 73,400
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_________________
`
`TV MANAGEMENT, INC., D/B/A GPS NORTH AMERICA
`Petitioner,
`
`v.
`
`PERDIEM CO., LLC.
`
`Patent Owner
`
`_________________
`
`Case IPR2016-01061
`
`U.S. Patent 8,223,012
`
`_________________
`
`PETITIONER’S REPLY
`
`
`
`i
`
`
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`
`I. Claim Construction .............................................................................................. 1
`
`A. The broad view: the administrator and first user may be the same person ... 2
`
`B.
`
`The narrow view: the administrator and first user are mutually exclusive ... 4
`
`II.
`
`Fast Anticipates the Challenged Claims ........................................................... 4
`
`A.
`
`Patent Owner mischaracterizes the teachings of Fast (Ex. 1003) ................. 4
`
`B.
`
`Fast anticipates independent claim 1 and dependent claims 2-6 .................. 6
`
`1. A Notification Scheme Number is an IAC specified by a first user: ............ 6
`
`2. A “user type” is an IAC specified by a first user .......................................... 7
`
`C.
`
`Fast anticipates independent claim 18 and dependent claims 19 and
`
` 22-24 ....................................................................................................................10
`
`D.
`
`Fast anticipates independent claim 7 and dependent claims 8-13. .............11
`
`III. Fast and Haney render the Challenged Claims obvious .................................12
`
`A. The teachings of Haney, when combined with Fast, render the challenged
`
`claims obvious ......................................................................................................12
`
`B. A POSITA would be motivated to combine the teachings of Fast with the
`
`teachings of Haney ................................................................................................13
`
`
`
`ii
`
`

`

`C.
`
`Patent Owner’s licensing evidence does not amount to a secondary
`
`consideration to rebut the obviousness case .........................................................16
`
`IV. Conclusion ......................................................................................................20
`
`V. Certification of Compliance ...........................................................................20
`
`
`
`iii
`
`
`
`
`
`

`

`TABLE OF AUTHORITIES
`
`CASE LAW
`
`Federal Circuit Court of Appeals
`
`In re Antor Media Corp., 689 F.3d 1282 (Fed. Cir. 2012) ............................... 17
`
`In re Blaise Laurent Mouttet, No. 2011-1451 (Fed. Cir. June 26, 2012) ......... 14
`
`In re Etter, 756 F.2d 852 (Fed. Cir. 1985) (en banc) ....................................... 14
`
`In re Kahn, 441 F.3d 977 (Fed. Cir. 2006) ....................................................... 14
`
`Novartis AG v. Torrent Pharmaceuticals, Case No. 2016-1352 (Fed. Cir.
`
` April 12, 2017 .............................................................................................. 17
`
`
`
`USPTO, Patent Trial and Appeal Board
`
`CaptionCall, LLC v. Ultratec Inc., IPR2013-00545, paper 67, pp.7-8 (PTAB,
`
` December 1, 2015) ....................................................................................... 14
`
`
`
`FEDERAL REGULATIONS
`
`37 C.F.R. § 42.64 .............................................................................................. 19
`
`37 C.F.R. § 42.65 .............................................................................................. 9, 15
`
`
`
`
`
`
`
`iv
`
`

`

`EXHIBIT LIST1
`
`Ex. 1001 U.S. Patent No. 8,223,012 (“’012 Patent”)
`
`Ex. 1002
`
`The file history of the ’012 Patent
`
`Ex. 1003 U.S. Patent No. 7,327,258 (“Fast”)
`
`Ex. 1004 U.S. Provisional Patent App. No. 60/542,208 (“Fast Provisional”)
`
`Ex. 1005 U.S. Patent No. 7,353,034 (“Haney”)
`
`Ex. 1006 Discrete Wireless’s Marcus GPS Fleet Management Application
`
`Product Brochure (“Marcus”)
`
`Ex. 1007 U.S. Patent App. No. 14/629,336, Response to Non-Final Office
`
`Action (Feb. 11, 2016)
`
`Ex. 1008
`
`Success Stories in Fleet Tracking (Sept. 1, 2005)
`
`Ex. 1009
`
`Supporting Declaration of Dr. Stephen Heppe
`
`Ex. 1010 Declaration of Vivek Ganti, Esq.
`
`Ex. 1011 Declaration of William Steckel
`
`Ex. 1012 Declaration of Steven. G. Hill
`
`Ex. 1013 Declaration of Michael Femal
`
`Ex. 1014 Declaration of Dr. Heppe filed in IPR2016-01064
`
`Ex. 1015
`
`Infringement Complaints Filed by Patent Owner
`
`
`1 Newly filed exhibits in bold.
`
`
`
`v
`
`

`

`The Board instituted trial on all claims and all grounds which include claims
`
`1-13, 18, 19, 22-24 of the ’012 Patent. (Inst. Dec., paper 11, pp. 1-2). Patent
`
`Owner filed its Corrected Patent Owner Response (POR, paper 36) addressing only
`
`independent claims 1, 7, and 18. Petitioner submits the following Reply
`
`demonstrating that the challenged claims are anticipated and rendered obvious by a
`
`preponderance of the evidence.
`
`I. Claim Construction
`
`Claim 1 requires “an administrator” and “a first user.” The issue is whether
`
`these two entities can be the same under BRI. Patent Owner’s entire argument for
`
`patentability stems from interpretation that these must be separate. (POR, p.7,
`
`stating that “this first user is expressly distinguished from the overarching
`
`‘administrator.’”). Patent Owner asserts the following:
`
`The users themselves (as opposed to the administrator) are given the
`
`power to specify an “information access code” that in turn specifies
`
`what other users will be allowed access to location information. This
`
`flexibility and user control is a hallmark of the invention, which the
`
`specification discusses again and again and which is claimed in every
`
`claim at issue in this IPR.
`
`(POR, p.1).
`
`
`
`Petitioner disagrees. Under the BRI standard, there is no reason why an
`
`administrator should be precluded from being a “first user.” In practice, system
`
`administrators are often participants (users) as well. Patent Owner has pointed to
`
`
`
`1
`
`

`

`nothing in the drawings, specification or prosecution history mandating a narrower
`
`construction. As shown herein, the intrinsic evidence of the ‘012 Patent
`
`contradicts the Patent Owner’s stated view. Under this broader interpretation of
`
`the claim, Patent Owner concedes that its claims are invalid.
`
`Having said that, and fully expecting that Patent Owner would take the
`
`narrower view in a failing attempt to protect the patentability of these overbroad
`
`claims, the original Petition crafted arguments assuming that the “administrator”
`
`authorizes a separate “first user.” For example, Argument 1 of the Petition
`
`assumes the Retailer is the administrator who authorizes a Subscriber as the first
`
`user. (Petition, p.16). Next, Argument 2 shows a Subscriber as the administrator
`
`who authorizes an organization’s manager as the first user. (Petition, p.24). The
`
`Board instituted trial on these arguments without a need to consider the broader
`
`view of the claims where an administrator and first user may be the same entity.
`
`
`
`Regardless of how the Board resolves the claim construction question, the
`
`Petition demonstrates the invalidity of these claims.
`
`A. The broad view: the administrator and first user may be the same
`person
`
`The intrinsic evidence supports this broad view. For example, the
`
`specification states: “The mother sets an object location information access code such
`
`that only the mother, specifically, a PDA or other computing device used by the
`
`mother, has authorized access to the object location information of the vehicle 202.”
`
`
`
`2
`
`

`

`(Ex. 1001, 9:23-26). Here the mother is an administrator who authorizes herself as a
`
`first user by setting her own information access code.
`
`Next, the claims of the ’012 Patent state “a second user identification code that
`
`is different from the first identification code.” Similarly, in the related patent, U.S.
`
`Pat. No. 8,149,113, which shares the same specification as the ’012 Patent, the
`
`patentee included claim limitations stating “a second user that is different from the
`
`first user” and “a third user that is different from the first and second users.” (See
`
`Claim 31 of 8,149,113). No such limitations exist in the claims of the ’012 Patent
`
`where the patentee is expressly differentiating the administrator from the first user.
`
` In addition, the Board, reading the same specification in a related IPR
`
`preliminarily concluded that “an ‘administrator’ and an ‘authorized user,’ construed
`
`according to their broadest reasonable interpretation, are not mutually exclusive.”
`
`(IPR2016-01063, institution decision, paper 20, p.10). For these reasons, “an
`
`administrator” and “a first user” are not mutually exclusive under BRI.
`
`Assuming this to be the case, Patent Owner’s patentability arguments
`
`collapse. Specifically, Fast discloses a super administrator as discussed in the POR
`
`who creates User types (which Patent Owner tacitly admits discloses information
`
`access codes). Patent Owner surmises that the only difference between Fast and
`
`the challenged claims is the suspect allegation that Fast is a pre-fixed hierarchical
`
`system where a super administrator controls the system, and where users cannot.
`
`
`
`3
`
`

`

`(POR, pp.1-2). Of course, if the super administrator (or any other administrator for
`
`that matter) authorizes himself as a user, there is no patentable distinction between
`
`Fast and the challenged claims.
`
`B. The narrow view: the administrator and first user are mutually
`exclusive
`
`The Petition analyzed the claims under the interpretation that the
`
`administrator and first user are mutually exclusive. The Board instituted review
`
`according to that analysis. The remainder of this Reply demonstrates why the
`
`challenged claims are unpatentable under this narrower view.
`
`II. Fast Anticipates the Challenged Claims
`
`A. Patent Owner mischaracterizes the teachings of Fast (Ex. 1003)
`
`Patent Owner’s reading of Fast boils down to a single assertion “Fast teaches
`
`a pre-fixed hierarchical system where the administrator – not the user – is in
`
`control of conveying location information.” (POR, pp.1-2). In other words, Patent
`
`Owner alleges that Fast is a rigid hierarchy unlike the ’012 Patent which is
`
`supposedly “flexible.” This “lack of flexibility” argument misses the mark. At the
`
`very outset, Fast states: “The system includes resellers, retailers, users and
`
`subscribers in a flexible relationship to enhance the ease in the system operation.”
`
`(Ex. 1003, Abstract (emphasis added)).
`
`In a related IPR, Dr. Heppe explains that Fast’s system “is flexible, and
`
`allows the creation of an unlimited number of users, each with a specified level of
`
`
`
`4
`
`

`

`access privilege.” (Ex. 1014, ¶30). In addition, a subscriber’s portal allows a user
`
`to “add, delete, and update system users, and assign an access level indicating
`
`which functionality that user will be restricted from using. 42:14-52; FIG. 16-1, R.
`
`504, 505c, 512, and 514; FIG. 16-2, 530, 532, and 534.” (Id., citing Ex. 1003).
`
`Dr. Heppe identified Fast’s flexibility in crafting groups of users with different
`
`access levels:
`
`
`
`(Id., ¶¶45-46). Here, Parents AX and AY, under a subscriber account, may track
`
`their children (dependents A1X and A1Y) by assigning guardians to those
`
`children. (Id.). The POR’s patentability arguments unravel with a showing that
`
`Fast teaches the opposite of a “pre-fixed hierarchical system.”
`
`
`
`5
`
`

`

`B. Fast anticipates independent claim 1 and dependent claims 2-6
`
`Claim 1 states:
`
`A method for conveying user location information, comprising:
`
`interfacing with an administrator that authorizes a first user
`
`associated with a first user identification code to access an object
`
`location information from a location information source associated with
`
`a second user identification code that is different from the first
`
`identification code; and
`
`conveying the object location information to a third user based
`
`on an information access code specified by said first user, said
`
`information access code being associated with a third user identification
`
`code that is different from the first and second user identification codes.
`
`
`
`Patent Owner argues that claim 1 is patentable because Fast does not
`
`disclose the emphasized language above. (POR, p.10). Patent Owner specifically
`
`argues that only a top-level administrator (i.e. Super Administrator) can specify an
`
`information access code (IAC), not a first user (i.e. any other user). Yet Fast
`
`identifies numerous system participants with administrative rights and performing
`
`administrative functions other than the Super Administrator. The Petition presents
`
`separate ways of showing how Fast teaches a conveyance based on an “access
`
`code specified by said first user” who is not a super administrator.
`
`1.
`
`A Notification Scheme Number is an IAC specified by a first user:
`
`In one way, Fast teaches an administrator (retailer) who authorizes a first user
`
`(subscriber) that conveys location information of a second user (a dependent) to a
`
`
`
`6
`
`

`

`third user (a guardian). (Petition, pp.16-24). Fast discloses an IAC (e.g., notification
`
`scheme number) that is specified by the first user (e.g., subscriber). (Id., p.23 citing to
`
`Ex. 1003, 35:43-46, 35:65-67, 36:1-6, and Ex. 1009, ¶¶66-69). The Board instituted
`
`trial based, at least in part, on this argument. (Inst. Dec., paper 21, p.10 stating
`
`“Insofar as an access code for that notification scheme, Fast discloses that the user
`
`selects ‘suitable entities . . . from a list of available entities,’ one of which includes ‘a
`
`guardian.’”).
`
`The POR lacks any discussion relating to Petitioner’s “notification scheme”
`
`argument. Patent Owner’s decision to not respond to this argument constitutes an
`
`outright waiver of this issue. (Scheduling Order, paper 22, p.3; see also In re:
`
`Nuvasive, Inc., Case No. 15-1670 at *6 (Fed. Cir. 2016). As such, the Patent Owner
`
`should not be permitted to address this issue in any further proceedings such as the
`
`final hearing on this matter.
`
`2.
`
`A “user type” is an IAC specified by a first user
`
` The Petition separately shows how Fast’s “User type” teaches an AIC
`
`specified by the subscriber (as opposed to it being specified by an administrator such
`
`as the retailer or super administrator). (Petition, p.15 stating “Fast describes a variety
`
`of subscriber functions, depending on the particular user’s level of access privilege,
`
`such as managing scenarios and managing user types (id., p.22, FIG. 16-2, boxes
`
`518 and 530)”). As Patent Owner correctly notes, the Board also instituted trial
`
`based on mapping Fast’s “User type” onto the claimed information access code.
`
`
`
`7
`
`

`

`(POR, p.13 citing to the institution decision, p.8). Unlike the “notification scheme
`
`number” argument presented above, Patent Owner addressed this point in its POR.
`
`Patent Owner asserts that only the Super Administrator can create user
`
`types. (POR, pp.15-16; see also id., p.12 stating “users other than the Super
`
`Administrator cannot define User types.”). This interpretation of Fast is flawed.
`
`Fast teaches a subscriber portal, shown in FIGS. 16-1 and 16-2, that allows a
`
`subscriber to “manage user types” (item 530), “add/update/delete system users”
`
`(item 532), and “assign access levels to system users” (item 534).” (Ex. 1003,
`
`FIGS. 16-1 and 16-2; 42:14-16).
`
`Contrary to what Patent Owner believes, super administrators are not the
`
`only individuals who control users and user types. The super administrator uses an
`
`“Administrator Module” of FIG. 13 (Ex. 1003, 2:33-34 and FIG. 13, item 363).
`
`This is different than Subscribers who use their own portals (id. at FIG.16, 42:14-
`
`16) that also allow adding/updating new users and managing user types through
`
`assignment of different access levels for different users. (Id., 2:33-34; id., FIG. 14-
`
`2, items 412, 413, and 416; id., FIG. 16-2, items 530, 532, and 534).
`
`Patent Owner cites two pieces of evidence to support its selective reading of
`
`Fast. First, Patent Owner relies on the following statement in Fast: “User types
`
`363 as specified by the Super Administrator using the administration manager
`
`367.” (POR, p.10 citing to Ex. 1003, 37:59-61). This statement does not preclude
`
`
`
`8
`
`

`

`other users such as subscribers from further managing user types. In fact, the
`
`opposite is true. (Ex. 1003, at FIG. 16-2, item 530). Patent Owner’s limited
`
`reading of Fast is at odds with the intrinsic evidence.
`
`Second, Patent Owner cites to its expert Dr. Schonfeld, who concludes that
`
`“Users other than the Super Administrator cannot define User types.” (Schonfeld
`
`Decl., filed as Ex. 2011, ¶19). This conclusory statement cites to no authority and
`
`flatly contradicts, inter alia, the subscriber portal of FIG. 16-2. (See Ex. 1003, at
`
`FIG. 16-2, item 530). Dr. Schonfeld mistakenly refers to FIG. 14 as applying to all
`
`users including subscribers. (See Schonfeld Decl., ¶19). He also refers to the
`
`following statement in Fast: “Each User type other than the Super Administrator
`
`has specific restrictions on access to the various functions within the Guardian
`
`Administration Module” (Id., citing Ex. 1003, 37:61-64). However, this statement
`
`says nothing about precluding other users from adding user types. Dr. Schonfeld’s
`
`opinion should be given no weight because it contradicts the teachings of Fast as a
`
`whole. In addition, he failed to disclose the underlying facts on which his opinion
`
`is based. (37 C.F.R. §42.65). As such, his opinion is entitled to no weight.
`
`For these reasons, User types are not “hard-wired into Fast’s system by the
`
`Super Administrator,” (POR, p.12), as Patent Owner suggests. (See Ex. 1003,
`
`42:47-48 stating “The managing of User types 530 includes adding, deleting and
`
`
`
`9
`
`

`

`updating system Users 532” which is part of FIG. 16’s subscriber portal
`
`functionality).
`
`As shown, Fast anticipates claim 1 regardless of the Board’s construction.
`
`Moreover, Patent Owner presented no separate arguments for dependent claims 2-
`
`6. Those claims are anticipated for reasons stated in the Petition.
`
`C. Fast anticipates independent claim 18 and dependent claims 19 and 22-
`24
`
`Patent Owner states that “claim 18 is substantially identical to claim 1” and
`
`then presents no arguments separate from those presented in claim 1. (POR, p.8).
`
`Again, Patent Owner’s assertion is that the “first user is expressly distinguished
`
`from the overarching ‘administrator.’” (POR, p.7). Patent Owner clings to this
`
`assertion – “overarching” is never used in any claim, in the written description, or
`
`in any figure − as the premise of its Fast-related arguments. However, claim 18
`
`does not recite an “administrator.” Thus, Patent Owner’s arguments relating to
`
`claim 1 do not apply to claim 18.
`
`To elaborate further, Patent Owner contends that Fast does not disclose
`
`“providing an interface to a first computing device associated with the first user to .
`
`. . . define an information package access code” and “conveying the information
`
`package . . . . . based on said information package access code” in claim 18. (POR,
`
`pp.15-16). This conclusion is flawed. Patent Owner does not account for the
`
`portal of FIG. 16 which shows how a first user (e.g., a subscriber or a user
`
`
`
`10
`
`

`

`authorized by a subscriber) uses an interface to set scenarios and manage User
`
`Types to ultimately convey information. (Ex. 1003, FIG. 16-2, items 518, 520, and
`
`530).
`
`Fast anticipates claim 18 for the reasons discussed above. Moreover, Patent
`
`Owner presented no separate arguments for dependent claims 19 and 22-24. All of
`
`these claims are anticipated for reasons stated in the Petition.
`
`D. Fast anticipates independent claim 7 and dependent claims 8-13.
`
`Patent Owner states that “claim 7 is a bit different in terms of verbiage, but
`
`recites a similar concept” and then presents no arguments separate from those
`
`presented in claim 1. (POR, pp.8-9). Unlike claim 1, claim 7 claims an
`
`“administrator system,” not an administrator. In addition, claim 7 does not claim a
`
`“first user.” As was the case with respect to claim 18, this suspect argument that
`
`the “first user is expressly distinguished from the overarching ‘administrator’”
`
`does not apply to claim 7. Claim 7 states “an information access code that
`
`specifies a user group” and “wherein an object location information provided by
`
`the location information source is conveyed based on the information access code.”
`
`Patent Owner believes that a “first user” is implied based on the claim language
`
`that “an information access code that specifies a user group.” (See POR, p.9).
`
`However, nothing in claim 7 requires a user to specify an IAC. Again, Patent
`
`
`
`11
`
`

`

`Owner’s arguments relating to claim 1 do not apply to claim 7, which does not
`
`recite the salient limitations at issue in the analysis of claim 1 invalidity.
`
`Fast anticipates claim 7 for the reasons discussed in the Petition. Patent
`
`Owner’s assertions to the contrary confuse the limitations of claim 1 with those of
`
`claim 7. Moreover, Patent Owner presented no separate arguments for dependent
`
`claims 9-13. Those claims are also anticipated for reasons stated in the Petition.
`
`III. Fast and Haney render the Challenged Claims obvious
`
`A. The teachings of Haney, when combined with Fast, render the
`challenged claims obvious
`
`Patent Owner believes Haney is limited to “two-way” information sharing
`
`where two parties are granted mutual access to each other’s location. (POR, p.17).
`
`Based on this assertion, Patent Owner concludes that “Haney fails to disclose the
`
`’012 claim elements that give users unfettered flexibility to determine which users
`
`to convey location information to.” (POR, p.18).
`
`First, Petitioner respectfully disagrees that Haney precludes one-way
`
`information sharing. Haney explains how it is advantageous to use a
`
`“unidirectional” location information sharing environment in the context of setting
`
`up a “corporate supervision” network:
`
`Corporations that wish to monitor the locations of their employees can
`
`use the system of the invention by using a corporate passcode. . . . In
`
`one embodiment, the location information sharing is unidirectional
`
`from employees to supervisor but each employee can see the location
`
`
`
`12
`
`

`

`of other employees on their phones but not the location of the
`
`supervisor.
`
`(Ex. 1005, 17:55-18:1). In this respect, Haney discloses a flexible corporate
`
`structure of supervisors and employees having unidirectional access to location
`
`information.
`
`
`
`Patent Owner believes that it is entitled to a monopoly over certain location
`
`systems because the ’012 Patent was the first to differentiate between the users and
`
`the administrator. (POR, p.1 stating “This flexibility and user control is a hallmark
`
`of the invention[.]”). However, Haney shows that differentiating between
`
`supervisors and employees in a unilateral location information sharing
`
`environment is an obvious concept prior to the time of invention.
`
`Second, Petitioner disagrees that the claims-at-issue are limited to only a
`
`“one-way” or “non-mutual” sharing of information under the BRI standard. Just
`
`because claim 1 claims an “administrator” along with a first, second, and third user
`
`does not preclude “two-way” information sharing. Patent Owner offers no claim
`
`construction analysis to suggest such a narrowing view of the claims under BRI.
`
`B. A POSITA would be motivated to combine the teachings of Fast with
`the teachings of Haney
`
`Petitioner articulates the motivation to combine in its Petition at pages 45-
`
`46. In opposition, Patent Owner relies on Dr. Schonfeld, who testifies that a
`
`POSITA would not have been motivated or even could be able to combine these
`
`
`
`13
`
`

`

`systems, due to their fundamentally different ways of arranging and conveying
`
`information. (POR, p.20 citing Schonfeld Decl., ¶24). Dr. Schonfeld does not draw
`
`any conclusion of non-obviousness but rather limits his opinion on whether a
`
`POSITA would be motivated to physically combine Fast’s system with Haney’s
`
`system. Specifically, Dr. Schonfeld’s analysis focused on the degree of difficulty
`
`of adding software code that implements “an array of simple lists” to the software
`
`code of Fast. (Schonfeld Decl., ¶22). He concluded that it would require
`
`completely re-writing Fast’s software code. (Id., ¶23). For the following reasons,
`
`Dr. Schonfeld’s opinions should be given no weight.
`
`First, his opinions are irrelevant when considering a correct obviousness
`
`analysis. A correct obviousness analysis focuses on whether a POSITA would
`
`have sufficient motivation to combine different teachings to arrive at the claimed
`
`invention. See In re Kahn, 441 F.3d 977, 987-88 (Fed. Cir. 2006). However, “[i]t
`
`is well-established that a determination of obviousness based on teachings from
`
`multiple references does not require an actual, physical substitution of elements.”
`
`In re Blaise Laurent Mouttet, No. 2011-1451, at *15 (Fed. Cir. June 26, 2012)
`
`(emphasis added); see also CaptionCall, LLC v. Ultratec Inc., IPR2013-00545,
`
`paper 67, pp.7-8 (PTAB, December 1, 2015); see also In re Etter, 756 F.2d 852,
`
`859 (Fed. Cir. 1985) (en banc) (“Etter’s assertions that Azure cannot be
`
`incorporated in Ambrosio are basically irrelevant, the criterion being not whether
`
`
`
`14
`
`

`

`the references could be physically combined but whether the claimed inventions
`
`are rendered obvious by the teachings of the prior art as a whole.”).
`
`Here, Dr. Schonfeld testifies that physically combining the two systems
`
`“would necessitate a complete rewriting of the system’s software.” (Schonfeld
`
`Decl., ¶23). This analysis is irrelevant to the issue-at-hand which focuses on
`
`combining the location sharing concepts taught in Fast and Haney. If anything,
`
`Dr. Schonfeld’s testimony suggests that the two systems can be combined when
`
`starting from scratch. Certainly, their relevant teachings are not incompatible,
`
`structurally or otherwise.
`
`Second, Dr. Schonfeld’s opinion that Fast is “a predefined hierarchical
`
`system” contradicts the prior art, as well as Dr. Heppe’s analysis of flexible
`
`subscriber accounts (Ex. 1014, ¶¶45-46). Fast explains that a subscriber has the
`
`flexibility to create different users and user relationships using the subscriber’s
`
`portal. (Ex. 1003, 42:14-52; id., FIG. 16-2, 530, 532, and 534; Ex. 1014, ¶30). This
`
`is not “predefined” as Dr. Schonfeld contends. His opinions should be afforded no
`
`weight given that they contradict the record evidence.
`
`Third, Dr. Schonfeld’s conclusion that Fast is limited to “a predefined
`
`hierarchical system” relies on no evidence or authority. Dr. Schonfeld does not
`
`indicate if he analyzed any code such as the commercial implementation of Fast.
`
`(See Ex. 1008). His characterization of Fast’s “code” should be rejected under 37
`
`
`
`15
`
`

`

`C.F.R. §42.65(a), which requires an expert to disclose the underlying facts or data
`
`on which the opinion is based.
`
`Fourth, Dr. Schonfeld’s opinions consider ways that Fast and Haney’s code
`
`may be implemented, but fail to consider other potential implementations. For
`
`example, Dr. Schonfeld states that “predefined hierarchical information structures
`
`may be organized in a dynamic nested tree structure” but fails to consider other
`
`possible implementations of predefined hierarchical information structures.
`
`(Schonfeld Decl., ¶22 (emphasis added)). The same deficiency appears in Dr.
`
`Schonfeld’s analysis of Haney. (Id.). There, he testifies that Haney “could consist
`
`of an array of simple lists” but fails to consider other implementations of Haney
`
`when opining on his physical combination of Fast and Haney. (Id. (emphasis
`
`added)). Thus, in addition to lacking merit, his analysis is incomplete.
`
`The Petition and supporting testimony of Dr. Heppe sets forth a sufficient
`
`rationale to combine the teachings and concepts disclosed in Fast and Haney in a
`
`manner proving obviousness of the challenged claims. Other than Dr. Schonfeld’s
`
`conclusory and incorrect assertions, the POR presents no counter to the Petitioner’s
`
`motivation to combine.
`
`C. Patent Owner’s licensing evidence does not amount to a secondary
`consideration to rebut the obviousness case
`
`Patent Owner appears to have extracted several licenses through its “sue and
`
`settle” strategy. (See Whitehurst Decl., filed as Ex. 2012, ¶2). All licensees were
`
`
`
`16
`
`

`

`sued by Patent Owner who asserted multiple patents including the ‘012 Patent.
`
`(See Ex. 1015, a collection of complaints filed by Patent Owner against the
`
`licensees). Patent Owner believes that its settlement licenses amount to a showing
`
`of “industry respect for the invention,” a secondary consideration of non-
`
`obviousness. (POR. pp.20-21). Petitioner disagrees.
`
`To establish a secondary consideration, a patent owner must show a nexus
`
`“between the evidence and the merits of the claimed invention.” Novartis AG v.
`
`Torrent Pharmaceuticals, Case No. 2016-1352, at pp.24-25 (Fed. Cir. April 12,
`
`2017). Specifically, the identified secondary consideration must be directed to
`
`what was not known in the prior art. (Id.). In this case, Patent Owner alleges that
`
`“flexibility and user control is a hallmark of the invention” (POR, p.1), but offers
`
`no evidence that a license was taken specifically for this reason. In any event, this
`
`Reply shows that flexibility and user control are known in the prior art. (See, e.g.,
`
`Ex. 1003, Abstract).
`
`In addition, the law distinguishes between licenses extracted from litigation
`
`and licenses due to the merits of the invention. See In re Antor Media Corp., 689
`
`F.3d 1282, 1293-94 (Fed. Cir. 2012) (“Antor”). In Antor, the Federal Circuit held:
`
`Antor, beyond alleging the existence of a number of licenses, has not
`
`asserted any nexus between the merits of the invention and the
`
`licenses themselves. See In re GPAC Inc., 57 F.3d 1573, 1580
`
`(Fed.Cir.1995). Antor merely lists the licensees and their respective
`
`
`
`17
`
`

`

`sales revenue. The licenses themselves are not even part of the record.
`
`Antor provides no evidence showing that the licensing program was
`
`successful either because of the merits of the claimed invention or
`
`because they were entered into as business decisions to avoid
`
`litigation, because of prior business relationships, or for other
`
`economic reasons. The Board was thus correct in holding that the
`
`existence of those licenses is, on its own, insufficient to overcome the
`
`prima facie case of obviousness.
`
`(Id.). The instant case is no different. Patent Owner has not 1) shown any reason
`
`why a license was taken other than to avoid litigation as a pure business decision,
`
`2) made any license part of the record, and 3) identified a nexus between the merits
`
`of the invention reflected in any claim of the ’012 Patent (as opposed to numerous
`
`other patents licensed in the same settlement agreements) and the licenses
`
`themselves.
`
`
`
`In fact, some of the licensees’ activity demonstrate no respect for the
`
`invention. GPS North America, the Petitioner in the instant proceeding, continues
`
`to maintain that this patent is invalid. Similarly, Geotab Inc., Navman Wireless,
`
`and Teletrac, Inc., were initially listed as petitioners in the instant proceeding
`
`believing that the challenged claims are invalid. These parties were eventually
`
`terminated from the proceeding because of settlement, but they never
`
`acknowledged the validity of the claims of the ’012 Patent, only the tremendous
`
`nuisance associated with litigating a case through trial involving numerous patents.
`
`
`
`18
`
`

`

`The only evidence on this matter is the Whitehurst Declaration. But this
`
`evidence should be given no weight because it lacks the specific terms of the
`
`licenses at-issue, including any discussion of the patents and patent applications
`
`licensed, the amount paid, whether validity of any patent was acknowledged, the
`
`costs of litigating as an alternative to settlement, and any specific terms creating a
`
`nexus between settlement and any claim of the ’012 Patent.
`
`Furthermore, Petitioner requested that Patent Owner provide the licenses
`
`pursuant to Fed. R. Evid.

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