Network-USB (NUSB) communication system by which network applications communicate with USB devices over power-over-ethernet (PoE) connection

• US 9,760,517 B2
• Filed: 12/02/2014
• Issued: 09/12/2017
• Est. Priority Date: 05/16/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Liston, Rob, Balasubramanian, Koussalya, Mehta, Naoshad
• Primary Examiner(s): Peyton, Tammara
• Application Number:
  US14/558,119
• Publication Number:
  US 20150331821A1
• Time in Patent Office: 1,015 Days
• Field of Search: 710308-310
• CPC Class Codes: G06F 1/26 Power supply means, e.g. regulation thereof for memories G11C
• CPC Class Codes: G06F 1/266 Arrangements to supply power to external peripherals either directly from the computer or under computer control, e.g. supply of power through the communication port, computer controlled power-strips
• CPC Class Codes: G06F 13/387 for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
• CPC Class Codes: G06F 13/42 Bus transfer protocol, e.g. handshake; Synchronisation
• CPC Class Codes: G06F 13/4282 on a serial bus, e.g. I2C bus, SPI bus on daisy chain buses G06F13/4247
• CPC Class Codes: G06F 2213/0042 Universal serial bus [USB]
• CPC Class Codes: H04L 12/10 Current supply arrangements
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: Y02D 30/00 Reducing energy consumption in communication networks

Abstract

A network device includes Power-over-Ethernet PoE ports to communicate with a communication network and Universal Serial Bus (USB) devices. The network device establishes an Internet Protocol (IP) related connection with an application program, and receives downlink IP packets carrying USB transaction requests destined for the USB device from the application program over the IP connection. The network device converts the received downlink IP packets carrying the USB transaction requests to downlink bus-level USB transactions that are understandable to the USB device. The network device sends the downlink bus-level USB transactions to the USB adaptor device over a PoE connection for forwarding by the USB adaptor device to the USB device.

Claims

1. A method comprising:

at a network device to enable an application program to communicate with a Universal Serial Bus (USB) device through a USB adaptor device having a Power-over-Ethernet (PoE) connection to a PoE port of the network device, and a USB connection to the USB device;

establishing a Transmission Control Protocol/Internet Protocol (TCP/IP) connection with the application program;

receiving downlink TCP/IP packets carrying USB transaction requests destined for the USB device from the application program over the TCP/IP connection;

converting the received downlink TCP/IP packets carrying the USB transaction requests to downlink bus-level USB transactions that are understandable to the USB device; and

sending, using a Reliable Message Protocol (RMP), the downlink bus-level USB transactions to the USB adaptor device over the PoE connection for forwarding by the USB adaptor device to the USB device over the USB connection, the sending including encapsulating each downlink bus-level USB transaction in an RMP message and sending the RMP message as an Ethernet packet formatted in accordance with a Network-USB (NUSB) protocol format that includes an Ethernet layer populated with Ethernet parameters, an RMP layer populated with RMP parameters, and a bus-level USB transaction layer populated by bus-level USB transactions.

2. The method of claim 1, further comprising, at the network device:

receiving, using the RMP, uplink bus-level USB transactions from the USB adaptor device over the PoE connection that originated from the USB device;

converting the uplink bus-level USB transactions to corresponding uplink TCP/IP packets carrying the uplink bus-level USB transactions; and

sending the uplink TCP/IP packets carrying the bus-level USB transactions to the application program over the TCP/IP connection.

3. The method of claim 1, wherein the sending using the RMP includes performing a multi-message handshake between an RMP sender implemented in the network device and an RMP receiver implemented in the USB adaptor device over the PoE connection so as to cause:

opening of an RMP connection between the RMP sender and the RMP receiver;

sending one or more RMP messages from the RMP sender to the RMP receiver using the RMP connection, wherein each RMP message encapsulates one of the downlink bus-level USB transactions; and

closing the RMP connection after the RMP messages are sent.

4. The method of claim 3, wherein:

the multi-message handshake further causes receiving one or more RMP acknowledgement messages before the closing; and

the receiving using the RMP includes receiving the uplink bus-level USB transactions encapsulated in corresponding ones of the RMP acknowledgement messages.

5. The method of claim 1, wherein:

the receiving downlink USB transaction requests includes receiving USB read, USB write, and USB control requests; and

the converting includes converting each of the USB read, USB write, and USB control requests into corresponding ones of the bus-level USB transactions that implement the USB transaction requests, including USB tokens, USB data, USB handshake, and USB special transactions according to a USB standard.

6. The method of claim 5, wherein the USB tokens include IN, OUT, and SETUP tokens according to the USB standard.

19. The method of claim 1, wherein the Ethernet parameters include destination and source Media Access Control (MAC) addresses, and an ethertype.

20. The method of claim 1, wherein the RMP parameters include an encapsulation protocol version, INIT, SYNC, MSG, and ACK parameters, and sender and receiver sequence numbers.

7. An apparatus comprising:

one or more Power-over-Ethernet (PoE) enabled network ports to communicate with a communication network and Universal Serial Bus (USB) devices; and

a processor coupled to the PoE network ports, to;

establish a Transmission Control Protocol/Internet Protocol (TCP/IP) connection with an application program;

receive downlink TCP/IP packets carrying USB transaction requests destined for the USB device from the application program over the TCP/IP connection;

convert the received downlink TCP/IP packets carrying the USB transaction requests to downlink bus-level USB transactions that are understandable to the USB device; and

send, using a Reliable Message Protocol (RMP), the downlink bus-level USB transactions to the USB adaptor device over the PoE connection for forwarding by the USB adaptor device to the USB device over the USB connection, wherein the send operation includes encapsulating each downlink bus-level USB transaction in an RMP message and sending the RMP message as an Ethernet packet formatted in accordance with a Network-USB (NUSB) protocol format that includes an Ethernet layer populated with Ethernet parameters, an RMP layer populated with RMP parameters, and a bus-level USB transaction layer populated by bus-level USB transactions.

8. The apparatus of claim 7, wherein the processor:

receives, using the RMP, uplink bus-level USB transactions from the USB adaptor device over the PoE connection that originated from the USB device;

converts the uplink bus-level USB transactions to corresponding uplink TCP/IP packets carrying the uplink bus-level USB transactions; and

causes the uplink TCP/IP packets to be sent carrying the bus-level USB transactions to the application program over the TCP/IP connection.

9. The apparatus of claim 7, wherein the processor causes the uplink packets to be sent using the RMP by performing a multi-message handshake between an RMP sender implemented in the network device and an RMP receiver implemented in the USB adaptor device over the PoE connection so as to cause:

opening of an RMP connection between the RMP sender and the RMP receiver;

causing one or more RMP messages to be sent from the RMP sender to the RMP receiver using the RMP connection, wherein each RMP message encapsulates one of the downlink bus-level USB transactions; and

closing the RMP connection after the RMP messages are sent.

10. The apparatus of claim 9, wherein:

the multi-message handshake further causes receiving one or more RMP acknowledgement messages before the closing; and

the processor receives, using the RMP, the uplink bus-level USB transactions encapsulated in corresponding ones of the RMP acknowledgement messages.

11. The apparatus of claim 7, wherein:

the processor receives USB read, USB write, and USB control requests; and

the processor converts each of the USB read, USB write, and USB control requests into corresponding ones of the bus-level USB transactions that implement the USB transaction requests, including USB tokens, USB data, USB handshake, and USB special transactions according to a USB standard.

12. The apparatus of claim 11, wherein the USB tokens include IN, OUT, and SETUP tokens according to the USB standard.

21. The apparatus of claim 7, wherein the Ethernet parameters include destination and source Media Access Control (MAC) addresses, and an ethertype.

22. The apparatus of claim 7, wherein the RMP parameters include an encapsulation protocol version, INIT, SYNC, MSG, and ACK parameters, and sender and receiver sequence numbers.

13. An apparatus comprising:

a Power-over-Ethernet (PoE) interface to receive a PoE power voltage, and receive and transmit Ethernet packets formatted in accordance with a Network-Universal Serial Bus (NUSB) protocol format that defines (i) an Ethernet layer including fields populated with Ethernet parameters, (ii) a Reliable Message Protocol (RMP) layer including fields populated with RMP parameters, and (iii) a bus-level USB transaction layer including fields populated with bus-level USB transactions;

a power converter to convert the PoE power voltage to a Universal Serial Bus (USB) power voltage;

a USB connector to mate with a USB device and output the USB power voltage to the connected USB device; and

a controller coupled to the PoE interface and the USB connector, to;

receive, through the PoE interface using the RMP, downlink Ethernet packets carrying bus-level USB transaction intended for and understandable by the connected USB device;

unwrap the bus-level USB transactions from the downlink Ethernet packets; and

convert the unwrapped bus-level USB transactions to a downlink USB transaction sequence to be transmitted to the USB device; and

send the downlink USB transaction sequence to the USB device through the USB connector.

14. The apparatus of claim 13, wherein the controller further:

receives an uplink bus-level USB transaction sequence from the USB device through the USB connector;

converts the USB transaction sequence into bus-level USB transactions; and

uses the RMP to cause the bus-level USB transactions to be transmitted in Ethernet packets through the PoE interface.

15. The apparatus of claim 14, wherein the controller uses the RMP as a sender-side RMP to both transmit and receive Ethernet packets.

16. The apparatus of claim 13, wherein the controller uses the RMP by performing a multi-message handshake between an RMP receiver and an RMP sender connected to the controller through the Ethernet interface, to:

open of an RMP connection between the RMP sender and the RMP receiver;

cause one or more RMP messages to be sent from the RMP sender to the RMP receiver using the RMP connection, wherein each RMP message encapsulates one of the bus-level USB transactions; and

close the RMP connection after the RMP messages are sent.

17. The apparatus of claim 13, wherein the bus-level USB transactions include USB tokens, USB data, USB handshake, and USB special transactions according to a USB standard.

18. The apparatus of claim 17, wherein the USB tokens include IN, OUT, and SETUP tokens according to the USB standard.

23. The apparatus of claim 13, wherein the Ethernet parameters include destination and source Media Access Control (MAC) addresses, and an ethertype.

24. The apparatus of claim 13, wherein the RMP parameters include an encapsulation protocol version, INIT, SYNC, MSG, and ACK parameters, and sender and receiver sequence numbers.