throbber
Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 1 of 31
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE WESTERN DISTRICT OF TEXAS
`WACO DIVISION
`
`
`MicroPairing Technologies LLC,
`
` Plaintiff,
`
`v.
`
`Toyota Motor Manufacturing Texas, Inc.,
`
` Defendant.
`
`
`
`
`
`
`
`
`
`
`
`Civil Action No. 6:20-cv-1001
`
`Jury Trial Demanded
`
`COMPLAINT FOR PATENT INFRINGEMENT
`
`Plaintiff MicroPairing Technologies LLC files this Complaint against Toyota Motor
`
`
`
`
`
`
`
`
`Manufacturing Texas, Inc. for infringement of U.S. Patent Nos. 6,629,033 (“the ’033 patent”),
`
`6,778,073 (“the ’073 patent”), 7,793,136 (“the ’136 patent”), 8,380,383 (“the ’383 patent”),
`
`8,953,816 (“the ’816 patent”), 9,697,015 (“the ’015 patent”), and 8,583,292 (“the ’292 patent”).
`
`The ’033 patent, ’073 patent, ’136 patent, ’383 patent, ’816 patent, ’015 patent, and ’292 patent
`
`are referred to collectively as the “patents-in-suit.”
`
`THE PARTIES
`
`1.
`
`Plaintiff MicroPairing Technologies LLC (“MicroPairing”) is a Texas limited
`
`liability company located in Plano, Texas.
`
`2.
`
`Defendant Toyota Motor Manufacturing Texas, Inc. (“Toyota Texas”) is a Texas
`
`corporation with a regular and established place of business at 1 Lone Star Pass, San Antonio,
`
`Texas 78624. Toyota may be served with process through its registered agent, CT Corporation
`
`System, 1999 Bryan Street, Suite 900, Dallas, Texas 75201.
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 2 of 31
`
`3.
`
`Toyota Texas employs approximately 2,600 workers at its San Antonio
`
`manufacturing facility, where it manufactures the Toyota Tundra and Toyota Tacoma pickup
`
`trucks. Toyota Texas states that the “San Antonio plant is also our first plant to integrate
`
`production facilities for many of our suppliers on the same grounds, and some under the same
`
`roof. It’s truly state-of-the-art.” See https://www.toyota.com/usa/operations/map.html#!/tmmtx.
`
`It also touts itself as “the home of the Toyota Tundra and Tacoma pickup trucks – built in the
`
`Southside of San Antonio!” On information and belief, each Toyota Tundra and Tacoma is
`
`manufactured with an infotainment system. Toyota Texas infringes one or more of the patents-
`
`in-suit whenever it makes, uses, sells, or offers to sell a Tundra or Tacoma with such a system.
`
`JURISDICTION AND VENUE
`
`4.
`
`This action arises under the patent laws of the United States, 35 U.S.C. § 101, et
`
`seq. This Court’s jurisdiction over this action is proper under the above statutes, including 35
`
`U.S.C. § 271, et seq., 28 U.S.C. § 1331 (federal question jurisdiction), and 28 U.S.C. § 1338
`
`(jurisdiction over patent actions).
`
`5.
`
`This Court has personal jurisdiction over Toyota Texas in accordance with due
`
`process and/or the Texas Long Arm Statute because, among other things, Toyota Texas is a
`
`Texas corporation with a physical location in Texas.
`
`6.
`
`This Court also has personal jurisdiction over Toyota Texas in accordance with
`
`due process and/or the Texas Long Arm Statute because Toyota Texas does business in this state
`
`by, among other things, “recruit[ing] Texas residents, directly or through an intermediary located
`
`in this state, for employment inside or outside this state.” TEX. CIV. PRAC. & REM. CODE §
`
`17.042(3):
`
`2
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 3 of 31
`
`
`
`See, e.g., https://tmm.taleo.net/careersection/10020/jobsearch.ftl?lang=en#.
`
`7.
`
`Further, this Court has personal jurisdiction over Toyota Texas because it has
`
`engaged, and continues to engage, in continuous, systematic, and substantial activities within this
`
`state, including the substantial marketing and sale of products and services within this state and
`
`this District. Indeed, this Court has personal jurisdiction over Toyota Texas because it has
`
`committed acts giving rise to MicroPairing’s claims for patent infringement within and directed
`
`to this District, has derived substantial revenue from its goods and services provided to
`
`individuals in this state and this District, and maintains a regular and established place of
`
`business in this District, including its facilities in San Antonio, Texas.
`
`8.
`
`Relative to patent infringement, Toyota Texas has committed and continues to
`
`commit acts in violation of 35 U.S.C. § 271, and has made, used, marketed, distributed, offered
`
`for sale, and/or sold infringing products and services in this state, including in this District, and
`
`otherwise engaged in infringing conduct within and directed at, or from, this District. Such
`
`infringing products and services, namely Toyota Tundra and Tacoma vehicles with infotainment
`
`3
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 4 of 31
`
`systems, have been and continue to be distributed to, sold, and used in this District and the
`
`infringing conduct has caused, and continues to cause, injury to MicroPairing, including injury
`
`suffered within this District. These are purposeful acts and transactions in this state and this
`
`District such that Toyota Texas reasonably should know and expect that it can be haled into this
`
`Court because of such activities.
`
`9.
`
`Venue is proper in this District under 28 U.S.C. §§ 1391 and 1400(b) because a
`
`substantial part of the events or omissions giving rise to the MicroPairing claims occurred in this
`
`District. This includes extensive commission of acts of infringement in this District. Toyota
`
`Texas also has a regular and established place of business in this District in the form of, at least,
`
`its San Antonio-based manufacturing plant and related facilities. Indeed, Toyota Texas conducts
`
`business in this District, including making and servicing infringing vehicles for, and offering to
`
`sell, selling, and distributing infringing vehicles and related services to, Toyota Texas customers
`
`in this District.
`
`THE PATENTS-IN-SUIT
`
`10.
`
`The ’033 patent is entitled, “Open Communication System for Real-Time
`
`Multiprocessor Applications.” The ’033 patent lawfully issued on September 30, 2003 and
`
`stems from U.S. Patent Application No. 09/841,753, which was filed on April 24, 2001. A copy
`
`of the ’033 patent is attached hereto as Ex. 1.
`
`11.
`
`The ’073 patent is entitled, “Method and Apparatus for Managing Audio
`
`Devices.” The ’073 patent lawfully issued on August 17, 2004 and stems from U.S. Patent
`
`Application No. 09/892,295, which was filed on June 26, 2001. A copy of the ’073 patent is
`
`attached hereto as Ex. 2.
`
`4
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 5 of 31
`
`12.
`
`The ’136 patent is entitled, “Application Management System with Configurable
`
`Software Applications.” The ’136 patent lawfully issued on September 7, 2010 and stems from
`
`U.S. Patent Application No. 11/616,650, which was filed on December 27, 2006. A copy of the
`
`’136 patent is attached hereto as Ex. 3.
`
`13.
`
`The ’383 patent is entitled, “Distributed vehicle control system.” The ’383 patent
`
`lawfully issued on February 19, 2013 and stems from U.S. Patent Application No. 13/447,793,
`
`which was filed on April 16, 2012. A copy of the ’383 patent is attached hereto as Ex. 4.
`
`14.
`
`The ’816 patent is entitled, “Method and Apparatus to Dynamically Configure a
`
`Vehicle Audio System.” The ’816 patent lawfully issued on February 10, 2015 and stems from
`
`U.S. Patent Application No. 13/196,654, which was filed on August 2, 2011. A copy of the ’816
`
`patent is attached hereto as Ex. 5.
`
`15.
`
`The ’015 patent is entitled, “Vehicle Audio Application Management System
`
`Using Logic Circuitry.” The ’015 patent lawfully issued on July 4, 2017 and stems from U.S.
`
`Patent Application No. 13/253,284, which was filed on October 5, 2001. A copy of the ’015
`
`patent is attached hereto as Ex. 6.
`
`16.
`
`The ’292 patent is entitled, “System and method for restricting access to vehicle
`
`software systems.” The ’292 patent lawfully issued on November 12, 2013 and stems from U.S.
`
`Patent Application No. 12/775,991, which was filed on May 7, 2010. A copy of the ’292 patent
`
`is attached hereto as Ex. 7.
`
`17. MicroPairing is the owner of the patents-in-suit with all substantial rights,
`
`including the exclusive right to enforce, sue, and recover damages for past and future
`
`infringements.
`
`5
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 6 of 31
`
`18.
`
`The claims of the patents-in-suit are directed to patent eligible subject matter
`
`under 35 U.S.C. § 101. They are not directed to an abstract idea, and the technologies covered
`
`by the claims comprise vehicle systems and/or consist of ordered combinations of features and
`
`functions that, at the time of invention, were not, alone or in combination, well-understood,
`
`routine, or conventional.
`
`19.
`
`The specifications of the patents-in-suit disclose shortcomings in the prior art and
`
`then explain, in detail, the technical way the claimed inventions resolve or overcome those
`
`shortcomings. For example, the ’033 patent explains that while “[c]ars include many different
`
`electro-mechanical and electronic systems . . . the processors that control these different car
`
`systems do not talk to each other.” Ex. 1 at 1:5-21. “This means that each one of these car
`
`systems has to provide a separate standalone operating system. . . . [and] [m]any of these
`
`different car processors may be underutilized since they are only used intermittently.” Id. To
`
`solve this problem, the ’033 patent discloses an invention where:
`
`multiple processors each run an Open Communication system that controls how
`data is transferred between processors based on data content as opposed to the
`links that connect the processors together. The open communication system enables
`data or messages to be effectively transferred and processed for real-time
`applications or other server based applications that may be running on the multiple
`processors in a secure environment regardless of processors, locations, or data
`links.
`
`Id. at 1:54-64 (emphasis added).
`
`20.
`
`Such a solution is embodied, for example, in claim 1 of the ’033 patent:
`
`A method for communicating between different software applications in a same
`mobile vehicle, comprising:
`
`individual communication managers with
`associating
`applications in the mobile vehicle;
`
`
`individual software
`
`6
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 7 of 31
`
`receiving messages at the different individual software applications in the mobile
`vehicle and generating messages from the different individual software applications
`in the mobile vehicle;
`
`passing the received messages through the individual communication managers
`associated with different individual software applications receiving the messages
`before processing the messages with the different software applications receiving
`the messages in the mobile vehicle and passing the generated messages through
`the individual communication managers associated with the different individual
`software applications before sending the generated messages to other software
`the mobile vehicle,
`the communication managers each
`applications
`in
`independently attaching message labels to individual messages that individually
`identify different priority values for the individual messages; and
`
`performing different real-time mobile vehicle applications in the mobile vehicle
`according to the message labels.
`
`
`Id. at claim 1 (emphasis added). The differing priority values given to the respective message
`
`processed by given differing software applications thus allow all messages from all different
`
`systems to be processed according to data content based on the message priority. This invention
`
`thus creates an “open communication system [that] enables data or messages to be effectively
`
`transferred and processed for real-time applications or other server based applications that may
`
`be running on the multiple processors in a secure environment regardless of processors,
`
`locations, or data links.” Id. (emphasis added).
`
`21.
`
`The specification of the ’073 patent also discloses shortcomings in the prior art
`
`and then explains, in detail, the technical way the claimed inventions resolve or overcome those
`
`shortcomings. For example, the ’073 patent explains that car audio systems had a number of
`
`issues, including that (1) “[a]ny other portable audio sources brought into the car cannot use the
`
`car speakers or amplifier system;” (2) “in-dash audio devices or portable audio devices brought
`
`into the car [] can disrupt the attention of the car driver;” and (3) “[o]ther types of audio devices,
`
`such as cellular telephones, are difficult to operate and hear while driving in a car.” Ex. 2 at 1:5-
`
`28. To solve these problems, the ’073 patent discloses the following invention:
`
`7
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 8 of 31
`
`A vehicle audio system includes a wireless audio sensor configured to wirelessly
`detect different portable audio sources brought into the vehicle. Audio output
`devices are located in the vehicle for outputting audio signals from the different
`audio sources. A processor selectively connects the different audio sources to the
`different audio output devices.
`
`
`Id. at 2:31-36.
`
`
`22.
`
`The ’073 patent specification goes on to describe an “audio manager 14 [that]
`
`detects and communicates with the different wireless audio sources using any one of a variety of
`
`wireless communication protocols, such as Bluetooth or IEEE 802.11.” Id. at 2:39-42. This
`
`audio manager also “detect[s] different portable audio output devices and any audio output
`
`devices contained in the audio output device.” Id. at 2:53-60. The audio manager further
`
`“displays the different audio output devices on GUI 30.” Id. at 2:61-62. “The audio manager 14
`
`in block 42 monitors the area around and inside the vehicle 12 for any audio sources or audio
`
`output devices that may be transmitting a wireless signal. Any detected audio sources or audio
`
`output devices are displayed on the GUI 30 in block 44. The data manager in block 46 then
`
`determines what applications are associated with the different audio sources.” Id. at 3:25-36. To
`
`decide which applications to output to audio,
`
`The data manager 14 in block 50 identifies any priorities and security values
`associated with the identified audio applications. In block 52, the data manager 14
`identifies requests to output different ones of the audio sources to different ones of
`the audio output devices. The selected audio application may have a higher priority
`than the audio application that is currently connected to the selected audio output
`device. If the priority of the requesting audio application is the same or higher than
`the currently connected audio application, then the audio manager 14 in block 56
`replaces the audio application currently coupled to the audio output device with the
`selected audio application. If the requesting audio application has a lower priority
`than the audio application currently coupled to the audio output device, then the
`audio manager in block 54 will not connect the new audio application.
`
`
`Id. at 3:25-36.
`
`
`8
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 9 of 31
`
`23.
`
`Solutions to the problems outlined in the ’073 patent are, for example, embodied
`
`in claim 10:
`
`A vehicle audio system, comprising:
`
` a
`
` wireless audio sensor configured to wirelessly detect different audio sources
`brought into or next to a vehicle;
`
`wireless audio output devices for outputting audio data having assigned priority
`values; and
`
` a
`
` processor for selectively connecting the different audio sources to the audio
`output devices according to the assigned priority values for the audio data.
`
`
`Id. at claim 10. The wireless audio sources are connected selectively to differing audio output
`
`devices according to the assigned priority values for the audio data. A wireless audio sensor
`
`detects the different sources brought into the vehicle, and a processor connects these sources to
`
`the output devices. This claim solves the issues of (1) other portable audio sources not being
`
`able to use the car speakers; (2) audio devices potentially distracting the driver; and (3) other
`
`types of audio devices being difficult to hear and operate while driving a car.
`
`24.
`
`The specification of the ’136 patent also discloses shortcomings in the prior art
`
`and then explains, in detail, the technical way the claimed inventions resolve or overcome those
`
`shortcomings. The specification of the ’136 patent discusses Java virtual machines (JVMs),
`
`which make “it possible for Java application programs to be built that can run on any platform
`
`without having to be rewritten or recompiled by the programmer for each separate platform.”
`
`Ex. 3 at 1:27-34. The specification also describes the Jini system, which “extends the Java
`
`application environment from a single virtual machine to a network of machines. . . . The Jini
`
`infrastructure provides mechanisms for devices, services, and users to join and detach from a
`
`network. Jini systems are more dynamic than is currently possible in networked groups where
`
`configuring a network is a centralized function done by hand.” Id. at 1:34-47.
`
`9
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 10 of 31
`
`25.
`
`“However, the Java/Jini approach is not without its disadvantages. Both Java and
`
`Jini are free, open source applications. The Java application environment is not designed for
`
`controlling messaging between different machines.” Id. at 1:48-58. “For example, the Java
`
`application is not concerned about the protocols between different hardware platforms. Jini has
`
`some built-in security that allows code to be downloaded and run from different machines in
`
`confidence. However, this limited security is insufficient for environments where it is necessary
`
`to further restrict code sharing or operation sharing among selected devices in a secure embedded
`
`system.” Id.
`
`26.
`
`To solve these problems, the ’136 patent proposes a “Secure Real-time Executive
`
`(SRE) 14 [which] provides an extension to the JVM 16 and allows Java to run on different
`
`processors for real-time applications. The SRE 20 manages messaging, security, critical data,
`
`file I/O multiprocessor task control and watchdog tasks in the Java environment as described
`
`below.” Id. at 2:35-43. “For example, the SRE 14 may prevent noncritical vehicle applications,
`
`such as audio control, from being loaded onto processor 16.” Id. at 2:66-3:6.
`
`27.
`
`The advantages of the invention of the ’136 patent are taught as follows:
`
`The SRE 14 allows any variety of real-time, mission critical, nonreal-time and
`nonmission critical Java applications to be loaded onto the multiprocessor system
`15. The SRE 14 then automatically manages the different types of applications and
`messages to ensure that the critical vehicle applications are not corrupted and
`processed with the necessary priority. The SRE 14 is secure software that cannot
`be manipulated by other Java applications.
`
`The SRE 14 provides priority preemption on a message scale across the entire
`system 15 and priority preemption on a task scale across the entire system 15. So
`the SRE 14 controls how the JVMs 10 talk to each other and controls how the JVMs
`10 are started or initiated to perform tasks. The SRE 14 allows programmers to
`write applications using Java in a safe and secure real time environment. Thus,
`viruses can be prevented by SRE 14 from infiltrating the system 15.
`
`Id. at 3:15-30.
`
`
`10
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 11 of 31
`
`28.
`
`An important aspect of the invention of the ’136 patent is the message manager:
`
`The message manager 50 determines the priority of sent and received messages. If
`the data transmitted and received by the sensor fusion thread 76 is higher priority
`than other data transmitted and received on the processor 84, then the sensor fusion
`data will be given priority over the other data. The task manager 58 controls the
`priority that the sensor fusion thread 76 is giving by processor 84. If the sensor
`fusion thread 76 has higher priority than, for example, an audio application that is
`also being run by processor 84, then the sensor fusion thread 76 will be performed
`before the audio application.
`
`Id. at 4:60-5:3.
`
`29.
`
`Solutions to the problems outlined by the ’136 patent are embodied in, for example,
`
`claim 31:
`
`An apparatus, comprising:
`
` a
`
` multiprocessor system configured to:
`
`
`identify a new device that is not currently coupled to the multiprocessor system;
`
`detect a communication protocol used by the new device and connect the new
`device to the multiprocessor system when signaling from the new device conforms
`to a communication protocol used in the multiprocessor system;
`
`configure the new device into the multiprocessor system when a data protocol
`operated by the new device conforms with a data protocol used in the
`multiprocessor system;
`
`display an image representing the new device on a graphical interface;
`
`identify data codes in the signaling from the new device identifying an application
`running on the new device, a data type used on the new device, and a security level
`associated with data stored in the new device;
`
`use the identified security level to prevent unauthorized data from being loaded into
`the multiprocessor system;
`
`identify a stored application in memory in the multiprocessor system that uses the
`same data type used on the new device and download the stored application from
`memory into a processor in the multiprocessor system;
`
`display an image on the graphical user interface representing the stored application
`loaded into the processor in the multiprocessor system; and
`
`11
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 12 of 31
`
`
`use the stored application to direct data exchanged with the portable device to a
`selectable output or a selectable input identified on the graphical interface.
`
`
`Id. at claim 31.
`
`
`30.
`
`The specification of the ’383 patent also discloses shortcomings in the prior art
`
`and then explains, in detail, the technical way the claimed inventions resolve or overcome those
`
`shortcomings. The specification of the ’383 patent explains, for instance, that “[c]ars include
`
`many different electro-mechanical and electronic systems … the processors that control these
`
`different car systems do not talk to each other.” Ex. 4 at 2:55-3:3. “This means that each one of
`
`these car systems has to provide a separate standalone operating system … [and] [m]any of these
`
`different car processors may be underutilized since they are only used intermittently.” Id. To
`
`solve this problem, the ’383 patent discloses an invention comprising:
`
`A multiprocessor system used in a car, home, or office environment includes
`multiple processors that run different real-time applications. A dynamic
`configuration system runs on the multiple processors and includes a device
`manager, configuration manager, and data manager. The device manager
`automatically detects and adds new devices to the multiprocessor system, and the
`configuration manager automatically reconfigures which processors run the real-
`time applications. The data manager identifies the type of data generated by the
`new devices and identifies which devices in the multiprocessor system are able to
`process the data.
`
` A
`
` communication system for a mobile vehicle, home, or office environment
`includes multiple processors. The multiple processors each run an Open
`Communication system that controls how data is transferred between processors
`based on data content as opposed to the links that connect the processors together.
`The open communication system enables data or messages to be effectively
`transferred and processed for real-time applications or other server based
`applications that may be running on the multiple processors in a secure environment
`regardless of processors, locations, or data links.
`
`31.
`
`Such a solution is embodied, for example, in claim 1 of the ’383 patent:
`
`A distributed vehicle control system, comprising:
`
`12
`
`
`
`Id. at 4:13-34.
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 13 of 31
`
`
`multiple processors in a distributed multi-processor system;
`
` a
`
` secure real-time executive (SRE) operating in the distributed multi-processor
`system, wherein the SRE operates on each processor independently and wherein
`each independently operating SRE comprises a message manager associated with
`an application running on each of the processors and configured to associate
`priority values with messages transmitted by the applications and to control the
`processing sequence of messages received by applications according to a
`predetermined priority scheme;
`
` a
`
` first processor in the distributed processing system running a first application,
`wherein the first processor receives a first message from the first application and
`associates a first priority value with the first message;
`
` a
`
` second processor in the distributed processing system running a second
`application, wherein the SRE running on the second processor receives a second
`message from the second application and associates a second priority value with
`the second message;
`
` a
`
` third processor in the distributed processing system running a third application,
`wherein the SRE running on the third processor receives the first message and
`associated first priority from the first processor and receives the second message
`and associated second priority from the second processor and responsive to
`receiving the priority associated messages, determines the sequence in which the
`third application handles the priority associated messages using the predetermined
`priority scheme.
`
`Id. at claim 1.
`
`32.
`
`The specification of the ’816 patent also discloses shortcomings in the prior art
`
`and then explains, in detail, the technical way the claimed inventions resolve or overcome those
`
`shortcomings. The specification of the ’816 patent discusses how “[c]ars include many different
`
`electro-mechanical and electronic applications. . . . [But] [g]enerally the processors that control
`
`these different car systems do not talk to each other.” Ex. 5 at 1:17-32. “For example, separate
`
`processors and separate user interfaces are required for the car temperature control system and
`
`for the car audio system. Many of these different car processors may be underutilized since they
`
`are only used intermittently.” Id. And “[e]ven when multiple processors in the car do talk to
`
`13
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 14 of 31
`
`each other, they are usually so tightly coupled together that it is impossible to change any one of
`
`these processors without disrupting all of the systems that are linked together.” Id. at 1:33-41.
`
`Furthermore, “[i]ntegration of new systems into a car is also limited. Car systems are designed
`
`and selected well before the car ever built. . . . Because after market devices cannot be integrated
`
`into car control and interface systems, it is often difficult for the driver to try and operate these
`
`after market devices.” Id. at 1:42-49.
`
`33.
`
`To solve these problems, the ’816 patent teaches:
`
`A multiprocessor system used in a car, home, or office environment includes
`multiple processors that run different real-time applications. A dynamic
`configuration system runs on the multiple processors and includes a device
`manager, configuration manager, and data manager. The device manager
`automatically detects and adds new devices to the multiprocessor system, and the
`configuration manager automatically reconfigures which processors run the real-
`time applications. The data manager identifies the type of data generated by the
`new devices and identifies which devices in the multiprocessor system are able to
`process the data.
`
`
`Id. at 1:65-2:8.
`
`
`34.
`
`The specification of the ’816 patent describes an embodiment of the invention as
`
`follows:
`
`FIGS. 5 and 6 show how a new device is added to the multiprocessor system 8.
`Each of the existing processors A, B, C, and D after power-up are configured to
`identify a set or subset of the processors in the multiprocessor system 8. A new
`device 72 is brought into the multiprocessor system 8 either via a hardwired link or
`a wireless link. For example, the device E may send out signals over any one or
`more of a 802.11 wireless link 67, Blue tooth wireless link 71 or send out signals
`over a hardwired Ethernet link 69. Depending on what communication protocol is
`used to send signals, one or more of the processors A, B, C or D using a similar
`communication protocol detect the processor E in block 74 (FIG. 6). All of the
`processors may be connected to the same fiber optic or packet switched network
`that is then used to communicate the information from processor E to the other
`processors.
`
`One of the device managers 46 in the multiprocessor system 8 checks the signals
`from processor E checks to determine if the signals are encrypted in a recognizable
`protocol in block 76. The device manager in the processor receiving the signals
`
`14
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 15 of 31
`
`from processor E then checks for any data codes from the new device signals in
`block 76. The data codes identify data types used in one or more applications by
`processor E. A device ID for processor E is then determined from the output signals
`in block 80.
`
`If all these data parameters are verified, the device managers 46 in one or more of
`the processors A, B, C and D add the new processor E to their processor arrays in
`block 82. For example, processor A adds processor E to the processor array in
`memory 65. After being incorporated into the multiprocessor system 8, the
`processor E or the applications running on the processor E may be displayed on a
`graphical user interface in block 84.
`
`
`Id. at 4:51-5:7.
`
`
`35.
`
`Solutions to the problems outlined by the ’816 patent are embodied, for example,
`
`in claim 1:
`
`A method of operating a vehicle audio system having a wired audio source, a
`display, multiple speakers and a logic circuit configured to:
`
`sense the availability of a wireless audio device that is located within or proximate
`to the vehicle;
`
`identify a wireless audio device record from among a plurality of different wireless
`audio device records previously identified and stored in memory, wherein the
`wireless device record includes previously identified data codes from the wireless
`audio device and from a first software application running on the wireless audio
`device;
`
`responsive to identifying the data codes and first software application running on
`the wireless audio device from the stored record, download a copy of a second
`software application selected from the memory and process data from the wireless
`audio device with the second software application;
`
`provide a user with an option to direct sound from the wireless audio device through
`at least a first one of the speakers of the vehicle audio system or back to a speaker
`in the wireless audio device.
`
`
`Id. at claim 1.
`
`
`36.
`
`The specification of the ’015 patent also discloses shortcomings in the prior art
`
`and then explains, in detail, the technical way the claimed inventions resolve or overcome those
`
`15
`
`
`

`

`Case 6:20-cv-01001-ADA Document 1 Filed 10/28/20 Page 16 of 31
`
`shortcomings. The ’015 patent identifies the same problems as the ’816 patent specification.
`
`See Ex. 6 at 2:56-3:31.
`
`37.
`
`To solve these problems, the ’015 patent teaches:
`
`A multiprocessor system used in a car, home, or office environment includes
`multiple processors that run different real-time applications. A dynamic
`configuration system runs on the multiple processors and includes a device
`manager, configuration manager, and data manager. The device manager
`automatically detects and adds new devices to the multiprocessor system, and the
`configuration manager automatically reconfigures which processors run the real-
`time applications. The data manager identifies the type of data generated by the
`new devices and identifies which devices in the multiprocessor system are able to
`process the data.
`
`
`Ex. 6 at 4:14-26.
`
`
`38.
`
`The specificatio

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