USB transmission system, device, method and program

Abstract

The purpose of the present disclosure is to enable data to be collected from a plurality of USB devices installed at distant locations.　The present invention is a USB transmission system comprising a device-side transmitter / receiver for transmitting / receiving data to and from the USB devices and a host-side transmitter / receiver for transmitting / receiving data to and from a USB host. The device-side transmitter / receiver and the host-side transmitter / receiver are provided with a data transmission / reception unit for transmitting / receiving a USB protocol layer packet via a data network, and the host-side transmitter / receiver is provided with a hub for transferring to the USB host the transmitted / received data of the data transmission / reception unit which this transmitter / receiver is provided with.

Description

[Technical field]

[0001] This disclosure relates to remote point-to-point USB communications. [Background technology]

[0002] With the spread of IoT and AI, the practice of installing various Universal Serial Bus (USB) devices such as USB sensors and USB cameras in a wide range of remote locations and collecting data generated from these devices is spreading. In order to advance the above activities, it is necessary to establish a method for collecting information from USB devices in remote locations. In general, a computer that connects to the USB device is installed near the USB device in the remote location, and the computer terminates the USB communication, interprets the information, transmits the interpreted information over a network, and collects it on a server in the remote location.

[0003] In this configuration, software is required to send and receive data between the computer and the server to collect data from the USB device. The data transmission software on the computer side must terminate very large-capacity USB communications such as 20 Gbps for USB3.2 Gen2 x2 and interpret the information, so a very high-spec computer is required. Since many USB devices are installed over a wide area, it is not realistic to install such a computer near each USB device. Therefore, it is desirable to adopt a configuration in which the USB device side equipment does not terminate USB communications or interpret the obtained data.

[0004] Also, in the case of a USB device, it is possible to change the settings of the device via the USB-IF. For example, the resolution of a camera. However, in this embodiment, the server and the USB device are not connected via the USB-IF, and only information on the USB device is collected via software, and the state of the USB device cannot be controlled from the server side. Of course, it is possible to provide the data transmission software and the data reception software with a function for controlling the state of the USB device, but in that case, such a function must be provided for each of the many USB devices, which is not realistic. Therefore, it is desirable to adopt a configuration in which USB communication is transparently transmitted to the server.

[0005] A technology called USB / IP (Internet Protocol) has been disclosed that allows a server to use a USB device connected to a computer in a remote location (for example, see Non-Patent Document 1). USB / IP terminates USB communication in USB / IP Client software, extracts data (USB Request Block), and transmits this to a remote USB / IP Host, where the USB / IP Host uses the transmitted data to simulate a USB device. By using this technology, it is possible to create a state in which a remote USB device appears to be directly connected to the server, and the USB communication is transmitted transparently to the server.

[0006] Also, a technology has been disclosed that transmits USB physical signals over optical signals (for example, see Non-Patent Document 2). This technology transmits USB physical signals as they are, making it possible to create a state in which a USB device in a remote location is connected directly to a server, and is configured to transmit USB communications transparently to the server. In addition, since the USB optical transceiver transmits USB physical signals as they are, it is also configured so that the USB device side does not terminate USB communications or interpret the data obtained by terminating USB communications.

[0007] However, in Non-Patent Document 1, the USB / IP software is configured to temporarily terminate USB communication, which poses a problem in that high-speed processing is required of the computer near the USB device.

[0008] Also, in Non-Patent Document 2, in USB 3.0 and later, a timer called Pending_HP_Timer exists in the link layer, and although the value of this timer differs depending on the device, it is a very small value of about 10 μs. In this method of extending the physical layer of USB, transmission is only possible for about 1 km considering the speed of light. Furthermore, in Non-Patent Document 2, the connection relationship between the USB device and the server depends on the physical configuration. Specifically, when two USB devices are connected to a USB optical transceiver installed on the device side, the two USB devices can only be connected to one server connected to the opposing USB optical transceiver. In other words, in order to connect two USB devices in the same area to different servers, two sets of opposing USB optical transceivers must be prepared. [Prior art documents] [Non-patent literature]

[0009] [Non-Patent Document 1] Takahiro Hirofuchi, Eiji Kawai, Kazutoshi Fujikawa, and Hideki Sunahara: USB / IP - a Peripheral Bus Extension for Device Sharing over IP Network, Proceedings of the 2005 USENIX Annual Technical Conference, p. 47-60, April 10-15, 2005, Anaheim, CA, USA.https: / / www.usenix.org / legacy / events / usenix05 / tech / freenix / hirofuchi / hirofuchi.pdf [Non-Patent Document 2] “USB 3.0 Extender”, Bay Technologies http: / / bayt.co.jp / products / branded / usb_extender / usb3 / spectra3022.html Summary of the Invention [Problem to be solved by the invention]

[0010] The present disclosure aims to enable data collection from multiple USB devices installed in remote locations. [Means for solving the problem]

[0011] In this disclosure, a host-side transceiver that operates as a USB hub is provided on the USB host side, and a device-side transceiver that operates as a DS (Downstream) port of the USB hub is provided on the USB device side. By adopting a configuration in which USB protocol layer packets are exchanged between these transceivers via a data network, remote transmission via USB is made possible.

[0012] The USB transmission system of the present disclosure comprises: a device-side transceiver having a USB port connectable to a USB device; A host-side transceiver that can be connected to a USB host; Equipped with the device-side transceiver and the host-side transceiver each include a data transceiver unit for transmitting and receiving packets of a USB protocol layer via a data network; The host-side transceiver includes a hub that transfers data transmitted and received by a data transceiver section included in the host-side transceiver to the USB host.

[0013] The USB transmission device of the present disclosure is A USB port that can be connected to a USB device, A DS (Downstream) function unit that transmits and receives data to and from a USB device connected to the USB port; A data transmitter / receiver unit that transmits and receives data via a data network and a host-side transmitter / receiver that is connected to a USB host, The data transmission / reception unit is When the DS function unit receives data from the USB device, it generates a packet of a USB protocol layer storing the data, and transmits the packet to the host-side transceiver; When a packet of the USB protocol layer is received from the host-side transceiver, the data stored in the packet is transferred to the DS function unit.

[0014] The USB transmission device of the present disclosure is A US (Up Stream) function section that transmits and receives data to and from a USB host; The device includes a device-side transceiver having a USB port connectable to a USB device, and a data transceiver for transmitting and receiving data via a data network, The data transmission / reception unit is When the US function unit receives data from the USB host, it generates a packet of a USB protocol layer storing the data, and transmits the packet to the device-side transceiver; When a packet of the USB protocol layer is received from the device-side transceiver, the data stored in the packet is transferred to the US function unit.

[0015] The USB transmission method of the present disclosure includes: A device-side transceiver having a USB port connectable to a USB device; A host-side transceiver that can be connected to a USB host; A USB transmission method executed by a USB transmission system comprising: The device-side transceiver and the host-side transceiver transmit and receive packets of a USB protocol layer over a data network; A hub provided in the host side transceiver transfers data transmitted and received by a data transceiver provided in the host side transceiver to the USB host.

[0016] The program of the present disclosure is a program for causing a computer to realize each functional unit of an apparatus of the present disclosure, and is a program for causing a computer to execute each step of a method performed by an apparatus of the present disclosure. Effect of the Invention

[0017] The present disclosure can enable data collection from multiple installed USB devices in remote locations. [Brief description of the drawings]

[0018] [Figure 1] 2 shows an example of a system configuration according to the present embodiment. [Diagram 2] 2 shows an example of a system configuration according to the present embodiment. [Diagram 3] 2 shows an example of a system configuration according to the present embodiment. [Figure 4] 2 shows an example of a system configuration according to the present embodiment. [Diagram 5] 1 shows an example of a system configuration of the present embodiment. [Figure 6] 2 shows an example of the configuration of a device-side transceiver 91. [Figure 7] 2 shows an example of the configuration of a host-side transceiver 93. [Figure 8] A configuration example of the orchestrator 95 is shown. [Figure 9] 13 shows an example of the configuration of a transceiver information management unit. [Figure 10] 13 shows an example of a host connection completion notification. [Figure 11] 13 shows an example of the configuration of a transceiver information management unit. [Figure 12] 1 shows an example of a connection establishment sequence. [Figure 13] An example of a USB port connection request is shown below. [Figure 14] 13 shows an example of the configuration of a transceiver information management unit. [Figure 15] 13 shows an example of a connection establishment request notification. [Figure 16] 13 illustrates an example of the configuration of a host-side connection information management unit. [Figure 17] 13 shows an example of a transmitter-receiver connection request. [Figure 18] 13 illustrates an example of the configuration of a device-side connection information management unit. [Figure 19] An example of a connection between the transmitter and receiver that is OK is shown below. [Figure 20] 13 illustrates an example of the configuration of a host-side connection information management unit. [Figure 21] 13 shows an example of the configuration of a DS status management unit. [Figure 22] An example of connection establishment OK is shown below. [Figure 23] An example of a USB port connection OK is shown below. [Figure 24] 1 shows an example of a device connection sequence. [Diagram 25] An example of a USB device connection completion notification is shown. [Figure 26] 13 shows an example of a port reset request. [Figure 27] An example of a port reset completion is shown. [Figure 28] 1 shows an example of a method for transmitting protocol layer packets in USB. [Figure 29] An example of a USB packet is shown below. [Diagram 30] An example of a USB packet is shown below. [Diagram 31] 1 shows an example of a method for transmitting protocol layer packets in USB. [Diagram 32] An example of a USB packet is shown below. [Diagram 33] An example of a USB packet is shown below. [Diagram 34] An example of processing (OUT transaction) performed with a USB packet is shown below. [Diagram 35] An example of a process (IN transaction) performed with a USB packet is shown below. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Hereinafter, the embodiments of the present disclosure will be described in detail with reference to the drawings. Note that the present disclosure is not limited to the embodiments shown below. These implementation examples are merely illustrative, and the present disclosure can be implemented in various forms with various modifications and improvements based on the knowledge of those skilled in the art. Note that components with the same reference numerals in this specification and drawings are assumed to indicate the same components.

[0020] (First embodiment) An example of the system configuration of this embodiment is shown in Fig. 1. In the USB transmission system of this embodiment, a device-side transceiver 91 is connected between a network 81 and a USB device 92, and a host-side transceiver 93 is connected between the data network 81 and a server 94. In this manner, this embodiment employs a configuration in which the host-side transceiver 93 that operates as a USB hub on the USB host side and the device-side transceiver 91 that operates as a DS (Down Stream) port of the USB hub on the USB device side are provided, and packets of the USB protocol layer are exchanged between the transceivers via the data network 81.

[0021] By adopting this configuration, the USB transmission system of this embodiment enables termination at the server 94, and does not terminate USB communication at the device-side transceiver 91, so it is possible to adopt a configuration that transparently transmits USB communication between the USB device 92 and a server 94 located at a remote location without installing a high-spec computer near the USB device 92. Also, by adopting this configuration, it is possible to extend USB communication between two remote points without relying on the link layer timer of USB 3.0.

[0022] Second Embodiment FIG. 2 shows an example of the system configuration of this embodiment. The USB transmission system of this embodiment includes: A connection state between the host-side transceiver 93 and the server 94, i.e., the USB host, A connection state between the device-side transceiver 91 and the USB device, A connection establishment state between the host-side transceiver 93 and the device-side transceiver 91; At least one of the above is exchanged between the host side transceiver 93 and the device side transceiver 91 via a control network 82 that is the same as or different from the data network 81, and the operation of the device side transceiver 91 and the host side transceiver 93 is determined based on these states.

[0023] The USB transmission system of this embodiment, with this configuration, can exchange the states of the USB hub and the DS port of the USB hub with each other, so that the USB hub and the entire DS port of the USB hub, which are physically separated, can appear to the server 94 and USB device 92 to be operating as a general USB hub.

[0024] (Third embodiment) 3 shows an example of the system configuration of this embodiment. The USB transmission system of this embodiment has a data transmitter / receiver 13 in a device-side transmitter / receiver 91 that corresponds one-to-one to the USB port of the device-side transmitter / receiver 91, and a data transmitter / receiver 33 in a host-side transmitter / receiver 93 that corresponds one-to-one to the DS port of the guest-side transmitter / receiver 91. The device-side transceiver 91 and the host-side transceiver 93 each have a table for controlling the connection relationship between these data transceivers. Based on the description in the table, a connection relationship between the data transmission / reception units 13 and 33 is established.

[0025] By adopting this configuration, the USB transmission system of this embodiment makes it possible to freely change the connection relationship between the server 94 and the USB device 92 via the data network 81.

[0026] (Fourth embodiment) An example of the system configuration of this embodiment is shown in Fig. 4. The USB transmission system of this embodiment has a configuration in which a table for controlling the connection relationship between the data transmission / reception units 31 and 33 described in the third embodiment can be controlled by an orchestrator 95.

[0027] By adopting this configuration, the USB transmission system of this embodiment is able to access the orchestrator 95 using software, making it possible to control the connection relationship between the USB device 92 and the server 94 via software.

[0028] (Effects of the present disclosure) The USB transmission system of the present disclosure may employ the system configurations described in the first to fourth embodiments. The device-side transceiver 91 and the host-side transceiver 93 function as the USB transmission device of the present disclosure. By employing the system configuration of any one of the first to fourth embodiments, the present disclosure can achieve the following effects. It is possible to directly connect a USB device 92 located in a remote location to a server 94 without the need for software processing. Since multiple USB ports of the device-side transceiver 91 can be connected to USB hubs of multiple different host-side transceivers 93, the connection relationship between the USB device 92 and the server 94 can be freely changed.

[0029] The present disclosure is not limited to the embodiments described above. For example, the data transmission / reception units 13 and 33 use UDP (User Datagram Protocol) / IP, but are not limited to this. For example, technologies such as Ethernet (registered trademark), MPLS (Multi-Protocol Label Switching), and OTN (Optical Transport Network) may also be used. Additionally, the server 94 may be any device that collects information about the USB device 92. In this disclosure, any device that collects information about the USB device 92 is referred to as a "USB host." Also, the orchestrator 95 may be configured to manage all the states of the host-side transceiver 93 and the device-side transceiver 91 .

[0030] Fifth embodiment In this embodiment, the details of the configuration of the present disclosure will be described. Fig. 5 shows an example of the system configuration of this embodiment. The system of this embodiment has the configuration described in the third and fourth embodiments. Specifically, a device-side transceiver 91 and a host-side transceiver 93 are connected to each other by a data network 81, and are connected to an orchestrator 95 via a control network 82.

[0031] 6 shows an example of the configuration of a device-side transceiver 91. The device-side transceiver 91 includes a USB port 11, a DS 12 that operates as a DS functional unit, a data transceiver unit 13, a control transceiver unit 14, a DS controller 15, a device-side transceiver control unit 16, a device-side connection information management unit 17, and a DS status management unit 18. The device-side transceiver 91 can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided via a network.

[0032] The USB port 11 is a port connected to a USB device 92. The device side connection information management unit 17 manages device side connection information indicating the connection relationship between the device side transceiver 91 and the host side transceiver 93. The DS status management unit 18 manages the connection status between each USB port 11 and the USB device 92.

[0033] A DS 12 is provided for each USB port 11, and transmits and receives packets to and from a USB device 92. A data transmitter / receiver 13 is provided for each USB port 11, and transmits and receives data to and from a connected host-side transmitter / receiver 93. A DS status manager 18 manages the connection state between each data transmitter / receiver 13 and a data transmitter / receiver 33.

[0034] 7 shows an example of the configuration of the host-side transceiver 93. The host-side transceiver 93 includes a US 32 that operates as a US functional unit, a data transceiver unit 33, a control transceiver unit 34, a US controller 35, a host-side transceiver control unit 36, a host-side connection information management unit 37, a hub 41, a hub-side port 42, and a hub controller 43. The host-side transceiver 93 can also be realized by a computer and a program, and the program can be recorded on a recording medium or provided via a network.

[0035] The US 32 transmits and receives data to and from a USB host 96. The hub 41 is connected to the US 32, and is connected to a data transmitter / receiver 33 via a hub-side port 42, and functions as a USB hub. A data transmitter / receiver 33 is provided for each hub-side port 42, and transmits and receives data to and from a device-side transmitter / receiver 91 to which it is connected.

[0036] The host side connection information management unit 37 manages host side connection information indicating the connection relationship between the host side transceiver 93 and the device side transceiver 91. The host side connection information includes a hub side port number, data transceiver information, destination transceiver information, destination transceiver port number information, destination control transceiver information, and destination data transceiver information. The data transceiver information is identification information of the data transceiver 33. The destination transceiver information is identification information of the destination device side transceiver 91. The destination transceiver port number information is a port number in the destination device side transceiver 91. The destination control transceiver information is identification information of the control transceiver in the destination device side transceiver 91. The destination data transceiver information is identification information of the data transceiver 13 in the destination device side transceiver 91. The identification information in this disclosure is any information unique within the USB transmission system, and may be a number or an IP address.

[0037] 8 shows an example of the configuration of the orchestrator 95. The orchestrator 95 includes a connection request receiving unit 51, a transceiver instruction unit 52, and a transceiver information management unit 53. The connection request receiving unit 51 receives a USB port connection request. The USB port connection request can be transmitted to the orchestrator 95 from any device, such as the device-side transceiver 91 and the host-side transceiver 93, or from a user, using software or the like. The transceiver instruction unit 52 is connected to the device side transceiver 91 and the host side transceiver 93, and provides information regarding the establishment of a connection to at least one of the device side transceiver 91 and the host side transceiver 93. This information is, for example, a request for establishing a connection, an instruction, or a notification of completion.

[0038] The transceiver information management unit 53 stores information on the host side transceiver 93 and the device side transceiver 91. Fig. 9 shows an example of the transceiver information management unit. The information on the host side transceiver 93 includes, for example, a host side transceiver number indicating identification information of the host side transceiver 93, a control transceiver unit IP address indicating identification information of the control transceiver unit 34, and a host connection status indicating the connection status with the USB host 96. The information on the device side transceiver 91 includes a device side transceiver number indicating identification information of the device side transceiver 91, and a control transceiver unit IP address indicating identification information of the control transceiver unit 14. The information on the device side transceiver 91 may include the connection status of each USB port 11 with the USB device 92.

[0039] The control transceiver 14 in the device-side transceiver 91 and the control transceiver 34 in the host-side transceiver 93 exchange the information described in the second embodiment with each other via the control network 82. The DS controller 15 controls the DS 12 based on the information transmitted and received by the control transmission / reception unit 14. The device side transceiver control unit 16 controls the data transmission / reception unit 13 based on the information transmitted and received by the control transmission / reception unit 14. The hub controller 43 controls the hub 41 based on the information transmitted and received by the control transceiver 34. The US controller 35 controls the US 32 based on the information transmitted and received by the control transceiver 34. The host transceiver control unit 36 ​​controls the data transceiver 33 based on the information transmitted and received by the control transceiver 34.

[0040] In the system configuration shown in FIG. 5, an embodiment in which a USB device 92 is connected to a host-side transceiver 93 for communication can be broadly described as follows: (1) Host connection sequence (2) Connection establishment sequence (3) Device connection sequence Below, each sequence will be described when the USB device 92#A-3 connected to the USB port 11#3 of the device-side transceiver 91#2 is connected to the host-side transceiver 93#2.

[0041] (1) Host connection sequence A user connects the host-side transceiver 93#2 to the USB host 96. At this time, the hub controller 43 and US controller 35 of the host-side transceiver 93#2 perform connection processing equivalent to that of a normal USB hub. When the process of connecting with the USB host 96 is completed, the hub controller 43 of the host side transceiver 93#2 notifies the host side transceiver control unit 36 ​​that the connection with the USB host 96 has been completed. The host side transceiver control unit 36 ​​transmits a host connection completion notification to the transceiver instruction unit 52 of the orchestrator 95 (S101). An example of the host connection completion notification is shown in Fig. 10. The host connection completion notification includes the identification information "#2" of the host side transceiver 93. When the orchestrator 95 receives the host connection completion notification, it updates the transceiver information management unit 53. For example, as shown in Fig. 11, it updates the host connection status of the host side transceiver number "#2" from "not connected" to "connected."

[0042] (2) Connection establishment sequence The connection establishment sequence between the host-side transceiver 93 and the USB device 92 will be described with reference to FIG. The user uses software to send a USB port connection request to the orchestrator 95. An example of the USB port connection request is shown in Fig. 13. The USB port connection request includes the identification information "#2" of the host-side transceiver 93, the identification information "#A" of the device-side transceiver 91, and the identification information "#3" of the USB port 11.

[0043] The connection request receiving unit 51 of the orchestrator 95 receives a USB port connection request from a user or the like (S111) and notifies the transceiver instruction unit 52. The transceiver instruction unit 52 of the orchestrator 95 refers to the transceiver information management unit 53, and if the host connection state of the host side transceiver 93 to which the connection request was made is "connected", it transmits a connection establishment request to the host side transceiver 93 (S112). In this embodiment, as shown in FIG. 14, since the host connection state of the host side transceiver 93#2 is "connected", a "connection establishment request" is transmitted to the host side transceiver 93.

[0044] An example of a connection establishment request notification is shown in Fig. 15. The connection establishment request notification includes the identification information "#2" of the host side transceiver 93, the IP address of the control transceiver unit 24 of the host side transceiver 93, the identification information "#A" of the device side transceiver 91, the port number "#3" of the device side transceiver 91, and the IP address of the control transceiver unit 14 of the device side transceiver 91.

[0045] The host-side transceiver control unit 36 ​​of the host-side transceiver 93 selects the data transceiver 33 to be used for connection based on the host-side connection information management unit 37, and updates the host-side connection information management unit 37. For example, as shown in Fig. 16, when the hub-side port #1 of the host-side transceiver 93#2 is connected to the USB device 92#A-3 of the device-side transceiver 91#A, the identification information "#A" of the device-side transceiver 91, the port number information "#3" of the connection destination, and the IP address "192.168.2.11" of the control transceiver 14 of the connection destination are associated with and stored in the identification information of the hub-side port #1 and the data transceiver 33#1.

[0046] Here, the method of selecting the data transmitter / receiver 33 is arbitrary, and for example, the unused data transmitter / receiver 33 may be selected in order from the top. If all the data transmitter / receiver 33 are occupied, a "connection establishment NG notice" is sent to the orchestrator 95 to inform the orchestrator that a connection cannot be established.

[0047] The host-side transceiver control unit 36 ​​adds the identification information of the selected data transceiver unit 33 and transmits the transceiver connection request to the device-side transceiver 91 (S113). For example, when the data transceiver unit 33#1 of the host-side transceiver 93#2 is selected, as shown in Fig. 17, the IP address "10.0.0.10:1000" of the data transceiver unit 33#1 is added to the connection establishment request in the transceiver connection request.

[0048] If the desired USB port number described in the received connection request is unused, the device-side transceiver control unit 16 of the device-side transceiver 91 updates the device-side connection information management unit 17. For example, as shown in Fig. 18, the identification information "#2" of the host-side transceiver 93, the port number "#1" of the destination host-side transceiver 93, and the IP address "10.0.0.10:1000" of the destination data transceiver unit 33 are stored in the destination transceiver information for USB port number #3. At this time, the IP address "192.168.1.12" of the control transceiver unit 34 of the destination host-side transceiver 93 may also be linked.

[0049] The device-side transceiver control unit 16 adds the data transceiver information and transmits a transceiver connection OK to the host-side transceiver 93 (S114). An example of the transceiver connection OK notification is shown in Fig. 19. The transceiver connection OK notification includes the IP address of the data transceiver unit 13, "10.0.0.20:10003", as the information of the data transceiver unit 13.

[0050] The host-side transceiver control unit 36 ​​updates the information in the host-side connection information management unit 37 based on the inter-transmitter / receiver connection OK from the device-side transceiver control unit 16. For example, as shown in Fig. 20, the IP address "10.0.0.20:10003" of the data transceiver unit 13 connected to the hub-side port #1 is stored in association with the hub-side port #1.

[0051] The host-side data transmission / reception unit 33 and the device-side data transmission / reception unit 13 establish a connection based on information from the host-side connection information management unit 37 and the device-side connection information management unit 17 (S115). Here, the method of establishing a connection is arbitrary, and for example, a TCP connection is established in the case of TCP (Transmission Control Protocol), an IPsec connection is established in the case of IPsec (Security Architecture for Internet Protocol), a UDP socket is established and a test packet is exchanged in the case of UDP, etc.

[0052] The device-side transceiver control unit 16 updates the DS status management unit 18 when the connection is established (S116). In this embodiment, since the connection to USB port number #3 is established, the status of USB port number #3 is updated to “connection established” as shown in FIG.

[0053] Upon connection establishment, the host-side transceiver control unit 36 ​​transmits a connection establishment OK notification to the transceiver instruction unit 52 of the orchestrator 95 (S117). An example of the connection establishment OK notification is shown in Fig. 22. The connection establishment OK notification includes the identification information "#2" of the host-side transceiver 93, the identification information "#A" of the device-side transceiver 91, the port number "#3" of the device-side transceiver 91, the IP address of the control transceiver unit 24 of the host-side transceiver 93, and the IP address of the control transceiver unit 14 of the device-side transceiver 91.

[0054] When the transceiver instruction unit 52 of the orchestrator 95 receives the connection establishment OK notification, it notifies the connection request receiving unit 51 that the connection has been completed. The connection request receiving unit 51 of the orchestrator 95 notifies the USB port connection request OK in response to the connection request from the user or the like (S118). An example of the USB port connection request OK notification is shown in FIG. 23. The USB port connection request OK notification includes the identification information "#2" of the host side transceiver 93, the identification information "#A" of the device side transceiver 91, and the port number "#3" of the device side transceiver 91.

[0055] (3) Device connection sequence The device connection sequence will be described with reference to FIG. The USB device 92 is connected to the USB port 11 of the device-side transceiver 91 (S131). When the DS controller 15 of the device-side transceiver 91 detects the connection of the USB device 92, it refers to the DS status management unit 18, and if the status of the USB port is connection established, it controls the DS 12 and starts supplying power. If the connection is not established, it does not supply power. Link training and port configuration are performed (S132) between the USB device 92 and the device-side transceiver 91. For example, this is in accordance with the description of USB3.2 Revision 1.0 7.5 Link Training and Status State Machine (LTSSM). When the port configuration is completed and the USB device 92 enters the default state, the DS controller 15 of the device-side transceiver 91 notifies the device-side transceiver control unit 16 of the completion of the USB device connection to the USB port 11 .

[0056] The device-side transceiver control unit 16 refers to the device-side connection information management unit 17 and transmits a USB device connection completion notification to the destination described in the connection destination control transceiver information of the port number to which the USB device 92 is connected (S133). For example, when the USB device 92 is connected to USB port number #3, the device-side transceiver control unit 16 transmits a USB device connection completion notification to the IP address "192.168.1.12" described in the connection destination control transceiver information shown in Fig. 18. As a result, the USB device connection completion notification is transmitted to the control transceiver unit 34 of the host-side transceiver 93#2.

[0057] An example of the USB device connection completion notification is shown in Fig. 25. The USB device connection completion notification indicates that the connection of the USB device has been completed, and includes the destination transceiver information and the destination transceiver port number information. The destination transceiver information is the identification information "#A" of the device-side transceiver 91, and the destination transceiver port number information is the port number "#3" to which the USB device 92 is connected.

[0058] The host side transceiver control unit 36 ​​refers to the host side connection information management unit 37, derives the corresponding hub side port number from the destination transceiver information and destination transceiver port number information described in the received USB device connection completion notification, and uses this to notify the hub controller 43 of a change in the hub side port state. For example, as shown in Fig. 20, the host side connection information management unit 37 describes the identification information #A of the device side transceiver 91 in the destination transceiver information and the port number information #3 in the destination transceiver port number information, and these are linked to the hub side port #1. In this case, the hub controller 43 is notified that the hub side port #1 has entered a connected state.

[0059] Upon receiving notification of the change in the hub-side port state, the hub controller 43 controls the hub 41 to start bus enumeration with the USB host 96. Communication between the USB host 96 and the hub 41 complies with the contents described in USB3.2 Revision 1.0 9.1.2 Bus Enumeration. The method of transmitting packets of the USB protocol layer exchanged between the USB host 96 and the USB device 92 will be described later.

[0060] Step S41: The hub 41 notifies the USB host 96 of the occurrence of an event of device insertion / removal. At this time, the hub side port number (#1 in this example) is used as the port number for the event occurrence. Step S42: The USB host 96 inquires of the hub 41 about a status change, and the hub 41 responds to the USB host 96 with the details of the status change. In step S43, the USB host 96 resets the connected USB device 92 if necessary. Step S44-1: When the USB device 92 is reset in step S43, the hub 41 resets its own hub-side port 42 and notifies the hub controller 43 of the reset. In step S44-2, the hub controller 43 refers to the host-side connection information management unit 37 to derive the destination transceiver information, destination transceiver port number information, and destination control transceiver information corresponding to the hub-side port number to which the reset USB device 92 belongs, and transmits a port reset request for the destination transceiver port number to the destination of the destination control transceiver information. An example of the port reset request is shown in FIG. 26. In step S44-3, the device-side transceiver control section 16 instructs the DS controller 15 to reset the USB port 11 requested by the DS controller 15. Step S44-4: Link training and port configuration are carried out between the USB device 92 and the device-side transceiver 91. Step S44-5. When the port configuration is completed and the USB device 92 enters the default state, the DS controller 15 of the device-side transceiver 91 notifies the device-side transceiver control unit 16 of the completion of the USB device connection to the USB port 11. In step S44-6, the device-side transceiver control unit 16 notifies the destination described in the destination control transceiver information of the port number to which the USB device 92 is connected of the port reset completion, with reference to the device-side connection information management unit 17. An example of the port reset completion is shown in FIG. The rest is the same as USB3.2 Revision 1.0 9.1.2 Bus Enumeration 5 and later.

[0061] An example of a method for transmitting protocol layer packets in USB will be described with reference to FIG. 28. (In the case of an IN transaction) The DS12 receives a USB packet from the USB device 92 (S211). A link command in the link layer is exchanged between the USB device 92 and the device-side transceiver 91. The DS12 passes the USB packet obtained by processing the link layer to the data transceiver unit 13 (S212).

[0062] The data transmitter / receiver 13 transmits the received USB packet to the opposing data transmitter / receiver 33 with which a connection has been established, using the specified transmission method (IP in this example) (S213). An example of a USB packet is shown in FIG. 29. At this time, it is noted that it is a data packet, and a header and data are separated before being sent. For example, "USB Protocol Info="DP"" is noted in the payload. This allows the receiving data transmitter / receiver 33 to separate the header and data and pass them to the hub-side port 42.

[0063] When the data transmitter / receiver 33 receives the data, it separates the data and the DP Header and passes them to the hub-side port 42 (S214). At this time, the data transmitter / receiver 33 exchanges link commands in the link layer with the device-side transceiver 91. The hub 41 transfers the data to the USB host 96 (S215). The transfer operation from hub-side port 42#1 → hub 41 → US32 → USB host 96 is the same as that of a normal hub.

[0064] The US32 receives a USB packet from the USB host 96 (S221). Here, the transfer operation from USB host 96 → US32 → hub 41 → hub-side port 42#1 is the same as that of a normal hub, but it should be noted that the route string of the ACK TP is set with route information for sending to the hub-side port 42#1. In other words, it is not the port number of the device-side transceiver 91.

[0065] The hub-side port 42#1 passes the USB packet to the corresponding data transmitter / receiver 33 (S222). The data transmitter / receiver 33 transmits the passed USB packet to the opposing data transmitter / receiver 13 with which a connection has been established, using the specified transmission method (IP in this example) (S223). An example of a USB packet is shown in FIG. 30. At this time, the packet is sent with a description that it is a transaction packet. For example, "USB Protocol Info="TP"" is written in the payload. This allows the receiving data transmitter / receiver 13 to pass the packet to the DS12 as a transaction packet.

[0066] When the data transmitter / receiver 13 receives the data, it passes it to the DS 12 as a transaction packet (S224). The DS 12 transfers the data to the USB device 92 (S225). Here, the transfer operation from DS 12#3 to the USB device 92 is the same as that of a normal hub DS.

[0067] An example of a method for transmitting protocol layer packets in USB will be described with reference to FIG. 31. (In the case of an OUT transaction) The US32 receives a USB packet from the USB host 96 (S311). Link commands in the link layer are exchanged in the device-side transceiver 91. Here, the transfer operation from USB host 96 → US32 → hub 41 → hub-side port 42#1 is the same as that of a normal hub. However, it should be noted that the route string of the ACK TP is set with route information for sending to the hub-side port 42#1. In other words, it is not the port number of the device-side transceiver 91.

[0068] The data transmitter / receiver 33 transmits the received USB packet to the opposing data transmitter / receiver 13 with which a connection has been established, using a specified transmission method (IP in this example) (S312). An example of a USB packet is shown in FIG. 32. At this time, it is noted that it is a data packet, and a header and data are separated before being sent. For example, "USB Protocol Info="DP"" is noted in the payload. This allows the receiver's data transmitter / receiver 13 to separate the header and data and pass them to the DS12.

[0069] When the data transmitter / receiver 13 receives the data, it separates the data and the DP Header and passes them to the DS12#3 (S313). The DS12 transfers the data to the USB device 92 (S314). At this time, a link command in the link layer is exchanged in the device-side transceiver 91. Here, the transfer operation from DS12#3 to the USB device 92 is the same as that of the DS12 of a normal hub.

[0070] The data transmitter / receiver 13 transmits the received USB packet to the opposing data transmitter / receiver 33 with which a connection has been established, using the specified transmission method (IP in this example) (S323). An example of a USB packet is shown in FIG. 33. At this time, the packet is sent with a description that it is a transaction packet. For example, "USB Protocol Info="TP"" is written in the payload. This allows the receiving data transmitter / receiver 33 to pass the packet to the hub-side port 42 as a transaction packet.

[0071] When the data transmitter / receiver 33 receives the data, it passes it as a transaction packet to the hub-side port 42 (S324). The transfer operation of hub-side port 42#1→hub 41→US32→USB host 96 is the same as that of a normal hub.

[0072] FIG. 34 shows an example of a process (OUT transaction) performed with a USB packet. The hub-side port 42 passes the USB packets transferred from the hub 41 as is to the data transmitter / receiver 33. The USB packets include a USB data packet, a USB header packet, and a USB transaction packet. The data transmitter / receiver 33 executes payload generation processing, UDP transmission processing, and IP transmission processing in that order. In the payload generation processing, a distinction is made between USB data packets, USB header packets, and USB transaction packets, and payloads are generated to be passed to the UDP transmission processing. In the UDP transmission processing and IP transmission processing, normal UDP and IP processing is executed.

[0073] The data transmitter / receiver 13 executes payload separation processing, UDP reception processing, and IP reception processing in this order. In the payload separation processing, separation into USB data packets, USB header packets, and USB transaction packets is performed. In the UDP reception processing and IP reception processing, normal UDP and IP processing is performed. The DS12 separates the USB data packet, USB header packet, and USB transaction packet. The DS12 adds CRC-16 and LCW to the SB header packet and USB transaction packet, and buffers the header packet for retransmission when a packet loss occurs in the link layer. The DS12 performs link layer processing and physical layer processing on the USB data packet and header packet. This completes the OUT transaction.

[0074] FIG. 35 shows an example of a process (IN transaction) performed with a USB packet. The DS12 performs physical layer processing and link layer processing. The DS12 performs CRC-16 and LCW checking processing, performs header packet buffering, and generates USB header packets and USB transaction packets. On the other hand, the DS12 generates USB data packets. The data transmitter / receiver 13 performs payload generation processing, UDP transmission processing, and IP transmission processing for each of these packets in that order.

[0075] The data transmitter / receiver 33 performs IP reception processing, UDP reception processing, and payload separation processing in that order. This separates the USB data packet, USB header packet, and USB transaction packet. The hub-side port 42 passes each packet transferred from the data transmitter / receiver 33 to the hub 41 as is. This completes the IN transaction.

[0076] The embodiment does not depend on the form shown in this example. Although UDP / IP is used for data transmission and reception, this is not limited to this. Technologies such as Ethernet, MPLS, and OTN may also be used. The orchestrator may be configured to manage the status of all the host-side transceivers and device-side transceivers. [Industrial Applicability]

[0077] The present disclosure can be applied to information communication. [Explanation of symbols]

[0078] 11: USB port 12:DS 13, 33: Data transmission and reception unit 14: Control transmitter / receiver 15:DS Controller 16: Device-side transceiver control unit 17: Device side connection information management unit 18: DS status management section 32:US 34: Control transmitter / receiver 35: US Controller 36: Host side transceiver control unit 37: Host side connection information management unit 41: Hub 42: Hub side port 43: Hub controller 51: Connection request reception unit 52: Transmitter / receiver instruction section 53: Transmitter / receiver information management section 81: Data Network 82: Control network 91: Device side transmitter / receiver 92: USB device 93: Host side transmitter / receiver 94: Server 95: Orchestrator 96: USB host

Claims

1. A device-side transceiver having a USB port connectable to a USB device; a host-side transceiver connectable to a USB host; an orchestrator that manages a connection relationship between the device-side transceiver and the host-side transceiver; Equipped with the device-side transceiver and the host-side transceiver each include a data transceiver unit for transmitting and receiving packets of a USB protocol layer via a data network; The device side transceiver includes: a DS (Down Stream) function unit for transmitting and receiving data to and from a USB device for each of the USB ports; a DS controller that operates the DS function unit as at least one of the DS ports of the host transceiver in accordance with an instruction from the orchestrator; Equipped with USB transmission system.

2. The device side transceiver and the host side transceiver are A connection state between the host-side transceiver and a USB host; A connection state between the device-side transceiver and the USB device, and A connection establishment state between the host-side transceiver and the device-side transceiver; between each other and the orchestrator via a control network; The device-side transceiver determines the operation of the DS function unit and the data transceiver unit based on the exchanged state, The host transceiver determines the operation of the data transceiver unit based on the exchanged state.

2. The USB transmission system according to claim 1.

3. The device side transceiver includes: When receiving a USB packet from a USB device, the data transmission / reception unit of the host transceiver, which is determined for each DS (Down Stream) function unit that transmits and receives data to and from the USB device, is designated as the destination, and the header information and data described in the USB packet received from the USB device are converted into a USB packet stored in a payload; When a USB packet is received from the data transceiver unit of the host transceiver, header information and data are obtained from a payload of the USB packet, and the header information and data are converted into a USB packet for a USB device.

3. The USB transmission system according to claim 1 or 2.

4. a USB port capable of connecting to a USB device; a DS (Down Stream) function unit for transmitting and receiving data to and from a USB device connected to the USB port; a data transmission / reception unit for transmitting and receiving data via a data network with a host-side transceiver connected to a USB host; a DS controller that operates the DS function unit as at least one of the DS ports of the host transceiver in accordance with an external instruction; Equipped with The data transmission / reception unit is When the DS function unit receives data from a USB device, it generates a packet of a USB protocol layer storing the data, and transmits the packet to the host-side transceiver; When a packet of a USB protocol layer is received from the host-side transceiver, the data stored in the packet is transferred to the DS function unit. USB transmission device.

5. a device-side transceiver having a USB port connectable to a USB device; a host-side transceiver connectable to a USB host; an orchestrator that manages a connection relationship between the device-side transceiver and the host-side transceiver; A USB transmission method executed by a USB transmission system comprising: the device transceiver and the host transceiver transmit and receive packets at a USB protocol layer over a data network; a DS (Down Stream) function unit provided in the device-side transceiver transmits and receives data to and from a USB device for each of the USB ports; a DS controller provided in the device-side transceiver causes the DS function unit to operate as at least one of the DS ports of the host-side transceiver in accordance with an instruction from the orchestrator; USB transmission method.

6. A program for implementing a computer as the USB transmission device according to claim 4.

Images