throbber
IPR2019-01015
`U.S. Patent 8,799,468
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`DISH NETWORK L.L.C.,
`Petitioner,
`
`v.
`
`MULTIMEDIA CONTENT MANAGEMENT LLC
`Patent Owner
`
`IPR2019-01015
`PATENT 8,799,468
`
`PATENT OWNER’S OPPOSITION TO PETITIONER’S REQUEST FOR
`REHEARING
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`
`I.
`
`INTRODUCTION
`
`Petitioner’s Request for Rehearing does not show how the Board actually
`
`misapprehended Petitioner’s argument. The Board denied institution of all grounds
`
`after a full consideration of the art, the claims, and the evidence. Petitioner now
`
`claims the Board acted “upon a misapprehension of the argument set forth in the
`
`Petition.” (Request for Rehearing, Paper No. 12 (“Request”), p. 1). However,
`
`Petitioner’s new argument does not address the fundamental technical flaws the
`
`Board identified in denying institution of the instant IPR. Further, even if
`
`Petitioner’s argument did solve these issues, Petitioner simply ignored multiple
`
`other, independent reasons the Board provided in support of institution denial. For
`
`at least these reasons, Petitioner has failed to show how the Board abused its
`
`discretion in denying institution of the instant IPR.
`
`II. ARGUMENT
`
`Petitioner Ignores Multiple Independent Reasons the Board
`A.
`Provided In Support of Institution Denial
`In denying institution, the Board provided at least five independent reasons
`
`to support the Board’s decision. Petitioner’s request only addresses three of those
`
`reasons. Thus, in addition to the fact that Petitioner’s argument regarding the three
`
`addressed reasons is flawed—see Section II.B below—the Board should reject
`
`Petitioner’s Request because Petitioner did not speak to all reasons for the Board’s
`
`1
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`
`denial.
`
`As Petitioner notes, (Request at 4–5), the Board stated at least five reasons to
`
`deny institution:
`
`1. “Petitioner’s proposed combination would use both unidirectional access
`
`control and bidirectional access control for the same data request.” Request at 4
`
`(citing Institution Decision, Paper No. 11 (“Decision”), p. 16).
`
`2. “Petitioner has not sufficiently explained why an ordinarily skilled artisan
`
`would have been motivated to use both the prior art access control using bidirectional
`
`communication and
`
`the
`
`improved access control using unidirectional
`
`communications at the same time.” Request at 4 (citing Decision at 16).
`
`3. “Petitioner has failed to establish why an ordinarily skilled artisan would
`
`have used both access control paradigms for the same data request.” Request at 4
`
`(citing Decision at 17).
`
`4. “Petitioner’s inference that this system would then also utilize account
`
`control using the resource-intensive bidirectional communications is speculative and
`
`not sufficiently supported by the evidence of record.” Request at 4 (citing Decision
`
`at 16).
`
`5. “Petitioner does not explain persuasively why an ordinarily skilled artisan
`
`would have continued to use unidirectional communications to provide access
`
`control for a data request when using bidirectional communications already
`
`2
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`provides access control for the same data request.” Request at 4 (citing Decision at
`
`17).
`
`Petitioner attempts to explain why Ground 1 does not expressly rely on both
`
`unidirectional access control and bidirectional access control for the same data
`
`request. E.g., Request at 5–9. However, Petitioner’s argument is only directed to
`
`items (1), (3), and (5) in Petitioner’s list of the Board’s reasons. Petitioner’s
`
`Request does not address in any way the Board’s holding that “Petitioner has not
`
`sufficiently explained why an ordinarily skilled artisan would have been motivated
`
`to use both the prior art access control using bidirectional communication and
`
`the improved access control using unidirectional communications at the same
`
`time,” (Decision at 15) (emphasis added), nor the holding that “Petitioner’s
`
`inference that this system would then also utilize account control using the
`
`resource-intensive bidirectional communications is speculative and not
`
`sufficiently supported by the evidence of record,” (Decision at 16) (emphasis
`
`added).
`
`Petitioner attempts to wave away these two bases of rejection by re-arguing
`
`the Petition, providing no reason to explain how or why the Board misapprehended
`
`Petitioner’s argument. For example, Petitioner states that the “Institution Decision
`
`faulted the Petition for reliance on ‘resource-intensive’ bidirectional
`
`communications techniques. But Petitioner’s Ground 1 selectively restricts the use
`
`3
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`of the bidirectional communications link to only authorized realtime content
`
`requests.” (Request at 11) (citing Decision at 15). Nothing in this brief aside
`
`addresses the Board’s fundamental declaration that any use of “the resource-
`
`intensive bidirectional communications is speculative and not sufficiently
`
`supported by the evidence of record.” (Decision at 16).
`
`Further, Petitioner’s argument does not address the underlying problem with
`
`Petitioner’s proposed combination: the inclusion of both unidirectional and
`
`bidirectional communications in a system that expressly disparages bidirectional
`
`communication. See, e.g., EX1008, Hoang ʼ980, [0005]. Petitioner did not attempt
`
`to provide any new and/or supplemental evidence to support its assertion that the
`
`Board somehow misunderstood Petitioner’s initial argument in the Petition.
`
`Petitioner’s position—that one of ordinary skill in the art would be motivated to
`
`use both unidirectional and bidirectional communications in the same system—
`
`remains purely speculative. Based on nothing more, the Board should deny
`
`Petitioner’s Request. However, as detailed in the next section, Petitioner’s
`
`remaining arguments are also flawed.
`
`B.
`
`The Board Did Not Misapprehend Petitioner’s Argument
`
`In denying institution, the Board correctly noted that Petitioner relied on a
`
`system that combines both unidirectional communication and bidirectional
`
`communication in a single system: “Petitioner has not sufficiently explained why
`
`4
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`an ordinarily skilled artisan would have been motivated to use both the prior art
`
`access control using bidirectional communication and the improved access control
`
`using unidirectional communication at the same time.” Decision at 16. Nothing in
`
`Petitioner’s Request deviates from this argument. E.g., Request at 5–6 (“As
`
`explained in the Petition, adding a bidirectional link was desirable because it
`
`would permit the modified unidirectional control system ‘to control access to
`
`user-initiated VOD programming,’ which was ‘the Holy Grail.’”) (emphasis
`
`modified). Petitioner’s current insistence that “Ground 1 of the [P]etition
`
`exclusively relied upon Hoang 980’s unidirectional control technique,” (Request at
`
`5) (emphasis in original), is, at best, disingenuous. See, e.g., Pet. at 29 (“This bi-
`
`directional transmission of a content request back to the server is obvious over the
`
`combination of Hoang 980’s uni-directional preferred embodiment system in Figs.
`
`7 and 8 with the bi-directional systems of Hoang 980’s Figs. 3 and 4 taught in the
`
`same patent disclosure.”).
`
`The Board Fully Considered Petitioner’s Argument And The
`
`1.
`Art
`
`The Board correctly summarized Petitioner’s argument that relies on both a
`
`unidirectional and a bidirectional system of Hoang ‘980:
`
`Petitioner relies on both the unidirectional and bidirectional systems
`taught by Hoang ’980 to meet the limitations of claim 1. For example,
`Petitioner relies on the unidirectional embodiment that employs a
`
`5
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`central controlling server to generate subscription data packets to be
`transmitted to client’s set top boxes for the limitation “a controller node
`coupled to the service provider network.” See Pet. 27‒33 (citing Ex.
`1008, Fig. 7). Petitioner relies on the bidirectional embodiment that
`transmits content requests to the cable system service provider network
`for the limitation “at least a second processor coupled to the second one
`or more network interfaces, wherein the second processor is to
`selectively transmit content requests to the service provider network in
`accordance with the controller instructions.” See Pet. 45‒53 (citing Ex.
`1008, Figs. 3, 4, 6).
`Decision at 12–13. The Board also considered Patent Owner’s Argument on this
`
`point:
`
`In particular, Patent Owner argues the unidirectional and bidirectional
`systems are not easily interchangeable or interoperable. Id. at 13. Patent
`Owner also argues Petitioner has not shown that the unidirectional and
`bidirectional systems are predictable variations of each other. Id. at 14.
`According to Patent Owner, Hoang ’980 disparages the bidirectional
`system to extoll the virtues of unidirectional systems. Id. at 14 (citing
`Ex. 1008 ¶ 5).
`
`Patent Owner argues combining the bidirectional and unidirectional
`systems would require the expenditure of significant processing and
`bandwidth in order to function, defeating the purpose of implementing
`access control using unidirectional communications, the primary
`benefit identified in Hoang ’980. See Prelim. Resp. 15. Dr. Hernandez’s
`testimony supports Patent Owner’s assertions. See Ex. 2001 ¶¶ 54‒62.
`
`6
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`Decision at 14–15. The Board also fully reviewed the prior art reference in question
`
`and the facts:
`
`Hoang ’980 teaches that one problem in the video-on-demand and data-
`on-demand industry is being able to control the access of a client’s set
`top box to on-demand programming without using bidirectional
`communications. Ex. 1008 ¶ 5. Hoang ’980 teaches traditional
`unidirectional communications had limitations in controlling access to
`programming, necessitating the use of bidirectional communications at
`the cost of a significant increase processing and bandwidth resources.
`Id. ¶ 5. Hoang ’980 explains the manner in which bidirectional
`communications were used in prior art systems to control access to
`programming, detailing such communications
`in embodiments
`described in Figures 4‒6. Id. ¶¶ 15‒24.
`
`Hoang ’980 teaches that its invention replaces the bidirectional
`communications used to control access to programming in prior art
`systems with an improved method that only needs unidirectional
`communications, detailing such communications in embodiments
`described in Figures 7‒11. Id. ¶¶ 25‒27, 48‒78.
`Decision at 14. The Board properly considered both the facts presented and the
`
`arguments presented by both the Petitioner and the Patent Owner. Based on the
`
`consideration, the Board decided not to institute the instant IPR. Decision at 17.
`
`2.
`
`Petitioner’s Technical Argument Remains Flawed
`
`As noted throughout Patent Owner’s Preliminary Response, an ordinarily skill
`
`7
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`artisan would not understand Petitioner’s proposed combination to function in the
`
`manner Petitioner suggests. See, e.g., Patent Owner’s Preliminary Response, Paper
`
`6 (“POPR”), at 22–28. Petitioner continues to rely on Hoang ’980’s statement that
`
`“all aspects of the present invention can be implemented within the bi-directional
`
`communication paradigm, the only difference being that even more features can be
`
`provided to the digital broadcast and DOD user when a bidirectional communication
`
`link is available.” Request at 10–11. That one sentence does not carry the day for
`
`Petitioner. See POPR at 25.
`
`As detailed above, Petitioner’s Request does not address Petitioner’s failure
`
`to support its speculative claim that unidirectional and bidirectional systems could
`
`be seamlessly combined. See also POPR at 25, Further, Petitioner’s Reqeust does
`
`not address the underlying problem of Hoang ʼ980’s disparagement of bidirectional
`
`systems. See id.; see also EX2001, Hernandez Decl., ¶61; EX1008, [0018–19,
`
`0025].
`
`Moreover, as noted in the POPR, a person of ordinary skill in the art would
`
`understand the teachings of Hoang ʼ980 to disclose a bidirectional communication
`
`system that is nonfunctional for the purposes to which Petitioner cites. POPR at 26,
`
`EX2001, Hernandez Decl., ¶¶ 67, 71–72, 74–75 (“The exemplary STB that is shown
`
`in FIG. 8 and that is used for the DOD system does not have a QAM modulator,
`
`which would be required for Petitioners position to be correct. A [quadrature phase
`
`8
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`shift keying (“QPSK”)] modulator is also not shown or described, making
`
`Petitioner’s position truly illogical.”). As an additional example, one of ordinary skill
`
`in the art would not understand Hoang ʼ980 as disclosing a bidirectional
`
`communication system in which a gateway unit communicates with a controller
`
`node via the service provider network as Petitioner suggests. See POPR at 27–28
`
`(citing EX1008, [0019]; EX2001, Hernandez Decl., ¶¶ 68–80)
`
`As Dr. Hernandez noted in his Declaration supporting the POPR:
`
`It is my opinion that Hoang ’980 fails to disclose or suggest a bi-
`directional system. It is my further opinion that Hoang ’980’s
`unidirectional teachings cannot be modified by what Hoang ’980
`discloses to produce a bi-directional system. It is my opinion that,
`contrary to Petitioner’s suggestion, a POSITA would not, and could
`not, simply use block 370 in the bi-directional system and method
`described by Hoang ’980 to implement the block 706 in the
`unidirectional system and method described by Hoang ’980.
`Petitioner’s suggested combination is fundamentally flawed.
`EX2001, Hernandez Decl., ¶ 81 (emphasis added). In the Request, Petitioner simply
`
`provides a two-page block quotation of its original argument. Request at 9–11.
`
`Petitioner does not provide any reason in the Request to suspect or rebut Dr.
`
`Hernandez’s conclusions, either by explaining how the Board—which cited Dr.
`
`Hernandez in support of Patent Owner’s argument (Decision at 15)—misunderstood
`
`Dr. Hernandez, or by providing new evidence. See, e.g., Request at 9–12. Because
`
`9
`
`

`

`IPR2019-01015
`U.S. Patent 8,799,468
`Petitioner fails to provide any reason why its original technical argument succeeds
`
`in the face of the Board’s reasoned analysis, the Board should reject Petitioner’s
`
`Request and maintain denial of institution.
`
`C. Conclusion
`
`Petitioner’s Request for Rehearing does not address each of the independent
`
`grounds for the Board’s denial of institution in the instant IPR. Further, Petitioner’s
`
`Request did not address the underlying technical flaws in Petitioner’s argument to
`
`combine the unidirectional and bidirectional aspects of Hoang, which the Board
`
`rejected. For at least these reasons, the Board should deny Petitioner’s Request for
`
`Rehearing and maintain denial of institution.
`
`Date: January 13, 2020
`
`
`
`
`
`Respectfully submitted,
`
`/s/ Benjamin R. Johnson
`Benjamin R. Johnson
`Reg. No. 64,483
`Jeffrey G. Toler
`Reg. No. 38,342
`MCDONNELL, BOEHNEN, HULBERT, &
`BERGHOFF, L.L.P.
`300 South Wacker Drive
`Chicago, Illinois 60606
`Telephone: (312) 913-0001
`Facsimile: (312) 913-0002
`
`Attorneys for Patent Owner
`
`10
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`IPR2019-01015
`U.S. Patent 8,799,468
`
` I
`
` certify that an electronic copy of the foregoing PATENT OWNER’S
`
`OPPOSITION TO PETITIONER’S REQUEST FOR REHEARING was served on
`
`Petitioner’ counsel of record at the following address:
`
`Eliot D. Williams
`G. Hopkins Guy III
`Baker Botts L.L.P.
`1001 Page Mill Road, Bld. 1, Suite 200
`Palo Alto, California 94304-1007
`650.739.7500
`
`Ali Dhanani
`Baker Botts L.L.P.
`910 Louisiana St.
`Houston, TX 77002
`713.229.1108
`
`Date: January 13, 2020
`
`
`
`
`
`
`
`Respectfully submitted,
`
`By: /s/ Benjamin R. Johnson
`Benjamin R. Johnson
`MCDONNELL, BOEHNEN,
`HULBERT, & BERGHOFF, L.L.P.
`300 South Wacker Drive
`Chicago, Illinois 60606
`Telephone: (312) 913-0001
`Facsimile: (312) 913-0002
`
`
`
`i
`
`

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