(12) United States Patent
`Humpleman et al.
`
`US006182094B1
`(10) Patent No.:
`US 6,182,094 B1
`(45) Date of Patent:
`Jan. 30, 2001
`
`(54) PROGRAMMING TOOL FOR HOME
`NETWORKS WITH AN HTML PAGE FOR A
`PLURALITY OF HOME DEVICES
`
`5.956,487 * 9/1999 Venkatraman et al. .............. 709/218
`6,005,861 * 12/1999 Humpleman ............
`... 370/352
`6,097,441
`8/2000 Allport ................................. 34.8/552
`
`(75) Inventors: Richard James Humpleman, Fremont;
`OTHER PUBLICATIONS
`G. Kevin Harms; Michael S. Deacon,
`“Dawn of the Internet Appliance,” Greg Lawtom, Computer
`ET. If Rs. ": vol. 30, No. 10, pp. 16, is, Coden CPTRB4, Oct. 1697.
`both of San Jose: Omi Chandi
`s
`s
`s
`“Browser-style Interfaces to a home Automation Network.”
`(73) Assignee: Samsung Electronics Co., Ltd., Suwon
`Corcoran et al., Proceedings of the 1997 IEEE Transactions
`(KR)
`on Consumer Electronics, Voluem 43, No. 4, pp. 1063-1069,
`Nov. 1997.*
`Under 35 U.S.C. 154(b), the term of this
`patent shall be extended for 0 days.
`
`* cited by examiner
`
`(*) Notice:
`
`Primary Examiner-Hosain T. Alam
`(21) Appl. No.: 09/104,606
`(74) Attorney, Agent, or Firm-Sherman & Sherman;
`22) Filled:
`24, 1998
`Kenneth L. Sherman; Jeffrey P. Aiello
`(22) File
`Jun. 24,
`(57)
`ABSTRACT
`Related U.S. Application Data
`(60) Provisional application No. 60/050,762, filed on Jun. 25,
`1997, and provisional application No. 60/059,499, filed on A method and System for generating a program guide for a
`Sep. 22, 1997.
`home network having at least one multi-media device con
`(51) Int. Cl." .................................................. G06F 17/30
`nected thereto is provided. According to the method, multi
`(52) U.S. Cl. ............................ 707/513; 707/10, 707/104;
`media material associated with a first home device is iden
`345/352; 709/218
`tified. An HTML page is generated, based on the identified
`(58) Field of Search .............................. 707/104, 10, 501,
`multi-media material associated with the first home device.
`707/513, 1–3; 709/217-218; 34.5/355-357,
`The HTML page is stored in an accessible area on the first
`352-354
`home device. A Second home device, which is browser
`based, may be connected to the home network to receive the
`HTML page and to render the HTML page, for display to a
`USC.
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`5,940,387 * 8/1999 Humpleman ......................... 370/352
`
`17 Claims, 16 Drawing Sheets
`
`
`
`402
`
`SECURITY
`SYSTEM
`
`406
`
`Charter Ex. 1009, Page 1
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 1 of 16
`
`US 6,182,094 B1
`
`122
`
`OO
`
`
`
`DSS-NU
`
`1394 SERIAL BUS
`HTTP/IP
`
`114
`
`DTV
`
`102
`
`HUMAN
`INTERFACE
`
`
`
`BRIDGE
`PROXY
`116
`
`SECURITY
`
`120
`
`1394 SERIAL BUS
`IEC 1883
`
`11
`
`FIG. 1
`
`Charter Ex. 1009, Page 2
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 2 of 16
`
`US 6,182,094 B1
`
`
`
`99 || || NE|TO
`
`NOISSES
`
`>HE/\\/T1
`
`Charter Ex. 1009, Page 3
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 3 of 16
`
`US 6,182,094 B1
`
`
`
`
`
`
`
`
`
`
`
`
`
`HOME
`DEVICE
`
`(SERVER)
`
`
`
`
`
`
`
`204
`
`HTML FILE
`
`DTV
`
`DISPLAY TO USER
`
`(CLIENT)
`
`202
`
`BUTTON"CLICK"
`SELECTION
`
`CONTROL/COMMAND
`
`FG. 3A
`
`external
`port
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`DSS-NIU and DHCP-SERVER
`
`dhcp server/devices.html
`dSS/user.html
`set-up control program
`
`
`
`DVCRMN)-SERVER
`
`dvor/user.html
`set-up control program
`
`DTV CLIENT BROWSER
`
`dtv/user.html
`Set-up Control program
`
`FIG. 3B
`
`Charter Ex. 1009, Page 4
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 4 of 16
`
`US 6,182,094 B1
`
`HOME
`DEVICE
`
`DHCP
`SERVER
`
`PADDRESS
`
`FIG 4A
`
`
`
`
`
`
`
`DHCP
`SERVER
`310
`
`
`
`DHCP
`DATABASE 314
`
`HOME
`DEVICE
`CLIENT
`(
`) 312
`
`
`
`
`
`FIG. 4B
`
`
`
`DEVICE LIST
`FILE
`318
`
`Charter Ex. 1009, Page 5
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet S of 16
`
`US 6,182,094 B1
`
`402
`
`406 || P
`
`406
`
`SECURITY
`SYSTEM
`
`406
`
`406
`
`406
`
`
`
`DEVICE LINK
`
`12
`
`FIG. 5B
`
`
`
`
`
`
`
`
`
`ICON.gif
`PROPERTIES
`420 FILE
`420
`
`EPG.html
`
`ar
`
`420 Logo.gif 420
`Default.html
`420
`
`Charter Ex. 1009, Page 6
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 6 of 16
`
`US 6,182,094 B1
`
`
`
`502
`
`FIG. 6
`
`Charter Ex. 1009, Page 7
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 7 of 16
`
`US 6,182,094 B1
`
`
`
`606
`
`-610.
`Living Room
`
`FIG. 7
`
`Charter Ex. 1009, Page 8
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 8 of 16
`
`US 6,182,094 B1
`
`
`
`Session Manager
`Available Devices
`
`DaCS WCR
`
`12
`
`Charter Ex. 1009, Page 9
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 9 of 16
`
`US 6,182,094 B1
`
`
`
`
`
`
`
`
`
`Charter Ex. 1009, Page 10
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 10 of 16
`
`US 6,182,094 B1
`
`
`
`Session Manager
`
`Available Devices
`
`708
`
`-
`
`Programming
`Front Panel
`
`Preferences
`Channel Security
`
`Channel
`
`Brightness
`
`FIG 10
`
`Charter Ex. 1009, Page 11
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 11 of 16
`
`US 6,182,094 B1
`
`
`
`902
`
`Session Manager
`Available Devices
`
`Jims TV
`
`Dads VCR
`
`804
`arras -
`
`JimS DVD
`904
`Playing Ben Hur
`
`22.É. 708
`
`Prodrammin
`Front Panel
`
`Preferences
`Channel Security
`
`Power
`
`Channel
`
`Brightness
`
`Eject <
`
`x.
`
`Functions Front Panel
`
`y
`
`Disc Selection
`
`FIG 11
`
`Charter Ex. 1009, Page 12
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 12 of 16
`
`US 6,182,094 B1
`
`800 ||
`
`
`
`Z00 ? NOISSES
`
`9 || 0 || 7 || 0 ||
`
`
`__^
`
`ZOO) NOISSES
`
`Charter Ex. 1009, Page 13
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 13 of 16
`
`US 6,182,094 B1
`
`
`
`1014
`
`EL IDEXIME:
`
`1016
`
`1022
`
`LOGO
`
`PWR
`
`CHANNEL A.
`v
`VOLUME al
`v.
`
`1042
`
`F.G. 13
`
`Charter Ex. 1009, Page 14
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 14 of 16
`
`US 6,182,094 B1
`
`122
`
`1100
`
`1394 SERAL BUS 11
`HTTP/IP
`-
`
`DTV
`
`102
`
`HUMAN
`INTERFACE
`
`DSS-NU
`
`SERVER
`
`DVD
`
`108
`
`
`
`BRIDGE
`PROXY
`116
`
`SECURITY
`SYSTEM
`
`1394 SERIAL BUS
`IEC 1883
`
`118
`
`INTERNET
`PROXY
`1104
`
`1102
`
`FIG. 14
`
`Charter Ex. 1009, Page 15
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 15 of 16
`
`US 6,182,094 B1
`
`
`
`?SIT OJOeW
`
`0 | Z |
`
`00Z ||
`
`90Z ||
`
`ZOZ !
`
`
`
`
`
`
`
`
`
`Charter Ex. 1009, Page 16
`
`

`

`U.S. Patent
`
`Jan. 30, 2001
`
`Sheet 16 of 16
`
`US 6,182,094 B1
`
`
`
`
`
`
`
`
`
`?SIT OJOeW
`
`
`
`36ed TWILH
`
`0 | 9 ||
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Z09 ||
`
`Charter Ex. 1009, Page 17
`
`

`

`US 6,182,094 B1
`
`15
`
`35
`
`40
`
`25
`
`1
`PROGRAMMING TOOL FOR HOME
`NETWORKS WITH AN HTML PAGE FOR A
`PLURALITY OF HOME DEVICES
`CROSS-REFERENCES TO RELATED
`APPLICATIONS
`This patent application claims priority from provisional
`patent application Ser. No. 60/050,762, filed on Jun. 25,
`1997, entitled Home Network, Browser Based, Command
`and Control and provisional patent application Ser. No.
`60/059,499, filed on Sep. 22, 1997, entitled Improved Home
`Network, Browser Based, Command and Control, which are
`incorporated herein by reference.
`BACKGROUND OF THE INVENTION
`1. Field of the Invention
`The present invention relates to the field of networks, and
`more particularly, to home networks having multi-media
`devices connected thereto.
`2. Description of Related Art
`A typical household contains Several home devices. AS
`used in this document, the term “home device' encompasses
`all electronic devices that are typically found in the home,
`with the exception of general purpose computers (i.e. per
`Sonal computers (PCs), laptop computers, etc). For example,
`the term home device includes but is not limited to Such
`electronic devices as Security Systems, theatre equipment
`(e.g., TVs, VCRS, Stereo equipment, and direct broadcast
`satellite services or (DBSS), also known as digital satellite
`Services (DSS)), Sprinkler Systems, lighting Systems, micro
`waves, dish washers, ovens/Stoves, and washers/dryers.
`Indeed, an automobile may be a home device. On the other
`hand, the term “device' as used in this document may
`comprise logical devices or other units having functionality
`and an ability to exchange data, and may include not only all
`home devices but also general purpose computers.
`In general, home devices are used to perform tasks that
`enhance a homeowner's life Style and Standard of living. For
`example, a dishwasher performs the task of Washing dirty
`dishes and relieves the homeowner of having to wash the
`dishes by hand. A VCR can record a TV program to allow
`a homeowner to watch a particular program at a later time.
`Security Systems protect the homeowner's valuables and can
`reduce the homeowner's fear of unwanted entry.
`Home devices (such as home theatre equipment) are often
`controlled using a single common control unit, namely a
`remote control device. This single common control unit
`allows a homeowner to control and command Several dif
`ferent home devices using a single interface. Thus, many
`manufacturers have developed control units for controlling
`and commanding their home devices from a single interface.
`One drawback associated with using the remote control
`unit to command and control home devices is that it provides
`Static control and command logic for controlling and com
`manding each home device. Therefore, a particular remote
`55
`control unit can only control and command those home
`devices for which it includes the necessary control and
`command logic. For example, if a remote control unit
`comprises logic for controlling a television (TV), a video
`cassette recorder (VCR), and a digital video device (DVD),
`but not a compact disk (CD) unit, the remote control unit can
`not be used to command and control the CD unit. In
`addition, as new home devices are developed, the remote
`control unit will not be able to control and command the new
`home devices that require control and command logic that
`was not known at the time the remote control unit was
`developed.
`
`45
`
`50
`
`60
`
`65
`
`2
`Another drawback associated with using a remote control
`unit for controlling home devices on a home network is that,
`unlike the use of a remote control for a multi-media device
`receiving data from an external network, it has thus far not
`been possible to generate a program guide for the data
`received from a multi-media device connected to a home
`network.
`Therefore, there is a need for a method for generating a
`program guide for a home network environment wherein at
`least one multi-media device is connected to a home
`network, and wherein the data provided thereby is provided
`to a user either at that device or at another device connected
`to the home network.
`SUMMARY OF THE INVENTION
`It is accordingly an object of the invention to overcome
`the problems of the prior art, and to provide a method and
`apparatus for control of a plurality of devices connected to
`a home network.
`It is still a further object of the invention to provide a
`method generating a program guide for a home network to
`identify multi-media material associated with a home device
`connected to the home network.
`It is a more specific object of the invention to provide a
`method for controlling a plurality of devices connected to a
`home network, at least one of the devices being a multi
`media device, and for generating a program guide for the
`information provided by the multi-media device on a Second
`home device connected to the home network.
`The present invention accordingly provides a method for
`generating a program guide for a home network.
`According to one aspect of the invention, a method for
`generating a program guide for a home network, wherein the
`program guide identifies multi-media material associated
`with a first home device connected to the home network,
`includes the Steps of identifying multi-media material asso
`ciated with the first home device; generating an HTML page
`based on the identified multi-media material associated with
`the first home device; and storing the HTML page in an
`accessible area on the first home device.
`The method according to the invention may further
`include the Steps of: connecting a Second, browser based,
`home device to the home network; receiving the HTML
`page at the Second home device over the home network from
`the first home device; and rendering the HTML page on the
`Second home device, wherein the Second home device
`includes a display unit for displaying the HTML page
`rendered thereby.
`Alternatively, a custom HTML page may be generated in
`accordance with the received HTML page for display on the
`Second home device.
`AS a feature of the invention, the material used to generate
`the HTML page may be derived from information contained
`on a medium associated with the first home device. The
`information may be contained on a CD, a memory associ
`ated with a PC, a DVD or a DVCR for example.
`In accordance with another feature, the method according
`to the invention further includes the Steps of retrieving
`multiple HTML pages from multiple home devices, wherein
`the multiple home devices are connected to the home
`network; generating a custom HTML page based on the
`multiple HTML pages; and displaying the custom HTML
`page on a browser based home device, wherein the browser
`based home device is connected to the home network.
`BRIEF DESCRIPTION OF THE DRAWINGS
`The objects and features of the present invention, which
`are believed to be novel, are set forth with particularity in the
`
`Charter Ex. 1009, Page 18
`
`

`

`3
`appended claims. The present invention, both as to its
`organization and manner of operation, together with further
`objects and advantages, may best be understood by reference
`to the following description, taken in connection with the
`accompanying drawings, in which:
`FIG. 1 is a block diagram of a home network constructed
`in accordance with the present invention;
`FIG. 2 illustrates an example of a layered interface model
`that can be used for communicating between home devices
`in accordance with the present invention;
`FIGS. 3A and 3B are block diagrams illustrating control
`ling and commanding of a home device using a browser
`based Digital TV (DTV) according to one embodiment of
`the present invention and a Specific example,
`FIG. 4A is a block diagram illustrating a home device
`discovery mechanism according to one embodiment of the
`invention;
`FIG. 4B depicts a flow diagram illustrating the generation
`of a device list file according to certain embodiments of the
`invention;
`FIG. 5A is a block diagram of a device link page in
`accordance with the present invention;
`FIG. 5B illustrates an example of a home device tree
`Structure according to certain embodiments of the invention;
`FIG. 6 graphically depicts a view of a device link page in
`accordance with the present invention;
`FIG. 7 graphically depicts an alternative view diagram of
`a device link page in accordance with the present invention;
`FIG. 8 graphically depicts a preliminary view of a Session
`page in accordance with the present invention;
`FIG. 9 is a block diagram illustrating a session manager
`causing two home devices to communicate over a home
`network according to certain embodiments of the invention;
`FIG. 10 graphically depicts a secondary view of the
`Session page in accordance with the present invention;
`FIG. 11 graphically depicts a third view of the session
`page in accordance with the present invention;
`FIG. 12A is a block diagram of a Session page in accor
`dance with the present invention;
`FIG. 12B is another block diagram of the Session page in
`accordance with the present invention;
`FIG. 13 is another block diagram of the Session page in
`accordance with the present invention;
`FIG. 14 is a block diagram of a home network that is
`connected to the Internet in accordance with the present
`inventions,
`FIG. 15 is a diagram illustrating the creation of a macro
`according to one embodiment of the invention; and
`FIG. 16 is a diagram illustrating the creation of a macro
`according to another embodiment of the invention.
`DESCRIPTION OF THE PREFERRED
`EMBODIMENTS
`The following description is provided to enable any
`person skilled in the art to make and use the invention and
`sets forth the best modes presently contemplated by the
`inventors of carrying out their invention of a method and
`apparatus for controlling home devices over a home net
`work. In the following description, for purposes of
`explanation, numerous specific details are Set forth in order
`to provide a thorough understanding of the present inven
`tion. It will be apparent, however, to one skilled in the art
`that the present invention may be practiced without these
`
`15
`
`25
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 6,182,094 B1
`
`4
`Specific details. In other instances, well-known Structures
`and devices are shown in block diagram form in order to
`avoid unnecessarily obscuring the present inventions.
`In an exemplary embodiment of the present invention, a
`browser based home network uses Internet technology to
`control and command home devices that are connected to a
`home network. Each home device contains interface data
`(e.g. HTML, XML, JAVA, JAVASCRIPT, GIF, JPEG,
`graphics files, or any other format useful for the intended
`purpose) that provides an interface for the commanding and
`controlling of the home device over the home network. In
`certain embodiments, each home device contains one or
`more Hypertext Markup Language (HTML) pages that
`provide for the commanding and controlling of the home
`device. Using the browser technology, the home network
`employs Internet standards to render the HTML pages in
`order to provide users with a plurality of graphical user
`interfaces ("GUIs) for commanding and controlling each
`home devices. In one embodiment, the home network is
`configured as an intranet.
`FIG. 1 is a block diagram of a home network 100
`constructed in accordance with one embodiment of the
`present invention. As depicted in FIG. 1, a 1394 serial bus
`114 electronically connects multiple home devices on the
`home network 100. In this example, the 1394 serial bus 114
`provides the physical layer (medium) for sending and
`receiving data between the various connected home devices.
`The 1394 serial bus 114 Supports both time-multiplexed
`audio/video (A/V) streams and standard IP (Internet
`Protocol) communications. In certain embodiments, the
`home network uses an IP network layer as the communica
`tion layer for the home network 100. However, other com
`munication protocols could be used to provide communica
`tion for the home network. For example, the invention may
`be implemented using FCP (Function Control Protocol) as
`defined by IEC 61883, or any other appropriate protocol.
`Thus, a network may generally include two or more devices
`interconnected by a physical layer for exchange or transfer
`of data in accordance with a predefined communication
`protocol.
`FIG. 2 illustrates an example of a layered interface model
`that can be used for communicating between home devices
`in accordance with the present invention. In this example, a
`home device (server) 150 communicates with a home device
`client 166 using network communication layers 152-164.
`By employing the Internet Protocol standard for the network
`layer 160, the home devices can communicate with each
`other without having to know specific details about the other
`communication layers (i.e. application 152, presentation
`154, session 156, transport 158, data link 162 and physical
`164). Thus, by employing the Internet Protocol standard for
`the network layer 160, the home network may use a com
`bination of different communication layers in communicat
`ing between different home devices. It should be recognized
`that a single physical package may include Several devices
`which are logically networked via a network layer for
`example as shown in FIG. 2, not necessarily via a physical
`network. Such devices may include a VCR and a TV in a
`Single housing, for example. Thus, for Such an embodiment,
`where a logical device accesses a GUI to enable a user to
`control a home device, the home device and the logical
`device may be included in the same physical package. In
`Such an embodiment, it could be considered that the physical
`device fetches a GUI from itself. However, in other embodi
`ments the home network interconnects Separate physical
`devices, wherein for example, a first device fetches a GUI
`from a Second device, to permit user interaction with the
`GUI to control the second device.
`
`Charter Ex. 1009, Page 19
`
`

`

`US 6,182,094 B1
`
`1O
`
`25
`
`35
`
`40
`
`15
`
`S
`By way of definition, it is contemplated that a “client” is
`a device providing control interface Service to a human
`operator, including a graphical display hardware for down
`communication and a mouse or other point-and-click device
`for up (or return) communication. A "server' is contem
`plated as a module Supplying a Service, which may be any
`Service other than a control interface provided by a client.
`Stated differently, the server/client relationship is a control
`relationship, wherein the Server provides a Service but a
`client may use the data, as a DTV displayS Video data, but
`does not manipulate or alter the data. It is thus consistent
`with this definition to observe that, frequently, a Server may
`be a Source of information and a client (a browser, for
`example) may be a consumer of information.
`Some specific functions which may be implemented by
`Servers include: return of information (data); performance of
`a function (e.g., mechanical function) and return of status;
`return of a data Stream and Status, reception of a data Stream
`and return of Status, or Saving of a State for Subsequent
`action. Examples of servers include MPEG source, sink and
`display Servers.
`While a Server typically includes a custom, built-in,
`control program to implement control of its own hardware,
`a client functions to interface with the server. It should be
`noted, however, that a "server” as used herein does not imply
`that a web server and a protocol Stack must be used.
`In a presently preferred embodiment, a 1394 serial bus is
`used as the physical layer 164 for the data communications
`on the home network 100. Because of its enhanced band
`width capabilities, the 1394 serial bus can provide a single
`medium for all data communications on the home network
`100 (i.e. audio/video streams and command/control).
`However, the home network 100 is not restricted to using a
`1394 serial bus, and, in alternative embodiments of the
`present invention, other bus types, Such as Ethernet, ATM,
`wireless, etc., may be used as the physical layer if they meet
`the particular throughput requirements of an individual
`home network.
`As depicted in FIG. 1, the home network 100 has several
`home devices connected to the 1394 serial bus 114. In this
`example, the home devices include a DBSS 104 which
`receives transmission signals from a Satellite 122 for Sub
`sequent display. Associated with the DBSS is a network
`interface unit (“NIU”) which, among other things, provides
`an interface between the DBSS satellite transmissions and
`the 1394 serial bus 114.
`A digital video device (“DVD') 108 is also connected to
`the exemplary home network 100. The DVD 108 can be
`used to display digitally encoded Videos on a home televi
`Sion.
`Also connected to the exemplary home network 100 is a
`digital video cassette recorder (“DVCR”) 110, i.e., a digital
`VCR, and a digital TV 102.
`In this example, the DTV 102 provides the human inter
`face for the home network 100 by employing browser
`technology to allow users to control and command the home
`devices over the home network 100. Unlike most other home
`devices that are typically connected to a home network, the
`DTV 102 can provide the human interface for the home
`60
`network 100 as it comprises a screen for displaying HTML
`pages. However other home devices having a display capa
`bility may be used to provide the human interface. Thus, in
`certain embodiments of the inventions, a device Such as a
`personal computer (“PC”) is used to provide the human
`interface for a respective home network, as a PC typically
`embodies a Screen display unit.
`
`45
`
`50
`
`55
`
`65
`
`6
`Although the 1394 serial bus 114 is depicted as using the
`HTTP/IP interface protocol, certain home devices may
`require other protocols interface types (e.g. TCP/IP, UDP/IP,
`FTP/IP, TELNET/IP, SNMP/IP, DNS/IP, SMTPJIP). There
`fore the HTTP/IP protocol may not be able to satisfy all
`home device connection requirements. Thus, in certain
`embodiments of the invention, a bridge proxy 116 is used to
`interface two networks using dissimilar interface protocols
`on their respective mediums which, when connected, com
`prise the home network 100. In certain embodiments, the
`two network mediums are of the same type. For example, as
`depicted in FIG. 1, the 1394 serial bus 114 using the
`HTTP/IP interface protocol is connected by a bridge proxy
`116 to the 1394 serial bus 118, which uses the IEC61883
`interface protocol. By using bridge proxy 116 to interface
`between the HTTP/IP and IEC61883 protocols, security
`system 120, which uses the IEC 61883 interface protocol is
`also accessible on the home network 100.
`In certain other embodiments, a home network may be
`comprised of two network mediums of dissimilar types, e.g.,
`a 1394 Serial bus and Ethernet. Therefore, in certain
`embodiments of the invention, a bridge proxy is used to
`interface two dissimilar medium types to form a single home
`network.
`The Dynamic Host Configuration Protocol (DHCP)
`server 106 is used for the discovery of home devices that are
`powered on and connected to the home network 100. The
`home device discovery proceSS is described in greater detail
`below.
`Home Network Overview
`As depicted in FIG. 1, DTV 102, DVCR 110, DVD 108,
`DSS-NIU 104 and security system 120 represent home
`devices that are currently connected to the home network
`100. A client-server relationship exists among the attached
`devices. With the DTV 102 typically behaving as the client
`and home devices DVCR 110, DVD 108, DSS-NIU 104 and
`Security System 120 behaving as Servers.
`AS previously mentioned, each home device is associated
`with one or more Hypertext Markup Language (HTML)
`files. The HTML files define the control and command
`functions associated with a particular home device. Each
`HTML file may also contain embedded references to other
`HTML files. The browser based DTV 102 (acting as a
`client), receives and interprets the HTML files associated
`with the home devices (acting as servers) and graphically
`displays the respective control and command information on
`its view able display.
`By conforming to the Hypertext Markup Language
`(HTML) and Hypertext Transfer Protocol (HTTP) Internet
`Standards, each home device Sends its custom GUI to the
`browser based DTV 102. The browser based DTV 102
`receives the HTML files from the home devices over the
`home network 100 using the HTTP protocol. Each HTML
`file contains Specific control and command information for
`a respective home device. The HTML files enable the
`browser based DTV 102 to graphically display control and
`command information to a user for a particular home device.
`Therefore, because each home device supplies its own GUI
`through its own HTML files to the browser based DTV 102,
`the browser based DTV 102 can provide a command and
`control interface for a home device without having to know
`any Specific details about the particular device. This feature
`allows the home network 100 to contain home devices from
`a multitude of different manufacturers.
`In addition, home devices can be transparently added or
`removed from the home network 100 without affecting the
`overall System as, in accordance with the invention. each
`
`Charter Ex. 1009, Page 20
`
`

`

`US 6,182,094 B1
`
`15
`
`25
`
`35
`
`40
`
`7
`home device defines its own command and control interface
`through its respective HTML files.
`HTML. Two Way Mechanism
`FIG. 3A depicts an exemplary embodiment in which a
`browser based DTV 202 (client) renders the characteristics
`of a home device 204 (server) over a home network. The
`home device 204 is represented by one or more HTML files
`stored in an accessible area within the home device 204. The
`one or more HTML files are ASCII text files containing
`Specific information pertaining to the particular home device
`204, along with data that enables a browser to present the
`information graphically. In addition to rendering the HTML
`file on the browser based DTV 202, by employing forms
`technology, the browser based DTV 202 can return infor
`mation back to the home device 204, thus providing a
`two-way communication. Other common techniques for
`providing the two-way communication may include the use
`of Java or Control Gate Interfaces (CGIs). Once the infor
`mation contained in a device's HTML file is graphically
`displayed on the DTV 202, the user can control the home
`device 204 from the DTV 202 by selecting icons that have
`asSociated hyperlinks to start the control programs displayed
`on the DTV's screen and/or entering data to the DTV 202.
`Home Device HTML Files
`AS previously Stated, each home device connected to the
`home network has one or more associated HTML files. The
`HTML files for a respective home device define the control
`and command functions for that particular home device.
`Each HTML file may also contain embedded references to
`other related HTML files. A device connected to the home
`network that has a view able display (e.g., Screen) and
`employs the browser technology may receive and interpret
`the HTML files associated with the home devices connected
`to the home network, and graphically display the informa
`tion contained therein using a GUI on its Screen.
`This is illustrated by FIG. 3A wherein is shown an
`interaction between a client and a Server's executables.
`However, it is a feature of the invention to provide control
`by interaction between executables of two servers or of a
`client and plural Servers. Thus, in accordance with the
`invention control is typically implemented by Service con
`trol programs (executables which are trying to be operated
`remotely), communications, commands and (if necessary),
`human interface with a Server control program via a GUI.
`As one example, FIG. 3B shows location of file and
`program components locally, permitting control actions to
`be implemented by running programs and Scripts on the
`device itself. This aspect of the invention thus permits
`implementation to be carried out in a local manner which
`may be proprietary to the device rather than being performed
`remotely, and which thus does not require a Standardized
`1394 command set.
`For example, the user may wish to change display bright
`neSS. To implement Such a change, the user may click on a
`“Brightness” button on the User HTML GUI page. In
`response, another GUI may be brought up, with “Bright”
`and "Dim” buttons. In response to the user clicking one of
`these two buttons, the http Server will cause a brightness
`control program for the display to run, in order to control the
`desired hardware action. For action local to the DTV, the
`DTV thus may include a server capability, to interpret the
`post actions from the browser.
`In that regard, in order to be able to post actions to control
`their local hardware, all home network DTV devices pref
`erably have a Server capability. For Such operation, a
`browser may pick up local htm1 files and render the files to
`a GUI, without invoking the http server. In order to invoke
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`the local http Server to respond, clicking on a button pref
`erably involves an http access to the local machine name or
`IP address. In turn, the http server invokes the local device
`control program, Such as "Brightness” in the above example.
`Generally, control may be implemented by transfer of a
`graphical control object (GCO), which preferably resides in
`the Server, from the Server for rendering on the client, to
`make the GUI. As an advantageous result of this approach,
`detailed controls back to the Server originating the GCO may
`be proprietary, as the Server device “understands' and is
`aware of its own GUI controls. Additionally, the look and
`feel of the GUI originates with the attached server (e.g., the
`program server, Server device or media) and not with the
`client. Independence of the command language makes the
`arrangement operable independently of any new features
`added to devices, which may be included in the GCO sent
`from the Server, as well as any other future modifications,
`i.e., the home network configuration is made inherently
`“new-feature proof” and “future proof”.
`Moreover, because a specific device may be selected for
`control by Selecting an icon, there is no need for hardware
`reconfiguration to implement control of different (or
`