throbber
(12) United States Patent
`Barnea et al.
`
`I IIIII IIIIIIII Ill lllll lllll lllll lllll lllll lllll lllll lllll 111111111111111111
`US006396164Bl
`US 6,396,164 Bl
`May 28, 2002
`
`(10) Patent No.:
`(45) Date of Patent:
`
`(54) METHOD AND APPARATUS FOR
`INTEGRATING CONTROLS
`
`(75)
`
`Inventors: Michael Barnea, Highland Park; Mark
`A. Ruthenbeck, Gurnee, both of IL
`(US)
`
`(73) Assignee: Motorola, Inc., Schaumburg, IL (US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by O days.
`
`(21) Appl. No.: 09/421,654
`
`(22) Filed:
`
`Oct. 20, 1999
`
`Int. Cl.7 ................................................... B60L 1/00
`(51)
`(52) U.S. Cl. ........................... 307/10.1; 701/36; 701/49
`(58) Field of Search ................................. 307/9.1, 10.1;
`701/36, 48, 49; 340/825.52
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`6,032,089 A * 2/2000 Buckley .. ... .. ... ... ... ... .. . 701/36
`
`6,114,970 A * 9/2000 Kirson et al. .......... 340/825.52
`6,163,079 A * 12/2000 Miyazaki et al. .......... 307/10.1
`6,189,057 Bl * 2/2001 Schwanz et al. .............. 701/72
`6,236,918 Bl * 5/2001 Sonoda et al. ................ 701/36
`6,240,347 Bl * 5/2001 Everhart et al.
`.............. 701/36
`
`* cited by examiner
`
`Primary Examiner-Josie Ballato
`Assistant Examiner-Sharon Polk
`(74) Attorney, Agent, or Firm-Gary J. Cunningham;
`Steven A May
`
`(57)
`
`ABSTRACT
`
`Electronic devices (38) are added to the electrical system
`(10) of a motor vehicle and utilize controls (20-26) and
`indicators (14) existing within the vehicle. The add-on
`electronic devices (34-38) interact with a gateway (30), and
`the gateway (30) is coupled to the electrical system (10). The
`function of the controls (20-26) and indicators (14) within
`the vehicle are context controlled relative to the operating
`context of the existing vehicle electronic systems and the
`add-on electronic devices (34-38).
`
`19 Claims, 2 Drawing Sheets
`
`rlO
`
`28
`
`24
`
`20
`
`18
`
`22
`
`HVAC
`
`52
`
`12
`
`___________ ...J
`
`14
`
`DIC
`
`16
`
`RADIO
`
`42
`
`31
`
`30
`
`44
`
`GATEWAY
`
`52
`
`36
`
`34
`
`PAGER
`
`CELL
`PHONE
`
`DEVICE
`
`40
`
`46
`
`48
`
`33
`
`32
`
`38
`
`Daimler Exhibit 1004
`
`Page 1 of 6
`
`

`

`U.S. Patent
`US. Patent
`
`May 28, 2002
`May 28, 2002
`
`Sheet 1 of 2
`Sheet 1 0f 2
`
`US 6,396,164 Bl
`US 6,396,164 B1
`
`a
`9v
`"l"'
`
`~
`
`co
`~
`
`~
`
`~
`mm,
`
`~
`mm.
`
`w
`u
`H >
`LI.J
`Cl
`
`.....J LI.J
`.....J :z
`wO
`u:::i:::
`a..
`
`a::::
`w
`C!)
`< a..
`
`<.o
`mm
`cY)
`
`~
`Fm,
`
`~
`N.AVNBN
`~
`~
`
`_mmmm_9;:_9V3»omHm_mm
`
`.-..i
`cY)
`
`_me"nnEu.6.Ca
`_)NW
`
`C'\J
`~
`
`co
`
`'"-i
`
`~
`vm_
`
`a
`
`'"-i
`
`\
`
`~
`
`Page 2 0f 6
`
`>-
`<
`3,::
`w
`I-
`< C!)
`
`:35-
`
`_
`
`_
`-
`
`-
`
`~
`
`-
`
`-,
`
`mm_1IIIIIIIIIII
`_NM89:.
`
`C'\J
`'"-i
`
`0
`H
`
`0 < a::::
`
`~
`
`u
`<
`> :::i:::
`
`"l"'
`3
`.-..i
`
`u
`08
`H
`0
`
`<.o
`'"""-I
`
`Page 2 of 6
`
`
`

`

`U.S. Patent
`
`May 28, 2002
`
`Sheet 2 of 2
`
`US 6,396,164 Bl
`
`100
`
`-
`1 02
`
`~
`
`104
`
`106
`
`-
`108
`
`RECEIVE INPUT
`FROM A CONTROL
`
`, ,
`
`DETERMINE THE
`OPERATING CONTEXT
`
`1
`
`INDENTIFY THE DEVICE
`ASSOCIATED WITH THE
`OPERATING CONTEXT
`
`. '
`MAP CONTROL INPUT
`TO CONTROL DATA
`FOR THE DEVICE
`
`FIG.2
`
`Page 3 of 6
`
`

`

`US 6,396,164 Bl
`
`1
`METHOD AND APPARATUS FOR
`INTEGRATING CONTROLS
`
`FIELD OF THE INVENTION
`
`The present invention relates generally to vehicle electri-
`cal systems, and more particularly, to a method and appa(cid:173)
`ratus for integrating control functions within a vehicle
`electrical system.
`
`BACKGROUND OF THE INVENTION
`
`2
`actually permits such interaction has not been achieved.
`Therefore, each add-on electronic device still requires a set
`of controls and displays separate from the vehicle controls
`and displays.
`Thus there is a need for a method and apparatus of
`integrating the controls and indicators of add-on devices
`with the existing electronic devices within a motor vehicle.
`
`5
`
`10
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`FIG. l is a block diagram illustration of vehicle electronic
`system architecture in accordance with a preferred embodi(cid:173)
`ment of the invention.
`FIG. 2 is a flow chart illustrating a method of integrating
`controls and functions in accordance with a preferred
`15 embodiment of the invention.
`
`Motor vehicles have seen a tremendous increase in the use
`of in-vehicle electronics. Many of these in-vehicle electron-
`ics are adapted to provide the vehicle driver and occupants
`with a vast amount and array of data and information via
`wireless communication technology, and to allow them to
`communicate data and information outside of the vehicle
`also using wireless technology. An example of these elec(cid:173)
`tronics devices are on-board navigation systems, remote
`vehicle diagnostic systems, real-time weather service, voice 20
`communication, Internet access, email and paging.
`However, since the design cycle for the typical motor
`vehicle is relatively long as compared to the design cycle for
`new electronic devices, new state-of-the art electronic prod(cid:173)
`ucts are available but may not be readily adaptable to the
`motor vehicle.
`Many motor vehicles are designed with an original equip(cid:173)
`ment manufacturer (OEM) communication bus structure
`that allows the original equipment (OE) electronic devices to
`communicate with each other and with device controllers 30
`and with other vehicle systems connected to the bus. This
`bus structure, however, typically operates using a propri(cid:173)
`etary communication protocol. The OE devices connected to
`the OEM bus are generally designed and engineered or
`specified by the vehicle manufacturer such that they are
`completely compatible with the proprietary protocol.
`However, since each manufacturer may have its own
`protocol, devices that are typically available as aftermarket
`equipment may not readily interface with the OEM bus. In
`addition, in view of the many governmental requirements
`for vehicle certification, safety, fuel economy, emissions,
`etc., and the possibility of adverse interactions between
`add-on devices with the vehicle systems, many manufactur(cid:173)
`ers restrict the ability to add devices directly to the OEM bus
`even if designed to be compatible. Hence, one will appre(cid:173)
`ciate that while numerous state-of-the-art electronic devices
`are being introduced into the market place, many such
`devices are not easily adapted to the many different motor
`vehicles.
`It has been proposed to provide a gateway to the OEM bus
`that permits a limited amount of interaction between add-on
`electronic devices and the OEM bus. However, having
`generally restricted direct access to the OEM bus, the
`vehicle manufacturers have also, as a result, generally
`restricted access to the various controls and indicators, e.g.,
`switches, buttons, displays, etc., within the vehicle that
`provide control input and feedback to and from the many
`different features and functions contained within the vehicle.
`For example, it is now common to include control switches
`on the steering wheel that allow the vehicle operator to 60
`control such things as the heating, ventilating and air con(cid:173)
`ditioning (HVAC) system, the radio, and the like. It is also
`common to provide vehicle information systems that display
`various information relating to the operation of the vehicle.
`While it has been only suggested to have such a gateway 65
`permit interaction of the OE controls and indicators with the
`add-on devices, a suitable architecture and methodology that
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`In accordance with the invention, electronic devices are
`added to the electrical system of a motor vehicle and utilize
`controls and indicators existing within the vehicle. The
`add-on electronic devices interact with a device bus, and the
`device bus interfaces with the vehicle bus and vehicle
`25 electrical system via a gateway. The function of the controls
`and indicators within the vehicle are context controlled
`relative to the operating state of the existing vehicle elec(cid:173)
`tronic systems and the add-on electronic devices.
`Referring to FIG. 1, a vehicle electrical system 10
`includes an original equipment manufacturer (OEM) data
`bus, vehicle bus 12, to which various original equipment
`(OE) electronic devices are coupled. As shown in FIG. 1, at
`least a driver information center (DIC) 14, a radio 16 and an
`HVAC controller 18 are coupled to the vehicle bus 12. The
`35 DIC 14 includes a suitable display, such as a light emitting
`diode (LED) or liquid crystal (LC) display that may provide
`text and graphic information to the driver. Also coupled to
`the vehicle bus 12 are controls 20, 22, 24 and 26, e.g.,
`switches, that as illustrated in FIG. 1 may be provided on a
`40 steering wheel 28 of the vehicle.
`Coupled to the vehicle bus 12 is a gateway 30. The
`gateway 30 couples the vehicle bus 12 with a device bus 32.
`To the device bus 32 is coupled to numerous additional
`electronic devices such as pager 34, cellular telephone 36
`45 and other electronic devices generally indicated as device
`38. The other devices that may be coupled to the device bus
`32, without limiting the number or type of devices, include
`navigation systems, infrared transceivers, personal
`computers, personal digital assistants, communication/data
`50 ports or docking stations, and the like. The devices coupled
`to the device bus 32 may communicate on a peer-to-peer
`basis permitting the device bus 32 to operate without a
`separate bus controller, and each device may further include
`memory for retaining operating information. While the
`55 preferred embodiment shown in FIG. 1 shows the electron(cid:173)
`ics devices coupled to the gateway 30 by way of the device
`bus 32, it will be appreciated that the device bus 32 may not
`be necessary and the electronic devices may be coupled
`directly to the gateway 32
`Also coupled to the data bus 32 is an auxiliary control
`assembly 40 including a plurality of controls, 42, 44, 46 and
`48, e.g., switches. The control assembly 40 may also include
`a display or indicators such as a LC display, LEDs, a voice
`synthesizer or an audible signal generator all generally
`illustrated as display 50. As will be described, the devices
`34--38 may be controlled and operated using the vehicle
`controls 20---26 and/or the controls 42-48.
`
`Page 4 of 6
`
`

`

`US 6,396,164 Bl
`
`10
`
`20
`
`3
`The controls 20-26 provide control signals which are
`communicated along a data link 52 to the vehicle bus 12 and
`hence to the gateway 30. In accordance with the invention,
`the controls 20---26 are not associated with the operation of
`any one particular electronic device, e.g., devices 16 and 18
`coupled to vehicle bus 12 or devices 34-38 coupled to the
`device bus 32. Whether the operation of any device is
`effected by manipulation of controls 20-26 depends on the
`current operating context of the electronic system 10.
`Similarly, controls 42-48 are not associated with the opera(cid:173)
`tion of any one particular device. Furthermore, the informa(cid:173)
`tion provided or displayed by either the DIC 14 and/or the
`display 50 may depend on the operating context.
`In a preferred embodiment, the operating context may be
`determined by the gateway 30. The gateway 30 may further
`include a memory 31 in which the various operating con(cid:173)
`texts of the electronic system 10 are stored. Associated with
`each of the operating contexts stored within the memory 31
`is control data. The control data provides a mapping of
`control manipulations to control data appropriate for the
`given device.
`Operating context may be established in a number of
`ways. For example, a default context may exist wherein
`manipulation of the controls 20-26 and 42-48 control a
`default electronic device or devices. For example, controls
`20 and 22 may, in the default context, control the volume, up
`or down, respectively, of the radio 16. The operating context
`may be selectable. For example, from the default context
`control 24 may manipulate a scrolling list of operating
`context choices on either or both of DIC 14 and display 50 30
`while control 26 may permit selection of a particular oper(cid:173)
`ating context. Upon selection, the electronic system 10
`enters the operating context.
`In accordance with a preferred embodiment of the
`invention, the operating context may be automatically 35
`selected based upon activation or operating state of a device.
`For example, if a page, e.g., data from an external source, is
`received by the pager 34, the pager 34 may send a message
`to the gateway 30 via the data link 52 indicating that a page
`has been received. The gateway 30 then automatically enters 40
`the operating context for the pager 34. If the previous
`operating context was the default operating context, the
`control 20 and 22 may be modified such that instead of
`effecting upon actuation radio volume, manipulation now
`provides for page acknowledgment and page read functions, 45
`respectively. That is, upon actuating control 20, a signal is
`received by the gateway 30. According to the operating
`context for the pager 34, the gateway 30 maps the input from
`control 20 to control data for the pager 34 that instructs the
`pager 34 to acknowledge the page. The gateway 30 then 50
`sends the data to the pager 34 via the link 52 and the device
`bus 32. Similarly, an input received from control 22 is
`mapped to control data for pager 34 to read the page. Upon
`receiving the control data to read the page, the pager 34
`places the page data on the device bus 32. With the operating 55
`context established for the pager 34, the page data received
`by the pager 34 is provided to the DIC 14 and/or the display
`50 and appropriately displayed.
`The default operating context may be returned to follow(cid:173)
`ing a time-out period. For example, once the page data has 60
`been displayed, after the time-out period the operating
`context may revert back to the default operating context.
`Alternatively, the vehicle operator may select a new oper(cid:173)
`ating context, for example, if in response to the page the
`vehicle operator wants to make a call using the cell phone 65
`36. Still, activation of another device may cause the elec(cid:173)
`tronic system to enter a different operating context.
`
`4
`It will be appreciated that some operating contexts may
`have priority over others such that a current operating
`context is maintained even in light of a change in a device
`operating state. Alternatively, hybrid or temporary operating
`5 contexts may be created. For example, if the current oper(cid:173)
`ating context is that associated with the cell phone 36,
`controls 20 and 22 may control the speaker volume for the
`cell phone 36. If a page is received by the pager 34, a
`temporary mapping may be established by the gateway 30 so
`that control 20 provides control inputs to the pager 34 to
`acknowledge the page, after which control 20 again provides
`speaker volume control.
`Auxiliary control assembly 40 and the associated controls
`42-48 may provide operation similar to controls 20---26. That
`15 is, control 42 may provide the same function as control 20,
`control 44 the same as control 22 and so on. Alternatively,
`controls 42-48 may provide different functions. Whether the
`controls 42-48 provide the same or different function as
`controls 20-26 is again dependent on the operating context.
`For example, in the default context, it may be preferred to
`have the controls 42-48 operate one or more of the devices
`34--38 while the controls 20---26 operate one or more of the
`devices 16 and 18. It should be further appreciated that
`certain controls may have fixed functions. That is, certain
`25 controls may provide the same function regardless of oper(cid:173)
`ating context. Of course, each device may still have its own
`set of dedicated controls; however, it should be appreciated
`that these controls too may be made flexible in accordance
`with the invention.
`With reference to FIG. 2, a method 100 in accordance
`with the invention begins at step 102 with receipt of an input
`from at least one of the controls 20---26 and 42-48. The
`gateway 30 then determines the operating context of the
`electronic system 10, step 104. Depending on the operating
`context, i.e., which device the operating context is associ(cid:173)
`ated with, step 106, the input is mapped to control data for
`the appropriate device, step 108. Thus, the invention pro(cid:173)
`vides a method of utilizing the controls already within a
`vehicle to control devices that are later added to the vehicle.
`As described, the gateway 30 may retain the data neces(cid:173)
`sary to determine the current operating context as well as the
`data necessary to map inputs from the controls 20-26 and
`42-48 to control data for the appropriate device. When a
`device is added to the device bus 32, the device may
`preferably report data to the gateway 30 that defines the
`device's operating context and associated control data. Thus,
`new devices are easily added to the electronic system 10
`utilizing the controls and indicators already associated with
`the electronic system 10.
`Still other modifications and alternative embodiments of
`the invention will be apparent to those skilled in the art in
`view of the foregoing description. This description is to be
`construed as illustrative only, and is for the purpose of
`teaching those skilled in the art the best mode of carrying out
`the invention. The details of the structure and method may
`be varied substantially without departing from the spirit of
`the intention, and the exclusive use of all modifications
`which come within the scope of the appended claims is
`reserved.
`We claim:
`1. A method of controlling a vehicle electronic system, the
`vehicle electronic system comprising a plurality of elec(cid:173)
`tronic devices coupled by a gateway to an original equip(cid:173)
`ment manufacturer (OEM) control, the method comprising
`the steps of:
`establishing one of a plurality of operating contexts of the
`vehicle electronic system, wherein each operating con-
`
`Page 5 of 6
`
`

`

`US 6,396,164 Bl
`
`10
`
`5
`text of the plurality of operating contexts is associated
`with an operation of an electronic device of the plu(cid:173)
`rality of electronic devices;
`receiving an input from the OEM control;
`determining whether the operating context is an operating 5
`context associated with a first electronic device of the
`plurality of electronic devices; and
`modifying the OEM control for providing control data
`appropriate to the operation of the first electronic
`device when the operating context is the operating
`context associated with the first electronic device.
`2. The method of claim 1, further comprising the step of
`controlling the first electronic device from the original
`equipment manufacturer (OEM) control.
`3. The method of claim 1, wherein the operating context
`is established by an activation of the first electronic device.
`4. The method of claim 1, wherein the operating context
`is established by receipt from an external source of data by
`the first electronic device.
`5. The method of claim 1, further comprising a step of
`providing from the first electronic device context informa(cid:173)
`tion to the gateway, the context information identifying the
`operating context associated with the first electronic device
`and the control data associated with the operation of the first
`electronic device.
`6. The method of claim 1, wherein the electronic system
`further comprises at least one indicator coupled to the
`gateway, and the method further comprises the steps of:
`providing indication data from the first electronic device 30
`and
`indicating the indication data on the indicator.
`7. The method of claim 6, wherein the indication data
`indicates the operating context.
`8. The method of claim 1, wherein the step of determining
`comprises a step of determining whether the operating
`context is an operating context associated with a first elec(cid:173)
`tronic device of the plurality of electronic devices or with a
`second electronic device of the plurality of electronic
`devices, and wherein the step of modifying comprises steps 40
`of:
`modifying the control for providing control data appro(cid:173)
`priate to the operation of the first electronic device
`when the operating context is the operating context
`associated with the first electronic device; and
`modifying the control for providing control data appro(cid:173)
`priate to the operation of the second electronic device
`when the operating context is the operating context
`associated with the second electronic device.
`9. The method of claim 8, wherein the first electronic 50
`device is operably coupled to the gateway via a device bus
`and wherein the second electronic device is operably
`coupled to the gateway via a vehicle bus.
`10. A vehicle electronic system comprising:
`an original equipment manufacturer (OEM) control;
`a gateway operably coupled to the OEM control;
`a plurality of electronic devices coupled to the gateway;
`
`6
`the vehicle electronic system having at least one operating
`context associated with each electronic device of the
`plurality of electronic devices; and
`wherein the gateway contains data identifying the oper(cid:173)
`ating context associated with each electronic device
`and further contains control data associated with the
`operation of the electronic device, and within the
`operating context, provides control data to the elec(cid:173)
`tronic device responsive to an input from the OEM
`control, allowing the OEM control to control each
`device based on the operating context.
`11. The vehicle electronic system of claim 10, wherein the
`original equipment manufacturer OEM control comprises
`one or more of a vehicle control and an auxiliary control,
`15 wherein the vehicle control is operably coupled to the
`gateway via a vehicle bus, wherein the auxiliary control is
`operably coupled to the gateway via a device bus, wherein
`a first electronic device of the plurality of electronic devices
`is coupled to the vehicle bus, wherein a second electronic
`20 device of the plurality of electronic devices is coupled to the
`device bus, and wherein each of the vehicle control and the
`auxiliary control is capable of operating each of the first
`electronic device and the second electronic device.
`12. The vehicle electronic system of claim 10, wherein a
`25 first electronic device of the plurality of electronic devices
`comprises a vehicle device operably coupled to the via a
`vehicle bus, and wherein the gateway contains data identi(cid:173)
`fying an operating context associated with the vehicle device
`and control data associated with the operation of the vehicle
`device.
`13. The vehicle electronic system of claim 10, further
`comprising at least one indicator operably coupled to the
`gateway.
`14. The vehicle electronic system of claim 10, wherein at
`35 least one electronic device of the plurality of electronic
`devices comprises one of the group of devices consisting of
`a pager, a cellular telephone, a personal computer, a personal
`digital assistant, a navigation system, an infrared interface,
`an entertainment device and a data port.
`15. The vehicle electronic system of claim 10, further
`comprising a device bus coupled to the gateway and wherein
`at least one electronic device of the plurality of electronic
`devices is coupled to the device bus.
`16. The vehicle electronic system of claim 15, further
`45 comprising a vehicle bus and wherein at least one electronic
`device of the plurality of electronic devices is coupled to the
`vehicle bus.
`17. The vehicle electronic system of claim 10, wherein the
`original equipment manufacturer (OEM) control comprises
`a switch device.
`18. The vehicle electronic system of claim 10, wherein the
`original equipment manufacturer OEM control comprises a
`switch in an OEM auxiliary control assembly.
`19. The vehicle electronic system of claim 10, wherein the
`55 original equipment manufacturer OEM control comprises a
`switch on a steering wheel.
`
`* * * * *
`
`Page 6 of 6
`
`

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