US20130191570A1 - MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) - Google Patents
MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) Download PDFInfo
- Publication number
- US20130191570A1 US20130191570A1 US13/521,739 US201113521739A US2013191570A1 US 20130191570 A1 US20130191570 A1 US 20130191570A1 US 201113521739 A US201113521739 A US 201113521739A US 2013191570 A1 US2013191570 A1 US 2013191570A1
- Authority
- US
- United States
- Prior art keywords
- usb
- packet
- port
- usb port
- upstream
- 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.)
- Abandoned
Links
- 230000003993 interaction Effects 0.000 title 1
- 238000011144 upstream manufacturing Methods 0.000 claims abstract description 173
- 238000000034 method Methods 0.000 claims description 33
- 230000004044 response Effects 0.000 claims description 15
- 238000012544 monitoring process Methods 0.000 claims description 9
- 238000007726 management method Methods 0.000 claims description 8
- 230000011664 signaling Effects 0.000 claims description 7
- 230000003139 buffering effect Effects 0.000 claims description 6
- 230000000903 blocking effect Effects 0.000 claims description 2
- 230000008859 change Effects 0.000 claims description 2
- 230000008901 benefit Effects 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 4
- 239000000872 buffer Substances 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing 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/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
- G06F13/4286—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus using a handshaking protocol, e.g. RS232C link
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing 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/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
- H04N21/43632—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wired protocol, e.g. IEEE 1394
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing 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/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
- H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
- H04N21/43632—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wired protocol, e.g. IEEE 1394
- H04N21/43635—HDMI
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2370/00—Aspects of data communication
- G09G2370/04—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller
- G09G2370/045—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller using multiple communication channels, e.g. parallel and serial
- G09G2370/047—Exchange of auxiliary data, i.e. other than image data, between monitor and graphics controller using multiple communication channels, e.g. parallel and serial using display data channel standard [DDC] communication
-
- G—PHYSICS
- G09—EDUCATION; CRYPTOGRAPHY; DISPLAY; ADVERTISING; SEALS
- G09G—ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION
- G09G2370/00—Aspects of data communication
- G09G2370/12—Use of DVI or HDMI protocol in interfaces along the display data pipeline
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2838—Distribution of signals within a home automation network, e.g. involving splitting/multiplexing signals to/from different paths
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L2012/2847—Home automation networks characterised by the type of home appliance used
- H04L2012/2849—Audio/video appliances
Definitions
- DiiVA Digital Interactive Interface For Video And Audio
- DiiVA is a bi-directional audio/video interface that allows uncompressed high-definition video, as well as multi-channel audio, high-bandwidth, and bi-directional data to be transferred over a single cable.
- DiiVA implements a bi-directional hybrid data channel capable of transporting different types of data, including but not limited to audio data, control data, Ethernet data, and bulk data.
- USB Universal Serial Bus
- FIG. 1 illustrates one example of a USB connection with a DiiVA network, in accordance with one embodiment of the present disclosure.
- FIG. 2 is a block diagram of a system configured to communicate USB data over a DiiVA network, in accordance with one embodiment of the present disclosure.
- FIG. 3 illustrates turn-around time constraint in USB, in accordance with one embodiment of the present disclosure.
- FIG. 4A illustrates one example of a Hybrid Link USB packet, in accordance with one embodiment of the present disclosure.
- FIG. 4B is a table illustrating the SSINFO Field of the Hybrid Link USB packet shown in FIG. 3
- FIG. 5 schematically illustrates one example of high-speed USB enumeration, in accordance with one embodiment of the present disclosure.
- FIG. 6 illustrates an example of control transfer in DiiVA USB, in accordance with one embodiment of the present disclosure.
- DiiVA which includes a bi-directional hybrid link as well as uni-directional links.
- DiiVA is a bi-directional audio/video interface that can allows uncompressed high-definition video, multi-channel audio, and high-bandwidth, bi-directional data to be all transferred over a single cable.
- DiiVA implements a bi-directional hybrid link capable of carrying audio, control, and bulk (Ethernet and USB) data, and status information.
- DiiVA also includes uni-directional video links dedicated to carrying noncompressed video pixel data and synchronization.
- DiiVA cable contain four twisted pairs, one of which is the hybrid link, and the remaining three of which comprise the uni-directional video links.
- DiiVA allows users to connect, configure and control a plurality of consumer electronic devices (including without limitation DVD players, digital video recorders, set top boxes, personal computers, camcorders, cameras, and home stereo systems, just by way of example) from their digital TV or other DiiVA node.
- USB 2.0 specification and “USB 3.0 specification,” which are publicly available through the internet, and which are incorporated herein by reference in their entireties.
- the techniques disclosed in the present disclosure may be used for the transfer of multi-media data and network management in any other system (i.e., system other than DiiVA) that includes the capability of both uni-directional and bi-directional data transfer over a single cable.
- system other than DiiVA system other than DiiVA
- FIG. 1 schematically illustrates one example of a USB connection in a DiiVA network.
- one or more DiiVA Hybrids Link serve to extend the USB connection through a DiiVA network 110 .
- USB in DiiVA can seamlessly connect a USB host 120 to at least one USB device 130 to the DiiVA network 110 .
- the DiiVA network 110 can function as if there were only a USB cable between the USB host 120 and the USB device 130 .
- the DiiVA network as a whole, inclusive of the USB device 130 can function as if there were only a USB device 130 connected to the USB host 120 through a USB cable and a USB upstream port, i.e., a USB port that faces upstream.
- FIG. 2 is a schematic block diagram of a system 200 configured to communicate USB data over a DiiVA network 210 , in accordance with one embodiment of the present disclosure.
- the system 200 includes a USB host controller 220 (for example a personal computer) connected to at least one USB device 230 (examples of which include without limitation a webcam or a memory stick) through a USB connection.
- the USB connection requires two DiiVA devices, DiiVA device A (shown with reference numeral 205 ) and DiiVA device B (shown with reference numeral 206 ), one connected to the USB host 220 and the other connected to the USB device 230 .
- USB host 220 is connected to a USB upstream port 225 of DiiVA device A ( 205 ), and USB device 230 is connected to USB downstream port 226 of DiiVA device B ( 206 ).
- a DiiVA device can have multiple USB upstream ports or multiple USB downstream ports, as seen in FIG. 2 .
- the system 200 thus includes a first DiiVA device 205 connected to the USB host controller 220 through an upstream USB port 225 , a second DiiVA device 206 connected to the USB device 230 through a downstream USB port 226 ; and a DiiVA network 210 connecting the two DiiVA devices 205 and 206 .
- the DiiVA network 210 includes at least one bi-directional DiiVA hybrid link 240 , and transfers data through the link between the first DiiVA device 205 and the second DiiVA device 206 , according to USB protocol.
- the elements in the DiiVA network 210 including but not limited to the hybrid link 240 , and the first and second DiiVA device 205 and 206 , all include hardware such as a processor or controller configured to carry out the functions described in the present disclosure.
- the network 210 is responsive to the USB host controller 220 to deliver contents for the USB protocol by transmitting through the hybrid link 240 at least one line state information packet and at least one USB data packet, between the upstream USB port 225 and the downstream USB port 226 .
- the first 205 and second 206 DiiVA device each include a USB PHY (physical layer) 232 connected to logical module 234 through an interface 236 .
- the logical module 234 may be a transceiver having bi-directional connection and configured to carry and share multi-protocol data.
- the interface 236 is UTMI (USB 2.0. Transceiver Microcell Interface) or ULPI (UTMI+Low Pin Interface). In other embodiments, interfaces other than UTMI or ULPI may be used.
- USB protocol relies on line state information, or the state of D+ and D ⁇ , and has limitations on turn-around time and the cable length.
- a DiiVA network does not guarantee delivery time and thus take a long time.
- FIG. 3 illustrates such a turn-around time constraint in USB, in accordance with one embodiment of the present disclosure.
- USB protocol defines the bus turn-around time limitation and it is considered as error if the response does not arrive within given time.
- DiiVA protocol itself does not guarantee the Hybrid Link Packet delay.
- USB in DiiVA uses USB flow-control protocol with NAK for Bulk/Control/Interrupt Transfer.
- USB protocol defines both minimum and maximum period of the turn-around time and the inter-packet delay.
- the minimum period can be controlled by buffering the USB data packet.
- the maximum period cannot be easily met because DiiVA network has inherent network delay and also does not guarantee the inter-packet delay. This issue affects the bus turn-around timing in two ways. One is when USB host waits and the other is when USB device waits as shown in FIG. 3 .
- DiiVA specific protocols for USB are described that overcome these limitations. Examples include without limitation The line state emulation, flow-control mechanism, and speculative ACK/NAK. By using these protocols, any USB host to any USB device point-to-point connection can be made through a DiiVA network. Multiple point-to-point connections also are possible under DCL management.
- USB line state information is available only when the USB host and the USB device are physically connected. As shown in FIG. 2 , however, the DiiVA network 210 , the USB host 220 and the USB device 230 are not directly connected, so line state information is not readily available.
- line state information at the UTMI (or ULPI) interface 260 of USB host 220 and USB device 230 is delivered over the DiiVA network 210 by a hybrid link USB packet to the other side of the USB host 220 and the USB device 230 .
- the line state information packet transmitted through the hybrid link 240 contains packetized line state information about one or more events.
- FIG. 4A illustrates one example of such a hybrid link USB packet 400 , in accordance with one embodiment of the present disclosure.
- Source and destination information i.e. the exact USB port, can be specified with a combination of CH_ID and Service ID information.
- the hybrid link USB packet contains a variety of USB related information.
- the SSINFO field of Hybrid Link USB Packet carries this information.
- FIG. 4B is a table illustrating the line state events for which information is contained the SSINFO field of the hybrid link USB packet shown in FIG. 4A .
- the prefix UU_ indicates the packet direction from USB Upstream-facing port to USB Downstream-facing port.
- UD_prefix indicates the reverse direction.
- J state and K state definitions in FIG. 4B follow those for full-speed USB as set forth in the USB 2.0 specification.
- Address and Endpoint fields, between bits 16 and 27 indicate the generic USB Packet USB address and USB endpoint.
- a transmitting USB port packetizes all line state information and transmits the packetized information to a receiving USB port.
- the receiving USB port sets the UTMI or ULPI interface to emulate the line state behavior of the transmitting USB port.
- the upstream USB port 225 is the transmitting USB port and the downstream USB port 226 is the receiving USB port. In other embodiments, the upstream USB port 225 is the receiving USB port and the downstream USB port 226 is the transmitting USB port.
- Enumeration in USB is a process of determining what device has just been connected to the bus, and what parameters (such as power consumption, number of endpoints etc.) it requires.
- the USB device enumeration process thus starts when a USB device is first connected to a USB host.
- the USB host assigns the device a unique address and sets up a configuration that allows the device to transfer data on the bus.
- FIG. 5 schematically illustrates one example of a method 500 of performing high-speed USB enumeration in a DiiVA network, in accordance with one embodiment of the present disclosure.
- a high-speed USB device is attached to a USB downstream port 515 , as illustrated in step 510 , namely USB device attach.
- a UD_FS_DEVICE_READY packet 518 is then sent to a USB upstream port 516 .
- the USB host is attached, as shown in the step 520 , namely USB host Plug In. VBus assertion in the USB upstream port 516 is detected.
- the USB upstream port 516 sends UU_VBUS_DETECT 524 to the USB downstream port 515 and the USB downstream port 515 deasserts VBus, as shown in the deassertion step, 525 .
- the USB upstream port 516 sends UU_VBUS_ENABLE 532 to the USB downstream port 515 and the USB downstream port 515 asserts Bus, step 522 .
- the USB downstream port 515 detects J state, step 534 , and sends UD_J_STATE 536 to the USB upstream port 516 .
- the USB upstream port 516 detects USB Reset from the USB host, step 540 , and sends UU_USB_RESET 542 .
- the USB downstream port 515 then detects K Chip in step 546 , and sends UD_K_STATE 544 .
- the USB downstream port 515 detects SE0 state and send UD_SEO_STATE 548 .
- step 550 toggling K-J Chirps are detected and UU_K_STATE 552 and UU_J_STATE 554 are sent to the USB downstream port 515 .
- SOF is detected from the USB host in step 560 , and high-speed enumeration is complete.
- USB Full Speed enumeration and/or USB Low Speed enumeration may be performed.
- performing Full Speed enumeration may comprise the acts of:
- Low Speed enumeration may be performed.
- performing Low Speed enumeration may comprise the acts of:
- the upstream USB port sends VBus Enable event packet to the downstream USB port, and the downstream USB port asserting Vbus;
- the downstream USB port detecting K State, and sending K State event packet; the upstream USB port detecting USB Reset from the USB host controller and sending USB Reset event packet;
- the upstream USB port detecting K state, and sending the K State Event packet to the downstream USB port;
- a USB Suspend and Resume operation may be performed.
- the following acts may be performed:
- upstream USB port detects K State, upstream USB port generating K State event packet and going to Resume state.
- USB host During an IN transaction, USB host expects Data packet or handshake after IN is issued within maximum bus turn-around time.
- the OUT transaction requires the same constraint on the handshake after OUT/SETUP and Data is transmitted.
- the USB Upstream-facing port in DiiVA device uses NAK with a flow control mechanism illustrated in FIG. 6 , in one embodiment of the present disclosure.
- an USB upstream port 625 receives SETUP and delivers the SETUP USB packet to a USB downstream port 626 .
- the downstream USB port 626 buffers this SETUP until next DATA is available on the downstream USB port. Meanwhile, the upstream USB port 625 sends a speculative ACK even if ACK from USB device is not available.
- the downstream USB port 626 starts to send SETUP and DATA and receives ACK.
- the IN transaction and OUT transaction occur as follows: the upstream USB port 625 receives IN and delivers to the downstream USB port 626 .
- the downstream USB port 626 sends IN and get the response from the USB device.
- the upstream USB port 625 first sends NAK for IN or OUT/DATA until DATA or handshake are available from the USB device.
- the USB upstream port 625 unblocks the next coming IN or OUT/DATA and delivers to the USB downstream port 626 to send IN or OUT/DATA to the USB device again with NAK handshake to the USB host. If the USB device sends DATA for IN or ACK for OUT/DATA and DATA or ACK arrives at the USB upstream port 625 , the USB downstream port 626 responds with ACK for IN transaction and delivers this DATA for IN or ACK for OUT to the USB upstream port 625 . The USB upstream port 625 sends DATA for next IN available or ACK for next OUT/DATA available.
- the USB upstream port 625 always responds with ACK for SETUP transaction because it is required to receive SETUP and DATA and responds with ACK according to USB Specification.
- the USB downstream port 626 buffers OUT or SETUP until next coming DATA is available in the USB downstream port 626 to guarantee the inter-packet delay between OUT/SETUP and DATA.
- USB supports a number of different types of data transfers: isochronous, interrupt, bulk, and control transfers.
- Isochronous transfers occur at some guaranteed data rate but with possible data loss, for example for real time audio or video.
- Interrupt transfers are used for devices that need guaranteed quick responses (bounded latency), such as pointing devices and keyboards.
- Bulk transfers are large sporadic transfers that use all remaining available bandwidth, but have no guarantees on bandwidth or latency, such as file transfers.
- Control transfers are typically used for short, simple commands to the device, and a status response, used, for example, by the bus control pipe number 0.
- isochronous transfers use zero data and pipelines IN transaction scheme.
- the USB upstream port responds with zero data, which is legitimate in the USB specification.
- This first IN is delivered to a USB downstream port and gets the DATA from an isochronous USB device.
- This first DATA is used to reply to the next isochronous IN when it arrives at USB upstream module. In this way, the USB host receives the delayed and pipelined isochronous DATA from the USB device.
- USB host stops to send isochronous IN, the last remaining DATA packets are dropped.
- An isochronous OUT transaction is delivered to the USB downstream port without NAK.
- the inter-packet delay between OUT and DATA should be maintained by buffering OUT until DATA is available in the USB downstream port.
- the USB upstream port should know which USB address and USB endpoint are used for isochronous transfer. To obtain this information, DiiVA USB should have the capability to decode the descriptor from the USB device.
- Decoding descriptor can be done by analyzing the hybrid link USB packet, or the USB downstream port may have USB Host capability to enumerate and read out the descriptor from the USB device before connecting a USB upstream port to a USB downstream port.
- the descriptor decoding method is implementation-dependent and other implementations are possible.
- DiiVA USB supports high bandwidth isochronous IN endpoints by the following method: only the first isochronous IN per micro frame is delivered.
- the USB downstream port receives the DATA for isochronous IN, it itself should decide how many INs need to be sent based on the DATA PID. If first Data PID is DATA0, the USB downstream port behaves like above pipelined isochronous transfer scheme. If the first Data PID is DATA2, the USB downstream port generates two more same INs in the same micro frame. If the first Data PID is DATA1, the USB downstream port generates one more same IN.
- the USB upstream port should have enough buffer to accommodate the maximum DATA size per frame in high bandwidth isochronous endpoint.
- a method of delivering USB data through a hybrid link with an isochronous IN token may comprise the following acts:
- an upstream port responding with one or more zero data packets
- USB host stops sending isochronous IN packets, dropping the last and remaining DATA;
- the upstream USB port finding out which endpoint and address are used for isochronous endpoint, by monitoring and decoding USB descriptor from DATA packet stream.
- a method of delivering USB data through a hybrid link with an isochronous OUT token may comprise:
- the upstream USB port finding out which endpoint and address are used for isochronous endpoint by monitoring and decoding USB descriptor from DATA packet stream.
- non-isochronous transfers of USB data may also be performed using DiiVA specific protocols.
- USB data may be delivered with a non-isochronous IN token, by performing the following acts:
- USB device sends a DATA0 or aDATA1 packet and the DATA0 or the DATA1 packet arrives in upstream USB port, the downstream port responding with an ACK packet and delivers the DATA0 or the DATA1 packet to the upstream port;
- the upstream port sending the DATA0 or DATA1 packet for the next available IN packet.
- USB data may be delivered with a non-isochronous OUT token, by performing the following acts:
- an upstream USB port receiving an OUT packet and either a DATA0 or a DATA1 packet and delivering to a downstream USB port;
- the downstream USB port buffering the OUT packet until the DATA0 or the DATA1 packet is available, and when the DATA0 or the DATA1 packet is available, sending the OUT packet and the DATA0 or the DATA1 packet to a USB device;
- the upstream USB port sending a NAK packet for the OUT transaction and not delivering the next incoming OUT packet and DATA0 or DATA1 packet until the response from downstream USB port is available;
- USB device sends a NAK packet for the OUT transaction and downstream USB port sends a NAK packet to the upstream USB port, the upstream USB port delivering the next incoming OUT packet and the DATA0 or DATA1 packet to the downstream port again;
- the upstream port sending ACK for the next OUT transaction.
- transfer of USB data may be performed using PING packets.
- PING protocol is implemented when the USB host gets NAK for OUT transaction.
- the USB upstream port responds with NAK and does not deliver the PING packet to the USB downstream port.
- the USB upstream port blocks PING and keeps sending NAK until the response for OUT transaction from the USB device is available.
- the USB upstream port responds with ACK for the next PING and also responds with ACK for next OUT transaction. This last OUT transaction is not delivered to the USB downstream port because the USB device already accepted the first OUT transaction.
- the USB upstream port delivers the next PING to the USB downstream port.
- the USB upstream module responds with ACK for next PING and responds with ACK for next OUT transaction. This last OUT transaction is delivered to the USB device and is expected to be responded with ACK.
- the USB upstream port responds with NAK for next PING and PING is delivered to the USB device again. This step is repeated until the USB device responds with ACK for PING. And the scenario follows the above step when the USB device responds with ACK.
- a method of delivering data through a hybrid link using a USB PING packet may comprise:
- an upstream USB port responds with NAK packet to OUT transaction
- the upstream USB port not delivering PING packet, and continuing to send NAK packet until the response from USB device is available;
- a USB device responds with ACK packet for OUT transaction, the upstream USB port responding with ACK packet for the next incoming PING packet and responding with ACK packet for the next OUT transaction; wherein the last OUT transaction is not delivered to the downstream USB port;
- the USB device if the USB device responds with NAK packet for OUT transaction and NAK packet is delivered to upstream USB port, the upstream USB port delivering next PING packet to the downstream USB port;
- the upstream USB port delivering the next PING packet to the downstream USB port;
- USB device responds with ACK packet with PING packet and ACK packet is delivered to upstream USB port, the upstream USB port responding with ACK packet for next PING packet;
- PING is used without a preceding OUT transaction.
- the USB upstream port responds with NAK and delivers PING to the USB downstream port.
- the USB upstream port does not deliver PING and keeps sending NAK until the response from the USB device is available.
- the USB upstream port responds with ACK for next PING and also responds with ACK for next OUT transaction.
- this last OUT transaction is delivered to the USB downstream port unlike the first scenario because no OUT transaction is delivered to the USB device yet.
- USB upstream port responds with NAK for next PING and delivers PING to the USB downstream port. This step is repeated until the USB downstream port gets ACK from the USB device.
- the acts when USB device responds with ACK, as described above, are then followed.
- the DiiVA USB module When the USB device responds with NYET for OUT Transaction, the DiiVA USB module considers NYET as ACK and the USB upstream port always sends ACK instead of NYET.
- a method of delivering data through a hybrid link using a USB PING packet may comprise:
- the upstream USB port not delivering PING packet and continuing to send NAK packet until response from USB device is available;
- USB device responds with ACK packet for PING packet and ACK packet is delivered to upstream USB port, the upstream USB port responding with ACK packet for the next PING packet and responding with ACK for the next OUT transaction;
- USB address management in a DiiVA network may be performed as follows.
- a USB upstream port can be attached to any hub downstream port, and packets with various USB addresses can be broadcasted to the USB upstream port.
- the USB upstream port should be able to recognize which USB address is assigned to the USB upstream port and it should not respond to generic USB packets for any other USB Device.
- USB upstream port accepts only generic USB packet with USB Address 0.
- USB upstream port recognizes which USB address is assigned to the USB device in the USB downstream port.
- USB upstream port After detecting SET_ADDRESS standard USB Device request, the USB upstream port only responds with generic USB packets with the newly assigned USB address. If USB Reset is detected in the USB upstream port, it resets the assigned USB address to 0 and waits for SET_ADDRESS standard USB device request again. Decoding SET_ADDRESS Device request is implementation specific.
- a method of USB address management in a DiiVA network may comprise:
- the upstream port recognizing which USB address is assigned to the USB device in the downstream port by monitoring and decoding SET_ADDRESS standard USB device request;
- the upstream port after detecting SET_ADDRESS standard USB device request, the upstream port only responding with packets with new USB address which is assigned with SET_ADDRESS standard USB device request;
- USB Reset resetting the assigned USB address to 0 and waiting for SET_ADDRESS standard USB device request again.
- Keep-Alive forwarding in a DiiVA network may be performed as follows.
- the USB upstream port starts to monitor line state.
- first toggling of line state is detected, it is considered as first Keep-Alive signaling.
- the USB upstream port sets the internal timer for T_KEEP_ALIVE and when it is expired, it starts to monitor line state toggling again to detect Keep-Alive.
- T_KEEP_ALIVE is set to 0.98 ms.
- Keep-Alive signaling is delivered to USB Downstream Module through UU_KEEP_ALIVE.
- a method of performing USB low speed Keep-Alive signaling in a DiiVA network may comprise:
- the upstream USB port setting the internal timer for T_KEEP_ALIVE and when it is expired, the upstream USB port monitoring whether line state is toggling again, to detect Keep-Alive and deliver Keep Alive event packet to downstream USB port.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Information Transfer Systems (AREA)
- Automation & Control Theory (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
- Small-Scale Networks (AREA)
Abstract
Description
- The present application is based upon, and claims the benefit of priority under 35 U.S.C. §119, to co-pending U.S. Provisional Patent Application No. 61/294,476 (the “'476 provisional application”), filed Jan. 12, 2010 and entitled “Multi-Media Data Transfer And Network Management Over A Cable Having Both Bi-Directional And Uni-Directional Links.” The content of the '476 provisional application is incorporated herein by reference in its entirety as though fully set forth.
- The present application is related to U.S. patent application Ser. No. 12/057,051, entitled “Bi-Directional Digital Interface For Video And Audio (DIVA),” filed Mar. 27, 2008, and U.S. patent application Ser. No. 12/636,063, entitled “Power Delivery Over Digital INTERFACE FOR VIDEO AND AUDIO (DiiVA),” filed Dec. 11, 2009. Both applications are incorporated herein by reference in their entireties.
- DiiVA (Digital Interactive Interface For Video And Audio) is a bi-directional audio/video interface that allows uncompressed high-definition video, as well as multi-channel audio, high-bandwidth, and bi-directional data to be transferred over a single cable. In addition to uni-directional video channels, DiiVA implements a bi-directional hybrid data channel capable of transporting different types of data, including but not limited to audio data, control data, Ethernet data, and bulk data.
- The USB (Universal Serial Bus) specification is widely used in order to establish communication between various devices and a host controller such as a personal computer, having now effectively taken the place of a number of previously implemented interfaces such as serial and parallel ports.
- Methods and systems are needed for reliably transferring USB data over networks such as DiiVA.
- The drawings disclose illustrative embodiments. They do not set forth all embodiments. Other embodiments may be used in addition or instead. When the same numeral appears in different drawings, it is intended to refer to the same or like components or steps.
-
FIG. 1 illustrates one example of a USB connection with a DiiVA network, in accordance with one embodiment of the present disclosure. -
FIG. 2 is a block diagram of a system configured to communicate USB data over a DiiVA network, in accordance with one embodiment of the present disclosure. -
FIG. 3 illustrates turn-around time constraint in USB, in accordance with one embodiment of the present disclosure. -
FIG. 4A illustrates one example of a Hybrid Link USB packet, in accordance with one embodiment of the present disclosure. -
FIG. 4B is a table illustrating the SSINFO Field of the Hybrid Link USB packet shown inFIG. 3 -
FIG. 5 schematically illustrates one example of high-speed USB enumeration, in accordance with one embodiment of the present disclosure. -
FIG. 6 illustrates an example of control transfer in DiiVA USB, in accordance with one embodiment of the present disclosure. - In the present disclosure, methods and systems are disclosed for transfer of USB data and multi-media data over networks such as DiiVA which includes a bi-directional hybrid link as well as uni-directional links. DiiVA is a bi-directional audio/video interface that can allows uncompressed high-definition video, multi-channel audio, and high-bandwidth, bi-directional data to be all transferred over a single cable. In particular, DiiVA implements a bi-directional hybrid link capable of carrying audio, control, and bulk (Ethernet and USB) data, and status information. DiiVA also includes uni-directional video links dedicated to carrying noncompressed video pixel data and synchronization.
- In some embodiments, DiiVA cable contain four twisted pairs, one of which is the hybrid link, and the remaining three of which comprise the uni-directional video links. DiiVA allows users to connect, configure and control a plurality of consumer electronic devices (including without limitation DVD players, digital video recorders, set top boxes, personal computers, camcorders, cameras, and home stereo systems, just by way of example) from their digital TV or other DiiVA node.
- Full details regarding USB are available in references such as “USB 2.0 specification” and “USB 3.0 specification,” which are publicly available through the internet, and which are incorporated herein by reference in their entireties.
- The techniques disclosed in the present disclosure may be used for the transfer of multi-media data and network management in any other system (i.e., system other than DiiVA) that includes the capability of both uni-directional and bi-directional data transfer over a single cable.
- Illustrative embodiments are discussed. Other embodiments may be used in addition or instead.
-
FIG. 1 schematically illustrates one example of a USB connection in a DiiVA network. As illustrated inFIG. 1 , in some embodiments of the present disclosure one or more DiiVA Hybrids Link serve to extend the USB connection through a DiiVAnetwork 110. Using the methods and systems described in the present disclosure, USB in DiiVA can seamlessly connect aUSB host 120 to at least oneUSB device 130 to the DiiVAnetwork 110. The DiiVAnetwork 110 can function as if there were only a USB cable between theUSB host 120 and theUSB device 130. The DiiVA network as a whole, inclusive of theUSB device 130, can function as if there were only aUSB device 130 connected to theUSB host 120 through a USB cable and a USB upstream port, i.e., a USB port that faces upstream. -
FIG. 2 is a schematic block diagram of asystem 200 configured to communicate USB data over a DiiVAnetwork 210, in accordance with one embodiment of the present disclosure. Thesystem 200 includes a USB host controller 220 (for example a personal computer) connected to at least one USB device 230 (examples of which include without limitation a webcam or a memory stick) through a USB connection. The USB connection requires two DiiVA devices, DiiVA device A (shown with reference numeral 205) and DiiVA device B (shown with reference numeral 206), one connected to theUSB host 220 and the other connected to theUSB device 230. - In the embodiment illustrated in
FIG. 2 ,USB host 220 is connected to a USBupstream port 225 of DiiVA device A (205), andUSB device 230 is connected to USBdownstream port 226 of DiiVA device B (206). In general, a DiiVA device can have multiple USB upstream ports or multiple USB downstream ports, as seen inFIG. 2 . In sum, thesystem 200 thus includes a first DiiVAdevice 205 connected to theUSB host controller 220 through anupstream USB port 225, a second DiiVAdevice 206 connected to theUSB device 230 through adownstream USB port 226; and a DiiVAnetwork 210 connecting the two DiiVAdevices - The DiiVA
network 210 includes at least one bi-directional DiiVAhybrid link 240, and transfers data through the link between the first DiiVAdevice 205 and the second DiiVAdevice 206, according to USB protocol. - The elements in the DiiVA
network 210, including but not limited to thehybrid link 240, and the first and second DiiVAdevice - The
network 210 is responsive to theUSB host controller 220 to deliver contents for the USB protocol by transmitting through thehybrid link 240 at least one line state information packet and at least one USB data packet, between theupstream USB port 225 and thedownstream USB port 226. - The first 205 and second 206 DiiVA device each include a USB PHY (physical layer) 232 connected to
logical module 234 through aninterface 236. Thelogical module 234 may be a transceiver having bi-directional connection and configured to carry and share multi-protocol data. In some embodiments, theinterface 236 is UTMI (USB 2.0. Transceiver Microcell Interface) or ULPI (UTMI+Low Pin Interface). In other embodiments, interfaces other than UTMI or ULPI may be used. - In general, USB protocol relies on line state information, or the state of D+ and D−, and has limitations on turn-around time and the cable length. A DiiVA network, however, does not guarantee delivery time and thus take a long time.
-
FIG. 3 illustrates such a turn-around time constraint in USB, in accordance with one embodiment of the present disclosure. USB protocol defines the bus turn-around time limitation and it is considered as error if the response does not arrive within given time. However, DiiVA protocol itself does not guarantee the Hybrid Link Packet delay. To overcome this limitation, USB in DiiVA uses USB flow-control protocol with NAK for Bulk/Control/Interrupt Transfer. - USB protocol defines both minimum and maximum period of the turn-around time and the inter-packet delay. The minimum period can be controlled by buffering the USB data packet. But the maximum period cannot be easily met because DiiVA network has inherent network delay and also does not guarantee the inter-packet delay. This issue affects the bus turn-around timing in two ways. One is when USB host waits and the other is when USB device waits as shown in
FIG. 3 . - In the present disclosure, DiiVA specific protocols for USB are described that overcome these limitations. Examples include without limitation The line state emulation, flow-control mechanism, and speculative ACK/NAK. By using these protocols, any USB host to any USB device point-to-point connection can be made through a DiiVA network. Multiple point-to-point connections also are possible under DCL management.
- USB line state information is available only when the USB host and the USB device are physically connected. As shown in
FIG. 2 , however, theDiiVA network 210, theUSB host 220 and theUSB device 230 are not directly connected, so line state information is not readily available. - In DiiVA, all of the line state information and generic USB packets are delivered in the form of hybrid link packet. In some embodiments of the present disclosure, line state information at the UTMI (or ULPI) interface 260 of
USB host 220 andUSB device 230 is delivered over theDiiVA network 210 by a hybrid link USB packet to the other side of theUSB host 220 and theUSB device 230. The line state information packet transmitted through thehybrid link 240 contains packetized line state information about one or more events. -
FIG. 4A illustrates one example of such a hybridlink USB packet 400, in accordance with one embodiment of the present disclosure. Source and destination information, i.e. the exact USB port, can be specified with a combination of CH_ID and Service ID information. - Other than such source and destination information, the hybrid link USB packet contains a variety of USB related information. The SSINFO field of Hybrid Link USB Packet carries this information.
FIG. 4B is a table illustrating the line state events for which information is contained the SSINFO field of the hybrid link USB packet shown inFIG. 4A . - In the table shown in
FIG. 4B , the prefix UU_indicates the packet direction from USB Upstream-facing port to USB Downstream-facing port. UD_prefix indicates the reverse direction. J state and K state definitions inFIG. 4B follow those for full-speed USB as set forth in the USB 2.0 specification. Address and Endpoint fields, between bits 16 and 27, indicate the generic USB Packet USB address and USB endpoint. - Using the line state information packet described in conjunction with
FIG. 4A andFIG. 4B , operations such as USB enumeration, USB suspend/resume, and flow control can be performed over a DiiVA network. In thesystem 200 shown inFIG. 2 , a transmitting USB port packetizes all line state information and transmits the packetized information to a receiving USB port. The receiving USB port sets the UTMI or ULPI interface to emulate the line state behavior of the transmitting USB port. - In some embodiments, the
upstream USB port 225 is the transmitting USB port and thedownstream USB port 226 is the receiving USB port. In other embodiments, theupstream USB port 225 is the receiving USB port and thedownstream USB port 226 is the transmitting USB port. - Enumeration in USB is a process of determining what device has just been connected to the bus, and what parameters (such as power consumption, number of endpoints etc.) it requires. The USB device enumeration process thus starts when a USB device is first connected to a USB host. The USB host assigns the device a unique address and sets up a configuration that allows the device to transfer data on the bus.
-
FIG. 5 schematically illustrates one example of amethod 500 of performing high-speed USB enumeration in a DiiVA network, in accordance with one embodiment of the present disclosure. - In this embodiment, a high-speed USB device is attached to a USB
downstream port 515, as illustrated instep 510, namely USB device attach. AUD_FS_DEVICE_READY packet 518 is then sent to a USBupstream port 516. The USB host is attached, as shown in thestep 520, namely USB host Plug In. VBus assertion in the USBupstream port 516 is detected. The USBupstream port 516 sendsUU_VBUS_DETECT 524 to the USBdownstream port 515 and the USBdownstream port 515 deasserts VBus, as shown in the deassertion step, 525. - The USB
upstream port 516 sendsUU_VBUS_ENABLE 532 to the USBdownstream port 515 and the USBdownstream port 515 asserts Bus,step 522. The USBdownstream port 515 detects J state,step 534, and sendsUD_J_STATE 536 to the USBupstream port 516. The USBupstream port 516 detects USB Reset from the USB host,step 540, and sendsUU_USB_RESET 542. - The USB
downstream port 515 then detects K Chip instep 546, and sendsUD_K_STATE 544. The USBdownstream port 515 detects SE0 state and sendUD_SEO_STATE 548. - In
step 550, toggling K-J Chirps are detected andUU_K_STATE 552 andUU_J_STATE 554 are sent to the USBdownstream port 515. Finally SOF is detected from the USB host instep 560, and high-speed enumeration is complete. - In other embodiments of the present disclosure, USB Full Speed enumeration and/or USB Low Speed enumeration may be performed. In these embodiments, performing Full Speed enumeration may comprise the acts of:
- attaching a full-speed USB device to the downstream USB port, and sending an FS Device Ready event packet to the upstream USB port;
- attaching the USB host controller, and when Bus is asserted, the upstream USB port sending Bus detect event packet to downstream USB port and disserting Bus in the downstream USB port;
- the upstream USB port sending Bus Enable event packet to downstream USB port, and the downstream USB port asserting Bus;
- the downstream USB port detecting J State, and sending J State event packet;
- the upstream USB port detecting USB Reset from the USB host controller and sending USB Reset event packet; and
- detecting J State in upstream USB port and sending J State Event packet to the downstream USB port; and detecting SOF packet from the USB host so that full-speed enumeration is done.
- In other embodiments, Low Speed enumeration may be performed. In these embodiments, performing Low Speed enumeration may comprise the acts of:
- attaching a low-speed USB device to the downstream USB port and sending a LS Device Ready event packet to the upstream USB port;
- attaching the USB host controller, and when VBus is asserted, the upstream USB port sending VBus detect event packet to the downstream USB port and deasserting VBus in the downstream USB port;
- the upstream USB port sends VBus Enable event packet to the downstream USB port, and the downstream USB port asserting Vbus;
- the downstream USB port detecting K State, and sending K State event packet; the upstream USB port detecting USB Reset from the USB host controller and sending USB Reset event packet;
- the upstream USB port detecting K state, and sending the K State Event packet to the downstream USB port; and
- detecting SOF packet from the USB host so that low-speed enumeration is done.
- In some embodiments, a USB Suspend and Resume operation may be performed. In these embodiments, the following acts may be performed:
- detecting a 3 ms Idle State, and generating a 3 ms Idle event packet and delivering same to downstream port;
- if previous speed was high-speed USB, upstream port checking whether 3 ms idle is suspend state or USB Reset according to USB specification and UTMI specification; and
- if upstream USB port detects K State, upstream USB port generating K State event packet and going to Resume state.
- During an IN transaction, USB host expects Data packet or handshake after IN is issued within maximum bus turn-around time. The OUT transaction requires the same constraint on the handshake after OUT/SETUP and Data is transmitted. To resolve this issue in USB host side, the USB Upstream-facing port in DiiVA device uses NAK with a flow control mechanism illustrated in
FIG. 6 , in one embodiment of the present disclosure. - In the
Setup Stage 610, an USBupstream port 625 receives SETUP and delivers the SETUP USB packet to a USBdownstream port 626. Thedownstream USB port 626 buffers this SETUP until next DATA is available on the downstream USB port. Meanwhile, theupstream USB port 625 sends a speculative ACK even if ACK from USB device is not available. When the DATA arrives at thedownstream USB port 626, thedownstream USB port 626 starts to send SETUP and DATA and receives ACK. - In the Data/
Status Stage 610, the IN transaction and OUT transaction occur as follows: theupstream USB port 625 receives IN and delivers to thedownstream USB port 626. Thedownstream USB port 626 sends IN and get the response from the USB device. Meanwhile, theupstream USB port 625 first sends NAK for IN or OUT/DATA until DATA or handshake are available from the USB device. - At the USB device side, if the USB device sends NAK for IN or OUT/DATA and NAK arrives at the USB
upstream port 625, the USBupstream port 625 unblocks the next coming IN or OUT/DATA and delivers to the USBdownstream port 626 to send IN or OUT/DATA to the USB device again with NAK handshake to the USB host. If the USB device sends DATA for IN or ACK for OUT/DATA and DATA or ACK arrives at the USBupstream port 625, the USBdownstream port 626 responds with ACK for IN transaction and delivers this DATA for IN or ACK for OUT to the USBupstream port 625. The USBupstream port 625 sends DATA for next IN available or ACK for next OUT/DATA available. - The USB
upstream port 625 always responds with ACK for SETUP transaction because it is required to receive SETUP and DATA and responds with ACK according to USB Specification. - The USB
downstream port 626 buffers OUT or SETUP until next coming DATA is available in the USBdownstream port 626 to guarantee the inter-packet delay between OUT/SETUP and DATA. - USB supports a number of different types of data transfers: isochronous, interrupt, bulk, and control transfers. Isochronous transfers occur at some guaranteed data rate but with possible data loss, for example for real time audio or video. Interrupt transfers are used for devices that need guaranteed quick responses (bounded latency), such as pointing devices and keyboards. Bulk transfers are large sporadic transfers that use all remaining available bandwidth, but have no guarantees on bandwidth or latency, such as file transfers. Control transfers are typically used for short, simple commands to the device, and a status response, used, for example, by the bus
control pipe number 0. - Instead of using flow control mechanism by sending NAK for IN or OUT/DATA, isochronous transfers use zero data and pipelines IN transaction scheme. For the first multiple isochronous INs, the USB upstream port responds with zero data, which is legitimate in the USB specification. This first IN is delivered to a USB downstream port and gets the DATA from an isochronous USB device. This first DATA is used to reply to the next isochronous IN when it arrives at USB upstream module. In this way, the USB host receives the delayed and pipelined isochronous DATA from the USB device.
- If the USB host stops to send isochronous IN, the last remaining DATA packets are dropped.
- An isochronous OUT transaction is delivered to the USB downstream port without NAK. The inter-packet delay between OUT and DATA should be maintained by buffering OUT until DATA is available in the USB downstream port.
- To respond properly to the isochronous IN without NAK response, the USB upstream port should know which USB address and USB endpoint are used for isochronous transfer. To obtain this information, DiiVA USB should have the capability to decode the descriptor from the USB device.
- Decoding descriptor can be done by analyzing the hybrid link USB packet, or the USB downstream port may have USB Host capability to enumerate and read out the descriptor from the USB device before connecting a USB upstream port to a USB downstream port. The descriptor decoding method is implementation-dependent and other implementations are possible.
- According to the USB specification, high bandwidth isochronous IN endpoints must support data PID sequencing depending on the DATA size. Because DATA size from isochronous USB devices vary, the number of INs per micro frame is different in every frame. Therefore, the mechanism of simply delivering isochronous IN from the USB upstream port to the USB downstream port cannot meet USB specification.
- DiiVA USB supports high bandwidth isochronous IN endpoints by the following method: only the first isochronous IN per micro frame is delivered. When the USB downstream port receives the DATA for isochronous IN, it itself should decide how many INs need to be sent based on the DATA PID. If first Data PID is DATA0, the USB downstream port behaves like above pipelined isochronous transfer scheme. If the first Data PID is DATA2, the USB downstream port generates two more same INs in the same micro frame. If the first Data PID is DATA1, the USB downstream port generates one more same IN. The USB upstream port should have enough buffer to accommodate the maximum DATA size per frame in high bandwidth isochronous endpoint.
- In some embodiments, a method of delivering USB data through a hybrid link with an isochronous IN token may comprise the following acts:
- the DATA packet using zero data and pipelining IN Data, wherein the number of states for IN DATA depends on latency of connection;
- for first, or first multiple, isochronous IN packets, an upstream port responding with one or more zero data packets;
- delivering said first, or first multiple, IN packets to a downstream port and receiving the DATA0 or DATA1 or DATA2 packet from an isochronous USB device;
- pipelining these DATA packets to reply with isochronous IN packets;
- if the USB host stops sending isochronous IN packets, dropping the last and remaining DATA; and
- the upstream USB port finding out which endpoint and address are used for isochronous endpoint, by monitoring and decoding USB descriptor from DATA packet stream.
- In some embodiments, a method of delivering USB data through a hybrid link with an isochronous OUT token may comprise:
- sending an isochronous OUT transaction out to the downstream port, wherein the upstream port does not send according to USB protocol;
- the downstream USB port buffering OUT packet until DATA0 or DATA1 or DATA2 or MDATA packet is available;
- when DATA0 or DATA1 or DATA2 or MDATA packet is available, sending OUT packet and DATA0 or DATA1 or DATA2 or MDATA packet to USB device; and
- the upstream USB port finding out which endpoint and address are used for isochronous endpoint by monitoring and decoding USB descriptor from DATA packet stream.
- In the present disclosure, non-isochronous transfers of USB data may also be performed using DiiVA specific protocols. In some embodiments, USB data may be delivered with a non-isochronous IN token, by performing the following acts:
- an upstream USB port receiving an IN packet and delivering same to downstream USB port;
- a downstream USB port sending the IN packet and receiving a Data packet or a handshake packet from a USB device;
- an upstream USB port sending NAK packet and blocking the next incoming IN packet with a NAK packet until the response from USB device is available;
- if a USB device sends NAK packet for IN packet and NAK packet arrives at upstream USB port from downstream USB port, upstream USB port unblocking the next incoming IN packet and delivering to downstream port to send IN packet to USB device again;
- if USB device sends a DATA0 or aDATA1 packet and the DATA0 or the DATA1 packet arrives in upstream USB port, the downstream port responding with an ACK packet and delivers the DATA0 or the DATA1 packet to the upstream port; and
- the upstream port sending the DATA0 or DATA1 packet for the next available IN packet.
- In some embodiments, USB data may be delivered with a non-isochronous OUT token, by performing the following acts:
- an upstream USB port receiving an OUT packet and either a DATA0 or a DATA1 packet and delivering to a downstream USB port;
- the downstream USB port buffering the OUT packet until the DATA0 or the DATA1 packet is available, and when the DATA0 or the DATA1 packet is available, sending the OUT packet and the DATA0 or the DATA1 packet to a USB device;
- the upstream USB port sending a NAK packet for the OUT transaction and not delivering the next incoming OUT packet and DATA0 or DATA1 packet until the response from downstream USB port is available;
- if the USB device sends a NAK packet for the OUT transaction and downstream USB port sends a NAK packet to the upstream USB port, the upstream USB port delivering the next incoming OUT packet and the DATA0 or DATA1 packet to the downstream port again; and
- if the USB device sends an ACK packet, the upstream port sending ACK for the next OUT transaction.
- In the present disclosure, transfer of USB data may be performed using PING packets.
- In some embodiments, PING protocol is implemented when the USB host gets NAK for OUT transaction. In these embodiments, the USB upstream port responds with NAK and does not deliver the PING packet to the USB downstream port. The USB upstream port blocks PING and keeps sending NAK until the response for OUT transaction from the USB device is available.
- If the USB device responds with ACK for OUT transaction, the USB upstream port responds with ACK for the next PING and also responds with ACK for next OUT transaction. This last OUT transaction is not delivered to the USB downstream port because the USB device already accepted the first OUT transaction.
- If the USB device responds with NAK for the OUT transaction, the USB upstream port delivers the next PING to the USB downstream port.
- If the USB device responds with ACK for PING and PING arrives at the USB upstream module, the USB upstream module responds with ACK for next PING and responds with ACK for next OUT transaction. This last OUT transaction is delivered to the USB device and is expected to be responded with ACK.
- If the USB device responds with NAK for PING and PING arrives at the USB upstream port, the USB upstream port responds with NAK for next PING and PING is delivered to the USB device again. This step is repeated until the USB device responds with ACK for PING. And the scenario follows the above step when the USB device responds with ACK.
- In sum, a method of delivering data through a hybrid link using a USB PING packet may comprise:
- an upstream USB port responds with NAK packet to OUT transaction;
- an upstream USB port responding with NAK packet, and delivering PING packet to a downstream USB port;
- the upstream USB port not delivering PING packet, and continuing to send NAK packet until the response from USB device is available;
- if a USB device responds with ACK packet for OUT transaction, the upstream USB port responding with ACK packet for the next incoming PING packet and responding with ACK packet for the next OUT transaction; wherein the last OUT transaction is not delivered to the downstream USB port;
- if the USB device responds with NAK packet for OUT transaction and NAK packet is delivered to upstream USB port, the upstream USB port delivering next PING packet to the downstream USB port;
- if the USB device responds with NAK packet with PING packet and NAK packet is delivered to the upstream USB port, the upstream USB port delivering the next PING packet to the downstream USB port;
- if the USB device responds with ACK packet with PING packet and ACK packet is delivered to upstream USB port, the upstream USB port responding with ACK packet for next PING packet;
- the next OUT transaction responding with ACK packet; and
- delivering these OUT packets and DATA0 or DATA1 packets to downstream USB port to send to USB device.
- In other embodiments, PING is used without a preceding OUT transaction. In these embodiments, the USB upstream port responds with NAK and delivers PING to the USB downstream port. The USB upstream port does not deliver PING and keeps sending NAK until the response from the USB device is available.
- If the USB device responds with ACK for PING, the USB upstream port responds with ACK for next PING and also responds with ACK for next OUT transaction. In this case, this last OUT transaction is delivered to the USB downstream port unlike the first scenario because no OUT transaction is delivered to the USB device yet.
- If the USB device responds with NAK for PING and PING arrives at the USB upstream port, the USB upstream port responds with NAK for next PING and delivers PING to the USB downstream port. This step is repeated until the USB downstream port gets ACK from the USB device. The acts when USB device responds with ACK, as described above, are then followed.
- When the USB device responds with NYET for OUT Transaction, the DiiVA USB module considers NYET as ACK and the USB upstream port always sends ACK instead of NYET.
- In sum, a method of delivering data through a hybrid link using a USB PING packet may comprise:
- an upstream USB port responding with NAK packet and delivering PING packet to a downstream USB port;
- the upstream USB port not delivering PING packet and continuing to send NAK packet until response from USB device is available;
- if USB device responds with ACK packet for PING packet and ACK packet is delivered to upstream USB port, the upstream USB port responding with ACK packet for the next PING packet and responding with ACK for the next OUT transaction; and
- delivering the OUT packet and DATA0 or DATA1 packets to downstream port;
- wherein there is no preceding OUT transaction before the upstream USB port receives PING packet.
- In some embodiments, USB address management in a DiiVA network may be performed as follows. A USB upstream port can be attached to any hub downstream port, and packets with various USB addresses can be broadcasted to the USB upstream port. The USB upstream port should be able to recognize which USB address is assigned to the USB upstream port and it should not respond to generic USB packets for any other USB Device.
- After USB Reset is detected in the USB upstream port, the USB upstream port accepts only generic USB packet with
USB Address 0. By monitoring and decoding SET_ADDRESS standard USB device request, the USB upstream port recognizes which USB address is assigned to the USB device in the USB downstream port. - After detecting SET_ADDRESS standard USB Device request, the USB upstream port only responds with generic USB packets with the newly assigned USB address. If USB Reset is detected in the USB upstream port, it resets the assigned USB address to 0 and waits for SET_ADDRESS standard USB device request again. Decoding SET_ADDRESS Device request is implementation specific.
- In sum, a method of USB address management in a DiiVA network may comprise:
- after USB Reset is detected in the upstream USB port, the upstream USB port accepting only packets that have
USB Address 0. - the upstream port recognizing which USB address is assigned to the USB device in the downstream port by monitoring and decoding SET_ADDRESS standard USB device request;
- after detecting SET_ADDRESS standard USB device request, the upstream port only responding with packets with new USB address which is assigned with SET_ADDRESS standard USB device request; and
- USB Reset resetting the assigned USB address to 0 and waiting for SET_ADDRESS standard USB device request again.
- In some embodiments, Keep-Alive forwarding in a DiiVA network may be performed as follows. When the enumeration state goes to LS_ENUM_DONE, the USB upstream port starts to monitor line state. When first toggling of line state is detected, it is considered as first Keep-Alive signaling. The USB upstream port sets the internal timer for T_KEEP_ALIVE and when it is expired, it starts to monitor line state toggling again to detect Keep-Alive. In some embodiments, T_KEEP_ALIVE is set to 0.98 ms. Keep-Alive signaling is delivered to USB Downstream Module through UU_KEEP_ALIVE.
- In sum, a method of performing USB low speed Keep-Alive signaling in a DiiVA network may comprise:
- after low-speed USB enumeration is done, the upstream USB port starting to monitor line state;
- when first change of line state is detected, considered that to be the first Keep-Alive signaling;
- the upstream USB port setting the internal timer for T_KEEP_ALIVE and when it is expired, the upstream USB port monitoring whether line state is toggling again, to detect Keep-Alive and deliver Keep Alive event packet to downstream USB port.
- In the present disclosure, methods and systems have been described relating to the transfer of USB and multi-media data over DiiVA, and network management in DiiVA. The components, steps, features, objects, benefits and advantages that have been discussed are merely illustrative. None of them, nor the discussions relating to them, are intended to limit the scope of protection in any way. While certain embodiments have been described of systems and methods relating to USB data transfer over DiiVA, it is to be understood that the concepts implicit in these embodiments may be used in other embodiments as well. Numerous other embodiments are also contemplated, including embodiments that have fewer, additional, and/or different components, steps, features, objects, benefits and advantages. The components and steps may also be arranged and ordered differently. Nothing that has been stated or illustrated is intended to cause a dedication of any component, step, feature, object, benefit, advantage, or equivalent to the public.
- In the present disclosure, reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure, known or later come to be known to those of ordinary skill in the art, are expressly incorporated herein by reference.
Claims (26)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/521,739 US20130191570A1 (en) | 2010-01-12 | 2011-01-12 | MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US29447610P | 2010-01-12 | 2010-01-12 | |
PCT/US2011/021031 WO2011088154A2 (en) | 2010-01-12 | 2011-01-12 | Multi-media usb data transfer over digital interaction interface for video and audio (diiva) |
US13/521,739 US20130191570A1 (en) | 2010-01-12 | 2011-01-12 | MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130191570A1 true US20130191570A1 (en) | 2013-07-25 |
Family
ID=44304952
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/521,739 Abandoned US20130191570A1 (en) | 2010-01-12 | 2011-01-12 | MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) |
US13/521,762 Active 2031-09-03 US9398329B2 (en) | 2010-01-12 | 2011-01-12 | Video management and control in home multimedia network |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/521,762 Active 2031-09-03 US9398329B2 (en) | 2010-01-12 | 2011-01-12 | Video management and control in home multimedia network |
Country Status (6)
Country | Link |
---|---|
US (2) | US20130191570A1 (en) |
EP (2) | EP2556631A4 (en) |
JP (2) | JP5663037B2 (en) |
KR (2) | KR101884255B1 (en) |
CN (2) | CN102835091B (en) |
WO (2) | WO2011088153A2 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013159205A1 (en) * | 2012-04-26 | 2013-10-31 | Icron Technologies Corporation | Usb 3.0 link layer timer adjustment to extend distance |
US20150229570A1 (en) * | 2014-02-10 | 2015-08-13 | Silex Technology, Inc. | Device server and control method thereof |
CN105472294A (en) * | 2015-11-11 | 2016-04-06 | 天津瑞发科半导体技术有限公司 | Mixed transmission system and method of video data and USB data |
US20170024344A1 (en) * | 2015-07-22 | 2017-01-26 | Microchip Technology Incorporated | Method and System for USB 2.0 Bandwidth Reservation |
US20180004685A1 (en) * | 2016-06-29 | 2018-01-04 | Intel Corporation | Efficient low cost on-die configurable bridge controller |
US10448007B2 (en) * | 2015-07-28 | 2019-10-15 | Spirent Communications, Inc. | Discovery and identification of layer 2 coax problems in MoCA networks |
US10742523B2 (en) | 2016-05-11 | 2020-08-11 | Spirent Communications, Inc. | Service based testing |
WO2021081269A1 (en) * | 2019-10-23 | 2021-04-29 | Texas Instruments Incorporated | Common bus data flow for serially chained devices |
US11171804B2 (en) | 2019-05-23 | 2021-11-09 | Texas Instruments Incorporated | Common bus data flow for serially chained devices |
US11258679B2 (en) | 2015-07-28 | 2022-02-22 | Spirent Communications, Inc. | Systems and methods for automated testing of MoCA networks |
WO2022087520A1 (en) * | 2020-10-23 | 2022-04-28 | Insight Automation | System and method for relative addressing based upon physical topology |
US11329844B2 (en) | 2019-05-23 | 2022-05-10 | Texas Instruments Incorporated | Selected mode signal forwarding between serially chained devices |
US11483517B2 (en) | 2019-05-23 | 2022-10-25 | Texas Instruments Incorporated | Selected forwarding between serially chained devices |
Families Citing this family (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9012766B2 (en) | 2009-11-12 | 2015-04-21 | Silevo, Inc. | Aluminum grid as backside conductor on epitaxial silicon thin film solar cells |
US9214576B2 (en) | 2010-06-09 | 2015-12-15 | Solarcity Corporation | Transparent conducting oxide for photovoltaic devices |
US9054256B2 (en) | 2011-06-02 | 2015-06-09 | Solarcity Corporation | Tunneling-junction solar cell with copper grid for concentrated photovoltaic application |
US9237124B2 (en) * | 2011-07-14 | 2016-01-12 | Marvell Israel (M.I.S.L) Ltd. | Scaling of virtual machine addresses in datacenters |
CN102572583B (en) * | 2011-12-26 | 2014-11-05 | Tcl集团股份有限公司 | Multimedia play system and play method |
US8819525B1 (en) * | 2012-06-14 | 2014-08-26 | Google Inc. | Error concealment guided robustness |
US8683091B2 (en) | 2012-06-30 | 2014-03-25 | Intel Corporation | Device disconnect detection |
US9865754B2 (en) | 2012-10-10 | 2018-01-09 | Tesla, Inc. | Hole collectors for silicon photovoltaic cells |
US9219174B2 (en) | 2013-01-11 | 2015-12-22 | Solarcity Corporation | Module fabrication of solar cells with low resistivity electrodes |
US9412884B2 (en) | 2013-01-11 | 2016-08-09 | Solarcity Corporation | Module fabrication of solar cells with low resistivity electrodes |
CN103118257B (en) * | 2013-02-05 | 2016-05-18 | 广东威创视讯科技股份有限公司 | The transfer of data integrated interface of HD video form |
US10116979B2 (en) | 2013-05-06 | 2018-10-30 | Andrew Setos | Method and system for the delivery and storage of high definition audio-visual content |
US10291676B2 (en) * | 2013-05-06 | 2019-05-14 | Setos Family Trust | Method and system for the delivery of high definition audio-visual content |
US20140337505A1 (en) * | 2013-05-08 | 2014-11-13 | Htc Corporation | Method for data transmission and corresponding electronic device |
US9575917B1 (en) * | 2013-08-30 | 2017-02-21 | Analogix Semiconductor, Inc. | Protocol for digital audio-video interface |
CN103841467A (en) * | 2014-03-13 | 2014-06-04 | 广州物联家信息科技股份有限公司 | Method and system for achieving security protection management based on Home-IOT cloud gateway |
CN103984590A (en) * | 2014-06-03 | 2014-08-13 | 浪潮电子信息产业股份有限公司 | Virtual machine USB-equipment sharing method |
US10309012B2 (en) | 2014-07-03 | 2019-06-04 | Tesla, Inc. | Wafer carrier for reducing contamination from carbon particles and outgassing |
US9899546B2 (en) | 2014-12-05 | 2018-02-20 | Tesla, Inc. | Photovoltaic cells with electrodes adapted to house conductive paste |
US9947822B2 (en) | 2015-02-02 | 2018-04-17 | Tesla, Inc. | Bifacial photovoltaic module using heterojunction solar cells |
US9761744B2 (en) | 2015-10-22 | 2017-09-12 | Tesla, Inc. | System and method for manufacturing photovoltaic structures with a metal seed layer |
US9842956B2 (en) | 2015-12-21 | 2017-12-12 | Tesla, Inc. | System and method for mass-production of high-efficiency photovoltaic structures |
WO2017151925A1 (en) * | 2016-03-02 | 2017-09-08 | Lattice Semiconductor Corporation | Link training in multimedia interfaces |
US10115838B2 (en) | 2016-04-19 | 2018-10-30 | Tesla, Inc. | Photovoltaic structures with interlocking busbars |
US10672919B2 (en) | 2017-09-19 | 2020-06-02 | Tesla, Inc. | Moisture-resistant solar cells for solar roof tiles |
US10855363B2 (en) * | 2018-05-07 | 2020-12-01 | Wilson Electronics, Llc | Multiple-input multiple-output (MIMO) repeater system |
CN108874721A (en) * | 2018-07-02 | 2018-11-23 | 威创集团股份有限公司 | Usb signal processing method, collection terminal and control terminal |
US10873402B2 (en) | 2019-04-30 | 2020-12-22 | Corning Research & Development Corporation | Methods and active optical cable assemblies for providing a reset signal at a peripheral end |
KR20220142202A (en) * | 2021-04-14 | 2022-10-21 | 삼성전자주식회사 | Electronic device providing method of multi-connection contol by using usb type-c connecting terminal and method of operation therof |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020144165A1 (en) * | 2001-03-29 | 2002-10-03 | Cypress Semiconductor Corp. | Method for reducing power consumption in a universal serial bus device |
US20040203296A1 (en) * | 2002-11-15 | 2004-10-14 | Globespan Virata Inc. | Method and system for attaching a USB network adapter supporting both RNDIS and non-RNDIS capable operating systems |
US20050144345A1 (en) * | 2002-12-27 | 2005-06-30 | Fujitsu Limited | Universal serial bus device and method for controlling universal serial bus device |
US20070011375A1 (en) * | 2005-07-08 | 2007-01-11 | Kumar Sasi K | Method and system for hardware based implementation of USB 1.1 over a high speed link |
US20080028120A1 (en) * | 2006-07-28 | 2008-01-31 | Mcleod John Alexander | Method and Apparatus for Distributing USB Hub Functions across a Network |
US7502878B1 (en) * | 2003-06-27 | 2009-03-10 | Cypress Semiconductor Corporation | Method and apparatus for switching USB devices between multiple USB hosts |
US20090147864A1 (en) * | 2007-02-07 | 2009-06-11 | Valens Semiconductor Ltd. | HDMI communication over twisted pairs |
Family Cites Families (82)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4575714A (en) | 1984-03-12 | 1986-03-11 | Tegal Corporation | Module presence sensor |
JPH0650860B2 (en) | 1984-06-29 | 1994-06-29 | ヒューレット・パッカード・カンパニー | Network initial setting method |
US5148144A (en) | 1991-03-28 | 1992-09-15 | Echelon Systems Corporation | Data communication network providing power and message information |
GB2260003B (en) | 1991-09-28 | 1995-06-14 | Motorola Israel Ltd | Option board identification |
US5541957A (en) | 1994-06-15 | 1996-07-30 | National Semiconductor Corporation | Apparatus for transmitting and/or receiving data at different data transfer rates especially in applications such as dual-rate ethernet local-area networks |
AU5317696A (en) | 1995-03-24 | 1996-10-16 | Ppt Vision, Inc. | High speed digital video serial link |
US5983288A (en) | 1996-08-20 | 1999-11-09 | Lucent Technologies Inc. | Dynamically configurable personal computer card utilizing variable interrogation signal to detect connected extension |
US5783926A (en) | 1996-11-05 | 1998-07-21 | Ericsson, Inc. | Apparatus for identifying accessories connected to radiotelephone equipment |
JP3045985B2 (en) | 1997-08-07 | 2000-05-29 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Connection establishment method, communication method, state change transmission method, state change execution method, wireless device, wireless device, and computer |
JP3304292B2 (en) | 1997-09-12 | 2002-07-22 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Automatic detection device for detecting attachment or identification of an external device, information processing device, and external device |
US7346785B2 (en) | 1999-01-12 | 2008-03-18 | Microsemi Corp. - Analog Mixed Signal Group Ltd. | Structure cabling system |
US6144399A (en) | 1999-03-25 | 2000-11-07 | Mediaone Group, Inc. | Passive system used to merge telephone and broadband signals onto one coaxial cable |
DE19914004B4 (en) | 1999-03-29 | 2005-04-14 | Robert Bosch Gmbh | Identifiable electrical component with methods of identification and evaluation |
US6836546B1 (en) | 1999-11-03 | 2004-12-28 | Advanced Micro Devices, Inc. | Apparatus and method of coupling home network signals between an analog phone line and a digital bus |
US7047313B1 (en) * | 2000-01-05 | 2006-05-16 | Thomas Licensing | Method for redirecting packetized data associated with a destination address in a communication protocol layer to a different destination address in a different protocol layer |
US7024539B2 (en) | 2000-07-17 | 2006-04-04 | Silicon Laboratories Inc. | Resistor identification configuration circuitry and associated method |
US6789136B1 (en) | 2000-12-29 | 2004-09-07 | Intel Corporation | Efficient method to obtain device addresses from devices on a bus |
CA2345596C (en) | 2001-04-27 | 2007-12-04 | Icron Systems Inc. | Method and apparatus for extending the range of the universal serial bus protocol |
GB2415314B (en) * | 2001-08-08 | 2006-05-03 | Adder Tech Ltd | Video switch |
US7257163B2 (en) * | 2001-09-12 | 2007-08-14 | Silicon Image, Inc. | Method and system for reducing inter-symbol interference effects in transmission over a serial link with mapping of each word in a cluster of received words to a single transmitted word |
US7295578B1 (en) | 2001-09-12 | 2007-11-13 | Lyle James D | Method and apparatus for synchronizing auxiliary data and video data transmitted over a TMDS-like link |
US7088398B1 (en) * | 2001-12-24 | 2006-08-08 | Silicon Image, Inc. | Method and apparatus for regenerating a clock for auxiliary data transmitted over a serial link with video data |
EP1490772B1 (en) | 2002-05-02 | 2005-06-01 | ELMOS Semiconductor AG | Method for addressing the users of a bus system by means of identification flows |
JP2004021613A (en) | 2002-06-17 | 2004-01-22 | Seiko Epson Corp | Data transfer controller, electronic apparatus, and data transfer control method |
US8064508B1 (en) * | 2002-09-19 | 2011-11-22 | Silicon Image, Inc. | Equalizer with controllably weighted parallel high pass and low pass filters and receiver including such an equalizer |
IL154234A (en) | 2003-01-30 | 2010-12-30 | Mosaid Technologies Inc | Method and system for providing dc power on local telephone lines |
US7088741B2 (en) | 2003-05-01 | 2006-08-08 | Genesis Microchip Inc. | Using an auxilary channel for video monitor training |
CA2466371A1 (en) | 2003-05-05 | 2004-11-05 | Engineering Services Inc. | Mobile robot hydrid communication link |
US20050018596A1 (en) | 2003-06-19 | 2005-01-27 | Robert Washburn | System for crosstalk noise reduction on twisted pair, ethernet, polyphase and shielded wire systems |
KR100497988B1 (en) | 2003-07-25 | 2005-07-01 | 엘지전자 주식회사 | Apparatus and method for suppling power by the automation through Ethernet |
JP2005129010A (en) * | 2003-09-29 | 2005-05-19 | Sharp Corp | Device-side controller, host-side controller, communication controller, usb system, method and program for packet-based communication, and recording medium |
TWI296083B (en) | 2003-09-29 | 2008-04-21 | Sharp Kk | Communication controller, host-side controller, communication system, usb system, communication equipment, communication method, packet-based communication method, packet-based communication program, and storage medium |
US7903809B2 (en) | 2004-11-05 | 2011-03-08 | Cisco Technology, Inc. | Power management for serial-powered device connections |
US8074084B2 (en) | 2004-11-03 | 2011-12-06 | Cisco Technology, Inc. | Powered device classification in a wired data telecommunications network |
EP1751938A1 (en) | 2004-06-04 | 2007-02-14 | Qualcomm Incorporated | High data rate interface apparatus and method |
KR101049129B1 (en) * | 2004-07-30 | 2011-07-15 | 엘지전자 주식회사 | Cable broadcast receiver and its status information processing method |
KR101092438B1 (en) * | 2004-08-05 | 2011-12-13 | 엘지전자 주식회사 | Cable broadcasting receiver and diagnostic method thereof |
US7911473B2 (en) * | 2004-10-18 | 2011-03-22 | Genesis Microchip Inc. | Method for acquiring extended display identification data (EDID) in a powered down EDID compliant display controller |
US8509321B2 (en) | 2004-12-23 | 2013-08-13 | Rambus Inc. | Simultaneous bi-directional link |
US20060164098A1 (en) | 2005-01-25 | 2006-07-27 | Linear Technology Corporation | Utilization of power delivered to powered device during detection and classification mode |
US7856561B2 (en) | 2005-01-25 | 2010-12-21 | Linear Technology Corporation | Detecting legacy powered device in power over ethernet system |
US20060209892A1 (en) * | 2005-03-15 | 2006-09-21 | Radiospire Networks, Inc. | System, method and apparatus for wirelessly providing a display data channel between a generalized content source and a generalized content sink |
EP1931079A1 (en) | 2005-09-26 | 2008-06-11 | Matsushita Electric Industrial Co., Ltd. | Single-line two-way communication device and system |
US20090260043A1 (en) | 2005-09-30 | 2009-10-15 | Akihiro Tatsuta | Wireless transmission system for wirelessly connecting signal source apparatus and signal sink apparatus |
CN101346936B (en) * | 2005-12-26 | 2011-02-09 | 松下电器产业株式会社 | Address managing method and communication device |
EP1980050B1 (en) | 2006-01-17 | 2014-12-17 | Broadcom Corporation | Power over ethernet controller integrated circuit architecture |
CN101379777B (en) * | 2006-02-10 | 2011-08-17 | 松下电器产业株式会社 | Radio communication system |
US7844762B2 (en) | 2006-02-24 | 2010-11-30 | Silicon Image, Inc. | Parallel interface bus to communicate video data encoded for serial data links |
US20070257923A1 (en) | 2006-03-15 | 2007-11-08 | Colin Whitby-Strevens | Methods and apparatus for harmonization of interface profiles |
US7921310B2 (en) | 2006-06-28 | 2011-04-05 | Broadcom Corporation | Unified powered device (PD) controller and LAN on motherboard (LOM) in a personal computing device (PCD) |
TW200805912A (en) | 2006-07-05 | 2008-01-16 | Apac Opto Electronics Inc | Transmission apparatus with fiber high-definition digital video data interface |
US20080129882A1 (en) * | 2006-11-30 | 2008-06-05 | Eiichi Moriyama | Data transfer device and transfer control method |
US8630312B2 (en) * | 2006-12-04 | 2014-01-14 | Samsung Electronics Company, Ltd. | System and method for wireless communication of uncompressed video having connection control protocol |
US9065657B2 (en) | 2006-12-21 | 2015-06-23 | Silicon Laboratories Inc. | Powered device including a detection signature circuit |
US7835382B2 (en) * | 2007-02-07 | 2010-11-16 | Valens Semiconductor Ltd. | High definition and low power partial functionality communication link |
US8355327B2 (en) * | 2007-02-07 | 2013-01-15 | Valens Semiconductor Ltd. | Methods and devices for daisy chain CE device power save modes |
US8159927B2 (en) | 2007-02-16 | 2012-04-17 | Gennum Corporation | Transmit, receive, and cross-talk cancellation filters for back channelling |
US7916780B2 (en) | 2007-04-09 | 2011-03-29 | Synerchip Co. Ltd | Adaptive equalizer for use with clock and data recovery circuit of serial communication link |
US7940809B2 (en) | 2007-04-09 | 2011-05-10 | Synerchip Co. Ltd. | Digital video interface with bi-directional half-duplex clock channel used as auxiliary data channel |
KR101401965B1 (en) * | 2007-05-25 | 2014-06-02 | 삼성전자주식회사 | Method for measuring a state of a plurality of channels and apparatus, Method for selecting idle channel and apparatus therefor |
KR20090002809A (en) | 2007-07-04 | 2009-01-09 | 삼성전자주식회사 | The method for transmitting and receiving data generated by application according to hdmi cec |
JP2009055306A (en) | 2007-08-27 | 2009-03-12 | Sony Corp | Data receiver |
US8990437B2 (en) * | 2007-11-13 | 2015-03-24 | Nvidia Corporation | HDMI network control of a media center computing device |
JP4618291B2 (en) * | 2007-11-30 | 2011-01-26 | ソニー株式会社 | Transmitting apparatus, receiving apparatus, and operation information transmitting method in receiving apparatus |
US7921231B2 (en) * | 2008-01-04 | 2011-04-05 | Silicon Image, Inc. | Discovery of electronic devices utilizing a control bus |
US7856520B2 (en) * | 2008-01-04 | 2010-12-21 | Silicon Image, Inc. | Control bus for connection of electronic devices |
JP5593596B2 (en) * | 2008-02-04 | 2014-09-24 | ソニー株式会社 | Video signal transmitting apparatus and video signal transmitting method |
JP5572929B2 (en) * | 2008-03-05 | 2014-08-20 | ソニー株式会社 | Transmitter |
US20090248918A1 (en) | 2008-03-27 | 2009-10-01 | Wael William Diab | Method and system for a usb ethertype to tunnel usb over ethernet |
JP5079872B2 (en) * | 2008-03-27 | 2012-11-21 | パナソニック株式会社 | Wireless communication device |
US9030976B2 (en) * | 2008-03-27 | 2015-05-12 | Silicon Image, Inc. | Bi-directional digital interface for video and audio (DIVA) |
US8253860B2 (en) * | 2008-04-07 | 2012-08-28 | Mediatek Inc. | System, method and devices for HDMI transmission using a commonly supported media format |
US8996732B2 (en) * | 2008-05-27 | 2015-03-31 | Valens Semiconductor Ltd. | Methods and devices for CEC block termination |
JP4645717B2 (en) * | 2008-09-26 | 2011-03-09 | ソニー株式会社 | Interface circuit and video apparatus |
US8275914B2 (en) | 2008-10-16 | 2012-09-25 | Silicon Image, Inc. | Discovery of connections utilizing a control bus |
US20100142723A1 (en) * | 2008-12-08 | 2010-06-10 | Willard Kraig Bucklen | Multimedia Switching Over Wired Or Wireless Connections In A Distributed Environment |
JP2012512567A (en) | 2008-12-11 | 2012-05-31 | シナーチップ カンパニー リミテッド | Power supply to bi-directional digital interface for video and audio |
US8122159B2 (en) | 2009-01-16 | 2012-02-21 | Allegro Microsystems, Inc. | Determining addresses of electrical components arranged in a daisy chain |
US8806094B2 (en) * | 2009-09-25 | 2014-08-12 | Analogix Semiconductor, Inc. | Transfer of uncompressed multimedia contents or data communications |
US8799537B1 (en) * | 2009-09-25 | 2014-08-05 | Analogix Semiconductor, Inc. | Transfer of uncompressed multimedia contents and data communications |
US8644334B2 (en) * | 2009-09-30 | 2014-02-04 | Silicon Image, Inc. | Messaging to provide data link integrity |
US8659986B1 (en) | 2011-07-25 | 2014-02-25 | Aquantia Corporation | Crosstalk cancellation for a multiport ethernet system |
-
2011
- 2011-01-12 WO PCT/US2011/021030 patent/WO2011088153A2/en active Application Filing
- 2011-01-12 KR KR1020127021123A patent/KR101884255B1/en active IP Right Grant
- 2011-01-12 CN CN201180005935.3A patent/CN102835091B/en active Active
- 2011-01-12 CN CN201180005909.0A patent/CN102860030B/en active Active
- 2011-01-12 WO PCT/US2011/021031 patent/WO2011088154A2/en active Application Filing
- 2011-01-12 JP JP2012549056A patent/JP5663037B2/en active Active
- 2011-01-12 EP EP11733338.5A patent/EP2556631A4/en not_active Withdrawn
- 2011-01-12 JP JP2012549055A patent/JP5789269B2/en active Active
- 2011-01-12 KR KR1020127021114A patent/KR20120135231A/en not_active Application Discontinuation
- 2011-01-12 US US13/521,739 patent/US20130191570A1/en not_active Abandoned
- 2011-01-12 US US13/521,762 patent/US9398329B2/en active Active
- 2011-01-12 EP EP11733339.3A patent/EP2556648A4/en not_active Withdrawn
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020144165A1 (en) * | 2001-03-29 | 2002-10-03 | Cypress Semiconductor Corp. | Method for reducing power consumption in a universal serial bus device |
US20040203296A1 (en) * | 2002-11-15 | 2004-10-14 | Globespan Virata Inc. | Method and system for attaching a USB network adapter supporting both RNDIS and non-RNDIS capable operating systems |
US20050144345A1 (en) * | 2002-12-27 | 2005-06-30 | Fujitsu Limited | Universal serial bus device and method for controlling universal serial bus device |
US7502878B1 (en) * | 2003-06-27 | 2009-03-10 | Cypress Semiconductor Corporation | Method and apparatus for switching USB devices between multiple USB hosts |
US20070011375A1 (en) * | 2005-07-08 | 2007-01-11 | Kumar Sasi K | Method and system for hardware based implementation of USB 1.1 over a high speed link |
US20080028120A1 (en) * | 2006-07-28 | 2008-01-31 | Mcleod John Alexander | Method and Apparatus for Distributing USB Hub Functions across a Network |
US20090147864A1 (en) * | 2007-02-07 | 2009-06-11 | Valens Semiconductor Ltd. | HDMI communication over twisted pairs |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9129064B2 (en) | 2012-04-26 | 2015-09-08 | Icron Technologies Corporation | USB 3.0 link layer timer adjustment to extend distance |
WO2013159205A1 (en) * | 2012-04-26 | 2013-10-31 | Icron Technologies Corporation | Usb 3.0 link layer timer adjustment to extend distance |
US9736076B2 (en) * | 2014-02-10 | 2017-08-15 | Silex Technology, Inc. | Device server and control method thereof |
US20150229570A1 (en) * | 2014-02-10 | 2015-08-13 | Silex Technology, Inc. | Device server and control method thereof |
US20170024344A1 (en) * | 2015-07-22 | 2017-01-26 | Microchip Technology Incorporated | Method and System for USB 2.0 Bandwidth Reservation |
US10448007B2 (en) * | 2015-07-28 | 2019-10-15 | Spirent Communications, Inc. | Discovery and identification of layer 2 coax problems in MoCA networks |
US11258679B2 (en) | 2015-07-28 | 2022-02-22 | Spirent Communications, Inc. | Systems and methods for automated testing of MoCA networks |
US11863420B2 (en) | 2015-07-28 | 2024-01-02 | Spirent Communications, Inc. | Diagnosing faults in a multimedia over coax alliance (MoCA) local area network (LAN) including a WiFi segment |
CN105472294A (en) * | 2015-11-11 | 2016-04-06 | 天津瑞发科半导体技术有限公司 | Mixed transmission system and method of video data and USB data |
US10742523B2 (en) | 2016-05-11 | 2020-08-11 | Spirent Communications, Inc. | Service based testing |
US20180004685A1 (en) * | 2016-06-29 | 2018-01-04 | Intel Corporation | Efficient low cost on-die configurable bridge controller |
US10127162B2 (en) * | 2016-06-29 | 2018-11-13 | Intel Corporation | Efficient low cost on-die configurable bridge controller |
US11171804B2 (en) | 2019-05-23 | 2021-11-09 | Texas Instruments Incorporated | Common bus data flow for serially chained devices |
US11329844B2 (en) | 2019-05-23 | 2022-05-10 | Texas Instruments Incorporated | Selected mode signal forwarding between serially chained devices |
US11483517B2 (en) | 2019-05-23 | 2022-10-25 | Texas Instruments Incorporated | Selected forwarding between serially chained devices |
US11736313B2 (en) | 2019-05-23 | 2023-08-22 | Texas Instruments Incorporated | Common bus data flow for serially chained devices |
WO2021081269A1 (en) * | 2019-10-23 | 2021-04-29 | Texas Instruments Incorporated | Common bus data flow for serially chained devices |
WO2022087520A1 (en) * | 2020-10-23 | 2022-04-28 | Insight Automation | System and method for relative addressing based upon physical topology |
US11799758B2 (en) | 2020-10-23 | 2023-10-24 | Insight Automation, Inc. | System and method for relative addressing based on physical topology |
Also Published As
Publication number | Publication date |
---|---|
JP5663037B2 (en) | 2015-02-04 |
CN102835091A (en) | 2012-12-19 |
KR20120123086A (en) | 2012-11-07 |
EP2556631A2 (en) | 2013-02-13 |
WO2011088153A3 (en) | 2011-11-24 |
WO2011088153A2 (en) | 2011-07-21 |
KR20120135231A (en) | 2012-12-12 |
CN102860030B (en) | 2017-02-08 |
EP2556631A4 (en) | 2013-12-18 |
JP5789269B2 (en) | 2015-10-07 |
KR101884255B1 (en) | 2018-08-01 |
WO2011088154A2 (en) | 2011-07-21 |
CN102860030A (en) | 2013-01-02 |
WO2011088154A3 (en) | 2011-12-01 |
JP2013517694A (en) | 2013-05-16 |
CN102835091B (en) | 2017-07-04 |
US20130191872A1 (en) | 2013-07-25 |
EP2556648A2 (en) | 2013-02-13 |
US9398329B2 (en) | 2016-07-19 |
EP2556648A4 (en) | 2013-12-11 |
JP2013517693A (en) | 2013-05-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20130191570A1 (en) | MULTI-MEDIA USB DATA TRANSFER OVER DIGITAL INTERACTION INTERFACE FOR VIDEO AND AUDIO (DiiVA) | |
US9479279B2 (en) | Multiple protocol tunneling using time division operations | |
US8301819B2 (en) | Method and system for docking a laptop with ethernet A/V bridging to guarantee services | |
US7349391B2 (en) | Tunneling between a bus and a network | |
KR101219910B1 (en) | Unified multi-transport medium connector architecture | |
AU2012250760B2 (en) | Methods and apparatus for transporting data through network tunnels | |
US7505455B1 (en) | Optimizations for tunneling between a bus and a network | |
US9129064B2 (en) | USB 3.0 link layer timer adjustment to extend distance | |
US8990470B1 (en) | Virtual hubs for communication interface | |
US9317465B2 (en) | System and method of sending PCI express data over ethernet connection | |
US8788734B2 (en) | Methods and devices for universal serial bus port event extension | |
JP2012518918A (en) | System, apparatus, and method for broadcasting a USB data stream | |
TW201717039A (en) | Method and system for USB 2.0 bandwidth reservation | |
US10459864B2 (en) | USB isochronous transfer over a non-USB network | |
US9240896B2 (en) | Method and system for USB connections over distinct network paths | |
US8645584B2 (en) | Method and system for partial USB enumeration and edge initiation | |
TW201532404A (en) | Method of logging in computers from remote end | |
US9049041B2 (en) | Method and system for distributed initiation of USB over network data plane connections | |
US9059865B2 (en) | USB host adaptor for initiating a USB connection over a non-USB network | |
KR200239091Y1 (en) | Ieee1394 ohci card | |
US8578061B2 (en) | Method and system for USB addressing by a network adaptor | |
US9059864B2 (en) | USB device adaptor for initiating a USB connection over a non-USB network | |
Mittal et al. | Super speed USB–Improvements and future scope |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SYNERCHIP CO. LTD., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LEE, DONGYUN;PAK, EDWARD;HAHN, JOHN;AND OTHERS;SIGNING DATES FROM 20130204 TO 20130205;REEL/FRAME:029815/0132 Owner name: SILICON IMAGE, INC., CALIFORNIA Free format text: NUNC PRO TUNC ASSIGNMENT;ASSIGNOR:SYNERCHIP CO., LTD.;REEL/FRAME:029815/0156 Effective date: 20121008 |
|
AS | Assignment |
Owner name: JEFFERIES FINANCE LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:LATTICE SEMICONDUCTOR CORPORATION;SIBEAM, INC.;SILICON IMAGE, INC.;AND OTHERS;REEL/FRAME:035223/0387 Effective date: 20150310 |
|
AS | Assignment |
Owner name: LATTICE SEMICONDUCTOR CORPORATION, OREGON Free format text: MERGER;ASSIGNOR:SILICON IMAGE, INC.;REEL/FRAME:036419/0792 Effective date: 20150513 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: SILICON IMAGE, INC., OREGON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC;REEL/FRAME:049827/0326 Effective date: 20190517 Owner name: DVDO, INC., OREGON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC;REEL/FRAME:049827/0326 Effective date: 20190517 Owner name: LATTICE SEMICONDUCTOR CORPORATION, OREGON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC;REEL/FRAME:049827/0326 Effective date: 20190517 Owner name: SIBEAM, INC., OREGON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JEFFERIES FINANCE LLC;REEL/FRAME:049827/0326 Effective date: 20190517 |
|
AS | Assignment |
Owner name: UNIVERSAL CONNECTIVITY TECHNOLOGIES INC., DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LATTICE SEMICONDUCTOR CORPORATION;REEL/FRAME:058979/0440 Effective date: 20211116 |