throbber
Trials@uspto.gov
`571-272-7822
`
`
`
`
`
`Paper No. 12
`Filed: January 17, 2019
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`DAIMLER AG,
`Petitioner,
`
`v.
`
`BLITZSAFE TEXAS, LLC,
`Patent Owner.
`____________
`
`Case IPR2018-01214
`Patent 7,489,786 B2
`____________
`
`
`Before JAMESON LEE, THOMAS L. GIANNETTI,
`and MIRIAM L. QUINN, Administrative Patent Judges.
`
`LEE, Administrative Patent Judge.
`
`
`
`
`DECISION
`Denying Institution of Inter Partes Review
`37 U.S.C. § 314(a)
`
`
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`I.
`
`INTRODUCTION
`
`A. Background
`On June 6, 2018, Petitioner filed a Petition to institute inter partes
`review of claims 1, 2, 4–8, 10, 13, 14, 23, 24, 44, 47, 57, 58, 60–65, 86, 88–
`92, 94, 97, and 98 of U.S. Patent No. 7,489,786 B2 (Ex. 1001, “the ’786
`patent”). On August 22, 2018, Petitioner filed a Corrected Petition,
`authorized by the Board and not opposed by Patent Owner. Paper 7. The
`Corrected Petition challenges the same claims on the same grounds as
`articulated in the original Petition. Hereinafter, we refer to the Corrected
`Petition as the Petition (“Pet.”). On November 9, 2018, Patent Owner filed a
`Preliminary Response (Paper 10, “Prelim. Resp.”).
`To institute an inter partes review, we must determine that the
`information presented in the Petition shows “that there is a reasonable
`likelihood that the petitioner would prevail with respect to at least 1 of the
`claims challenged in the petition.” 35 U.S.C. § 314(a). Having considered
`both the Petition and the Preliminary Response, we determine that Petitioner
`has not demonstrated a reasonable likelihood that it would prevail in
`establishing the unpatentability of any of the challenged claims.
`Accordingly, we do not institute review and the Petition is denied.
`Related Matters
`The parties identify eight civil actions involving the ’786 patent. Pet.
`83; Paper 4, 1–2. The ’786 patent also is the subject of these inter partes
`review proceedings: IPR2016-00421, IPR2016-00422, IPR2016-01448,
`IPR2016-01472, IPR2016-01477, IPR2018-01142, IPR2018-01203,
`IPR2018-01204, and IPR2018-01211. Paper 4, 2. We instituted review
`
`B.
`
`2
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`only in IPR2016-00421, which has terminated by settlement. We have
`denied institution of review in all other proceedings.
`
`C.
`
`The ’786 Patent
`The ’786 patent is entitled “Audio Device Integration System.” Ex.
`1001, [54]. According to the ’786 patent, a “particular problem with
`integrating after-market audio systems with existing car stereos is that
`signals generated by the car stereo is in a proprietary format, and is not
`capable of being processed by the after-market system.” Id. at 1:36–39.
`“Thus, in order to integrate after-market systems with car stereos, it is
`necessary to convert signals between such systems.” Id. at 1:42−44.
`The ’786 patent is directed to an audio device integration system that
`allows after-market audio devices to be integrated for use with an existing
`car stereo system, such that control commands can be issued at the car stereo
`for execution by the audio device and data from the audio device can be
`displayed on the car stereo. Id. at Abstr., 2:12–42. More specifically,
`control commands generated at the car stereo are received, converted into a
`format recognizable by the after-market audio device, and dispatched to the
`device for execution. Id. at Abstr., 2:35–40. In addition, information from
`the audio device, such as track, channel, song, and artist information, is
`received, processed, converted into a format recognizable by the car stereo,
`and dispatched to the stereo for display. Id. at Abstr., 2:40–47. The audio
`device could, for example, comprise a “CD player, CD changer, MP3 player,
`satellite receiver, [or] digital audio broadcast (DAB) receiver.” Id. at 4:28–
`30; see id. at [57], 2:23–26. Figures 2A–2C are reproduced below:
`
`3
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`
`
`
`Figures 2A–C illustrate embodiments in which a car stereo is integrated with
`a CD player (Figure 2A), an MP3 player (Figure 2B), and a satellite radio or
`DAB receiver (Figure 2C). Id. at 3:14–23.
`With regard to Figure 2B, the ’786 patent describes:
`The interface 20 allows data and audio signals to be exchanged
`between the MP3 player 30 and the car radio 10, and processes
`and formats signals accordingly so that instructions and data
`from the radio 10 are processable by the MP3 player 30, and vice
`versa. Operational commands, such as track selection, pause,
`play, stop, fast forward, rewind, and other commands, are entered
`via the control panel buttons 14 of car radio 10, processed by the
`interface 20, and formatted for execution by the MP3 player 30.
`Data from the MP3 player, such as track, time, and song
`information, is received by the interface 20, processed thereby,
`and sent to the radio 10 for display on display 13. Audio from
`MP3 player 30 is selectively forwarded by the interface 20 to the
`radio 10 for playing.
`Id. at 6:11–24. Similar description is provided with respect to Figures 2A
`and 2C. Id. at 5:49–55, 6:35–43.
`In addition, an external audio device as well as auxiliary input sources
`may be integrated with a car stereo. Id. at Abstr., 2:53–56. A user then “can
`select between the external audio device and the auxiliary input using the
`controls of the car stereo.” Id. at 2:56–57. Figure 1 is reproduced below:
`
`4
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`
`Figure 1 illustrates an embodiment integrating a car stereo with a CD player,
`a MP3 player, and a satellite radio or DAB receiver, as well as a number of
`auxiliary input sources. Id. at 3:12–13, 5:14–27.
`As shown in the above figures, central to the ’786 patent is an
`“interface” positioned between the car stereo and the audio device(s) and
`auxiliary input(s). See, e.g., id. at Fig. 1, 2A–C, 5:33–36. The interface
`allows for the integration of the audio devices and auxiliary inputs with the
`original or after-market car radio or stereo. Id. at 5:33–36. A docking
`station also is provided for docking a portable audio or video device for
`integration with the car stereo. Id. at Abstr.
`Claims 1, 44, 57, 86, and 92 are independent. Claim 1 is directed to a
`system that connects an after-market audio device as well as one or more
`auxiliary input sources to a car stereo. In particular, claim 1 recites a first
`connector electrically connectable to a car stereo, a second connector
`electrically connectable to an after-market device, and a third connector
`electrically connectable to one or more auxiliary input sources. Id. at 21:33–
`38. Claim 1 also recites an interface connected between the first and second
`electrical connectors, and that the interface includes a microcontroller pre-
`programmed to execute:
`
`5
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`a first pre-programmed code portion for remotely controlling the
`after-market audio device using the car stereo by receiving a
`control command from the car stereo through said first
`connector in a format incompatible with the after-market
`audio device, processing the received control command into
`a formatted command compatible with the after-market audio
`device, and transmitting the formatted command to the after-
`market audio device through said second connector for
`execution by the after-market audio device;
`a second pre-programmed code portion for receiving data from
`the after-market audio device through said second connector
`in a format incompatible with the car stereo, processing the
`received data into formatted data compatible with the car
`stereo, and transmitting the formatted data to the car stereo
`through said first connector for display by the car stereo; and
`a third pre-programmed code portion for switching to one or
`more auxiliary input sources connected to said third electrical
`connector.
`Id. at 21:44–64.
`Claim 57 is directed to a system including an interface that connects a
`portable MP3 player to a car stereo. Claim 86 is directed to a system
`including an interface that connects an after-market video device to a car
`stereo. Claim 92 is directed to a system including an interface that connects
`a portable audio device with a car stereo. Claims 57, 86, and 92 each require
`the generation, within an interface, of a device presence signal that is
`transmitted to the car stereo to maintain the car stereo in an operational state.
`Claims 57, 86, and 92 are reproduced below:
`57. An audio device integration system comprising:
`a first electrical connector connectable to a car stereo;
`a second electrical connector connectable to a portable MP3
`player external to the car stereo
`an interface connected between said first and second electrical
`
`6
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`connectors for transmitting audio from a portable MP3 player
`to a car stereo, said interface including a microcontroller in
`electrical communication with said first and second electrical
`connectors,
`said microcontroller pre-programmed to execute:
`a first pre-programmed code portion for generating a
`device presence signal and transmitting the signal to
`the car stereo to maintain the car stereo in an
`operational state; and
`a second pre-programmed code portion for remotely
`controlling the MP3 player using the car stereo by
`receiving a control command from the car stereo
`through said first electrical connector in a format
`incompatible with the MP3 player, processing the
`control command into a formatted control command
`compatible with the MP3 player, and transmitting
`the formatted control command to the MP3 player
`through said second electrical connector for
`execution by the MP3 player.
`Id. at 26:13–37.
`86. A device for integrating video information for use with a car
`stereo, comprising:
`a first electrical connector connectable to a car stereo;
`a second electrical connector connectable to an after-market
`video device external to the car stereo;
`an interface connected between said first and second electrical
`connectors for transmitting video information from the after-
`market video device to the car stereo, the interface including
`a microcontroller in electrical communication with said first
`and second electrical connectors, said microcontroller pre-
`programmed to execute:
`a first pre-programmed code portion for generating a
`device presence signal and transmitting the signal to
`the car stereo through said first electrical connector
`to maintain the car stereo in an operational state
`
`7
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`responsive to signals generated by the after-market
`video device.
`Id. 28:40–56.
`92. An audio device integration system comprising:
`a car stereo;
`a portable audio device external to the car stereo;
`an interface connected between the car stereo and the portable audio
`device, the interface including a microcontroller pre-programmed
`to execute:
`first pre-programmed means for generating a device presence
`signal and transmitting the signal to the car stereo to
`maintain the car stereo in an operational state;
`second pre-programmed means for remotely controlling the
`portable audio device using the car stereo by receiving a
`control command from the car stereo in a format
`incompatible with the portable audio device, processing
`the control command into a formatted control command
`compatible with
`the portable audio device, and
`transmitting the formatted control command to the
`portable audio device for execution thereby; and
`means for transmitting audio from the portable audio device
`to the car stereo.
`Id. at 29:11–31.
`Claim 44 is directed to an apparatus for docking a portable device for
`integration with a car stereo. We reproduce claim 44 in the portion of our
`analysis below specifically discussing claim 44.
`
`
`
`8
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`D.
`
`Evidence Relied Upon
`Petitioner relies on the following references:1
`
`
`
`Reference
`
`Barnea
`
`U.S. Patent 6,396,164 B1
`
`Plagge
`
`German App. Pub. DE
`10101702A1
`
`Bhogal
`
`U.S. Patent 6,629,197 B1
`
`Ohmura
`
`U.S. App. Pub. 2001/0028717
`A1
`
`Frese
`
`U.S. Patent 6,472,711 B1
`
`Exhibit
`
`Ex. 1004
`
`Date
`
`May 28, 2002,
`filed
`October 20,
`1999.
`
`July 18, 2002 Ex. 10052
`
`Ex. 1006
`
`Sept. 30, 2003,
`filed Nov. 3,
`2000
`
`Oct. 11, 2001 Ex. 1008
`
`Ex. 1009
`
`Oct. 29, 2002,
`filed July 31,
`2000
`
`
`Petitioner also relies on the Declarations of Chris Kyriakakis, Ph.D.
`(Ex. 1003), and Philip Koopman, Ph.D. (Ex. 1013).
`
`
`
`
`1 The ’786 patent was filed on December 11, 2002. Ex. 1001, [22].
`2 Exhibit 1005 contains a certified English translation of the German
`publication. Hereinafter, references to the German reference will be made to
`the English translation thereof.
`
`9
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`E.
`
`The Asserted Grounds
`Petitioner asserts the following grounds of unpatentability:
`
`Basis
`
`References
`
`§ 103(a) Barnea, Plagge, and Bhogal
`
`Claim(s) Challenged
`1, 2, 4, 5, 13, 14, 23, 24, 44, and
`47
`6, 57, 58, 60, 63, 64, 65, 92, 94,
`97, and 98
`
`7 and 8
`
`61 and 62
`
`10
`
`86, 88, 89, 90, and 91
`
`A.
`
`§ 103(a) Barnea, Plagge, Bhogal, and
`CAN
`§ 103(a) Barnea, Plagge, Bhogal, and
`Ohmura
`§ 103(a) Barnea, Plagge, Bhogal,
`Ohmura, and CAN
`§ 103(a) Barnea, Plagge, Bhogal, and
`Frese
`§ 103(a) Barnea, Plagge, Bhogal,
`Frese, and CAN
`
`II. ANALYSIS
`The Law on Obviousness
`The question of obviousness is resolved on the basis of underlying
`factual determinations including: (1) the scope and content of the prior art;
`(2) any differences between the claimed subject matter and the prior art;
`(3) the level of ordinary skill in the art; and (4) when in evidence, objective
`evidence of nonobviousness. Graham v. John Deere Co., 383 U.S. 1, 17–18
`(1966). One seeking to establish obviousness based on more than one
`reference also must articulate sufficient reasoning with rational
`underpinnings to combine teachings. See KSR Int’l Co. v. Teleflex, Inc., 550
`U.S. 398, 418 (2007).
`
`
`10
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`B.
`
`The Level of Ordinary Skill in the Art
`Petitioner asserts that the level of ordinary skill in the art at the time of
`the earliest effective filing date of the ’786 patent corresponds to “at least an
`undergraduate degree in computer science or computer engineering, or
`equivalent work experience, including familiarity with transmission of audio
`and video and methods of software control and data conversions.” Pet. 14
`(citing Ex. 1003 ¶ 26). Patent Owner states that for purposes of this
`proceeding, it agrees that the level of ordinary skill as articulated by
`Petitioner is appropriate. Prelim. Resp. 4. We credit the supporting
`testimony of Dr. Kyriakakis. Ex. 1003 ¶ 26. We adopt the level of ordinary
`skill as articulated by Petitioner, except that we delete the qualifier “at least”
`to eliminate vagueness. The qualifier expands the range indefinitely without
`an upper bound and thus precludes a meaningful indication of the level of
`ordinary skill in the art.
`
`C. Claim Construction
`In an inter partes review, the Board interprets claims terms of an
`unexpired patent using the “broadest reasonable construction in light of the
`specification of the patent.” 37 C.F.R. § 42.100(b); Cuozzo Speed Techs.,
`LLC v. Lee, 136 S. Ct. 2131, 2144–46 (2016). Under the broadest
`reasonable interpretation standard, claim terms generally 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). There are, however, two
`exceptions to that rule: “1) when a patentee sets out a definition and acts as
`his own lexicographer,” and “2) when the patentee disavows the full scope
`
`11
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`of a claim term either in the specification or during prosecution.” Thorner v.
`Sony Comp. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012).
`It is likewise not enough [for disavowal] that the only
`embodiments, or all of the embodiments, contain a particular
`limitation. We do not read limitations from the specification into
`claims; we do not redefine words. Only the patentee can do that.
`To constitute disclaimer, there must be a clear and unmistakable
`disclaimer.
`Id. at 1366–67. See also EPOS Techs. Ltd. v. Pegasus Techs. Ltd., 766 F.3d
`1338, 1341 (Fed. Cir. 2014).
`If an inventor acts as his or her own lexicographer, the definition must
`be set forth in the specification with reasonable clarity, deliberateness, and
`precision. Renishaw PLC v. Marposs Societa’ per Azioni, 158 F.3d 1243,
`1249 (Fed. Cir. 1998). Disavowal can be effectuated by language in the
`specification or the prosecution history. Poly-America, L.P. v. API Indus.,
`Inc., 839 F.3d 1131, 1136 (Fed. Cir. 2016). “In either case, the standard for
`disavowal is exacting, requiring clear and unequivocal evidence that the
`claimed invention includes or does not include a particular feature.” Id.
`Neither party contends that the Specification of the ’786 patent specially
`defined any term or that the inventors of the ’786 patent acted as their own
`lexicographer. We have no reason to determine otherwise.
`Only those claim terms that are in controversy need to be construed,
`and only to the extent necessary to resolve the controversy. See Nidec
`Motor Corp. v. Zhongshan Broad Ocean Motor Co. Ltd. Matal, 868 F.3d
`1013, 1017 (Fed. Cir. 2017); Wellman, Inc. v. Eastman Chem. Co., 642 F.3d
`1355, 1361 (Fed. Cir. 2011); Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc.,
`200 F.3d 795, 803 (Fed. Cir. 1999).
`
`12
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`For purposes of this decision on whether to institute review, we need
`to construe the term “interface.”
`“interface”
`Of all challenged claims, claims 1, 44, 57, 86, and 92 are independent,
`
`and each recites an “interface.”
`Claims 1, 57, and 86 require the interface to be connected between a
`first electrical connector and a second electrical connector, where the first
`connector is connectable to a car stereo and the second connector is
`connectable to an after-market audio device (claim 1), a portable MP3 player
`(claim 57), or an after-market video device (claim 86). Claim 92 requires
`the interface to be connected between the car stereo and a portable audio
`device. Claim 44 recites a docking portion that mates with a portable
`device, and an interface that is connected to the car stereo as well as to a data
`port that communicates with the docking portion.
`Also, claim 57 recites that the interface is “for transmitting audio from
`a portable MP3 player to a car stereo”; claim 86 recites that the interface is
`“for transmitting video information from the after-market video device to the
`car stereo”; claim 1 recites that the interface is “for channeling audio signals
`to the car stereo from the after-market audio device”; claim 44 recites an
`interface for “channeling audio from the portable device to the car stereo”;
`and claim 92 recites that the interface includes a microcontroller pre-
`programmed to execute “means for transmitting audio from the portable
`audio device to the car stereo.”
`Petitioner has not proposed a construction for “interface,” but
`indicates that but for the term “device presence signal,” and all means-plus-
`function elements, all other terms should be accorded their plain and
`
`13
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`ordinary meaning. Pet. 14–17. Patent Owner assumes that we would adopt
`the construction the Board accorded the term “interface” in IPR2016-00421
`(Paper 13, 15) involving the same patent, i.e., “a physical unit that connects
`one device to another and that has a functional and structural identity
`separate from that of both connected devices.” Prelim. Resp. 6.
`With regard to an “interface,” the Specification states:
`Thus, as can be readily appreciated, the interface 20 of the
`present invention allows for the integration of a multitude of
`devices and inputs with an OEM or after-market car radio or
`stereo.
`Ex. 1001, 5:33–36.
`As mentioned earlier, the interface 20 of the present invention
`allows for a plurality of disparate audio devices to be integrated
`with an existing car radio for use therewith.
`Id. at 6:4–7.
`Data from the MP3 player, such as track, time, and song
`information, is received by the interface 20, processed thereby,
`and sent to the radio 10 for display on display 13. Audio from
`the MP3 player 30 is selectively forwarded by the interface 20 to
`the radio 10 for playing.
`Id. at 6:19–24. Thus, the Specification refers to the interface receiving
`information from an audio device and forwarding information to the car
`stereo, and to the interface allowing integration of a plurality of disparate
`audio devices with a car radio.
`
`During prosecution, the Applicants of the ’786 patent distinguished
`U.S. Patent 6,993,615 B2 (“Falcon”), in part by arguing that the reference
`failed to disclose an interface connected between a car stereo and an external
`audio source. Ex. 1002, 267. Specifically, in distinguishing the invention
`from Falcon, Applicants stated: “[Falcon’s graphical user interface] is an
`
`14
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`entirely different concept than the interface of the present invention, which
`includes a physical interface device connected between a car stereo system
`and an external audio source (e.g., a plurality of auxiliary input sources).”
`Id.
`Construing the term “interface” in light of the Specification, other
`
`language in the claims, as well as the prosecution history noted by
`Petitioner, we determine that—interface is a physical unit that connects one
`device to another and that has a functional and structural identity separate
`from that of both connected devices.3
`In the specific context of claims 1 and 86, the connected devices are
`
`the car stereo and an after-market device. In the specific context of claims
`44, 57, and 92, the connected devices are the car stereo and a portable
`device.
`D. Motivation to Combine Barnea and Bhogal
`Barnea
`1.
`Barnea is directed to vehicle electrical systems, and in particular, to a
`method and apparatus for integrating control functions within a vehicle
`electrical system. Ex. 1004, 1:5–8. As background, Barnea explains:
`Many motor vehicles are designed with an original
`equipment manufacturer (OEM) communication bus structure
`that allows the original equipment (OE) electronic devices to
`communicate with each other and with device controllers and
`with other vehicle systems connected to the bus. This bus
`structure, however, typically operates using a proprietary
`communications protocol. The OE devices connected to the
`
`3 This is the same construction the Board gave the term “interface” in
`IPR2016-00421. A copy of the Board’s institution decision there is entered
`in this proceeding as Exhibit 3001, and a copy of Exhibit 1102 in that
`proceeding is entered in this proceeding as Exhibit 3002.
`
`15
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`OEM bus are generally designed and engineered or specified by
`the vehicle manufacturer such that they are completely
`compatible with the proprietary protocol. However, since each
`manufacturer may have its own protocol, devices that are
`typically available as aftermarket equipment may not readily
`interface with the OEM bus.
`Ex. 1004, 1:27–39.
`
`It has been proposed to provide a gateway to the OEM bus
`that permits a limited amount of interaction between add-on
`electronic devices and the OEM bus. . . . While it has been only
`suggested to have such a gateway permit interaction of the OE
`controls and indicators with the add-on devices, a suitable
`architecture and methodology that actually permits such
`interaction has not been achieved. Therefore, each add-on
`electronic device still requires a set of controls and displays
`separate from the vehicle controls and displays.
`Thus, there is a need for a method and apparatus of
`integrating the controls and indicators of add-on devices with the
`existing electronic devices within a motor vehicle.
`Id. at 1:50–2:7.
`Figure 1 of Barnea is reproduced below:
`
`
`Figure 1 is a block diagram illustration of vehicle electronic system
`architecture in accordance with a preferred embodiment of Barnea.
`Ex. 1004, 2:30–32. According to Barnea, electronic devices are added to the
`
`16
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`electrical system of a motor vehicle and they utilize controls and indicators
`already existing within the vehicle. Id. at 2:19–21.
`Vehicle electrical system 10 includes an original equipment
`manufacturer (OEM) data bus, vehicle bus 12, to which various
`original equipment (OE) electronic devices are coupled. Id. at 2:29–
`32. Driver information center (DIC) 14, radio 16, and HVAC
`controller 18 are coupled to vehicle bus 12. Id. at 2:32–33. DIC 14
`includes a suitable display, such as a light emitting diode (LED) or
`liquid crystal (LC) display that may provide text and graphic
`information to the driver. Id. at 2:33–36. Also coupled to the vehicle
`bus are controls 20, 22, 24, and 26, which may be provided on
`steering wheel 28 of the vehicle. Id. at 2:36–39.
`Coupled to vehicle bus 12 is gateway 30. Id. at 2:41. Gateway
`30 couples vehicle bus 12 with device bus 32. Id. at 41–42. To
`device bus 32 is coupled numerous electronic devices such as pager
`34, cellular phone 36, and other devices generally indicated by
`reference numeral as 38 and which can be navigation systems,
`infrared transceivers, personal computers, personal digital assistants,
`communication/data ports or docking stations, and the like. Id. at
`2:46–50.4 Barnea further describes that device bus 32 may not be
`necessary and that the various electronic devices may be coupled
`directly to the gateway. Id. at 2:54–59.
`
`
`4 Claim 14 of Barnea refers to an “entertainment device” as a member of a
`group of devices from which at least one of a plurality of electronic devices
`coupled to the gateway may be chosen. Id. at 6:34–39.
`
`17
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`Also coupled to data bus 32 is an auxiliary control assembly 40
`including a plurality of controls 42, 44, 46, and 48. Id. at 2:60–62.
`Control assembly 40 also may include a display or indicators such as a
`LC display, LEDs, a voice synthesizer or an audible signal generator,
`all generally depicted as display 50. Id. at 2:62–65. Barnea states that
`“the devices 34–38 may be controlled and operated using the vehicle
`controls 20–26 and/or the controls 42–48.” Id. at 2:65–67.
`According to Barnea, controls 20–26 are not associated with the
`operation of any one particular electronic device, and whether the
`operation of any device is effected by manipulation of controls 20–26
`depends on the current operating context of electronic system 10.
`Id. at 3:3–9. Similarly, according to Barnea, controls 42–48 are not
`associated with the operation of any one particular device, and the
`information provided or displayed by either DIC 14 and/or display 50
`may also depend on the operating context. Id. at 3:10–13.
`The operating context may be determined by gateway 30. Id. at
`3:14–15. Gateway 30 includes memory 31 in which various operating
`contexts are stored. Id. at 3:15–17. Associated with each operating
`context are control data which provide a mapping of control
`manipulations for a given device. Id. at 3:17–21.
`About establishing an operating context, Barnea describes:
`Operating context may be established in a number of
`ways. For example, a default context may exists wherein
`manipulation of the controls 20–26 and 42–48 control a default
`electronic device or devices. For example, controls 20 and 22
`may, in the default context, control the volume, up or down,
`respectively, of the radio 16. The operating context may be
`selectable. For example, from the default context control 24 may
`
`18
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`manipulate a scrolling list of operating context choices on either
`or both of DIC 14 and display 50 while control 26 may permit
`selection of a particular operating context. Upon selection, the
`electronic system 10 enters the operating context.
`In accordance with a preferred embodiment of the
`invention, the operating context may be automatically selected
`based upon activation or operating state of a device.
`Id. at 3:22–36.
`
`Figure 2 of Barnea is reproduced below:
`
`
`
`Figure 2 is a flow chart illustrating a method of integrating controls and
`functions according to a preferred embodiment of Barnea.
`
`With respect to the steps shown in Figure 2, Barnea describes:
`With reference to FIG. 2, a method 100 in accordance with
`
`the invention begins at step 102 with respect [to] an input from
`at least one of the controls 20–26 and 42–48. The gateway 30
`then determines the operating context of the electronic system
`10, step 104. Depending on the operating context, i.e., which
`device the operating context is associated with, step 106, the
`input is mapped to control data for the appropriate device, step
`108. Thus, the invention provides a method of utilizing the
`
`19
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`
`controls already within a vehicle to control devices that are later
`added to the vehicle.
`Id. at 4:29–38 (emphasis added).
`As described, the gateway 30 may retain the data
`
`necessary to determine the current operating context as well as
`the data necessary to map inputs from the controls 20–26 and
`42–48 to control data for the appropriate device. When a
`device is added to the device bus 32, the device may preferably
`report data to the gateway 30 that defines the device’s operating
`context and associated control data. Thus, new devices are
`easily added to the electronic system 10 utilizing the controls
`and indicators already associated with the electronic system 10.
`Id. at 4:39–48 (emphasis added).
`Plagge
`2.
`Plagge relates to an “interface emulator” connected between a media
`player that plays audio stored therein in compressed form and a vehicle
`audio device that includes input for receiving only standard CD audio
`signals. Ex, 1005, [57]. The interface emulator converts control and status
`signals emitted by the vehicle audio device into a format compatible with the
`media player, and status signals emitted by the media player into a format
`compatible with the input requirements of the vehicle audio device for
`receiving CD audio. Id. In a preferred embodiment, the media player is a
`portable MP3 player detachably mountable to an accepting unit. Id. ¶ 16.
`
`Specifically, Plagge describes “the interface emulator converting
`control and status signals emitted by the vehicle radio into a format
`compatible for the player and status signals emitted by the player into a
`format compatible to the CD-converter [the input/output interface at the car
`stereo for a CD player].” Ex. 1005 ¶ 8. Additionally, Plagge describes that,
`in one preferred embodiment, “the output of the player for the digital audio
`
`20
`
`
`
`

`

`IPR2018-01214
`Patent 7,489,786 B2
`
`signals saved in a compressed form is directly connected to an input of the
`vehicle audio device, with the digital audio signals then being converted in
`the player, prior to forwarding to the vehicle audio device, into analog audio
`signals.” Id. ¶ 9.
`
`Figure 1 of Plagge is reproduced below:
`
`
`Figure 1 of Plagge illustrates a schematic diagram of Plagge’s system.
`
`In pertinent part, Plagge states:
`The interface emulator 4 receives these signals [control and
`status signals from the vehicle audio unit] and converts them into
`a format for the MP3-player 7. The converted control and status
`signals are then sent by the interface emulator 4 via the wireless
`interface 5 and received via the wireless interface 9 by the MP3-
`player 7 and executed. Inversely, the MP3-player 7 sends its
`status signals via the wireless interface 9, which are then received
`by the wireless interface 5 of the interface emulator 4. The
`interface emulator 4 converts the status signals of the MP3-
`player 7 into status signals of a CD-transformer [CD player] and
`transmits them via the interface 2 to the motor vehicle radio 1.
`Id. ¶ 18

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