(12) United States Patent
`Berry
`
`USOO6559773B1
`(10) Patent No.:
`US 6,559,773 B1
`(45) Date of Patent:
`May 6, 2003
`
`(54) RECONFIGURABLE DISPLAY
`ARCHITECTURE WITH SPONTANEOUS
`RECONFIGURATION
`
`(75) Inventor: Richard Charles Berry, West
`Bloomfield, MI (US)
`(73) Assignee: Visteon Global Technologies, Inc.,
`Dearborn, MI (US)
`-
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(*) Notice:
`
`(21) Appl. No.: 09/468,170
`(22) Filed:
`Dec. 21, 1999
`9
`7
`(51) Int. Cl.' .................................................. G08B 5/00
`(52) U.S. Cl. ...................... 340/815.4; 340/531; 701/29;
`701/33; 700/17; 700/83; 345/326
`(58) Field of Search .............................. 340/815.4,531;
`701/29, 33; 700/17, 83; 345/326
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`5,418,962 A 5/1995 Bodin et al.
`5,627,547 A * 5/1997 Ramaswamy et al. ...... 342/357
`5,742,226. A
`4/1998 Szabo et al. ............. 340/425.5
`
`5,794,164 A 8/1998 Beckert et al.
`
`OTHER PUBLICATIONS
`Sun Microsystems, Inc., “Why Jini Now', Aug. 1, 1998, pp.
`1-14.
`Sun Microsystems, Inc., “What is Jini'?' Summary.
`Clohessy, Kim, Object Technology, Inc., Virtual Machine
`Technology: Managing Complexity and Providing Portabil
`ity for Embedded Systems.
`Mobile GT, “The Architecture for Driver Information Sys
`tems’.
`* cited by examiner
`Primary Examiner Daniel J. Wu
`Assistant Examiner Tai T. Nguyen
`(74) Attorney, Agent, or Firm John E. Kajander
`(57)
`ABSTRACT
`A control panel/display Subsystem acts as a device portal for
`interacting with multiple devices interconnected via a
`dynamic local network. Display content and the human
`machine interface (HMI) implemented using the display
`Subsystem automatically reconfigures itself when new
`devices are added to the vehicle network. An interface
`Specifier enabling each new device to work with the device
`portal is obtained either from a local archive or a remote
`archive via connection with a remote network.
`
`18 Claims, 3 Drawing Sheets
`
`
`
`S$ 6.
`
`E-NET PHONE
`
`NAVIGATION
`
`AHM, Exh. 1006, p. 1
`
`

`

`U.S. Patent
`
`May 6, 2003
`
`Sheet 1 of 3
`
`US 6,559,773 B1
`
`
`
`
`
`CO
`
`S
`
`(?
`
`E-NET PHONE
`
`NAVIGATION
`
`Jugels list
`
`14
`
`/25
`
`l6
`
`17
`
`
`
`
`
`
`
`
`
`
`
`3.
`
`6O
`
`FIG. 1
`6/
`
`62
`
`1: Registration
`
`O
`
`O 2: HM Check
`
`3. HM Request
`
`4: HM Report
`
`5. Cleanup
`
`AHM, Exh. 1006, p. 2
`
`

`

`U.S. Patent
`U.S. Patent
`
`May 6, 2003
`May6, 2003
`
`Sheet 2 of 3
`Sheet 2 of 3
`
`US 6,559,773 B1
`US 6,559,773 B1
`
`
`
`
`
`a0108g
`
`
`
`BPOSIWYAUCD'UOS]SIA-MAMJOAISS{WH0:edk,
`
`
`
`
`
`
`
`UediLBfSIG}JO)BAIUTY|INH
`
`Uao1nag|a01AaqQa0;AageyeyCa)éY(WH(WHINH
`
`PP\_Aowon|
`
`r
`
`- -
`
`-
`
`
`
`UWaaikeg)9%oP
`
`2p
`
`
`
`EPBPIYSAspisul
`
`
`
`aPlyaAapIsing
`
`wapow
`
`ssajuimbP
`
`SSOlAIM
`
`Wapow
`
`at
`
`
`
`
`Frjabeuey|}08cA{Ae\dsiq40)aNuotyTWH
`
`SPOILUY/WODJBANOSAUYMW“JAAIBS|HU‘ady
`
`UadIAagbdd1Aeq0a31A0q
`
`ao1KEg
`
`9dazisUeg
`
`JQyene104dOf
`
`IWHIH
`
`
`
`
`
`SPOSIWY/WO'S2IUSAAWMAMJONESWH|:adk,
`
`aonag
`
`ftJaReldEd
`uanlAag|a1A0q0d0)A0q
`
`
`
`
`
`
`
` IWHIWH|8dX)AB\dsigJo)aAIUAY[WH
`
`AHM, Exh. 1006, p. 3
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Øø
`OP
`
`audud(18D
`
`
`
`JO:JO}
`
`UanAag|a0ag(0aoa
`
`
`
` INHINH0SGA]AB|CSIqJO)SAIYUYINH
`
`
`
`
`
`
`
`AHM, Exh. 1006, p. 3
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`May 6, 2003
`
`Sheet 3 of 3
`
`US 6,559,773 B1
`
`
`
`Human-Machine Interface (HMI)
`Application Objects For a
`Climate Control, Radio Tuner, Wireless, E-Mail, Cellular Phone,
`Audio, CD Player, etc...
`
`HMI Widgets Component Library
`Objects For
`Button Metaphor, ListBox, Window, Text Box, Time, etc.
`
`Graphics Primitives (Graphics Device Interface (GDI))
`VECTOR: Line, Rectangle, Polygon, Arc, etc.
`RASTER: Bitmap, Font, etc.
`WINDOWMANAGEMENT: Clipping, Scrolling, etc.
`ATTRIBUTES: Color, Rotation, LineStyle, etc.
`
`Display Frame Buffer
`Bit Plane(s) Target Selection
`Bit Plane(s) Visibility Selection
`Draw Mode (BOOLEAN Operation or REPLACE)
`
`FIG. 3
`
`AHM, Exh. 1006, p. 4
`
`

`

`US 6,559,773 B1
`
`1
`RECONFIGURABLE DISPLAY
`ARCHITECTURE WITH SPONTANEOUS
`RECONFIGURATION
`
`BACKGROUND OF THE INVENTION
`The present invention relates in general to a reconfig
`urable display/control panel for controlling various elec
`tronic accessories, and more specifically to an architecture
`for reconfigurable displays and an overall network for
`Spontaneously interconnecting the displays with various
`electronic accessories or devices in a manner which auto
`matically reconfigures menu elements shown on the recon
`figurable display to interact with each electronic accessory.
`Reconfigurable displays are used in automotive vehicles
`in order to control a plurality of electronic accessories from
`a single control panel. Such a System reduces cost, Saves
`Space on the vehicle instrument panel, and makes the
`electronic accessories easier to control. A reconfigurable
`display includes a generic graphic display Surface, Such as a
`dot matrix, and a collection of “soft keys” (i.e., program
`mable buttons). The function of each key is dynamically
`reconfigured via Software to allow access to all the available
`functions or the accessories, typically using a menu struc
`ture. A typical reconfigurable display Subsystem may also
`include a number of “hard keys”, buttons that provide instant
`access to frequently used functions (e.g., navigation, climate
`control, audio players, etc.).
`Because of their generic, reusable nature, reconfigurable
`automotive displays have facilitated an increase in the
`number of features that are made available to the user.
`Consumers are demanding ever-greater functionality from
`their electronic accessories, while product design cycles of
`the accessories are simultaneously becoming shorter. Thus,
`it becomes a major challenge for manufacturers to provide
`new and innovative System architectures while delivering
`high content, high quality products and features at a reason
`able cost.
`First generation automotive reconfigurable display SyS
`tems utilize embedded architectures that build Specific fea
`ture content into the display design that cannot be altered or
`augmented after the design is implemented. All Supported
`features must be identified at the time of initial design. While
`this approach provides high performance and low cost, it
`lacks flexibility.
`Second generation automotive reconfigurable display SyS
`tems utilize a personal computer (PC) type of architecture,
`such as the AutoPC platform. Such systems enable incre
`mental feature deployment, wherein new features can be
`integrated Seamlessly with those already present. However,
`Such feature deployment is essentially a Static model Since
`installed Software applications occupy a percentage of the
`display resources at all times. Thus, it is distinctly possible
`that System resources could be inadvertently depleted during
`installation of a new feature. Furthermore, Such customiza
`tion requires installation skills on the part of the users (not
`just System developers and integrators), which limits the
`utility of Such customization for a significant percentage of
`customers. Such Systems are not truly “plug-and-play' Since
`a manual installation procedure is required.
`SUMMARY OF THE INVENTION
`The present invention has the advantage of providing a
`reconfigurable display architecture in which a human
`machine interface (HMI) is dynamically constructed in
`response to the electronic accessories which are present in
`the System.
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`In one aspect of the invention, an electronic accessory
`display/control System is provided for a transportation
`vehicle. A reconfigurable control panel has a visual display
`for displaying menu items for an electronic accessory and
`has at least one control actuator. Ahuman-machine interface
`controller is coupled to the reconfigurable control panel and
`includes a local archive for Storing a plurality of interface
`Specifiers. Each specifier defines interaction between the
`reconfigurable control panel and a respective electronic
`accessory for performing operations via the menu items
`using a predetermined communications protocol. The SyS
`tem includes an expandable interconnection link for cou
`pling compatible electronic accessories with the human
`machine interface controller. A wireleSS transceiver is
`provided for accessing a remote archive of interface Speci
`fiers. The remote archive includes interface Specifiers each
`adapted for a corresponding combination of a particular
`electronic accessory and a particular reconfigurable control
`panel. The human-machine interface controller responds to
`a coupling of an electronic accessory to the expandable
`interconnection link by checking the local archive for pres
`ence of a desired interface Specifier corresponding to the
`electronic accessory and the reconfigurable control panel. If
`the desired interface Specifier is not present in the local
`archive, then the wireleSS transceiver is activated to auto
`matically obtain the desired interface Specifier from the
`remote archive.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`FIG. 1 is a front, plan view of a reconfigurable display
`employing the present invention.
`FIG. 2 is a Schematic diagram showing the overall net
`work System of the present invention.
`FIG. 3 is a block diagram showing the interaction of
`Software objects for forming a human-machine interface and
`its interaction with the reconfigurable display.
`FIG. 4 illustrates the main tasks executed when a new
`device is joined into the vehicle network.
`DETAILED DESCRIPTION OF PREFERRED
`EMBODIMENTS
`The present invention creates a device portal within a
`network architecture having a dynamically constructed
`human-machine interface (HMI). A control panel/display
`Subsystem includes a collection of hard and Soft controls and
`is made available as a network resource on a dynamic local
`network. The display Subsystem of the device portal may
`include Standard embedded features Such as an audio tuner
`or CD player, but its main purpose is to be dynamically
`reconfigurable to interact with other network resources via a
`collection of Standard protocols. These other network
`resources include devices Such as a navigation System,
`cellular phone, audio player, a palm-size PC, or any other
`device employing an HMI in the vehicle. These devices need
`not be present in the network at all times. Using Java/Jini
`technology or similar technology, a dynamic network can be
`constructed which allows automatic installation of devices
`into the network.
`Referring to FIG. 1, a control panel/display subsystem 10
`includes a multi-element graphical display 11. A plurality of
`push buttons 12-17 provide soft keys for accessing func
`tions as identified by graphic/text labels displayed on display
`screen 11. Hard controls include a knob 18 which is pressed
`to control System power and can be rotated to control audio
`Volume. An arrow pad 19 is used to navigate through menus
`displayed on display Screen 11. An enter button 20 and a
`
`AHM, Exh. 1006, p. 5
`
`

`

`3
`back button 21 are also used to navigate through menu
`screens. A plurality of shortcut buttons 22-26 are provided
`to create Shortcuts to menu Screens for device functionality
`embedded in Subsystem 10 (e.g., CD player or AM/FM
`radio).
`An HMI for a particular electronic accessory device
`includes graphical display elements to identify the device
`and its available features. A menu Screen for each accessory
`device includes labels to be displayed associated with par
`ticular soft keys 12-17 to identify controllable functions of
`the device. For the electronic accessory of a cellular phone,
`the Soft keys may be associated with cellular phone func
`tions of accessing memory locations, initiating a call, ending
`a call, or other functions performable by the phone. Display
`Screen 11 can also be used to display event information as
`communicated from the cellular phone, Such as connection
`Status, duration of call, and other information communicated
`by the cellular phone to display Subsystem 10.
`The use of the reconfigurable display Subsystem as a
`device portal in a dynamic local network is shown in FIG.
`2. Reconfigurable display Subsystem 30 includes a display
`screen 31 and hard and soft keys 32. Display subsystem 30
`may also receive input commands from a voice recognition
`unit 33. An HMI controller 34 resides in display subsystem
`30 and controls graphical display Screen 31, monitors keys
`32, accepts input from voice recognition (VR) unit 33, and
`interfaces with devices on the dynamic local network 36. A
`memory 35 stores interface Specifiers (i.e., drivers) used by
`controller 34 to drive graphic display screen 31 and to
`communicate with the various electronic accessory devices
`on dynamic local network 36.
`Each particular display Subsystem ("device portal')
`design is uniquely identified by a type identifier. Thus,
`display subsystem 30 is identified as type 0, while additional
`display Subsystems which may be connected to the local
`dynamic network 36 have different identifiers such as type
`1 for a display subsystem 37 and type n for a display
`Subsystem 38.
`Dynamic local network 36 includes a collection of soft
`ware and communication specifications and Standard proto
`cols for hardware interconnection. Examples of Such a
`system are Jini by Sun Microsystems, Inc., JetSend by
`Hewlett-Packard, and Bluetooth by the Bluetooth Special
`Interest Group. System resources Such as reconfigurable
`display Subsystems, electronic accessories or other compo
`nents can join the network automatically once they are
`connected to it. Network 36 recognizes the coupling of a
`new device to the network and interacts with all the network
`resources as appropriate to enable operation of the new
`device within the network. Examples of electronic accesso
`ries connected to the network in FIG. 2 include a cellular
`phone 40, an MP3 audio player 41, and a palm-sized PC or
`personal digital assistant (PDA) 42. Once connected to the
`network 36, these accessories will communicate core func
`tionality control signals and messages with a particular
`display Subsystem. Thus, the accessory and the reconfig
`urable display Subsystem will eXchange messages concern
`ing control actions and State changes or events but would not
`include Specific messages on how to display messages or
`how the display is to be driven.
`Each device 40-42 includes a unique device type identi
`fier. Each device type may interact with a predetermined
`reconfigurable display type using an interface Specifier
`developed for the combination of device and display Sub
`system. Thus, when HMI controller 34 detects the presence
`of a new electronic accessory, it determines the device type
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,559,773 B1
`
`15
`
`25
`
`4
`for the accessory and checks whether it currently has an
`interface Specifier to Support interaction with the device
`stored in memory 35. If the desired interface specifier is
`present, then HMI controller 34 can communicate core
`functionality messages between the reconfigurable display
`and the accessory device. If an appropriate interface Speci
`fier is not already contained in memory 35, then HMI
`controller 34 takes Steps to retrieve an appropriate interface
`Specifier, if possible.
`A memory in each reconfigurable display Subsystem
`provides a local archive for Storing a plurality of interface
`Specifiers each of which defines interaction between the
`reconfigurable display Subsystem and a respective electronic
`accessory. Whenever an additional interface Specifier must
`be retrieved, it may preferably be obtained using a universal
`resource locator (URL) of a server that contains a further
`collection of HMI interface specifiers. Such a server may
`also be a local archive in the vehicle directly connected to
`dynamic local network 36 as shown by a server 43 in FIG.
`2. Server 43 is a local server containing a first group of HMI
`interface Specifiers 44 corresponding to the configurable
`display type Zero. Additional HMI interface specifiers are
`Stored in other groups for other reconfigurable display types
`as shown. For each reconfigurable display type, a plurality
`of interface Specifiers are Stored as indexed by device type.
`Server 43 may be constructed with some interface specifiers
`contained in a read-only memory (ROM) in order to provide
`a fixed set of interface Specifiers for a known Set of elec
`tronic accessories which are expected to be utilized in a
`particular vehicle. In addition, re-writeable memory may
`also be included for Subsequent Storage of interface Speci
`fiers for other device types in order to provide flexibility for
`growth.
`In order to accommodate electronic accessory devices not
`included in local Server 43, the present invention also
`provides access to a remote archive web server outside the
`vehicle. Thus, a wireless modem 45 is interconnected with
`dynamic local network 36 and can be used to communicate
`with a remote wireless modem 46 which is connected to a
`remote web server 47 containing additional interface Speci
`fiers in a remote archive. Remote server 47 may be con
`nected to the world-wide web or internet and wireless
`modem 46 may be connected to an internet Service provider
`(ISP), for example. The URL address for remote server 47
`may be a predetermined address as defined by convention
`and stored in either local server 44 or HMI controller 34, for
`example. Preferably, the URL address of an remote archive
`may be obtained directly from each accessory device itself.
`Thus, cellular phone 40 stores a remote archive address
`providing the URL to the other resources on dynamic local
`network 36. Thus, cellular phone 40 stores URL of
`www.Visteon.com/hmicode where an appropriate interface
`Specifier corresponding to cellular telephone device type 0
`and a plurality of reconfigurable display types are Stored.
`Thus, as new electronic accessory devices are developed,
`interface Specifiers can also be developed in order to inter
`face the new device with the existing reconfigurable display
`types. The location from where these interface Specifiers can
`be retrieved is Stored in the new accessory device, thus
`making the device compatible with all reconfigurable dis
`plays of those types.
`FIG. 3 shows the various software elements required in
`the System of FIG. 2, including Software elements compris
`ing the HMI itself, (i.e., the interface between the display
`Subsystem and the accessory device and Software for driving
`the display). Thus, a human-machine interface Software
`element 50 provides application objects for a particular
`
`AHM, Exh. 1006, p. 6
`
`

`

`S
`accessory Such as climate control, radio tuner, wireleSS
`information Service, e-mail, cellular phone, audio, CD
`player, or others. These objects interact with other objects in
`an HMI widgets component library 51 including such
`objects as button metaphor (i.e., button icon and identifica
`tion of corresponding Soft key), list box, window, text box,
`time, and others. These objects interact with graphics primi
`tives 52 providing a graphics device interface. These graph
`ics primitives define vector shapes, raster elements, perform
`window management, and provide graphic attributes. These
`primitives interact with software for display frame buffer 53
`for managing display activation Such as target Selection,
`Visibility Selection, and drawing mode.
`More specifically, an interface specifier which would be
`downloaded from either a local or a remote archive contains
`compiled Software class objects that collectively implement
`an application Specific HMI for the unique display driver/
`accessory device combination. In a Java implementation,
`these objects will be precompiled from JavaSource code into
`Java bytecodes which are the instructions that run on the
`Java Virtual machine (JVM). Some of these downloaded
`objects implement an overall HMI for the specific class of
`application of the accessory device, Such as cellular phone,
`compact disc player, or address book. Some of the other
`downloaded objects are generic (i.e., application
`independent) and can be applied to a wide range of appli
`cations. These generic, reusable components or widgets may
`typically already reside in the display Subsystem, but may be
`included in a downloaded interface Specifier for complete
`neSS and flexibility to use display Subsystems not already
`containing the widgets. Downloading may include the capa
`bility to identify objects already residing in the display
`Subsystem and then only downloading objects which are in
`fact needed.
`The behavior of a particular HMI is embedded in the
`collection of class objects within the interface Specifier and
`include four main functional areas: 1) processing user input
`events, 2) processing device events, 3) rendering graphic
`displays, and 4) sending commands to devices.
`User input events are generated when a user manipulates
`a control actuator of the display Subsystem, Such as pressing
`a button, issuing a voice command, manipulating the point
`ing device Such as a mouse or track ball, or otherwise
`initiates a control action. Physical device events are repre
`Sented by Software abstractions and are reported to the
`accessory device via the dynamic local network. Examples
`of physical device events include button pressed, button
`held, button released, Switch closed, Switch opened, pointing
`device position change, pointing device pressed, pointing
`device held, and pointing device released. The control
`actuator being used may be physically contained on the
`display Subsystem or may be remotely connected to the
`display Subsystem, Such as a pointing device mounted on a
`Steering wheel in the vehicle.
`Objects for processing device events provide notification
`to the display Subsystem of State changes occurring within
`the electronic accessory device. Specific device events
`depend upon the functionality of the particular electronic
`accessory device. For an electronic accessory device pro
`Viding navigation features, examples of device events
`include notification of a pending route maneuver, vehicle
`approaching destination, vehicle off-route, and others.
`With regard to Software objects to render graphics on the
`Visual display, these objects respond to user input or device
`or System events (e.g., power-up initialization) to initiate and
`execute all required rendering operations. The HMI inter
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,559,773 B1
`
`15
`
`25
`
`6
`face Specifier embeds the knowledge of how to display the
`information, including font size, Screen location, number of
`digits, size and shape of graphic elements, timing for ani
`mated components, etc.
`The Software objects include those that send predeter
`mined commands to the electronic accessory devices in
`order to enable the user to control and monitor the devices.
`Some typical examples include incrementing or decrement
`ing a CD track Selection, Selecting an FM radio pre-Set,
`adjusting the time-of-day clock, Setting climate control
`temperature or fan Speed, dialing a phone number, and
`others. The Specific implementation of the user interface
`Specifier can enable these actions in many different ways.
`These objects correlate user input events with the corre
`sponding control action.
`A preferred method of the present invention will be
`described in connection with FIG. 4. The sequence of steps
`shows interaction between an accessory device 60, a recon
`figurable display Subsystem 61, and a Server 62 containing
`an archive of interface Specifiers. Device 60 is a pluggable
`device such as a cellular phone, palm-size PC, or MP3
`player and is identified via a device type identifier which is
`embedded into the device's persistent storage, such as ROM
`or FLASH. Persistent storage also contains a universal
`resource locator (URL) that indicates the location of an HMI
`Server containing interface Specifiers corresponding to the
`device. Display subsystem 61 likewise has its own display
`type identifier embedded into persistent Storage. Server 62
`may be a local Server or a world-wide Web Server containing
`collections of HMI interface specifiers for the various dis
`play Subsystem and accessory device combinations. The
`Server processes requests for interface Specifiers which
`include the device type identifier and the display type
`identifier. The first phase of the process is registration. In
`registration, device 60 communicates its presence to
`resources on the dynamic local network and provides its
`device type identifier and the URL of a Server containing a
`collection of interface Specifiers corresponding to the
`device. The second phase of the process is an HMI check in
`which the display subsystem 61 checks to see if it already
`has an interface Specifier Supporting the accessory device
`represented by the device type identifier. If a Supporting
`interface Specifier is already present, then the device auto
`matically begins to use the display Subsystem as a device
`portal.
`If a Supporting interface Specifier is not present, then the
`third phase of the process is entered which comprises an
`HMI request. This phase includes attempting to connect to
`the server specified by the device. If connection is
`Successful, the display Subsystem communicates the device
`type identifier and the display type identifier to the Server.
`HMI report is the fourth phase of the process. Once the
`Server Successfully receives a request it checks its archive of
`HMI interface specifiers for a match as defined by the
`display type identifier and device type identifier. If a match
`is found, it returns the interface Specifier packaged as a Java
`archive (JAR) file, for example. If not, it sends a message
`Specifying that no interface Specifier is available for the
`device/display combination. In the clean-up phase, display
`Subsystem 61 responds to the information obtained from the
`Server. If the Server indicated that no interface Specifier was
`available, then the display Subsystem indicates an error
`condition to the user. If a JAR file was successfully returned,
`then the display Subsystem extracts and installs the new
`Software objects automatically to allow the display Sub
`System to act as a device portal for the installed device.
`In order to minimize the amount of memory required for
`Storing interface Specifiers, and to Simultaneously reduce
`
`AHM, Exh. 1006, p. 7
`
`

`

`7
`download times required, a memory manager or caching
`technique is used for Storing interface Specifiers. Preferably,
`a memory in any individual Subsystem is large enough to
`hold interface Specifiers to Service the complete maximum
`load of accessory devices that may be in operation using the
`display Subsystem at any one time. Since Some devices may
`be disconnected after having been used in the System, Some
`interface Specifiers may be present in memory in a display
`Subsystem for which the original accessory device is no
`longer present in the network. According to the present
`invention, any Such inactive interface Specifier is given a
`lower priority than active interface Specifiers. Furthermore,
`the longer an interface Specifier has been inactive, the lower
`priority it is given relative to other inactive interface Speci
`fiers. If the amount of remaining free memory becomes
`restricted, the HMI controller deletes the lowest priority
`interface Specifiers to make room for additional interface
`Specifiers for other accessory devices that have joined the
`network. Priority assignments may also take into account
`file Size and/or frequency of use So as to minimize overall
`downloading to restore interface Specifiers that have been
`deleted.
`Local server 43 in FIG. 2 may also contain a memory
`manager 48 for Similarly managing prioritizing and/or dele
`tion of HMI interface specifiers to most effectively use
`Storage space in Server 43.
`With regard to the dynamic local network, this may take
`the form of an RF-wireless network using the Bluetooth
`Specification, for example. When a wireleSS-capable acces
`Sory comes within communication distance of the dynamic
`local network, this is detected by means of a wireleSS polling
`Signal eXchanged between the local network and the new
`device. Based on a response to the polling signal, the devices
`eXchange network messages to establish the new device as
`a resource available to devices on the local network.
`What is claimed is:
`1. An electronic accessory display/control System for a
`transportation vehicle, comprising:
`a reconfigurable control panel having a Visual display for
`displaying menu items for an electronic accessory and
`having at least one control actuator;
`a human-machine interface controller coupled to Said
`reconfigurable control panel and including a local
`archive for Storing a plurality of interface Specifiers,
`each specifier defining interaction between Said recon
`figurable control panel and a respective electronic
`accessory for performing operations via Said menu
`items using a predetermined communications protocol;
`an expandable interconnection link for coupling compat
`ible electronic accessories with Said human-machine
`interface controller; and
`a wireleSS transceiver for accessing a remote archive of
`interface Specifiers, wherein Said remote archive
`includes interface Specifiers each adapted for a corre
`sponding combination of a particular electronic acces
`Sory and a particular reconfigurable control panel;
`wherein Said human-machine interface controller
`responds to a coupling of an electronic accessory to
`Said expandable interconnection link by checking Said
`local archive for presence of a desired interface Speci
`fier corresponding to Said electronic accessory and Said
`reconfigurable control panel, and if Said desired inter
`face Specifier is not present in Said local archive then
`activating Said wireleSS transceiver to automatically
`obtain Said desired interface Specifier from Said remote
`archive.
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,559,773 B1
`
`8
`2. The electronic accessory display and control System of
`claim 1 wherein Said desired interface Specifier assigns a
`predetermined function to Said control actuator.
`3. The electronic accessory display and control System of
`claim 1 wherein Said expandable interconnection link is
`comprised of a dynamic local network.
`4. The electronic accessory display and control System of
`claim 3 wherein Said dynamic local network is comprised of
`a wireleSS network, and wherein presence of new electronic
`accessories is detected automatically in response to a wire
`leSS polling Signal.
`5. The electronic accessory display and control System of
`claim 1 wherein Said compatible electronic accessories each
`provide to Said human-machine interface controller a unique
`device identifier and a remote network address for Said
`remote archive.
`6. The electronic accessory display and control System of
`claim 1 wherein Said interface Specifiers are comprised of
`Software objects.
`7. The electronic accessory display and control System of
`claim 6 wherein Said Software objects include objects to
`process user events initiated by Said control actuator.
`8. The electronic accessory display and control System of
`claim 6 wherein Said Software objects include objects to
`process device events corresponding to a State change within
`Said electronic accessory.
`9. The electronic accessory display and control System of
`claim 6 wherein Said Software objects include objects to
`render graphics on Said visual display.
`10. The electronic accessory display and control System of
`claim 6 wherein Said Software objects include objects to
`Send predetermined commands to Said electronic accessory.
`11. The electronic accessory display and control System of
`claim 1 further including Said electronic accessory, and
`wherein Said electronic accessory is comprised of a portable
`computing device.
`12. The electronic accessory display and control System of
`claim 1 further including Said electronic accessory, and
`wherein Said electronic accessory is comprised of a mobile
`communication device.
`13. The electronic accessory display and control System of
`claim 1 wherein Said control actuator is comprised of a push
`button Switch.
`14. The electronic accessory display and control System of
`claim 1 wherein Said control actuator is comprised of a
`Speech recognition unit.
`15. The electronic accessory display and control System of
`claim 1 further comprising a memory manager for priori
`tizing interface Specifiers Stored in Said local archive and
`deleting interface Specifiers