`
`
`
`
`
`
`
`Trials@uspto.gov
`Tel: 571-272-7822
`
`Paper 48
`Entered: August 21, 2017
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`SAMSUNG ELECTRONICS CO. LTD.,
`SAMSUNG ELECTRONICS AMERICA, INC., and APPLE INC.,
`Petitioner,
`
`v.
`
`ROSETTA-WIRELESS CORPORATION,
`Patent Owner.
`
`Case IPR2016-006221
`Patent 7,149,511 B1
`
`Before JUSTIN T. ARBES, PATRICK R. SCANLON, and
`JOHN A. HUDALLA, Administrative Patent Judges.
`
`Opinion for the Board filed by Administrative Patent Judge HUDALLA.
`
`Opinion Dissenting filed by Administrative Patent Judge ARBES.
`
`HUDALLA, Administrative Patent Judge.
`
`
`
`FINAL WRITTEN DECISION
`Inter Partes Review
`35 U.S.C. § 318(a) and 37 C.F.R. § 42.73
`
`In Case IPR2016-00622 (“622 IPR”), Samsung Electronics Co., Ltd.,
`
`Samsung Electronics America, Inc., and Apple Inc. (collectively
`
`
`1 Case IPR2016-00616 has been consolidated with this proceeding.
`
`1
`
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`“Petitioner”), filed a Petition (Paper 42, “622 Petition” or “622 Pet.”)
`
`requesting an inter partes review of claims 1–10, 19–22, 58–65, and 68–71
`
`of U.S. Patent No. 7,149,511 B1 (Ex. 1001, “the ’511 patent”) pursuant to
`
`35 U.S.C. §§ 311–319. Patent Owner, Rosetta-Wireless Corporation
`
`(“Patent Owner”), filed a Preliminary Response to the 622 Petition. Paper 8
`
`(“622 Preliminary Response” or “622 Prelim. Resp.”). Taking into account
`
`the arguments presented in Patent Owner’s 622 Preliminary Response, we
`
`determined that the information presented in the 622 Petition established that
`
`there was a reasonable likelihood that Petitioner would prevail in
`
`challenging claims 1–10, 19–22, 58–65, and 68–71 of the ’511 patent under
`
`35 U.S.C. § 103(a). Pursuant to 35 U.S.C. § 314, we instituted this
`
`proceeding on August 22, 2016, as to these claims of the ’511 patent.
`
`Paper 12 (“622 Institution Decision” or “622 Dec. on Inst.”).
`
`In related Case IPR2016-00616 (“616 IPR”), Petitioner filed a second
`
`Petition (616 IPR, Paper 1, “616 Petition” or “616 Pet.”) requesting an inter
`
`partes review of claims 1–10 and 58–65 of the ’511 patent. Patent Owner
`
`filed a Preliminary Response to the 616 Petition. 616 IPR, Paper 7
`
`(“616 Preliminary Response” or “616 Prelim. Resp.”). Taking into account
`
`the arguments presented in Patent Owner’s 616 Preliminary Response, we
`
`also determined that the information presented in the 616 Petition
`
`established that there was a reasonable likelihood that Petitioner would
`
`prevail in challenging claims 1–10 and 58–65 of the ’511 patent under
`
`35 U.S.C. § 103(a). Pursuant to 35 U.S.C. § 314, we instituted an inter
`
`partes review proceeding on August 22, 2016, as to these claims of the
`
`
`2 Unless otherwise indicated, citations to papers and exhibits are made to
`Case IPR2016-00622.
`
`2
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`’511 patent. Paper 153 (“616 Institution Decision” or “616 Dec. on Inst.”).
`
`In the 616 Institution Decision, we ordered the consolidation of the 616 IPR
`
`with the 622 IPR for purposes of trial. Id. at 30–31.
`
`During the course of trial, Patent Owner filed a Patent Owner
`
`Response (Paper 28, “PO Resp.”), and Petitioner filed a Reply to the Patent
`
`Owner Response (Paper 37, “Pet. Reply”). An oral hearing was held on
`
`February 14, 2017, and a transcript of the hearing is included in the record.
`
`Paper 46 (“Tr.”).
`
`Petitioner proffered a Declaration of Erez Zadok, Ph.D. (Ex. 1004)
`
`with the 622 Petition and a Declaration of Nathaniel Polish, Ph.D.
`
`(Ex. 1058) with the 616 Petition. Petitioner also proffered a Declaration of
`
`Dr. Zadok (Ex. 1064) with its Reply. Patent Owner proffered Declarations
`
`of William H. Mangione-Smith, Ph.D. with its Preliminary Responses
`
`(Exs. 2001, 2016) and with its Response (Ex. 2022).
`
`We have jurisdiction under 35 U.S.C. § 6. This decision is a Final
`
`Written Decision under 35 U.S.C. § 318(a) as to the patentability of
`
`claims 1–10, 19–22, 58–65, and 68–71 of the ’511 patent. For the reasons
`
`discussed below, Petitioner has demonstrated by a preponderance of the
`
`evidence that these claims are unpatentable under 35 U.S.C. § 103(a).
`
`
`
`A.
`
`Related Proceedings
`
`I. BACKGROUND
`
`
`
`Both parties identify the following proceedings related to the
`
`’511 patent (616 Pet. 1–2; 622 Pet. 6–7; Paper 7, 2):
`
`
`3 The 616 Institution Decision is included in the 622 IPR as Paper 15
`because it includes a consolidation order.
`
`3
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`Rosetta-Wireless Corp. v. Apple Inc., No. 1:15-cv-00799 (N.D. Ill.,
`
`filed Jan. 27, 2015);
`
`Rosetta-Wireless Corp. v. High Tech Computer Corp., No. 1:15-cv-
`
`10603 (N.D. Ill., filed Nov. 24, 2015);
`
`Rosetta-Wireless Corp. v. Samsung Elecs. Co., Ltd., No. 1:15-cv-
`
`10605 (N.D. Ill., filed Nov. 24, 2015);
`
`Rosetta-Wireless Corp. v. LG Electronics Co., No. 1:15-cv-10608
`
`(N.D. Ill., filed Nov. 24, 2015); and
`
`Rosetta-Wireless Corp. v. Motorola Mobility LLC, No. 1:15-cv-10611
`
`(N.D. Ill., filed Nov. 24, 2015).
`
`
`
`B.
`
`The ’511 patent
`
`The ’511 patent is directed to “a wireless intelligent personal server
`
`that receives data transmitted over a wireless communications channel and
`
`automatically processes it so as to maintain a copy of at least one electronic
`
`file stored in a source computer.” Ex. 1001, 1:8–12. Figure 1 of the
`
`’511 patent is reproduced below.
`
`4
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`
`
`Figure 1 depicts wireless communication system 10 having enterprise
`
`information technology (IT) system 12 connected to one or more personal
`
`computers 14 and centralized enterprise database 16. Id. at 3:62–4:6.
`
`Enterprise IT system 12 uses wireless network management system 29 to
`
`communicate with first wireless network 20 and second wireless network 22
`
`via intermediate network 28, which may be a wide-area network (WAN) or a
`
`local-area network (LAN). Id. at 4:34–41.
`
`Wireless intelligent personal server (WIPS) 30 receives and stores
`
`data wirelessly transmitted over downstream channel 34 by first wireless
`
`network 20. Id. at 4:44–46, 5:35–36. WIPS 30 can use the received data to
`
`either update one or more of the files stored in its memory or to add a new
`
`5
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`file to its memory. Id. at 5:41–44. WIPS 30 also may transmit signals to
`
`second wireless network 22 over upstream channel 26. Id. at 6:16–21.
`
`Moreover, WIPS 30 is able to transfer data stored in its memory to and from
`
`different types of display devices 32 on an intermittent basis. Id. at 4:48–50.
`
`Display device 32, which may be a desktop PC or a personal digital
`
`assistant (PDA), interfaces with WIPS 30 to display data stored in WIPS 30.
`
`Id. at 4:55–67. This is accomplished by WIPS 30 copying requested data
`
`and transmitting it to display device 32. Id. at 9:64–10:8. Applications
`
`running on display device 32 also may allow a user to modify data stored in
`
`WIPS 30. Id. at 4:55–67; 8:39–41; 10:9–16.
`
`The patent application from which the ’511 patent issued was filed on
`
`August 31, 2000. Id. at [22].
`
`
`
`
`
`C.
`
`Illustrative Claim
`
`Claims 1 and 58 of the ’511 patent are independent and have been
`
`amended by Ex Parte Reexamination Certificate US 7,149,511 C1, dated
`
`Jan. 10, 2012. Ex. 1001, 16–17 (certificate issued from Reexamination
`
`Control No. 90/011,569).4 The remaining claims have not been amended.
`
`Claims 2–10 and 19–22 depend directly or indirectly from claim 1, and
`
`claims 59–65 and 68–71 depend directly or indirectly from claim 58.
`
`Claim 1 is illustrative of the challenged claims and recites:
`
`
`4 The ’511 patent also was the subject of a request for ex parte
`reexamination in Reexamination Control No. 90/011,418, which was
`terminated.
`
`6
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`A wireless
`1.
`comprising:
`
`intelligent personal network
`
`server,
`
`a radio frequency (RF) receiver for receiving downstream
`data transmitted over a first wireless communications channel;
`
`a memory;
`
`a central processing unit (CPU);
`
`a set of embedded machine language instructions within
`said personal network server, said set of embedded machine
`language instructions being executable by said CPU for
`processing said downstream data to provide at least one
`electronic file in said memory; and
`
`a first interface for allowing an application on an external
`display device to pick and open said at least one electronic file
`while said at least one electronic file remains resident on said
`personal network server, wherein said personal network server is
`hand-portable.
`
`Ex. 1001, 17 (1:21–2:8). Claim 58 differs from claim 1 only insofar as the
`
`word “receiver” in “radio frequency (RF) receiver” is replaced with
`
`“transceiver.” Id. at 17 (2:11).
`
`
`
`D.
`
`The Prior Art
`
`Petitioner relies on the following prior art:
`
`Kimura et al., U.S. Patent No. 5,864,853, filed Sept. 14,
`1995, issued Jan. 26, 1999 (Ex. 1035, “Kimura”);
`
`Terence A. Goggin, WINDOWS CE DEVELOPER’S
`HANDBOOK (1999) (Ex. 1030, “Goggin”);
`
`“Proxim Delivering Industry’s Lowest Priced Commercial
`Frequency Hopping Wireless LAN PC Card,” Business Wire
`(Mar. 29, 1999) (Ex. 1015, “Proxim”);
`
`Bodnar, U.S. Patent No. 6,012,063, filed Mar. 4, 1998,
`issued Jan. 4, 2000 (Ex. 1005, “Bodnar”);
`
`HEWLETT-PACKARD HP JORNADA 820/820E HANDHELD
`PC USER’S GUIDE (1998) (Ex. 1006, Ex. A, “Jornada”);
`
`7
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`to
`“Earthmate™ GPS Receiver: The Smart Way
`Navigate,” http://www.delorme.com/earthmate/ (as allegedly
`archived by the Internet Archive on Feb. 2, 1999) (Ex. 1012,
`“DeLorme Receiver”), and “Earthmate™ Accessories,”
`http://delorme.com/earthmate/accessories.htm
`(as
`allegedly
`archived by the Internet Archive on May 4, 1999) (Ex. 1039,
`“DeLorme Accessories”) (collectively, “DeLorme”);
`
`Todd Ogasawara, “HP Jornada External Keyboard (Part
`HP F1275A)
`Impressions,” http://to-tech.com/windowsce/
`jornada/keyboard/index.html (as allegedly archived by the
`Internet Archive on May 8, 1999) (Ex. 1013, “Ogasawara”); and
`
`HEWLETT-PACKARD HP CAPSHARE 920 PORTABLE E-
`COPIER (1999) (Ex. 1007, “CapShare”).
`
`
`
`E.
`
`Instituted Grounds
`
`We instituted trial based on the following grounds (616 Dec. on
`
`Inst. 30; 622 Dec. on Inst. 41–42):
`
`Reference(s) Basis
`
`Claims
`Challenged
`
`Citation
`
`Kimura
`
`Goggin
`
`Goggin,
`Proxim
`
`Goggin,
`Bodnar
`
`Goggin,
`Proxim,
`Bodnar
`
`Goggin,
`Jornada
`
`35 U.S.C. § 103(a) 1–6, 8–10, 58–63,
`and 65
`
`616 Pet. 13–59
`
`35 U.S.C. § 103(a) 1–10, 19, 58–65,
`and 68
`
`622 Pet. 17–39
`
`35 U.S.C. § 103(a) 1–10, 19, 58–65,
`and 68
`
`622 Pet. 17–39
`
`35 U.S.C. § 103(a) 2 and 59
`
`622 Pet. 39–44
`
`35 U.S.C. § 103(a) 2 and 59
`
`622 Pet. 39–44
`
`35 U.S.C. § 103(a) 8 and 9
`
`622 Pet. 44–50
`
`8
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`Reference(s) Basis
`
`Claims
`Challenged
`
`Citation
`
`35 U.S.C. § 103(a) 8 and 9
`
`622 Pet. 44–50
`
`35 U.S.C. § 103(a) 20 and 69
`
`622 Pet. 50–53
`
`35 U.S.C. § 103(a) 20 and 69
`
`622 Pet. 50–53
`
`35 U.S.C. § 103(a) 21 and 70
`
`622 Pet. 53–55
`
`35 U.S.C. § 103(a) 21 and 70
`
`622 Pet. 53–55
`
`35 U.S.C. § 103(a) 22 and 71
`
`622 Pet. 55–57
`
`35 U.S.C. § 103(a) 22 and 71
`
`622 Pet. 55–57
`
`Goggin,
`Proxim,
`Jornada
`
`Goggin,
`DeLorme
`
`Goggin,
`Proxim,
`DeLorme
`
`Goggin,
`Ogasawara
`
`Goggin,
`Proxim,
`Ogasawara
`
`Goggin,
`CapShare
`
`Goggin,
`Proxim,
`CapShare
`
`
`
`F.
`
`Claim Interpretation
`
`In an inter partes review, we construe claims by applying the broadest
`
`reasonable interpretation in light of the specification. 37 C.F.R. § 42.100(b);
`
`see Cuozzo Speed Techs., LLC v. Lee, 136 S. Ct. 2131, 2144–46 (2016).
`
`Under the broadest reasonable interpretation standard, and absent any
`
`special definitions, claim terms are given their ordinary and customary
`
`meaning, as would be understood by one of ordinary skill in the art in the
`
`context of the entire disclosure. See In re Translogic Tech. Inc., 504 F.3d
`
`1249, 1257 (Fed. Cir. 2007). Any special definitions for claim terms or
`
`9
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`phrases must be set forth “with reasonable clarity, deliberateness, and
`
`precision.” In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994).
`
`For purposes of this Decision, and based on the entire trial record, we
`
`construe the challenged claims as follows.
`
`
`
`1. Whether the Preambles of Independent Claims 1 and 58 are
`Limiting
`
`In our Decisions on Institution, we determined that the preambles of
`
`independent claims 1 and 58 are limiting based on the use of “personal
`
`network server” in the bodies of claims 1 and 58. 616 Dec. on Inst. 6–7;
`
`622 Dec. on Inst. 8–9. The parties do not dispute this determination. See
`
`PO Resp. 24–25; Pet. Reply 6 n.7. We do not perceive any reason or
`
`evidence that compels any deviation from this determination. Accordingly,
`
`we adopt our previous analysis for purposes of this Final Written Decision
`
`and maintain our determination that the preambles of these independent
`
`claims are limiting.
`
`
`
`2.
`
`“Personal Network Server”
`
`In our Decisions on Institution, we determined that the term “personal
`
`network server” did not require explicit construction. 616 Dec. on Inst. 7–9;
`
`622 Dec. on Inst. 9–10. In its Response, Patent Owner proffers a
`
`construction of “network server” that is slightly different than the one from
`
`its Preliminary Response: “a computer in a network configured to receive
`
`and share data resources with other devices in that network.” PO Resp. 24
`
`(citing Ex. 2022 ¶ 57), 26; 616 Prelim. Resp. 23 (proposing construction of
`
`“personal network server” as “a device configured to be interposed between
`
`a source server and an external display device that provides source server
`
`10
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`data locally to a user.”); 622 Prelim. Resp. 20 (same). Patent Owner
`
`additionally contends an ordinarily skilled artisan “would have understood
`
`that a ‘network server’ did not include two computers connected in a direct
`
`point-to-point communications link.” Id. (citing Ex. 2022 ¶ 58). According
`
`to Patent Owner, the Specification of the ’511 patent never uses “network”
`
`to refer to a direct point-to-point communications link; instead, Patent
`
`Owner contends “network” is used in the Specification with reference to
`
`“one of the upstream networks.” Id. at 29–31 (citing Ex. 1001, 6:51–53,
`
`6:55–64, 7:8–13, 8:43–51, Ex. 2022 ¶¶ 68, 80–81). Patent Owner also
`
`highlights certain arguments made during prosecution of the ’511 patent in
`
`which the inventors purportedly distinguished a prior art reference
`
`(Ex. 1038, “Boals”) on the basis that “Boals was not a ‘network server’
`
`because it merely received video display data over a direct point-to-point
`
`communications link.” PO Resp. 33 (citing Ex. 1002, 355–56; Ex. 2017
`
`¶ 50).
`
`In reply, Petitioner argues that the Specification “actually describe[s]
`
`accessing files on WIPS the same way as accessing files on external devices,
`
`such as hard drives (i.e., via direct point-to-point communications links).”
`
`Pet. Reply 9 (citing Ex. 1064 ¶¶ 12–14). Dr. Zadok testifies that
`
`“Applicant[s] cited to the specification and argued that this portion of the
`
`specification described how a ‘display device 32 accesses the memory in
`
`WIPS 30 as it would an external device, such as an external hard drive or
`
`a server on a local area network (LAN).’” Ex. 1064 ¶ 13 (quoting Ex. 1001,
`
`6:25–28 and citing Ex. 1002, 206) (emphasis added by Dr. Zadok).
`
`Petitioner also argues that none of the dictionaries cited by the parties
`
`precludes a network server from merely having a point-to-point
`
`11
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`communications link. Pet. Reply 9–10 (citing Ex. 1026, 5; Ex. 2024, 4;
`
`Ex. 2025, 4). Petitioner likewise cites its dictionary evidence that “a
`
`‘computer network’ can consist of only two computers.” Id. at 10 (citing
`
`Ex. 1008, 4). Petitioner additionally argues that the Applicants of the
`
`’511 patent distinguished Boals based on arguments other than the point-to-
`
`point communications link. Id. at 9–10 (citing Ex. 1002, 353, 355–56).
`
`We disagree with Patent Owner’s contention that the recited “network
`
`server” cannot have a point-to-point connection. The Specification of the
`
`’511 patent states that display device 32 can access WIPS 30 just as it would
`
`with an external device, such as an external hard drive. See Ex. 1001, 6:25–
`
`28. Such access is characteristic of a point-to-point connection. We also
`
`agree with Petitioner that the Applicants of the ’511 patent distinguished
`
`Boals during prosecution “from the WIPS because Boals’ host 101 ‘act[ed]
`
`as a video display driver’ for the display device, rather than as, e.g., an
`
`external hard drive.” Pet. Reply 8–9 (citing Ex. 1002, 353, 355–56). This
`
`does not support Patent Owner’s proposed exclusion of point-to-point
`
`connections. Finally, we agree with Petitioner that the extrinsic evidence
`
`from dictionaries does not preclude a server from having a point-to-point
`
`connection; in fact, a contemporaneous dictionary definition in the record
`
`expressly supports the notion of a “network server” having a point-to-point
`
`connection with its client. See Ex. 1008, 4 (defining “computer network” as
`
`“a complex consisting of two or more interconnected computers”). Based
`
`on this evidence, we do not agree that the term “network server” precludes a
`
`point-to-point connection.
`
`Regarding the “personal” nature of the network server, Patent Owner
`
`contends we should construe “personal” to mean “configured to provide
`
`12
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`access to a user’s individual data.” PO Resp. 35 (citing Ex. 2022 ¶¶ 82–84).
`
`Petitioner argues that construction of “personal” is unnecessary because it
`
`does not factor into our unpatentability determination. Pet. Reply 10. We
`
`agree with Petitioner.
`
`For these reasons, we determine that no explicit construction of
`
`“personal network server” is required beyond our determination that the
`
`term does not exclude a point-to-point connection. See Vivid Techs., Inc. v.
`
`Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those
`
`terms need be construed that are in controversy, and only to the extent
`
`necessary to resolve the controversy.”).
`
`
`
`3.
`
`“Downstream Data”
`
`In our Decisions on Institution, we determined that the term
`
`“‘downstream data’ simply reflects data moving downstream from one place
`
`to another, so the term needs no further elucidation.” 616 Dec. on Inst. 11;
`
`622 Dec. on Inst. 12. We also determined that the source of “downstream
`
`data” and the “external display device” need not be different entities.
`
`616 Dec. on Inst. 12; 622 Dec. on Inst. 13.
`
`Consistent with its Preliminary Response, Patent Owner contends
`
`“downstream data” should be construed to mean “data transmitted from a
`
`source server to the personal network server.” PO Resp. 15 (citing Ex. 2022
`
`¶ 32). Patent Owner argues that the Specification of the ’511 patent “clearly
`
`and consistently uses ‘downstream data’ to refer to data received from the
`
`source server and flowing in one direction within the network: toward the
`
`display device.” Id. at 16. Patent Owner contends that each instance of the
`
`term “‘downstream’ is used to specify the direction of the data flow as being
`
`13
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`from the source server.” Id. (citing Ex. 2022 ¶ 33). Patent Owner also
`
`highlights the distinction between the use of “downstream” and “upstream”
`
`in the Specification and claims as further supporting its proposed
`
`construction of “downstream data.” Id. at 17–18, 21–22. Patent Owner’s
`
`arguments regarding the application of the words “downstream” and
`
`“upstream” are illustrated in its annotated version of Figure 1, which is
`
`reproduced below.
`
`
`
`Id. at 16–17 (citing Ex. 2022 ¶ 34). In this annotated figure, Patent Owner
`
`has added arrows tying the words “downstream” and “upstream” to
`
`enterprise IT system 12, which Patent Owner calls a “source server,” and
`
`display device 32. Id. at 17 (citing Ex. 2022 ¶ 35).
`
`Patent Owner further references the word “receiving” that precedes
`
`“downstream data” in claims 1 and 58 as indicating that “downstream” must
`
`mean something other than simply “received.” Id. at 21. Patent Owner
`
`14
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`additionally cites testimony from Dr. Mangione-Smith and certain dictionary
`
`definitions as supporting a construction of “downstream” that reflects a flow
`
`of data from a server to an end user. Id. at 23 (citing Ex. 2007, 3; Ex. 2022
`
`¶¶ 45–52; Ex. 2023, 3).
`
`In reply, Petitioner argues that we should not adopt a construction that
`
`reads in an upstream source server. Pet. Reply 2. Petitioner contends a
`
`statement made by the Applicants of the ’511 patent during prosecution
`
`amounts to an express definition of “downstream data” as “data that is
`
`transmitted over a wireless communications channel.” Id. at 2–3 (quoting
`
`Ex. 1002, 356–57). Petitioner also notes that the Applicants distinguished
`
`certain prior art during prosecution because it “failed to teach WIPS files
`
`‘originat[ing]’ from the ‘external display device.’” Id. at 5–6 (quoting
`
`Ex. 1002, 356–57). According to Petitioner, this confirms that
`
`“‘downstream data’ may originate from the display device and not from a
`
`separate ‘source server.’” Id.
`
`“A claim construction that gives meaning to all the terms of the claim
`
`is preferred over one that does not do so.” Merck & Co., Inc. v. Teva
`
`Pharm. USA, Inc., 395 F.3d 1364, 1372 (Fed. Cir. 2005). “The preference
`
`for giving meaning to all terms, however, is not an inflexible rule that
`
`supersedes all other principles of claim construction.” SimpleAir, Inc. v.
`
`Sony Ericsson Mobile Commc’ns AB, 820 F.3d 419, 429 (Fed. Cir. 2016).
`
`We are mindful that “it is the claims, not the written description, which
`
`define the scope of the patent right.” Laitram Corp. v. NEC Corp., 163 F.3d
`
`1342, 1347 (Fed. Cir. 1998). In addition, our reviewing court “has
`
`repeatedly cautioned against limiting the claimed invention to preferred
`
`embodiments or specific examples in the specification.” Williamson v.
`
`15
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`Citrix Online, LLC, 792 F.3d 1339, 1346–47 (Fed. Cir. 2015) (internal
`
`quotation omitted).
`
`We are reticent to read in a limitation—that “downstream data” must
`
`be transmitted from a “source server”—when claims 1 and 58 do not recite a
`
`source server. Thus, our inclination is not to read a “source server” into the
`
`construction of “downstream data” unless the Specification expressly
`
`requires the same.
`
`Having reviewed the Specification of the ’511 patent in detail, we
`
`agree with Petitioner (see Pet. Reply 4–5) that the embodiment described
`
`with reference to Figure 1 is an “exemplary embodiment.” See Ex. 1001,
`
`3:46–48, 3:62–64. As such, we do not discern that the Applicants intended
`
`the claims to be limited such that “downstream data” must come from a
`
`“source server.” Moreover, the Specification never describes
`
`communications coming from (or going to) enterprise IT system 12 as
`
`occurring via a downstream (or upstream) channel. Rather, the Specification
`
`uses broad language—and not the terms “downstream” or “upstream”—to
`
`describe communications involving enterprise IT system 12:
`
`An intermediate network 28 is connected to first wireless
`network 20 and to second wireless network 22, and enterprise
`IT system 12 uses a wireless network management system 29 to
`communicate with wireless networks 20 and 22, via
`intermediate network 28. Intermediate network 28 may[ ]be
`any wide-area network (WAN) or local-area network (LAN)
`capable of transmitting digital data between enterprise IT
`system 12 and wireless networks 20 and 22. Preferably,
`intermediate network 28 is either the Internet or a private
`corporate network.
`
`Id. at 4:34–43.
`
`16
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`Furthermore, the Specification ties the term “downstream data” to the
`
`channel from which it is received. For example, several passages in the
`
`Specification state that the WIPS (or its associated receiver) receives
`
`downstream data over a wireless communications channel. See Ex. 1001,
`
`Abstract, 2:53–55, 2:66–3:2, 3:13–15, 3:24–26, 3:36–38, 9:3–6; see also id.
`
`at 1:7–12 (“[T]his invention relates to a wireless intelligent personal server
`
`that receives data transmitted over a wireless communications channel.”).
`
`This channel, which corresponds to the “first wireless communications
`
`channel” in claims 1 and 58, is illustrated as downstream channel 34 in
`
`Figure 1, and it is associated with first wireless network 20. See id. at 5:35–
`
`36, 6:60–62, Fig. 1. Correspondingly, the WIPS causes a wireless telephone
`
`to transmit upstream data over an upstream channel. See id. at 7:23–28. In
`
`Figure 1, upstream channel 26 is associated with second wireless
`
`network 22. See id. at 4:30–33, 5:51–53, Fig. 1. Thus, the Specification
`
`associates the words “downstream” and “upstream” with a particular channel
`
`and/or network, rather than the ultimate source or destination of any data.
`
`As such, data moving from the downstream channel to the WIPS can
`
`encompass data arising from a source server without necessarily being
`
`limited to it. We defer to the Specification in this regard because claims
`
`must be given their broadest reasonable interpretation consistent with the
`
`Specification. See 37 C.F.R. § 42.100(b).
`
`We also have reviewed the record evidence regarding the prosecution
`
`history. We do not agree with Petitioner’s contention (Pet. Reply 2–3 (citing
`
`Ex. 1002, 356–57)) that the Applicants expressly defined “downstream data”
`
`during prosecution as “data that is transmitted over a wireless
`
`communications channel.” Such a construction of “downstream data” would
`
`17
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`be entirely redundant of other words in the claim limitation “receiving
`
`downstream data transmitted over a first wireless communications channel.”
`
`Nonetheless, this part of the prosecution history is further evidence that
`
`“downstream data” is not necessarily tied to a source server. It also
`
`evidences the tie between “downstream data” and an associated
`
`communication channel.
`
`Although Patent Owner and Dr. Mangione-Smith put forth certain
`
`extrinsic evidence purportedly showing that “downstream” must be tied to a
`
`source server (see PO Resp. 22–24; Ex. 2022 ¶¶ 45–52), this evidence does
`
`not override the tie in the Specification of the ’511 patent between
`
`“downstream data” and the downstream channel. Indeed, certain of the
`
`extrinsic evidence supports the notion of directionality, such as data coming
`
`from the downstream channel toward the WIPS. See, e.g., Ex. 2007, 3
`
`(“[T]he direction of transmission flow from the source toward the sink
`
`(destination/user).”).
`
`Finally, we consider whether we can give proper meaning to the term
`
`“downstream” without referring to a source server. In light of the
`
`embodiments in the Specification, data can reflect “downstream”
`
`directionality with reference to both the downstream channel from which it
`
`flows and the WIPS to which it flows. Thus, we do not agree with Patent
`
`Owner (PO Resp. 20–21) that our construction must refer to a source server
`
`to give meaning to the word “downstream.” And, contrary to Patent
`
`Owner’s argument (id.), a construction referring to the downstream channel
`
`18
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`from which downstream data flows would not be merely redundant of the
`
`“receiving” aspect of claims 1 and 58.5
`
`Accordingly, we decline to adopt Patent Owner’s proposed
`
`construction, because we determine that the patentees of ’511 patent did not
`
`“demonstrate[] a clear intention to limit the claim scope using words or
`
`expressions of manifest exclusion or restriction” regarding a “source server.”
`
`See Innova/Pure Water, Inc., v. Safari Water Filtration Sys., Inc., 381 F.3d
`
`1111, 1117 (Fed. Cir. 2004) (internal quotations omitted). The Specification
`
`ties “downstream data” to the downstream channel from which it flows, so
`
`we construe “downstream data” in claims 1 and 58 with reference to the
`
`downstream channel from which it is received, which is the “first wireless
`
`communications channel” in the parlance of claims 1 and 58. “Downstream
`
`data” also is tied to place where it flows, which is the wireless intelligent
`
`personal network server. Accordingly, under our broadest reasonable
`
`interpretation standard, we interpret “downstream data” to mean “data
`
`moving from a downstream channel to the wireless intelligent personal
`
`network server.”
`
`As a point of further clarification, we address Patent Owner’s
`
`contention that “downstream data” must flow toward the display device. See
`
`
`5 To the extent Patent Owner might argue that construing “downstream data”
`with reference to the downstream channel conflicts with the claim
`interpretation preference for giving meaning to all terms, SimpleAir counsels
`that this is not an inflexible rule. See SimpleAir, 820 F.3d at 429. In this
`case, we judge fidelity to the broad disclosure in the Specification to be a
`more important consideration. Specifically, in contrast to its description of
`“downstream data” flowing from the downstream channel, the Specification
`does not expressly tie “downstream data” to a source server.
`
`
`
`19
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`PO Resp. 16–17. We determine that the Specification does not support such
`
`an interpretation. Importantly, communications between the WIPS and the
`
`display device are not necessarily made via the upstream or downstream
`
`wireless channels. Instead, such communications are described as follows:
`
`Data transfer between WIPS 30 and wireless telephone 24 and
`display device 32 may occur in various ways. For example,
`WIPS 30 may be electrically connected to wireless telephone
`24 and/or display device 32. Such electrical connection may be
`direct, i.e., so that electrical contacts on WIPS 30 directly
`contact electrical contacts on wireless telephone 24 and/or
`display device 32. Alternatively, the electrical connection may
`be through electrical cables, which may be provided with
`standard connectors, such as USB connectors. Data transfer
`between WIPS 30 and wireless telephone 24 and display device
`32 may also be wireless. For example, WIPS 30 and either
`wireless telephone 24 or display device 32 may be provided
`with infrared ports, such as IrDA ports. Alternatively, WIPS 30
`and either wireless telephone 24 or display device 32 may use
`short-range RF communication, such as the Bluetooth protocol,
`to transfer data. Other methods for data transfer may also be
`used. For example, WIPS 30 may be provided with a flash
`memory card, in which case data transfer to display device 32
`may be effected by removing the flash memory card from
`WIPS 30 and connecting it to display device 32.
`
`Ex. 1001, 5:8–28. Therefore, even where there is a wireless connection
`
`between the WIPS and the display device, the wireless connection is not
`
`associated expressly with the downstream and upstream channels that are
`
`described elsewhere in the Specification. Thus, our interpretation of
`
`“downstream data” neither requires the display device to be in a downstream
`
`relationship with the WIPS, nor requires the display device and the WIPS to
`
`communicate over the downstream channel (also known as the “first
`
`wireless communications channel”).
`
`
`
`20
`
`
`
`IPR2016-00622
`Patent 7,149,511 B1
`
`4.
`
`Remaining Terms
`
`Although the parties proffer other terms for construction (see 616 Pet.
`
`9–10, 12; 622 Pet. 13–15; PO Resp. 35–36; Pet. Reply 11–12), none of these
`
`terms requires explicit construction to resolve issues in this case. See Vivid
`
`Techs., 200 F.3d at 803.
`
`
`
`II. ANALYSIS
`
`A.
`
`Obviousness Ground Based on Kimura (616 IPR)
`
`Petitioner contends claims 1–10 and 58–65 would have been obvious
`
`over Kimura. 616 Pet. 13–59; Pet. Reply 22–33. Patent Owner disputes
`
`Petitioner’s contention. PO Resp. 51–68.
`
`
`
`1.
`
`Principles of Law
`
`A claim is unpatentable under 35 U.S.C. § 103(a)6 if the differences
`
`between the claimed subject matter and the prior