Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/12—Use of codes for handling textual entities
  • G06F40/14—Tree-structured documents
  • G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/451—Execution arrangements for user interfaces
  • G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation

Definitions

• the field of the present invention is electronic devices that are coupled together in a multi-source system.
• a standalone device is generally fully operative by itself, and can be selectively configured by a user.
• the SAD may or may not have its own user interface for setting its configuration.
• an external host such as a PC computer, is used to configure the SAD. Selection of a configuration generally affects functionality of the SAD, since different configurations correspond to different features.
• the driver method is used in cases where a user runs an application that controls the client behavior from a PC host, such as an MP3 player connected to a PC computer.
• the host SAD is loaded at the time of connecting the host with the client, or pre-loaded beforehand, with a software stack referred to as a "driver".
• the driver instructs the host how to send commands to the client.
• Drivers may be implemented at different software levels, from low level operating system (OS) drivers to application level drivers with user interfaces.
• a host SAD loaded with a driver is able to control the client SAD, and to configure operations of the client SAD using a communication channel between the host and the client.
• OS operating system
• the screen method is used in cases where a user browses a configuration screen at a designated IP address, such as a router or a printer connected to a PC computer. According to the screen method, the host SAD displays a graphics screen that includes information transferred from the client SAD. The host itself is unaware of the content displayed on its screen to the user, or of the actions performed by the user.
• the screen method generally uses internal browsers that are installed in host SADs, and obviates the need for OEMs to develop their own dedicated OS drivers.
• a look & feel refers to visual elements that are presented in a user interface, and include inter alia font, background color, menu design, position and shape of buttons and other controls, and arrangement of various options.
• aspects of the present invention overcome drawbacks of conventional multi- source systems, and provide methods and systems for inter-connecting two or more SADs that communicate with one another, in such a way as to maintain a unified user interface look & feel.
• a user experiences the same-looking interface when he switches from a host configuration screen to a client configuration screen. Both screens have the same look & feel, and a client SAD appears transparent to the user and does not appear as a foreign device.
• a client SAD is aware of the specific host SAD connected thereto, and adapts its screen graphics to the host's user interface. As such, the same user interface displays both host and client configurations and a unified look & feel is maintained.
• the present invention is of particular advantage with multi-source systems where a client SAD is connected to one of multiple host SAD's. Methods of the present invention ensure that the user experiences a homogenous look & feel in each host SAD source, when he navigates from the host configuration screen to the client configuration screen.
• the present invention provides methods and systems for on-line configuration of controlled software, which flexibly support a client connected to one of multiple hosts yet retain the same operational control over the client, and which adapt the look & feel so as to integrate the client control software in the host software environment in a homogeneous way.
• a host SAD is used to configure the multi-source system, and the host user interface is maintained as a fixed point of reference for the user. Adaptation to the host user interface is carried out in each client SAD.
• the present invention is advantageous for a network of auxiliary display devices connected to a computer.
• the present invention introduces a bridge device that displays information on the bridge device screen according to the look & feel of auxiliary display devices connected thereto.
• the present invention enhances the SideShowTM architecture of Microsoft, by enabling a bridge device to display a plurality of display device's information, and by enabling one display device to display another display device's information, with the look & feel of the other display device.
• a bridge system for auxiliary display devices connected to a computer including a computer running a plurality of mini-programs, each mini-program sending information of a specific nature from the computer to a corresponding auxiliary display device, for presentation to a user, a plurality of auxiliary display devices, each auxiliary display device including an auxiliary screen and each auxiliary display device having look & feel display parameters, for receiving information from the corresponding plurality of mini-programs, and for displaying the received information on the auxiliary screens according to the corresponding look & feel parameters, and at least one bridge device coupled to the computer, each bridge device coupled to at least one of the auxiliary display devices, each bridge device including a bridge screen, and each bridge device receiving information from a corresponding at least one of the mini-programs, forwarding the received information to the at least one of the auxiliary display devices, and displaying the received information on the bridge screen according to the look & feel display parameters of the at least one of the auxiliary display devices.
• a method for managing auxiliary display devices connected to a computer including receiving XML information of a specific nature from a mini-program running on a computer, and receiving look & feel parameters from an auxiliary display device that displays information in a display format conforming to the look & feel parameters, for presentation to a user, transforming the XML information to a BMP image conforming to the look & feel parameters of the auxiliary display device, transmitting the BMP image to the auxiliary display device for presentation to the user, receiving an indication of an action performed by the user on the auxiliary display device in response to viewing the BMP image, generating a second BMP image based on the received indication, conforming to the look & feel parameters of the auxiliary display device, and further transmitting the second BMP image to the auxiliary display device for further presentation to the user.
• a method for managing auxiliary display devices connected to a computer including receiving XML information of a specific nature from a mini-program running on a computer, and receiving look & feel parameters from an auxiliary display device that displays information in a display format conforming to the look & feel parameters, for presentation to a user, transforming the XML information to a BMP image conforming to the look & feel parameters of the auxiliary display device, transmitting the BMP image to the auxiliary display device for presentation to the user, receiving additional XML information from the mini-program, generating a second BMP image based on the additional XML information, conforming to the look & feel parameters of the auxiliary display device, and further transmitting the second BMP image to the auxiliary display device for further presentation to the user.
• FIGS. IA and IB, FIGS. 2A and 2B, and FIGS. 3 A and 3B are displays of various configuration screens for a host SAD and a client SAD connected together within a multi- source system, wherein the host and client screens are controlled so as to have the same look & feel, in accordance with an embodiment of the present invention
• FIG. 4 is a simplified block diagram of a multi-source system with a uniform interface for configuring a host and a client, in accordance with an embodiment of the present invention
• FIGS. 5A, 5B and 5C are simplified flowcharts of three embodiments of a method for controlling a configuration interface for a client SAD so as to conform to the look & feel of a configuration interface for a host SAD, in accordance with an embodiment of the present invention
• FIG. 6 is an illustration of button keys for a multi-source system that have different key assignments for host mode and client mode, but a common look & feel user interface for setting host and client configuration parameters, in accordance with an embodiment of the present invention
• FIG. 7 is a prior art block diagram of auxiliary display devices connected to a computer
• FIG. 8 is a simplified block diagram of auxiliary display devices and bridge devices connected to a computer, in accordance with an embodiment of the present invention.
• FIG. 9 is a simplified flow chart of a method for generating a display on a bridge device according to look & feel parameters of an auxiliary display device.
• FIG. 10 is a simplified flow chart of a method for a client to control the display information sent to it by a host, in accordance with an embodiment of the present invention.
• aspects of the present invention relate to multi-source systems with interconnected standalone devices (SADs), where one of the SADs serves as a host device, and is used to configure itself and to configure the client devices in the system.
• the client devices adapt the look & feel of their configuration screens so as to conform to the look & feel of the host configuration screen.
• the host interface look & feel thereby serves as a fixed and familiar point of reference for a user of the multi-source system.
• the look & feel of an interface relates to visual elements that a user experiences when he interacts with the interface.
• the look & feel includes inter alia: • screen size (pixel width and height);
• background color and background pattern e.g., BMP or JPG image, or multiple images for animation
• menu type e.g., scroll with items selected marked by highlight or zoom
• transitional entry effects e.g., flip, zoom
• screen and button topology e.g., location of specific buttons on the screen, such as the X button at the top-right corner of a window for closing the window
• menu topology e.g., location of items in a specific menu
• screen template e.g., usage and position of general progress keys, such as Next, Back, Cancel and Enter.
• look & feel parameters may be defined in an XML document.
• Such an XML document make, for example, take the form provided below.
• FIGS. IA and IB 5 FIGS. 2A and 2B, and FIGS. 3 A and
• FIG. IA is a media player, such as an MP3 player
• the client shown in FIG. IB is a cell phone.
• Shown in FIG. IA is a sample interface for the host.
• the screen shown in FIG. IA corresponds to the host configuration screen, before the client is connected to the host, and the screen shown in FIG. IB corresponds to the client configuration screen, after the client is connected to the host. It is noted that both screens have the same look & feel. Specifically, when the client SAD is attached to the host SAD, the font size, type and color remain the same, and the screen size and background color remain the same.
• the screen template is preserved for two "soft-keys" 110 and 120 and a bar 130 above them that includes their corresponding function names.
• Soft keys are multifunction keys that use part of a display to identify their function at any moment. Soft-keys are generally located directly below the display.
• FIG. IA soft keys 110 and 120 correspond respectively to Vol. Up and Vol. Down functions, as indicated by bar 130; and in FIG. IB soft keys 110 and 120 correspond respectively to Call and End functions, respectively, as indicated by bar 130.
• the host shown in FIG. 2A is a digital camera, and the client shown in FIG. 2B is another electronic device. Shown in FIG. 2A is a sample interface for the host. Again, in accordance with the present invention, the look & feel of FIG. 2B (client configuration) is the same as that of FIG. 2A (host configuration). As may be seen in FIGS. 2A and 2B, the look & feel of the configuration interface includes a left panel 210 and a right panel 220. The left panel 210 is created by the host. When the client is attached to the host, the left panel may be altered by the host. Thus in FIG. 2B the left panel includes a control element 230 in the shape of a star, for toggling between host mode and client mode.
• the right panel 220 is controlled by the host when the host mode is running, and controlled by the client when the client mode is running. In either case, the content displayed in the right panel conforms to the look & feel parameters for the host.
• the "look parameters" of the right panel including inter alia the dimensions of the right panel, its background color, its font type, size and color, and its menu header and location, are the same in FIGS. 2 A and 2B.
• the "feel" parameters of the right panel including inter alia assignment of client options 1, 2 and 3 to corresponding host buttons and the jog dial options, are also the same in FIGS. 2A and 2B.
• the host shown in FIG. 3 A is a GPS navigator, and the client shown in FIG. 3B is another electronic device. Shown in FIG. 3A is a sample interface for the host. Again, in accordance with the present invention, the look & feel of FIG. 3B (client configuration) is the same as that of FIG. 3 A (host configuration). For example, it is noted that the "X" remains in the top right corner when the client is attached to the host.
• FIG. 4 is a simplified block diagram of a multi-source system with a uniform interface for configuring a host and a client, in accordance with an embodiment of the present invention. Shown in FIG. 4 is a host SAD
• Client SAD 450 includes a CPU 460, an optional display 470 and an optional power source 480.
• Client SAD also includes a configuration program 490, which enables a user to select configuration settings for client
• Host SAD 400 and client SAD 450 communicate via respective communication modules 405 and 455 over a communication channel 415.
• Communication channel 415 may be a physical or a wireless channel.
• Host look & feel parameters 440 are transmitted by communication module 405 over communication channel 415, and received by communication module 455. In turn, the look & feel parameters are transmitted to configuration program 490.
• Configuration program 490 has a default screen look & feel. In accordance with an embodiment of the present invention, configuration program 490 adapts its look & feel accordingly, so as to conform to look & feel parameters 440 of host SAD 400.
• Configuration program 490 generates a graphics screen image that conforms to look & feel parameters 440.
• the graphics screen image is transmitted to communication module 455, which transmits it further to communication module 405 over communication channel 415.
• the graphics image is then transmitted to host display 420, for display to a user.
• the commands are transmitted via communication channel 415 back to configuration program 490, which generates successive graphics screen images in response to the user commands.
• the successive graphics screen images are transmitted to display 420 for further display to the user. Reference is now made to FIG.
• FIG. 5 A which is a simplified flowchart of a first embodiment of a method for controlling a configuration interface for a client SAD so as to conform to the look & feel of a configuration interface for a host SAD, in accordance with an embodiment of the present invention.
• the flowchart of FIG. 5A is divided into three columns.
• the leftmost column indicates steps performed by a user who is operating a multi- source system including the host SAD and the client SAD.
• the middle column indicates steps performed by the host SAD, and the rightmost column indicates steps performed by the client SAD.
• the client device is attached to the host device.
• the host transfers its own look & feel parameters to the client.
• the host look & feel parameters may be specified in an XML document.
• the host may also transfer requisite font files, for fonts specified in the look & feel parameters.
• the client adapts the look & feel of its configuration program according to the host look & feel parameters.
• the client configuration program
• I generates a configuration screen, in the form of a bitmap image, that conforms to the look & feel of the host configuration screen.
• the host receives the bitmap image of the configuration screen from the client, and at step 518 the host displays the bitmap image, which conforms to the host look & feel.
• the user interface displayed by the host preserves a unified look & feel, even when being used to configure the client.
• the host displays its own configuration options and the client configuration options on the same screen, and with a common look & feel.
• the host may display both configurations at the same time, or may switch between host options and client options, but in each case the same visual user interface is presented to the user.
• the user interacts with the system and issues a command, the response to which may require a change in the display screen.
• the host sends the client notification of the user command.
• the client configuration program generates a new bitmap image for a configuration screen, in response to the user command, as appropriate.
• the host receives the new configuration screen, in the form of the new bitmap image, from the client.
• the host displays the altered screen, which again conforms to the look & feel of the host. The method then returns to step 521, as the user continues to interact with the system.
• FIG. 5B which is a simplified flowchart of a second embodiment of a method for controlling a configuration interface for a client SAD so as to conform to the look & feel of a configuration interface for a host SAD, in accordance with an embodiment of the present invention.
• the flowchart of FIG. 5B is divided into three columns.
• the leftmost column indicates steps performed by a user who is operating a multi- source system including the host SAD and the client SAD.
• the middle column indicates steps performed by the host SAD, and the rightmost column indicates steps performed by the client SAD.
• the method of FIG. 5B uses a web interface for a user to configure the client device.
• the client device is attached to the host device.
• the host device transfers is look & feel parameters to the client device.
• the host may also transfer requisite font files, for fonts specified in the look & feel parameters.
• the client configuration program sets it parameters according to the host look & feel parameters.
• the client configuration program generates a web page, which conforms to the host look & feel parameters.
• the client device uploads the web page to a URL on a web server.
• the host using a web browser installed therein, browses the URL and renders and displays the web page. Referring back to FIG.
• host device 400 includes a web browser 445, which browses and renders web pages stored in a web server 495.
• the web pages are generated by configuration program 490 so as to comply with host look & feel parameters 440, and are uploaded to web server 495.
• a user who is viewing the web page displayed at step 551 issue a user command.
• the host sends the user command to the client.
• the client configuration program generates a new web page, in response to the user command, as appropriate.
• the client uploads the web page to a URL on the web server.
• the host browses the URL and renders and displays the new web page. The method then returns to step 554, as the user continues to interact with the system.
• FIG. 5C is a simplified flowchart of a third embodiment of a method for controlling a configuration interface for a client SAD so as to conform to the look & feel of a configuration interface for a host SAD, in accordance with an embodiment of the present invention.
• the flowchart of FIG. 5 C is divided into three columns.
• the leftmost column indicates steps performed by a user who is operating a multi- source system including the host SAD and the client SAD.
• the middle column indicates steps performed by the host SAD, and the rightmost column indicates steps performed by the client SAD.
• the client device is attached to the host device.
• the client transfers its configuration program to the host, thus enabling the host to generate the appropriate user interfaces.
• the host sets parameters of the client's configuration program corresponding to the host look & feel parameters.
• the host by itself generates a screen image for client configuration, running the client's configuration program.
• the host displays the screen image.
• a user who is viewing and interacting with the user interface issues a command.
• the host generates a new screen image, in response to the user command, as appropriate, running the client's configuration program.
• the host displays the new screen image. The method then returns to step 584, as the user continues to interact with the system. It will thus be appreciated by those skilled in the art that the methods of FIGS.
• 5 A, 5B and 5 C enable a host SAD in a multi-source system to display both host configuration settings and client configuration settings on the host screen, simultaneously, with a uniform look & feel. As such, a user of the system experiences a homogeneous interface, and it is transparent to the user that two different SADs are operating.
• TABLES IA and IB Shown in TABLES IA and IB are example button key assignments for a host mode and a client mode, respectively, within a multi-source system.
• TABLES IA and IB correspond to FIGS. IA and IB, respectively, where the host is an MP3 player running in media player mode, and the client is a cell phone running in dialer mode.
• the buttons of the system are labeled Bl - B 15, together with a TOUCH button on the touch screen displayed with a question mark.
• the buttons have one assignment of functions in host mode and another assignment of functions in client mode.
• Button B8, for example, is assigned a play function in TABLE IA, and is assigned a function to enter the numeral "8" in TABLE IB.
• buttons Bl - B12 correspond to the four rows of three buttons on the keypad, in the order from top left to bottom right.
• Buttons B13 and B 14 correspond to the soft keys 110 and 120 in FIGS. IA and IB.
• Button Bl 5 corresponds to the speaker button. It is also noted that buttons B4, B6, B13 and B 14 have dual functions, corresponding to a short duration press and a long duration press. Key-press and key-release events may be analyzed so as to distinguish between long duration short duration presses.
• the key assignments When running in host mode, the key assignments correspond to media player key assignments, as in TABLE IA. However, when running in client mode, the key assignments correspond to conventional cell phone key assignments, as in TABLE IB. It may be seen from TABLE IA that in host mode, buttons B5 and Bl 5 are not used, and long button presses are not distinguished from short presses.
• the host key assignments such as shot indicated in TABLE IA, are used. Switching between host mode and client mode niay be performed, for example, using a toggle switch such as control element 230 in FIG. 2B.
• the client sends the host a list of user functions it supports, such as the various functions indicated in TABLE IB. The host then assigns the functions to buttons, and sends the client the key assignments.
• the graphic image displayed on the host screen, or a portion of the graphic image that is assigned to the client is generated by the client and transmitted to the host for display.
• the button press event is sent to the client, and translated by the client according to the key assignment for that button.
• the client If the user presses a touch screen, then the X-Y coordinates of the press location are send to the client.
• the client In response, the client generates a new graphic image, conforming to the look & feel parameters that the client received from the host.
• the new graphic image is transmitted to the host for display, thus completing a cycle of user input and screen display in response to the input. Generally, several such cycles are performed in an interactive session.
• the host may do the analysis to make the distinction and pass the result (long press or short press) to the client.
• the host may send the key- press and key-release events to the client, and the client then determines the type of press (long or short) from these events.
• FIG. 7 is a prior art block diagram of auxiliary display devices connected to a computer. Shown in FIG. 7 is a computer 710 with an input device 720 such as a keyboard or mouse. Computer 710 is connected to multiple auxiliary display devices 731 - 739. Each auxiliary display device is used to display information stored on computer 710, such as e-mail messages, calendar reminders, or such other notifications.
• Auxiliary display devices 731 — 739 include inter alia mobile phones, GPS navigators, remote controls with built-in screens, keyboards with built- in screens, wearable display devices, music players, digital picture frames, game stations, home entertainment systems, and such other consumer electronic (CE) devices.
• CE consumer electronic
• An auxiliary display device may be embedded within computer 710, such as an in-lid attached laptop display.
• An auxiliary display device may be a separate peripheral device connected to computer 710 by a wired or wireless connection, including inter alia USB, Bluetooth, TCP/IP or other such data communication protocols, existing now or to be developed in the future.
• An auxiliary display device may also be a designated area within a main screen of computer 710.
• Such gadgets include (i) a calendar gadget that periodically retrieves data from a calendar application such as Microsoft Outlook ® , and sends the data to an auxiliary display device, (ii) a weather gadget that retrieves data from a web service and updates an auxiliary display device with weather information in designated locales, and (iii) an instant messaging gadget that provides presence information regarding a user's buddies on an auxiliary display device.
• auxiliary display devices 731 - 739 require that auxiliary display devices 731 - 739 be able to interpret the Simple Content Format (SCF) and, optionally the iCalendar data format.
• SCF defines a set of XML elements and attributes that allow content, dialog and menu pages to be sent to auxiliary devices 731 - 739.
• SCF enables extended custom content types to be defined.
• Auxiliary display devices 731 - 739 may be powered even when computer 710 is in a low-power mode such as standby mode or hibernate mode.
• Auxiliary display devices 731 - 739 behave as client devices, which receive their data from their corresponding gadgets running on computer 710, which behaves as a host. This is indicated in FIG. 7 by referring to display devices 731 - 739 as client #1 - client #9, respectively, and by referring to computer 710 as host computer.
• the designation of a device as host or client in FIG. 7 relates to the display of information.
• a host device sends display information to a client device, which the client device displays on its screen.
• Display devices 731 - 739 do not manipulate data that they display, and such data remains within the auxiliary display devices and is not transmitted elsewhere. Moreover, if an auxiliary display device has an internal application, then such application is not shared with other devices. As such, display devices 731 - 739 are dumb terminals.
• FIG. 8 is a simplified block diagram of auxiliary display devices and bridge devices connected to a computer, in accordance with an embodiment of the present invention. Shown in FIG. 8 is a computer 810 with an input device 820 such as a keyboard or mouse, and auxiliary display devices 831 - 839. FIG. 8 also includes two devices 841 and 842, referred to as bridges, with respective input devices 851 and 852.
• Bridges 841 and 842 are connected directly to computer 810 and connected directly to one another.
• Auxiliary display devices are arranged so that devices 831 - 833 are connected to bridge 841, device 834 - 836 are connected to bridge 842, and devices 837 — 839 are connected directly to computer 810.
• Bridges own two types of gadgets; namely, (i) gadgets generated from their own internal running applications, and (ii) gadgets inherited from other devices.
• bridge 841 owns its own gadgets, as well as gadgets inherited from host computer 810 and from bridge 842.
• Auxiliary display devices generally do not own gadgets, and can only display information from gadgets that are presented to them.
• Bridge devices 841 and 842 combine capabilities of host computer 810 and client devices 831 - 839. As clients, bridge devices 841 and 842 receive display information from other devices and present the display information on their own screens. As hosts, bridge devices 841 and 842 act as source of display information for display on client device screens. For example, bridge 841 may receive display information from computer 810 or from clients 842 and 843 and display such information on its own screen; and conversely, bridge 841 may transmit display information to computer 810 or to clients 842 and 843 for display on their screens. Display information transmitted by bridge 841 may be generated by bridge 841 be internal applications running on device 841, or may be information received from other devices. Moreover, bridge 841 can combine display information that is generates from its internal applications with display information that it receives from remote devices, the latter referred to as "inherited notifications", so as to create single display information for devices that connect to bridge 841.
• computer 810 connects to bridges 841 and 842 via wireless links.
• display information is rendered as a bitmap image, it is cumbersome to transmit bitmap images over wireless links, due to their large sizes.
• computer 810 transmits display information to bridges 841 and 842 in a compressed XML format.
• Auxiliary display devices 831 - 839 generally have limited CPU power and limited software resources, and may only support simpler data, such as BMP image data.
• bridges 841 and 842 transform the display information they receive in compressed XML format to a BMP format, for forwarding to display devices 831 - 839.
• such transformation uses look & feel parameters appropriate to each corresponding display device, as described hereinabove with reference to FIGS. 5A - 5C.
• the XML -> BMP transformation performed by bridges 841 and 842 uses configuration information provided by each corresponding target display device, such as the sample XML document described hereinabove, in transforming the compressed XML data to a BMP image for the target display device.
• Bridges 841 and 842 may split their displays to include both display information provided by computer 810, as well as display information generated from internal applications running on bridges 841 and 842.
• each bridge device maintains an assignment table that holds data defining which devices owns which gadget and which client performs an operation that requires a change of display.
• General notifications such as a new e-mail message transmitted by an e-mail gadget, are distributed to all clients 831 - 839 that use this e-mail gadget.
• TABLE II is a sample assignment table maintained by bridge, device 841.
• FIG. 9 is a simplified flow chart of a method for generating a display on a bridge device according to look & feel parameters of an auxiliary display device.
• a user connects a bridge, such as bridge 841, to an auxiliary display device, such as client 831, and to a PC computer, such as computer 810.
• the bridge receives look & feel configuration parameters from client 831, and XML display information from the gadget installed on computer 810 for device 831.
• the bridge transforms the XML display information along with display information generated by applications internal to the bridge, to generate a BMP image for display on the client device, wherein the BMP image conforms to the client device's look & feel parameters.
• the client device displays the BMP image received from the bridge on its client screen.
• the user interacts with the client device and performs an action that requires a change in display.
• a notification is received from the gadget for device 831.
• the method proceeds to step 930 where the bridge generates a new BMP accordingly, as appropriate.
• the cycle of user interaction/new notifications ⁇ --> new BMP image continues.
• each host device in FIG. 8 may define which gadgets it wishes to expose to devices connected to it. The host device further designates whether each connected device either (i) has permission to further export the gadget display information to devices that are connected to it, or else (ii) is limited to displaying the gadget display information only on its own display.
• Such an extended display configuration is set up using a utility presented to the user referred to herein as a gadget configuration utility, or as a "gadget configuration gadget".
• a bridge device such as bridge 841 is a host and, as such has its own gadget configuration utility.
• the bridge presents the user with bridge internal applications that generate display information, and gadgets provided by hosts connected to the bridge, for those gadgets for which the bridge is permitted to forward their display information.
• bridge 841 presents the user with its internal applications that generate display information, and with those gadgets for host 810 and bridge 842, for which host 810 and bridge 842 are permitted to forward the gadget's display information to bridge 841.
• a client such as auxiliary display device 831
• a host may define its own configuration utility as a gadget, which in turn enables the client to control the display information sent to it by the host.
• FIG. 10 is a simplified flow chart for a method for a client to control the display information sent to it by a host, in accordance with an embodiment of the present invention.
• a host device arranges its self-owned (internal) gadgets and its inherited (external) gadgets into a gadget configuration gadget.
• the host device's gadget configuration gadget is sent to client auxiliary displays.
• a user of the client selects desired gadgets in a configuration display window.
• the user's selections are sent to the host, which alters its data content accordingly, and sends requested notifications to the client.
• auxiliary display devices 834 - 836 display gadgets on host computer 810, on bridge 841 and on bridge 842, via bridge 842; and at step 1030 the user can select some or all of these gadgets.
• auxiliary display devices as bridges
• client devices in prior art architectures behave as passive isolated displays.
• client 831 is a GPS device
• client 832 is an audio player
• client 833 is a mobile phone
• each client device 831, 832 and 833 is able to review the other clients' displays.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Software Systems (AREA)
• Physics & Mathematics (AREA)
• General Engineering & Computer Science (AREA)
• General Physics & Mathematics (AREA)
• Human Computer Interaction (AREA)
• Health & Medical Sciences (AREA)
• Artificial Intelligence (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Computational Linguistics (AREA)
• General Health & Medical Sciences (AREA)
• Digital Computer Display Output (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=40954653

Family Applications (1)

Country Status (3)

Families Citing this family (9)

Family Cites Families (97)

• 2009
  • 2009-02-18 US US12/372,812 patent/US9448814B2/en not_active Expired - Fee Related
  • 2009-02-19 EP EP09712355.8A patent/EP2248039A4/de not_active Withdrawn
  • 2009-02-19 WO PCT/IL2009/000193 patent/WO2009104185A2/en not_active Ceased

Also Published As

Similar Documents

Legal Events