throbber
Case IPR2019-00106
`Patent No. 5,699,275
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`___________________________
`
`MICROSOFT CORPORATION,
`Petitioner,
`
`v.
`
`IRON OAK TECHNOLOGIES, LLC.,
`Patent Owner.
`
`___________________________
`
`IPR2019-00106
`U.S. Patent No. 5,699,275
`___________________________
`
`PATENT OWNER PRELIMINARY RESPONSE
`
`PURSUANT TO 37 C.F.R. §42.107(a)
`
`{HD100872.1}
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`TABLE OF CONTENTS
`
`I.
`II.
`
`2.
`
`INTRODUCTION ........................................................................................ 1
`RELATED INTER PARTES REVIEW CASES ........................................... 2
`A.
`Petitions Based Primarily on Sugita and Ballard ............................... 2
`B.
`Petitions Based Primarily on Hapka .................................................. 3
`III. PATENT OWNER’S RESERVATION OF RIGHTS ................................. 3
`IV. LISTING OF FACTS ................................................................................... 4
`V.
`THE PETITION DOES NOT SHOW A REASONABLE
`LIKELIHOOD OF SUCCESS ON ANY GROUND ................................... 5
`A. Grounds A, B, and C: The Petition Does Not Show That
`Sugita Anticipates or Renders Obvious Claim 1 ............................... 7
`1.
`The Petition Does Not Show That Sugita
`Discloses Selective Patching of First and
`Second Mobile Units ................................................................ 8
`The Petition Does Not Show That Sugita
`Discloses “Merging” A “Patch” With “Current
`Operating Code” .................................................................... 10
`The Petition Does Not Show That
`Sugita Discloses “Switch[ing] Execution”
`To The “Patched Operating Code” ........................................ 12
`Conclusion: Grounds A and B As Presented
`By Petitioner Lack Merit ....................................................... 13
`Ground C: Burson is irrelevant ............................................. 13
`5.
`B. Grounds D and E: The Petition Does Not Show That
`Claim 1 is Rendered Obvious by Sugita and Kirouac
`(with or without Burson), or Rendered Obvious by Sugita
`and Ballard (with or without Kirouac or Burson) ............................ 13
`
`3.
`
`4.
`
`VI. CONCLUSION ........................................................................................... 15
`
`{HD100872.1}
`
`ii
`
`

`

`CERTIFICATE OF COMPLIANCE .................................................................... 16
`CERTIFICATE OF SERVICE ............................................................................. 17
`
`Case IPR2019-00106
`Patent No. 5,699,275
`
`{HD100872.1}
`
`iii
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`I.
`
`INTRODUCTION
`
`As a threshold matter, the Board should note that grounds A and B in this
`
`petition for Inter Partes Review are substantively identical to the petitions earlier
`
`filed by Samsung Electronics Co., Ltd. (IPR 2018-01552) and Google LLC (IPR
`
`2019-01110), and to which Patent Owner has filed preliminary responses. By
`
`substantively identical, we mean the identified claim is the same (Claim 1); the
`
`identified art is identically the same (Sugita); and the arguments presented are
`
`identically the same. From Patent Owner’s detailed review, the only differences
`
`relate to the petitioner specific information. See Institution Decision in IPR2018-
`
`01554 at 27 – 31.
`
`For the reasons presented below, Iron Oak Technologies, LLC (Patent Owner)
`
`respectfully requests that the Board exercise its discretion to deny the Petition for
`
`Inter Partes Review filed by Microsoft Corporation (Petitioner) concerning U.S.
`
`Patent No. 5,699,275 (’275 patent).
`
`35 U.S.C. § 314(a) sets forth the standard by which an IPR may be instituted:
`
`The Director may not authorize an inter partes review to be instituted
`unless the Director determines that the information presented in the
`petition filed under section 311 and any response filed under section
`313 shows that there is a reasonable likelihood that the petitioner would
`prevail with respect to at least 1 of the claims challenged in the petition.
`
`{HD100872.1}
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`Thus, it is not the Board’s burden or duty to sift through the art relied upon in the
`
`Petition to see if a reasonable likelihood of unpatentability could have been shown.
`
`Rather, it is the Board’s duty to determine whether the arguments and evidence
`
`actually presented in the Petition demonstrate such likelihood by a preponderance
`
`of the evidence in the first instance. The Petition does not meet this standard.
`
`Each ground advanced in the Petition fails because Petitioner did not establish
`
`the content of each reference as would have been understood by a person of ordinary
`
`skill in the art (hereafter, POSITA). Graham v. John Deere Co., 383 U.S. 1, 17
`
`(1966) (“Under §103, the scope and content of the prior art are to be determined;
`
`…”). The properly understood content of the cited art demonstrates that they do not
`
`anticipate or render obvious the subject matter of Claim 1 of the ’275 Patent.
`
`For at least these reasons, the Petition should be denied in its entirety.
`
`II. RELATED INTER PARTES REVIEW CASES
`
`IPR Petitions currently pending against the ’275 Patent are listed below. As
`
`of this filing, trial has not been instituted against the ’275 Patent.
`
`A.
`
`Petitions Based Primarily on Sugita and Ballard
`
`As noted above, a petition for inter partes review was earlier filed by Samsung
`
`Electronics Co. Ltd (IPR2018-01552) contending that claim 1 of the ’275 patent is
`
`{HD100872.1}
`
`- 2 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`anticipated by Sugita; or obvious over Sugita and Wortham; or obvious over Ballard
`
`and Shimizu. No institution decision has yet been issued.
`
`As noted above, a petition for inter partes review was earlier filed by Google
`
`LLC (IPR2019-00110) contending that claim 1 of the ’275 patent is anticipated by
`
`Sugita; or obvious over Sugita and Wortham; or obvious over Ballard and Shimizu.
`
`No institution decision has yet been issued.
`
`B.
`
`Petitions Based Primarily on Hapka
`
`A petition for inter partes review was earlier filed by Samsung Electronics
`
`Co. Ltd. (IPR2018-01553) contending that claim 1 of the ’275 patent is obvious
`
`over Hapka and Parillo; or obvious over Hapka, Parillo and Wortham. No institution
`
`decision has yet been issued.
`
`A petition for inter partes review was later filed by Google LLC, (IPR2019-
`
`0111) contending that claim 1 of the ’275 patent is obvious over Hapka and Parillo;
`
`or obvious over Hapka, Parillo and Wortham. It should be noted that this petition
`
`by Google is substantially identical, if not absolutely identical, to petition IPR2018-
`
`01553 earlier filed by Samsung. No institution decision has yet been issued.
`
`III. PATENT OWNER’S RESERVATION OF RIGHTS
`
`In this Preliminary Response, Patent Owner has chosen to point out only
`
`certain errors in the Petition, and to present only certain arguments why trial should
`
`{HD100872.1}
`
`- 3 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`not be instituted on the any of the grounds presented in the Petition. This Preliminary
`
`Response is made without prejudice to or waiver of Patent Owner’s rights to present
`
`to the Board at a later date the other errors in the Petition and the grounds relied
`
`upon, and to present further and different arguments and evidence, as desired or
`
`necessary.
`
`For example, and not limitation, Patent Owner and Petitioner conducted a
`
`Markman claim construction hearing in the underlying litigation on September 20,
`
`2018. Patent Owner has disputed the claim constructions proposed by Petitioner in
`
`that proceeding, and the parties await the Court’s ruling. See Pet. at 13. For
`
`purposes of this Preliminary Response, Patent Owner will not offer its proposed
`
`constructions, as Petitioner’s grounds fail even under its proposed constructions.
`
`Patent Owner submits that the Board need not construe any claim term in a particular
`
`manner in order to arrive at the conclusion that the Petition is substantively deficient.
`
`Wellman, Inc. v. Eastman Chem. Co., 642 F.3d 1355, 1361 (Fed. Cir. 2011) (“need
`
`only be construed to the extent necessary to resolve the controversy”).
`
`IV. LISTING OF FACTS
`
`The Petition did not include a Statement of Material Facts to be Admitted or
`
`Denied.
`
`{HD100872.1}
`
`- 4 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`V.
`
`THE PETITION DOES NOT SHOW A REASONABLE
`LIKELIHOOD OF SUCCESS ON ANY GROUND
`
`Petitioner has the burden of proof to establish through its Petition that trial
`
`should be instituted. 37 C.F.R. § 42.108(c). This burden never shifts to Patent
`
`Owner. 35 U.S.C. 316(e).
`
`To prevail on institution based on anticipation (Ground A), the Petition must
`
`provide credible evidence and argument demonstrating to the Board that “each and
`
`every element as set forth in [Claim 1] is found, either expressly or inherently
`
`described, in a single prior art reference.” Verdegaal Bros., Inc. v. Union Oil Co. of
`
`Cal., 814 F.2d 628, 631 (Fed. Cir. 1987); see also Nidec Motor Corp. v. Zhongshan
`
`Broad Ocean Motor Co., 851 F.3d 1270, 1274 (Fed. Cir. 2017) (reversing finding of
`
`anticipation based on skilled artisan “at once envisage” the claimed subject matter).
`
`To prevail on institution based on obviousness (Grounds B, C, D, and E), the
`
`Petition must demonstrate to the Board that the differences between the claimed
`
`subject matter and the prior art are such that the subject matter of Claim 1, as a
`
`whole, would have been obvious at the time the invention was made to a person
`
`having ordinary skill in the art. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406
`
`(2007). A demonstration of obviousness involves the following four questions, for
`
`which Petitioner bears the burden of proof: (1) the scope and content of the prior art;
`
`(2) any differences between the claimed subject matter and the prior art; (3) the level
`
`{HD100872.1}
`
`- 5 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`of skill in the art; and (4) where in evidence, so-called secondary considerations.
`
`Graham v. John Deere Co., 383 U.S. 1, 17 (1966). The Petition must have a clear
`
`articulation of why a POSITA would have been motivated to combine the references
`
`in the manner described. In re Magnum Oil Tools Int’l, Ltd, 829 F.3d 1364, 1380
`
`(Fed. Cir. 2016.) (holding “a petitioner cannot employ mere conclusory statements.
`
`The petitioner must instead articulate specific reasoning, based on evidence of
`
`record, to support the legal conclusion of obviousness). To establish obviousness of
`
`Claim 1, all the claim limitations must be taught or suggested by the properly
`
`combined prior art. See CFMT, Inc. v. Yieldup Int’l Corp., 349 F.3d 1333, 1342
`
`(Fed. Cir. 2003); In re Royka, 490 F.2d 981, 985 (CCPA 1974). Thus, the Petition
`
`“must specify where each element of the claim is found in the prior art patents or
`
`printed publications relied upon.” 37 C.F.R. § 42.104(b)(4); see also Arendi S.A.R.L.
`
`v. Apple, Inc., 832 F.3d 1355 (Fed. Cir. 2016) (reversing Board obviousness
`
`determination based on “common sense” that was conclusory and unsupported by
`
`substantial evidence).
`
`As shown below, the grounds presented in the Petition fail to provide the
`
`Board with credible evidence or argument concerning several key elements of Claim
`
`1.
`
`{HD100872.1}
`
`- 6 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`A. Grounds A, B, and C: The Petition Does Not Show That Sugita
`Anticipates or Renders Obvious Claim 1
`
`For its anticipation argument (Ground A), Petitioner has the burden of
`
`establishing that a POSITA would have understood that the content of Sugita
`
`disclosed each element of Claim 1 as ordered and related in Claim 1. Karsten Mfg.
`
`Corp. v. Cleveland Golf, 242 F.3d 1376, 1383 (Fed. Cir. 2001) (“To establish
`
`anticipation, every element and limitation of the claimed invention must be found in
`
`a single prior art reference, arranged as in the claim.”) Even under Petitioner’s
`
`improper claim constructions, it has failed this burden. Specifically, Petitioner and
`
`its expert have failed to establish that Sugita is configured such that the base station
`
`addresses a patch to a first mobile terminal, but not to a second mobile terminal as
`
`required by Claim 1.
`
`According to Petitioner’s translation, Sugita (Ex. 1005) is a Japanese
`
`Unexamined Patent Application entitled “Update Method
`
`for Mobile
`
`Communications Terminal.”1 A POSITA reading Sugita as of April 12, 1995, would
`
`have understood that Sugita was concerned with wirelessly updating all
`
`communication terminals in a fleet of vehicles, such as ships, aircrafts, and
`
`automobiles. Ex. 1005 at [0002].
`
`1 Patent Owner will not challenge the accuracy of the translation for purposes of this Preliminary Response.
`However, Patent Owner reserves its right to challenge the accuracy and content of the translation if trial is
`instituted.
`
`{HD100872.1}
`
`- 7 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`1.
`
`The Petition Does Not Show That Sugita Discloses Selective
`Patching of First and Second Mobile Units
`
`Sugita describes updating every mobile terminal of a plurality of mobile
`
`terminals.2 Sugita has no disclosure that a mobile terminal within the plurality of
`
`mobile terminals is not sent the update. In other words, all mobile terminals are
`
`addressed and sent the update. This is in direct contrast to the subject matter of
`
`Claim 1, which is directed to a manager host addressing a “patch message” to a first
`
`mobile unit, but not to a second mobile unit (read: selective patching). Note that
`
`Claim 1 requires only that the at least one patch message be transmitted by the
`
`manager host, and does not that the mobile unit has to receive the patch message.
`
`Petitioner and its expert argue that because Sugita discloses a two-stage
`
`transmission scheme of a group transmission followed by individual transmission(s)
`
`for those group units that failed to update, Sugita necessarily discloses the selective
`
`patching required by Claim 1. This is an erroneous argument not supported by
`
`Sugita.
`
`Sugita notes as background that replacing read-only-memory (ROM) in each
`
`of the mobile terminals in a fleet is time consuming, as you typically must wait for
`
`2 See, e.g., Abstract (“update each mobile communications terminal…”); Claim 1 (“update of software on
`each mobile terminal of a plurality of mobile communication terminals …”; Paragraph [0017](“Method for
`update of mobile communications terminals when performing updates of software on each mobile terminal
`(m1, m2, m3, m4, …) of multiple mobile communication terminals …” ; Fig. 1 (individual update sent to
`terminals that are part of group ID already sent an update).
`
`{HD100872.1}
`
`- 8 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`the vehicle to return to the yard. Ex. 1005 at [0004 -0007]. Rather than physically
`
`replacing ROM, Sugita discloses a method whereby the random-access-memory
`
`(RAM) in all of the terminals in a fleet of mobile terminals are updated in groups,
`
`followed by individual updates for those terminals that failed to update as part of
`
`the group(s). Ex. 1007 at [0012] and Fig. 1. For example, a group update may be
`
`sent by the base station to all mobile terminals. Those terminals in the yard will
`
`receive the update and likely complete the update. Those terminals not in the yard
`
`either may not receive the group update or may not complete the update based on
`
`the group update. Based on responses from the mobile terminals, which necessarily
`
`includes a failure to respond, the base station then resends the update individually
`
`to a smaller subset of mobile terminals than were sent the group update. Ex. 1005
`
`at [0026] (mobile
`
`terminals receive both one-to-one and one-to-multiple
`
`communication formats). Thus, every mobile terminal in Sugita is sent the group
`
`update by the base station with some receiving a redundant individual update. Sugita
`
`never discloses an instance when a mobile terminal is not sent the update
`
`transmission. Sugita has no appreciation of selective patching.
`
`The Petition does not adequately demonstrate the “selective patching”
`
`required by Claim 1.
`
`{HD100872.1}
`
`- 9 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`2.
`
`The Petition Does Not Show That Sugita Discloses
`“Merging” A “Patch” With “Current Operating Code”
`
`
`Claim 1 requires that “operating code” be remotely “patched” to create
`
`“patched operating code. Ex. 1001 at Claim 1. Therefore, the “patch” of Claim 1 is
`
`separate and different from either the “operating code” or the “patched operating
`
`code” that is created. The ’275 Patent discloses that “patching” operating code by
`
`“merging” a “patch” with “current operating code” is but one form of “updating”
`
`operating code. For example, Col 13, Lines 9-25 of the ’275 Patent begins (emphasis
`
`added), “The system and method of remote patching or updating of operating code”
`
`and goes to describe updating by patching and merging, and updating by
`
`downloading “messages collectively representing new operating code.” Claim 1 is
`
`not directed to updating operating code by downloading new code.
`
`Notably Petitioner’s translation of Sugita does not use the word “patch” or
`
`“patching” when describing its non-selective method of updating software on the
`
`mobile communication terminals. What Sugita discloses is sending “update
`
`information that may be either all or some of the above-mentioned mobile
`
`communications terminal software.” Ex. 1005 at [0035]. Sugita does not disclose
`
`sending an operating code “patch” that must be merged into the operating code. The
`
`Petition’s conclusion that Sugita’s “updating” software by sending “software” is the
`
`same as Claim 1’s “patching” by merging a patch has not been supported. Indeed,
`
`{HD100872.1}
`
`- 10 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`rather than relying on the content of Sugita, Petitioner relies mainly on the
`
`conclusions of its expert. Pet. at 38 – 42. Under Petitioner’s faulty logic, since
`
`Sugita discloses “updating,” it also discloses the “patching” required by Claim 1 Id.
`
`Patent Owner challenges that reasoning.
`
`Concerning Claim 1’s requirement that the “patch” be “merged” with current
`
`operating code, Petitioner relies on Sugita’s disclosure in Figure 6 (mobile terminal
`
`operation) that “update information” is copied to the program area (S14). Pet. at 41.
`
`It is this last step of “copy[ing] update information to program area,” that Petitioner’s
`
`expert opines would have disclosed to a POSITA the claimed “merging” a “patch”
`
`into “current operating code.” Yet, Petitioner’s expert’s opinion is based solely on
`
`Sugita’s disclosure in Figure 6 that the “update information” is copied to the
`
`program “area.” That stretches Sugita too far. Copying “update information” to
`
`an area in RAM where the program is actually operating cannot disclose “patching”
`
`current operating code by “merging” as required by Claim 1.
`
`Further, Claim 1 requires that the “mobile unit” be operable to “create patched
`
`operating code by merging. Ex. 1001 at Claim 1. In other words, once the “patch
`
`messages” are received by the mobile unit, the mobile unit, and not the “manger
`
`host,” controls the patching process. Ex.1001 at Claim 1. In contrast, Sugita
`
`discloses that “processor 11 software operates on RAM 15 to enable updating by
`
`remote operation using a wireless circuit.” Ex. 1005 at [0025] (emphasis added).
`
`{HD100872.1}
`
`- 11 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`Further, Sugita discloses “[i]n other words, in this Invention, updates of mobile
`
`communications terminal software in wireless data communication systems are
`
`performed by remote manipulation by way of a base station.” Ex. 1005 at [0013]
`
`(emphasis added). Remote control of the updating process by Sugita’s base station
`
`is not the same as Claim 1’s mobile unit being operable to create patched operating
`
`code.
`
`Thus, the Petition does not sufficiently establish that Sugita discloses
`
`transmitting a “patch” for operating code, or that Sugita discloses “merging” a patch
`
`into current operating code, or that Sugita discloses that the patching process is
`
`carried out by the mobile terminal, rather than the base station, all as required by
`
`Claim 1.
`
`3.
`
`The Petition Does Not Show That Sugita Discloses
`“Switch[ing] Execution” To The “Patched Operating Code”
`
`Similarly to failing to show “patching” by “merging” in Sugita, Petitioner has
`
`failed to show that Sugita discloses “switch[ing] execution” from “current operating
`
`code” to “patched [by merging] operating code” as required by Claim 1. Because
`
`Sugita has no discernable disclosure of switching execution, Petitioner again relies
`
`on the conclusory opinions of its expert. See Pet. at 47-48.
`
`{HD100872.1}
`
`- 12 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`4.
`
`Conclusion: Grounds A and B As Presented By Petitioner
`Lack Merit
`
`Petitioner bore the burden of demonstrating through its Petition the legally
`
`correct “content” of Sugita, and bore the burden of demonstrating how that “content”
`
`would have rendered Claim 1 unpatentable. Graham v. John Deere Co., 383 U.S.
`
`1, 17 (1966). As demonstrated above, Petitioner has failed to demonstrate
`
`adequately that the content of Sugita as would have been understood by a POSITA
`
`anticipates or renders obvious Claim 1.
`
`5.
`
`Ground C: Burson is Irrelevant.
`
`Petitioner relies on Burson (Ex. 1008) “[t]o the extent one may argue Sugita’s
`
`mobile terminal is not a ‘battery-powered-device’…” Because the mobile unit of
`
`Claim 1 is not limited to a battery-powered-device, Petitioner’s reliance on Burson
`
`is irrelevant.
`
`B. Grounds D and E: The Petition Does Not Show That Claim 1 is
`Rendered Obvious by Sugita and Kirouac (with or without
`Burson), or Rendered Obvious by Sugita and Ballard (with or
`without Kirouac or Burson)
`
`Petitioner recognizes Sugita’s lack of disclosure concerning the mobile
`
`terminal being operable to create patched operating code “by merging the … patch”
`
`{HD100872.1}
`
`- 13 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`with current operating code.”3 Ex. 1001 at Claim 1. Petitioner also recognizes
`
`Sugita’s lack of disclosure concerning the mobile terminal begin operable to “switch
`
`execution to the patched operating code.”4
`
` Because of these recognized deficiencies, Petitioner relies on Kirouac (Ex.
`
`1007) “[t]o the extent one might argue Sugita does not sufficiently disclose
`
`“creat[ing] [a] patched operating code by merging the at least one patch with
`
`current operating code,” and on Ballard (Ex. 1006) “[t]o the extent one might argue
`
`“switch[ing] execution to the patched operating code” requires two separate
`
`memories.” Pet. at 51 & 56.
`
`Even if it were true that Kirouac sufficiently discloses patched operating code
`
`created “by merging the … patch with current operating code,” and even if it were
`
`true that Ballard discloses “switch[ing] execution to the patched operating code,”
`
`and even if were true that a POSITA would have been motivated combine Kirouac,
`
`Ballard, or both, with Sugita—positions to which Patent Owner does not accede—
`
`the resulting combination still would not disclose all of the elements of Claim 1.
`
`As presented above, such combination still would not have the “selective
`
`patching” element required by claim 1. Specifically, the combination proposed by
`
`Petitioner still would lack a “manager host operable to address the … patch message
`
`3 As demonstrated above, Sugita has absolutely no disclosure of the mobile terminal “merging” a “patch.”
`4 As demonstrated above, Sugita has absolutely no disclosure of the mobile terminal “merging” a “patch.”
`
`{HD100872.1}
`
`- 14 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`such that the … patch message is transmitted to the first mobile unit but not to the
`
`second mobile unit. See Section V.A.3.
`
`Not surprisingly, this deficiency in the prior art was recognized by the Office
`
`when it issued the Notice of Allowance.
`
`Ex. 1002 at 110.
`
`VI. CONCLUSION
`
`For at least the reasons set forth above, Patent Owner respectfully requests
`
`that the Board exercise its discretion and deny institution of trial because of
`
`deficiencies in the Petition.
`
`Date: February 21, 2019
`
`Respectfully submitted,
`
`
`By: /Al Deaver/
`Albert B. Deaver, Jr.
`Reg. No. 34,318
`Lead Counsel for Patent Owner
`
`{HD100872.1}
`
`- 15 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`CERTIFICATE OF COMPLIANCE
`
`Pursuant to 37 C.F.R. § 42.24(d), I certify that this Preliminary Response to
`
`Petition complies with the type-volume limitation of 37 C.F.R. § 42.21(b)(1)
`
`because it contains fewer than the limit of 14,000 words, as determined by the word
`
`processing program used to prepare the document, excluding the parts of the
`
`document exempted by 37 C.F.R. § 42.24(a)(1).
`
`Date: February 21, 2019
`
`Respectfully submitted,
`
`
`By: /Al Deaver/
`Albert B. Deaver, Jr.
`Reg. No. 34,318
`Lead Counsel for Patent Owner
`
`{HD100872.1}
`
`- 16 -
`
`

`

`Case IPR2019-00106
`Patent No. 5,699,275
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 C.F.R. §42.6(e), I certify that an electronic copy of the foregoing
`
`PATENT OWNER’S PRELIMINARY RESPONSE was served along with any
`
`accompanying exhibits via the Patent Review Processing System to Petitioner’s
`
`counsel and email to sidley_microsoft_ironoak_ipr@sidley.com
`
`Date: February 21, 2019
`
`Respectfully submitted,
`
`
`By: /Al Deaver/
`Albert B. Deaver, Jr.
`Reg. No. 34,318
`Lead Counsel for Patent Owner
`
`{HD100872.1}
`
`- 17 -
`
`

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