throbber
Paper No. ____
`Filed: September 8, 2020
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`ZTE (USA), INC. AND
`SAMSUNG ELECTRONICS CO., LTD.,
`Petitioners
`
`v.
`
`BELL NORTHERN RESEARCH, LLC,
`Patent Owner
`
`
`
`Case: IPR2019-01365
`U.S. Patent No. 7,039,435
`
`
`
`PETITIONER’S REPLY TO PATENT OWNER’S RESPONSE
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`TABLE OF CONTENTS
`INTRODUCTION .......................................................................................... 1
`I.
`II. CLAIM CONSTRUCTION ........................................................................... 1
`III. THE ’435 PATENT IS NOT ENTITLED TO AN EARLIER
`INVENTION DATE ....................................................................................... 5
`IV. CLAIMS 1-3 AND 6 ARE UNPATENTABLE ............................................ 9
`A. Ground 1: Baiker Anticipates Claims 1-3 ............................................ 9
`B. Ground 2: The Baiker-Werling Combination Renders Obvious
`The Challenged Claims ...................................................................... 14
`C. Ground 3: Irvin Anticipates Claims 1-3 ............................................. 17
`D. Ground 4: The Irvin-Myllymäki Combination Renders Obvious
`The Challenged Claims ...................................................................... 20
`Ground 5: The Bodin-Irvin Combination Renders Obvious The
`Challenged Claims ............................................................................. 22
`V. BNR’S EVIDENCE OF SECONDARY CONSIDERATIONS IN
`SUPPORT OF NON-OBVIOUSNESS FAILS ............................................ 24
`VI. CONCLUSION ............................................................................................. 27
`
`E.
`
`
`
`
`
`
`i
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`I.
`
`INTRODUCTION
`Bell Northern Research, LLC’s (“BNR”) arguments in its Response (Paper
`
`19) should be rejected and the claims found unpatentable for at least the reasons set
`
`forth in the record, including the additional reasons and evidence discussed below.
`
`II. CLAIM CONSTRUCTION
`Petitioner proposed two possible interpretations of the term “position to a
`
`communications tower,” recited in claim 1.
`
`First interpretation
`
`Second interpretation
`
`“transmit signal strength of a communications path
`between the communications tower and the portable cell
`phone.” (Petition, 10-12; Ex. 1003, ¶¶33-34.)1
`Plain and ordinary meaning, where a “position” is
`simply a location or distance relative to another object.
`(Petition, 12-13; Ex. 1003, ¶35.)
`The Petition demonstrates the unpatentability of claim 1 under both the first
`
`interpretation (Grounds 1-4) and the second interpretation (Ground 5). (Petition, 5-
`
`6, 11-13; Ex. 1003, ¶¶34-35.)
`
`
`1 All citations, unless otherwise noted, are to this IPR2019-01365 record initiated by
`
`ZTE (USA), Inc. (termination pending), to which Petitioner was joined. (Paper 25,
`
`5-7.) Petitioner Samsung’s petition and supporting evidence are substantially
`
`identical to those submitted in this proceeding. See IPR2020-00697, Paper 1 at 1.
`
`1
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`The Board agreed that this term encompasses the first interpretation and “may
`
`also encompass [the second interpretation] . . . which appears to fall within the words
`
`of the claim.” (Paper 13 (“Decision”), 17-18.) The Board added, “[w]e will further
`
`consider the scope of this phrase during institution of this proceeding.” (Id., 18.)
`
`BNR agrees with Petitioner’s first interpretation (Response, 2) but disagrees with
`
`both Petitioner and the Board with respect to the second interpretation (id., 3-5, 8).
`
`As explained below, BNR’s position is misplaced and should be rejected. (Ex. 1030,
`
`¶¶8-10.)2
`
`BNR’s arguments do not overcome the intrinsic and extrinsic evidence
`
`supporting Petitioner’s position that the subject claim term encompasses the second
`
`interpretation. (Petition, 12-13; Ex. 1003, ¶135; Ex. 1001, 2:18-21, 3:4-6, 6:33-37;
`
`Ex. 1019, 46-51; Ex. 1014, 4; Ex. 1017, 3; Ex. 1030, ¶¶11-12.) Indeed, the evidence
`
`supplied by BNR and relied upon by Dr. Horenstein confirms that the (i) transmit
`
`signal strength and (ii) location or distance aspects of “position to a communications
`
`tower” (Response, 3-5; Ex. 2022, ¶¶38, 43-45) fall within the scope of this term.
`
`
`2 While Petitioner does not agree with BNR’s slightly different definition of a
`
`POSITA (Response, 1), Dr. Wells’ opinions are equally applicable under both
`
`definitions. (Ex. 1031, ¶¶6-7.)
`
`2
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`For example, to support BNR’s argument that “position” be limited to signal
`
`strength, Dr. Horenstein selects certain examples from the Lee textbook (Ex. 2003).
`
`(Response, 4-5; Ex. 2022, ¶¶43-44.) But Dr. Horenstein ignores the disclosures in
`
`Lee that show that “position to a communications tower” is related to geographical
`
`distance and position. For instance, Lee teaches how mobile cell sites are designed
`
`and cell areas are configured. In planning such cell sites, “cell boundaries are
`
`defined” around communication towers. (Ex. 2003, 9.) These boundaries are
`
`defined in terms of a cell radius and a distance between two adjacent frequency-
`
`reuse cells. (Id., 9-10.) As such, Lee does not support the notion that the claimed
`
`“position” is limited to transmit signal strength to the exclusion of any relationship
`
`to location or distance as advocated by BNR. Rather, Lee informs a POSITA that
`
`the term also relates to location or distance to a communication tower.3 (Ex. 1030,
`
`
`3 BNR’s attempt to limit any interpretation of the term to “account[] for obstructions
`
`between the phone and the tower” (Response, 8) should also be rejected as it
`
`impermissibly attempts to further narrow the first interpretation by adding unclaimed
`
`subject matter. (Ex. 2023, 89:16-90:2.) Continental Circuits LLC v. Intel Corp.,
`
`915 F.3d 788, 797-98 (Fed. Cir. 2019) (finding that importing a limitation from the
`
`specification into the claim is improper).
`
`3
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`¶13.)
`
`Additionally, Dr. Horenstein has previously testified that “position” relates to
`
`“location or distance” (or related terms such as proximity or vicinity) within a
`
`communication system, which contradicts his positions here. For example, in other
`
`IPR proceedings related to the same District Court matter as this IPR, Dr. Horenstein
`
`opined as follows:
`
`Given the close proximity of base stations in a cellular
`telephone network, the latter are designed with the
`assumption that the user’s phone will typically be
`located in the vicinity of a base station (comprising the
`existence of a “cell”) . . . In contrast, a satellite phone must
`communicate with a distant, orbiting satellite. The
`position of the satellite (compass bearing and
`elevation) relative to the phone must be ascertained
`using the global positioning system (GPS), then the rf
`beam must be directed toward the satellite.
`
`(IPR2019-01319, Ex. 2053, ¶121 (emphasis added); IPR2019-01320, Ex. 2053,
`
`¶121.) Dr. Horenstein’s testimony above compares “[t]he position of the satellite”
`
`(emphasis added) to “compass bearing and elevation” (i.e., location). Dr. Horenstein
`
`also testified that this “position of the satellite” (emphasis added) is “relative to the
`
`phone” (emphasis added), and that such “position” “must be ascertained using the
`
`4
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`global positioning system (GPS).” Thus, Dr. Horenstein agrees that the term
`
`“position” is “related to distance or location.”
`
`And contrary to BNR’s suggestions (Response, 7-8), the Board’s analysis is
`
`consistent with the District Court’s interpretation. As the Board noted, the District
`
`Court “construed this term to have its plain meaning, [but] the District Court
`
`interpreted the plain meaning as broader than distance, including ‘the relationship to
`
`the phone to the tower in all its aspects, whether it’s distance or obstructions or
`
`whatever.’” (Decision, 16-17 (emphasis in original) (quoting Ex. 2004, 57:20-24).)
`
`Thus, the Board recognized the Court’s view that the term be construed broader than
`
`what BNR advocates. (Id.; see also Ex. 2004, 50:4-12, 55:8-10, 55:18-56:1, 56:13-
`
`25; Ex. 2023, 89:29-90:2.) Indeed, the Board added some clarity to the District
`
`Court’s understanding by recognizing that the term appears to encompass both
`
`interpretations. (Decision, 17-18; Ex. 2004, 55:8-10, 57:20-24.)
`
`Regardless of the dispute over the first and second interpretations, the record
`
`shows that the challenged claims are unpatentable under both interpretations.
`
`III. THE ’435 PATENT IS NOT ENTITLED TO AN EARLIER
`INVENTION DATE
`In an effort to antedate Baiker, BNR ignores the Board’s guidance and submits
`
`essentially the same arguments that the Board preliminarily rejected. (Response, 17-
`
`24; Decision, 10-12; Paper 8 (POPR), 60-64.)
`
`5
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`For instance, BNR ignores the Board’s caution that “Patent Owner does not
`
`provide an explicit analysis of [the] Invention Submission document comparing it to
`
`the limitations of the challenged claims.” (Decision, 11 (emphasis added).)
`
`BNR’s table does not show that “that no later than February 28, 2001, the inventors
`
`possessed the subject-matter as used within the claimed invention” (Response, 18-
`
`20) because it does not include all the claim limitations. Specifically, BNR omits at
`
`least the following claim limitations from its table:
`
` “power circuit” (Ex. 1001, 8:3 (emphasis added)); and
`
` “[a power governing subsystem,] coupled to said location sensing
`
`subsystem that determines a proximity transmit power level of said
`
`cell phone based on said location and determines a [transmit power
`
`level for said portable cell phone . . .]” (id., 8:9-13 (emphasis added)).
`
`(Response, 18-20.) Thus, BNR cannot prove conception as to at least those missing
`
`limitations, as BNR acknowledges. (Response, 24 (citing to Coleman v. Dines, 754
`
`F.2d 353 (Fed. Cir. 1985)).)
`
`BNR’s table also fails to support conception of other features. For example,
`
`the two portions of the Invention Submission document that allegedly support
`
`conception of “a network adjusted transmit power level as a function of a position
`
`to a communications tower” (Response, 18) do not describe any “network adjusted”
`
`power level or a “position to a communication tower,” let alone their relationship.
`
`6
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`(Ex. 2013, 1.) Named inventor Philip Mooney of the ’435 patent agreed. (Ex. 2009,
`
`215:7-14, 217:6-14; see also Decision, 11-12.)
`
`To overcome this issue, BNR now points to Mr. Mooney’s testimony
`
`regarding “the standard way in which a cell phone would control the power,” which
`
`contradicts his previous testimony, to allege he simply acknowledged “a well-known
`
`cellular concept.” (Response, 21 (quoting Ex. 2009, 215:15-216:4).) BNR’s shift
`
`shows Mr. Mooney’s testimony should be afforded little or no weight. First, Mr.
`
`Mooney acknowledged that “he is not familiar enough with the industry” (Ex. 2009,
`
`215:21-216:4) and so he is unqualified to opine on what BNR alleges. Further, he
`
`admits that the Invention Submission document fails to address that standard way of
`
`controlling the transmission power. (Id., 217:13-14.)
`
`BNR’s reliance on Mr. Mooney’s testimony (Response, 18-20 (citing to Ex.
`
`2009)) should also be rejected as it remains unexplained. Despite the Board faulting
`
`BNR for citing to essentially the same testimony “without adequate explanation or
`
`elaboration . . . of how the testimony supports conception,” BNR provides nothing
`
`to help further evaluate the same evidence considered pre-institution. (Decision, 12;
`
`Response, 18-20; POPR, 61.)
`
`Accordingly, BNR failed to establish earlier conception to antedate Baiker as
`
`prior art in this proceeding.
`
`7
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`The Board need not reach BNR’s arguments regarding diligence since the
`
`perquisite showing of conception is not met. But even if conception is found, BNR’s
`
`attempt to antedate Baiker fails because BNR has not met its burden to show
`
`diligence.
`
`BNR’s “diligence” timeline (Response, 26) actually shows several lengthy
`
`periods of inactivity rendering it insufficient to demonstrate reasonably continuous
`
`diligence. Perfect Surgical Techniques, Inc. v. Olympus Am., Inc., 841 F.3d 1004,
`
`1007, 1009 (Fed. Cir. 2017).
`
`BNR’s timeline and associated arguments fail to explain at least three long
`
`periods of inactivity: (1) from March 2001 to April 2001, (2) from April 2001 to
`
`July 27, 2001, and (3) from August 15, 2001 to September 28, 2001, all of which
`
`span more than a month. (Response, 26.) Lesser periods of inactivity have been
`
`found inadequate to support diligence. See In re Mulder, 716 F.2d 1542, 1545 (Fed.
`
`Cir. 1983) (finding two-day period of inactivity as fatal); Fitzgerald v. Arbib, 268
`
`F.2d 763, 766 (CCPA 1959) (finding lack of diligence with less than one month of
`
`inactivity). Further, BNR’s overgeneralization of its cited testimony is far too
`
`speculative to support a finding that BNR was diligent through its constructive
`
`reduction of practice date. (Response, 27.) GEP Power Products, Inc. v. Arctic Cat
`
`Inc., IPR2016-01388, Paper 31 at 16 (PTAB Dec. 5, 2017) (citing Kendall v. Searles,
`
`173 F.2d 986, 993 (CCPA 1949) (holding that testimony of a general nature is not
`
`8
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`sufficiently corroborative)).
`
`Thus, the evidence of diligence is insufficient to antedate Baiker as prior art.
`
`IV. CLAIMS 1-3 AND 6 ARE UNPATENTABLE
`A. Ground 1: Baiker Anticipates Claims 1-3
`Contrary to BNR’s suggestions (Response, 27-29) preliminarily rejected by
`
`the Board (Decision 21), the phrase “network adjusted” in the term “network
`
`adjusted transmit power level” is clearly an adjective describing transmit power level
`
`and thus cannot be considered a verb requiring an active action by the network.
`
`BNR’s citation to the specification (Response, 28 (citing Ex. 1001, 3:31-42)) fails
`
`as the cited portion does not explicitly state the purpose of “communications” with
`
`the network, let alone mention that it is for setting the network adjusted transmit
`
`power level. (Ex. 1001, 3:31-42.) It also fails to indicate what specific affirmative
`
`action the network performs during the “communications.” (Id.)
`
`As Petitioner explained (and the Board preliminarily agreed), “[t]he claim
`
`requires a ‘network adjusted’ transmit power level [and] Baiker discloses that the
`
`quality signal reflects to the signal strength of the network path to the cell tower
`
`(base station), and is used to adjust the power level.” (Decision, 21 (emphasis
`
`added); Petition, 18; Ex. 1003, ¶¶45-56; Ex. 1004, ¶34.) This reading is consistent
`
`with the portion of the ’435 patent that immediately follows BNR’s cited portion,
`
`which states that the network adjusted transmit power level is merely based on a
`
`9
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`transmit signal strength of a communications path. (Ex. 1003, ¶¶45, 87; Ex. 1001,
`
`3:39-41.)
`
`BNR is misplaced that “there is no explanation of how the RF amplifier
`
`functions to provide a network adjusted power-level.” (Response, 29; id., 30-32.)
`
`To support its position, BNR sets up a straw man by relying on selected deposition
`
`testimony by Dr. Wells (Ex. 2023). (Response, 30-32.) In reality, Dr. Wells was
`
`asked general questions about RF amplifiers, and was then asked a separate question
`
`about paragraph 1165 of his Expert Report (Ex. 1032) in a related District Court
`
`case. (Ex. 2023, 81:24-83:6.) Paragraph 1165 relates to the analysis of claim 6
`
`under Ground 2 in this IPR, where Dr. Wells demonstrated that Werling provides
`
`the well-known teaching of using an integrated circuit to embody some of the
`
`claimed circuitry. In this regard, Dr. Wells opined that since “Baiker does not
`
`expressly provide implementation details of its construction, portable cell phones
`
`at the time normally used an ‘integrated circuit’ to control operation of the
`
`phone while maintaining portability of the device.” (Ex. 1032, ¶1165 (emphasis
`
`added); Ex. 1030, ¶¶14-17.)
`
`BNR impermissibly attempts to tie Dr. Wells’ testimony about the lack of an
`
`explicit disclosure of an integrated circuit in Baiker, to an argument that Baiker fails
`
`to disclose the implementation of the RF amplifier. (Response, 31-32.) This
`
`misdirection is irrelevant to the teachings of Baiker regarding the limitations of claim
`
`10
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`1. As Petitioner demonstrated, the claimed “power circuit” is Baiker’s “RF
`
`amplifier,” alone or together with the “control” and “associated electrical
`
`connections.” (Petition, 16; Ex. 1003, ¶43.)
`
`BNR’s suggestion that “Baiker does not produce a power level adjusted by a
`
`network as required by the claim” because a “POSITA would have understood that,
`
`given the same input, an ordinary RF amplifier will always produce the same power
`
`output” (Response, 30) ignores the extensive record contradicting this point.
`
`Baiker’s “RF amplifier 10 is regulated by a control 15,” which includes an “input
`
`provided for a quality signal supplied by the base station,” where the “quality signal”
`
`serves to indicate a transmit signal strength of a communications path between the
`
`“base station” and “mobile telephone.” (Petition, 14, 16-17; Ex. 1003, ¶¶40, 46; Ex.
`
`1004, ¶¶[0028], [0031]).4 This is shown in Figure 3, reproduced and annotated
`
`
`4 During deposition, Dr. Wells explained that an amplifier with a fixed gain would
`
`have the same output given the same inputs and objected to BNR’s suggestion that
`
`ordinary RF amplifiers have fixed gain. (Ex. 2023, 82:12-18; see also id., 82:5-11
`
`(clarifying that variable gain RF amplifiers produce different output power given the
`
`same input).) But this distinction is irrelevant to Baiker’s disclosure regarding the
`
`limitation at issue.
`
`11
`
`PUBLIC VERSION
`
`

`

`below.
`
`Case IPR2019-01365
`
`
`
`(Ex. 1004, FIG. 3 (annotated); Ex. 1003, ¶43.) Given the well-known
`
`implementation details of Baiker’s electrical components, express disclosure of the
`
`same would have been unnecessary. (Ex. 1003, ¶ 62; Ex. 1030, ¶¶18-19; see also
`
`Decision at 20-21.)
`
`BNR’s argument that Baiker does not teach producing a power level adjusted
`
`by the network (Response, 32-33) similarly lacks merit. First, the claim does not
`
`require that the network adjust the power level as discussed above. Second, just like
`
`the ’435 patent, Baiker discloses that the “quality signal” is indicative of a transmit
`
`12
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`signal strength of a communications path between the base station and mobile
`
`telephone. (Petition, 17-18; Ex. 1003, ¶46; Ex. 1004, ¶[0031]; Ex. 1030, ¶¶20-21.)5
`
`Moreover, Baiker’s power level does not depend only on the measured
`
`distance (Response, 35-37) because as explained, Baiker’s “control 15” regulates the
`
`RF amplifier 10 based on “a first input for a distance signal, which is detected and
`
`processed by the distance sensor 7 and the sensor electronics 14” and “a second
`
`input … provided for a quality signal supplied by the base station.” (Ex. 1004,
`
`¶[0028] (emphasis added); Ex. 1003, ¶52; Petition, 23-24.) The first input is the
`
`claimed “proximity transmit power level,” the second input is the claimed “network
`
`adjusted transmit power level,” and Baiker uses both to determine the claimed
`
`“transmit power level.” (Ex. 1030, ¶¶22-24.)6
`
`
`5 Contrary to BNR’s assertions (Response, 33-34), the file history does not establish
`
`a distinction between providing data to a cell phone for general-purpose use and
`
`transmit power level data (Ex. 1002, 73) nor did the Examiner recognize such a
`
`distinction (id., 27).
`
`6 And contrary to BNR’s suggestion (Response, 37), Baiker’s control 15 further
`
`reduces the transmit power level with good connection quality. (Ex. 1003, ¶¶50-52;
`
`Ex. 1004, ¶[0032], Petition, 24.)
`
`13
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`Given BNR makes no separate argument for claims 2-3 with respect to Baiker,
`
`claims 2-3 are anticipated by Baiker for the previously provided reasons. (Petition,
`
`24-26.)
`
`B. Ground 2: The Baiker-Werling Combination Renders Obvious
`The Challenged Claims
`BNR mostly reargues its previously failed arguments with respect to the
`
`Baiker-Werling combination. (Response, 38-47; POPR, 33-38; Decision, 25-28.)
`
`The Board should affirm its preliminary findings, for the reasons discussed below.
`
`Werling discloses a “power circuit” comprising a “transmitting circuit”
`
`coupled to “an antenna” that includes a “power amplifier.” (Petition, 29-30; Ex.
`
`1003, ¶¶60-61; Ex. 1005, 3:58-4:3.)
`
` Notwithstanding BNR’s
`
`irrelevant
`
`categorization that the “power circuit” in Werling being “basically an antenna-
`
`switching network,” and that “a POSITA would have understood that the ‘power
`
`regulation device’ disclosed in Werling is really a power redistribution device[.]”
`
`(Response, 38-40 (emphasis in original)), BNR does not dispute Werling discloses
`
`a “power circuit” that includes a power amplifier coupled to an antenna (id.).
`
`BNR’s assertions regarding a lack of motivation to arrive at the Baiker-
`
`Werling combination (Response, 41-47) are similarly unavailing.
`
`First, as BNR acknowledges, under Ground 2 Petitioner relies on Werling’s
`
`teachings of a “power circuit” (claim 1) and “integrated circuit” (claim 6).
`
`(Response, 38 (citing Petition, 29-35).) Indeed, the Petition explains in detail why
`
`14
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`it would have been obvious to implement the functionality disclosed and relied upon
`
`in Baiker utilizing a power circuit or integrated circuit as disclosed by Werling.
`
`(Petition, 30-31, 32-35; Ex. 1003, ¶¶62-63, 70-75.) Rather than focusing on this
`
`proposed combination, BNR touts alleged differences between Baiker and Werling
`
`with respect to the manner in which they disclose power regulation. (Response, 44-
`
`47.) But given that Baiker (not Werling) is relied upon for the functionality carried
`
`out by the claimed power circuit (Petition, 29-31; Ex. 1003, ¶¶60-64), BNR’s
`
`arguments simply miss the mark. (Ex. 1030, ¶¶25-27.) Indeed, the ’435 patent itself
`
`discloses that the arrangement of its power circuit was “typical” in the art. (Ex.
`
`1001, 3:31-42; Ex. 1003, ¶¶61-62; Petition, 29-31; Ex. 1031, 295:2-17 (Dr.
`
`Horenstein acknowledging that an integrated circuit or a microprocessor would have
`
`been used for RF circuitry in cell phones at the relevant time), 296:12-17, 304:23-
`
`305:8.)
`
`Second, BNR’s postulated significant differences between Baiker and
`
`Werling (Response, 44-45) boil down to minor variations between the references.
`
`For example, BNR provides no support for the assertion that unlike Baiker,
`
`“detection [in Werling] is a simple ‘yes-or-no’ determination obtained by measuring
`
`humidity and temperature.” (Response, 44-45.) And in any event, both Baiker and
`
`Werling include proximity detectors, and there is nothing in the claims at issue that
`
`require any particular type of proximity detector. Thus, such differences are
`
`15
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`immaterial, since both references disclose using proximity detectors for detecting
`
`the presence of humans, and to limit emissions for the benefit of human health. (Ex.
`
`1030, ¶¶28-29; Ex. 1004, ¶¶[0001], [0005]; Ex. 1005, 2:17-24; see also Petition, 30-
`
`31, 32-35; Ex. 1003, ¶¶62-63, 70-75; Decision, 26.)
`
`BNR’s assertion that Werling and Baiker have “significant” and “different
`
`strategies for the management of RF radiation” (Response, 45) is factually incorrect,
`
`and these differences are also irrelevant in the context of the claims at issue. Both
`
`Werling and Baiker provide teachings of radio telephones that adjust transmit power
`
`when proximate a human, so as to avoid unwanted health consequences, as discussed
`
`above. (Ex. 1004, ¶¶[0001], [0005]; Ex. 1005, 2:17-24; Ex. 1030, ¶¶30-31; see also
`
`Ex. 1003, ¶¶56-58.) Thus, BNR’s arguments for not combining Baiker and Werling
`
`have no merit.7
`
`BNR’s suggestion that a showing of “how Baiker’s technology . . . would be
`
`incorporated into Werling’s systems” is required (Response, 45-46 (emphasis in
`
`
`7 BNR’s generic arguments regarding the motivation to combine (Response, 40-41)
`
`ignore that Petitioner’s framework is consistent with obviousness case law. (See,
`
`e.g., Petition, 30-31, 33-35; Ex. 1003, ¶¶63, 70-74; see also Decision, 26-27
`
`(preliminary finding that the “combination is consistent with KSR[]”).)
`
`16
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`original)) has no legal basis. Indeed, a showing of obviousness does not require the
`
`details of an exact implementation. Facebook, Inc. v. Windy City Innovations, LLC,
`
`No. 2018-1400, 2020 WL 526797, 36 (Fed. Cir. Sept. 4, 2020) (affirming Board’s
`
`obviousness finding and noting it was unnecessary to show that the prior art
`
`references could be physically combined because a skilled artisan is also a person of
`
`ordinary creativity, “so the fact that it would take some creativity to carry out the
`
`combination does not defeat a finding of obviousness.”) (citing KSR Int'l Co. v.
`
`Teleflex Inc., 550 U.S. 398, 421 (2007)). Petitioner demonstrated why a POSITA
`
`would have been motivated to configure Baiker’s device to incorporate the teachings
`
`of Werling, and BNR failed to present evidence as to why a POSITA could not have
`
`applied such techniques. (See, e.g., Petition, 30-31, 32-35; Ex. 1003, ¶¶62-63, 70-
`
`75.)
`
`C. Ground 3: Irvin Anticipates Claims 1-3
`BNR’s issue with Irvin’s Mobile Attenuation Code (MAC) taught by Irvin
`
`(Response, 47-48) is misplaced. The MAC identifies one of eight power levels, and
`
`is transmitted by the base station to the mobile terminal. (Petition, 36-37, 40-41; Ex.
`
`1003, ¶¶79, 87-89; Ex. 1006, 1, 6-7.) The processor within the mobile station uses
`
`this MAC to control a power control loop so that the output power satisfies the power
`
`level indicated by the MAC. (Id.) BNR’s argument that the MAC is not the claimed
`
`network adjusted power level (Response, 47-48) is consistent with Petitioner’s
`
`17
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`analysis, since the MAC is sent to the mobile terminal, and the mobile terminal uses
`
`this to provide a network adjusted power level. (Petition, 40-41, Ex. 1003, ¶¶79, 84-
`
`89; Ex. 1030, ¶¶32-37 (reiterating Irvin’s operation and its application to the claim);
`
`see also Decision, 30-31.)
`
`BNR’s attempt to undermine Irvin’s “Background” section—i.e., something
`
`that was known in the art and is discussed to help frame Irvin’s disclosure—to
`
`understand the MAC’s characteristics (Response, 47-50) also misses the mark. The
`
`Background section
`
`in Irvin describes
`
`the “BACKGROUND TO THE
`
`INVENTION.” (Ex. 1006 at 1 (emphasis added).) Irvin explains here that “[i]n a
`
`cellular communication system” “the base station instructs the mobile terminal to
`
`use the least power” and the base station “does so by measuring the signal strength
`
`and returning instructions to the mobile terminal to modify transmitter power
`
`output.” (Id.; see also Ex. 1003, ¶87; Petition, 40.) Irvin then teaches that in the
`
`Advanced Mobile Phone System (AMPS) cellular system (a first generation phone
`
`system introduced in the 1980s, many years before the filing of Irvin), this was done
`
`by “the base station with which the mobile terminal 10 is communicating transmits
`
`a mobile attenuation code (MAC) identifying one of eight power levels.” (Ex. 1006,
`
`6; see also Ex. 1003, ¶¶79, 87; Petition, 37, 40.) There is a clear linkage between
`
`these two disclosures, and a POSITA would have readily understood that the MAC
`
`is based on a measurement of signal strength of a communications path between the
`
`18
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`base station and the mobile device. (Ex. 1030, ¶¶38-39.)
`
`Furthermore, contrary to BNR’s assertions (Response, 48-50), drawing from
`
`separate portions of a reference’s disclosure to provide a fulsome analysis of a claim
`
`limitation is permissible if it is “immediately apparent to one of ordinary skill in the
`
`art.” Unified Patents Inc. v. Intellectual Ventures I LLC, IPR2016-01643, Paper 51
`
`at 28-29 (PTAB March 26, 2018) (citing Kennametal, Inc. v. Ingersoll Cutting Tool
`
`Co., 780 F.3d 1376, 1382 (Fed. Cir. 2015).) Here, since both statements address the
`
`common feature discussed above, it would have been immediately apparent to a
`
`POSITA to understand the latter description in light of the earlier portion. (Ex. 1030,
`
`¶¶38-39; see also Decision at 31 (“even in an anticipation ground, Petitioner can rely
`
`on what Irvin reasonably discloses to [a POSITA].”).)
`
`BNR’s assertion that Irvin’s MAC does not take into account the proximity to
`
`the user (Response, 50-51) is based on a misunderstanding of Irvin’s operation.
`
`When Irvin’s proximity detector detects proximity to the user, a power cap of 100
`
`mW is set, equivalent to the MAC value of 100. (Ex. 1006, 6-7; Petition, 37, 45, Ex.
`
`1003, ¶¶79, 96; Ex. 1030, ¶¶40-42.) Thus, if during operation, MAC values of 000,
`
`001, 010 or 011 are received by the mobile device, indicating output powers of
`
`greater than the 100 mW power cap, the processor resets these to 100, to maintain
`
`the 100 mW power cap. (Ex. 1006, 6-7.) Other received MAC values (indicating
`
`output powers of 100 mW or less) “would be processed unaltered, regardless of
`
`19
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`proximity to the user, as the power out amounts generated from these codes are less
`
`than the cap.” (Id.; Petition, 37, 45; Ex. 1003, ¶¶79, 96.) Accordingly, Irvin teaches
`
`the claimed “transmit power level … based on said network adjusted transmit power
`
`level and said proximity transmit power level,” because Irvin’s processor provides a
`
`transmit power level based on both a network adjusted transmit power level
`
`determined from the MAC and measured proximity of the device to a user. (Ex.
`
`1003, ¶96; Petition, 45; Ex. 1030, ¶¶42-43.)8
`
`Given BNR makes no separate argument for claims 2-3 with respect to Irvin,
`
`claims 2-3 are anticipated by Irvin for the previously provided reasons. (Petition,
`
`45-47.)
`
`D. Ground 4: The Irvin-Myllymäki Combination Renders Obvious
`The Challenged Claims
`Contrary to BNR’s allegations concerning Myllymäki (Response, 51),
`
`Petitioner explained Myllymäki’s description of the base station controlling the
`
`
`8 BNR’s allegation that “Petitioner cannot use the same disclosure to satisfy [two]
`
`limitations” (Response, 50-51) is unsubstantiated. Aside from misunderstanding
`
`Petitioner’s application of Irvin, neither BNR nor its declarant demonstrate how the
`
`“network adjusted power level limitation as well as the ‘level’ part of the ultimate
`
`transmit power level” are distinct. (Id.; see also Decision, 33.)
`
`20
`
`PUBLIC VERSION
`
`

`

`Case IPR2019-01365
`
`mobile communication device’s transmitted power based on the received signal level
`
`discloses the “power circuit that provides a network adjusted transmit power level
`
`as a function of a position to a communications tower.” (Petition, 50-51 (citing Ex.
`
`1003, ¶¶107-108; Ex. 1007, 1:9-17; Ex. 1001, 3:31-34).)
`
`BNR’s argument that the “[received signal level] does not necessarily take
`
`into account position—or the communications path—of the device relative to the
`
`communications tower” ignores Myllymäki’s cited portion which explains the
`
`received signal level in the context of “place in which the device is used” and the
`
`distance between a mobile communication means and base station. (Ex. 1007, 1:9-
`
`17; Ex. 1003, ¶¶101, 107.) BNR’s attempt to distinguish “level” in “received signal
`
`level” with “strength” (Response, 51-52) should be rejected, as it overlooks the cl

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