Patent Application
20240119018
The present disclosure relates to USB communication between two locations.
With the spread of IoT and AI, efforts to widely install various USB devices such as a universal serial bus (USB) sensor and a USB camera in remote locations and collect data generated from these devices have been expanded. In order to proceed with the above operation, it is necessary to establish a method for collecting information on a USB device at a remote location. In general, a computer connected to a USB device is installed in the vicinity of the USB device at a remote location, USB communication is terminated at the computer, information is interpreted, and the information obtained by the interpretation is transmitted over a network and collected by a server at the remote location.
In this configuration, in order to collect data from the USB device, software for transmitting/receiving data between the computer and the server is required. In the data transmission software on the computer side, it is necessary to interpret information by terminating extremely large-capacity USB communication such as 20 Gbps like USB 3.2 Gen 2×2, and thus, a very high-spec computer is required. A large number of USB devices are installed in a wide area, and thus, it is not realistic to install such a computer in the vicinity of each USB device. It is therefore desirable to adopt a configuration in which termination of the USB communication and interpretation of the obtained data are not performed by equipment on the USB device side.
In the USB device, settings of the device can be changed via a USB-IF. For example, the settings include resolution of a camera. However, in the present 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, so that a 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 of controlling the state of the USB device, but in that case, such a function needs to be provided for each of a large number of USB devices, which is not realistic. It is therefore desirable to adopt a configuration in which USB communication is transparently transmitted to the server.
A technology called USB/internet protocol (IP) that enables a server to use a USB device connected to a computer at a remote location is disclosed (see, for example, Non Patent Literature 1). In USB/IP, USB communication is terminated in USB/IP client software, data (USB Request Block) is extracted and transmitted to a remote USB/IP host, and the USB device is simulated using the data transmitted in the USB/IP host. By using the present technology, it is possible to create a state as if the USB device at the remote location were directly connected to the server, and the USB communication is transparently transmitted to the server.
In addition, a technology for transmitting a USB physical signal on an optical signal is disclosed (see, for example, Non Patent Literature 2). In the present technology, the USB physical signal is transmitted as it is, so that it is possible to create a state as if the USB device at the remote location were directly connected to the server, and the USB communication is transparently transmitted to the server. In addition, a USB optical transmitter/receiver transmits the USB physical signal as it is, equipment on the USB device side neither terminates USB communication nor interprets the data obtained by terminating the USB communication.
However, in Non Patent Literature 1, USB/IP software is configured to temporarily terminate USB communication, and thus, there is a problem that a computer in the vicinity of the USB device is required to perform high-speed processing.
In Non Patent Literature 2, a timer called Pending HP Timer exists in a link layer after USB 3.0, but a value of the timer is a very small value of about 10 μs although the value varies depending on the device. In this method of extending a physical layer of the USB, only about 1 km can be transmitted in view of speed of light. Furthermore, in Non Patent Literature 2, a connection relationship between the USB device and the server depends on a physical configuration. Specifically, in a case where two USB devices are connected to the USB optical transmitter/receiver installed on the device side, the two USB devices can only be connected to one server connected to the corresponding USB optical transmitter/receiver. In other words, in order to adopt a mode in which two USB devices in the same area are connected to another server, it is necessary to prepare two sets of corresponding USB optical transmitters/receivers.
An object of the present disclosure is to enable data collection from a plurality of USB devices installed at remote locations.
In the present disclosure, a host-side transmitter/receiver that operates as a USB hub is provided on a USB host side, and a device-side transmitter/receiver that operates as a downstream (DS) port of the USB hub is provided on a USB device side. Adopting a configuration in which packets of a USB protocol layer are exchanged between these transmitters/receivers via a data network enables remote transmission using a USB.
A USB transmission system of the present disclosure includes:
A USB transmission apparatus of the present disclosure includes:
A USB transmission apparatus of the present disclosure includes:
A USB transmission method of the present disclosure to be performed by a USB transmission system including:
A program of the present disclosure is a program for causing a computer to be implemented as each functional unit included in an apparatus according to the present disclosure, and is a program for causing a computer to execute each step included in a method to be executed by the apparatus according to the present disclosure.
The present disclosure enables data collection from a plurality of USB devices installed at remote locations.
Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The present disclosure is not limited to the embodiments described below. These embodiments are merely an example, and the present disclosure can be carried out in forms with various modifications and improvements based on knowledge of those skilled in the art. Note that components having the same reference numerals in the present specification and the drawings indicate the same components.
The USB transmission system of the present embodiment adopting the present configuration enables termination in the server 94 and does not terminate USB communication in the device-side transmitter/receiver 91, so that it is possible to adopt a configuration in which USB communication between the USB device 92 and the server 94 at a remote location is transparently transmitted without installing a high-spec computer in the vicinity of the USB device 92. Furthermore, by adopting the present configuration, it is possible to extend USB communication between two remote locations without depending on a timer of a link layer in USB 3.0.
In the USB transmission system of the present embodiment adopting the present configuration, the USB hub and the DS port of the USB hub can exchange the states with each other, so that the whole of the USB hub and the DS port of the USB hub, which are physically separated from each other, can be seen from the server 94 and the USB device 92 as if the USB hub and the DS port operated as a general USB hub.
The USB transmission system of the present embodiment can freely change the connection relationship between the server 94 and the USB device 92 via the data network 81 by adopting the present configuration.
The USB transmission system of the present embodiment adopting the present configuration can access the orchestrator 95 using software, so that the connection relationship between the USB device 92 and the server 94 can be controlled via software.
(Effects of Present Disclosure)
The USB transmission system of the present disclosure can adopt the system configuration described in the first to fourth embodiments described above. The device-side transmitter/receiver 91 and the host-side transmitter/receiver 93 function as the USB transmission apparatus of the present disclosure. The present disclosure can obtain the following effects by adopting the system configuration of any one of the first to fourth embodiments.
Note that the present disclosure does not depend on the modes described in the embodiments.
For example, a user datagram protocol (UDP)/IP is used as the data transmission/reception units 13 and 33, but the present disclosure is not limited thereto. For example, a technology such as Ethernet (registered trademark), multi-protocol label switching (MPLS), or optical transport network (OTN) may be used.
Furthermore, the server 94 may be any apparatus that collects information of the USB device 92. In the present disclosure, an arbitrary apparatus that collects information of the USB device 92 is referred to as a “USB host”.
In addition, the orchestrator 95 may manage all the states of the host-side transmitter/receiver 93 and the device-side transmitter/receiver 91.
In the present embodiment, details of the configuration of the present disclosure will be described.
The USB port 11 is a port connected to the USB device 92. The device-side connection information management unit 17 manages device-side connection information indicating a connection relationship between the device-side transmitter/receiver 91 and the host-side transmitter/receiver 93. The DS status management unit 18 manages a connection state with the USB device 92 for each USB port 11.
The DS 12 is provided for each USB port 11 and transmits/receives packets to/from the USB device 92. The data transmission/reception unit 13 is provided for each USB port 11 and transmits/receives data to/from the host-side transmitter/receiver 93 as a connection destination. The DS status management unit 18 manages a connection state between each data transmission/reception unit 13 and the data transmission/reception unit 33.
The US 32 transmits/receives data to/from the USB host 96. The hub 41 is connected to the US 32, is connected to the data transmission/reception unit 33 via the hub side port 42 and functions as a USB hub. The data transmission/reception unit 33 is provided for each of the hub side ports 42 and transmits/receives data to/from the device-side transmitter/receiver 91 as a connection destination.
The host-side connection information management unit 37 manages host-side connection information indicating a connection relationship between the host-side transmitter/receiver 93 and the device-side transmitter/receiver 91. The host-side connection information includes a hub side port number, data transmission/reception unit information, connection destination transmitter/receiver information, connection destination transmitter/receiver port number information, connection destination control transmission/reception unit information, and connection destination data transmission/reception unit information. The data transmission/reception unit information is identification information of the data transmission/reception unit 33. The connection destination transmitter/receiver information is identification information of the device-side transmitter/receiver 91 of the connection destination. The connection destination transmitter/receiver port number information is a port number in the device-side transmitter/receiver 91 of the connection destination. The connection destination control transmission/reception unit information is identification information of the control transmission/reception unit in the device-side transmitter/receiver 91 of the connection destination. The connection destination data transmission/reception unit information is identification information of the data transmission/reception unit 13 in the device-side transmitter/receiver 91 of the connection destination. The identification information in the present disclosure is arbitrary information unique in the USB transmission system and may be a number or an IP address.
The connection request acceptance unit 51 accepts a USB port connection request. The USB port connection request can be transmitted to the orchestrator 95 from any apparatus from a user, or the like, in addition to the device-side transmitter/receiver 91 and the host-side transmitter/receiver 93 by using software, or the like.
The transmitter/receiver instruction unit 52 is connected to the device-side transmitter/receiver 91 and the host-side transmitter/receiver 93 and provides information regarding establishment of connection to at least one of the device-side transmitter/receiver 91 or the host-side transmitter/receiver 93. This information is, for example, a connection establishment request, an instruction, or a notification of completion.
The transmitter/receiver information management unit 53 stores information on the host-side transmitter/receiver 93 and the device-side transmitter/receiver 91.
The control transmission/reception unit 14 included in the device-side transmitter/receiver 91 and 34 included in the host-side transmitter/receiver 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 on the basis of the information transmitted/received by the control transmission/reception unit 14. The device-side transmitter/receiver control unit 16 controls the data transmission/reception unit 13 on the basis of the information transmitted/received by the control transmission/reception unit 14.
The hub controller 43 controls the hub 41 on the basis of the information transmitted/received by the control transmission/reception unit 34. The US controller 35 controls the US 32 on the basis of the information transmitted/received by the control transmission/reception unit 34. The host-side transmitter/receiver control unit 36 controls the data transmission/reception unit 33 on the basis of the information transmitted/received by the control transmission/reception unit 34.
In the system configuration illustrated in
(1) Host Connection Sequence
A user connects the host-side transmitter/receiver 93 #2 to the USB host 96. The hub controller 43 and the US controller 35 of the host-side transmitter/receiver 93 #2 at this time perform connection processing equivalent to that of a normal USB hub.
If the connection processing with the USB host 96 is completed, the hub controller 43 of the host-side transmitter/receiver 93 #2 notifies the host-side transmitter/receiver control unit 36 of completion of the connection with the USB host 96.
The host-side transmitter/receiver control unit 36 transmits a host connection completion notification to the transmitter/receiver instruction unit 52 of the orchestrator 95 (S101).
Upon receiving the host connection completion, the orchestrator 95 updates the transmitter/receiver information management unit 53. For example, as illustrated in
(2) Connection Establishment Sequence
A connection establishment sequence between the host-side transmitter/receiver 93 and the USB device 92 will be described with reference to
The user transmits a USB port connection request to the orchestrator 95 using software.
The connection request acceptance unit 51 of the orchestrator 95 accepts the USB port connection request from the user, or the like (S111) and notifies the transmitter/receiver instruction unit 52 of the USB port connection request. The transmitter/receiver instruction unit 52 of the orchestrator 95 refers to the transmitter/receiver information management unit 53, and if the host connection state of the host-side transmitter/receiver 93 for which a connection has been requested is “connected”, transmits a connection establishment request to the host-side transmitter/receiver 93 (S112). In the present embodiment, as illustrated in
The host-side transmitter/receiver control unit 36 of the host-side transmitter/receiver 93 selects the data transmission/reception unit 33 to be used for connection on the basis of the host-side connection information management unit 37 and updates the host-side connection information management unit 37. For example, as illustrated in
Here, the data transmission/reception unit 33 may be selected using any method, and for example, the data transmission/reception unit 33 that is not used may be selected in order from the top. If all the data transmission/reception units 33 are unavailable, the orchestrator 95 is notified of a “connection establishment NG notification” indicating that connection cannot be established.
The host-side transmitter/receiver control unit 36 adds identification information of the selected data transmission/reception unit 33 and transmits a request for connection between the transmitters/receivers to the device-side transmitter/receiver 91 (S113). For example, in a case where the data transmission/reception unit 33 #1 of the host-side transmitter/receiver 93 #2 is selected, the IP address “10.0.0.10:1000” of the data transmission/reception unit 33 #1 is added to the request for connection between the transmitters/receivers as illustrated in
If the USB port number to be connected described in the received connection request is in an unused state, the device-side transmitter/receiver control unit 16 of the device-side transmitter/receiver 91 updates the device-side connection information management unit 17. For example, as illustrated in
The device-side transmitter/receiver control unit 16 adds the data transmission/reception unit information and transmits a connection OK between the transmitters/receivers to the host-side transmitter/receiver 93 (S114).
The host-side transmitter/receiver control unit 36 updates the information of the host-side connection information management unit 37 on the basis of the connection OK between the transmitters/receivers from the device-side transmitter/receiver control unit 16. For example, as illustrated in
The host-side data transmission/reception unit 33 and the device-side data transmission/reception unit 13 establish a connection on the basis of the information of the host-side connection information management unit 37 and the device-side connection information management unit 17, respectively (S115). Here, a connection may be established using any method, and for example, transmission control protocol (TCP) is used to establish a TCP connection, security architecture for Internet protocol (IPsec) is used to establish an IPsec connection, UDP Socket is used to establish a UDP socket and exchange a test packet, and the like.
The device-side transmitter/receiver control unit 16 updates the DS status management unit 18 when the connection is established (S116). In the present embodiment, the connection of the USB port number #3 has been established, and thus, a status of the USB port number #3 is updated to “connection established” as illustrated in
The host-side transmitter/receiver control unit 36 transmits a connection establishment OK notification to the transmitter/receiver instruction unit 52 of the orchestrator 95 when the connection is established (S117).
Upon receiving the connection establishment OK notification, the transmitter/receiver instruction unit 52 of the orchestrator 95 notifies the connection request acceptance unit 51 that the connection has been completed. The connection request acceptance unit 51 of the orchestrator 95 gives a notification of a USB port connection request OK in response to a connection request from the user, or the like (S118).
(3) Device Connection Sequence
The device connection sequence will be described with reference to
The USB device 92 is connected to the USB port 11 of the device-side transmitter/receiver 91 (S131).
Upon detecting the connection of the USB device 92, the DS controller 15 of the device-side transmitter/receiver 91 refers to the DS status management unit 18, and if the status of the USB port is connection established, controls the DS 12 and starts power supply. Here, in a case where the connection is not established, the power supply is not performed.
Link training and port configuration are performed between the USB device 92 and the device-side transmitter/receiver 91 (S132), for example, in accordance with USB 3.2 Revision 1.0 7.5 Link Training and Status State Machine (LTSSM).
When the port configuration is completed and the USB device 92 is put into a default state, the DS controller 15 of the device-side transmitter/receiver 91 notifies the device-side transmitter/receiver control unit 16 of completion of the USB device connection of the USB port 11.
The device-side transmitter/receiver 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 transmission/reception unit information of the port number to which the USB device 92 is connected (S133). For example, in a case where the USB device 92 is connected to the USB port number #3, the USB device connection completion notification is transmitted to the IP address “192.168.1.12” described in the connection destination control transmission/reception unit information illustrated in
The host-side transmitter/receiver control unit 36 refers to the host-side connection information management unit 37 to derive the corresponding hub side port number from the connection destination transmitter/receiver information and the connection destination transmitter/receiver port number information described in the received USB device connection completion notification and notifies the hub controller 43 of change in a state of the hub side port using the derived hub side port number. For example, as illustrated in
The hub controller 43 controls the hub 41 to start bus enumeration with the USB host 96 by being triggered by notification of the change in the state of the hub side port. The USB host 96 and the hub 41 perform communication in accordance with content described in USB 3.2 Revision 1.0 9.1.2 Bus Enumeration. A method for transmitting a packet of a protocol layer in the USB to be exchanged between the USB host 96 and the USB device 92 will be described later.
The rest of the description is identical to section 5 and subsequent sections of USB 3.2 Revision 1.0 9.1.2 Bus Enumeration.
An example of a method for transmitting a packet of a protocol layer in a USB will be described with reference to
The DS 12 receives the USB packet from the USB device 92 (S211). Link commands of the link layer are exchanged between the USB device 92 and the device-side transmitter/receiver 91. The DS 12 passes the USB packet obtained by performing the link layer processing to the data transmission/reception unit 13 (S212).
The data transmission/reception unit 13 transmits the transferred USB packet to the corresponding data transmission/reception unit 33 with which a connection has been established by a designated transmission method (IP in this example) (S213).
Upon receiving the data, the data transmission/reception unit 33 divides DATA and DP Header and passes the divided data and DP Header to the hub side port 42 (S214). In this event, the data transmission/reception unit 33 exchanges the link commands of the link layer with the device-side transmitter/receiver 91. The hub 41 transfers data to the USB host 96 (S215). Transfer operation of the hub side port 42 #1→the hub 41→the US 32→the USB host 96 is the same as operation of the normal hub.
The US 32 receives the USB packet from the USB host 96 (S221). Here, the transfer operation of the USB host 96→US 32→the hub 41→the hub side port 42 #1 is the same as operation of the normal hub, but it should be noted that route information to be transmitted to the hub side port 42 #1 is set in a root string of ACK TP. In other words, the set information is not the port number of the device-side transmitter/receiver 91.
The hub side port 42 #1 passes the USB packet to the corresponding data transmission/reception unit 33 (S222). The data transmission/reception unit 33 transmits the transferred USB packet to the corresponding data transmission/reception unit 13 with which a connection has been established by a designated transmission method (IP in this example) (S223).
Upon receiving the data, the data transmission/reception unit 13 passes the data as a transaction packet to the DS 12 (S224). The DS 12 transfers the data to the USB device 92 (S225). Here, transfer operation of the DS 12 #3→the USB device 92 is the same as operation of the DS of the normal hub.
An example of a method for transmitting a packet of a protocol layer in a USB will be described with reference to
The US 32 receives a USB packet from the USB host 96 (S311). Link commands of the link layer are exchanged in the device-side transmitter/receiver 91. Here, transfer operation of the USB host 96→the US 32→the hub 41→the hub side port 42 #1 is the same as operation of the normal hub. However, it should be noted that route information to be transmitted to the hub side port 42 #1 is set in a root string of ACK TP. In other words, the set information is not the port number of the device-side transmitter/receiver 91.
The data transmission/reception unit 33 transmits the transferred USB packet to the corresponding data transmission/reception unit 13 with which a connection has been established by a designated transmission method (IP in this example) (S312).
Upon receiving the data, the data transmission/reception unit 13 divides the DATA and the DP Header and passes the data to the DS 12 #3 (S313). The DS 12 transfers the data to the USB device 92 (S314). In this event, link commands of the link layer are exchanged in the device-side transmitter/receiver 91. Here, transfer operation of the DS 12 #3→the USB device 92 is the same as operation of the DS 12 of the normal hub.
The data transmission/reception unit 13 transmits the transferred USB packet to the corresponding data transmission/reception unit 33 with which a connection has been established by a designated transmission method (IP in this example) (S323).
Upon receiving the data, the data transmission/reception unit 33 passes the data to the hub side port 42 as a transaction packet (S324). Transfer operation of the hub side port 42 #1→the hub 41→the US 32→the USB host 96 is the same as operation of the normal hub.
The hub side port 42 passes the USB packet transferred from the hub 41 to the data transmission/reception unit 33 as it is. The USB packet includes a USB data packet, a USB header packet, and a USB transaction packet.
The data transmission/reception unit 33 sequentially performs payload generation processing, UDP transmission processing, and IP transmission processing. In the payload generation processing, the payload to be passed to the UDP transmission processing is generated by distinguishing among the USB data packet, the USB header packet, and the USB transaction packet. In the UDP transmission processing and the IP transmission processing, normal UDP transmission processing and IP transmission processing are performed.
The data transmission/reception unit 13 sequentially performs payload separation processing, UDP reception processing, and IP reception processing. In the payload separation processing, the USB data packet, the USB header packet, and the USB transaction packet are separated. In the UDP reception processing and the IP reception processing, normal UDP reception processing and IP processing are performed.
The DS 12 separates the USB data packet, the USB header packet, and the USB transaction packet. The DS 12 assigns CRC-16 and LCW to an SB header packet and the USB transaction packet and performs header packet buffer for retransmission when a packet loss occurs in the link layer. The DS 12 performs link layer processing and physical layer processing on the USB data packet and the header packet. As a result of this, the OUT transaction is completed.
The DS 12 performs physical layer processing and link layer processing. The DS 12 performs confirmation processing of the CRC-16 and the LCW, performs header packet buffer and generates a USB header packet and a USB transaction packet. Meanwhile, the DS 12 generates a USB data packet. The data transmission/reception unit 13 sequentially performs payload generation processing, UDP transmission processing, and IP transmission processing on each of these packets.
The data transmission/reception unit 33 sequentially performs IP reception processing, UDP reception processing, and payload separation processing. As a result, the USB data packet, the USB header packet, and the USB transaction packet are separated. The hub side port 42 passes each packet transferred from the data transmission/reception unit 33 to the hub 41 as it is. As a result of this, the IN transaction is completed.
The present disclosure is not limited to the modes described in the present embodiment.
The present disclosure can be applied to information communication.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP2021/006111 | 2/18/2021 | WO |
