throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`
`
`
`
`MICROSOFT CORPORATION
`
`Petitioner
`
`v.
`
`UNILOC 2017 LLC
`
`Patent Owner
`
`
`
`
`
`IPR2019-00973
`
`U.S. PATENT NO. 7,075,917
`
`
`
`
`
`
`
`
`
`
`
`PATENT OWNER SUR REPLY TO PETITION
`
`
`
`
`
`
`
`
`

`

`
`
`
`
`I.
`
`II.
`
`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`Table of Contents
`
`
`INTRODUCTION ........................................................................................... 1
`
`Petitioner fails to meet its burden to establish that TR25.835
`constitutes a prior art PRINTED PUBLICATION as to the ’917 Patent ........ 1
`
`A.
`
`B.
`
`C.
`
`D.
`
`E.
`
`F.
`
`G.
`
`Patent Owner has been prejudiced by Petitioner’s failure to
`specify the pre-AIA statutory subsection under which
`TR25.832 allegedly qualifies as a prior art printed publication
`
`The undisputed cataloging and indexing factors weigh in favor
`of finding TR25.832 was not publicly accessible
`
`Petitioner fails to prove that allegedly uploading the asserted
`reference to a website or disseminating it via email to a targeted
`list of recipients establishes public accessibility
`
`Petitioner fails to prove that an alleged presentation at a
`meeting establishes public accessibility
`
`Petitioner failed to explain in its Reply the alleged relevance, if
`any, for each one of the 20 exhibits attached thereto
`
`Petitioner has not met its burden by pointing to extraneous
`statements that, if relevant at all, are helpful only to Uniloc
`
`Petitioner’s Reply impermissibly relies on inadmissible hearsay
`and unauthenticated documents
`
`2
`
`3
`
`4
`
`7
`
`9
`
`10
`
`12
`
`III.
`
`PETITIONER FAILS TO PROVE OBVIOUSNESS ................................... 13
`
`A.
`
`Petitioner fails to meet its burden to prove obviousness of
`“storing abbreviated sequence numbers whose length depends
`on the maximum number of coded transport blocks to be stored
`and which can be shown unambiguously in a packet data unit
`sequence number” (claim 1)
`
`B.
`
`Petitioner fails to meet its burden to prove obviousness based
`on its exclusive reliance on TR25.835 for limitations of claim 1
`
`13
`
`20
`
`IV. CONCLUSION .............................................................................................. 23
`
`
`
`
`
`ii
`
`

`

`I.
`
`INTRODUCTION
`
`Uniloc 2017 LLC (the “Patent Owner” or “Uniloc”) submits this Sur-Reply
`
`to the Petition for Inter Partes Review (“Pet.” or “Petition”) of United States Patent
`
`No. 7,075,917 (“the ’917 patent” or “Ex. 1001”) filed by Microsoft Corporation
`
`(“Petitioner”) in IPR2019-00973. For the reasons given in Uniloc’s Response (Paper
`
`9, “POR”) and herein, Petitioner fails to carry its burden of proving unpatentability
`
`of the challenged claims of the ’917 patent based on the grounds presented in the
`
`Petition.
`
`II.
`
`PETITIONER FAILS TO MEET ITS BURDEN TO ESTABLISH
`THAT TR25.835 CONSTITUTES A PRIOR ART PRINTED
`PUBLICATION AS TO THE ’917 PATENT
`
`As a threshold issue addressed in detail in Patent Owner’s Response,
`
`Petitioner has failed to meet its burden to establish that TR25.835 (Ex. 1005)
`
`constitutes prior art. As the sole Ground relies on TR25.835, the Board is
`
`respectfully requested to hold Claims 1‒3 and 9‒10 not unpatentable.
`
`Petitioner does not dispute in its Reply that the Petition itself “does not recite
`
`any applicable standard that TR25.832 must meet to qualify as a printed publication
`
`under pre-AIA 35 U.S.C. §102(a) or 102(b), or explain how the supporting evidence
`
`allegedly demonstrates that the applicable standard is met, thus failing to meet the
`
`minimum standards required to explain the significance of evidence, both under
`
`applicable regulations and under applicable case law.” POR 17.
`
`
`
`1
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`Petitioner tacitly acknowledges the Petition is itself deficient by purporting to
`
`rely, instead, on new argument and evidence introduced in its Reply. Indeed, the
`
`deficiency of the Petition is conceded by the fact that Petitioner filed with its Reply
`
`no less than twenty additional exhibits made up of unauthenticated documents
`
`containing inadmissible hearsay (as explained further below).
`
`The Federal Circuit has instructed that “[u]nlike district court litigation—
`
`where parties have greater freedom to revise and develop their arguments over time
`
`and in response to newly discovered material—the expedited nature of IPRs bring
`
`with it an obligation for petitioners to make their case in their petition to institute.”
`
`Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1369 (Fed. Cir.
`
`2016) (emphasis added); see also see 37 C.F.R. § 42.23(b); Trial Practice Guide
`
`Update 15 (August 2018).
`
`Even if the Board were inclined to consider the new argument and evidence
`
`Petitioner impermissibly attempts to introduce in its Reply, this still would not cure
`
`the failure of the Petition to provide sufficient evidentiary support to prove, by a
`
`preponderance of the evidence, that TR25.835 qualifies as prior art here.
`
`A.
`
`Patent Owner has been prejudiced by Petitioner’s failure to
`specify the pre-AIA statutory subsection under which TR25.832
`allegedly qualifies as a prior art printed publication
`
`Patent Owner’s Response noted, and Petitioner does not contest in its Reply,
`
`that the Petition fails to specify the pre-AIA which statutory subsection under which
`
`2
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`TR25.832 allegedly qualifies as a prior art printed publication. POR 16. Under the
`
`section heading “Critical Dates” (in the plural), Petitioner acknowledges in its Reply
`
`that different dates would be relevant depending, for example, on whether TR25.832
`
`is allegedly asserted under pre-AIA 35 U.S.C. §102(a) or 102(b). Rep. 4. Petitioner
`
`has effectively admitted, therefore, that the failure in the Petition to assert a statutory
`
`subsection under which TR25.835 allegedly qualifies as prior art has prejudiced
`
`Patent Owner’s ability to respond.
`
`B.
`
`The undisputed cataloging and indexing factors weigh in favor of
`finding TR25.832 was not publicly accessible
`
`In remains undisputed that TR25.832 “was not publicly accessible by virtue
`
`of indexing or cataloging” and that “the document bore an arbitrary title that had no
`
`information regarding its subject matter.” POR 16. Rather than contest these factual
`
`observations, or point to any record evidence in rebuttal, Petitioner’s Reply merely
`
`offers the Federal Circuit instruction that “neither cataloging nor indexing is a
`
`necessary condition for a reference to be publicly accessible.” Rep. 3 (quoting In re
`
`Lister, 583 F.3d 1307, 1312 (Fed. Cir. 2009)).
`
`Petitioner tellingly ignores the remainder of that Federal Circuit instruction
`
`that, while not a necessary condition, “cataloging and indexing have played a
`
`significant role” and remain relevant factors bearing on public accessibility. Lister,
`
`583 F.3d at 1312. Further underscoring the continued relevance of these factors
`
`3
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`here, the Federal Circuit has since instructed that cataloging and indexing are “no
`
`more or less important in evaluating the public accessibility of online references than
`
`for those fixed in more traditional, tangible media.” Voter Verified, Inc. v. Premier
`
`Election Sols., Inc., 698 F.3d 1374, 1380 (Fed. Cir. 2012).
`
`C.
`
`Petitioner fails to prove that allegedly uploading the asserted
`reference to a website or disseminating it via email to a targeted
`list of recipients establishes public accessibility
`
`As note in Patent Owner’s Response, the record evidence fails to establish that
`
`TR25.835 was uploaded to a 3GPP server prior to the critical date and that persons
`
`of ordinary skill in the art in general could readily access the reference online prior
`
`to the critical date. POR 16‒31. Petitioner primarily argues in its Reply that “anyone
`
`could easily subscribe to and access the 3GPP email listservs (aka ‘exploders’)
`
`relating to the technology discussed in TR25.835” and a person of ordinary skill in
`
`the art “would have known, through TR25.835 v0.0.2 or the ETSI/3GPP staff or
`
`both, that the relevant 3GPP working group was TSG RAN Working Group 2.” Rep.
`
`7. Petitioner leaves unaddressed controlling authority, addressed in Patent Owner’s
`
`Response, and holding that while uploading a reference to a website may make “the
`
`work technically accessible—someone could theoretically find it on the Internet—
`
`. . . ‘public accessibility requires more than technical accessibility.’” Samsung
`
`Elecs. Co. v. Infobridge Pte. Ltd., 929 F.3d 1363, 1369 (Fed. Cir. 2019).
`
`4
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`Petitioner cannot meet its burden to establish public accessibility of TR25.835
`
`before the critical date by ignoring such controlling authority. This standard is
`
`simply not met by Petitioner’s two primary assertions—i.e., the alleged ease of
`
`either (1) receiving the necessary group information from 3GPP staff that
`
`purportedly would have been required to locate the reference, or (2) discovering in
`
`advance which one of dozens if not hundreds of email lists might possibly receive
`
`notice or dissemination via email. Petitioner’s rebuttal, untethered to any of the legal
`
`authority Patent Owner had cited, is akin to arguing a library book located in a closet
`
`at a library could possibly be found by knowing one has to join the correct janitor
`
`email list in order to obtain the secret of where exactly to look.
`
`Petitioner’s argument is also internally inconsistent. If, as Petitioner suggests,
`
`consulting 3GPP staff was necessary or at least typical to determine “the relevant
`
`3GPP working group” (id.) and this staff-provided knowledge was then necessary to
`
`have any idea where to search on the 3GPP website for specific documents, this then
`
`would only further undermine Petitioner’s argument concerning public accessibility.
`
`See Samsung v. Infobridge, 929 F.3d at 1372 (“[A] work is not publicly accessible
`
`if the only people who know how to find it are the ones who created it.”). To borrow
`
`again from the library analogy, that a given library book may possibly be found by
`
`asking a librarian where to look does not somehow make the book publicly
`
`accessible.
`
`5
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`Petitioner’s Reply also purports to offer new evidence allegedly supporting its
`
`theory that TR25.835 was itself distributed via a specific email list. Rep. 8. Setting
`
`aside the untimeliness of this new evidence, according to Petitioner, the emails in
`
`question were sent only to select individuals who had the foresight to subscribed in
`
`advance to one and only correct list of legions of possible lists. Id. In raising this
`
`new evidence, Petitioner does not dispute, or even acknowledge, Patent Owner’s
`
`observation that the original declaration of Mr. Rodermund “states that those
`
`notification emails were provided to selected representatives of 3GPP member
`
`companies, not the general public.” POR 17 (citing Ex. 1004 ¶ 19).
`
`Even if the Board were to consider the evidence Petitioner attempts to
`
`untimely introduce in its Reply, Petitioner fails to explain whether and how this
`
`would impact the analysis previously cited from Samsung Elecs. Co. v. Infobridge.
`
`See POR 28‒30 (discussing, inter alia, Samsung v. Infobridge, 929 F. 3d at 1374–
`
`75). There, the Federal Circuit expressed reluctance “to assume that an email among
`
`potential collaborators should be treated the same as a public disclosure.” Id. It is
`
`telling that Petitioner’s Reply fails to mention the analysis in Samsung Elecs. Co. v.
`
`Infobridge on this issue, even though Patent Owner had addressed relevant portions
`
`of this opinion in detail in its Response. Id. Patent Owner’s legal argument and
`
`observations set forth in its Response remain uncontested. As was the case in
`
`Samsung Elecs. Co. v. Infobridge, the record evidence here concerning use of a
`
`6
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`targeted email list of collaborators, who knew which one of multiple possible lists
`
`to join in advance, simply does not establish that the asserted reference was publicly
`
`accessible in general to persons of ordinary skill as of the critical date.
`
`D.
`
`Petitioner fails to prove that an alleged presentation at a meeting
`establishes public accessibility
`
`Petitioner’s Reply also offers no basis dispute that “Petitioner has not shown
`
`that TR25.835 became publicly accessible via [any alleged] distribution at a 3GPP
`
`meeting” and that the Petition itself “makes no mention of distribution of TR25.835
`
`at a meeting.” POR 30 (emphasis added); see also id. 17. At most, Petitioner’s reply
`
`offers the conclusory and conciliatory statement, relegated to a footnote, that
`
`Uniloc’s observations “fail” for reasons Petitioner neglects to identify—as if the
`
`burden had somehow shifted to Uniloc on a point that Petitioner does not even
`
`attempt to prove. Rep. 4 n.4. The same conclusory footnote tacitly concedes that
`
`Petitioner does not rely on any distribution at a meeting. Id. (“but regardless
`
`TR25.385 was publicly available independent of distribution at that conference.”).
`
`It appears that Petitioner has come to recognize it failed to even mention the
`
`word “meeting” in its Petition and thus it has waived any corresponding theory
`
`concerning public accessibility allegedly arising from activity at a meeting. The
`
`word “meeting” only appears in Petitioner’s briefing in the following single sentence
`
`of its Reply: “TR25.385 [was] . . . presented at a September 2000 meeting attended
`
`7
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`by 140 people.” Rep. 1 (citing Ex. 1004, ¶ 25). As alleged support, Petitioner cites
`
`only to a single paragraph of the original declaration of Mr. Rodermund Ex. (1004,
`
`¶ 25), without purporting to rely on any portion of the supplemental declaration of
`
`Mr. Rodermund filed with the Reply (Ex. 1033). Accordingly, petitioner not only
`
`has waived reliance on any distribution at a “meeting” by failing to even mention
`
`this word in the Petition, Petitioner has also waived any reliance on testimony in the
`
`supplemental declaration concerning any alleged activity occurring at a meeting.
`
`Petitioner’s Reply also fails to even affirmatively state, with citation to
`
`allegedly supportive evidence, that any distribution of the TR25.385 reference took
`
`place at any meeting before the critical date. At most, Petitioner ambiguously
`
`asserts, for the first time in its Reply, that the TR25.385 was allegedly “presented”
`
`at the meeting. Rep. 1. Even if the Board were to consider this belated and hence
`
`waived theory, introduced for the first time in a reply brief, it is unavailing. That a
`
`reference was allegedly presented does not necessarily mean that printed
`
`publications of the same were necessarily distributed to those in attendance.
`
`Petitioner’s reluctance to elaborate further in its Reply, in the single and only passing
`
`reference to an alleged “meeting” set forth in its briefing, should be taken as an
`
`admission that no distribution of TR25.835 took place at that time.
`
`8
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`E.
`
`Petitioner failed to explain in its Reply the alleged relevance, if
`any, for each one of the 20 exhibits attached thereto
`
`While Petitioner’s Reply purports to newly rely on no less than 20 additional
`
`exhibits, the Reply fails to address each one individually and explain its alleged
`
`relevance. In several instances, for example, the Reply merely provides an
`
`unexplained citation which ambiguously encompasses multiple exhibit numbers or
`
`which purports to encompass nearly the entirety of Mr. Rodermund’s supplemental
`
`declaration. See, e.g., Pet. 9
`
`(citing “Exs. 1012-1019”);
`
`id.,
`
`(citing
`
`“Rodermund_Reply, ¶¶ 5-27”).
`
`Well-established authority proscribes Petitioner’s approach. As Patent Owner
`
`noted in its Response, the Board has held it is improper for a petitioner to merely
`
`offer general citations to exhibits in manner that “invites the opponent and the
`
`decision-maker to sift through the evidence on their own initiative and to draw their
`
`own conclusions based on their own manner of harnessing, interpreting, and
`
`characterizing the evidence.” Spalding v. Hartsell, Interference No. 104,699, Paper
`
`No. 92 at 5 (2002); Corning Incorp. v. Danjou’s DSM IP Assets B.V., IPR2013-
`
`00043, Paper No. 95 at 13 (PTAB May 1, 2014) (citing the 7th Circuit’s statement
`
`that “[a] brief must make all arguments accessible to the judges, rather than ask them
`
`to play archaeologist with the record.”). In addition, it is impermissible to
`
`incorporate arguments from one document into another, including by unexplained
`
`9
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`citations to exhibits. 37 CFR § 42.6(3) (“Arguments must not be incorporated by
`
`reference from one document into another document.”); PCT Int’l. Inc. v. Amphenol
`
`Corp., IPR2013-00229, Paper No. 17 at 2 (PTAB Dec. 24, 2013) (“Arguments must
`
`not be incorporated by reference from one document into another document. . .
`
`Among other things, this rule prevents parties from avoiding page limitations.”).
`
`F.
`
`Petitioner has not met its burden by pointing to extraneous
`statements that, if relevant at all, are helpful only to Uniloc
`
`Petitioner, evidently recognizing its failure to timely submit evidentiary
`
`support for its contention of public accessibility, attempts to raise the new (and hence
`
`waived) argument in its Reply that Patent Owner has somehow conceded the issue
`
`by admission. Nothing could be further from the truth.
`
`First, Petitioner newly points to the statement in the background section of the
`
`’917 patent that mentions a document entitled “3G TR 25.835 V0.0.2.” Rep. 1‒2,
`
`7. The referenced document is not, however, the TR25.385 reference relied upon in
`
`the Petition. Rather, according to Petitioner, the document identified as “3G TR
`
`25.835 V0.0.2” was “an outdated and superseded document.” Pet. 6. If the so-called
`
`“superseding” TR25.385 reference (V1.0.0) had been publicly accessible and
`
`generally known to persons of ordinary skill in the art prior to the filing date of the
`
`’917 patent, particularly those who were aware of what Petitioner refers to as
`
`“preceding version of the same document” (Rep. 2), surely the ’917 patent would
`
`10
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`have referenced, instead, what Petitioner refers to as version “V1.0.0.”The fact that
`
`the ’917 patent references only “3G TR 25.835 V0.0.2,” without mentioning
`
`“TR25.385 V1.0.0,” if relevant at all to the issue of public accessibility, is helpful
`
`only to Patent Owner. Indeed, under the circumstances, the cited statement in the
`
`’917 patent refutes Petitioner’s unsubstantiated speculation, offered through its
`
`declarant, that “for somebody interested in HARQ functionality and similar radio
`
`layer technologies, TR 25.835 v1.0.0 (Ex. 1005) would have been easily locatable
`
`and, in fact quite hard to miss, in September 2000.” Rep. 9 (citing Ex. 1033
`
`(Rodermund_Reply), ¶ 31).
`
`Second, Petitioner grossly mischaracterizes as party admissions certain
`
`statements from an oral hearing in a different matter. Rep. 2 (citing Apple, Inc. et
`
`al. v. Uniloc 2017 LLC, IPR2019-00222, Paper 26, TR at 41:10-25.). Setting aside
`
`the fact that the cited statements address a completely different document in a
`
`different matter, Petitioner overlooks the context in which those statements were
`
`made. Patent Owner had argued there, consistent with its position here, that public
`
`accessibility is not established by merely asserting a reference was made available
`
`at a 3GPP server or distributed to those who had previously elected to participate in
`
`an email list. See, e.g., Apple, Inc. et al. v. Uniloc 2017 LLC, IPR2019-00222, Paper
`
`26, TR at 39:15-17 (“So first of all, in their Slide 11, they have three bases. R20
`
`qualifies 16 as prior art: A, presented at the 3GPP meeting, B, distributed on email
`
`11
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`17 reflector, C, published on 3GPP server.”). Clearly, Patent Owner did not concede
`
`in that matter, nor does it concede here, that all documents 3GPP allegedly uploads
`
`to a server or distributes to a select list of recipients via email, must be deemed
`
`“publicly accessible” by those alleged acts.
`
`G.
`
`Petitioner’s Reply impermissibly relies on inadmissible hearsay
`and unauthenticated documents
`
`As further evidence that the Petition is deficient on its face on the issue of
`
`public accessibility of the asserted TR25.385 reference, Petitioner filed with its
`
`Reply no less than twenty additional exhibits, without any explanation as to why
`
`these exhibits could not have been included with the filing of the Petition. In
`
`addition to the issue of waiver, addressed above, the untimely exhibits submitted
`
`with the Reply should be afforded no weight because (1) they are replete with
`
`impermissible hearsay, (2) they are not properly authenticated, and (3) the vast
`
`majority are not even cited in the Reply.
`
`Petitioner filed with its Reply, for example, a significant number of documents
`
`purportedly downloaded from the Internet Archive’s Wayback Machine, without
`
`accompanying those documents with any authentication testimony from a person
`
`with knowledge at the Internet Archive concerning those documents, and without
`
`even providing the URL allegedly used to access those documents. See, e.g., Ex.
`
`1013‒1017. While Petitioner purports to rely upon the testimony of Mr.
`
`12
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`Rodermund, Mr. Rodermund does not testify to having any personal knowledge
`
`concerning any archiving performed by the Internet Archive’s Wayback Machine.
`
`At most, Mr. Rodermund merely asserts a subset of these exhibits purportedly “from
`
`the Wayback Machine appear to be an authentic archival copy.” Ex. 1033 ¶ 14.
`
`Such a conclusory testimony fails to cure the authentication and hearsay issues
`
`of the belated exhibits. In addressing this very issue, the Board has stated that
`
`“[w]hen offering a printout of a webpage into evidence to prove the website’s
`
`contents, the proponent of the evidence must authenticate the information from the
`
`website itself, not merely the printout.” Neste Oil Oyj v. REG Synthetic Fuels, LLC,
`
`IPR2013-00578 (Paper 53) (PTAB March 12, 2015). Petitioner offers no allegedly
`
`authenticating testimony from someone with proper personal knowledge regarding
`
`the alleged website source itself.
`
`III. PETITIONER FAILS TO PROVE OBVIOUSNESS
`
`While Petitioner has the burden of proof with respect to each element of every
`
`challenged claim, and this burden never shifts to Patent Owner, Patent Owner had
`
`nevertheless explained in its Response why the Petition is substantially deficient at
`
`least with respect to certain example claim language. Petitioner’s Reply either
`
`mischaracterizes or ignores the deficiencies Patent Owner had identified.
`
`A.
`
`Petitioner fails to meet its burden to prove obviousness of “storing
`abbreviated sequence numbers whose length depends on the
`maximum number of coded transport blocks to be stored and
`
`13
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`which can be shown unambiguously in a packet data unit
`sequence number” (claim 1)
`
`Among other deficiencies, Patent Owner explained why the theory set forth
`
`in the Petition fails to prove a POSITA would have found it obvious to modify
`
`TR25.835 using the teachings of Abrol, and that the proposed combination would
`
`have rendered obviousness “storing abbreviated sequence numbers whose length
`
`depends on the maximum number of coded transport blocks to be stored and which
`
`can be shown unambiguously in a packet data unit sequence number,” as recited in
`
`independent claim 1. POR 31‒38.
`
`First, Petitioner does not deny that the “[t]he Petition and [Dr. Bims]
`
`Declaration fail to consider whether a POSITA would apply Abrol to TR25.835 in
`
`view of Abrol’s clear teaching that it is intended for situations where channel
`
`capacity varies.” POR. 35. Petitioner also provides no rational basis to contest that
`
`Abrol expressly requires a varying channel capacity as basic principle of operation.
`
`At most, Petitioner offers the conclusory statement in its Reply that a person of
`
`ordinary skill in the art would allegedly be mistaken if she “understood Abrol as
`
`applying only to wireless networks of varying capacity.” Rep. 13. Such a conclusory
`
`assertion does not rebut the detailed explanation to the contrary in Patent Owner’s
`
`Response, nor does it explain how Abrol’s cited teachings could be implemented in
`
`the absence of a varying channel capacity. POR 32‒35.
`
`14
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`
`While Petitioner cites in its Reply, without explanation, to the supplemental
`
`declaration of Dr. Bims, the cited testimony is unavailing. Rep. 13 (citing Ex. 1032
`
`(Bims_Reply), ¶¶ 19‒21). In the cited paragraphs, Dr. Bims merely points, without
`
`further explanation, to the statement in Abrol that its system is “applicable to any
`
`communication system employing transmission of a byte stream over a wireless
`
`channel.” Ex. 1032 ¶ 19 (quoting Abrol, 3:32‒35). Dr. Bims conveniently
`
`overlooks, however, that the quoted statement in Abrol appears immediately after
`
`Abrol expressly identifies its “present invention” (i.e., its system) as specifically
`
`configured for “enable[ing] efficient transmission of a featureless byte Stream
`
`through a channel of varying capacity.” Abrol, 3:24‒26. It is axiomatic that Abrol’s
`
`consistent description of its system as requiring a varying channel capacity could not
`
`have been implemented on a channel that did not have such capacity. Dr. Bims
`
`undermines his own credibility in suggesting otherwise. Ericsson Inc. v. Intellectual
`
`Ventures I LLC, 890 F.3d 1336, 1346 (Fed. Cir. 2018) (“To contradict a reference,
`
`an unsupported opinion is not substantial evidence.”) (citing Homeland Housewares,
`
`LLC v. Whirlpool Corp., 865 F.3d 1372, 1378 (Fed. Cir. 2017) (“[W]e must
`
`disregard the testimony of an expert that is plainly inconsistent with the record, or
`
`based on an incorrect understanding of the claim[s].”)).
`
`Second, Petitioner impermissibly advances new argument and evidence which
`
`only further underscore the very deficiencies Patent Owner had identified as arising,
`
`15
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`at least in part, from the unaddressed requirement in Abrol for varying channel
`
`capacity. For example, Petitioner points to the statement in TR25.385 that “Fast
`
`HARQ is planned to be employed on DSCH.” Rep. 12 (citing TR25.835, 27 § 7.2)
`
`(emphasis altered). Petitioner then offers the conclusory assertion, without any
`
`accompanying explanation or documentation support, that DSCH allegedly had (as
`
`of an unspecified date) a variable bit rate. Id.
`
`Petitioner’s new and bald assertions in its Reply fail to carry its burden or even
`
`address the example deficiencies of the Petition Patent Owner had identified.
`
`Petitioner overlooks, for example, that the quoted statement in TR25.385 purports
`
`to describe only what is planned to be—i.e., it is not an assertion of what is expressly
`
`disclosed within the four corners of TR25.385. Moreover, neither Petitioner nor Dr.
`
`Bims point to anything in TR25.385 itself allegedly disclosing how the Fast HARQ
`
`mentioned in TR25.385 would be employed on DSCH as of the alleged publication
`
`date of that document, without further undisclosed modification, much less how it
`
`would or even could be employed using the varying channel capacity required by
`
`Abrol.
`
`Third, Petitioner’s Reply does not dispute that additional and unaddressed
`
`deficiencies arise at least to the extent “Abrol teaches modifying the RLP2 protocol
`
`by adding byte sequence numbers rather than frame sequence numbers” and further
`
`“provides for adding sequence numbers to constituents of frames.” POR 34‒38.
`
`16
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`Instead, Petitioner only attacks part of the underlying premise by newly asserting,
`
`through the supplemental declaration of Dr. Bim, that Abrol discloses “use of frame
`
`sequence numbers” rather than byte sequence numbers. Rep. 15‒16 (citing Ex. 1032
`
`(Bims_Reply), ¶ 25). The reference speaks for itself on this point, however, and Dr.
`
`Bim’s argument to the contrary only further undermines his credibility.
`
`In summarizing its claimed invention, Abrol states it achieves its efficiency
`
`“by changing the interpretation of the sequence numbers carried in the RLP protocol
`
`header.” Abrol, 3:40‒41 (emphasis added). This statement is immediately followed
`
`with reference to what interpretation must be changed—i.e., “[i]n RLP2, sequence
`
`numbers are used to denote frame numbers.” Id., 3:41‒42. After explaining “use of
`
`a byte sequence number” accomplishes “more reliable data retransmission” than a
`
`frame sequence number, Abrol states “[t]he embodiments of the invention provide
`
`the benefits of large byte sequence numbers while transmitting a fraction of the
`
`sequence number bits in the majority of over-the-air frames.” Id., 4:12‒43
`
`(emphasis added).
`
`The phrase “byte sequence number” (in plural and singular form) appears
`
`approximately 40 times in Abrol and is consistent and recurring theme of each
`
`embodiment. See, e.g., id., 4:43‒44 (“a 20-bit byte sequence number is used”)
`
`(emphasis added); id., 5:36‒46 (stating a possible disadvantage of “using sequence
`
`numbers corresponding to bytes instead of frames”—as required by all
`
`17
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`embodiments—may be minimized “by sometimes omitting most significant and
`
`least significant bits from the sequence number.”); id., 6:21‒23 (“each sequence
`
`number corresponds to the first byte of the data in the RLP frame.”) (emphasis
`
`added); id., 6:28‒29 (“the sequence numbers are byte sequence numbers”)
`
`(emphasis added).
`
`As shown at least by the above quotations, and by the more detailed
`
`explanation provided in Patent Owner’s Response, it cannot rationally be disputed
`
`that Abrol teaches modifying the RLP2 protocol in a manner that uses byte sequence
`
`numbers rather than frame sequence numbers. POR 34‒38. Conversely, Abrol does
`
`not expressly describe even a single embodiment as using frame sequence numbers
`
`as opposed to byte sequence numbers. Try is it might, Petitioner cannot rely on
`
`conclusory testimony of its declarant for a proposition that is directly contradicted
`
`in the reference itself. While the burden lies with Petitioner, its untenable and
`
`untethered technical attack fails to rebut, or even address, Patent Owner’s previously
`
`submitted explanation as to why this correct understanding of the express disclosure
`
`Abrol gives rise to deficiencies in the combination theory. Id.
`
`Fourth, Petitioner attacks its own fabricated strawman, and undermines the
`
`alleged motivation to combine asserted in the Petition, in newly arguing in its Reply
`
`that Abrol “is not limited to [8-bit] sequence numbers.” Rep. 18. The issue is not
`
`whether Abrol is limited to 8-bit sequence numbers. Rather, Patent Owner had
`
`18
`
`

`

`IPR2019-00973
`U.S. Patent No. 7,075,917
`
`
`contested the contention in the Petition that there would have been motivation to
`
`modify TR25.835 to incorporate 8-bit sequence numbers as an alleged improvement
`
`over what TR25.835 discloses. It is well established that motivation to modify does
`
`not arise from an alleged deficiency that is not itself recognized in the reference
`
`being modified. See In re Omeprazole Patent Litigation, 536 F.3d 1361, 1380 (Fed.
`
`Cir. 2008). Petitioner failed to comprehend, and leaves wholly unrebutted, the actual
`
`point Patent Owner had raised, responsive to the legal error presented in the Petition.
`
`Fifth, Petitioner falls into the same legal error in purporting to address Patent
`
`Owner’s observation that “neither the Petition nor the Declaration points to any
`
`statement in TR25.835 that overhead is a concern in error control protocols.” POR
`
`36; Rep. 18. Petitioner concedes the point in its Reply by, yet again, failing to point
`
`to any statement in TR25.835 that overhead is a concern in error control protocols.
`
`Instead, Petitioner alleges the flaw allegedly prompting the motivatio

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