throbber
asy United States
`a2) Patent Application Publication co) Pub. No.: US 2003/0152088 Al
`(43) Pub. Date: Aug. 14, 2003
`
`Kominamietal.
`
`US 20030152088A1
`
`(54) ELECTRONIC CONTROL SYSTEM FOR
`VEHICLE ACCESSORY DEVICES
`
`(52) US. C1. ececsessseessseecesnesseseees 370/401; 370/469
`
`(76)
`
`Inventors: Yukio Kominami, Novi, MI (US);
`Jungwon Lee, Plymouth, MI (US);
`Jason 1). Stafne, Novi, MI (US);
`Hirohide Suda, Dublin, OH (US);
`Matthew J. Lehmer, Columbus, OH
`(US)
`
`Correspondence Address:
`HARNESS, DICKEY & PIERCE, P.L.C.
`P.O. BOX 828
`BLOOMFIELD HILLS, MI 48303 (US)
`
`(21) Appl. No.:
`
`10/075,515
`
`(22)
`
`Filed:
`
`Feb. 13, 2002
`Publication Classification
`
`(S1)
`
`Int. Ch? eee HO4L 12/56; HO4J 3/16
`
`(57)
`
`ABSTRACT
`
`Asystem and method for managing user preference settings
`in a vehicle includes an electronic control unit having a
`microcontroller and memory. The electronic control unit
`controls vehicle accessory devices. A data controller is in
`communication with the microcontroller of the electronic
`contral unit for receiving the user preference data ta control
`the acccssory devices. The keyless receiver is in communi-
`cation with the microcontroller of the electronic control unit
`for receiving a control signal from a key fob. A PDA
`including a processor, memory, and transceiver in electrical
`communication can be used to transmit the user preference
`data to the data controller. The preference data is transmitted
`to the memoryofthe electronic control unit, which executes
`an algorithm to control the accessory devices according to
`the user preference data.
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 1 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 1 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 1 of 13
`
`US 2003/0152088 Al
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 2 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 2 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 2 of 13
`
`US 2003/0152088 Al
`
`
`
`CEIVER
`TRANS!
`
`
`
`|
`IRDATA
`| FORMAT
`
`
`
` VEHICLEPREFERENCE
`
`MANAGER WEBSITE
`
`i
`
`IR
`
`
`
`
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 3 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 3 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 3 of 13
`
`US 2003/0152088 Al
`
`{ Data Frame(11 bit}
`
`
`
`loentifier
`
`3
`
`Figure-3
`
`Dafa Frame
`
`Driver||Auto
`1D|)Light
`
`
`
`ldle Time
`(UARTtransmission termination)
`Figure-4
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 4 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 4 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 4 of 13
`
`US 2003/0152088 Al
`
`12
`
`Time Out
`
`
`Transmit
`
`Transmit
`DataFrame3
`
`Transmit
`Data Frame 3
`Again
`
`Data Frame 1
`
`Acknowledge 1
`
`Data Frame 2
`
`Acknowledge2
`
`Data Frame 2
`
`Acknowledge 2
`
`DataFrame 3
`
`Data Frame 3
`
`Suecesstultransmission
`ofdata frame 1
`
`
`
`Missing Acknowledge2
`
`
`
`TransmitAcknowledge 2
`
`
`
`
`
`
`
`
`
`Figure - 3
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 5 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 5 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 5 of 13
`
`US 2003/0152088 Al
`
`Data Frame 1
`
`Dit
`
`Errordeiected
`
`TransmitAcknowledge
`again
`
`iF
`
`rame 2
`
`Time Out
`
`Transmit
`Data
`Frame 2
`Again
`
`Transmit
`Data Frame 3
`
`knowledge 4
`
`DataFrame2
`
`Acknowledge2
`
`Data Frame 2
`
`Acknowledge 2
`
`Successful transmission
`ofdaarf
`
`Missing Acknowledge
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 6 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 6 of 24
`
`

`

`
`
`vBU
`
`SIL DR LOCK
`SIL DR UNLOCK
`
`
`
`
`
`
`Patent Application Publication Aug. 14,2003 Sheet 6 of 13
`
`US 2003/0152088 Al
`
`2
`
`A
`
`DIL UNLOCKDR
`Di LOCK
`
`)
`
`F
`
`H
`
`SMALL LIGHT:
`
`
`
`HEAD LIGHT
`
`
` INSTRUMENT
`ILLUMINATION
`
`[a= SEE
`KEES Py
`BUZZER
`
`E
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 7 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 7 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 7 of 13
`
`US 2003/0152088 Al
`
`Time foAuto OFF: 602 seconds
`0
`seconds
`&
`
`Tine to OFFafterclosing
`alldoors:
`0 & seconds
`6
`AbodvencePh|*d
`
`Vehicle Preferencas Manager
`{s theproperty of
`SumitomoElectric Wiring Systems
`
`a B
`
`eam VehiclePHTo anotherPOA
`
`Rostore FactorySotgs
`
`(ee)
`
`Htumination Brightness:
`5 & baghtness lovel
`
`s
`
`Figure . 8
`
`ooo
`
`ae)
`er Unlock wien ignition is tumedOFF
`
`Auto DoorLock Options:
`sm Lock when shiftedoutofPARK
`DoorUnlockSelect:
`
`sv Onlydriver'sdoorunlocks
`
`Auto Door UnlockOptions:
`
`(aie)
`
`Activate the buzzerwhen vehicle is
`shiftedoutof "Pant"positioni:
`EyEmergencyBrakeisset
`EeAny doorisajar
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 8 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 8 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 8 of 13
`
`US 2003/0152088 Al
`
`ce
`
`TransmitSeftings to Vehicle
`
`Figure-8A
`
`Figure . & eeovi-Oiert[|
`Figure - 8D——
`
`Figure-8B
`
`About VehiclePM [
`
`Vehicle Preferences Manager
`[s thepropertyof
`SumitomoElectricWiringSystems
`
`
`
`(aisleDiet[1
`
`
`
`AutoDoorLockOptions:
`~@ Lock when shifiedoutofPARK
`
` Figure - 8E
`DoorUnlockSelect:
`so Onlydriver's doorunlocks
`
`AutoDoorUnlock Options:
`“7 Unlock wien ignition is fumedOF
`
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 9 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 9 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 9 of 13
`
`US 2003/0152088 Al
`
`InteriorLighting «Driver 1
`
`
`
`
`Time to OFFafter closing
`alldoors:
`8 & seconds
`
`Figure-8F
`
`
`
`instramentPanel-Driver1 |
`
`
`HuminationBightiess:
`
`
`5 S brightness level
`Figure-86
`
`
`
`
`
`Light
`Dark
`—S
`
`
`
`AutoLights-Drver!=||
`
`
`Auto Light ON Options:
`7 ONin Medium outdoorlight
`AutoLight OFFOptions:
`
`
`s@ Ignition OFF, driver's door CLOSED
`TimetoAutoOFF:
`5 & seconds
`
`6
`0
`seconds
`
`eee
`
`Figure-8H
`
`Emergencybrakeldoorajarbuzzar
`
`Figure-8f
`
`Activate the buzzer when vehick i
`shiftedout of"Park"positioni
`[AEmergencyBrake isset
`FYAnydoorisafar
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 10 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 10 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 10 of 13.~~US 2003/0152088 Al Figure-9
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 11 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 11 of 24
`
`

`

`MAIN INITIAL
`
`120
`
`‘m0
`
`AIDAND FILTER PROCESS
`
`READ VEHICLE SPEED
`
`
`READ ILLUMINATION CONTROL
`
`210
`
`
`
`
`
`
`ILLUMINATION CONTROL|_~260
` PROCESS
`
`HANNCLROK|#
`560
`BUZZERCONTROL|42/0
`
`
`150
`
`PROCESS
`TIMER
`
`
`INTERRUPTPROCES,
` 160
`AUTO LIGHTON
`PROCESS
`
`
`AUTO LIGHT OFF
`180
`PROCESS
`
`
`WAKEUPINTERRUPT)|_RECEIVEART|TOLERRECEIVE UART
`
`
`
`
`TRANSMITUART
`|-——~190
`340
`WAKE-UP PROCESS
` WRITEEEPROM
`P*™
`
`
`
`
`KEVFOB DATA PROCESS
`
` 229
`<r
`
`
`
`AUTO LOCKPROCESS
`
`
`
`T SLEEPPROCESS
` 310
`
`
`Patent Application Publication Aug. 14,2003 Sheet 11 of 13
`
`US 2003/0152088 Al
`
`1
`
`INITIAL PROCESS
`
`[10
`
`KEYLESS PROCESS
`
`12
`
`DOOR LOCKPROCESS
`
`25
`
`Figure - 10
`
`280
`
`290
`
`
`
`J50
`
`UARTINTERRUPT
`PROCESS
`
`uo
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 12 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 12 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 12 of 13)
`
`US 2003/0152088 Al
`
`
`
`DATA
`
`Hi-Byte
`
`As igo
`
`LO-Byte
`Auto light
`
`
` er
`
`
`
`
`
`
`
`
`[iwAait
`[AarePas
`
`Figure - 11
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 13 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 13 of 24
`
`

`

`Patent Application Publication Aug. 14,2003 Sheet 13 of 13.
`
`US 2003/0152088 A1
`
`CODE C
`
`ECU
`EXECUTABLE
`
`Figure - 12
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 14 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 14 of 24
`
`

`

`US 2003/0152088 Al
`
`Aug. 14, 2003
`
`ELECTRONIC CONTROL SYSTEM FOR VEHICLE
`ACCESSORY DEVICES
`
`FIELD OF THE INVENTION
`
`invention generally relates to elec-
`[0001] The present
`tronic control systems and, more particularly, an electronic
`control system for controlling vehicle accessory devices as
`well as a wireless communication system for programming
`the electronic control system.
`
`BACKGROUND OF THE INVENTION
`
`
`
`[0002] Modern automotive vehicles typically include an
`clectronic control system having an electronic control unit
`coupled to various clectrical accessory devices. The elcec-
`ronic control unit may include a microprocessor and non-
`volatile memory. The microprocessor controls multiple clec-
`rical accessory devices in the vehicle by executing the
`operating instructions of the control program. Such control
`programs in vehicles govern the operation of electrical
`accessory devices and features such as automatic doorlocks,
`interiorlights, instrument panel illumination, exteriorlights,
`keyless door locks, audible notification signals, windshield
`and lamp wiper systems, security system, etc.
`
`In viewof the recent advances in modern automo-
`[0003]
`ive vehicles, however, user capability for programming
`preference settings for electrical accessory devices have
`been deficient. In existing electrical control units, users are
`not able to choose the preference settings for most electrical
`accessory devices. Purther, the programming of these func-
`ions is physically defined in the manufacturing process and
`is not provided to the end user. For cxample, vehicles
`
`
`cquipped with headlamp control functions that automati-
`
`cally turn the headlights on and off
`at a predetermined
`
`hreshold of ambicnt brightness and turn off the headlights
`when the driver exits the vehicle do not allow a user to
`program the predetermined threshold of ambient brightness
`or the length of time before the headlights are turned off after
`he user exits the vehicle. Also, existing entry light control
`devices use an internal timer to turn off the light after a
`predetermined period of time, typically including a dimming
`
`operation,but do not allowthe user to choose the time period
`
`
`
`before the entry lights turn off. Moreover, existing door lock
`controls include factory-programmed lock and unlock con-
`ditions. These lock and unlock conditions can be vehicle
`speed sensilive or depend on key and door operations, but do
`not provide the capability for the end user lo program the
`particular speed or particular key and door operations that
`trigger the lock and unlock conditions.
`[0004]
`Further, in uscr programmable functions provided
`in contemporary automotive vehicles, such as memoryscat
`position and audio system preferences, the user must select
`every preference setting from inside the vehicle. This input
`process is oftcn timc consuming, inconvenicnt, awkward,
`and limited. Further, each function must be defined by an
`input device in the vehicle.
`
`SUMMARYOF THE INVENTION
`
`[0005] The system and method according to the invention
`provides user programmable control functions for vehicle
`accessory devices that are input using a user interface.
`Control information is communicated from the user inter-
`face to an electronic contro] unit via a data controller.
`
`Further, the user interface preferably includes a transceiver
`circuit for producing and transmitting wireless control sig-
`nals and vehicle-specific software for setting and program-
`ming user specified functions. Vehicle-specific software can
`be installed on the user interface, such as a personaldigital
`assistant (PDA), vehicle information system, or navigation
`system.
`
`[0006] The data controller receives and transmits user-
`selected function data from the user interface and includes a
`transceiver and encoder/decoder. This data controller may
`be a component independent from the vehicle, or may be
`included in other vehicle components such as the center
`cluster, audio/video system, or climate control system. The
`control unit
`includes a microprocessor and non-volatile
`memory. The non-volatile memoryis clectrically reloadable
`with data for controlling an object of control by cxecuting a
`control program made up of data stored in the non-volatile
`memory. This control unit includes the vehicle electronic
`control unit for controlling automatic lights, door locks,
`interior lights, memory seats, instrument panelillumination,
`automatic headlamps, keyless door locks, and notification
`tones, as well as audio system and climate control system
`preferences. Further, the data controller and the control unit
`can be coupled together.
`[0007] Generally, the user interface includes a graphical
`user interface (GUI) for inputing user-selectable options and
`a data processor for encoding the input data to a specified
`infrared data transmission [ormat or radio data format (such
`as Bluetooth, available from the Bluetooth Special Interest
`Group al www.bluetooth.com).
`[0008] Wireless communication with the data controller
`can be achieved with any type of PDA, or hand-held
`computer, preferably running PALM OS (available from
`Palm, Inc. of Santa Clara, Calif.) or a compatible operating
`system such as Windows CE (available from Microsoft
`Corp. of Redmond, Wash.). Generally, the accessory devices
`of the automotive vehicle can be simply programmedto user
`preferences using a PDA and the vehicle electronic control
`unit. For example, the automatic headlamp control function
`can be programmed with multiple threshold conditions and
`multiple automatic off conditions. In this function, a thresh-
`old value of
`ambient brightness decides light on and off
`
`points. A user can select one of these thresholds and an
`
`
`automatic-off
`condition, or can completely disable these
`
`
`functions. For the automatic-off
`option, the user can select
`various signal conditions including driver-door open, driver-
`
`door closed, or keyless lock set. As another example, the
`
`user can select cntry-light off
`time with a sclectable delay
`time. Also, the door-lock control gives the user sclectable
`options with multiple lock and unlock conditions. A com-
`bination of these lock and unlock conditions, which depend
`on vehicle speed, kcy position, transmission position and
`door operations, provides a user with various preference
`settings. A user can also select an audible notification signal,
`or buzzer, for warning of certain vehicle conditions such as
`door open or parking brake engagement.
`[0009] Further areas of applicability of the present inven-
`tion will become apparent
`from the detailed description
`provided hereinafter.
`It should be understood that
`the
`detailed description and specific examples, while indicating
`the preferred embodimentof the invention, are intended for
`purposes ofillustration only and are not intendedto limit the
`scope of the invention.
`
`
`
`
`
`
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 15 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 15 of 24
`
`

`

`US 2003/0152088 Al
`
`Aug. 14, 2003
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`invention will become more fully
`[0010] The present
`understood from the detailed description and the accompa-
`nying drawings, wherein:
`
`[0011] FIG. 1 is a partial perspective view of a vehicle
`including a system for managing user preference settings
`according to the invention;
`
`[0012] FIG. 2 is a schematic view of the system for
`managing user preference settings according to the inven-
`tion;
`
`FIG.3 illustrates a data frame for transmitting user
`[0013]
`preference data according to the invention;
`
`FIG.4 illustrates a series of data framesrelating to
`[0014]
`various user preference settings according to the invention;
`
`[0015] FIG. 5 is a schematic viewof the transmission of
`data from a PDAto a vehicle according to the invention;
`
`[0016] FIG. 6 is a schematic viewof the transmission of
`data from a vehicle to a PDA according to the invention;
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`[0032] The following description of the preferred embodi-
`ment(s) is merely exemplary in nature and is in no way
`intended to limit the invention,its application, or uses.
`[0033] With reference to FIGS. 1 and 2, a vehicle 10
`according to the invention is shown. The vehicle 10 includes
`a data controller 14 for two-way communication wilh a
`transceiver 18 of a computer such as PDA 12, or which can
`be hardwired to a vehicle information system or navigation
`system, which can be used as an inpul device 32. FIG. 2
`illustrates both arrangements, which may be used coopera-
`tively or alternatively.
`‘The data controller 14 and user
`interface 32, as shown, are housed in a vehicle console 38.
`The PDA 12 will be used as an exemplary hand-held
`computer, but other computer devices, including other hand-
`held devices, can be used.
`
`
`
`
`
`[0034] As shown, the data controller 14 of the vehicle 10
`includes a transceiver 16 and a microcontroller 24. The
`
`
`microcontroller 24 includes a buffer 62, processor 64, and a
`UARTtransceiver 58. The processor 64 includes an encader/
`decoder. As shown in FIG. 2, the microcontroller 24 of the
`[0017] FIG.7is a schematic view of a vehicle electronic
`data controller 14 encodes and decades data transmitted
`control unit including various inputs and outputs according,
`to the invention;
`therethrough. As shown, vehicle preference data is received
`via infrared transmission from the PDA 12,and specifically
`via the transceiver 18 of the PDA 12. ‘The transceiver 16 of
`the data controller 14 receives the data, which is then
`formatted as UARTdata bythe processor 64 and transmitted
`from the UARTtransceiver 58 of the microcontroller 24 to
`the UARTtransceiver 56 of a vehicle electronic control unit
`22. The vehicle preference data received by the electronic
`control unit 22 is stored in EEPROM 28.
`
`[0018] FIG. 8 is an illustration of screen shots for the
`vehicle preference manager according to the invention;
`
`[0019] FIG. 8A is a screen shot of the main menu of the
`vehicle preference manager of FIG.8;
`
`FIG.8B is the advanced options screen shotof the
`[0020]
`vehicle preference manager of FIG.8;
`
`[0021] FIG. 8C is the about screen shot of the vehicle
`preferences manager of FIG.8;
`
`[0022] FIG. 8D is the vehicle options screen shot of the
`vehicle preferences manager of FIG. 8;
`
`[0023] FIG. 8E is the auto door locks screen shot of the
`vehicle preferences manager of FIG. 8;
`
`[0024] FIG. 8F is the interior lighting screen shot of the
`vehicle preferences manager of FIG. 8;
`
`[0025] FIG. 8G is the instrument panel screen shot of the
`vehicle preferences manager of FIG. 8;
`
`[0026] FIG. 8His the auto light screen shot ofthe vehicle
`preferences manager of FIG.8;
`
`[0027] FIG. 8I is the buzzer serccn shot of the vehicle
`preferences manager of FIG.8;
`
`[0028] FIG. 9 is a flowchart illustrating transmission of
`user preference data according to the invention;
`
`[0029] FIG. 10 is a flowchart illustrating the transmission
`and execution of user preference data according to the
`invention;
`
`[0030] FIG. 11 is a table illustrating the data structure of
`the memoryof a system for managing vehicle preference
`data according to the invention; and
`
`[0031] FIG. 12 is a schematic illustrating the relationship
`of driver ID and user preference data in a system according
`to the invention.
`
`[0035] The PDA 12 includes a processor 20 in communi-
`cation with the transceiver 18 and for executing control
`instructions, as well as an input device 21 for inputting user
`settings. Similarly, the vehicle 10 includes the electronic
`control unit 22 in communication with the transceiver 16 of
`the vehicle 10 through the microcontroller 24 of the data
`controller 14. The electronic control unit 22 of the vehicle 10
`is responsible for electronic control of accessory devices 40,
`sensors 41, keyless receiver 42, and switches 43 of the
`vehicle 10 and includes a microcontroller 26, EEPROM 28,
`and driver circuit 3(). A resonator or clock 60 is in commu-
`nication with the microcontroller 26. The microcontroller 26
`includes a processor 26A and a memory26B. ‘The EEPROM
`28 includes data structure D (as shown in FIG. 11) while the
`microcontroller 26 includes code C (as shown in FIG. 10)
`in ils memory 26B. ‘The vehicle 10 may alternatively or
`additionally include a user input device 32, such as a vehicle
`information or navigation system 32, which is in two-way
`communication with the microcontroller 26 of the electronic
`control unit 22.
`
`[0036] The PDA 12 and vehicle 10 are in two-way com-
`munication via a hard-wired or wireless signal. Specifically,
`the transceiver 18 of the PDA 12 is in two-way communi-
`cation with the transceiver 16 of the vehicle 10. In one
`variation, transceivers 16, 18 are wireless transceivers and
`the wireless signal is an infrared or radio frequency signal.
`In another variation, the PDA 12 is in two-way communi-
`cation with the vehicle 10 through a hard-wired connection.
`In such a variation, the PDA 12 can be docked in a port 36
`to facilitate hard-wired communication between the trans-
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 16 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 16 of 24
`
`

`

`US 2003/0152088 Al
`
`Aug. 14, 2003
`
`ceiver 18 of the PDA 12 andthe transceiver 16 ofthe vehicle
`10. In FIG. 1, the port 36 is shown housed in the vehicle
`console 38. In another variation, data transmission can be
`both wireless and hard-wired, adding additional communi-
`cation flexibility.
`
`[0037] The data is transmitted between the PDA 12 and
`data controller 14 in a ten-bit segment: one start bit, three ID
`bits, five data bits, and one stop bit; and the data is further
`transmitted from the data controller 14 to the microcontrol-
`ler 26 in an eleven-bit segment adding an oddparity bit. The
`start bit will be low (zero), and the stop bit will be high
`(one).
`In one example,
`the baud rate is 9600 bps. An
`exemplary eleven-bit segment, or data frame, is shown in
`FIG.3. As shown in FIG.2, data transmission between the
`PDA12 and data controller 14 is wireless, and particularly
`infrared wireless transmission. Thatis, a ten-bit segment, or
`IR data format, is transmitted between the transceiver 18 of
`the PDA 12 andthe transceiver 16 of the data controller 14.
`The transceiver 16 transmits a ten-bit segment electrical
`signal, which is converted from the received infrared signal,
`to the processor 64. Thc UARTtranscciver 58 transmits an
`eleven-bit segment, or UART data format,
`to a UART
`transeciver 56 of the vehicle clectronic control unit 22 via
`UARTbus 66.
`
`[0038] When transmitting new setting data to the vehicle
`10,
`the PDA 12 sends a three-bit driver identifier data
`segment followed by seven data frames respectively corre-
`sponding to automatic lighting, automatic doorlocks, instru-
`mentpanel, automatic lightoff 1, automatic light off 2, dome
`light, and buzzcr. The cight data frames are sent in succes-
`sion with an idle time of Iess than onc millisecond between
`successive data frames, as best illustrated in FIG. 4.
`
`[0040] Two-way communication with automatic repeat
`request (ARQ) between the transceiver 18 of the PDA 12
`and the transceiver 16 of the vehicle 10 allows the vehicle
`10 to acknowledge the successful transmission of data from
`the PDA 12. Alternatively, high-level data link control
`communication can be used. With reference to FIG. 5, a
`schematic illustrates that upon sending Data Frame1 to the
`vehicle 10, the PDA 12 awaits an acknowledgment message
`of the successful transmission of Data Frame 1 based on a
`stop-and-wait flow-control technique. Upon reccipt, trans-
`mission of Data Frame 1 is complete. Note with the trans-
`mission of Data Frame 2 ta the vehicle 10, the PDA 12 does
`not receive an acknowledgment message before the time
`period for receiving a respanse from the vehicle 10 times
`out. At such point, the PDA 12 sends Data Frame 2 again an
`acknowledgment request message to the vehicle 10, which
`then transmits an acknowledgment message. Uponreceipt of
`the acknowledgment message from the vehicle 10, the PDA
`12 transmits Data Frame 3.
`In this case, Data Frame 3
`contains an error, which the data controller 14 of the vehicle
`10 detecis and transmits an error message to the PDA. Upon
`receipt of the error message, the PDA 12 re-transmits the
`
`[0039] After transceiver 16 of vehicle 10 receives data
`from the PDA 12, the microcontroller 24 decodes the data
`and then sendsthe data to the electronic control unit 22. The
`EEPROM28ofthe electronic control unit is rewritten with
`this updated data. Specifically, the EEPROM 28is updated
`with the data in the same frame format shown in FIG. 4.
`Morespecifically, AppendixAlists the five data bits for each
`[0043] The microcontroller 26 of the vehicle electronic
`of the cight data frame types.
`control unit 22 also receives keyless control signals from
`key fobs 44, 46, which are reccived via radio frequency by
`the keyless receiver 42 and sent via a control signal to the
`microcontroller 26. The microcontroller 26 also reccives
`from the EEPROM 28 an output of user information to
`correspond to the respective key fob for which the control
`signal was received. The microcontroller 26 also sends user
`information corresponding to key fob type to the EEPROM
`28. Finally, the microcontroller 26 sends control signals to
`the driver circuit 30, which, in turn, operates the correspond-
`ing vehicle accessory devices 40.
`
`Data Frame 3 until it is successfully received and acknowl-
`edgment of its receipt is provided by the vehicle 10. With
`reference to FIG. 6, transmission of operation data to the
`PDA 12 from the vehicle 10 operates in a similar manner.
`
`[0041] Referring again to FIG.2, the data transmission of
`user preference settings will be explained in further detail.
`The PDA 12 includes the transceiver 18 for two-way com-
`munication with the transceiver 16 of the vehicle 10. While
`wireless data transmission is shown, such data transmission
`may be wireless and/or hard-wired. Further, the PDA 12
`includes the processor 20 and an input device 21, such as a
`keyboard, touch screen or stylus. The transceiver 16 is in
`two-way communication with the microcontroller 24, which
`is in two-way communication with the microcontroller 26 of
`the electronic control unit 22. The microcontroller 26
`receives input signals from sensors 41, keyless receiver 42,
`and switches 43 of the vehicle 10. Moreover, the driver
`circuit 30 of the electronic control unit 22 is controlled by
`the microcontroller 26 and operates the accessory devices
`40. Multiple key fobs 44, 46 are able to send wireless data
`to the keyless receiver 42 for communication with the
`microcontroller 26.
`
`[0042] The input device 21 of the PDA 12 is used to input
`user preference settings to the PDA 12, specifically to
`memory48 of the PDA 12. The PDA processor 20 transmits
`encoded user preference settings to the transceiver 18 of the
`PDA 12, which in turn sends data from the PDA 12 to the
`vehicle 10, and specifically to the transceiver 16 of the data
`controller 14. Such data transmission is wireless and/or
`hard-wired. The transceiver 16 transmits the reccived data to
`the microcontroller 24, which decodes the reecived data.
`The microcontroller 24 transfers the decoded data to the
`vehicle electronic control unit 22, specifically to the micro-
`controller 26, via the UART bus 66. In a variation of the
`invention, the data is transmitted via serial bus from hard-
`wired input device 32, such as a vehicle information system
`or navigation system. Such an input device 32 mayinclude
`a transceiver, microcontroller, and/or encoder/decoder.
`
`[0044] The vehicle electronic control unit 22 is shown
`schematically connected to various
`sensors,
`switches,
`meters and accessory devices in FIG. 7. Specifically, the
`lock, unlock, door and trunk switches are monitored at group
`A, as well as parking brake,
`transmission position, and
`ignition switch condition. Group B is a data contraller,
`including an infrared wireless transceiver 16 and microcon-
`troller 24. Optionally, a radio-frequency receiver may be
`used. Group C is a speed sensor for sending vehicle speed
`data ta the vehicle electronic control unit 22. Keyless
`receiver 42 for receiving radio wave signals [rom key fobs
`44, 46 is shown as group D for sending lock, unlock, and
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 17 of 24
`
`UNIFIED PATENTS EXHIBIT 1009
`Page 17 of 24
`
`

`

`US 2003/0152088 Al
`
`Aug. 14, 2003
`
`trunk opensignals to the vehicle electronic control unit 22.
`Group E is a keyless buzzer for sending various audible
`notification signals relating to keyless operation. The door
`lock and unlock control is provided at group F, while group
`G provides the same function for the vehicle trunk. Head-
`light and small light control is provided by group H, while
`automatic light control and sensing is provided at group I.
`Group J provides interior lighting control including ignition
`key lighting control. A dimmingcircuit for instrument panel
`illumination, including a manual adjustment knob, is pro-
`vided by group K. As shown, the vehicle electronic control
`unit 22 receives input signals from Groups A, B, C, D, and
`I and operates Groups E,F, G, H, J and K, but more or fewer
`sensors, switches, meters and accessory deviccs may be
`interconnected.
`
`[0045] Next, we will more specifically address the various
`control functions and the user selectable preferences pro-
`vided by the present invention. Specifically, the PDA 12 of
`the present invention provides the user with various prefer-
`ence options in programming the EEPROM 28 of the
`vehicle ECU 22. FIG.8 is a collection of screen shots of the
`graphical user interface for the PDA 12. The screen shot of
`FIG. 8A illustrates that initially the user selects whether
`they are changing the preferences for Driver 1 or Driver 2.
`Further, this screen gives the user the option of changing the
`preference settings or transmitting the settings to the vehicle
`for the selected driver. Also, this screen shot illustrates that
`the user may select advanced options, as shownin the screen
`shot of FIG. 8B, which allow the user to beam the vehicle
`preference manager software to another PDAorrestore the
`factory settings. The “About” option provides information
`about the product, such as that shown in the serecn shot of
`FIG.8C.
`
`[0046] By selecting “Driver 1” and “Change Preference
`Settings” in the screen shot of FIG.8A, the user is presented
`with the screen shot of FIG. 8D, which provides vehicle
`options for automatic lights, interior lighting, instrument
`panel illumination, automatic door locks, and buzzers.
`[0047]
`First, regarding the automatic doorlocks, a user is
`given several unlock options to input from the PDA 12, as
`illustrated in the screen shot of FIG. 8E. The locking options
`include disabling automatic lacks, locking when ignition is
`turned on, locking when the vehicle exceeds a predeter-
`mined threshold speed, or locking when the vehicle trans-
`mission is shifted [rom park. Further,
`the user is given
`several automatic door unlock selections including unlock-
`ing all doors or only unlocking the driver’s door. Finally, the
`user is given several unlock options including unlocking
`when shifted into park and vehicle speed equals zero,
`unlocking whenignition is turned off, or unlocking whenthe
`key is removed fromthe ignition cylinder.
`
`[0048] As shownin the screen shot of FIG. 81’, there are
`several
`interior light options provided by the PDA 12.
`
`Interior lights are controlled to turn on by a door switch or
`
`
`
`
`keyless entry, and controlled off by the door switch. When
`the door switch is closed, the time to off
`is dependent on
`information contained in the EEPROM 28 as input by the
`driver from the PDA 12. The timeto off is user selectable
`between zero and 30 seconds. A smaller or larger time range
`may be provided as desired.
`
`
`
`Instrument panel illumination is also user select-
`[0049]
`able, as shown in the screen shot of FIG. 8G. Instrument
`
`panel brightness setting can be input via the PDA 12. The
`instrument panel backlighting is also adjustable manually
`with a dial in the vehicle if a change is required.
`
`[0050] With reference to the screen shot of FIG. 8H,
`automatic headlamp control, including small lights and rear
`lights control, automatically turn the lights on at one of four
`driver-selectable settings provided by the PDA 12. The
`lights can be set to always on, on in low brightness, on in
`medium brightness, or on in high brightness. Further, the
`headlamp, smalllights and rear lights will automatically turn
`off at one ofthree driver-selectable settings from the PDA 12
`including off when ignition is off and the driver’s door is
`opened, timed off from zcro to 60 seconds when ignition is
`off and the driver’s door is opened and then closed, and
`timed off from zcro to 60 scconds when ignition is off and
`keyless lock is initiated.
`
`functions (not
`lock control
`[0051] Keyless and door
`shown) mayalso be selected from the PDA as well. Options
`include controlling the door lock motor to lock/unlock the
`door by door lock switch input or controlling the door lock
`motor and trunk opener by the key fob’s wireless transmis-
`sion. Other control functions available to the user include
`keyless acknowledgment and door lock motor superlock
`functions via superlock relay based on key cylinder switch
`input.
`
`[0052] As shown in the screen shot of FIG. 81, buzzer
`control functions provided by the PDA include activating the
`buzzer when (1) the vehicle is shifled out of park and (2)
`either the emergency brake is on or any dooris ajar.
`
`‘The PDA12stores vehicle preference management
`[0053]
`software in its memory 48. ‘This software allows a user lo
`select preference settings for vehicle acc

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