throbber
Trials@uspto.gov
`Tel: 571-272-7822
`
`Paper 33
`Entered: March 22, 2018
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`TCT MOBILE, INC. AND TCT MOBILE (US) INC.,
`Petitioner,
`v.
`WIRELESS PROTOCOL INNOVATIONS, INC.,
`Patent Owner.
`
`Case IPR2016-01865
`Patent 9,125,051 B2
`
`
`
`
`
`
`
`
`
`Before KEVIN F. TURNER, MITCHELL G. WEATHERLY, and
`KAMRAN JIVANI, Administrative Patent Judges.
`TURNER, Administrative Patent Judge.
`
`FINAL WRITTEN DECISION
`Determining Claims 6, 7, 9–12, and 14–19 Unpatentable
`35 U.S.C. § 318(a)
`
`
`
`
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`
`I.
`
`INTRODUCTION
`
`A. BACKGROUND
`TCT Mobile, Inc. and TCT Mobile (US) Inc. (collectively “TCT”)
`filed a petition (Paper 1, “Pet.”) to institute an inter partes review of claims
`6, 7, 9–12, and 14–19 (the “challenged claims”) of U.S. Patent No.
`9,125,051 B2 (Ex. 1001, “the ’051 Patent”). 35 U.S.C. § 311. TCT
`supported the Petition with evidence including the declaration of Stuart J.
`Lipoff (Ex. 1005). Wireless Protocol Innovations, Inc. (“WPI”) timely filed
`a Preliminary Response. Paper 5 (“Prelim. Resp.”). WPI supported its
`Preliminary Response with evidence including the declaration of Gary
`Lomp, Ph.D. (Ex. 2001). On March 24, 2017, based on the record before us
`at the time, we instituted an inter partes review of claims 6, 7, 9–12, and 14–
`19. Paper 8 (“Decision on Institution” or “Dec.”). We instituted the review
`on the following challenge:
`
`References
`International Patent Publication No. WO 99/61993
`(Ex. 1022, “Abi-Nassif”) and Data-Over-Cable
`Service Interface Specifications,1 Radio Frequency
`Interface Specification, Second Interim Release,
`Document Control No. SP-RFIv1.1-I02-990731
`(Ex. 1019, “DOCSIS 1.1”)
`
`Claims
`challenged
`Basis
`§ 103 6, 7, 9–12,
`and 14–19
`
`After we instituted this review, Patent Owner filed a Patent Owner
`Response in opposition to the Petition (Paper 18, “PO Resp.”) that was
`supported by a Second Declaration from Gary Lomp, Ph.D. (Ex. 2004).
`
`
`1 We refer to the first version of the Data-Over-Cable Service Interface
`Specifications as “DOCSIS.”
`
`2
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`Petitioner filed a Reply in support of the Petition (Paper 24, “Reply”).
`Patent Owner did not move to amend any claim of the ’051 Patent.
`We heard oral argument on December 7, 2017. A transcript of the
`argument has been entered in the record (Paper 32, “Tr.”).
`We have jurisdiction under 35 U.S.C. § 6(c). The evidentiary standard
`is a preponderance of the evidence. See 35 U.S.C. § 316(e); 37 C.F.R.
`§ 42.1(d). This Final Written Decision is issued pursuant to 35 U.S.C.
`§ 318(a) and 37 C.F.R. § 42.73. For the reasons expressed below, we
`conclude that Petitioner has demonstrated by a preponderance of evidence
`that claims 6, 7, 9–12, and 14–19 are unpatentable.
`B. RELATED PROCEEDINGS
`TCT and WPI identified as related proceedings the co-pending district
`court proceedings of Wireless Protocol Innovations, Inc. v. TCL
`Corporation, et al., Case Number 6:15-cv-918 (E.D. Tex.) and Wireless
`Protocol Innovations, Inc. v. ZTE Corporation, et al., Case Number 6:15-cv-
`919 (E.D. Tex.). Pet. 2–3; Paper 4, 2. Additional claims of the instant
`patent, specifically claims 1, 2, 4, 5, 21–23, 25, and 26 of the ’051 Patent,
`are the subject of concurrent proceeding for inter partes review in IPR2016-
`01861.
`WPI identified three issued U.S. patents and two pending U.S. patent
`applications as being related to the ’051 Patent including: U.S. Patent
`Nos. 7,173,921 B2, 8,274,991 B2, and 8,565,256 B2; and U.S. Application
`Nos. 14/078,246 and 14/805,051. Paper 4, 3. The following inter partes
`reviews initiated by TCT are also considered related:
`
`3
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`
`Proceeding
`IPR2016-01492
`
`Status
`Patent No.
`6,381,211 B2 Motion for adverse judgment
`granted: June 6, 2017
`
`IPR2016-01494
`
`8,274,991 B2 Final Written Decision issued
`February 12, 2018
`
`IPR2016-01700
`
`6,381,211 B2 Motion for adverse judgment
`granted: June 6, 2017
`
`IPR2016-01702
`
`6,381,211 B2 Motion for adverse judgment
`granted: June 6, 2017
`
`IPR2016-01704
`
`8,565,256 B2 Final Written Decision issued
`March 1, 2018
`
`
`C. THE ’051 PATENT
`The ’051 Patent relates to “point-to-multipoint communication; in
`particular, the invention relates to control of contention for data slots by
`customer premises equipment in a wireless point-to-multipoint
`communication system.” Ex. 1001, 1:37–40. “Contention” is shorthand for
`the process by which many instances of customer provided equipment (one
`being a “CPE”) negotiate for assignment of data slots available from a base
`station controller (“BSC”). Id. at 1:44–55. The Specification identifies
`problems with conventional methods when two CPEs “collide” while
`requesting a data slot, especially when the traffic from the CPEs is not
`“bursty” (e.g., traffic generated by online games and voice sources). Id.
`at 1:59–2:12. To address such problems, the Specification suggests a system
`of “using a new state machine to control a contention state” that “includes a
`grant pending absent state in which the [CPE] is polled with a unicast
`
`4
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`request slot.” Id. at 2:23–31. The Specification briefly describes the grant
`pending absent state as follows:
`By virtue of the grant pending absent state, the customer
`premises equipment can request a data slot without entering into
`contention and generating excess contention traffic. After a
`suitable delay without more data being received to send
`upstream, the state machine can exit the grant pending absent
`state. This delay preferably is long enough for receipt of new
`non-bursty data for a communication, for example 50 ms.
`Id. at 2:36–42.
`Of the challenged claims, only claims 6, 11, and 16 are independent,
`and dependent claims 7, 9, 10, 12, 14, 15, and 17–19 depend directly from
`one of claims 6, 11, and 16. Id. at 10:42–12:27. Claim 6 is representative
`and recites as follows:
`6. A method of operating a customer premises equipment
`(CPE) unit, comprising:
`transmitting a first bandwidth request to a base station
`controller (BSC) unit in a contention slot;
`receiving a bandwidth grant from the BSC unit;
`transmitting data to the BSC unit within a transmission
`resource specified by the bandwidth grant;
`if additional pending data is available for transmission to the
`BSC unit within the transmission resource:
`transmitting a second bandwidth request to the BSC unit
`within the transmission resource, the second bandwidth
`request requesting a subsequent transmission resource for
`accommodating transmission of the additional pending
`data;
`receiving a subsequent bandwidth grant from the BSC unit;
`transmitting the additional pending data to the BSC unit in the
`subsequent
`transmission resource specified by
`the
`subsequent bandwidth grant;
`
`5
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`if no additional pending data is available for transmission to
`the BSC unit within the transmission resource and if new
`data becomes available for transmission prior to expiry of
`a timeout, transmitting a third bandwidth request to the
`BSC unit in a contention free bandwidth request
`opportunity, the third bandwidth request requesting a
`second
`subsequent
`transmission
`resource
`for
`accommodating transmission of the new data; and
`if no additional pending data is available for transmission to
`the BSC unit within the transmission resource and if no
`new data becomes available for transmission prior to
`expiry of the timeout, transitioning the CPE unit to an idle
`state.
`Id. at 10:42–11:5.
`
`II. ANALYSIS
`A. CLAIM INTERPRETATION
`“A claim in an unexpired patent shall be given its broadest reasonable
`construction in light of the specification of the patent in which it appears.”
`37 C.F.R. § 42.100(b); see also Cuozzo Speed Techs., LLC v. Lee, 136 S. Ct.
`2131, 2142 (2016) (affirming that USPTO has statutory authority to construe
`claims according to Rule 42.100(b)). When applying that standard, we
`interpret the claim language as it would be understood by one of ordinary
`skill in the art in light of the specification, and absent any special definition,
`we give claim terms their ordinary and customary meaning. See In re Suitco
`Surface, Inc., 603 F.3d 1255, 1260 (Fed. Cir. 2010); In re Translogic Tech.,
`Inc., 504 F.3d 1249, 1257 (Fed. Cir. 2007) (“The ordinary and customary
`meaning is the meaning that the term would have to a person of ordinary
`skill in the art in question.” (internal quotation marks omitted)). Only terms
`which are in controversy need to be construed, and then only to the extent
`
`6
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`necessary to resolve the controversy. See Vivid Techs., Inc. v. Am. Sci. &
`Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999).
`In the Decision on Institution, we acknowledged that TCT addressed
`the preambles of claims 6, 11, and 16, and that WPI took no issue with the
`proposed constructions of those preambles “for purposes of [its] Preliminary
`Response.” Dec. 6. No claim terms were explicitly construed in the
`Decision on Institution. Id. WPI continues to have no dispute with TCT’s
`claim construction of the preamble. PO Resp. 9.
`WPI also argues that the broadest reasonable interpretation of
`“transitioning the CPE unit to an idle state,” as recited in claims 6 and 11, is
`“transitioning the CPE unit to an idle state, in which the CPE awaits
`arrival of data packets to send as upstream data to the BSC unit.” PO
`Resp. 9. In so arguing, WPI relies on a commensurate passage in the
`Specification describing idle state 20. Id. (citing Ex. 1001, 6:50–52).
`TCT argues that we should reject WPI’s interpretation because the
`’051 Patent does not define a special meaning for idle state and the cited
`portion of the Specification merely describes one type of “idle state.”
`Reply 9–11. The Specification also provides another description of “idle
`state” that reads: “The state machine preferably also includes an idle state in
`which the customer premises equipment awaits arrival of data packets to
`send as upstream data to the base station controller.” Ex. 1001, 2:43–45.
`However, TCT asserts that all claims are unpatentable even if we were to
`accept WPI’s proposed interpretation. Id. at 11.
`Based on our review of the Specification, we determine that both
`passages cited by the parties support WPI’s argument that “idle state” as
`used in claims 6 and 11 refers to a state in which the CPE awaits arrival of
`
`7
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`data packets to send as upstream data to the BSC. Accordingly, we adopt
`WPI’s interpretation of “idle state.”
`However, we also note that the Specification describes at least two
`different states in which the CPE “awaits arrival of data packets to send as
`upstream data to the BSC.” For example, the CPE awaits arrival of data
`while it is still receiving unicast polling requests from the BSC. See
`Ex. 1001, 7:25–35 (describing grant pending absent state in which “CPE 13
`can use [a] . . . unicast request slot to request a data slot” (i.e., without
`contention) for upstream data “if more data is received” by CPE 13).
`CPE 13 also awaits arrival of data packets when it has no grant pending and
`is not receiving unicast polling requests from BSC 12. Id. at 6:50–52. The
`Specification refers to this type of state as “idle state 20.” The claimed “idle
`state” refers to the second of these two states in which CPE awaits arrival of
`data packets to send as upstream data.
`
`B. THE PARTIES’ POST-INSTITUTION ARGUMENTS
`In our Decision on Institution, we concluded that the argument and
`evidence adduced by TCT demonstrated a reasonable likelihood that claims
`6, 7, 9–12, and 14–19 were unpatentable as obvious based on the challenges
`identified in the table in Part I.A above. Dec. 16. We must now determine
`whether Petitioner has established by a preponderance of the evidence that
`the specified claims are unpatentable over the cited prior art. 35 U.S.C.
`§ 316(e). In this regard, we previously instructed Patent Owner that “any
`arguments for patentability not raised in the [Patent Owner Response] will
`be deemed waived.” Paper 9, 6; see also In re Nuvasive, Inc., 842 F.3d
`1376, 1381 (Fed. Cir. 2016) (holding that patent owner’s failure to proffer
`argument at trial as instructed in scheduling order constitutes waiver).
`
`8
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`Additionally, the Board’s Trial Practice Guide states that the Patent Owner
`Response “should identify all the involved claims that are believed to be
`patentable and state the basis for that belief.” Office Patent Trial Practice
`Guide, 77 Fed. Reg. 48,756, 48,766 (Aug. 14, 2012).
`C. LEGAL STANDARDS
`TCT challenges the patentability of claims 6, 7, 9–12, and 14–19 on
`the grounds that the claims are obvious in light of Abi-Nassif and
`DOCSIS 1.1. To prevail in its challenges to the patentability of the claims,
`TCT must establish facts supporting its challenges by a preponderance of the
`evidence. 35 U.S.C. § 316(e); 37 C.F.R. § 42.1(d). “In an [inter partes
`review], the petitioner has the burden from the onset to show with
`particularity why the patent it challenges is unpatentable.” Harmonic Inc. v.
`Avid Tech., Inc., 815 F.3d 1356, 1363 (Fed. Cir. 2016) (citing 35 U.S.C.
`§ 312(a)(3) (requiring inter partes review petitions to identify “with
`particularity . . . the evidence that supports the grounds for the challenge to
`each claim”)). The burden of persuasion never shifts to WPI. See Dynamic
`Drinkware, LLC v. Nat’l Graphics, Inc., 800 F.3d 1375, 1378 (Fed. Cir.
`2015) (citing Tech. Licensing Corp. v. Videotek, Inc., 545 F.3d 1316, 1326–
`27 (Fed. Cir. 2008)) (discussing the burden of proof in inter partes review).
`The Supreme Court in KSR International Co. v. Teleflex Inc., 550 U.S.
`398 (2007), reaffirmed the framework for determining obviousness as set
`forth in Graham v. John Deere Co., 383 U.S. 1 (1966). The KSR Court
`summarized the four factual inquiries set forth in Graham that we apply in
`determining whether a claim is reasonably likely to be unpatentable as
`obvious under 35 U.S.C. § 103(a) as follows: (1) determining the scope and
`content of the prior art, (2) ascertaining the differences between the prior art
`
`9
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`and the claims at issue, (3) resolving the level of ordinary skill in the
`pertinent art,2 and (4) considering objective evidence indicating obviousness
`or nonobviousness. KSR, 550 U.S. at 406 (citing Graham, 383 U.S. at 17–
`18). In an inter partes review, Petitioner cannot satisfy its burden of proving
`obviousness by employing “mere conclusory statements.” In re Magnum
`Oil Tools Int’l, Ltd., 829 F. 3d 1364, 1380 (Fed. Cir. 2016). Thus, to prevail
`Petitioner must explain how the proposed combinations of prior art would
`have rendered the challenged claims unpatentable. With these standards in
`mind, we address each challenge below.
`D. OBVIOUSNESS IN VIEW OF ABI-NASSIF AND DOCSIS 1.1
`TCT argues that the combination of Abi-Nassif and DOCSIS 1.1
`renders claims 6, 7, 9–12, and 14–19 unpatentable as obvious. Pet. 37–77.
`TCT frames its challenge based on this combination by analyzing it two
`ways, one with Abi-Nassif being modified by teachings in DOCSIS 1.1, id.
`at 37–57, and another with DOCSIS 1.1 being modified by teachings in Abi-
`Nassif, id. at 57–77. We consider the pair of these separately identified
`challenges as if TCT had merely cast its challenge as being based on Abi-
`Nassif and DOCSIS 1.1 considered together.3 For the reasons expressed
`
`
`2 The parties do not dispute that a person having ordinary skill in the art
`refers to a person holding an undergraduate degree in electrical engineering
`or having an equivalent educational experience, and three or more years
`working in a relevant field employing digital communications technology to
`deliver telecommunication services, or alternatively a relevant field
`involving the design of telecommunication products. Pet. 5 (citing Ex. 1005
`¶ 33); PO Resp. 8.
`3 The predecessor to our reviewing court has previously explained that:
`In a case of this type where a rejection is predicated on two
`references each containing pertinent disclosure which has been
`
`10
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`below, we are persuaded that TCT has demonstrated by a preponderance of
`evidence that the combination of Abi-Nassif and DOCSIS 1.1 renders claims
`6, 7, 9–12, and 14–19 unpatentable as obvious.
`1. Overview of Abi-Nassif
`TCT contends that Abi-Nassif “discloses almost every limitation of
`the challenged claims, including using contention, piggyback and non-
`contention requests using unicast polling.” Pet. 21. Abi-Nassif describes a
`medium access control (“MAC”) protocol for coordinating access to a
`shared medium communication network such as data-over-cable using
`hybrid fiber-optic and coaxial cable. Ex. 1022, 3:6–9, 19:23–33. The MAC
`protocol provides rules for resolving collisions among secondary stations
`104 as they request access to upstream channel 107. Id. at 20:19–21:9. The
`MAC protocol includes provisions for secondary stations to access the
`network using contention-free and contention-based methods. Id. at 21:10–
`22:20. Abi-Nassif describes the operating states
`of its network as ACTIVE, INACTIVE, and
`CONTENTION and an ability for secondary
`station 104 to transition from INACTIVE to
`ACTIVE without entering into contention. Id.
`at 24:30–26:4, Fig. 9. Abi-Nassif’s Figure 9,
`reproduced above, is a state diagram reflecting
`
`
`pointed out to the applicant, we deem it to be of no significance,
`but merely a matter of exposition, that the rejection is stated to
`be on A in view of B instead of on B in view of A, or to term one
`reference primary and the other secondary.
`In re Bush, 296 F.2d 491, 496 (CCPA 1961).
`
`11
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`these three states. Although the preferred embodiment of Abi-Nassif is a
`wired network, Abi-Nassif also suggests that its methods may be used over a
`wireless network. Id. at 19:32–20:2.
`2. Overview of DOCSIS 1.1
`DOCSIS 1.1 is a complex and detailed standard by which cable
`providers deliver internet services to subscribers. See generally Ex. 1019. It
`specifies interactions among various hardware in the network, which is
`schematically depicted at a high level in Figure 1-1 that is reproduced below.
`
`
`
`Figure 1-1 illustrates IP traffic over a “Data-Over-Cable” system.
`Figure 1-1 illustrates the communication pathway from customer premises
`equipment to cable modems (“CM”), which relay data traffic over the cable
`network to a “cable modem termination system” (“CMTS”) located at the
`provider’s end. Ex. 1019 § 1.3.1. DOCSIS 1.1 uses a time division multiple
`access (“TDMA”) method for the CM to transmit data upstream in which the
`CMTS manages usage of time slots by CMs via a MAC protocol similar to
`the one discussed in Abi-Nassif. Id. §§ 3.5.2, 7.1. In operation, the CMTS
`regularly broadcasts a Bandwidth Allocation Map (“MAP”) message, which
`allocates upstream transmission opportunities (i.e., bandwidth) among the
`various CMs. Id. §§ 6.3.4, 7.1.1 et seq., Appendix O (“Bandwidth
`Allocation Map”); Ex. 1005 ¶¶ 146–147.
`The CMTS may broadcast an interval for requesting bandwidth,
`which the CMs interpret as an invitation to contend for bandwidth by
`
`12
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`sending requests during that interval. Ex. 1019 § 7.1.2.1, § 7.1.3.
`Alternatively, the CMTS may unicast an interval to a specific CM, which
`allows a specific CM to request a data slot without contending with other
`CMs. Id. DOCSIS 1.1 also offers enhanced quality of service (“QoS”),
`when compared to DOCSIS 1.0, in which certain types of data (e.g., voice
`over IP, high bandwidth FTP) that require high levels of network
`performance (e.g., high bandwidth, low latency, low jitter) are prioritized.
`Id. §§ 8.1.1.2, 8.1.6.
`DOCSIS 1.1 describes the use of two “service flows” that use unicast
`polling to prioritize certain types of upstream data transmission. One, the
`real-time polling service (“rtPS”), enables the CM to reserve upstream data
`slots for real-time traffic like voice over IP (“VoIP”) while avoiding having
`to contend for those slots. Id. § 8.2.2, C.2.2.6.4; Ex. 1005 ¶ 192. The
`polling interval for the rtPS is on the order of tens of milliseconds or less.
`Ex. 1019 § 8.2.2. Another, the non-real-time polling service (“nrtPS”),
`reserves upstream data slots for applications like high bandwidth FTP
`transfers. Id. § 8.2.4. Like the rtPS, the nrtPS also allows the CM to reserve
`data slots without resorting to contention. Id.; Ex. 1005 ¶¶ 193–199.
`3. Claim 6
`TCT contends that Abi-Nassif describes every claimed element (other
`than the timeout period recited in claim 6), Pet. 21, and DOCSIS 1.1
`describes every claimed element “nearly identical[ly],” but using different
`terminology, id. at 28. TCT also explains in detail how the teachings of Abi-
`Nassif and DOCSIS 1.1 would have rendered the claimed methods obvious
`to an ordinarily skilled artisan. Id. at 37–56, 57–73. TCT also cites
`testimony from Mr. Lipoff in which he explains in great detail how specific
`
`13
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`functionality within Abi-Nassif and DOCSIS 1.1 correlate to the specific
`steps recited in the claimed method and system. Id.
`Claim 6 is directed to a method of operating a customer premises
`equipment (CPE) unit. The first three steps (1) involve transmitting a first
`bandwidth request to the BCS in a contention slot, receiving a bandwidth
`grant, and then transmitting data to the BSC unit within a specified
`transmission resource. The next three steps (2) involve transmitting a
`second bandwidth request, a subsequent transmission resource for
`accommodating transmission of the additional pending data, to the BSC unit,
`receiving the grant, and transmitting additional pending data to the BSC unit.
`The next elements involve transmitting a third bandwidth request or
`transitioning to an idle state, based on the following conditions:
`if no additional pending data is available for transmission to the
`BSC unit within the transmission resource and if new data
`becomes available for transmission prior to expiry of a timeout,
`transmitting a third bandwidth request to the BSC unit in a
`contention free bandwidth request opportunity, the third
`bandwidth request requesting a second subsequent transmission
`resource for accommodating transmission of the new data; and
`if no additional pending data is available for transmission to the
`BSC unit within the transmission resource and if no new data
`becomes available for transmission prior to expiry of the timeout,
`transitioning the CPE unit to an idle state.
`Ex. 1001, 10:60–11:5.
`WPI does not contest that Abi-Nassif and DOCSIS 1.1 describe steps
`denoted as (1)–(2) above, but argues only that references fail to teach or
`suggest the conditions of claim 6 reproduced above, i.e., the last two
`elements. We conclude that TCT’s contentions regarding the steps denoted
`as (1)–(2) above are persuasive. See Pet. 37–56, 57–73. WPI argues that
`
`14
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`TCT acknowledges Abi-Nassif’s failure to disclose the “expiry of a time
`out” condition and instead relies on DOCSIS 1.1 for the teaching of such a
`condition. PO Resp. 24–25 (citing Pet. 49). WPI counters, however, that
`DOCSIS 1.1 has no teaching or suggestion of timeouts in connection with
`operating a unit in an idle state. Id. at 25 (citing Ex. 2001 ¶ 18). We address
`WPI’s specific arguments below.
`WPI argues that TCT has misread Abi-Nassif as teaching that “unicast
`requests are used after piggybacking transmissions have ended.” Id. at 26–
`27 (citing Ex. 2001 ¶ 36). WPI also argues that “[t]he inevitability of
`transitions from contention-oriented to contention-free operations suggests
`nothing about a transition from one contention-free operation (e.g.,
`piggybacking) to a different contention-free operation (e.g., unicast
`requests).” Id. at 27–28 (citing Ex. 2001 ¶ 37). We do not agree.
`As TCT points out, Abi-Nassif discloses that “[u]pon transmitting all
`of its data, the MAC User transitions back into the INACTIVE state,” but
`when new data to be transmitted are received, “a contention-free opportunity
`to transmit a request” is provided. Pet. 48; Reply 13–14 (citing Ex. 1022,
`24:31–25:5, 25:17–21). Figure 9 of Abi-Nassif, reproduced above,
`illustrates the transitions from the ACTIVE state to the INACTIVE state and
`from the INACTIVE state to the ACTIVE state, with the latter through a
`non-contention request. Reply 14–15 (citing Ex. 1022, Fig. 9, 24:30–25:5,
`25:17–21).
`WPI also argues that TCT has misconstrued DOCSIS 1.1 by
`rearranging elements thereof, by moving functions of the CMTS to the cable
`modem. PO Resp. 28–29, 31, 34–35, 45–46, 51–52 (citing Pet. 49–50, 52,
`53, 72–74; Ex. 2001 ¶¶ 40–41, 52–53). More specifically, WPI argues that
`
`15
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`the “Timeout for Active QoS Parameters,” relied upon by TCT, is not an
`operation of the cable modem, but rather an operation of the CMTS,
`correlated with the BSC of claim 6. Id. at 29–30, 46 (citing Ex. 2001 ¶¶ 41,
`53). WPI continues that any incorporation of DOCSIS 1.1’s cited
`functionalities into the system of Abi-Nassif would result in deactivation to
`the primary station, contrary to claim 6. Id. We do not agree.
`As TCT points out, claim 6 does not recite that the timeout must be
`maintained by the wireless communication unit, and that a person of
`ordinary skill in the art would have understood that “BSC could maintain the
`timeout and notify the [wireless communication unit] regarding the change
`in state of the timeout.” Reply 15–16 (citing Ex. 1001, 10:15–18, 10:24–25;
`Ex. 1019, 251; Ex. 1057 ¶¶ 10–11). TCT also points out that WPI’s
`declarant acknowledged that the cited element of claim 6 would be met
`where the base station maintains the timer and then tells the wireless
`communication unit that the timeout has expired, as taught by DOCSIS 1.1.
`Id. (citing Ex. 1056, 79:19–25).
`WPI also argues that DOCSIS 1.1 discloses that although one service
`flow is inactive, another service flow is still active, and finds that TCT’s
`declarant acknowledges that at least one service flow is active at all times.
`PO Resp. 30–32, 47–51 (citing Pet. 35–36, 50, 52–53, 72–74; Ex. 2006,
`32:8–10, 34:16–23, 41:13–22). WPI asserts that claim 6 requires operating
`the wireless communication unit is an “idle state,” and not merely operating
`with a service flow in an idle state. Id. We do not agree.
`The instant ground of unpatentability relies on the combination of
`Abi-Nassif and DOCSIS 1.1 to teach an “idle state,” as pointed out by TCT.
`Reply 17–18 (citing Pet. 48–49). In the INACTIVE state of Abi-Nassif, the
`
`16
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`secondary station has unicast polling opportunities, where those polling
`opportunities would time out if not used, as taught by DOCSIS 1.1. Id.
`(citing Ex. 1022, 24:30–25:5, 25:20–21; Ex. 1019, 251). We are not
`persuaded that the INACTIVE state in Abi-Nassif necessarily differs from
`the claimed “idle state,” such that the combination suggests “operating the
`wireless communication unit in an idle state,” per claim 6.
`With respect to the same aspect in DOCSIS 1.1, WPI also argues that
`the “idle state” shown in Figure K-1 of DOCSIS 1.1 is not associated with
`the “timeout” relied upon by TCT. PO Resp. 32–34 (citing Ex. 1019, 284,
`Fig. K-1; Ex. 2001 ¶¶ 18, 30, 45–46; Ex. 2004 ¶¶ 6–8). This is not
`persuasive, however, because the combination of Abi-Nassif and
`DOCSIS 1.1 does not seek to incorporate the idle state of DOCSIS 1.1’s
`Figure K-1, as noted by TCT. Reply 19.
`Additionally, WPI argues that “DOCSIS 1.1 lacks the entire concept
`of a grant pending absent state,” and that “[c]laim 6 recites aspects of the
`grant pending absent state.” PO Resp. 43–44. Although it is correct that the
`specification of the ’051 Patent discusses a “grant pending absent state,” as
`discussed above in Section I.C., the challenged claims do not recite such a
`limitation. As such, we are not persuaded that DOCSIS 1.1’s omission of
`that specifically-recited state is problematic, given the discussions of Abi-
`Nassif and DOCSIS1.1, and their functionalities discussed above.
`With respect to combining Abi-Nassif and DOCSIS1.1, TCT argues
`that because Abi-Nassif expressly incorporates DOCSIS 1.0, an ordinarily
`skilled artisan would have found it obvious to incorporate the revised
`DOCSIS 1.1 and its improvements into Abi-Nassif to provide higher QoS
`and increase the efficiency of Abi-Nassif’s use of bandwidth. Pet. 47–51,
`
`17
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`55–56, 59–60 (citing Ex. 1005 ¶¶ 261–270, 279, 283–286, 305–315). TCT
`also argues that because Abi-Nassif explicitly incorporates DOCSIS 1.0 and
`DOCSIS 1.1 indicates that it is backward compatible with DOCSIS 1.0, an
`ordinarily skilled artisan would have used teachings in DOCSIS 1.1 relating
`to enhanced QoS features to improve the implementation of unicast polling
`already described in Abi-Nassif. Id. at 50–51 (citing Ex. 1005 ¶¶ 262–264,
`266–270).
`WPI counters that motivation, arguing that the “expiration of the timer
`associated with a service flow causes that service flow to become inactive
`[per DOCSIS 1.1]” and that “[i]ncorporating such functionality from a
`service flow into the operation of the MAC User [per Abi-Nassif] would not
`cause the cable modem to operate in its idle state, but rather would end an
`upstream transmission process for one service flow.” PO Resp. 35–36
`(citing Pet. 50). This is not persuasive, however, in view of Dr. Lomp’s
`acknowledgement that a person of ordinary skill in the art would have
`looked to the DOCSIS protocol generally to figure out how to implement the
`system of Abi-Nassif. See Ex. 1056, 64:19–21.
`Lastly, WPI argues that although TCT cites to an increase the
`efficiency of the use of bandwidth as a motivation to combine Abi-Nassif
`and DOCSIS1.1, the release of transmission reservations, per DOCSIS 1.1,
`is distinct from permitting request opportunities to be released, and TCT has
`failed to demonstrate equivalence to show increased efficiency. PO Resp. 36
`(citing Pet. 51; Ex. 2001 ¶ 41). TCT points out that DOCSIS 1.1 discloses
`that the intent of a service flow “is to reserve upstream transmission
`opportunities,” and that request opportunities are used to obtain transmission
`opportunities, used to make transmission reservations. Reply 21 (quoting
`
`18
`
`

`

`IPR2016-017041865
`Patent 9,125,051 B2
`Ex. 1019 § 8.2.2). Although we agree with WPI that the releases of
`transmission reservations and request opportunities are different, we are
`persuaded either can potentially provide for greater bandwidth use efficiency
`and would have motivated the combination of Abi-Nassif and DOCSIS 1.1.
`For all the reasons expressed above, we determine that TCT has
`established by a preponderance of evidence that the combined teachings of
`Abi-Nassif and DOCSIS 1.1 render claim 6 obvious.
`4. Dependent Claims 7, 9, and 10
`Based on our review of the record, we determine that TCT has
`demonstrated by a preponderance of evidence that the combined teachings
`of Abi-Nassif and DOCSIS 1.1 render dependent claims 7, 9, and 10
`unpatentable as obvious. WPI does not contend that the limitations
`introduced in claims 7 and 10 are a basis for patentability over the
`combination of Abi-Nassif and DOCSIS 1.1. PO Resp. 37, 52. Instead,
`WPI argues that claims 7 and 10 are patentable due to their dependency from
`claim 6 and the deficiencies that WPI marshals against TCT’s challenges to
`claim 6. Id.
`With respect to claim 9, WPI assert’s TCT’s analysis of claim 9
`“highlights the impropriety of Petitioner’s reliance on the inactivity of the
`Polling Service Flow as the claimed ‘idle state.’” Id. at 37, 52–53. WPI
`continues that TCT argues that only a particular service flow enters an
`inactive state, while one or more other service flows remains active, which is
`different from “transitio

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