EP1762094A2 - Integriertes adressierungsschema zur verwendung in einem system mit einer baumstruktur - Google Patents

Integriertes adressierungsschema zur verwendung in einem system mit einer baumstruktur

Info

Publication number
EP1762094A2
EP1762094A2 EP03816010A EP03816010A EP1762094A2 EP 1762094 A2 EP1762094 A2 EP 1762094A2 EP 03816010 A EP03816010 A EP 03816010A EP 03816010 A EP03816010 A EP 03816010A EP 1762094 A2 EP1762094 A2 EP 1762094A2
Authority
EP
European Patent Office
Prior art keywords
router
repeater
command
address
transmitter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP03816010A
Other languages
English (en)
French (fr)
Other versions
EP1762094A4 (de
Inventor
James D. Lyle
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Silicon Image Inc
Original Assignee
Silicon Image Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Silicon Image Inc filed Critical Silicon Image Inc
Publication of EP1762094A2 publication Critical patent/EP1762094A2/de
Publication of EP1762094A4 publication Critical patent/EP1762094A4/de
Withdrawn legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00Television systems
    • H04N7/16Analogue secrecy systems; Analogue subscription systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41Structure of client; Structure of client peripherals
    • H04N21/4104Peripherals receiving signals from specially adapted client devices
    • H04N21/4108Peripherals receiving signals from specially adapted client devices characterised by an identification number or address, e.g. local network address
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/4367Establishing a secure communication between the client and a peripheral device or smart card
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00Television systems
    • H04N7/16Analogue secrecy systems; Analogue subscription systems
    • H04N7/173Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal

Definitions

  • the invention is a system having a tree structure and configured to distribute data (e.g., video data) to multiple devices, in which each repeater in the system has a unique router address,
  • TMDS link transition minimised differential signaling interface
  • This link is used primarily for high-speed transmission of video data from a set-top box to a television, and also for high-speed transmission of video data from a host processor (e.g. * a personal computer) to a monitor.
  • host processor e.g. * a personal computer
  • TMDS link a transition minimised differential signaling interface
  • video data are encoded and then transmitted as encoded words (each 8-bit word of digital video data is converted to an encoded 10-bit word before transmission); 2.
  • the encoded video data and a video clock signal are transmitted as differential signals (the video clock and encoded video data are transmitted as differential signals over conductor pairs without the presence of a ground line); 3. three conductor pairs are employed to transmit the encoded video, and a fourth conductor pair is employed to transmit the video clock signal; and 4. signal transmission occurs in. one direction, from a transmitter (typically associated with a desktop or portable computer, or other host) to a receiver (typically an element of a monitor or other display device), It has been proposed to transmit encrypted video data over a TMDS serial link (e,g., from a set-top box to a television).
  • TMDS serial link e,g., from a set-top box to a television.
  • HDMI High Definition Multimedia Interface
  • DV1 Digital Video Interface
  • a DVI linlc can be implemented to include two TMDS links (which share a common conductor pair for transmitting a video clock signal) or one TMDS lin , as well as additional control lines between the transmitter and receiver.
  • TMDS links which share a common conductor pair for transmitting a video clock signal
  • TMDS lin a DVI link that includes one TMDS link
  • additional control lines between the transmitter and receiver.
  • 1 includes transmitter I, receiver 3, and the following condiictors between the transmitter and receiver: four conductor pairs (Channel 0, Channel I, and Channel 2 for video data, and Channel C for a video clock signal), Display Data Ct-taimel (“DDC") lines for bidirectional communication between the transmitter and a monitor associated with the receiver in accordance with the conventional Display Data Channel standard (the Video Electronics Standard Association's "Display Data Channel Standard," Version 2, Rev. 0, dated April 9, 1996).
  • a Hot Plug Detect (HPD) line on which the monitor transmits a signal that enables a processor associated with the transmitter to identify the monitor's presence
  • Analog lines for transmitting analog video to the receiver
  • Power lines for providing DC power to the receiver and a monitor associated with the receiver).
  • the Display Data Channel standard specifies a protocol fo bidirectional communication between a transmitter and a monitor associated with a receiver, including transmission by the monitor of Extended Dis lay Identification (“EDID") data that specifies various characteristics of the monitor, ⁇ tnd transmission by the transmitter of control signals for the monitor.
  • Transmitter 1 includes three identical e ⁇ coder/serializcr units (units 2, A, and 5) and additional oircuitry (not shown).
  • Receiver 3 includes three identical recovery/decoder units (units 8, 10. and 12) and inter-channel alignment circuitry 14 connected as shown, a additional circuitry (not shown). As shown in Fig. I, circuit 2 encodes the data to be transmitted over Channel 0, and serializes the encoded bits.
  • circuit 4 encodes the data to be tran$mitted over Channel 1 (and serializes the encoded bits), and circu-it 6 encodes the data to be transmitted over Channel 2 (and serializes the encoded bits).
  • Each of circuits 2. 4, and 6 responds to a control signal (an active high binary control signal referred to as a 'data enable" or "DE" signal) by selectively encoding either digital video words (in response to DE having a high value) or a control or synchronization signal pair (in response to DE having a low value).
  • a control signal an active high binary control signal referred to as a 'data enable" or "DE” signal
  • Each o f encoders 2, 4, and 6 receives a different pair of control or synchronization signals: encoder 2 receives horizontal and vertical synchronization sigtials (HSYNC and VSYNC); encoder 4 receives control bits CTLO and CTLl; and encoder 6 receives control bits CTL2 and CTL3.
  • encoder 2 receives horizontal and vertical synchronization sigtials (HSYNC and VSYNC); encoder 4 receives control bits CTLO and CTLl; and encoder 6 receives control bits CTL2 and CTL3.
  • each of encoders 2, 4, and 6 generates in-band words indicative of video data (in response to DE having a high value), encoder 2 generates out-of-band words indicative of the values of HSYNC and VSYNC (in response to DE having a low value), encoder 4 generates out-of-band words indicative of the values of CTLO and CTLl (in response to DE having a low value), and encoder 6 generates out-of-band words indicative of the values of CTL2 and CTL3 (in response to DE having a low value). In response to DE having a low value, each of encoders 4 and 6 generates one of four specific out-of-band words indicative of the values 00, 01.
  • serial links include the set of serial links known as Low Voltage Differentia! Signaling ("LVDS' ⁇ ) links (e.g., "LDI," the LVDS Display Interface), each of which satisfies the TIA/EIA-644 standard or the TEEE-1596.3 standard, ethemet links, l ⁇ berchannel links, serial ATA links used by disk drives, and others.
  • LVDS' ⁇ Low Voltage Differentia! Signaling
  • the invention is applicable to systems comprising devices (e.g., transmitters, receivers, and repeaters) connected by serial links, and is also applicable to systems comprising devices (e.g., transmitters, receivers, and repeaters) connected by parallel links,
  • channel refers to a portion of a link that is employed to transmit data (e.g., a particular conductor or conductor pair between the transmitter and receiver over which the data are transmitted, and specific circuitry within the transmitter and/or receiver used for transmitting and/or recovery of the data) and to the technique employed to transmit the data over the link.
  • a multi-drop distribution system e.g., a multi-drop video distribution system
  • a single source a transmitter
  • one or more receivers e.g., receivers associated with video display devices. All of these devices need unique addresses.
  • the system may also include one or more repeaters, which may need addresses of their own.
  • each receiver is associated with a display device that contains an ED ⁇ D PROM which is accessed on a DDC bus (e.g., the DDC lines of a DVI link as mentioned above).
  • a DDC bus is very similar to an I2C bus.
  • Each EDID PROM in such a system has the same fixed address.
  • a DDC bus is not designed for large, distributed systems. It has electrical limits that both limit its range and increase the difficulty of buffering or extending the range.
  • each receiver includes an HDCP (or other) content protection subsystem ("block").
  • HDCP does not solve this problem, except by assuming that each branch will be a separate entity, with some (largely undefined) way of moving data between the branches.
  • the invention seeks to solve these problems and limitations of the prior art in an integrated way.
  • the invention is a communication system including at least one transmitter and at least one repeater (and typically also at least one receiver), with each transmitter, repeater, and receiver coupled to at least one other transmitter, repeater, and receiver by a link.
  • Data e.g., video data or audio data
  • commands each accompanied by an address
  • the system has a tree structure and the transmitter is the root node (and is sometimes referred to as the "root device").
  • each repeater includes a router to which a unique address (to be referred to as a "router address”) is assigned at the time the repeater is manufactured.
  • the router address can be an identification or serial number, and optionally also serves at least one purpose in addition to identifying the router.
  • the router address c-r-n be composed of various portions, including some portions that are common to particular vendor or device family, For example, the router address can include a Vendor ID field, a Product ID field and optionally also a Device Type field, and a sub-code, On_ly the sub-code need change from one particular router to the next.
  • t e router has no unique address (in the sense that neither the router, nor the repeater including the router, remembers a unique address) but is located at a unique location in the system so that it can be "addressed" purely by this unique location.
  • an ups tream device e.g., a transmitter
  • a command either accompanied only by &.
  • each repeater is also assigned a common address (to be referred to as a "router access” address) for accessing its router.
  • the router access address is distinct from the above-mentioned router address.
  • management functions are identification, status checking, and control functions, and functions that use the router as a conduit to another repeater further downstream.
  • Exemplary functions of tb.e latter type are reading data from a downstream repeater (and forwarding such data to a upstream device that requested the data) and forwarding at least one of data, an address, and a command from an upstream device to one or more downstream repeaters.
  • a repeater that receives a router access address is the only repeater directly connected to the upstream device via th-e link. In this case, no conflict can arise despite the fact that the router access address is shared by two or more repeaters in the: system.
  • each repeater has at least one other common address and each receiver has at least one common address.
  • common addresses are an "identification data” address for accessing a memory (in or associated with the repeater or receiver) that contains identification data (e.g., a PROM containing Extended Display Identification (EDID) data or similar identification data, in a monitor associated with the repeater) and a "content protection" address for accessing a selected content protection subsystem (e.g., a cipher engine) of the device.
  • identification data e.g., a PROM containing Extended Display Identification (EDID) data or similar identification data, in a monitor associated with the repeater
  • EDID Extended Display Identification
  • a selected content protection subsystem e.g., a cipher engine
  • Preferred embodiments of the inventive system include a repeater configured xo execute certain types of commands (e.g., or to read or otherwise process data received with such commands) only if the commands are accompanied by a unique router address for the repeater.
  • the repeater when one embodiment of the repeater receives a message, a command to forward the message to a downstream device (e.g., a downstream repeater), and a router access address (shared by the repeater with at least one other repeater) but not the repeater's unique router address, the repeater responds by executing the command without opening, reading, or otherwise processing the message.
  • a downstream device e.g., a downstream repeater
  • the repeater responds by executing the command without opening, reading, or otherwise processing the message.
  • this repeater also receives its router address along with the command, message, and router access address
  • the repeater reads the message (and executes some internal operation in response thereto, where "internal operation" denotes an operation internal to the repeater) and also executes the command by forwarding the message downstream.
  • the repeater's router when an embodiment of the repeater receives a command to perform an identification, status checking, or control operation, the repeater's router performs the operation specified by the command only if the commaaid is accompanied by the router address.
  • a repeater of the inventive system is typically configured to execute certain types of commands (and/or process data received with such commands) even if the commands (or commands and data) are not accompanied by a unique address (e.g., a unique address of the repeater's router).
  • a repeater when a repeater receives a "broadcast" command, a message, and a router access address (shared by the repeater with at least one other repeater) but no unique router address, the repeater responds by executing the command (e.g., by forwarding the command and message to each downstream repeater coupled thereto) and also reading the message and executing an internal operation in response to the message, hi a variation on this example, the broadcast command is accompanied only by a message (and is not accompanied by any address) and the repeater responds to the command and message by executing the command (e.g.. by forwarding the command and message to each downstream repeater coupled thereto) and also reading the message and executing an internal operation in response to the message.
  • the broadcast command is accompanied only by a message (and is not accompanied by any address) and the repeater responds to the command and message by executing the command (e.g.. by forwarding the command and message to each downstream repeater coupled thereto) and also reading the message and executing an
  • the inventive system has a tree structure, and includes a transmitter (the root device) configured to assert addresses and commands in accordance with the invention, and at least one repeater and at least one other device to which at least one such address has been assigned.
  • each repeater has a router that performs at least the following three functions: gathering information about the repeater itself (such as its address, capabilities, and status); gathering equivalent information about any and all repeaters connected downstream of the repeater (this is preferably done using a switcliing fimction of the router that can also be used to isolate branches of the system that do not respond properly or that respond or babble when they should not; and broadcasting commands and/or messages to routers of repeaters that are connected downstream of the repeater and passing (he appropriate responses back upstream.
  • the inventi e system implements a new transmission protocol.
  • commands initiate at the root device and travel only outward (downstream).
  • Responses travel inward (upstream) only, toward the root device.
  • Commands can be broadcast by the root device, and commands that are broadcast are seen by each repeater of a system.
  • Responses are point-to-point, and are seen only by devices in the direct path between the response-originating device and the root device. Commands and responses can but need not share the same communication path.
  • each channel that they share along the path will typically not support communication in both directions at the same time so that will be necessary for each router to switch direction between each phase of the transaction, in the sense that a router will only send commands (with accompanying addresses) downstream over the channel during a first phase, and then receive responses over the channel from a downstream device (and forward the response upstream) during the next phase.
  • a command and the response thereto will use completely different paths.
  • a repeater sends commands downstream on one or more video (or video clock) channels of a TMDS link (e.g., in packets between video frames, or on a modulated clock channel), and the receiver receives the responses on a DDC bus.
  • a command (with an accompanying address) can define a router (using its preset unique address), an address to which the router should forward the command, a command code (e.g., a write code or read code), and any other data that is appropriate.
  • a response to a command will typically contain the result data (if applicable), and an acknowledgment (completion) code.
  • Preferred embodiments of the invention support split transactions, in the following sense.
  • the root device (which can be a repeater, in the case that such repeater is the root device of a branch of a larger system) sends an address, a command, and any related data to a repeater connected thereto, and receives an acknowledgement (e.g., a "retry" acknowledgment) indicating that the operation has begun but is not yet finished.
  • the root device receives either an "error" acknowledgment (indicating that the operation is not supported or cannot be completed for some other reason) or a completion acknowledgement.
  • the root device initiates another transaction to the same device.
  • each repeater is responsible for gathering data that characterizes the structure of each branch ofthe device tree that is downstream therefrom. In this way, the entire tree can be determined in a hierarchical way, and the root device (and each repeater) need only query the devices immediately downstream therefrom (using the appropriate known router address and/or router access address); each repeater includes a router that serves as the router both for itself and for each branch (downstream o he repeater) that does not include its own router or routers.
  • This provides backward compatibility and can reduce the cost of implementing pure "leaf * nodes (where a "leaf node has no device coupled downstream therefrom). If the structure of a tree reveals that a particular leaf node does not have a router, the router immediately upstream from the leaf node (to be referred to as a "surrogate” router) will assume the router responsibility for that leaf node.
  • a command to read an EDID PROM or HDCP register in (or associated with) the leaf node would go to the surrogate router, and the surrogate router would decode the command, translate it as necessary, and perform the necessary function on the branch that includes the leaf node.
  • the surrogate router preferably does this in isolation from other branches, and using pre-defined function addresses; each repeater monitors the routers coupled downstream therefrom for
  • a repeater is configured to forward a command only to those downstream routers that are expected to respond to the command, but even when the repeater is configured to forward a command to all downstream routers (including those that are not expected to respond to the command), it preferably is configured to actively disconnect any misbehaving downstream router; and each repeater monitors the status of downstream branches, and can send "interrupt" (or status change) infonnation upstream toward the root device.
  • commands, addresses, and data are transmitted downstream two or more different channels of a link.
  • responses to commands are transmitted upstream over a different channel (or different channels) of a link than the channel(s) over which the commands are transmitted downstream.
  • the inventive repeater is a router configured to forward (but not to translate or otherwise modify) commands, addresses, and/or data to a downstream device, and typically also to perform identification, status checking, and control functions.
  • the inventive repeater is capable of forwarding translated versions of commands, addresses, and/or data to a downstream device, and its router is typically also capable of performing identification, status checking, and control functions and forwarding (without translating or otherwise modifying) commands, addresses, and/or data to a downstream device.
  • the repeater can translate received data in some way (e.g., by decrypting the data, translating the decrypted data, and re-encrypting the translated data) and forward the translated data downstream.
  • Fig. 1 is a block diagram of a conventional system including a Digital Video Interface ("DVI”) fink.
  • Fig.2 is a block diagram of a system that can be implemented in accordance with tli ⁇ present invention,
  • ⁇ transmitter is used herein in a broad sense to denote any unit capable of transmitting data over a communication link (and optionally also encoding and/or encrypting the data to be transmitted).
  • receiveriver is used herein in a broad sense to denote any uni capable of receiving data that has been transmitted over a communication link (and optionally also decoding and/or decrypting the received data).
  • the link can, but need not, be a TMDS link or other serial link.
  • transmitter can denote a transceiver that performs the functions of a receiver as well as the functions of a transmitter.
  • Downstream Toward the device (e.g., display device) that is the final destination of transmitted data.
  • Upstream Toward the source of a stream (or other quantity) of transmitted data.
  • Repeater A device configured to receive content (e.g., encrypted digital data) and forward the content, or to receive content, translate the content (e.g., decrypt and/or otherwise modify or translate the content), and then forward the translated content.
  • One type of repeater (sometimes referred to herein as a "switch”) receives data and forwards the data without decrypting or translating it in any way.
  • a switch buffers the forwarded data to allow - ⁇ - for longer links, and can be coupled between at least two upstream devices and at least two downstream devices and configured to selectively forward data from any ofthe upstream devices to all o the downstream devices or to any selected one (or subset) o the downstream devices (all the downstream links coupled to the selected upstream link will have the same resolution and timing characteristics).
  • Router a subsystem of a repeater, configured to perform at least one (and typically more than one) router function, where "router function" denotes forwarding content from an upstream, device (e.g., one of multiple upstream devices coupled to the repeater) to a downstream device, forwarding a translated version of content from an upstream device to one or more downstream devices (e.g., to a selected one of multiple downstream devices coupled to the repeater) to a downstream device, or forwarding to an upstream device a downstream device's response to content from the upstream device (or a translated version of such a response).
  • a router is typically also configured to perform at least one other management fimction, such as but not limited to an identification, status checking, o ⁇ control function.
  • the invention is implemented in systems that have a tree structure.
  • a system has a "tree" structure is used herein (including in the claims) to denote tha
  • the system includes a transmitter, at least one repeater, and optionally also at least one receiver; each repeater and receiver is coupled to the transmitter or to at least one other repeater or recei er by a link; each transmitter, repeater, and receiver is a different node ofthe system; the transmitter is the root node; and the nodes ofthe system include the root node and additional nodes of at least two different degrees relative to the root node,
  • the 2 system has a tree structure and includes transmitter 1, repeaters 3 and 5 coupled to transmitter I (downstream o the transmitter), receivers 7 and 9 coupled to repeater 3 (downstream of the repeater), and receiver 11 coupled to repeater 5 (downstream ofthe repeater),
  • transmitter 1 is the root node
  • repeaters 3 and 5 are nodes of a first degree
  • receivers 7, 9, and 11 are nodes of a second degree.
  • the invention is a communication system including at least one transmitter and at least one repeater (and typically also at least one receiver), in which each repeater and receiver is coupled to at least one transmitter and/or to at least one other repeater and/or receiver by a link.
  • Data can be transmitted over each link from each transmitter to at least one repeater, and from each repeater to each device (repeater or receiver) coupled downstream from such repeater.
  • Each repeater includes a router.
  • the router is given a unique address (to be referred to as a "router address") at the time the repeater is manufactured.
  • the router address can be an identification (ID) or serial number, and optionally also serves at least one purpose in addition to identifying the router.
  • the router address could be used in some cryptographic way (e.g., it could be used as a key selection Vector, as in the conventional HDCP protocol).
  • the unique router address can be composed of various portions, including some portions that are common to a particular vendor or device family.
  • the router address can include a Vendor ID field, a Product ID field and optionally also a Device Type field, and a sub-code. Only the sub-code need change from one particular router to the next.
  • the sub-code is kept in some kind of programmable memory (such as EEPROM or FLASH, or a laser-trimmed area) of the repeater. The rest ofthe router address will not change appreciably from repeater to repeater, and so can. be kept in ROM in each repealer.
  • Each repeater also has a common address (to be referred to as a "router access” address) for accessing its router, where the expression “common address” is used herein (including in the claims) to denote an address that is not unique to a device (of a system) and is instead shared with at least one other device of the system.
  • the router access address is distinct from the above-mentioned unique "router" address, hi response to the correct router access address (accompanied by a management function command), the repeater's router performs a management function, such as (but not limited to) an identification, status checking, or control function, or a function that uses the router as a conduit to another repeater further downstream.
  • Exemplary functions of the latter type are reading data from a downstream repeater (and forwarding such data to the upstream device that requested the data) and forwarding data from an upstream device to a downstream repeater.
  • a repeater that receives a router access address is the only repeater directly connected to the upstream device via the Unit, no conflict can arise despite the fact that the router access address is a common address used by two or more repeaters in the system.
  • no router has a unique address (in the sense that no router, nor any repeater including a router, remembers a unique address).
  • each router is located at a unique location in the system so that it can be "addressed” purely by this unique location.
  • an upstream device e.g., transmitter 1 of Fig. 2
  • can assert a command (accompanied only by a common address, or accompanied by no address) via a specific l nk to one repeater, so that this repeater's router is the only router that receives and responds to the command
  • each repeater has at least one other common address and each receiver has at least one common address.
  • each receiver has more than one common address.
  • Examples of such common addresses are an 'identification data" address for accessing a memory in the device that contains identification data (e.g., a PROM containing the above-mentioned Extended Display Identification (EDID) data or similar identification data) and a "content protection" address for accessing a selected content protection subsystem o the device (e.g., an HDCP cipher engine or any other element configured to perform an HDCP or non-HDCP content protection function).
  • a repeater ofthe inventive system is configured to execute certain types of commands (e.g., or to read or otherwise process data received with such commands) only if the commands (or commands and data) are accompanied by the repeater's unique router address.
  • one such repeater when one such repeater receives a message, a command to forward the message to a downstream device (e.g., a downstream repeater), and a router access address (shared by the repeater with at least one other repeater) but does not receive its own router address, the repeater responds by executing the command without opening, reading, or otherwise processing the message.
  • a downstream device e.g., a downstream repeater
  • a router access address shared by the repeater with at least one other repeater
  • the repeater responds by executing the command without opening, reading, or otherwise processing the message.
  • the repeater if the repeater also receives its router address along with the command, message, and router access address, the repeater would read the message (and execute some internal operation in response thereto) and also execute the command by forwarding the message downstream.
  • a Tepeater o the inventive system can be configured to execute certain types of commands (and/or process data received with such commands) even if the commands (or commands and data) arc not accompanied by a unique address (e.g., a unique address of the repeater's router).
  • the repeater can be configured so that when it receives a "broadcast" command, a message, and a router access address (which it shares with at least one other repeater) but not its unique router address, the repeater responds by executing the command (by forwarding the command and message to each downstream repeater coupled thereto) and also reading the message and executing an internal operation in response to the message.
  • the broadcast com and is accompanied only by a message (and is not accompanied by any address) and the rqieater responds to the command and message by executing the command (e.g., by forwarding the command and message to each downstream repeater coupled thereto) and also reading the message and executing an internal operation response to the message.
  • a broadcast command has an address field that is ignored by each device that receives and executes the broadcast command.
  • a broadcast command has an address field whose contents are used (by at least one device that receives and executes the broadcast command) for some purpose entirely different than as an address
  • a broadcast command can include, or be accompanied by, a message (or other data) to be forwarded with the command.
  • a command that is received and executed by at least one device o the inventive system can have more than two associated addresses (e.g., one unique address and one common address), but more typically such a command has only one address associated with it.
  • Each common address is shared by a subset of he devices of he system (e.g., where the devices implement a bit mask scheme), where the subset includes at least two devices.
  • the communication system of Fig. 2 can be implemented in accordance with the invention.
  • 2 system has a tree structure and includes transmitter 1 (the root node), repeater 3 coupled by link 20 to transmitter I , repeater 5 coupled by linlc 21 to transmitter 1, receiver 7 coupled by link 22 to repeater 3, receiver 9 coupled by link 23 to repeater 3, and receiver 1 1 coupled by link 24 to repeater 5,
  • Repeaters 3 and 5 are nodes of a first degree, and receivers 7, 9, and 11 are nodes of a second degree.
  • Repeater 3 includes router 4.
  • Repeater 5 includes router 6.
  • Display device 8 is coupled to receive video data from receiver 7
  • display device 10 is coupled to receive video data from receiver 9, and display device 12 is coupled to receive video data from receiver 1 1.
  • transmitter 1 and receivers 7, 9, and 11 implement content protection (and each includes a cipher engine) so that transmitter 1 can transmit encrypted data over links 20 and 21, repeaters 3 and 5 can pass diraugh the encrypted data to one or more of links 22, 23, and 24, and each of receivers 7, , and 11 can decrypt the encrypted data received repeater 3 or 5.
  • each of display devices S, 10, and 12 includes an EDID PROM, the EDID PROM of device S can be accessed by transmitter 1 (via repeater 3 and receiver 7), the EDID PROM of device 10 can be accessed by transmitter 1 (via repeater 3 and receiver 9), and the EDID PROM of device 12 can be accessed by transmitter 1 via repeater 5 and receiver 11.
  • receivers 7, 9, and 11 share the same identification data address.
  • each receiver is configured to respond to the identification data address (accompanied by an appropriate command) by accessing the EDID PROM ofthe display device coupled thereto.
  • receivers 7, 9, and 1 share the same content protection address.
  • the content protection subsystem of each receiver is configured to respond to the content protection address (accompanied by an appropriate command) by performing a content protection operation, when the appropriate one of repeaters 3 and 5 forwards such address and command to the receiver from the content protection subsystem of transmitter 1.
  • each of routers 4 and 6 has a unique router address, and repeaters 3 and 5 also share a router access address. These addresses can be used as described above.
  • transmitter 1 can send to repeater 5 (over link 21) a message, a command to forward the message to a downstream device, and the router access address (but not the unique router address of repeater 5),
  • router 6 of repeater 5 is configured to respond to these three hems by executing the command (forwarding the message to receiver 11) witiiout opening, reading, or otherwise processing the message.
  • transmitter 1 sends (to repeater 5) repeater 5 's unique router address along with the same command, message, and router access address that transmitter 1 sends in the previous example.
  • router 6 of repeater 5 is configured to respond to these four items by reading the message (and executing some internal operation in response thereto) as well as executing the command (forwarding the message to receiver 11).
  • repeater 3 can receive a command to forward encrypted data (from transmitter 1) to a specific one of receivers 7 and 9 determined by the command, and a router access address, In response to the command and router access address, repeater 3 forwards the data to the appropriate one of receivers 7 and 9.
  • repeaters 3 and 5 implement a content protection function and each includes a cipher engine (e.g., in translation subsystem 25 of repeater 3 or translation subsystem 26 of repeater 5), hi some such implementations, repeater 3 responds to a content protection address (accompanied by an appropriate command) by performing a content protection operation (e.g tone encrypting or decrypting data received from transmitter 1 in translation subsystem 25 and asserting the encrypted or decrypted data to router 4) and optionally also forwarding to one or both of receivers 7 and 9 (from router 4) an encrypted or decrypted version of data recei ed from transmitter 1.
  • the command could specify which of receivers 7 and 9 should receive the encrypted or decrypted data.
  • a repeater e.g., a repeater that is a switch, as defined above
  • a repeater that does not have an EDID PROM and does not implement a content protection function would not need an identification data address or content protection address, and would not be configured to respond to an EDID or content protection address.
  • a variation of repeater 3 of Fig. 1 which lacks subsystem 25 (and lacks an EDID PROM), and consists of router 4 only is a repeater that is a switch.
  • identification data addresses and content protection addresses could be allocated even to a repeater that is purely a switch (such addresses would be shared by such a repeater with at least one other device).
  • a variation on repeater 3 or 5 of Fig, 2 that consists of a router only (e.g., router 4 or 6) can be allocated an identification data address and a content protection address even though such repeater does not implement a content protection function (or include a cipher engine) and does not include an EDID PROM.
  • transmitter 1 would be able to communicate with the replacement device using the predetermined identification data address and/or content protection address.
  • a repeater implements a content protection fimction, and includes a cipher engine, registers for storing values used by the cipher engine to implement the content protection function, and a router. In some cases, the router shares at least some of such registers with the cipher engine.
  • the receiver is typically the only repeater directly connected to the upstream device via the link (i.e., the link is typically a point-to-point link).
  • the repeater In response to a content protection command accompanied by die content protection address, the repeater would execute the command. Addresses can be allocated to the devices of a system in accordance with the invention even when the system includes no repeater and does not have a tree structure.
  • one such system consists of a transmitter (configured to assert addresses and commands in accordance with the invention) and at least one other device (to which at least one such address has been assigned).
  • the transmitter is preferably configured to access an EDID PROM and/or content protection circuit in (or associated with) each downstream device using conventional addresses and conventional predefined interfaces.
  • the inventive system has a tree structure, and includes a transmitter (the root device) configured to assert addresses and commands in accordance with the invention, and at least one repeater and at least one other device to which at least one such address has been assigned.
  • each repeater has a router that performs at least the following three functions: gathering information about the repeater itself (such as its address, capabilities, and status); gathering equivalent information about any and all repeaters connected downstream of die repeater. This is preferably done using a switching function o he router that can also be used to isolate branches of he system that do not respond properly (or that respond or babble when they should not); and broadcasting commands and/or messages to routers of repeaters that are connected downstream ofthe repeater, and passing the appropriate responses back upstream.
  • the inventive system implements a new transmission protocol. In accordance with the new transmission protocol, commands initiate at the root device and travel only outward (downstream). Responses travel inward (upstream) only, toward the root device.
  • Commands can be broadcast by the root device, and commands that are broadcast are seen by each repeater of a system. Responses are point-to-point, and are seen only by devices in the direct path between the response-originating device and the root device.
  • This new transmission protocol differs from but is compatible with the protocol conventionally used on DDC (I2C) lines. In accordance with the new transmission protocol, commands and responses can but need not share the same communication path.
  • each channel that they share along the path • will typically not support conuminication in both directions at the same time so that will be necessary for each router to switch direction between each phase o he transaction, in the sense that a router will only send commands (with accompanying addresses) downstream over the channel during a first phase, and then receive responses over the channel from a downstream device (and forward the response upstream) during the next phase.
  • a router can easily be implemented to function in this manner because there will be a single boundary between the transaction phases and this boundary will be distinct and readily identifiable. Alternatively, a command and the response thereto will use completely different paths.
  • a repeater sends commands downstream on one or more video (or video clock) channels of a TMDS linlc (e.g., in packets between vidoo frames, or on a modulated clock channel), and the receiver receives the responses on a DDC bus.
  • a command (with an accompanying address) can define a router (using its preset unique address), an address to which the router should forward the command, a command code (e.g., a write code or read code), and any other data that is appropri te.
  • the response will typically contain the result data (if applicable), and an acknowledgment (completion) code. There may bo some latency involved in certain operations (e.g., in execution of some commands).
  • the root device sends an address, a command, and any related data to a repeater, and receives an acknowledgement (e.g., a "retry” acknowledgment) indicating that the operation has begun but is not yet finished.
  • the root device receives either an "error" acknowledgment (indicating that the operation is not supported or cannot be completed for some other reason) or a completion acknowledgement.
  • the root device can be a repeater, namely a repeater that is the root device of a branch of a larger system.
  • each repeater is responsible for gathering data that characterizes the structure of each branch o he device tree that is downstream therefrom, In this way, the entire tree can be determined in a hierarchical way, and the root device (and each repeater) need only query the devices immediately downstream therefrom (using the appropriate known router address and/or router access address); (2) each repeater includes a router that serves as the router both for itself and for each branch (downstream ofthe repeater) that does not include its own router or routers.
  • This provides backward compatibility and can reduce the cost of implementing pure "leaf nodes (where a "leaf node has no device coupled downstream therefrom). If the structure of a tree reveals that a particular leaf node does not have a router, the router immediately upstream from the leaf node (to be referred to as a "surrogate” router) will assume the router responsibility for that leaf node. A command to read an EDID PROM or HDCP register in (or associated with) the leaf node would go to the surrogate router, and the surrogate router would decode the command, translate it as necessary, and perform the necessary function on the branch that includes the leaf node.
  • the surrogate router preferably does this in isolation from other branches, and using pre-defined fimction addresses; (3) each repeater monitors the routers coupled downstream therefrom for "babbling” or otherwise incorrect operation, and disconnects any downstream router that is not behaving properly. It can do this because it knows the structure ofthe downstream tree, and can see and decode at least some of he commands it receives from an upstream device (e.g., it can typically see and decode each "broadcast" command that it receives from an upstream device).
  • a repeater is configured to forward a command only to those downstream routers that are expected to respond to the command, but even when the repeater is configured to forward a command to all downstream routers (including tiiose that are not expected to respond to the command), it preferably is configured to actively disconnect any misbehaving downstream router; and (4) each repeater monitors the status of downstream branches, and can send "interrupt" (or status change) information upstream toward the root device.
  • a router ofthe type described herein is preferably implemented in each ofthe repeaters of a system that embodies the invention, except that a router is optionally implemented (and not required) in a repeater that is connected as a "leaf node (a node with no device coupled downstream of it).
  • a repeater connected as a leaf node can include a router (that implements a full or partial set of router functions) if the leaf node requires at least one router capability other than a switching capability (e.g., an expanded diagnostic or control capability, or an additional downstream bandwidth or buffering capability) or if a content protection mechanism (or other function) in the leaf node requires a router interface for its own use.
  • tree management preferably occurs as follows * . (1) the root device detects when a new device is coupled to the system; (2) if the new device is a repeater, it will have a router. The root device queries this router for information about any and all "trees" (branches ofthe overall system) downstream ofthe new device.
  • the root device builds this infoimation into a cohesive map ofthe entire system.
  • This "map updating" operation may take significant time, but the structure ofthe inventive system allows many operations to proceed in parallel with a map updating operation.
  • a map updating operation can be accomplished without using the command/response capabilities of preferred embodiments o the inventive system, though these capabilities can optionally be used if repeaters are present; (3) once the updated map is built, die root device preferably uses it to individually address each device in the system using the command/response capabilities of preferred embodiments of the invention.
  • Leaf nodes that do not have routers are preferably addressed through their "surrogate" router(s) as explained above; and (4) the root device occasionally queries the closest router(s) for status change information (each router preferably gathers such status change information from all downstream routers on a continuous basis). When a status change is detected, the root device can query each appropriate individual router for more detailed infor ation.
  • the router of an embodiment ofthe inventive repeater e.g., router 4 of repeater 3 of Fig. 2
  • the switch can. be a cross-point switch that allows any of its inputs to be connected to any of its outputs, hi variations on such an implementation, the router functions as two or more switches that are "ganged" subject to the following rules :
  • any output port may be connected to at most one input port at a time; • an input port may be connected to more than one output port;
  • the invention is a method for designing a tree- structured communication system that is to include a transmitter configured to assert addresses and commands, at least one primary repeater having a primary router and being configured to be coupled to the transmitter downstream from said transmitter, and at least two secondary repeaters, each having a secondary router and being configured to be coupled to the primary repeater downstream from said primary repeater.
  • the method includes the steps of assigning a router access address to each of the secondary routers, such that all of the secondary routers share said router access address; and assigning a unique router address to each said primary router and each ofthe secondary routers, such that no two oT the primary and secondary routers share one said router address.
  • the method also includes one or both ofthe steps of: assigning the router access address to each said primary router, such that all ofthe primary and secondary routers share said router access address; and assigning at least one additional address to each ofthe secondary repeaters, such that all ofthe secondary routers share each said additional address.
  • the at least one additional address can include one or both of an identification data address (for use in triggering an access to a memory that contains identification data) and a content protection address.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)
EP03816010A 2003-12-08 2003-12-08 Integriertes adressierungsschema zur verwendung in einem system mit einer baumstruktur Withdrawn EP1762094A4 (de)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2003/026519 WO2005091734A2 (en) 2003-12-08 2003-12-08 Integrated adressin scheme for use in a system having a tree structure

Publications (2)

Publication Number Publication Date
EP1762094A2 true EP1762094A2 (de) 2007-03-14
EP1762094A4 EP1762094A4 (de) 2007-11-14

Family

ID=35056619

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03816010A Withdrawn EP1762094A4 (de) 2003-12-08 2003-12-08 Integriertes adressierungsschema zur verwendung in einem system mit einer baumstruktur

Country Status (3)

Country Link
EP (1) EP1762094A4 (de)
JP (1) JP2007536762A (de)
WO (1) WO2005091734A2 (de)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5335309B2 (ja) * 2008-07-22 2013-11-06 キヤノン株式会社 通信装置
TW201008574A (en) 2008-08-19 2010-03-01 Oncotherapy Science Inc INHBB epitope peptides and vaccines containing the same

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4250489A (en) * 1978-10-31 1981-02-10 Westinghouse Electric Corp. Distribution network communication system having branch connected repeaters
EP0511851A2 (de) * 1991-04-30 1992-11-04 Hewlett-Packard Company Ermittlung der physikalischen Topologie über Verstärker und Brücken in einem Computernetzwerk
EP0871310A2 (de) * 1997-04-07 1998-10-14 Yazaki Corporation Verfahren und System zur Adresseneinstellung in einem Baumstruktur

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5754540A (en) * 1995-07-18 1998-05-19 Macronix International Co., Ltd. Expandable integrated circuit multiport repeater controller with multiple media independent interfaces and mixed media connections
US5742603A (en) * 1995-09-14 1998-04-21 Level One Communications, Inc. Method and apparatus for integrating repeater management, media access control, and bridging functions
US5764638A (en) * 1995-09-14 1998-06-09 Level One Communications, Inc. Method and apparatus for filtering and forwarding messages in a computer network using a last source address
US6115391A (en) * 1997-02-20 2000-09-05 Level One Communications, Inc. Method and apparatus for integrating multiple repeaters into a single collision domain

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4250489A (en) * 1978-10-31 1981-02-10 Westinghouse Electric Corp. Distribution network communication system having branch connected repeaters
EP0511851A2 (de) * 1991-04-30 1992-11-04 Hewlett-Packard Company Ermittlung der physikalischen Topologie über Verstärker und Brücken in einem Computernetzwerk
EP0871310A2 (de) * 1997-04-07 1998-10-14 Yazaki Corporation Verfahren und System zur Adresseneinstellung in einem Baumstruktur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of WO2005091734A3 *

Also Published As

Publication number Publication date
WO2005091734A2 (en) 2005-10-06
JP2007536762A (ja) 2007-12-13
EP1762094A4 (de) 2007-11-14
WO2005091734A3 (en) 2007-05-24

Similar Documents

Publication Publication Date Title
US6388591B1 (en) Apparatus and method for receiving data serially for use with an advanced technology attachment packet interface (atapi)
US6388590B1 (en) Apparatus and method for transmitting data serially for use with an advanced technology attachment packet interface (atapi)
US8190786B2 (en) Data receiver, data transmitter, and information processing method, and computer program
KR100814207B1 (ko) 케이블, 케이블을 포함하는 시스템 및 케이블 데이터 제공방법
JP4794574B2 (ja) 光無線通信のための方法及び装置
AU2017245363B2 (en) Human interface device switch with security function
US7187307B1 (en) Method and system for encapsulation of multiple levels of communication protocol functionality within line codes
US6954491B1 (en) Methods and systems for sending side-channel data during data inactive period
US7225282B1 (en) Method and apparatus for a two-wire serial command bus interface
WO2015137716A1 (ko) Hdmi를 사용한 데이터 송수신 기기 및 방법
US20060117367A1 (en) Integrated addressing scheme for use in a system having a tree structure
US20220358074A1 (en) PCIe-Based Data Transmission Method, Apparatus, and System
US10129019B2 (en) DP HDCP version converter
US20220365899A1 (en) PCIe-Based Data Transmission Method, Apparatus, and System
US20200257649A1 (en) Transmitting displayport 2.0 information using usb4
KR102095911B1 (ko) 오디오 리턴 데이터 링크를 통한 디지털 컨텐트 보호
EP1762094A2 (de) Integriertes adressierungsschema zur verwendung in einem system mit einer baumstruktur
KR100814223B1 (ko) 트리 구조를 갖는 시스템에서 사용하기 위한 통합 어드레싱방식
JP2002164898A (ja) データ送受信装置及びデータ送受信方法
JP3851904B2 (ja) 一群の受信ワードの各ワードを単一送信ワードにマッピングすることで連続リンク送信上のシンボル間干渉効果を低減させる方法および装置。
US10860503B2 (en) Virtual pipe for connecting devices
JP3742518B2 (ja) バスブリッジおよび記録媒体
WO2005015820A1 (ja) データ転送装置
Alicke et al. Comparing Bus Solutions
SU642701A1 (ru) Устройство дл сопр жени электронной вычислительной машины с абонентами

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060627

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT RO SE SI SK TR

PUAK Availability of information related to the publication of the international search report

Free format text: ORIGINAL CODE: 0009015

A4 Supplementary search report drawn up and despatched

Effective date: 20071016

17Q First examination report despatched

Effective date: 20080708

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20090908