JP5932571B2 - Transfer control device, transfer control method, and transfer control program - Google Patents

Description

  The present invention relates to a transfer control device, a transfer control method, and a transfer control program. For example, the present invention relates to a transfer control device, a transfer control method, and a transfer control program that perform transfer by dividing data to be transferred into a plurality of data strings.

  Patent Document 1 discloses a technology related to a USB host system for executing data transfer by USB (Universal Serial Bus) at high speed. The USB host system according to Patent Document 1 includes a CPU (Central Processing Unit) memory and a transfer memory inside the USB host controller. The USB host controller stores data from the USB device in the transfer memory in accordance with the transfer request. In accordance with the control program, the CPU performs data transfer from the transfer memory to the CPU memory after the transfer is completed.

JP 2007-249938 A

  Here, when a large amount of data is bulk-transferred between the host controller and the device device, data transfer is performed for each transfer unit such as a plurality of packets. However, the data transfer may be interrupted by a request from the CPU. Here, when the transfer of the first half of the plurality of packets is normally completed and the second half of the packets is not yet transferred, the packet is not retransmitted because the transfer has not failed in units of packets. On the other hand, the transfer has not been completed for the large amount of data that is the original transfer target. Therefore, when resuming the interrupted data transfer, if the position of the packet that has been transferred last is known, for example, the transfer can be restarted from the packet immediately after the transferred packet. Such a data transfer halfway situation is usually managed in the host controller.

  However, when the midway situation is managed only within the host controller, there is a problem that information on the midway situation cannot be utilized from the outside such as a driver. In particular, in USB 3.0, this problem becomes apparent as bulk transfer can be performed in parallel by a plurality of streams. Patent Document 1 described above does not disclose means for solving such a problem.

  Other problems and novel features will become apparent from the description of the specification and the accompanying drawings.

  According to one embodiment, the transfer control device notifies the transfer progress information indicating the transfer progress status in each of the plurality of data strings divided from the transfer target data to the outside.

  According to another embodiment, the transfer control device outputs transferred information based on the number of transferred packets at a predetermined timing to the outside during transfer of transfer target data.

  According to the embodiment, it is possible to flexibly cope with various needs related to data to be transferred by utilizing the intermediate state of data transfer outside the transfer control device.

1 is a block diagram showing a configuration of a transfer control device according to a first exemplary embodiment; 3 is a flowchart showing a flow of a transfer control process according to the first embodiment. It is a block diagram which shows the structure of the USB host controller concerning this Embodiment 2. FIG. It is a figure for demonstrating the control area | region of the stream concerning this Embodiment 2. FIG. It is a sequence diagram explaining the flow of the registration process (at the time of transmission) of the transfer intermediate data concerning this Embodiment 2. FIG. It is a sequence diagram explaining the flow of the update process (at the time of transmission) of the transfer intermediate data concerning this Embodiment 2. FIG. 10 is a sequence diagram for explaining a flow of transfer intermediate data registration processing (during reception) according to the second exemplary embodiment; It is a sequence diagram explaining the flow at the time of the transfer stop command concerning this Embodiment 2. FIG. It is a block diagram which shows the structure of the USB host controller concerning this Embodiment 3. FIG. FIG. 10 is a sequence diagram for explaining a flow of transfer intermediate data registration processing (during transmission) according to the third exemplary embodiment; It is a sequence diagram explaining the flow at the time of the transfer stop command concerning this Embodiment 4.

<Embodiment 1>
FIG. 1 is a block diagram showing a configuration of the transfer control apparatus 10 according to the first embodiment. The transfer control apparatus 10 performs transfer that is at least one of transmission and reception of transfer target data with the device apparatus 20. Here, it is assumed that the data to be transferred is so large that it cannot be transferred in a single transfer process. Therefore, data transfer is performed between the transfer control device 10 and the device device 20 in units of transfer such as packets. Specifically, between the transfer control device 10 and the device device 20, a plurality of data strings divided from the transfer target data are transferred in units of packets by parallel processing. The parallel processing is, for example, pipeline processing, and actual packet transfer itself may be performed in series.

  The transfer control device 10 includes a transfer processing unit 11 and a notification unit 12. The transfer processing unit 11 transfers a plurality of data strings divided from the transfer target data to the communication partner device. The notification unit 12 notifies the transfer progress information 13 indicating the transfer progress status of each of the plurality of data strings to the outside. Here, the outside is a device other than the device device 20 and is a device connected to the transfer control device 10.

  In other words, the transfer control device 10 according to the first embodiment is a packet that has been transferred at a predetermined timing while a plurality of data strings divided from the transfer target data are being transferred in parallel with the communication partner in packet units. The transferred information based on the number is output to the outside for each data string.

  As a result, even if the transfer of the transfer target data is interrupted, the progress status can be known from the transfer progress information even outside the transfer control device 10, so that the transfer progress information can be used to meet various needs. Flexible processing can be performed.

  FIG. 2 is a flowchart showing the flow of transfer control processing according to the first embodiment. First, the transfer processing unit 11 transfers partial data to the communication partner device 20 (S11). Here, the partial data is a part of a data string divided into a plurality of data to be transferred, for example, a packet. In addition, the transfer processing unit 11 only needs to transmit the partial data to the device apparatus 20 or receive the partial data from the device apparatus 20.

  Next, the notification unit 12 outputs the transfer progress information 13 to the outside (S12). In other words, after completing the transfer of the partial data, the notification unit 12 outputs the transfer progress information 13 indicating the transfer progress status in the data string to which the partial data belongs to each data string at a predetermined timing.

  As described above, according to the first embodiment, it is possible to flexibly cope with various needs related to data to be transferred by utilizing the intermediate state of data transfer outside the transfer control device.

<Embodiment 2>
The second embodiment is an example of the transfer control device 10 of the first embodiment described above. The notification unit according to the second embodiment calculates the amount of data already transferred in the data sequence to which the partial data belongs each time the transfer processing unit completes the transfer of the partial data that is a part of the data sequence. At this timing, the calculated transferred data amount is notified to the outside as transfer progress information. Thus, the transferred data amount is used as the transfer progress information. Then, for example, the amount of transferred data is calculated for each packet transfer. Thereafter, the amount of transferred data at that time is notified to the outside at a predetermined timing. Thus, by calculating for each transfer, the latest transfer progress information can be notified immediately at the timing when notification is required. In addition, by setting the transfer progress information as the data amount, it is possible to easily specify the data position where the retransmission is to be started at the time of retransmission in the data string.

  Furthermore, every time the transfer processing unit completes the transfer of the partial data, the notifying unit according to the second embodiment acquires transfer progress information in the data string to which the partial data belongs from the outside, and the acquired transfer progress information is included in the acquired transfer progress information. The size of the partial data is added to calculate the transferred data amount, and the transferred data amount is notified to the outside as an update value of the transfer progress information. In other words, the transfer control device according to the second embodiment outputs the transferred information to the outside every time the transfer of the packet is completed.

  In this way, since the transfer progress information is notified to the outside every time one packet is transferred, the transfer control device does not need a memory for holding the transfer progress information inside. Therefore, the circuit area in the transfer control device can be suppressed.

  Further, since the latest transfer progress information is sequentially notified to the outside, for example, even when there is a transfer stop request from the CPU or the like, the transfer progress information has already been notified. The latest transfer progress information can be acquired immediately.

  FIG. 3 is a block diagram showing a configuration of the USB host controller 100 according to the second embodiment. The USB host controller 100 performs data transfer with the USB device 400 via the peripheral bus 502. The USB host controller 100 is connected to the driver 200, the system memory 300, and the like via the system bus 501. Then, the USB host controller 100 transmits the transfer target data to the USB device 400 or receives the transfer target data from the USB device 400 in accordance with an instruction from the driver 200 or the like.

  The USB host controller 100 performs data transfer by parallel processing in units of a plurality of streams divided from transfer target data. Here, in the following description, it is assumed that the USB host controller 100 is compatible with USB 3.0. In USB 3.0, it is necessary to handle intermediate information in data transfer called EDTLA (Event Data Transfer Length Accumulator) for each Endpoint. EDTLA indicates the transferred data length. Therefore, EDTLA is an example of the transfer progress information. Further, when handling the Bulk Streaming Protocol, a maximum of 65533 streams can be processed per 1 endpoint. Therefore, the maximum number of EDTLA is 65533.

  The USB host controller 100 is an example of the transfer control device 10 and may be compatible with standards other than USB 3.0. That is, the number of streams and the number of EDTLA described above are merely examples, and are not limited thereto.

  The driver 200 is a functional block realized by a CPU (not shown) reading and executing a driver program. The driver 200 provides an abstract interface for instructing the USB host controller 100 from application software. Therefore, the USB host controller 100 receives a data transfer instruction and a stop instruction from the driver 200.

  The system memory 300 is an example of the above-described external. That is, the system memory 300 is a storage device connected to the USB host controller 100 other than the data transfer partner (USB device 400) of the USB host controller 100. The system memory 300 stores a control area 310 and a stream 320. A stream 320 is each data string divided into a plurality of pieces of data to be transferred. The control area 310 is an area for managing the control information of the stream 320. In the second embodiment, transfer intermediate data 311 described later is stored in the control area 310.

  FIG. 4 is a diagram for explaining a stream control area according to the second embodiment. As described above, in the second embodiment, an area for storing the transfer intermediate data 311 (EDTLLA) is secured in an empty area of the Stream Context in the system memory 300.

  Here, the system memory 300 is a storage device shared by the entire system including the USB host controller 100 and the driver 200. Therefore, by storing the transfer intermediate data 311 in the system memory 300, it is possible to easily access the transfer intermediate data 311 from other than the USB host controller 100 such as the driver 200. Therefore, the transfer intermediate data 311 from the driver 200 can be used for various processes.

  Returning to FIG. 3, the description will be continued. The USB host controller 100 includes a system bus control unit 101, a data buffer 102, a peripheral control unit 103, a data transfer processing unit 104, and a transfer progress status management unit 105. The system bus control unit 101 is connected to the system bus 501 and controls communication between the data buffer 102, the data transfer processing unit 104, the transfer progress status management unit 105, the driver 200, and the system memory 300. The data buffer 102 is a storage device for temporarily holding at least one transfer unit of transfer target data, for example, partial data for one packet. The data buffer 102 can store both or one of partial data to be transmitted to the USB device 400 and partial data received from the USB device 400. The peripheral control unit 103 is connected to the peripheral bus 502 and controls communication between the data buffer 102 and the data transfer processing unit 104 and the USB device 400.

  The data transfer processing unit 104 is an example of the transfer processing unit 11 described above. The data transfer processing unit 104 performs partial data transmission and reception processing using the system bus control unit 101 and the peripheral control unit 103. The transfer progress status management unit 105 is an example of the notification unit 12 described above. The transfer progress status management unit 105 detects that the transfer of the packet in the data transfer processing unit 104 is completed, and generates the transfer intermediate data by calculating the transferred data length in the stream to which the packet belongs. The transfer intermediate data is associated with identification information for specifying the stream and the transferred data length in the stream. The transfer intermediate data is an example of the transfer progress information described above. Therefore, the transfer intermediate data is not limited to the transferred data length. If the position (address) or packet size of the last transferred data in the stream is a fixed length, the transfer intermediate data is the number of transferred packets. It doesn't matter. Alternatively, it may be the ratio of the transferred data length to the data length per stream. Further, the untransferred data length or the ratio of the untransferred data length may be used as the transfer intermediate data.

  Further, the transfer progress status management unit 105 outputs the generated transfer intermediate data to the system memory 300 via the system bus control unit 101 at a predetermined timing. In particular, the transfer progress status management unit 105 stores the transfer intermediate data in the control area 310 in the system memory 300. That is, the transfer progress management unit 105 stores the transfer intermediate data 311 corresponding to each stream in the control area 310 for each stream in the system memory 300 for the transfer intermediate data in each of the plurality of streams. As described above, since the stream is managed for each stream using the free area of the control area, the area can be used efficiently.

  In particular, every time the data transfer processing unit 104 completes packet transfer, the transfer progress status management unit 105 according to the second embodiment acquires transfer intermediate data 311 in a stream to which the packet belongs from the system memory 300, The size of the packet is added to the acquired transfer intermediate data 311 to calculate the transferred data amount, and the transferred data amount is notified to the system memory 300 as an update value of the transfer intermediate data 311.

  When the data transfer processing unit 104 transmits a plurality of streams to the USB device 400, the transfer progress status management unit 105 notifies the system memory 300 of the transmitted data amount in each stream as EDTLA. When the data transfer processing unit 104 receives a plurality of streams from the USB device 400, the transfer progress status management unit 105 notifies the system memory 300 of the received data amount in each stream as EDTLA. Therefore, it can respond to both transmission and reception.

  FIG. 5 is a sequence diagram for explaining a flow of transfer intermediate data registration processing (during transmission) according to the second embodiment. It is assumed that the transfer target data is divided into a plurality of streams by the CPU or the like and stored in the stream 320 of the system memory 300. In addition, it is assumed that a control area 310 corresponding to each stream 320 is secured. However, the transfer intermediate data 311 is not stored in the control area 310 at this time. The USB host controller 100 is assumed to have established a USB connection with the USB device 400.

  First, the driver 200 executes a doorbell ring for the USB host controller 100 (S201). Here, it is assumed that the driver 200 instructs the USB host controller 100 to start data transmission for each stream 320 in the system memory 300.

  Next, the USB host controller 100 executes a Stream Context Read command (S202). That is, the USB host controller 100 tries to read EDTLA from the control area 310 of the system memory 300. However, here, since it is before the start of data transmission, it is not read out.

  Subsequently, the USB host controller 100 performs TRB Fetch on the target stream 320 to which data transmission is performed first (S203). Thereafter, the USB host controller 100 performs USB transfer on the USB device 400 (S204). Here, the data transfer processing unit 104 transmits data of a predetermined size from the head of the target stream to the USB device 400 as one packet.

  Thereafter, the USB host controller 100 calculates EDTLA (S205). That is, the transfer progress status management unit 105 sets the data length of the packet as the EDTLA value after the packet transmission is normally completed. Then, the USB host controller 100 executes the Stream Context Write with EDTLA command (S206). That is, the transfer progress status management unit 105 stores the calculated EDTLA in a predetermined area in the control area 310 corresponding to the stream in the system memory 300.

  As a result, when data transmission is performed for the same stream, the transfer intermediate data that has already been stored is read from the system memory, so that the transfer can be resumed immediately after the transferred data position. Examples thereof will be described below.

  FIG. 6 is a sequence diagram for explaining the flow of transfer intermediate data update processing (during transmission) according to the second embodiment. Subsequent to step S206 in FIG. 5, the driver 200 performs doorbell ring on the USB host controller 100 in the same manner as described above (S211). Here, it is assumed that the instruction is to transmit the next packet to the same stream as in FIG.

  Next, the USB host controller 100 executes a Stream Context Read with EDTLA command (S212). In other words, the transfer progress status management unit 105 reads EDTLA from the control area 310 in the corresponding stream of the system memory 300. At this time, the read EDTLA has already been set with the transferred data length.

  Therefore, the USB host controller 100 performs TRB Fetch on the position immediately after the data length indicated by EDTLA in the same stream 320 as in FIG. 5 (S213). Then, the USB host controller 100 performs USB transfer for the USB device 400 (S214). Here, the data transfer processing unit 104 transmits data of a predetermined size as one packet immediately after the transferred data to the USB device 400 (S214).

  Thereafter, the USB host controller 100 updates EDTLA (S215). That is, the transfer progress status management unit 105 updates the EDTLA by adding the packet size transmitted in step S214 to the EDTLA read in step S212.

  Subsequently, the USB host controller 100 executes a Stream Context Write with EDTLA command (S216). That is, the transfer progress status management unit 105 stores the updated EDTLA in a predetermined area in the control area 310 corresponding to the stream in the system memory 300.

  FIG. 7 is a sequence diagram for explaining the flow of transfer intermediate data registration processing (during reception) according to the second embodiment. As a difference from FIG. 5, it is assumed that the transfer target data is divided into a plurality of streams and held on the USB device 400 side. In addition, it is assumed that the control area 310 and the area of the stream 320 are secured before the data itself is stored in the stream 320 of the system memory 300.

  First, the driver 200 executes Doorbell ring in order to instruct the start of data reception from the USB device 400 (S221). Next, the USB host controller 100 executes steps S222 and S223 in the same manner as steps S202 and S203 in FIG.

  Then, the USB host controller 100 transmits a data transfer request to the USB device 400 (S224). Subsequently, the USB device 400 performs USB transfer to the USB host controller 100 in response to the data transfer request (S225). Then, the USB host controller 100 receives the packet and calculates EDTLA (S226). That is, the transfer progress status management unit 105 sets the data length of the packet as the EDTLA value after the packet reception is completed normally. Then, the USB host controller 100 executes the Stream Context Write with EDTLA command (S227). That is, the transfer progress status management unit 105 stores the calculated EDTLA in a predetermined area in the control area 310 corresponding to the stream in the system memory 300.

  Note that the case of continuous data reception can also be inferred from FIG.

  FIG. 8 is a sequence diagram for explaining a flow at the time of a transfer stop instruction according to the second embodiment. As a premise, it is assumed that the transfer intermediate data 311 has already been stored in the control area 310 of the system memory 300 in advance according to FIG. 5, FIG. 6, or FIG.

  First, the driver 200 executes a Stop Endpoint Command for the USB host controller 100 (S231). Thereby, the USB host controller 100 interrupts the data transfer being executed. Then, the USB host controller 100 notifies Completion to the driver 200 (S232). As a result, the driver 200 recognizes that the instructed data transfer interruption processing has been completed.

  Thereafter, the driver 200 reads Read ALL Stream Context. The EDTLA command is executed (S233). That is, the driver 200 can acquire EDTLA for all streams and perform processing as necessary. For example, the data transfer can be resumed after updating the untransferred data in each stream. In addition, flexible processing can be realized according to various needs.

  As described above, in the second embodiment, the transfer intermediate data 311 is stored not on the memory inside the USB host controller 100 but on the system memory 300. Therefore, the circuit area in the USB host controller 100 can be suppressed. Since the transfer intermediate data 311 is in the system memory 300, when the driver 200 executes the Stop Endpoint Command, the EDTLA field added to the Stream Context on the system memory 300 is read, and the EDTLA fields of all the Streams are read. The value can be grasped.

<Embodiment 3>
The third embodiment is a modification of the USB host controller 100 of the second embodiment described above. The transfer control apparatus according to the third embodiment further includes a storage unit that stores the calculated transferred data amount in association with each data string. Then, each time the transfer processing unit completes the transfer of the partial data, the notifying unit determines the portion of the transferred data amount stored in the storage unit that is associated with the data string to which the partial data belongs. The data size is added and updated, and when the transfer processing unit completes a predetermined number of transfers, each transferred data amount stored in the storage unit is read and notified to the outside as transfer progress information. In other words, the transferred information is updated every time the packet transfer is completed, and the updated transferred information is output to the outside every time a plurality of packet transfers are completed. Thus, for example, every time transfer of two or more packets is completed, transfer progress information is notified to the outside. Therefore, the communication load can be suppressed by reducing the number of external notifications.

  FIG. 9 is a block diagram of the configuration of the USB host controller 100a according to the third embodiment. The USB host controller 100a is different from FIG. 3 in that the transfer progress status management unit 105 is replaced with the transfer progress status management unit 105a and a storage unit 106 is added.

  The storage unit 106 is a storage device that stores the transfer intermediate data 107 that is the calculated transferred data amount in association with each stream. Each time the data transfer processing unit 104 completes the packet transfer, the transfer progress status management unit 105a determines the transfer intermediate data 107 stored in the storage unit 106 that is associated with the stream to which the packet belongs. Update by adding the size of the partial packet. Then, when the data transfer processing unit 104 completes the predetermined number of transfers, the transfer progress status management unit 105a reads the transfer intermediate data 107 associated with each stream stored in the storage unit 106, and transfers the transfer progress. Information is sent to the system memory 300 as information.

  FIG. 10 is a sequence diagram for explaining the flow of transfer intermediate data registration processing (during transmission) according to the third embodiment. It is assumed that the premise is the same as in FIG.

  First, the driver 200 executes Doorbell ring in order to instruct the start of data transmission to the USB device 400 (S301). Next, the USB host controller 100a executes steps S302 and S303 in the same manner as steps S202 and S203 in FIG.

  Then, the USB host controller 100a performs USB transfer for the USB device 400 (S3041). Thereafter, the transfer progress status management unit 105a calculates EDTLA and stores it as transfer intermediate data 107 in the storage unit 106 (S3042). Subsequently, the USB host controller 100a performs USB transfer for the USB device 400 (S3043). That is, the data transfer processing unit 104 transmits the next packet. If the EDTLA in the corresponding stream has already been stored, the transfer progress status management unit 105a reads the EDTLA, adds the data length of the packet, and updates the EDTLA. Thereafter, the transfer progress status management unit 105a stores the updated EDTLA in the storage unit 106 (S3044). Similarly, steps S3045 and S3046 are repeated.

  Thereafter, when the transfer progress management unit 105a detects that steps S3045 and S3046 have been repeated a predetermined number of times, the USB host controller 100a executes a Stream Context Write with EDTLA command (S305). That is, the transfer progress status management unit 105a reads the transfer intermediate data 107 corresponding to each stream from the storage unit 106, and reads each EDTLA read into a predetermined area in the control area 310 corresponding to each stream in the system memory 300. Is stored.

  As a result, the number of notifications from the USB host controller 100a to the system memory 300 can be reduced as compared with the second embodiment.

<Embodiment 4>
The fourth embodiment is a modification of the USB host controller 100 of the second embodiment described above. When the notification unit of the transfer control apparatus according to the fourth embodiment receives an instruction to cancel transfer from the outside, the notifying unit externally uses each transferred data amount calculated immediately before for each of a plurality of data strings as transfer progress information. To notify. In other words, the transfer control device according to the third embodiment updates the transferred information every time the packet transfer is completed, and if the transfer stop instruction is received from the outside, Output to. As described above, the transfer control apparatus according to the fourth embodiment outputs the transfer progress information to the outside only when necessary while calculating the transfer progress information in advance. For example, since the notification from the USB host controller 100a to the system memory 300 is generated for the first time when a transfer cancellation request from a driver or the like is issued, the number of notifications can be further reduced as compared with the third embodiment.

  The configuration of the transfer control apparatus according to the fourth embodiment is the same as that shown in FIG.

  FIG. 11 is a sequence diagram for explaining a flow at the time of a transfer stop instruction according to the fourth embodiment. Here, as in steps S3041 to S3046 of FIG. 10, the update and storage of USB Transfer and EDTLA are repeatedly performed a predetermined number of times (S4011 to S4014). Therefore, the latest transfer intermediate data 107 is already stored in the storage unit 106.

  At this time, the driver 200 executes a Stop Endpoint Command for the USB host controller 100a as in Step S231 of FIG. 8 (S402). As a result, the USB host controller 100a interrupts the data transfer being executed. Then, the USB host controller 100a executes a Write ALL Stream EDTLA command (S403). That is, the transfer progress status management unit 105 a reads EDTLA in all streams from the storage unit 106 and stores it in the control area 310 in each stream of the system memory 300.

  Thereafter, the USB host controller 100a notifies Completion to the driver 200 in the same manner as Step S232 of FIG. 8 (S404). As a result, the driver 200 recognizes that the instructed data transfer interruption processing has been completed. Then, as in step S233 of FIG. 8, the driver 200 reads Read ALL Stream Context. The EDTLA command is executed (S405). Thereby, the same effect as FIG. 8 can be produced.

<Other embodiments>
Furthermore, the present invention is not limited to the above-described embodiments, and various modifications can be made without departing from the gist of the present invention described above. For example, in the above-described embodiment, the present invention has been described as a hardware configuration, but the present invention is not limited to this. The present invention can also realize the processing described above by causing a CPU (Central Processing Unit) to execute a computer program.

  In the above example, the program can be stored and supplied to a computer using various types of non-transitory computer readable media. Non-transitory computer readable media include various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (for example, flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (for example, magneto-optical disks), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, DVD (Digital Versatile Disc), BD (Blu-ray (registered trademark) Disc), semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM ( Random Access Memory)). The program may also be supplied to the computer by various types of transitory computer readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.

Based on the above, a part of the contents described in the embodiment will be described below.
The transfer control program includes a transfer process for transferring a plurality of data strings divided from the transfer target data to a communication partner device device, and transfer progress information indicating a transfer progress status in each of the plurality of data strings. And causing the computer to execute notification processing for notifying the outside. As a result, even if the transfer of the transfer target data is interrupted, the progress status can be known from the transfer progress information even outside the computer, so the transfer progress information can be used to flexibly meet various needs. Processing can be performed.

  As mentioned above, the invention made by the present inventor has been specifically described based on the embodiments. However, the present invention is not limited to the embodiments already described, and various modifications can be made without departing from the scope of the invention. It goes without saying that it is possible.

DESCRIPTION OF SYMBOLS 10 Transfer control apparatus 11 Transfer process part 12 Notification part 13 Transfer progress information 20 Device apparatus 100 USB host controller 100a USB host controller 101 System bus control part 102 Data buffer 103 Peripheral control part 104 Data transfer process part 105 Transfer progress condition management part 105a Transfer status management unit 106 Storage unit 107 Transfer intermediate data 200 Driver 300 System memory 310 Control area 311 Transfer intermediate data 320 Stream 400 USB device 501 System bus 502 Peripheral bus

Claims (9)

A transfer processing unit that transfers a plurality of data strings divided from the transfer target data to and from the communication partner device; and
A notification unit for notifying the transfer progress information indicating the transfer progress in each of the plurality of data strings to the outside;
Equipped with a,
The transfer progress information is a transferred data amount in a data string to which partial data that is a part of the data string belongs,
The notification unit
Each time the transfer processing unit completes the transfer of the partial data, the transfer progress information in the data string to which the partial data belongs is acquired from the outside, and the size of the partial data is added to the acquired transfer progress information, notify the transfer progress information after the addition to the external
Transfer control device. The notification unit
The transfer control device according to claim 1, wherein when an instruction to cancel transfer is received from outside, the transfer control device according to claim 1, which notifies the outside of each transferred data amount calculated immediately before for each of the plurality of data strings as the transfer progress information. . The outside is a storage device connected to the transfer control device other than the communication partner,
2. The notification unit stores the transfer progress information corresponding to each data string in a control area corresponding to each data string in the storage device for transfer progress information in each of the plurality of data strings. The transfer control device described. The transfer control device according to claim 3 , wherein the storage device is a memory shared by a system including the transfer control device. The notification unit
When the transfer processing unit transmits the plurality of data strings to the communication partner device, it notifies the outside of the transmitted data amount in each data string as the transfer progress information,
If the transfer processing unit receives the plurality of data strings from the device apparatus of the communication partner, any one of claims 1 to 4 for notifying the outside received data amount in each data row as the transfer progress information 2. The transfer control device according to item 1. Wherein the plurality of data columns, USB (Universal Serial Bus) transfer control device according to any one of claims 1 to 5, a plurality of streams based on 3.0. While transferring multiple data strings divided from the transfer target data to the communication partner in packet units by parallel processing, transferred information based on the number of packets transferred at a predetermined timing is sent to the outside for each data string. Output ,
The transferred information is a transferred data length for each data string,
Each time the transfer of the packet is completed, the transferred information in the data string to which the packet belongs is acquired from the outside, the size of the packet is added to the acquired transferred information, and the transferred information after the addition is obtained. Output to the outside
Transfer control device. Each time the transfer of the packet is completed, the transferred information is updated,
The transfer control device according to claim 7 , wherein when the transfer stop instruction is received from the outside, the updated information after update is output to the outside. Transfer partial data that is part of the data string divided into multiple parts from the transfer target data to and from the communication partner device,
The transfer progress information indicating the transfer progress status in the data string to which the partial data belongs is output to the outside for each data string ,
The transfer progress information is a transferred data amount in a data string to which partial data that is a part of the data string belongs,
Each time the transfer of the partial data is completed, the transfer progress information in the data string to which the partial data belongs is acquired from the outside, the size of the partial data is added to the acquired transfer progress information, and the transfer after the addition A transfer control method for outputting progress information to the outside .

Images