IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`MISCELLANEOUS LETTER
`
`REGARDING PAYMENT OF FEES AND EXTENSION OF TIME
`
`x Applicant petitions the Commissioner to extend the time for response (if
`
`applicable).
`
`Applicant requests that any deficiency or overpayment be charged or credited to
`deposit account number 13-1703.
`
`Customer No. 20575
`
`MARGER JOHNSON & McCOLLOM, P.C.
`
`Respectfully submitted,
`
`Stephen S. Ford
`Reg. No. 35,139
`
`MARGER JOHNSON & McCOLLOM, P.C.
`210 SW Morrison Street, Suite 400
`Portland, OR 97204
`(503) 222-3613
`
`AHM, Exh. 1031, p. 1
`
`

`

`PTO/SB/14 (08-05)
`Approved for use through 07/31/2006. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`9032-34
`
`Application Number
`
`Title of Invention
`
`METHOD AND APPARATUS FOR DYNAMIC CONFIGURATION OF MULTIPROCESSOR SYSTEM
`
`The application data sheet is part of the provisional or nonprovisional application for which it is being submitted. The following form contains the
`bibliographic data arranged in a format specified by the United States Patent and Trademark Office as outlined in 37 CFR 1.76.
`This document may be completed electronically and submitted to the Office in electronic format using the Electronic Filing System (EFS) or the
`document may be printed and included in a paper filed application.
`
`Secrecy Order 37 CFR 5.2
`Portions or all of the application associated with this Application Data Sheet may fall under a Secrecy Order pursuant to
`37 CFR 5.2 (Paper filers only. Applications that fall under Secrecy Order may not be filed electronically.)
`
`Applicant Information:
`Applicant 1
`Applicant Authority ®Inventor
`Prefix Given Name
`
`Legal Representative under 35 U.S.C. 117
`
`Middle Name
`
`°Party of Interest under 35 U.S.C. 118
`I
`Family Name
`
`Suffix
`
`Remove
`
`Preston
`Alan
`Dan
`Residence Information (Select One) ® US Residency O Non US Residency O Active US Military Service
`City
`State/Province WA
`Country of Residence i US
`Bainbridge Island
`
`Citizenship under 37 CFR 1.41(b) i
`Mailing Address of Applicant:
`Address 1
`11621 Meadowmeer Circle, NE
`Address 2
`
`US
`
`City
`
`Bainbridge Island
`
`Postal Code
`
`98110
`
`State/Province
`
`WA
`
`Countryi US
`
`Applicant 2
`Applicant Authority C)Inventor °Legal Representative under 35 U.S.C. 117
`°Party of Interest under 35 U.S.C. 118
`I
`Prefix Given Name
`Middle Name
`Family Name
`
`Suffix
`
`Remove
`
`Lutter
`Pierce
`Robert
`Residence Information (Select One) ® US Residency O Non US Residency O Active US Military Service
`City
`State/Province WA
`Country of Residence i US
`Tacoma
`
`Citizenship under 37 CFR 1.41(b) i
`Mailing Address of Applicant:
`Address 1
`2809 North 32nd Street
`Address 2
`
`US
`
`City
`
`Tacoma
`
`State/Province
`
`WA
`
`Postal Code
`
`98407
`All Inventors Must Be Listed - Additional Inventor Information blocks may be
`within this form by selecting the Add button. generated
`
`
`Countryi WA
`
`Add
`
`Correspondence Information:
`Enter either Customer Number or complete the Correspondence Information section below.
`For further information see 37 CFR 1.33(a).
`
`An Address is being provided for the correspondence Information of this application.
`
`EFS Web 1.0
`
`AHM, Exh. 1031, p. 2
`
`

`

`PTO/SB/14 (08-05)
`Approved for use through 07/31/2006. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`9032-34
`
`Application Number
`
`Title of Invention
`
`METHOD AND APPARATUS FOR DYNAMIC CONFIGURATION OF MULTIPROCESSOR SYSTEM
`
`Customer Number
`
`20575
`
`Email Address
`
`docketing@techlaw.com
`
`Application Information:
`
`Title of the Invention
`
`METHOD AND APPARATUS FOR DYNAMIC CONFIGURATION
`QVCTCRA
`Attorney Docket Number 9032-34
`
`Add Email
`
`Remove Email
`
`OF MULTIPROCESSOR
`
`n
`
`Small Entity Status Claimed
`
`j
`
`Application Type
`
`Nonprovisional
`
`Subject Matter
`
`Utility
`
`Suggested Class (if any)
`
`Suggested Technology Center (if any)
`
`Sub Class (if any)
`
`Total Number of Drawing Sheets (if any)
`
`12
`
`Suggested Figure for Publication (if any)
`
`Publication Information:
`
`Request Early Publication (Fee required at time of Request 37 CFR 1.219)
`Request Not to Publish. I hereby request that the attached application not be published under 35 U.S.C. 122(b)
`and certify that the invention disclosed in the attached application has not been and will not be the subject of an
`application filed in another country, or under a multilateral agreement, that requires publication at eighteen months
`after filing.
`
`Representative Information:
`
`Representative information should be provided for all practitioners having a power of attorney in the application. Providing
`this information in the Application Data Sheet does not constitute a power of attorney in the application (see 37 CFR 1.32).
`Enter either Customer Number or
`complete
`the Representative Name
`section below.
`If both
`are completed the Customer Number will be used for the Representative Information during processing.
`
`sections
`
`Please Select One:
`
`Customer Number
`
`O US Patent Practitioner
`
`O US Representative (37 CFR 11.9)
`
`Customer Number
`
`20575
`
`Domestic Priority Information:
`This section allows for the applicant to claim benefit under 35 U.S.C. 119(e), 120, 121, or 365(c). Providing this information in the
`application data sheet constitutes the specific reference required by 35 U.S.C. 119(e) or 120, and 37 CFR 1.78(a)(2) or CFR 1.78(a)
`(4), and need not otherwise be made part of the specification.
`
`Prior Application Status
`
`Remove
`
`Application Number
`
`Continuity Type
`
`Prior Application Number
`
`Filing Date (YYYY-MM-DD)
`
`Continuation of
`
`09841915
`
`2001-04-24
`
`Additional Domestic Priority Data may be generated within this form by selecting
`the Add button.
`
`Add
`
`Foreign Priority Information:
`
`EFS Web 1.0
`
`AHM, Exh. 1031, p. 3
`
`

`

`PTO/SB/14 (08-05)
`Approved for use through 07/31/2006. OMB 0651-0032
`U.S. Patent and Trademark Office; U.S. DEPARTMENT OF COMMERCE
`Under the Paperwork Reduction Act of 1995, no persons are required to respond to a collection of information unless it contains a valid OMB control number.
`
`Application Data Sheet 37 CFR 1.76
`
`Attorney Docket Number
`
`9032-34
`
`Application Number
`
`Title of Invention
`
`METHOD AND APPARATUS FOR DYNAMIC CONFIGURATION OF MULTIPROCESSOR SYSTEM
`
`This section allows for the applicant to claim benefit of foreign priority and to identify any prior foreign application for which priority is
`not claimed. Providing this information in the application data sheet constitutes the claim for priority as required by 35 U.S.C. 119(b)
`and 37 CFR 1.55(a).
`
`Remove
`
`Application Number
`
`Country I
`
`Parent Filing Date (YYYY-MM-DD)
`
`Priority Claimed
`
`0 Yes O No
`
`Additional Foreign Priority Data may be generated within this form by selecting the
`Add button.
`Assignee Information:
`Providing this information in the application data sheet does not substitute for compliance with any requirement of part 3 of Title 37
`of the CFR to have an assignment recorded in the Office.
`
`Add
`
`Assignee 1
`If the Assignee is an Organization check here.
`
`1
`
`Organization Name
`
`Medius, Inc.
`
`Mailing Address Information:
`
`Remove
`
`Address 1
`
`Address 2
`
`City
`
`Country i US
`
`Phone Number
`
`Email Address
`
`945 Hildebrand Lane NE
`
`Suite 230
`
`Bainbridge Island
`
`State/Province
`
`WA
`
`5032223613
`
`dockefing@techlaw.com
`
`Postal Code
`
`Fax Number
`
`98110
`
`5032744622
`
`Additional Assignee Data may be generated within this form by selecting the Add
`button.
`
`Add
`
`Signature:
`A signature of the applicant or representative is required in accordance with 37 CFR 1.33 and 10.18. Please see 37
`CFR 1.4(d) for the form of the signature.
`
`Signature
`
`/Stephen S. Ford/
`
`Date (YYYY-MM-DD) 2006-08-07
`
`First Name
`
`Stephen
`
`Last Name
`
`Ford
`
`Registration Number
`
`35139
`
`This collection of information is required by 37 CFR 1.76. The information is required to obtain or retain a benefit by the public which
`is to file (and by the USPTO to process) an application. Confidentiality is governed by 35 U.S.C. 122 and 37 CFR 1.14. This
`collection is estimated to take 23 minutes to complete, including gathering, preparing, and submitting the completed application data
`sheet form to the USPTO. Time will vary depending upon the individual case. Any comments on the amount of time you require to
`complete this form and/or suggestions for reducing this burden, should be sent to the Chief Information Officer, U.S. Patent and
`Trademark Office, U.S. Department of Commerce, P.O. Box 1450, Alexandria, VA 22313-1450. DO NOT SEND FEES OR
`COMPLETED FORMS TO THIS ADDRESS. SEND TO: Commissioner for Patents, P.O. Box 1450, Alexandria, VA 22313-1450.
`
`EFS Web 1.0
`
`AHM, Exh. 1031, p. 4
`
`

`

`Privacy Act Statement
`
`The Privacy Act of 1974 (P.L. 93-579) requires that you be given certain information in connection with your submission of the attached form related to
`a patent application or patent. Accordingly, pursuant to the requirements of the Act, please be advised that: (1) the general authority for the collection
`of this information is 35 U.S.C. 2(b)(2); (2) furnishing of the information solicited is voluntary; and (3) the principal purpose for which the information is
`used by the U.S. Patent and Trademark Office is to process and/or examine your submission related to a patent application or patent. If you do not
`furnish the requested information, the U.S. Patent and Trademark Office may not be able to process and/or examine your submission, which may
`result in termination of proceedings or abandonment of the application or expiration of the patent.
`
`The information provided by you in this form will be subject to the following routine uses:
`
`1
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`8.
`
`The information on this form will be treated confidentially to the extent allowed under the Freedom of Information Act (5 U.S.C. 552)
`and the Privacy Act (5 U.S.C. 552a). Records from this system of records may be disclosed to the Department of Justice to determine
`whether the Freedom of Information Act requires disclosure of these records.
`
`A record from this system of records may be disclosed, as a routine use, in the course of presenting evidence to a court, magistrate, or
`administrative tribunal, including disclosures to opposing counsel in the course of settlement negotiations.
`
`A record in this system of records may be disclosed, as a routine use, to a Member of Congress submitting a request involving an
`individual, to whom the record pertains, when the individual has requested assistance from the Member with respect to the subject matter of
`the record.
`
`A record in this system of records may be disclosed, as a routine use, to a contractor of the Agency having need for the information in
`order to perform a contract. Recipients of information shall be required to comply with the requirements of the Privacy Act of 1974, as
`amended, pursuant to 5 U.S.C. 552a(m).
`
`A record related to an International Application filed under the Patent Cooperation Treaty in this system of records may be disclosed,
`as a routine use, to the International Bureau of the World Intellectual Property Organization, pursuant to the Patent Cooperation Treaty.
`
`A record in this system of records may be disclosed, as a routine use, to another federal agency for purposes of National Security
`review (35 U.S.C. 181) and for review pursuant to the Atomic Energy Act (42 U.S.C. 218(c)).
`
`A record from this system of records may be disclosed, as a routine use, to the Administrator, General Services, or his/her designee,
`during an inspection of records conducted by GSA as part of that agency's responsibility to recommend improvements in records
`management practices and programs, under authority of 44 U.S.C. 2904 and 2906. Such disclosure shall be made in accordance with the
`GSA regulations governing inspection of records for this purpose, and any other relevant (i.e., GSA or Commerce) directive. Such
`disclosure shall not be used to make determinations about individuals.
`
`A record from this system of records may be disclosed, as a routine use, to the public after either publication of the application pursuant
`to 35 U.S.C. 122(b) or issuance of a patent pursuant to 35 U.S.C. 151. Further, a record may be disclosed, subject to the limitations of 37
`CFR 1.14, as a routine use, to the public if the record was filed in an application which became abandoned or in which the proceedings were
`terminated and which application is referenced by either a published application, an application open to public inspections or an issued
`patent.
`
`9.
`
`A record from this system of records may be disclosed, as a routine use, to a Federal, State, or local law enforcement agency, if the
`USPTO becomes aware of a violation or potential violation of law or regulation.
`
`EFS Web 1.0
`
`AHM, Exh. 1031, p. 5
`
`

`

`PATENT APPLICATION
`Attorney Docket No. 9032-34
`
`METHOD AND APPARATUS FOR DYNAMIC
`CONFIGURATION OF MULTIPROCESSOR SYSTEM
`
`This application is a continuation of U.S. Patent Application Serial No. 09/841,915,
`
`filed April 24, 2001, now U.S. Patent No.
`
` , the disclosure of which is
`
`incorporated herein by reference in its entirety.
`
`BACKGROUND
`
`Cars include many different electro-mechanical and electronic applications.
`
`Examples include braking systems, electronic security systems, radios, Compact Disc (CD)
`
`players, internal and external lighting systems, temperature control systems, locking systems,
`
`seat adjustment systems, speed control systems, mirror adjustment systems, directional
`
`indicators, etc. Generally the processors that control these different car systems do not talk to
`
`each other. For example, the car radio does not communicate with the car heating system or
`
`the car braking system. This means that each one of these car systems operate independently
`
`and do not talk to the other car systems. 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.
`
`Even when multiple processors in the car do talk to 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 arc linked together. For example, some cars may have a
`
`dashboard interface that controls both internal car temperature and a car radio. The car radio
`
`cannot be replaced with a different model and still work with the dashboard interface and the
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`AHM, Exh. 1031, p. 6
`
`

`

`ear temperature controller.
`
`Integration of new systems into a car is also limited. Car systems are designed and
`
`selected well before the car is ever built. A custom wiring harness is then designed to
`
`connect only those car systems selected for the car. A car owner cannot incorporate new
`
`systems into the existing car. For example, a car may not originally come with a navigation
`
`system. An after market navigation system from another manufacturer cannot be integrated
`
`into the existing car.
`
`Because after market devices can not be integrated into car control and interface
`
`systems, it is often difficult for the driver to try and operate these after market devices. For
`
`example, the car driver has to operate the after market navigation system from a completely
`
`new interface, such as the keyboard and screen of a laptop computer. The driver then has to
`
`operate the laptop computer not from the front dashboard of the car, but from the passenger
`
`seat of the car. This makes many after market devices both difficult and dangerous to operate
`
`while driving.
`
`The present invention addresses this and other problems associated with the prior art.
`
`SUMMARY OF THE INVENTION
`
`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.
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`2
`
`AHM, Exh. 1031, p. 7
`
`

`

`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a diagram of a car that has multiple processors that each run a Dynamic
`
`Configuration (DC) system.
`
`FIG. 2 is a detailed diagram of the dynamic configuration system shown in FIG. 1.
`
`FIGS. 3 and 4 are diagrams showing an example of how the DC system operates.
`
`FIGS. 5 and 6 are diagrams showing how a device manager in the DC system
`
`operates.
`
`FIGS. 7-10 are diagrams showing how a reconfiguration manager in the DC system
`
`operates.
`
`FIGS. 11 and 12 are diagrams showing how a data manager in the DC system
`
`operates.
`
`FIG. 13 is a diagram showing different multiprocessor systems that can use the DC
`
`DC system.
`
`DETAILED DESCRIPTION
`
`FIG. 1 shows a car 12 that includes a car multiprocessor system 8 having multiple
`
`processors 14, 16, 18 and 20. An engine monitor processor 14 monitors data from different
`
`sensors 22 and 24 in the car engine. The sensors 22 and 24 can be any sensing device such as
`
`sensors that monitor water temperature, oil temperature, fuel consumption, car speed, etc. A
`
`brake control processor 20 monitors and controls an Automatic Braking System (ABS) 28. A
`
`display processor 16 is used to control and monitor a graphical user interface 26. A security
`
`processor 18 monitors and controls latches and sensors 30 and 32 that are used in a car
`
`security system.
`
`The processors 14, 16, 18 and 20 all include software that run a Dynamic
`
`Configuration (DC) system 10 that enables new processors or devices to be automatically
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`3
`
`AHM, Exh. 1031, p. 8
`
`

`

`added and removed from the car multiprocessor system 8. The DC system 10 also
`
`automatically reconfigures the applications running on different processors according to
`
`application failures and other system processing requirements.
`
`For example, the processor 20 may currently be running a high priority brake control
`
`application. If the processor 20 fails, the DC system 10 can automatically download the
`
`braking application to another processor in car 12. The DC system 10 automatically
`
`identifies another processor with capacity to run the braking control application currently
`
`running in processor 20. The DC system 10 then automatically downloads a copy of the
`
`braking control application to the identified processor. If there is no extra reserve processing
`
`resources available, the DC system 10 may replace a non-critical application running on
`
`another processor. For example, the DC system 10 may cause the display processor 16 to
`
`terminate a current non-critical application and then download the brake control application
`
`along with any stored critical data.
`
`The DC system 10 also automatically incorporates new processors or applications into
`
`the multiprocessor system 8. For example, a laptop computer 38 can communicate with the
`
`engine monitor processor 34 through a hardwired link 34 or communicate to the display
`
`processor 16 through a wireless link 36. The DC system 10 automatically integrates the
`
`laptop computer 38, or any other processor or device, into the multiprocessor system 8. After
`
`integrated into the multiprocessor system 8, not only can the laptop computer 38 transfer data
`
`with other processors, but the laptop computer may also run car applications normally run by
`
`other processors in car 12.
`
`The DC system 10 allows the car driver to manage how different applications are
`
`processed in the car 12. As described above, a car operator may have to run an aftermarket
`
`navigation system through a GPS transceiver attached to the laptop computer 38. The car
`
`driver has to place the laptop computer 38 in the passengers seat and then operate the laptop
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`4
`
`AHM, Exh. 1031, p. 9
`
`

`

`computer 38 while driving.
`
`The DC system 10 in the display computer 16 can automatically detect the navigation
`
`application running on the laptop computer 38. The display computer 16 notifies the car
`
`operator through the user interface 26 that the navigation application has been detected. The
`
`car operator can then control the navigation application through the user interface 26. Since
`
`the user interface 26 is located in the dashboard of car 12, the car operator no longer has to
`
`take his eyes off the road while operating the navigation application.
`
`The description below gives only a few examples of the different processors, devices
`
`and applications that can be implemented using the DC system 10. Any single or
`
`multiprocessor system located either inside or outside of car 12 can communicate and
`
`exchange data using the OC system 10. It should also be understood that the DC system 10
`
`can be used in any real-time environment such as between processors in different home or
`
`office appliances and different home and office computers.
`
`FIG. 2 is a block diagram showing in more detail the Dynamic Control (DC) system
`
`10 located in a processor 40 that makes up part of the multiprocessor system 8 in car 12 (FIG.
`
`1). The DC system 10 includes a device manager 46 that establishes communications with
`
`new devices that are to be incorporated into the multiprocessor system 8. A configuration
`
`manager 44 in the processor 40 dynamically moves applications between different processors
`
`according to user inputs and other monitored conditions in the multiprocessor system 8. A
`
`data manager 42 identifies a type of data input or output by a new processor and identifies
`
`other processors or devices in the multiprocessor system that can output data from the new
`
`device or input data to the new device.
`
`In one example, sensors 52 feed sensor data to processor 40. The sensor data may
`
`include engine-monitoring data such as speed, oil temperature, water temperature,
`
`temperature inside the car cab, door open/shut conditions, etc. The sensors 52 are coupled to
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`5
`
`AHM, Exh. 1031, p. 10
`
`

`

`processor 40 through a link 54, such as a proprietary bus. A Compact Disc (CD) player 50 is
`
`coupled to the processor 40 through another link 48, such as a Universal Serial Bus (USB).
`
`Graphical User Interface (GUI) 56 displays the data associated with sensors 52 and CD
`
`player 50. The GUI 56 displays the outputs from sensors 52 using an icon 60 to identify
`
`temperature data and an icon 62 to identify car speed. The processor displays the CD player
`
`50 as icon 62.
`
`FIGS. 3 and 4 show an example of how two new applications are dynamically added
`
`to the multiprocessor system 8 in car 12 (FIG. 1). In FIG. 2, the DC system 10 in processor
`
`40 previously detected a CD player 50 and some sensors 56. The CD player 50 was
`
`displayed on GUI 56 as icon 58 and the temperature and speed data from sensors 56 were
`
`displayed on GUI 56 as icons 60 and 62, respectfully.
`
`The processor 40 is located in car 12 (FIG. 1). A passenger may bring a Digital
`
`Video Disc (DVD) player 86 into the car 12. The DVD 86 sends out a wireless or wired
`
`signal 88 to the processor 40. For example, the DVD 86 may send out signals using a IEEE
`
`802.11 wireless protocol. The processor 40 includes an IEEE 802.11 interface that reads the
`
`signals 88 from DVD player 86. If the 802.11 protocol is identified as one of the protocols
`
`used by processor 40, the DC system 10 incorporates the DVD player 86 into a processor
`
`array 57 that lists different recognized applications.
`
`The DC system 10 then automatically displays the newly detected DVD player 86 on
`
`GUI 56 as icon 96. If capable, the car operator by selecting the icon 96 can then display a
`
`video stream output from the DVD player 86 over GUI 56. The DVD player 86 can now be
`
`controlled from the GUI 56 on the car dashboard. This prevents the car driver from having to
`
`divert his eyes from the road while trying to operate the portable DVD player 86 from
`
`another location in the car, such as from the passenger seat.
`
`Other processors or devices can also be incorporated into the multiprocessor system 8
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`6
`
`AHM, Exh. 1031, p. 11
`
`

`

`in car 12. In another example, the car 12 drives up to a drive-in restaurant 90. The drive-in
`
`90 includes a transmitter 92 that sends out a wireless Blue tooth signal 94. The processor 40
`
`includes a Blue tooth transceiver that allows communication with transmitter 92. The DC
`
`system 10 recognizes the signals 94 from transmitter 92 and then incorporates the drive-in 90
`
`into the multiprocessor system 8 (FIG. 1). The DC system 10 then displays the drive-in 90 as
`
`icon 98 in GUI 56.
`
`Referring to FIG. 4, when the car operator selects the icon 98, a menu 102 for the
`
`driver-in 90 is displayed on the GUI 56. The car operator can then select any of the items
`
`displayed on the electronic menu 102. The selections made by the car operator are sent back
`
`to the transceiver 92 (FIG. 3). The amount of the order is calculated and sent back to the
`
`processor 40 and displayed on menu 102. Other messages, such as a direction for the car
`
`operator to move to the next window and pickup the order can also be displayed on the GUI
`
`56. At the same time, the drive-in transceiver 92 (FIG. 3) may send audio signals that are
`
`received by the processor 40 and played out over speakers in car 12.
`
`FIG. 5 shows in more detail the operation of the device manager 46 previously shown
`
`in FIG. 2. Multiple processors A, B, C and D all include device managers 46. The device
`
`managers 46 can each identify other devices in the multiprocessor system that it
`
`communicates with. For example, processors A, B, C and D communicate to each other over
`
`one or more communication links including a Ethernet link 64, a wireless 802.11 link 68, or a
`
`blue tooth link 70.
`
`Processor A includes a memory 65 that stores the other recognized processors B, C
`
`and D. The data managers 46 also identify any applications that may be running on the
`
`identified processors. For example, memory 65 for processor A identifies an application #2
`
`running on processor B, no applications running on processor C, and an application #4
`
`running on processor D.
`
`Patent Application
`Atty. Doc. No, 9032-34
`
`7
`
`AHM, Exh. 1031, p. 12
`
`

`

`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 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.
`
`FIG. 7 describes in further detail the operation of the reconfiguration manager 44
`
`previously described in FIG. 2. In the car multiprocessor system 8 there are four processors
`
`A, B, C and D. Of course there may be more than four processors running at the same time
`
`in the car but only four are shown in FIG. 7 for illustrative purposes. The processor A
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`8
`
`AHM, Exh. 1031, p. 13
`
`

`

`currently is operating a navigation application 110 that uses a Global Positioning System
`
`(GPS) to identify car location. Processor B currently runs an audio application 112 that
`
`controls a car radio and CD player. The processor C runs a car Automatic Braking System
`
`(ABS) application 114 and the processor D runs a display application 116 that outputs
`
`information to the car operator through a GUI 118.
`
`The processor D displays an icon 120 on GUI 118 that represents the navigation
`
`system 110 running in processor A. An icon 124 represents the audio application running in
`
`processor B and an icon 122 represents the ABS application 114 running in processor C.
`
`The memory 128 stores copies of the navigation application 110, audio application
`
`112, ABS application 114 and display application 116. The memory 128 can also store data
`
`associated with the different applications. For example, navigation data 130 and audio data
`
`132 are also stored in memory 128. The navigation data 130 may consist of the last several
`
`minutes of tracking data obtained by the navigation application 110. The audio data 132 may
`
`include the latest audio tracks played by the audio application 112.
`
`The memory 128 can be any CD, hard disk, Read Only Memory (ROM), Dynamic
`
`Random Access (RAM) memory, etc. or any combination of different memory devices. The
`
`memory 128 can include a central memory that all or some of the processors can access and
`
`may also include different local memories that are accessed locally by specific processors.
`
`FIG. 8 shows one example of how the configuration manager 44 reconfigures the
`
`multiprocessor system when a failure occurs in a critical application, such as a failure of the
`
`ABS application 114. The configuration manager 44 for one of the processors in the
`
`multiprocessor system 8 detects a critical application failure in block 134.
`
`One or more of the configuration managers 44 include a watchdog function that both
`
`monitors its own applications and the applications running on other processors. If an internal
`
`application fails, the configuration manager may store critical data for the failed application.
`
`Patent Application
`Atty. Doc. No. 9032-34
`
`9
`
`AHM, Exh. 1031, p. 14
`
`

`

`The data for each application if stored in the memory 128 can selectively be encrypted so that
`
`only the car operator has the authority to download certain types of data.
`
`The configuration manager detecting the failure initiates a reboot operation for that particular
`
`application. The application is downloaded again from memory 128 and, if applicable, any
`
`stored application data. If the application continues to lockup, the configuration manager
`
`may then initiate a reconfiguration sequence that moves the application to another processor.
`
`Failures are identified by the watchdog functions in one example by periodically
`
`sending out heartbeat signals to the other processors. If the heartbeat from one of the
`
`processors is not detected for one of the processors, the configuration manager 44 for the
`
`processor that monitors that heartbeat attempts to communicate with the pro