`EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`
`
`PARTHENON UNIFIED MEMORY
`ARCHITECTURE LLC,
`
`
`MEMORANDUM OPINION AND ORDER
`
` On October 26, 2015, the Court held a hearing to determine the proper construction of
`
`the disputed terms in nine Asserted Patents. The Court, having considered the parties’ claim
`
`construction briefing (Dkt. Nos. 56, 60, and 64) and their arguments at the hearing, issues this
`
`Memorandum Opinion and Order construing the disputed terms.
`
`BACKGROUND AND THE ASSERTED PATENTS
`
`Parthenon Unified Memory Architecture LLC (“PUMA”) brought this action against
`
`ZTE Corp., ZTE USA, Inc., and ZTE (TX), Inc. (collectively, “Defendants”) alleging that
`
`Defendants infringe U.S. Patent Nos. 5,812,789 (“the ’789 Patent”), 6,058,459 (“the ’459
`
`Patent”), 6,427,194 (“the ’194 Patent”), 7,321,368 (“the ’368 Patent”), 7,542,045 (“the ’045
`
`Patent”), 7,777,753 (“the ’753 Patent”), 8,054,315 (“the ’315 Patent”), 8,681,164 (“the ’164
`
`Patent”) and 5,960,464 (“the ’464 Patent”) (collectively, “the Asserted Patents”). The ’789
`
`Patent and the ’459 Patent were filed on the same day, have similar specifications, and
`
`incorporate each other by reference. Six patents are based on continuation applications of the
`
`’459 Patent: the ’194 Patent, the ’368 Patent, the ’045 Patent, the ’753 Patent, the ’315 Patent,
`
`
`
`1
`
`Plaintiff,
`
`
`v.
`
`ZTE CORP., ZTE USA, INC. AND
`ZTE (TX), INC.,
`
`
`Defendants.
`
`
`
`
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`§
`
`Case No. 2:15-cv-00225-JRG-RSP
`(Lead)
`
`
`
`Apple Inc. v. Parthenon
`Ex. 1013 / Page 1 of 43
`
`
`
`and the ’164 Patent.1 All nine Asserted Patents were subject to claim construction orders issued
`
`by this Court in Parthenon Unified Memory Architecture, LLC v. HTC Corp. et al., 2:14-cv-
`
`0690-JRG-RSP, Dkt. No. 155 (E.D. Tex. July 30, 2015) (“the Parthenon I Order”) and
`
`Parthenon Unified Memory Architecture, LLC v. Samsung Elecs. Co., Ltd. et al., 2:14-cv-902-
`
`JRG-RSP, Dkt. No. 155 (E.D. Tex. Jan. 24, 2016) (“the Parthenon II Order”). Furthermore, one
`
`additional Eastern District of Texas claim construction order involved the ’789 Patent.
`
`STMicroelectronics, Inc. v. Motorola, Inc., 327 F. Supp. 2d 687 (E.D. Tex. 2004).
`
`In general, the ’789 Patent, the ’459 Patent, the ’194 Patent, the ’368 Patent, the ’045
`
`Patent, the ’753 Patent, the ’315 Patent, and the ’164 Patent relate to systems in which a first
`
`device (for example a processor) and a decoder/encoder share a common memory. The ’459
`
`Patent abstract recites:
`
`An electronic system provides direct access between a first device and a
`decoder/encoder and a memory. The electronic system can be included in a
`computer in which case the memory is a main memory. Direct access is
`accomplished through one or more memory interfaces. Direct access is also
`accomplished in some embodiments by direct coupling of the memory to a bus,
`and in other embodiments, by direct coupling of the first device and
`decoder/encoder to a bus. The electronic system includes an arbiter for
`determining access for the first device and/or the decoder/encoder to the memory
`for each access request. The arbiter may be monolithically integrated into a
`memory interface of the decoder/encoder or the first device. The decoder may be
`a video decoder configured to decode a bit stream formatted to comply with the
`MPEG-2 standard. The memory may store predicted images which are obtained
`from a single preceding image and may also store intra images. Bidirectional
`images which are directly supplied to a display adapter may be obtained from two
`preceding intra or predicted images.
`
`’459 Patent Abstract.
`
`
`1 The specification of the ’464 Patent is not shared by the other Asserted Patents.
`2
`
`
`
`Ex. 1013 / Page 2 of 43
`
`
`
`
`
`The ’464 Patent relates, generally, to a system whereby a decoder, which requires
`
`contiguous blocks of memory, can utilize noncontiguous blocks of the system’s memory. The
`
`’464 patent abstract recites:
`
`A method and apparatus employing a memory management system that can be
`used with applications requiring a large contiguous block of memory, such as
`video decompression techniques (e.g., MPEG 2 decoding). The system operates
`with a computer and the computer's operating system to request and employ
`approximately 500 4-kilobyte pages in two or more noncontiguous blocks of the
`main memory to construct a contiguous 2-megabyte block of memory. The
`system can employ, on a single chip, a direct memory access engine, a
`microcontroller, a small block of optional memory, and a video decoder circuit.
`The microcontroller retains the blocks of multiple pages of the main memory, and
`the page descriptors of these blocks, so as to lock down these blocks of memory
`and prohibit the operating system or other applications from using them. The
`microcontroller requests the page descriptors for each of the blocks, and programs
`a lookup table or memory mapping system in the on-chip memory to form a
`contiguous block of memory. As a result, the video decoder circuit can perform
`operations on a 2-megabyte contiguous block of memory, where
`the
`microcontroller employs the lookup table to translate each 2-megabyte contiguous
`address requested by the video decoder circuit to its appropriate page in the main
`memory. As soon as the video decoding operations are complete, the
`microcontroller releases the blocks of multiple pages of memory back for use by
`the computer.
`
`’464 Patent Abstract.
`
`APPLICABLE LAW
`
`1. Claim Construction
`
`“It is a ‘bedrock principle’ of patent law that ‘the claims of a patent define the invention
`
`to which the patentee is entitled the right to exclude.’” Phillips v. AWH Corp., 415 F.3d 1303,
`
`1312 (Fed. Cir. 2005) (en banc) (quoting Innova/Pure Water Inc. v. Safari Water Filtration Sys.,
`
`Inc., 381 F.3d 1111, 1115 (Fed. Cir. 2004)). To determine the meaning of the claims, courts start
`
`by considering the intrinsic evidence. Id. at 1313; C.R. Bard, Inc. v. U.S. Surgical Corp., 388
`
`F.3d 858, 861 (Fed. Cir. 2004); Bell Atl. Network Servs., Inc. v. Covad Commc’ns Grp., Inc., 262
`
`F.3d 1258, 1267 (Fed. Cir. 2001). The intrinsic evidence includes the claims themselves, the
`
`
`
`3
`
`Ex. 1013 / Page 3 of 43
`
`
`
`specification, and the prosecution history. Phillips, 415 F.3d at 1314; C.R. Bard, Inc., 388 F.3d at
`
`861. Courts give claim terms their ordinary and accustomed meanings as understood by one of
`
`ordinary skill in the art at the time of the invention in the context of the entire patent. Phillips,
`
`415 F.3d at 1312–13; Alloc, Inc. v. International Trade Comm’n, 342 F.3d 1361, 1368 (Fed. Cir.
`
`2003).
`
`The claims themselves provide substantial guidance in determining the meaning of
`
`particular claim terms. Phillips, 415 F.3d at 1314. First, a term’s context in the asserted claim
`
`can be very instructive. Id. Other asserted or unasserted claims can also aid in determining the
`
`claim’s meaning, because claim terms are typically used consistently throughout the patent. Id.
`
`Differences among the claim terms can also assist in understanding a term’s meaning. Id. For
`
`example, when a dependent claim adds a limitation to an independent claim, it is presumed that
`
`the independent claim does not include the limitation. Id. at 1314–15.
`
`“[C]laims ‘must be read in view of the specification, of which they are a part.’” Id.
`
`(quoting Markman v. Westview Instruments, Inc., 52 F.3d 967, 979 (Fed. Cir. 1995) (en banc)).
`
`“[T]he specification ‘is always highly relevant to the claim construction analysis. Usually, it is
`
`dispositive; it is the single best guide to the meaning of a disputed term.’” Id. (quoting Vitronics
`
`Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1582 (Fed. Cir. 1996)); Teleflex, Inc. v. Ficosa N. Am.
`
`Corp., 299 F.3d 1313, 1325 (Fed. Cir. 2002). This is true because a patentee may define his own
`
`terms, give a claim term a different meaning than the term would otherwise possess, or disclaim
`
`or disavow the claim scope. Phillips, 415 F.3d at 1316. In these situations, the inventor’s
`
`lexicography governs. Id. The specification may also resolve ambiguous claim terms “where the
`
`ordinary and accustomed meaning of the words used in the claims lack sufficient clarity to
`
`permit the scope of the claim to be ascertained from the words alone.” Teleflex, Inc., 299 F.3d at
`
`
`
`4
`
`Ex. 1013 / Page 4 of 43
`
`
`
`1325. But, “‘[a]lthough the specification may aid the court in interpreting the meaning of
`
`disputed claim language, particular embodiments and examples appearing in the specification
`
`will not generally be read into the claims.’” Comark Commc’ns, Inc. v. Harris Corp., 156 F.3d
`
`1182, 1187 (Fed. Cir. 1998) (quoting Constant v. Advanced Micro-Devices, Inc., 848 F.2d 1560,
`
`1571 (Fed. Cir. 1988)); see also Phillips, 415 F.3d at 1323. The prosecution history is another
`
`tool to supply the proper context for claim construction because a patent applicant may also
`
`define a term in prosecuting the patent. Home Diagnostics, Inc., v. Lifescan, Inc., 381 F.3d 1352,
`
`1356 (Fed. Cir. 2004) (“As in the case of the specification, a patent applicant may define a term
`
`in prosecuting a patent.”).
`
`Although extrinsic evidence can be useful, it is “‘less significant than the intrinsic record
`
`in determining the legally operative meaning of claim language.’” Phillips, 415 F.3d at 1317
`
`(quoting C.R. Bard, Inc., 388 F.3d at 862). Technical dictionaries and treatises may help a court
`
`understand the underlying technology and the manner in which one skilled in the art might use
`
`claim terms, but technical dictionaries and treatises may provide definitions that are too broad or
`
`may not be indicative of how the term is used in the patent. Id. at 1318. Similarly, expert
`
`testimony may aid a court in understanding the underlying technology and determining the
`
`particular meaning of a term in the pertinent field, but an expert’s conclusory, unsupported
`
`assertions as to a term’s definition are entirely unhelpful to a court. Id. Generally, extrinsic
`
`evidence is “less reliable than the patent and its prosecution history in determining how to read
`
`claim terms.” Id.
`
`2. Claim Indefiniteness
`
`
`
`Patent claims must particularly point out and distinctly claim the subject matter regarded
`
`as the invention. 35 U.S.C. § 112, ¶ 2. “[I]ndefiniteness is a question of law and in effect part of
`
`
`
`5
`
`Ex. 1013 / Page 5 of 43
`
`
`
`claim construction.” ePlus, Inc. v. Lawson Software, Inc., 700 F.3d 509, 517 (Fed. Cir. 2012). A
`
`party challenging the definiteness of a claim must show it is invalid by clear and convincing
`
`evidence. Young v. Lumenis, Inc., 492 F.3d 1336, 1345 (Fed. Cir. 2007).
`
`
`
`The definiteness standard of 35 U.S.C. § 112, ¶ 2 requires that:
`
`[A] patent’s claims, viewed in light of the specification and prosecution history,
`inform those skilled in the art about the scope of the invention with reasonable
`certainty. The definiteness requirement, so understood, mandates clarity, while
`recognizing that absolute precision is unattainable. The standard we adopt
`accords with opinions of this Court stating that “the certainty which the law
`requires in patents is not greater than is reasonable, having regard to their subject-
`matter.”
`
`Nautilus, Inc. v. Biosig Instruments, Inc., 134 S. Ct. 2120, 2129–30 (2014) (internal citations
`
`omitted).
`
`3. Construing Claim Terms that Have Previously Been Construed by This Court or
`Other Courts
`
`This is not the first time a Court in this District has construed some of the disputed terms.
`
`The Parthenon I Order and Parthenon II Order construed a number of the presently disputed
`
`terms, and in STMicroelectronics, Inc. v. Motorola, Inc., 327 F. Supp. 2d 687 (E.D. Tex. 2004)
`
`the Court construed the ’789 Patent. These previous constructions are not controlling here but
`
`can be instructive and will, at times, provide part of the basis for the Court’s analysis. See Burns,
`
`Morris & Stewart Ltd. P’ship v. Masonite Int’l Corp., 401 F. Supp. 2d 692, 697 (E.D. Tex. 2005)
`
`(while a previous construction may be instructive and provide the basis of the analysis, the
`
`previous construction is not binding on the Court, particularly when there are new parties and
`
`those parties have presented new arguments).
`
`AGREED TERMS
`
`The parties agreed to the following constructions in their joint claim construction chart:
`
`6
`
`
`
`
`
`
`
`Ex. 1013 / Page 6 of 43
`
`
`
`Term
`“simultaneously accesses the bus” (’789 Patent
`claim 1)
`“display device” (’194 Patent claims 1, 3, 7,
`11, 16-17; ’368 Patent claims 1, 7, 13, 14, 20,
`21; ’045 Patent claims 1, 4-6, 12, 13; and ’753
`Patent claims 1, 7)
`“display adapter” (’368 Patent claims 2, 3;
`’045 Patent claim 2; and ’753 Patent claim 3)
`
`(Dkt. No. 65-2 at 4-5.)
`
`Agreed Construction
`“accesses the bus at the same time”
`
`“screen and its circuitry”
`
`“an adapter that processes images for a display
`device”
`
`DISPUTED TERMS
`
`
`1. “bus” (’789 Patent claims 1, 13, 15, 28; ’459 Patent claims 1, 2, 7, 11, 13; ’194 Patent
`claims 1, 2, 9, 11, 16-18, 23; ’368 Patent claims 1, 5, 7, 13, 19, 20, 23; ’045 Patent
`claims 1, 4, 5, 12, 15; ’753 Patent claims 1, 7; ’315 Patent claim 1 and ’164 Patent
`claims 1, 6, 7)
`
`PUMA’s Construction
`No construction necessary.
`
`Alternatively:
`“a signal line or a set of associated signal
`lines to which a number of devices are
`coupled and over which information may be
`transferred between them”
`
`
`Defendants’ Construction
`“a signal line or set of associated signal lines
`to which a number of devices are connected
`and over which information may be
`transferred by only one device at a time”
`
`The parties dispute (1) whether devices must be “connected” verses “coupled” to a bus
`
`and (2) whether a bus may only transfer information one device at a time.
`
`Positions of the Parties
`
`
`
`PUMA asserts that the term “bus” is known in the art and does not need construction. Its
`
`alternative construction comes from STMicroelectronics. In STMicroelectronics, the parties
`
`agreed to “a signal or set of signal lines to which a number of devices are coupled and over
`
`which information may be transferred between them.” STMicroelectronics, 327 F. Supp. 2d at
`
`
`
`7
`
`Ex. 1013 / Page 7 of 43
`
`
`
`711. PUMA asserts its construction is consistent with an IEEE extrinsic evidence dictionary.
`
`(Dkt. No. 56 at 6.)
`
`
`
`PUMA objects to Defendants’ construction with regard to the “one device at a time”
`
`limitation. PUMA asserts that such limitation would read out common bus technologies such as
`
`split-transaction buses and other buses that can transfer information between multiple devices at
`
`the same time. PUMA points to the prior art described in U.S. Patent No. 4,785,394 (the ’394
`
`Patent) which shows a split-transaction bus where multiple devices use the bus at the same time:
`
`For example, the ’394 Patent states: “During the time period which elapses between the read
`
`address signal and the response from the memory, the other processors in the computer system
`
`are communicating other signals to other components of the system over the bus.” (Dkt. No. 56
`
`at 6-7 (quoting Dkt. No. 56 Ex. L at 1:58–62).)
`
`
`
`PUMA also points to the prior art Mercury RACEway bus as a bus that allows multiple
`
`devices to send information at the same time. (Id. at 7.) PUMA asserts that Defendants’
`
`construction would exclude this prior art bus. PUMA notes that the defendants in Parthenon II
`
`characterized the Mercury RACEway bus as a “fabric” but that PUMA identified documents
`
`associated with the chips in the Parthenon II defendants’ products that characterized the “fabric”
`
`as a bus. (Id.) In its reply, PUMA notes that Defendants removed the word “directly” from their
`
`proposed construction. Based on such removal, PUMA asserts that the only issue in dispute is
`
`the “one device at a time” limitation. (Dkt. No. 64 at 1.)
`
`
`
`8
`
`Ex. 1013 / Page 8 of 43
`
`
`
`Defendants incorporate by reference the evidence and arguments of the defendants from
`
`Parthenon II. (Dkt. No. 60 at 3.)2 Defendants summarized the Parthenon II arguments that it
`
`adopted as follows:
`
`• The construction of “bus” from the Parthenon I Order is incomplete because it does not
`
`provide sufficient guidance on where one bus ends and another bus begins.
`
`• The limitation “by only one device at a time” clarifies that, if two devices may transmit
`
`at the same time on different signal lines, those lines are not part of a single “bus.”
`
`• Using the term “coupled” to define a “bus” makes it impossible to differentiate between
`
`one bus and two buses.
`
`(Id.).
`
`Defendants assert that the Parthenon I Order made clear that the PCI bus, ISA bus and
`
`memory bus lines are separate buses. Defendants state, however, that the Parthenon I Order left
`
`room for mischief and confusion at trial. (Id. at 4.) Specifically, Defendants assert that the
`
`construction in that Order did not provide a method for determining whether one set of lines is
`
`part of a bus. (Id.)
`
`Furthermore, Defendants state that the lines of a bus are a shared transmission medium
`
`and that a “one device at a time” limitation is fundamental to a shared medium. (Id.) Defendants
`
`assert that if more than one device could simultaneously transmit data over a “set of associated
`
`signal lines,” then that set of signal lines is not a bus within the meaning of the patents-in-suit.
`
`(Id. at 4–5.) Defendants assert that there would be collisions if more than one device transmitted
`
`
`2 Defendants’ responsive brief did not provide substantive argument for six of the nine disputed
`term groupings. Rather, Defendants merely incorporated by reference arguments, exhibits and
`even expert reports/testimony from the Parthenon I or II cases. The Court does not approve of
`such techniques. Though the Court has considered such arguments here, in circumstances in
`which the Court views such briefing techniques as skirting this District’s local rules regarding
`disclosures, page limits, expert testimony, evidence, etc. the Court may decide otherwise.
`9
`
`
`
`Ex. 1013 / Page 9 of 43
`
`
`
`at a time. Defendants assert that mechanisms such as the “arbiter” in the patents prevent or deal
`
`with these collisions. (Id. at 5–6.)
`
`Defendants counter PUMA’s assertions in three ways. First, Defendants assert that every
`
`bus described in the Asserted Patents has a shared medium in which only one device at a time
`
`can transmit. (Id. at 6.) Second, Defendants contend that “one device at a time” does not exclude
`
`split-transaction bus protocols. Defendants assert that a split-transaction bus does not allow two
`
`devices to transmit at once. Defendants claim that even in a split-transaction bus any particular
`
`transaction is split into a request and a response. (Id.) Defendants assert that while one device’s
`
`transaction is being worked on (for example the request is worked on), other devices can transmit
`
`on the bus. However, Defendants assert only one device is transmitting at a time. (Id. 6-7, n. 10.)
`
`Third, Defendants disagree with PUMA’s statements on the Mercury RACEway. Defendants
`
`agree that their construction would exclude the Mercury RACEway. Defendants assert, however,
`
`that the Mercury RACEway is not a bus (id. at 7) and that even if it were an exotic species of
`
`bus, it would be very different from the buses in the specification.
`
`Defendants assert that the intrinsic record does not show that the inventors considered a
`
`“bus” to be anything other than the type of bus discussed in the specification. Defendants state
`
`that the specification and file history do not mention fabrics or crossbars. Therefore, Defendants
`
`assert that PUMA is not entitled to a construction that is divorced from the context of the
`
`intrinsic record. (Id.) Defendants further assert that the RACEway is not a bus but rather a
`
`crossbar extension to a VMEbus. Defendants cite to an explanation provided by Mercury
`
`Systems:
`
`As a backward-compatible upgrade, Interlink modules transform the topology of
`an existing VMEbus chassis from a single transaction bus to a scalable real-time
`fabric . . . .
`
`10
`
`
`
`
`
`Ex. 1013 / Page 10 of 43
`
`
`
` (Dkt. No. 60 at 8 (quoting Dkt. 56 Ex. O at 1).) Defendants assert that Mercury System’s
`
`literature describes the product as something that works with ordinary buses:
`
`The RACEway interconnect fabric provides a uniform communications medium
`that connects processors, I/O devices, and standard bus interfaces, such as VME
`and VSB, in a consistent way throughout the system.
`
`(Id. (quoting Dkt. 56 Ex. O at 3-4).) Defendants assert that the term “bus” is never used to refer
`
`to the RACEway system, except insofar as a “bus” is something that RACEway connects to and
`
`transforms. (Id.) Defendants assert that in context of the patents, the RACEway creates
`
`additional connections between the devices through the RACEway crossbar, so that the devices
`
`do not need to use the actual bus. Defendants assert that because the RACEway allows multiple
`
`devices to transmit at once, it is not a shared medium that each connected device uses to
`
`transmit.
`
`
`
`Defendants assert that the additional documents that PUMA cites to regarding the
`
`RACEway are third party non-Mercury Systems documents. Defendants assert that third party
`
`descriptions of the RACEway are not relevant and not probative. Defendants contend that any
`
`evidentiary value they may possess is far outweighed by the relevant intrinsic record. (Id. at 9.)
`
`Defendants point out that the first additional document PUMA cites (PUMA’s Exhibit N) relates
`
`to military digital signal processor architectures. Defendants assert that the document references
`
`different types of buses including control buses, data buses (Defendants consider RACEway a
`
`data bus), test buses, input/output buses, local/wide area network buses, and PC buses.
`
`Defendants assert that all the examples of buses in the patent fall within the PC bus category. (Id.
`
`at 10.) Defendants assert that though other examples of buses are listed, such examples are not
`
`useful in the context of the patents-in-suit which are about personal computer or system-on-chip
`
`architectures. (Id.) As to PUMA’s Exhibit M, Defendants assert that this document relates to
`
`
`
`11
`
`Ex. 1013 / Page 11 of 43
`
`
`
`military radar systems and on one page refers to Mercury RACEway Bus. (Id.) Defendants assert
`
`that the description is inaccurate. Further, Defendants assert the field (radars) is not relevant to
`
`the technology and audience of the patents-in-suit. (Id.)
`
`As to PUMA’s Exhibit X (which appears to use “fabric” interchangeably with “bus”),
`
`Defendants assert the document is not relevant. Defendants note that the document is dated 2011,
`
`and, thus, assert that it is not probative on the use of the term “bus” fifteen years earlier.
`
`Defendants further assert that the document contains no technical disclosure as to the meaning of
`
`the term “fabric.” Defendants assert that “fabric” could mean a “bus” like those disclosed in the
`
`patent (one device at a time) or could mean a type of switched network of buses. Defendants
`
`contend that would not be a “bus” as used in the patent but rather a collection of multiple buses.
`
`(Id. at 11.) Finally, Defendants state that the removal of “direct” from Defendants’ construction
`
`has rendered the arguments over “direct” moot. (Id.)
`
`In reply, PUMA reiterates that split-transaction buses and the Mercury RACEway bus
`
`would be excluded by Defendants’ construction. As to the split-transaction bus, PUMA asserts
`
`that Defendants admit that, in a split-transaction bus, while the request from one device “is being
`
`worked on, other devices can transmit on the bus.” (Dkt. No. 64 at 2 (quoting Dkt. No. 60 at 6-
`
`7).) PUMA asserts that Defendants’ construction, thus, excludes split-transaction buses. PUMA
`
`state that Defendants attempt to avoid this problem by differentiating between requests and
`
`responses and by suggesting that a bus can handle only one of each type of transaction at a time.
`
`PUMA asserts that Defendants’ construction does not reflect this distinction. PUMA notes that
`
`“request” and “response” transactions are not mentioned in the patents. (Id.) PUMA asserts this
`
`would create jury confusion.
`
`
`
`12
`
`Ex. 1013 / Page 12 of 43
`
`
`
`PUMA contends that Defendants admit that their construction excludes the Mercury
`
`RACEway. (See id. (“PUMA is correct that the term ‘bus’ as used in the patents-in-suit would
`
`not read on Mercury RACEway.”) (quoting Dkt. No. 60 at 7).) PUMA asserts that the patents use
`
`the term “bus” generally without disclaimer. PUMA asserts that, as a result, Defendants’ attempt
`
`to carve out some buses from the construction should be rejected.
`
`PUMA responds to Defendants’ argument that the Mercury RACEway is not a bus.
`
`PUMA asserts that persons of ordinary skill in the art disagree with Defendants. PUMA asserts
`
`that the exhibits cited by PUMA repeatedly refer to the Mercury RACEway as a bus. (Id. (citing
`
`Dkt. No. 56 Ex. N at 203 and Ex. M at 31).) PUMA notes that Exhibit N states that “some
`
`currently available choices for a data bus” include “RACEway (Mercury Computer).” (Dkt. No.
`
`56 Ex. N at 203.) PUMA also notes prior art that states “[t]he Mercury Raceway bus is an
`
`important part of the IFB architecture” and “[t]he P2 connector is also used to propagate the
`
`Raceway bus from board to board.” (Dkt. No. 56 Ex. M at 31.) As to Defendants’ quote from
`
`Exhibit O, PUMA asserts that it supports PUMA’s position. PUMA asserts that the document
`
`states that the Mercury Interlink modules transform the topology from “a single transaction bus
`
`to a scalable real-time fabric.” PUMA asserts that the document distinguishes between two types
`
`of buses: “single transaction buses” and “real-time fabrics.” PUMA asserts that under
`
`Defendants’ argument, the phrase “single transaction” would be entirely redundant because all
`
`buses under Defendants’ construction would presumably be “single transaction” buses.
`
`PUMA asserts that the Qualcomm technical documents that are central to this case refer
`
`to the fabric as a type of bus. (Dkt. No. 64 at 3 (noting that Dkt. 56 Ex. X at 67 states that there
`
`are “three buses that span the entire MSM device” and lists the “system fabric,” “applications
`
`fabric” and “system fast peripheral bus.”).) PUMA cautions that it has raised this evidence for
`
`
`
`13
`
`Ex. 1013 / Page 13 of 43
`
`
`
`the simple purpose of assuring the Court that persons of ordinary skill in the art have always
`
`understood the term “bus” to be broad and inclusive. PUMA asserts that based on the evidence
`
`associated with the Mercury RACEway bus and the Qualcomm fabrics, persons of skill in the art
`
`have not restricted the term “bus” in the manner urged by Defendants. (Id.)
`
`At the oral hearing, Defendants acknowledged that the Parthenon I and Parthenon II
`
`constructions were technically correct but did not provide adequate jury guidance as to where
`
`one bus begins and another bus ends. (Dkt. No. 69 at 7 (hereinafter “Oral Hearing Tr.”).)
`
`Defendants also asserted that “connected” vs. “coupled” was not a primary dispute as that
`
`dispute is better addressed with regard to the “coupled” claim term dispute. (See id. at 12.)
`
`Defendants also acknowledge that they rely on the expert testimony from the Parthenon II case
`
`and that the expert from the Parthenon II case never stated that a structure that could handle two
`
`or more devices at the same time was not a bus. (Id. at 15-17.) At the Oral Hearing, Defendants
`
`emphasized that any given wire can only transmit voltages from one device at any particular
`
`time. (Id. at 17.)
`
`Analysis
`
`The analysis from Parthenon I and Parthenon II applies to the arguments raised by the
`
`parties. Parthenon I Order at 14-17; Parthenon II Order at 13-16. As to the phrase “one device at
`
`a time,” Defendants are, in effect, seeking a negative limitation that bars multiple devices. The
`
`inclusion of a negative limitation within a claim construction generally requires support from the
`
`intrinsic evidence. See Santarus, Inc. v. Par Pharms., Inc., 694 F.3d 1344, 1351 (Fed. Cir. 2012)
`
`(“Negative claim limitations are adequately supported when the specification describes a reason
`
`to exclude the relevant limitation.”); Omega Eng’g, Inc. v. Raytek Corp., 334 F.3d 1314, 1322-23
`
`(Fed. Cir. 2003) (declining to add a negative limitation when there was no “express disclaimer or
`
`
`
`14
`
`Ex. 1013 / Page 14 of 43
`
`
`
`independent lexicography in the written description that would justify adding that negative
`
`limitation”). As to the intrinsic evidence, Defendants only cite to an embodiment. Defendants do
`
`not cite to any disclaimer or disavowal. Even if only a single embodiment exists, the preferred
`
`embodiment is not required to be read into the claims. See Arlington Indus., Inc. v. Bridgeport
`
`Fittings, Inc., 632 F.3d 1246, 1254 (Fed. Cir. 2011) (“Even where a patent describes only a
`
`single embodiment, claims will not be read restrictively unless the patentee has demonstrated a
`
`clear intention to limit the claim scope using words or expressions of manifest exclusion or
`
`restriction.”) (internal citations omitted). Moreover, Defendants’ construction, in essence, reads
`
`the arbiter concept into the “bus” term. However, as described in the patents, the arbiter is a
`
`separate structure that has a separate function. ’459 Patent Figure 7, 12:49-13:36; ’789 Patent
`
`Figure 2, 4:4-11, 9:42-57. The fact that the specification discloses a separate arbiter and
`
`arbitration function shows that the structure and function are not inherent in the term “bus.” As
`
`PUMA points out, the claims also confirm that the arbiter function is not inherently part of the
`
`claimed bus. Some claims recite the arbiter and arbitration limitaions and some claims do not.
`
`See, e.g., ’789 Patent Claims 15 and 19. The intrinsic record does not teach that buses that allow
`
`multiple devices to access at the same time are excluded from the term “bus.”
`
`Most of the parties’ briefing and oral argument focuses on whether the extrinsic evidence
`
`established that “bus,” at the time of the invention, was thought of by those skilled in the art to
`
`require a “one device at a time” limitation. On balance, the Court finds that the extrinsic
`
`evidence does not support including a negative limitation on the term “bus.”
`
`First, the Court notes that Defendants arguments mix concepts that relate to two distinct
`
`structures: a single wire and a bus. None of the parties appears to dispute that a single wire a can
`
`
`
`15
`
`Ex. 1013 / Page 15 of 43
`
`
`
`transmit information for only one device at a time. However, “bus” contains a collection of
`
`wires, not just a single wire.
`
`As for Defendants’ reliance upon the expert declaration of Dr. Stone from Parthenon II,
`
`it is telling that Dr. Stone does not affirmatively state that a bus cannot carry information from
`
`more than one device at a time. See Parthenon II Dkt. No. 86-1 at 10-16. Defendants
`
`acknowledged this issue with Dr. Stone’s testimony at the oral hearing. (Oral Hearing Tr. at 15-
`
`17.) Indeed, the Court notes that Dr. Stone’s testimony was likely directed to a signal line and
`
`not to a “bus”:
`
`36. A wire or “signal line,” can carry only one symbol at any one time because a
`wire is only at one voltage level or carries only one current at any given time.
`
`37. Because a wire can carry only one symbol at any one time, a “bus” composed
`of one or more wires can carry only one bus transaction at any one time over the
`wires. This concept . . . .
`
`Parthenon II Dkt. No. 86-1 at 11. The declaration does not state that any multi-line structure that
`
`carries information from more than one device cannot be a “bus.”
`
`With respect to Defendants claim that a split-transaction bus still transfers information
`
`“one device at a time,” it is clear that Defendants acknowledge that a split-transaction bus
`
`provides for overlapping transactions. (Dkt. No. 60 at 6-7.) PUMA asserts that in the split-
`
`transaction process both devices use the bus at the same time (i.e., two operations are being
`
`performed concurrently). Defendants assert that only one device uses the bus at a time because at
`
`any particular time only data from one device is on the signal lines. The question reduces to
`
`whether “one device at a time” should be construed to mean the usage of the bus in an
`
`“oper