TW201824838A - Synchronous transmission device and synchronous transmission method - Google Patents

Abstract

A synchronous transmission device includes a first communication port, a first bus instance and a second bus instance. The first communication port is connected to a first endpoint and a second endpoint. The first bus instance is configured to perform a first data transmission with the first endpoint according to a first node of a first schedule list. The first node of the first schedule list is corresponding to the first endpoint, and the first bus instance is disposed according to the first communication port. When the first data transmission is performed, the first bus instance is further configured to determine whether the second bus instance is idle. When the second bus instance is determined to be idle, the first bus instance controls the second bus instance to perform a second data transmission with the second endpoint according to a second node of the first schedule list. The second node of the first schedule list is corresponding to the second endpoint.

Description

 Synchronous transmission device and synchronous transmission method  

This case is related to a synchronous transmission device.

For multiple endpoints connected to the same communication port, when data is transmitted, the data transmission of the endpoint is usually performed in sequence according to the schedule list. That is to say, when a data transmission is completed, the next data transmission can be started, which makes the efficiency of data transmission difficult to improve.

One aspect of the present disclosure is directed to a synchronous transmission apparatus including a first communication port, a first bus instance, and a second bus item. The first communication port connects the first endpoint (Endpoint) with the second endpoint. The first bus line item is configured to perform first data transmission with the first end point according to the first node of the first schedule list. The first node of the first time-history list corresponds to the first end point, and the first bus line item corresponds to the first communication port setting. When the first data transmission is performed, the first bus line item is further used to judge whether the second bus line item is idle. When it is determined that the second busbar item is idle, the first busbar item controls the second busbar item according to the second node of the first time-history list to perform the second data transmission with the second endpoint. The second node of the first time history list corresponds to the second end point.

Another aspect of the present disclosure is directed to a synchronous transmission method that includes the following steps. The first data transmission with the first endpoint is performed according to the first node of the first time schedule by the first bus item. The first node of the first time history list corresponds to the first endpoint. With the first bus line item, when the first data transmission is performed, it is determined whether the second bus line item is idle. With the first busbar item, when it is determined that the second busbar item is idle, the second busbar item is controlled according to the second node of the first time-history list to perform second data transmission with the second endpoint. The second node of the first time-history list corresponds to the second end point, the first communication port is connected to the first end point and the second end point, and the first bus bar item corresponds to the first communication port setting.

In summary, when an end point data transmission is performed, the synchronous transmission device can use the idle bus line item to perform data transmission with another end point according to the time-history list, thereby achieving the effect of synchronous transmission, thereby improving data transmission. effectiveness.

The above description will be described in detail in the following embodiments, and further explanation of the technical solutions of the present disclosure is provided.

100‧‧‧Synchronous transmission device

110‧‧‧First Busbar Project

111A, 111B‧‧‧First Scheduler

112A, 112B‧‧‧ first direct memory access unit

113A, 113B‧‧‧ first agreement unit

120‧‧‧Second busbar project

121A, 121B‧‧‧Second Scheduler

122A, 122B‧‧‧Second direct memory access unit

123A, 123B‧‧‧Second Agreement Unit

130‧‧‧First Communication埠

131‧‧‧Links

132‧‧‧root

140‧‧‧Second Communications埠

141‧‧‧ Linkage

142‧‧‧root

150‧‧‧ memory

151‧‧‧ Firmware

160‧‧‧ Arbitration Unit

170‧‧‧ hub

171‧‧‧ first endpoint

172‧‧‧second endpoint

180‧‧‧ hub

181‧‧‧ third endpoint

182‧‧‧ fourth endpoint

190‧‧‧Central Processing Unit

200‧‧‧First time schedule list

210, 220, 230, 240‧‧‧ nodes

300‧‧‧second time schedule list

310, 320, 330, 340‧‧‧ nodes

400‧‧‧Synchronous transmission method

S401~S404‧‧‧Steps

The above and other objects, features, advantages and embodiments of the present disclosure will become more apparent and understood. 2 is a schematic diagram of a first time-history list according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a second time-history list according to an embodiment of the present invention; and FIG. 4 is a first embodiment according to the present invention. A flow chart of a synchronous transmission method is illustrated.

When an element is referred to as being "connected" or "coupled" to another element, it can be either directly connected or coupled to the other element or an additional element. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, no additional element is present.

The terms “first”, “second”, etc. used in this document are not specifically meant to refer to the order or order, nor are they used to limit the case, but merely to distinguish between components or operations described in the same technical terms. .

Please refer to FIG. 1 , which is a schematic diagram of a synchronous transmission device 100 according to an embodiment of the present disclosure. The synchronous transmission device 100 includes a first bus instance 110, a second bus item 120, an arbitration unit 160, a first communication port 130, and a second communication port 140. The first bus bar item 110 corresponds to the first communication port 130, and the second bus bar item 120 corresponds to the second communication port 140.

The number of the first bus bar item 110, the second bus bar item 120, the first communication port 130, and the second communication port 140 shown in FIG. 1 is only an example, and the synchronous transmission device 100 may include other numbers of bus bar items and Communication 埠. In an embodiment, the synchronous transmission device 100 includes a plurality of communication ports and corresponding plurality of bus bar items, and the number of communication ports is the same as the number of bus bar items.

In an embodiment, the first bus bar item 110 includes a first scheduler 111A, 111B, a first direct memory access (DMA) unit 112A, 112B, and a first protocol unit 113A, 113B. The first direct memory access unit 112A is connected to the first protocol unit 113A, and the first direct memory access unit 112B is connected to the first protocol unit 113B. The second bus bar item 120 includes second schedulers 121A, 121B, second direct memory access units 122A, 122B, and second protocol units 123A, 123B. The second direct memory access unit 122A is connected to the second protocol unit 123A, and the second direct memory access unit 122B is connected to the second protocol unit 123B.

In one embodiment, the first scheduler 111A may be an output scheduler, the first scheduler 111B may be an input scheduler, and the first direct memory access unit 112A may be an output direct memory access engine. (DMA engine), the first direct memory access unit 112B may be an input direct memory access engine, the first protocol unit 113A may be a transfer protocol unit, and the first protocol unit 113B may be a receive protocol unit. Similarly, the second scheduler 121A may be an output scheduler, the second scheduler 121B may be an input scheduler, the second direct memory access unit 122A may be an output direct memory access engine, and second The direct memory access unit 122B may be an input direct memory access engine, the second protocol unit 123A may be a transfer protocol unit, and the second protocol unit 123B may be a receive protocol unit.

In one embodiment, the first schedulers 111A, 111B, the first direct memory access units 112A, 112B, the second schedulers 121A, 121B, and the second direct memory access units 122A, 122B may be expanded. The Extensible Host Controller Interface (xHCI) specification operates. The first protocol unit 113A, 113B, the second protocol unit 123A, 123B, and the arbitration unit 160 can be in accordance with the Universal Serial Bus protocol (USB 3.1 protocol). ) Standard operation. In an embodiment, the arbitration unit 160 can be an arbitrator.

In one embodiment, the first communication port 130 includes a link port 131 and a root port 132, and the second port 140 includes a link node 141 and a root port 142. The links 、131, 141 are located in the data link layer, and the roots 132, 142 are located in the physical layer (Physical layer). The root port 132 of the first communication port 130 is connected to the first end point 171 and the second end point 172 through the hub 170, and the root port 142 of the second communication port 140 is connected to the third end point 181 and the fourth end through the hub 180. Point 182. The first endpoint 171 and the second endpoint 172 may be the same or different devices, and the third endpoint 181 and the fourth endpoint 182 may be the same or different devices. In one embodiment, the hubs 170, 180 may be USB 3.1 hubs, and the first endpoint 171, the second endpoint 172, the third endpoint 181, and the fourth endpoint 182 may be USB 3.1 devices, USB 3.0 devices.

Hereinafter, the synchronous transmission device 100 outputs the data to the first end point 171 and the second end point 172 as an example for description. Please refer to Figure 1 and Figure 2. FIG. 2 is a schematic diagram of a first time schedule list 200 according to an embodiment of the present disclosure. The first time-history list 200 includes a first node 210, a second node 220, a third node 230, and a fourth node 240, where the first node 210 and the third node 230 correspond to the first endpoint 171, and the second node 220 The four nodes 240 correspond to the second endpoint 172, that is, the adjacent two nodes in the first schedule entry 200 respectively correspond to different endpoints. In an embodiment, the first node 210 and the third node 230 may represent communication and/or actions with the first endpoint 171. For example, the first node 210 of the first schedule 200 may indicate that the data is transmitted to the first node. An endpoint 171 (eg, a USB 3.1 device, a USB 3.0 device), the second node 220 of the first schedule 200 can represent the transfer of data to the second endpoint 172 (eg, a USB 3.1 device, a USB 3.0 device), but the disclosure The content is not limited to this. In one embodiment, the firmware 151 is stored in the memory 150 (for example, a program random access memory (Prgram random access memory)), and the central processing unit (CPU) 190 executes the firmware 151 to Two nodes corresponding to the first endpoint 171 and the second endpoint 172 are arranged as neighboring nodes to generate a first schedule entry 200. As shown in FIG. 1, the first endpoint 171 and the second endpoint 172 correspond to different connection paths.

In another embodiment, the first communication port 130 is connected to a plurality of endpoints (including but not limited to the first endpoint 171 and the second endpoint 172), and the central processing unit 190 executes the firmware 151 to generate the firmware according to the endpoints. The first time schedule list 200. In one embodiment, central processing unit 190 executes firmware 151 to arrange two nodes, respectively, corresponding to some of the endpoints as neighboring nodes to generate first time-history list 200.

Please refer to Figure 4. FIG. 4 is a flow chart of a synchronous transmission method 400 according to an embodiment of the present disclosure. The synchronous transmission method 400 has a plurality of steps S401 to S404 which are applicable to the synchronous transmission device 100 as shown in FIG. 1. The steps mentioned in the above embodiments can be adjusted according to actual needs, and can be performed simultaneously or partially simultaneously, unless otherwise specified.

In step S401, the first bus item 110 performs the first data transmission with the first endpoint 171 according to the first node 210 of the first schedule entry 200, that is, transmits the first data to the first endpoint 171. In an embodiment, the first scheduler 111A is configured to control the first direct memory access unit 112A to acquire data from a memory (not shown) according to the first node 210 of the first schedule 200, and control the first A protocol unit 113A processes the data according to the host-side transfer protocol as a packet to transmit to the first endpoint 171 through the arbitration unit 160 and the first communication port 130, and completes the first data transmission with the first endpoint 171.

When the first data transmission is performed, the first bus line item 110 determines whether the second bus line item 120 is idle (step S402). When it is determined that the second bus bar item 120 is idle, the first bus bar item 110 controls the second bus bar item 120 according to the second node 220 of the first time schedule list 200 to perform second data transmission with the second end point 172 ( Step S403). On the other hand, if it is determined that the second bus bar item 120 is not idle, the first bus bar item 110 does not use the second bus bar item 120 for the second data transmission, that is, ends the synchronous transmission method (step S404). In one embodiment, the first scheduler 111A determines whether the second direct memory access unit 122A is idle. When it is determined that the second direct memory access unit 122A is idle, the second direct memory access unit 122A controls the second direct memory access unit 122A to acquire data from the memory (not shown) according to the second node 220 of the first time history list 200, and controls the first The second protocol unit 123A processes the above data into a packet according to the host-side transfer protocol to transmit to the second endpoint 172 through the arbitration unit 160 and the first communication port 130, and completes the second data transmission with the second endpoint 172. The case where the synchronous transmission device 100 receives the data from the first endpoint 171 and the second endpoint 172 is also similar to the above implementation manner, and the description thereof will not be repeated here. Similarly, the data transmission of the third node 230 and the fourth node 240 of the first time schedule 200 may also utilize the idle second bus item 120 to achieve synchronous transmission, which is not repeated herein.

When the first data transmission with the first endpoint 171 is performed, the first bus line item 110 can perform the second data transmission with the second endpoint 172 by using the idle second bus line item 120 to achieve the effect of synchronous transmission. Thus, the first data transmission can be transmitted at the highest speed of the first endpoint 171, and the second data transmission can be transmitted at the highest speed of the second endpoint 172. In one embodiment, the hub 170 is a USB 3.1 hub, and the first endpoint 171 and the second endpoint 172 are both USB 3.0 devices, so the speed of the first data transmission can reach 5 G bits/s, and the speed of the second data transmission. Can reach 5G bits/s.

In another embodiment, the second busbar item 120 can also use the idle first busbar item 110 to perform data transmission of the third endpoint 181 and the fourth endpoint 182 to achieve the effect of synchronous transmission.

The following describes an example in which the synchronous transmission device 100 outputs data to the third terminal 181 and the fourth terminal 182 as an example. Please refer to Figures 1 and 3. FIG. 3 is a schematic diagram of a second time schedule list 300 according to an embodiment of the present disclosure. The second time-history list 300 includes a first node 310, a second node 320, a third node 330, and a fourth node 340, where the first node 310 and the third node 330 correspond to the third endpoint 181, and the second node 320 The four nodes 340 correspond to the fourth endpoint 182, that is, the adjacent two nodes in the second schedule 300 correspond to different endpoints respectively. In an embodiment, the first node 310 and the third node 330 may represent communication and/or actions with the third endpoint 181. For example, the first node 310 of the second schedule 300 may indicate that the data is transmitted to the first node 310. An endpoint 171 (eg, a USB 3.1 device, a USB 3.0 device), the second node 320 of the second schedule 300 can represent the transfer of data to the fourth endpoint 182 (eg, a USB 3.1 device, a USB 3.0 device), but the disclosure The content is not limited to this. In an embodiment, the central processing unit 190 executes the firmware 151 to arrange two nodes corresponding to the third endpoint 181 and the fourth endpoint 182 as adjacent nodes to generate the second schedule list 300. As shown in FIG. 1, the third endpoint 181 and the fourth endpoint 182 correspond to different connection paths.

In another embodiment, the second communication port 140 is connected to a plurality of endpoints (including but not limited to the third endpoint 181 and the fourth endpoint 182), and the central processing unit 190 executes the firmware 151 to generate the firmware according to the endpoints. The second time schedule list 300. In one embodiment, the isochronous transfer device 100 executes the firmware 151 to arrange two nodes respectively corresponding to the two of the endpoints as neighboring nodes to generate the second schedule list 300.

In an embodiment, the second bus item 120 performs the third data transmission with the third endpoint 181 according to the first node 310 of the second schedule 300, that is, transmits the third data to the third endpoint 181. . In an embodiment, the second scheduler 121A is configured to control the second direct memory access unit 122A to acquire data from a memory (not shown) according to the first node 310 of the second schedule 300, and control the first The second protocol unit 123A processes the above data into a packet according to the host-side transfer protocol to transmit to the third endpoint 181 through the arbitration unit 160 and the second communication port 140, and completes the third data transmission with the third endpoint 181.

When the third data transmission is performed, the second bus line item 120 determines whether the first bus line item 110 is idle. When it is determined that the first bus bar item 110 is idle, the second bus bar item 120 controls the first bus bar item 110 according to the second node 320 of the second time schedule list 300 to perform fourth data transmission with the fourth end point 182. On the other hand, if it is determined that the first busbar item 110 is not idle, the second busbar item 120 does not use the first busbar item 110 for fourth data transmission. In an embodiment, when the third data transmission is performed, the second scheduler 121A determines whether the first direct memory access unit 112A is idle. When it is determined that the first direct memory access unit 112A is idle, the second direct memory access unit 112A controls the first direct memory access unit 112A to acquire data from the memory (not shown) according to the second node 320 of the second time history list 300, and controls the first A protocol unit 113A processes the data according to the host-side transfer protocol as a packet to transmit to the fourth endpoint 182 through the arbitration unit 160 and the second communication port 140, and completes the fourth data transmission with the fourth endpoint 182. The case where the synchronous transmission device 100 receives the data from the third endpoint 181 and the fourth endpoint 182 is also similar to the above implementation manner, and the description thereof will not be repeated here. Similarly, the data transmission of the third node 330 and the fourth node 340 of the second schedule 300 can also utilize the idle first bus item 110 to achieve synchronous transmission, which will not be repeated here.

In this way, when the third data transmission with the third endpoint 181 is performed, the second bus line item 120 can perform the fourth data transmission with the fourth endpoint 182 by using the idle first bus line item 110 to achieve synchronization. The effect of the transmission, so the third data transmission can be transmitted at the highest speed of the third endpoint 181, and the fourth data transmission can be transmitted at the highest speed of the fourth endpoint 182. In one embodiment, the hub 180 is a USB 3.1 hub, and the third endpoint 181 and the fourth endpoint 182 are both USB 3.0 devices, so the third data transmission speed can reach 5G bits/s, and the fourth data transmission speed Can reach 5G bits/s.

In summary, when the data transmission of an endpoint is performed, the synchronous transmission device 100 can use the idle bus line item to perform data transmission with another endpoint according to the time-history list, thereby achieving the effect of synchronous transmission, thereby improving data transmission. s efficiency.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present case. Anyone skilled in the art can make various changes and refinements without departing from the spirit and scope of the case. Therefore, the scope of protection of this case is considered. The scope defined in the patent application is subject to change.

Claims (10)

 A synchronous transmission device includes: a first communication port connecting a first end point and a second end point; and a first bus bar item for performing a first node according to one of the first time history lists a first data transmission of the first endpoint, wherein the first node of the first schedule includes a first endpoint, the first busbar item corresponds to a first communication port setting; and a second sinking stream a row item, wherein the first bus line item is further used to determine whether the second bus line item is idle when the first data transmission is performed, and when determining that the second bus line item is idle, according to the first time schedule A second node of the list controls the second bus item to perform a second data transmission with one of the second endpoints, the second node of the first schedule list corresponding to the second endpoint.    The synchronous transmission device of claim 1, wherein the first bus bar item comprises: a first direct memory access unit; a first protocol unit connected to the first direct memory access unit; and a first a scheduler for controlling the first direct memory access unit and the first protocol unit to perform the first data transmission with the first endpoint according to the first node of the first schedule list.    The synchronous transmission device of claim 2, wherein the second bus bar item comprises: a second direct memory access unit; and a second protocol unit connected to the second direct memory access unit, wherein When the first data transmission is performed, the first scheduler is further configured to determine whether the second direct memory access unit is idle, and when determining that the second direct memory access unit is idle, according to the first time The second node of the process list controls the second direct memory access unit and the second protocol unit to perform the second data transmission with the second endpoint.    The synchronous transmission device of claim 1, wherein the first communication port is connected to a plurality of endpoints, the endpoints including the first endpoint and the second endpoint corresponding to different connection paths, the synchronization transmission device A firmware generates the first schedule list based on the endpoints.    The synchronization transmission device of claim 4, wherein the firmware arranges two nodes corresponding to the two end points of the endpoints as neighboring nodes to generate the first time history list, wherein the two nodes correspond to different Connection path.    The synchronous transmission device of claim 1, further comprising: a second communication port, connecting a third endpoint and a fourth endpoint, wherein the second busbar item corresponds to the second communication port setting, the The second bus line item is further configured to perform a third data transmission with one of the third end points according to one of the second time-history lists, wherein the first node of the second time-history list corresponds to the third node An endpoint, when the third data transmission is performed, the second busbar item is further configured to determine whether the first busbar item is idle, and when determining that the first busbar item is idle, according to the second schedule list A second node controls the first busbar item to perform a fourth data transmission with one of the fourth endpoints, the second node of the second schedule list corresponding to the fourth endpoint.    The synchronous transmission device of claim 6, wherein the second busbar item further comprises: a second scheduler, configured to control the second direct memory storage according to the first node of the second schedule list And the second protocol unit is taken to perform the third data transmission with the third endpoint.    The synchronous transmission device of claim 7, wherein when the third data transmission is performed, the second scheduler is further configured to determine whether the first direct memory access unit is idle, and when determining the first direct When the memory access unit is idle, the second node according to the second time-history list controls the first direct memory access unit and the first protocol unit to perform the fourth data transmission with the fourth endpoint .    A synchronous transmission method includes: performing, by a first bus line item, a first data transmission with a first node according to a first time history list, wherein the first time history list is The first node corresponds to the first end point; by the first bus line item, when the first data transmission is performed, determining whether a second bus line item is idle; and by using the first bus line item, When it is determined that the second bus line item is idle, the second bus node controls the second bus line item according to one of the first time schedule lists to perform second data transmission with one of the second end points, wherein the first time The second node of the process list corresponds to the second endpoint, and a first communication port connects the first endpoint to the second endpoint, and the first busbar item corresponds to the first communication port setting.    The synchronous transmission method of claim 9, further comprising: arranging, by a firmware, two nodes corresponding to the two ends of the plurality of endpoints as adjacent nodes to generate the first time history list, wherein the The first communication port connects the endpoints, and the endpoints include the first endpoint and the second endpoint, and the two endpoints correspond to different connection paths.