WO2022142901A1 - Data transmission method and apparatus, readable storage medium, and terminal device - Google Patents

Abstract

A data transmission method and apparatus, a computer readable storage medium, and a terminal device, relating to the technical field of chips. The method comprises: creating a data transmission channel between a host end and a slave end (S501), the data transmission channel comprising a sending task queue, a sending port, and a receiving port; sending a data processing task of a source thread to the sending task queue (S502); reading the data processing task from the sending task queue by means of the sending port, and encapsulating the data processing task into a data packet and sending the data packet to the receiving port (S503); and receiving the data packet by means of the receiving port, and parsing the data processing task from the data packet and sending the data processing task to a destination thread (S504). According to the method, a task queue processing mechanism is introduced into the data transmission channel to implement coordination management between a thread of the host end and a thread of the slave end, such that the processing efficiency for a large number of complex tasks is greatly improved.

Description

A data transmission method, apparatus, readable storage medium and terminal device technical field

The present application belongs to the field of chip technology, and in particular, relates to a data transmission method, an apparatus, a computer-readable storage medium, and a terminal device.

This application claims the priority of the Chinese patent application filed on December 29, 2020 with the application number 202011614094.3 and the invention name is "a data transmission method, device, readable storage medium and terminal device", all of which are The contents are incorporated herein by reference. 

Background technique

With the popularization of various artificial intelligence (AI) chips, AI coprocessor chip solutions have gradually become the main application scenarios of solutions in the field of artificial intelligence. In the prior art, when the cross-platform data transmission between the main processor and the AI co-processor chip is performed, most of them directly call the general USB interface to realize it. However, this method requires complicated coordination and management of the data transmission process, and is inefficient when faced with a large number of complex tasks.

technical solutions

In view of this, the embodiments of the present application provide a data transmission method, an apparatus, a computer-readable storage medium, and a terminal device, so as to solve the problem of low efficiency of the existing data transmission method.

A first aspect of the embodiments of the present application provides a data transmission method, which may include:

Create a data transmission channel between the host and the slave, and the data transmission channel includes a sending task queue, a sending port and a receiving port;

sending the data processing task of the source thread to the sending task queue; the source thread is the data stream output party in the data processing thread of the host side and the data processing thread of the slave side;

Read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port;

The data packet is received through the receiving port, the data processing task is parsed from the data packet and sent to the destination thread; the destination thread is the data processing thread on the host side and the data processing on the slave side The data stream input side in the thread.

Further, creating a data transmission channel between the host and the slave may include:

passing the channel name and channel parameters of the data transmission channel to the channel creation module in the preset channel management component;

Calling the USB endpoint resource management module in the channel management component by the channel creation module to create a USB endpoint logical channel corresponding to the channel name and the channel parameter;

A sending task queue, a sending port and a receiving port corresponding to the logical channel of the USB endpoint are created on the host side and the slave side by the channel creation module.

Further, the data transmission channel is a channel from the host side to the slave side; the channel creation module creates logic with the USB endpoint on the host side and the slave side The sending task queue, sending port and receiving port corresponding to the channel can include:

Create a sending port and a sending task queue corresponding to the sending port on the host side by the channel creation module;

A receive port is created on the slave side by the channel creation module using a preset remote procedure call module.

Further, the data transmission channel is a channel from the slave side to the host side; the channel creation module creates logic with the USB endpoint on the host side and the slave side The sending task queue, sending port and receiving port corresponding to the channel can include:

Using the preset remote procedure call module to create a sending port and a sending task queue corresponding to the sending port on the slave end through the channel creation module;

A receiving port is created on the host side by the channel creation module.

Further, after passing the channel name and channel parameters of the data transmission channel to the channel creation module in the preset channel management component, it may further include:

Call the channel resource management module in the channel management component through the channel creation module to query whether there is a target channel, where the target channel is a data transmission channel corresponding to the channel name and channel parameters;

If the target channel exists, the channel creation process is stopped.

Further, the sending the data processing task of the source thread to the sending task queue may include:

serializing the data processing task to obtain a serialized data processing task;

A new data processing task is formed according to the serialized data processing task, the task type and the pointer of the task queue of the destination thread;

Send the new data processing task to the sending task queue.

Further, the encapsulating the data processing task into a data packet and sending it to the receiving port may include:

Encapsulate the data processing task into a data package according to a preset package format;

If the data length of the data packet is greater than a preset threshold, send the data packet to the receiving port;

If the data length of the data packets is less than or equal to the threshold, a plurality of the data packets are encapsulated into aggregate packets and sent to the receiving port.

A second aspect of the embodiments of the present application provides a data transmission apparatus, which may include various functional modules for implementing any of the foregoing data transmission methods.

A third aspect of the embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, implements the steps of any of the foregoing data transmission methods.

A fourth aspect of the embodiments of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, when the processor executes the computer program Implement the steps of any of the above data transmission methods.

A fifth aspect of the embodiments of the present application provides a computer program product that, when the computer program product runs on a terminal device, causes the terminal device to execute the steps of any of the above data transmission methods.

Compared with the prior art, the embodiments of the present application have the following beneficial effects: the embodiments of the present application create a data transmission channel between the host end and the slave end, and the data transmission channel includes a sending task queue, a sending port, and a receiving port; Send the data processing task of the source thread to the sending task queue; read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port; receiving the data packet through the receiving port, parsing the data processing task from the data packet and sending it to the destination thread. Through the embodiment of the present application, the existing USB interface is further encapsulated as a data transmission channel between the host and the slave, and a task queue processing mechanism is introduced therein to realize the coordination management between the threads of the host and the threads of the slave. , without requiring users to perform complicated control operations, which greatly improves the processing efficiency of a large number of complex tasks.

Description of drawings

Fig. 1 is a schematic diagram of a task queue for inter-thread task communication;

Fig. 2 is the schematic diagram of USB endpoint logic channel;

Fig. 3 is the schematic diagram of the point-to-point channel from the host side to the slave side direction;

4 is a schematic diagram of a channel management component for point-to-point channel management;

FIG. 5 is a flowchart of an embodiment of a data transmission method in an embodiment of the present application;

6 is a schematic diagram of cross-platform data transmission through a data transmission channel;

Fig. 7 is the schematic diagram of group package format;

Fig. 8 is the schematic diagram of polybag;

FIG. 9 is a structural diagram of an embodiment of a data transmission apparatus in an embodiment of the present application;

FIG. 10 is a schematic block diagram of a terminal device in an embodiment of the present application.

Embodiments of the present invention

In this embodiment of the present application, the task queue (denoted as TaskQueue) as shown in FIG. 1 may be used to perform communication between tasks (denoted as Task) between data processing threads (denoted as Node). The TaskQueue internally uses a fixed-size First Input First Output (FIFO) queue to store the Task information between threads. The Task information includes the Task type information and the Task pointer information. In the example shown in Figure 1, the sending threads A and B dynamically apply for Task objects on the heap space, send tasks Task X and Y through the TaskQueue object, and the receiving thread C reads the Tasks from the TaskQueue object in turn and processes them. Indicates that the type information of the Task pointer is agreed, and the Task object is released on the heap space after processing. If the FIFO queue of the TaskQueue is full when the sending thread sends the task, the sending thread will block until the receiving thread removes the Task from the FIFO queue; if the FIFO queue of the TaskQueue is empty when the receiving thread receives the task, the receiving thread will block waiting for the sending thread to send the Task .

In this embodiment of the present application, a USB endpoint (denoted as Endpoint) may be used to perform data communication between the host end (denoted as Host) and the slave end (denoted as Device). Generally, USB supports up to 16 endpoints, and each endpoint can configure the maximum transfer block, transfer direction and transfer mode. Among them, Host is generally an X86 or ARM-based main processor, and Device is generally a device used for a specific purpose, such as an AI coprocessor chip. Figure 2 shows a schematic diagram of the USB endpoint logical channel. The USB endpoint logical channel can be divided into point-to-point channels in two directions (denoted as P2P Channel), that is, the point-to-point channel from Host to Device (denoted as HostàDevice P2P Channel), and the point-to-point channel from Device to Host (denoted as DeviceàHost P2P Channel).

P2P Channel is an application communication channel carried on the logical channel connection of USB endpoints, and uses the transmission characteristics of USB to efficiently transmit user data to the opposite end.

Taking the channel from the Host to the Device direction shown in Figure 3 as an example, the P2P Channel may include:

(1) The TaskQueue of the P2P sending port of the Host is used to receive the Task sending requests of other threads of the Host. The sent Task content includes: the TaskQueue information of the Device, the serialized code stream information of the Task, and the Task type information. The type information is used to inform the Device how to deserialize the received stream information.

(2) The P2P sending port of the Host (referred to as TxChannel) is used to take out the Task from the TaskQueue and send it in packets;

(3) The P2P receiving port of the Device (referred to as RxChannel) is used to receive data packets and unpack them. After unpacking, the receiving TaskQueue and Task type information of the Task are obtained and pushed to the TaskQueue corresponding to the Device.

The P2P Channel in the direction from the Device to the Host is similar, and it is only necessary to exchange the Device and the Host in the foregoing content, which is not repeated in this embodiment of the present application.

In this embodiment of the present application, the P2P Channel can be managed on the Host side through a channel management component (referred to as P2P ChannelWrapper) as shown in FIG. 4 . The P2P ChannelWrapper can specifically include the following modules:

The channel creation module and channel deletion module of H2D (Host to Device) are responsible for the creation and deletion of the P2P Channel from Host to Device;

The channel creation module and channel deletion module of D2H (Device to Host) are used to create and delete the P2P Channel from Device to Host;

The channel resource management module is used to maintain the created P2P Channel resource information and support P2P Channel multiplexing;

The USB endpoint resource management module is used to manage the use of USB endpoint resources, and supports dynamic application and release of USB endpoints in pairs.

Referring to FIG. 5, an embodiment of a data transmission method in this embodiment of the present application may include:

Step S501 , creating a data transmission channel between the host end and the slave end.

In this embodiment of the present application, a P2P Channel may be used as a data transmission channel between the Host and the Device, and a specific creation process thereof may include the following steps:

(1) Pass the channel name and channel parameters of the data transmission channel to be created to the channel creation module in the channel management component.

The channel name and the channel parameters can be set by the user according to the actual situation, and the channel name can be a combination of numbers, letters and symbols. For example, the channel name can be set as: "H2D VideoStream #1", The channel parameters may include specific parameters such as maximum transmission block, transmission direction, and transmission mode. For example, the maximum transmission block in the channel parameters may be set to 1MB, that is, the maximum data block that can be transmitted in the channel is 1MB.

If the data transmission channel to be created is the channel from the Host to the Device direction, the channel name and the channel parameters need to be passed to the H2D channel creation module; if the data transmission channel to be created is the direction from the Device to the Host direction channel, the channel name and the channel parameters need to be passed to the channel creation module of D2H.

(2) The channel creation module invokes the channel resource management module in the channel management component to query whether there is a target channel, where the target channel is a data transmission channel corresponding to the channel name and channel parameters.

For example, if the channel name is: "H2D VideoStream #1", the channel parameter is the maximum transmission block of 1MB, and a channel with the same name exists, and the maximum transmission block of the channel is not less than 1MB, the The channel is determined as the target channel.

If the target channel exists, the channel can be used directly without re-creating a new channel, and the consumption of channel resources can be reduced by multiplexing the existing channel. At this time, the channel resource management module is called to add 1 to the reference count of the target channel, and step (3) is performed; if the target channel does not exist, a new channel needs to be recreated, that is, step (4) is continued. .

(3) Stop the channel creation process, and return the pointer of the sending task queue of the target channel so that it can be directly called when the sending task queue needs to be used later.

(4) Calling the USB endpoint resource management module in the channel management component through the channel creation module to create a USB endpoint logical channel corresponding to the channel name and the channel parameter.

The USB endpoint resource management module can call the general USB interface, and pass specific parameters such as the maximum transmission block, transmission direction and transmission mode in the channel parameters to the API function provided by the USB interface, thereby creating a new USB endpoint logic channel, and name it after the channel name.

If the resource of the USB endpoint is insufficient, a message of channel application failure is returned, and the failure reason can be attached to the message that the resource of the USB endpoint is exhausted; if the resource of the USB endpoint is sufficient, proceed to step (5).

(5) Create a sending task queue, sending port and receiving port corresponding to the USB endpoint logical channel on the Host side and the Device side through the channel creation module.

If the data transmission channel to be created is a channel from the Host to the Device, a sending port and a sending task queue corresponding to the sending port can be created on the Host side through the channel creation module, and the channel creation module can use the preset The remote procedure call module (Remote Procedure Call, RPC) creates a receiving port on the Device side, thereby establishing a data transmission channel from the Host to the Device.

If the data transmission channel to be created is a channel from the Device to the Host direction, the channel creation module can use RPC to create a sending port and a sending task queue corresponding to the sending port on the Device side, and create a module through the channel. Create a receiving port on the Host side to establish a data transmission channel from Device to Host.

Through the process of step S501, a cross-platform data transmission channel can be created between the host end and the slave end, thereby providing a basis for subsequent data transmission.

After the above channel creation process is completed, the channel resource management module can be called to increase the reference count of the newly created data transmission channel by 1, and return the pointer of the created sending task queue so that the sending task queue needs to be used later. call it directly.

Step S502: Send the data processing task of the source thread to the sending task queue.

The source thread is the data stream output party in the data processing thread of the host side and the data processing thread of the slave side; correspondingly, the destination thread is the data processing thread of the host side and the data processing thread of the slave side. The data stream input side in the thread. Taking Figure 6 as an example, the thread A of the Host sends the Task of type TaskX1 and TaskX2 to the thread B of the Device, and sends the Task of the type TaskY to the thread C of the Device, then the thread A is the source thread, and the threads B and C are the destination threads. .

Before data transmission, the source thread can obtain the following information through RPC:

(1) The TaskQueue pointer of the destination thread;

(2) The task type agreement between the source thread and the destination thread. Taking Figure 6 as an example, it can be agreed that TaskType 0 in the TaskQueue sent to thread B represents the serialized code stream of the TaskX1 type, and TaskType 1 represents the TaskX2 type. Serialization code stream; TaskType 0 in the TaskQueue agreed to be sent to thread C represents the serialization code stream of the TaskY type.

After obtaining the above information, the source thread can send the Task data stream. First, according to the task type, serialize the data processing task that needs to be transmitted to obtain the serialized data processing task, or it is called the Task serialization code stream. Then, a new data processing task is formed according to the serialized data processing task, the task type and the TaskQueue pointer of the destination thread, and the new data processing task is sent to the sending task queue.

Step S503: Read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port.

The content read by the sending port includes the Task serialization code stream, the task type and the TaskQueue pointer of the destination thread. After reading these contents, it can be encapsulated into a data packet according to the preset packet format, and the USB can be called. The endpoint driver sends the packet. The specific packet format can be set according to the actual situation. Figure 7 shows a schematic diagram of a packet format. The packet format adds a transmission header including the following content before the Task serialization code stream:

Magic word: used for data transmission header detection;

Data area description: including the length information of the Task serialization code stream, etc.;

Task type: the type identification (id) information of the task, the destination thread deserializes according to the type id of the task;

Destination thread Queue pointer: the TaskQueue pointer of the destination thread;

Number of aggregated packets: the number of packets in the transmission block, P2P Channel supports the aggregation of multiple small data packets to send together, please refer to the following specific instructions for details;

Cyclic Redundancy Check (CRC) information: optional. If CRC check is supported, CRC calculation is performed on the data area of the transmission header or the transmission header + Task serialized code stream to ensure the integrity of data transmission.

Through such a packet format, it is convenient for the receiver to detect the received data packets, and promptly remove the invalid data packets that may appear therein, thereby improving the accuracy of the data.

Preferably, in order to reduce data copying, in this embodiment of the present application, when the user applies for the memory required for task serialization, a buffer with continuous physical addresses can be allocated to the user, and the storage of the transmission header is reserved before the buffer. Space, through such special processing, data copying is not required during the packet transmission process.

After the grouping is completed, if the data length of the data packet is greater than the preset threshold, the data packet can be directly sent to the receiving port without performing the packet aggregation process; if the data length of the data packet is less than or equal to the threshold, the Then, several of the data packets can be encapsulated into one data packet (denoted as a cluster packet) and sent to the receiving port, thereby improving the USB transmission efficiency. Specifically, the sending port can allocate a maximum transmission block buffer supported on the USB endpoint during the initialization phase for packet data transmission, and then periodically read Tasks from the TaskQueue continuously, and group packets into the buffer. If The buffer is full, then call USB send. The threshold may be set according to actual conditions, which is not specifically limited in this embodiment of the present application.

Figure 8 shows the format in which two data packets are encapsulated into one aggregated packet. The data length in the transmission header of the aggregated packet is the transmission header of the two data packets and the total length of the Task serialization code stream. The Task type and The TaskQueue pointers of the destination thread are all -1, which means they are invalid.

Step S504: Receive the data packet through the receiving port, parse the data processing task from the data packet, and send it to the destination thread.

The receiving port can parse the data packet according to the agreed packet format, and use the magic word and CRC information to judge the validity of the data packet transmission, and discard the data packet if it is invalid. If the received packet is composed of multiple data packets, it will be unpacked according to the indication of the number of packets. For each valid data packet received, read the TaskQueue pointer and Task type in the transmission header, and send the Task to the TaskQueue of the corresponding destination thread. The destination thread reads the Task in its TaskQueue, and performs deserialization and subsequent processing according to the instruction of the Task type.

After completing the data transmission, you can delete the P2P Channel through the following steps:

(1) Pass the channel name of the data transmission channel to be deleted to the channel deletion module in the channel management component.

If the data transmission channel to be deleted is the channel from the Host to the Device direction, the channel name needs to be passed to the H2D channel deletion module; if the data transmission channel to be deleted is the channel from the Device to the Host direction, the The channel name is passed to the channel delete module of D2H.

(2) Call the channel resource management module in the channel management component through the channel deletion module to query whether there is a target channel, where the target channel is a data transmission channel corresponding to the channel name.

For example, if the channel name is: "H2D VideoStream #1", and a channel with the same name is found in the query, the channel can be determined as the target channel.

If the target channel does not exist, return a message that the deletion failed, and the failure reason can be attached to the message to delete the non-existing P2P Channel; if the target channel exists, continue to execute step (3).

(3) The channel resource management module is called by the channel deletion module, and the reference count of the target channel is decremented by 1. At this time, if the reference count is not 0, a message of successful deletion is returned; if the reference count is 0, Then proceed to step (4).

(4) Call the channel resource management module through the channel deletion module, clear the record of the target channel, and call the USB endpoint resource management module to release the USB endpoint resources occupied by the target channel, and return a channel deletion success message.

To sum up, through the embodiments of the present application, the existing USB interface is further encapsulated as a data transmission channel between the host and the slave, and a task queue processing mechanism is introduced therein to realize the thread of the host and the thread of the slave. The coordination and management between users does not require users to perform complicated control operations, which greatly improves the processing efficiency of a large number of complex tasks.

It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

 

Corresponding to a data transmission method described in the above embodiment, FIG. 9 shows an embodiment structure diagram of a data transmission apparatus provided by an embodiment of the present application.

In this embodiment, a data transmission device may include:

The channel creation module 901 is used to create a data transmission channel between the host end and the slave end, the data transmission channel including a sending task queue, a sending port and a receiving port;

A data sending module 902, configured to send the data processing task of the source thread to the sending task queue; the source thread is the data stream output party in the data processing thread on the host side and the data processing thread on the slave side ;

A data encapsulation module 903, configured to read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port;

The data receiving module 904 is configured to receive the data packet through the receiving port, parse the data processing task from the data packet and send it to a destination thread; the destination thread is the data processing thread of the host and the The data stream input side in the data processing thread of the slave side.

Further, the channel creation module may include:

Create an information transfer unit for transferring the channel name and channel parameters of the data transmission channel to the channel creation module in the preset channel management component;

a resource management unit, configured to invoke the USB endpoint resource management module in the channel management component through the channel creation module to create a USB endpoint logical channel corresponding to the channel name and the channel parameter;

A channel creation unit, configured to create a sending task queue, a sending port and a receiving port corresponding to the logical channel of the USB endpoint on the host side and the slave side through the channel creating module.

Further, the channel creation unit may include:

The first creation subunit is used to create a sending port and a sending task queue corresponding to the sending port on the host side through the channel creation module; the channel creation module uses a preset remote procedure call module in the Create a receive port on the slave side.

The second creation subunit is used to create a sending port and a sending task queue corresponding to the sending port on the slave side by using the preset remote procedure call module through the channel creating module; The host side creates a receive port as described above.

Further, the channel creation module may also include:

a channel query unit, configured to invoke the channel resource management module in the channel management component through the channel creation module to query whether there is a target channel, where the target channel is a data transmission channel corresponding to the channel name and channel parameters;

The stop creation unit is configured to stop the channel creation process if the target channel exists.

Further, the data sending module may include:

a serialization unit, used to serialize the data processing task to obtain the serialized data processing task;

a package unit, for forming a new data processing task according to the serialized data processing task, the task type and the pointer of the task queue of the destination thread;

A sending unit, configured to send the new data processing task to the sending task queue.

Further, the data encapsulation module may include:

a package unit, configured to encapsulate the data processing task into a data package according to a preset package format;

a first processing unit, configured to send the data packet to the receiving port if the data length of the data packet is greater than a preset threshold;

The second processing unit is configured to encapsulate a plurality of the data packets into aggregated packets and send them to the receiving port if the data length of the data packets is less than or equal to the threshold.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described devices, modules and units can be referred to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

FIG. 10 shows a schematic block diagram of a terminal device provided by an embodiment of the present application. For convenience of description, only parts related to the embodiment of the present application are shown.

As shown in FIG. 10 , the terminal device 10 in this embodiment includes: a processor 100 , a memory 101 , and a computer program 102 stored in the memory 101 and executable on the processor 100 . When the processor 100 executes the computer program 102, the steps in each of the above data transmission method embodiments are implemented, for example, steps S505 to S504 shown in FIG. 5 . Alternatively, when the processor 100 executes the computer program 102, the functions of the modules/units in the foregoing device embodiments are implemented, for example, the functions of the modules 901 to 904 shown in FIG. 9 .

Exemplarily, the computer program 102 may be divided into one or more modules/units, and the one or more modules/units are stored in the memory 101 and executed by the processor 100 to complete the this application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 102 in the terminal device 10 .

The terminal device 10 may be a computing device such as a desktop computer, a notebook, a palmtop computer, a smart phone, and a smart TV. Those skilled in the art can understand that FIG. 10 is only an example of the terminal device 10, and does not constitute a limitation on the terminal device 10. It may include more or less components than the one shown, or combine some components, or different components For example, the terminal device 10 may further include an input and output device, a network access device, a bus, and the like.

The processor 100 may be a central processing unit (Central Processing Unit, CPU), other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field-Programmable Gate Array (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The processor 100 may be the nerve center and command center of the terminal device 10, and the processor 100 may generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching and executing instructions.

The memory 101 may be an internal storage unit of the terminal device 10 , such as a hard disk or a memory of the terminal device 10 . The memory 101 may also be an external storage device of the terminal device 10, for example, a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) equipped on the terminal device 10 card, flash memory card (Flash Card), etc. Further, the memory 101 may also include both an internal storage unit of the terminal device 10 and an external storage device. The memory 101 is used to store the computer program and other programs and data required by the terminal device 10 . The memory 101 may also be used to temporarily store data that has been output or will be output.

The terminal device 10 may further include a communication module, and the communication module may provide a wireless local area network (Wireless Local Area Network) which is applied on the network device. Local Area Networks, WLAN) (such as Wi-Fi networks), Bluetooth, Zigbee, mobile communication networks, Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication Technology (Near) Field Communication, NFC), infrared technology (Infrared, IR) and other communication solutions. The communication module may be one or more devices integrating at least one communication processing module. The communication module may include an antenna, and the antenna may have only one array element, or may be an antenna array including multiple array elements. The communication module can receive the electromagnetic wave through the antenna, frequency modulate and filter the electromagnetic wave signal, and send the processed signal to the processor. The communication module can also receive the signal to be sent from the processor, perform frequency modulation and amplification on it, and then convert it into electromagnetic waves for radiation through the antenna.

The terminal device 10 may further include a power management module, which may receive input from an external power source, a battery and/or a charger, and supply power to the processor, the memory, the communication module, and the like.

The terminal device 10 may further include a display module, which may be used to display information input by the user or information provided to the user. The display module may include a display panel, optionally, a liquid crystal display (Liquid Crystal Display, LCD), organic light-emitting diode (Organic Light-Emitting Diode, OLED) and other forms to configure the display panel. Further, the touch panel can cover the display panel, and when the touch panel detects a touch operation on or near it, it is transmitted to the processor to determine the type of the touch event, and then the processor determines the type of the touch event according to the type of the touch event. A corresponding visual output is provided on the display panel.

Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment may be integrated in one processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit, and the above-mentioned integrated units may adopt hardware. It can also be realized in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing from each other, and are not used to limit the protection scope of the present application. For the specific working processes of the units and modules in the above-mentioned system, reference may be made to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

In the foregoing embodiments, the description of each embodiment has its own emphasis. For parts that are not described or described in detail in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.

In the embodiments provided in this application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units. Or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The embodiments of the present application provide a computer program product, which enables the terminal device to implement the steps in the foregoing method embodiments when the computer program product runs on the terminal device.

The integrated modules/units, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the present application can implement all or part of the processes in the methods of the above embodiments, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer When the program is executed by the processor, the steps of the foregoing method embodiments can be implemented. Wherein, the computer program includes computer program code, and the computer program code may be in the form of source code, object code, executable file or some intermediate form, and the like. The computer-readable storage medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM, Read-Only). Memory), random access memory (RAM, Random Access Memory), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content contained in the computer-readable storage medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, computer-readable Storage media exclude electrical carrier signals and telecommunications signals.

Claims (10)

1. A data transmission method, comprising:

   Create a data transmission channel between the host and the slave, and the data transmission channel includes a sending task queue, a sending port and a receiving port;

   sending the data processing task of the source thread to the sending task queue; the source thread is the data stream output party in the data processing thread of the host side and the data processing thread of the slave side;

   Read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port;

   The data packet is received through the receiving port, the data processing task is parsed from the data packet and sent to the destination thread; the destination thread is the data processing thread on the host side and the data processing on the slave side The data stream input side in the thread.
2. The data transmission method according to claim 1, wherein the creating a data transmission channel between the host and the slave comprises:

   passing the channel name and channel parameters of the data transmission channel to the channel creation module in the preset channel management component;

   Calling the USB endpoint resource management module in the channel management component by the channel creation module to create a USB endpoint logical channel corresponding to the channel name and the channel parameter;

   A sending task queue, a sending port and a receiving port corresponding to the logical channel of the USB endpoint are created on the host side and the slave side by the channel creation module.
3. The data transmission method according to claim 2, wherein the data transmission channel is a channel from the host end to the slave end direction;

   The creating a sending task queue, sending port and receiving port corresponding to the USB endpoint logical channel on the host side and the slave side through the channel creation module, including:

   Create a sending port and a sending task queue corresponding to the sending port on the host side by the channel creation module;

   A receive port is created on the slave side by the channel creation module using a preset remote procedure call module.
4. The data transmission method according to claim 2, wherein the data transmission channel is a channel from the slave end to the host end;

   The creating a sending task queue, sending port and receiving port corresponding to the USB endpoint logical channel on the host side and the slave side through the channel creation module, including:

   Using the preset remote procedure call module to create a sending port and a sending task queue corresponding to the sending port on the slave end through the channel creation module;

   A receiving port is created on the host side by the channel creation module.
5. The data transmission method according to claim 2, wherein after passing the channel name and channel parameters of the data transmission channel to the channel creation module in the preset channel management component, the method further comprises:

   Call the channel resource management module in the channel management component through the channel creation module to query whether there is a target channel, where the target channel is a data transmission channel corresponding to the channel name and channel parameters;

   If the target channel exists, the channel creation process is stopped.
6. The data transmission method according to claim 1, wherein the sending the data processing task of the source thread to the sending task queue comprises:

   serializing the data processing task to obtain a serialized data processing task;

   A new data processing task is formed according to the serialized data processing task, the task type and the pointer of the task queue of the destination thread;

   Send the new data processing task to the sending task queue.
7. The data transmission method according to any one of claims 1 to 6, wherein the encapsulating the data processing task into a data packet and sending it to the receiving port comprises:

   Encapsulate the data processing task into a data package according to a preset package format;

   If the data length of the data packet is greater than a preset threshold, send the data packet to the receiving port;

   If the data length of the data packets is less than or equal to the threshold, a plurality of the data packets are encapsulated into aggregate packets and sent to the receiving port.
8. A data transmission device, comprising:

   a channel creation module for creating a data transmission channel between the host and the slave, the data transmission channel including a sending task queue, a sending port and a receiving port;

   A data sending module, configured to send the data processing task of the source thread to the sending task queue; the source thread is the data stream exporter among the data processing thread of the host side and the data processing thread of the slave side;

   a data encapsulation module, configured to read the data processing task from the sending task queue through the sending port, encapsulate the data processing task into a data packet and send it to the receiving port;

   A data receiving module, configured to receive the data packet through the receiving port, parse out the data processing task from the data packet and send it to a destination thread; the destination thread is the data processing thread on the host side and the The input side of the data stream in the data processing thread of the slave side.
9. A computer-readable storage medium storing a computer program, characterized in that, when the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 7 is implemented A step of.
10. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the computer program, the process according to claim 1 to Steps of the data transmission method described in any one of 7.