WO2024046117A1

WO2024046117A1 - Data transmission method and terminal device

Info

Publication number: WO2024046117A1
Application number: PCT/CN2023/113203
Authority: WO
Inventors: 李鹏飞
Original assignee: 荣耀终端有限公司
Priority date: 2022-09-02
Filing date: 2023-08-15
Publication date: 2024-03-07
Also published as: CN117692551A

Abstract

The present application provides a data transmission method and a terminal device, which can improve the data transmission efficiency, reduce the operations of a user, and improve the user experience. The data transmission method provided in the present application comprises: a first device detecting a first operation of a user, wherein the first operation is used for moving, by means of a mouse, an identifier of target data from a third device to the first device via a second device, the third device and the second device support keyboard-mouse crossover, and the second device and the first device support keyboard-mouse crossover; in response to the first operation, the first device sending information of requesting the target data to the third device by means of the second device; and the first device receiving the target data from the third device.

Description

Data transmission method and terminal equipment

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 2, 2022, with application number 202211071845.0 and application name "Data transmission method and terminal equipment", the entire content of which is incorporated into this application by reference. middle.

Technical field

The present application relates to the field of terminal technology, and in particular, to a data transmission method and terminal equipment.

Background technique

In order to meet the needs of users for work and study, multiple terminal devices can support keyboard and mouse traversal to achieve cross-device collaboration. For example, after the user's computer, mobile phone and tablet are connected, they can share the computer's mouse and keyboard. In other words, the user can control the mobile phone and tablet through the computer's mouse and keyboard. For example, users can use the mouse to drag files, text, pictures and other data from their mobile phones or tablets to their computers, or users can use their mouse to drag files, texts, pictures and other data from their computers to their mobile phones or computers.

In this case, if the user transfers the data from the mobile phone to the tablet, he can only drag the data from the mobile phone to the computer through the mouse, and then drag the data from the computer to the tablet through the mouse. The data from the mobile phone cannot be transferred directly to the tablet. Tablets reduce data transmission efficiency and are cumbersome to operate, which is not conducive to user experience.

Contents of the invention

This application provides a data transmission method that can improve data transmission efficiency, reduce user operations, and improve user experience.

In a first aspect, a data transmission method is provided, including: a first device detects a first operation of a user, and the first operation is used to move an identification of target data from a third device to the first device via a second device through a mouse. , the third device and the second device support keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal; in response to the first operation, the first device sends information requesting target data to the third device through the second device; One device receives target data from a third device.

The first operation is used to move the identification of the target data from the third device to the first device via the second device through the mouse, where moving to the first device can be understood as dragging to the first device, that is, the user controls Use the mouse to drag the mark of the target data to the first device through the second device. The identification of the target data may be pictures, documents, texts, music, videos, etc., which are not limited in the embodiments of the present application.

The target data is data dragged by the user, which can be any data that supports dragging, and can also be called dragging data, which is not limited in the embodiment of the present application.

The first device is the device that receives the target data, and can also be understood as the device that drags in the target data. The second device can be understood as an intermediate device, which does not drag data out or import data. The third device is a device that sends target data, and can also be understood as a device that drags out target data.

Optionally, the first device and the third device may deploy the Android system and may be called Android devices. The second device can deploy Windows system.

Illustratively, in the example shown in FIG. 2 , the first device may be a tablet 103 , the second device may be a computer 101 , and the third device may be a mobile phone 102 . In the example shown in FIG. 5 , the first device may be a mobile phone 102 , the second device may be a computer 101 , and the third device may be a tablet 103 .

The first device requests the target data by requesting information about the target data. The message may be sent to the first device first, and then sent by the second device to the third device.

The data transmission method provided by this application can support users to drag data from the first device through the second device to the third device, which can improve data transmission efficiency, reduce user operations, and improve user experience.

Combined with the first aspect, in some implementations of the first aspect, the first device receives the target data from the third device, including: the first device establishes a data transmission channel with the third device; the first device uses the data transmission channel Receive target data from a third device.

In the data transmission method provided by this application, the first device and the third device directly establish a data transmission channel. Using a transmission channel to transmit data does not require a second device to transfer data, which is more efficient and helps further improve data transmission efficiency.

In conjunction with the first aspect, in some implementations of the first aspect, after the first device receives the target data from the third device through the data transmission channel, the method further includes: the first device removes the data transmission channel.

In the data transmission method provided by this application, after the data is transmitted, the first device can dismantle the data transmission channel and establish it again when data needs to be transmitted, which is beneficial to saving the power consumption of the first device and avoiding waste of resources.

In conjunction with the first aspect, in some implementations of the first aspect, the first device receiving the target data from the third device includes: the first device receiving the target data from the third device through the second device.

The first device receives the target data from the third device through the second device, that is, the first device can obtain the target data from the second device, and the target data of the second device is sent by the third device.

With the data transmission method provided by this application, the first device can obtain target data from the second device, and the target data of the second device is sent by the third device. The existing data transmission method can be reused with minimal changes, which is conducive to application promotion. .

In connection with the first aspect, in some implementations of the first aspect, before sending the information requesting the target data to the third device through the second device, the method further includes: the first device determines that the mouse drags the identifier of the target data into Whether the area is a preset area; sending information requesting target data to the third device through the second device, including: in the case that the area dragged into by the identifier of the target data is a preset area, the first device sends the request to the third device through the second device. Three devices send messages requesting target data.

The preset area is an area provided by the first device that allows data to be dragged in, and may vary according to different applications, and is not limited in this embodiment of the present application.

If the area to which the target data identifier is dragged is a preset area, it means that the drag operation is completed, and the first device can send information requesting the target data to the third device through the second device. If the area to which the target data identifier is dragged is not a preset area, it may indicate that the drag operation failed and the first device does not need to request the target data.

The data transmission method provided by this application, when the area into which the target data identifier is dragged is a preset area, requests the target data from the third device through the second device, which is beneficial to displaying the drag data in the preset area.

In conjunction with the first aspect, in some implementations of the first aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In a second aspect, a data transmission method is provided, including: a third device detects a user's first operation, and the first operation is used to move an identification of target data from the third device to the first device through the second device through the mouse. , the third device and the second device support keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal; the third device responds to the first operation, Information requesting target data from the first device is received through the second device; and the third device sends the target data to the first device.

Combined with the second aspect, in some implementations of the second aspect, the third device sends the target data to the first device, including: the third device establishes a data transmission channel with the first device; the third device transmits the target data to the first device through the data transmission channel. The first device sends the target data.

Combined with the second aspect, in some implementations of the second aspect, after the third device sends the target data to the first device through the data transmission channel, the method further includes: the third device removes the data transmission channel.

Combined with the second aspect, in some implementations of the second aspect, the third device sends the target data to the first device, including: the third device sends the target data to the first device through the second device.

In conjunction with the second aspect, in some implementations of the second aspect, before receiving the information requesting the target data from the first device through the second device, the method further includes: in response to the first operation, the third device obtains the target data. The identified universal resource identifier (URI); the third device determines the data corresponding to the URI as the target data.

When the third device detects the first operation, it may first obtain the URI identified by the target data, so as to determine the target data based on the URI.

Combined with the second aspect, in some implementations of the second aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In a third aspect, a data transmission method is provided, including: the second device detects a first operation of the user, and the first operation is used to move the identification of the target data from the third device to the first device through the second device through the mouse. , the third device and the second device support keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal; in response to the first operation, the second device receives information requesting target data from the first device; the second device sends The third device sends a message requesting the target data.

In the data transmission method provided by this application, after the second device receives the information requesting the target data, it sends the information requesting the target data to the third device, which is helpful for the first device and the third device to complete communication.

In conjunction with the third aspect, in some implementations of the third aspect, before the second device sends the information requesting the target data to the third device, the method further includes: in response to the first operation, the second device determines the movement status as Move from the third device to the first device; the second device sends the information requesting the target data to the third device, including: the second device sends the information requesting the target data to the third device based on the information requesting the target data and the movement status.

The moving state may also be called a dragging state, which is not limited in the embodiments of the present application. The moving status can be dragging completed, dragging to the first device, dragging to the second device, or dragging to the third device, etc.

If the movement state is dragging to the first device, it means that the target data is moved from the third device to the first device. If the movement state is dragging to the third device, it means that the target data is moved from the first device to the third device. If the movement state is dragging to the second device, it means that the target data is moved from the first device or the third device to the second device. If the moving status is dragging completed, it means the moving operation is completed.

The second device may send the information requesting the target data to the third device based on the information requesting the target data and the movement status to implement communication between the first device and the third device.

Combined with the third aspect, in some implementations of the third aspect, the method further includes: the second device receives target data from the third device; and the second device sends the target data to the first device.

Combined with the third aspect, in some implementations of the third aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In the fourth aspect, a terminal device is provided, including: a processing module and a transceiver module. Wherein, the processing module is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the third device to the second device through the mouse, the third device and the second device support keyboard and mouse traversal, The second device supports keyboard and mouse traversal; the transceiver module is configured to: in response to the first operation, send information requesting target data to the third device through the second device; and receive target data from the third device.

In connection with the fourth aspect, in some implementations of the fourth aspect, the above-mentioned processing module is also used to: establish a data transmission channel with the third device; the above-mentioned transceiver module is also used to: receive data from the third device through the data transmission channel. target data.

Combined with the fourth aspect, in some implementations of the fourth aspect, the above processing module is also used to: remove the data transmission channel.

In conjunction with the fourth aspect, in some implementations of the fourth aspect, the above-mentioned transceiver module is further configured to: receive target data from the third device through the second device.

Combined with the fourth aspect, in some implementations of the fourth aspect, the above-mentioned processing module is also used to: determine whether the area into which the mark of the target data is dragged by the mouse is a preset area; the above-mentioned transceiver module is also used to: in the target data When the area dragged into by the identifier is a preset area, information requesting target data is sent to the third device through the second device.

Combined with the fourth aspect, in some implementations of the fourth aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In the fifth aspect, a terminal device is provided, including: a processing module and a transceiver module. Wherein, the processing module is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the second device to the first device through the mouse, and the second device supports keyboard and mouse traversal, and the second device The first device supports keyboard and mouse traversal; the transceiver module is configured to: in response to the first operation, receive information requesting target data from the first device through the second device; and send the target data to the first device.

Combined with the fifth aspect, in some implementations of the fifth aspect, the above-mentioned processing module is also used to: establish a data transmission channel with the first device; the above-mentioned transceiver module is also used to: send the target to the first device through the data transmission channel. data.

Combined with the fifth aspect, in some implementations of the fifth aspect, the above processing module is also used to: dismantle the data transmission channel.

In conjunction with the fifth aspect, in some implementations of the fifth aspect, the above-mentioned transceiver module is also used to: send target data to the first device through the second device.

In conjunction with the fifth aspect, in some implementations of the fifth aspect, the above processing module is further configured to: in response to the first operation, obtain the universal resource identifier URI identified by the target data; and determine the data corresponding to the URI as the target data.

Combined with the fifth aspect, in some implementations of the fifth aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In a sixth aspect, a terminal device is provided, including: a processing module and a transceiver module. Wherein, the processing module is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the third device to the first device through the mouse, the third device supports keyboard and mouse traversal, and the first device The device supports keyboard and mouse traversal; the transceiver module is configured to: in response to the first operation, receive information requesting target data from the first device; and send information requesting target data to the third device.

In conjunction with the sixth aspect, in some implementations of the sixth aspect, the above-mentioned processing module is further configured to: in response to the first operation, determine the movement state as moving from the third device to the first device; the above-mentioned transceiver module is also configured to: : Based on the information and movement status of the requested target data, send the information requesting the target data to the third device.

Combined with the sixth aspect, in some implementations of the sixth aspect, the above-mentioned transceiver module is also used to: receive target data from the third device; and send the target data to the first device.

Combined with the sixth aspect, in some implementations of the sixth aspect, the target data includes at least one of the following: text data, image data, document data, email data, compressed package data, music data or video data.

In a seventh aspect, the present application provides a terminal device, including a processor, which is coupled to a memory and can be used to execute instructions in the memory to implement the method in any of the possible implementation manners of any of the above aspects. Optionally, the device further includes memory. Optionally, the device further includes a transceiver, and the processor is coupled to the transceiver.

In an eighth aspect, the present application provides a processor, including: an input circuit, an output circuit and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, so that the processor performs the method in any of the possible implementations of any of the above aspects.

In the specific implementation process, the above-mentioned processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, a gate circuit, a flip-flop, and various logic circuits. The input signal received by the input circuit may be received and input by, for example, but not limited to, the receiver, and the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter, and the input circuit and the output A circuit may be the same circuit that functions as an input circuit and an output circuit at different times. This application does not limit the specific implementation methods of the processor and various circuits.

In a ninth aspect, the present application provides a processing device, including a processor and a memory. The processor is used to read instructions stored in the memory, and can receive signals through a receiver and transmit signals through a transmitter to execute the method in any of the possible implementations of any of the above aspects.

Optionally, there are one or more processors and one or more memories.

Alternatively, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory (ROM), which can be integrated on the same chip as the processor, or can be set in different On the chip, this application does not limit the type of memory and the arrangement of the memory and the processor.

It should be understood that the relevant data interaction process, for example, sending instruction information may be a process of outputting instruction information from the processor, and receiving capability information may be a process of the processor receiving input capability information. Specifically, the data output by the processing can be output to the transmitter, and the input data received by the processor can come from the receiver. Among them, the transmitter and receiver can be collectively called a transceiver.

The processing device in the ninth aspect can be a chip, and the processor can be implemented by hardware or software. When implemented by hardware, the processor can be a logic circuit, an integrated circuit, etc.; when implemented by software. When implemented, the processor can be a general-purpose processor, which is implemented by reading the software code stored in the memory. The memory can be integrated in the processor, or can be located outside the processor and exist independently.

In a tenth aspect, the present application provides a computer-readable storage medium that stores a computer program (which can also be called code, or instructions) that when run on a computer causes the computer to execute any of the above. A method in any of the possible implementations.

In an eleventh aspect, the present application provides a computer program product. The computer program product includes: a computer program (which can also be called a code, or an instruction). When the computer program is run, it causes the computer to execute any one of the above aspects. possible implementation methods.

Description of drawings

Figure 1 is a schematic diagram of transferring photos across devices;

Figure 2 is a schematic diagram of transmitting photos across devices according to an embodiment of the present application;

Figure 3 is a schematic diagram of another cross-device photo transmission provided by an embodiment of the present application;

Figure 4 is a schematic diagram of yet another cross-device photo transmission provided by an embodiment of the present application;

Figure 5 is a schematic diagram of a cross-device file transfer failure provided by an embodiment of the present application;

Figure 6 is a software structure block diagram of a PC provided by an embodiment of the present application;

Figure 7 is a software structure block diagram of an Android device provided by an embodiment of the present application;

Figure 8 is a schematic flow chart of a keyboard and mouse connection method provided by an embodiment of the present application;

Figure 9 is a schematic flow chart of a mouse crossing detection method provided by an embodiment of the present application;

Figure 10 is a schematic diagram of establishing a screen coordinate system provided by an embodiment of the present application;

Figure 11 is a schematic flow chart of a data transmission method provided by an embodiment of the present application;

Figure 12 is a schematic flow chart of a method for obtaining data provided by an embodiment of the present application;

Figure 13 is a schematic flow chart of another method of obtaining data provided by an embodiment of the present application;

Figure 14 is a schematic diagram of a terminal device provided by an embodiment of the present application;

Figure 15 is a schematic diagram of another terminal device provided by an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings.

In order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as “first” and “second” are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the number and execution order, and words such as "first" and "second" do not limit the number and execution order.

It should be noted that in this application, words such as "exemplarily" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" or "such as" is not intended to be construed as preferred or advantageous over other embodiments or designs. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

In addition, "at least one" means one or more, and "plurality" means two or more. "And/or" describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. The character "/" generally indicates that the related objects are in an "or" relationship. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, where a, b, c can be single or multiple.

Exemplarily, FIG. 1 shows a schematic diagram of transmitting photos across devices. As shown in a in Figure 1, the communication system includes a computer 101, a mobile phone 102 and a tablet 103. Among them, the operating system of the computer 101 is Windows system, and the operating system of mobile phone 102 and tablet 103 is Android system. Keyboard and mouse travel can be realized between the computer 101 and the mobile phone 102, and keyboard and mouse travel can be realized between the computer 101 and the tablet 103. That is to say, the computer 101, the mobile phone 102 and the tablet 103 can share the mouse and keyboard. In this case, the computer 101 can be called the source device or the sending end, and the mobile phone 102 and the tablet 103 can be called the peer device or the receiving end, but the embodiment of the present application is not limited thereto.

After the keyboard and mouse of the computer 101 travel to the mobile phone 102 or tablet 103, cross-screen collaboration can be achieved. That is to say, the user can use the mouse to click, drag, or double-click on the mobile phone 102 or tablet 103, and can use the keyboard to input information on the mobile phone 102 or tablet 103.

After the computer 101's keyboard and mouse travel to the mobile phone 102 or tablet 103, it can also realize cross-device transfer of files, photos, music and other content. That is to say, the user can drag files, photos, music and other content from the mobile phone 102 or tablet 103. Drag it to the computer 101, or drag files, photos, music and other content in the computer 101 to the mobile phone 102 or tablet 103. It can be understood that the embodiments of the present application are not limited to content such as documents, photos, and music.

As shown in a in Figure 1, when the user takes a screenshot of the main interface of the mobile phone 102, the mobile phone 102 takes a screenshot in response to the user's operation of taking a screenshot, and displays the picture in the lower left corner of the interface. The user can drag the picture to the desktop of the computer 101 through the mouse. When the computer 101 detects the user's operation of dragging the picture to the main interface of the computer 101, b in Figure 1 may be displayed in response to the operation. As shown in b in Figure 1, the computer 101 can display the drag icon of the picture, and accordingly, the picture in the lower right corner of the interface of the mobile phone 102 disappears. When the computer 101 detects that the user cancels the dragging operation on the picture, in response to the operation, the picture can be saved to the file manager and the interface of the file manager is displayed, that is, c in Figure 1 is displayed. As shown in c in Figure 1, the computer 101 saves the image to the file manager and names the image as 20220405_1 by default. The format of the displayed image is png and the size of the displayed image is 302.08 kilobytes (Kilobyte, kb). As well as showing the time the picture was saved was "just now".

In the above communication system, if the user transfers a screenshot of the mobile phone 102 to the tablet 103, he can only drag the data from the mobile phone 102 to the computer 101 through the mouse, and then drag the data from the computer 101 to the tablet 103 through the mouse. The data from the mobile phone is directly transmitted to the tablet, which reduces the data transmission efficiency and makes the operation cumbersome, which is not conducive to the user experience.

In view of this, embodiments of the present application provide a data transmission method, which can improve data transmission efficiency, reduce user operations, and improve user experience. That is to say, the user can use the mouse to drag the data from the mobile phone 102 directly to the tablet 103 via the computer 101, or the user can directly drag the data from the tablet 103 to the mobile phone 102 via the computer 101. There is no need to drag the data into the computer 101 first. Drag to Tablet 103.

In order to better understand the embodiments of the present application, the scenarios used in the embodiments of the present application are first introduced.

Figure 2 shows a schematic diagram of transferring photos across devices. As shown in Figure 2, the user drags the picture on the mobile phone 102 to the main interface of the tablet 103. As shown in a in Figure 2, when the user takes a screenshot of the main interface of the mobile phone 102, the mobile phone 102 takes a screenshot in response to the user's operation of taking a screenshot, and displays the picture in the lower left corner of the interface. The user can drag the picture to the main interface of the tablet 103 through the computer 101 using the mouse. When the computer 101 detects the user's operation of dragging the picture to the main interface of the computer 101, b in Figure 2 may be displayed in response to the operation. As shown in b in Figure 2, the computer 101 can display the drag icon A, and accordingly, the picture in the lower right corner of the interface of the mobile phone 102 disappears. The computer 101 detects the user's drag operation to the tablet 103, and in response to the operation, c in Figure 2 can be displayed. As shown in c in Figure 2, the tablet 103 may display the drag icon B. When the tablet 103 detects that the user cancels the drag operation on the picture, in response to the operation, the picture can be saved to the file manager and the interface of the file manager is displayed, that is, d in Figure 2 is displayed. like As shown in d in Figure 2, the tablet 103 saves the image to the file manager and names the image as 20220405_1 by default, the format of the displayed image is png and the size of the displayed image is 302.08 kilobytes (Kilobyte, kb).

It should be noted that the file manager can support any type of data, so the tablet 103 can be used to save data such as pictures, music, and files dragged to the main interface.

Figure 3 shows another schematic diagram of transferring photos across devices. As shown in Figure 3, the user drags the picture on the mobile phone 102 to the chat interface of the tablet 103. As shown in a in Figure 3, when the user takes a screenshot of the main interface of the mobile phone 102, the mobile phone 102 takes a screenshot in response to the user's operation of taking a screenshot, and displays the picture in the lower left corner of the interface. The user can drag the picture to the chat interface of the tablet 103 through the computer 101 with the mouse. When the computer 101 detects the user's operation of dragging the picture to the main interface of the computer 101, b in Figure 3 may be displayed in response to the operation. As shown in b in Figure 3, the computer 101 can display the drag icon A, and accordingly, the picture in the lower right corner of the interface of the mobile phone 102 disappears. The computer 101 detects the user's drag operation to the tablet 103, and in response to the operation, c in Figure 3 can be displayed. As shown in c in Figure 3, the tablet 103 can display the drag icon B on the chat interface. When the tablet 103 detects that the user cancels the drag operation on the picture, in response to the operation, the picture can be displayed on the chat interface, that is, d in Figure 3 is displayed. As shown in d in Figure 3, tablet 103 is displayed on the chat interface.

It should be noted that the chat application can support data of image, file and other types, and can allow data transmission.

Figure 4 shows yet another schematic diagram of transferring photos across devices. As shown in Figure 4, the user drags pictures from the mobile phone 102 to the gallery application of the tablet 103. As shown in a in Figure 4, when the user takes a screenshot of the main interface of the mobile phone 102, the mobile phone 102 takes a screenshot in response to the user's operation of taking a screenshot, and displays the picture in the lower left corner of the interface. The user can drag the picture to the gallery application of the tablet 103 through the computer 101 with the mouse. When the computer 101 detects the user's operation of dragging the picture to the main interface of the computer 101, b in Figure 4 may be displayed in response to the operation. As shown in b in Figure 4, the computer 101 can display the drag icon A, and accordingly, the picture in the lower right corner of the interface of the mobile phone 102 disappears. The computer 101 detects the user's drag operation to the tablet 103, and in response to the operation, c in Figure 4 can be displayed. As shown in c in Figure 4 , the tablet 103 can display the drag icon B in the gallery application. When the tablet 103 detects that the user cancels the drag operation on the picture, in response to the operation, the picture can be saved to the gallery application, that is, d in Figure 4 is displayed. As shown in d in Figure 4, the tablet 103 can display the picture in the gallery application.

It should be noted that the gallery application only supports the transmission of image data and does not allow the transmission of other data.

If the user drags a file to the gallery application, the gallery application does not support the file format, the gallery application does not save the dragged data, and the drag and drop fails.

Exemplarily, FIG. 5 shows a schematic diagram of a file transfer failure across devices. As shown in a in Figure 5 , tablet 103 displays a file manager interface, which includes two documents, one of which is the meeting process and the other is the meeting content. The computer 101 displays the main interface, and the mobile phone 102 displays the interface of the gallery application. The interface includes 5 pictures, and the 5 icons include photo 1, photo 2, photo 3, photo 4 and photo 5. If the user drags a meeting document on the tablet 103 to the gallery application of the mobile phone 102 via the computer 101, and the tablet 103 detects the user's operation of dragging the document out of the screen and onto the computer 101, in response to the operation, it can be displayed b in Figure 2. As shown in b in Figure 2 , the interface displayed by the tablet 103 only includes the meeting process document, and the computer 101 can display the drag icon A. The computer 101 detects the user's operation of dragging the document out of the screen and onto the mobile phone 102. In response to the operation, c in Figure 5 can be displayed. As shown in c in Figure 5, the mobile phone 102 can display the drag icon B in the gallery application. When the mobile phone 102 detects that the user cancels the drag operation on the document, in response to the operation, it determines whether the document is a data type supported by the gallery application. If the document does not meet the data type supported by the gallery application, the document can be refused to be received, and the document can be displayed as shown in Figure 4 d. As shown in d in Figure 4 As shown, the tablet 103, the computer 101 and the mobile phone 102 display the initial interface before the drag operation without any changes.

It should be noted that the above drag icon B may vary according to the data type of the drag data. The corresponding relationship between the data type and the drag icon B may be preset.

In order to realize the above functions, embodiments of the present application provide specific implementation methods of data transmission.

The method provided by the embodiment of the present application can be applied to a communication system with keyboard and mouse traversal, and the communication system includes three devices. Among them, the communication system can include personal computers and Android devices. Among them, the Android device includes Android device 1 and Android device 2, such as the communication system 100 described in Figure 1 above. The PC is the computer 101, the mobile phone 102 can be the Android device 1, and the tablet 103 can be the Android device 2. However, in the embodiment of this application It is not limited to this. A personal computer can be a desktop computer, a laptop computer (such as 101 above), a small laptop computer, a tablet computer, an ultrabook and other devices. The software system of the personal computer is the windows system. Android devices are devices that deploy the Android system, such as mobile phones (such as the above-mentioned mobile phone 102), tablets (such as the above-mentioned mobile phone 103), and so on.

In order to better understand the embodiment of the present application, the PC, the Android device 1 and the software structure of the Android device 1 in the embodiment of the present application are introduced below.

Exemplarily, FIG. 6 shows a software structure block diagram of a PC. As shown in Figure 6, PC includes business layer, capability layer and driver layer.

The business layer includes applications, human-computer interaction (user interface, UI) interface implementation modules, keyboard and mouse business modules, and drag-and-drop modules. Among them, applications include applications such as gallery, chat, and file managers. The UI interface implementation module is used to provide users with a visual interface. For example, the UI interface implementation module can display the main interface shown in Figure 1 above, and so on. The keyboard and mouse business module is used to call the keyboard virtualization capability module to realize keyboard and mouse traversal. The drag module is used to call the drag framework to monitor the user's drag operation.

The capability layer includes the drag-and-drop framework, communication module (magic link), PC manager framework, keyboard virtualization capability module, audio system and storage system. Among them, the drag and drop framework is used to support the user's drag and drop operation. The communication module is used to communicate with Android devices. The keyboard virtualization capability module is used to obtain keyboard and mouse events and transmit keyboard and mouse events. PC housekeeper framework is used to manage PC housekeeper options. The audio system manages the playback of high-performance audio. Storage systems are used for data storage.

The driver layer includes Bluetooth driver, audio driver, wifi driver and human interface device (HID) driver.

Figure 7 shows a software structure block diagram of an Android device. As shown in Figure 7, the Android device includes the application layer, application framework layer, Android runtime and system libraries, and kernel layer.

The application layer includes keyboard and mouse business modules, UI interface implementation modules, drag and drop modules, keyboard and mouse virtualization capability modules, communication modules (magic link) and applications. Among them, the UI interface implementation module is used to provide users with a visual interface. For example, the UI interface implementation module is used to display the main interface and application interface. The drag module is used to call the drag framework to monitor the user's drag operation. The keyboard and mouse virtualization capability module is used to provide keyboard and mouse virtualization capabilities, that is, to obtain keyboard and mouse events and to transmit keyboard and mouse events. The communication module is used to provide connection channels between devices and data capability transmission. Applications include applications such as gallery, chat, and file managers.

The application framework layer includes drag-and-drop framework, multi-screen framework, input management module and storage system. Among them, the drag frame is used to provide drag capabilities when the keyboard and mouse traverse. The input management module is used to provide keyboard and mouse event reporting. Storage systems are used to store data. The multi-screen framework is used to provide multi-screen operation with keyboard and mouse.

Android runtime and system libraries include core libraries, virtual machines, surface managers, media libraries, and 3D graphics processing libraries. The Android system runtime is responsible for the scheduling and management of the Android system. The core library contains two parts: one part is required by the Java language The function function called, the other part is the core library of Android. The application layer and application framework layer run in virtual machines. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions. The system library can contain modules with multiple functions, such as surface manager, media library, and 3D graphics processing library.

The surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support multiple audio and video encoding formats, such as JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, composition and layer processing.

The kernel layer is the layer between hardware and software. The kernel layer is used to drive the hardware and make the hardware work. The kernel layer includes Bluetooth driver, audio driver, wifi driver, virtual input driver (Uinput driver) and HID driver. Among them, the virtual input driver is used to inject input events.

In order to better understand the embodiment of the present application, the embodiment of the present application specifically introduces the method provided by the embodiment of the present application in conjunction with the modules involved in the above-mentioned Figures 5 and 6.

After the PC and the Android device are successfully connected, before data transmission between the PC and the Android device, you can first determine whether the keyboard and mouse are successfully connected. If the connection is successful, the data can be transferred.

Exemplarily, FIG. 8 shows a schematic flow chart of a keyboard and mouse connection method 800. As shown in FIG. 8 , the method 800 can be applied to communication systems including PCs and Android devices, such as the above-mentioned communication system 100 , but the embodiments of the present application are not limited thereto. The software architecture diagram of the PC can be shown in Figure 6, and the software architecture diagram of the Android device can be shown in Figure 7. The embodiments of the present application are not limited thereto.

The method 800 may include the following steps:

S801. The keyboard and mouse business module of the PC establishes a transmission connection with the keyboard and mouse business module of the Android device.

After the PC is connected to the Android device, the keyboard and mouse business module of the PC and the keyboard and mouse business module of the Android device can establish a transmission connection. Wherein, the Android device is Android device 1 or Android device 2, which is not limited in the embodiment of the present application.

S802. The keyboard and mouse business module of the PC sends the instruction information for starting the keyboard and mouse service to the keyboard and mouse business module of the Android device. Correspondingly, the keyboard and mouse business module of the Android device receives the instruction information for starting the keyboard and mouse service.

The instruction information for enabling the keyboard and mouse service is used to instruct the keyboard and mouse business module of the Android device to enable the keyboard and mouse service.

The keyboard and mouse service is also the keyboard and mouse traversal option. The instruction information to enable the keyboard and mouse service means instructing the keyboard and mouse business module of the Android device to enable the keyboard and mouse traversal option.

S803. The keyboard and mouse business module of the Android device determines whether the keyboard and mouse service is supported based on the instruction information for enabling the keyboard and mouse service.

The keyboard and mouse service is also the keyboard and mouse traversal option. The opening and closing of the keyboard and mouse service is determined by the user. The keyboard and mouse business module of the Android device determines whether the keyboard and mouse service is supported, that is, the keyboard and mouse business module of the Android device determines whether the user has checked, selected, or enabled the keyboard and mouse traversal option.

If the user checks, selects or enables the keyboard and mouse traversal option, the keyboard and mouse business module of the Android device can support the keyboard and mouse service. If the user has not checked, unchecked, or turned off the keyboard and mouse traversal option, the keyboard and mouse business module of the Android device does not support the keyboard and mouse service, and keyboard and mouse traversal cannot be performed.

S804. When the keyboard and mouse service is supported, the keyboard and mouse business module of the Android device sends the instruction information for starting the keyboard and mouse service to the keyboard and mouse virtualization capability module of the Android device. Correspondingly, the keyboard and mouse virtualization capability module of the Android device receives Instructions for starting the keyboard and mouse service.

S805. The keyboard and mouse virtualization capability module of the Android device registers a virtual input (Uinput) based on the instruction information for starting the keyboard and mouse service.

Uinput is used to inject keyboard and mouse events.

S806. The keyboard and mouse virtualization capability module of the Android device sends the registration result A to the keyboard and mouse business module of the Android device. Correspondingly, the keyboard and mouse business module of the Android device receives the registration result A.

The registration result A can be used to indicate whether the registration of Uinput is successful. The registration result can be success or failure. In one embodiment, success and failure may be represented by binary identifiers. For example, 1 indicates success and 0 indicates failure.

S807. Based on the instruction information of starting the keyboard and mouse service, the keyboard and mouse virtualization capability module of the Android device sends the instruction information of registering cursor position monitoring to the multi-screen framework module of the Android device. Correspondingly, The multi-screen framework module of the Android device receives the instruction information for registering cursor position monitoring and registers cursor position monitoring.

After the multi-screen framework module registers cursor position monitoring, it can monitor the cursor position.

It should be noted that the keyboard and mouse virtualization capability module of the Android device is based on the instruction information for starting the keyboard and mouse service. The order between registering Uinput and sending the instruction information for registering cursor position monitoring is not limited. That is to say, the embodiment of the present application The execution order of the above S805 and S808 is not limited.

S808. The keyboard and mouse virtualization capability module of the Android device sends the registration result B to the keyboard and mouse business module of the Android device. Correspondingly, the keyboard and mouse business module of the Android device receives the registration result B.

Registration result B can be used to indicate whether the registration for cursor position monitoring is successful. The registration result can be success or failure. In one embodiment, success and failure may be represented by binary identifiers. For example, 1 indicates success and 0 indicates failure.

S809. When the keyboard and mouse service is supported, the keyboard and mouse business module of the Android device sends instruction information for registering drag and drop monitoring to the drag and drop management module of the Android device. Correspondingly, the keyboard and mouse virtualization capability module of the Android device receives the registration. Instructions for drag monitoring.

It should be noted that when the keyboard and mouse service is supported, the order in which the keyboard and mouse business module of the Android device sends the instruction information for starting the keyboard and mouse service and the instruction information for registering drag and drop monitoring is not limited. That is to say, The embodiment of the present application does not limit the execution order of the above S804 and S809.

S810. The drag management module of the Android device sends the instruction information for registering drag and drop monitoring to the multi-screen framework module of the Android device. Correspondingly, the multi-screen framework module of the Android device receives the instruction information for registering drag and drop monitoring.

S811. The keyboard and mouse business module of the Android device saves the processing result A, where the processing result A includes the results of whether the keyboard and mouse service is enabled, whether the Uinput registration is successful, and whether the cursor position monitoring registration is successful.

For example, the processing result A may include that the keyboard and mouse service is started, Uinput is successfully registered, and cursor position monitoring is successfully registered.

S812. The keyboard and mouse business module of the Android device sends the processing result A to the keyboard and mouse business module of the PC. Correspondingly, the keyboard and mouse business module of the PC receives the processing result A.

S813. The keyboard and mouse business module of the PC sends instruction information to enable the keyboard and mouse service to the keyboard and mouse virtualization capability module of the PC. Correspondingly, the keyboard and mouse business module of the PC receives the instruction information to enable the keyboard and mouse service.

The above-mentioned S802 and S813 are sent in parallel by the keyboard and mouse business module of the PC, so the above-mentioned S802~S812 and S813~S818 are executed in parallel.

S814. The PC's keyboard and mouse virtualization capability module registers keyboard and mouse event monitoring based on the instruction information for starting the keyboard and mouse service.

The PC's keyboard and mouse virtualization capability module registers keyboard and mouse event monitoring, and can monitor keyboard and mouse events. For example, the PC's keyboard and mouse virtualization capability module can monitor keyboard presses and mouse movements, clicks, drags, and other operations.

S815. The keyboard and mouse virtualization capability module of the PC sets keyboard and mouse event interception based on the instruction information to enable the keyboard and mouse service.

When the keyboard and mouse travel through, the keyboard and mouse events are intercepted on the PC side, and the response to the keyboard and mouse events is executed by the Android device. Therefore, the keyboard and mouse virtualization capability module of the PC sets up the keyboard and mouse event interception to intercept the keyboard and mouse events after the keyboard and mouse travel through.

The embodiment of the present application does not limit the execution order of the above S814 and S815.

S816. The keyboard and mouse virtualization capability module of the PC saves the processing result B, where the processing result B includes the results of whether the registration of the keyboard and mouse software is successful and whether the setting of keyboard and mouse event interception is successful.

For example, the processing result B may include successful registration of keyboard and mouse components and success in setting keyboard and mouse event interception.

S818. The keyboard and mouse virtualization capability module of the PC sends the processing result B to the keyboard and mouse business module of the PC. Correspondingly, the keyboard and mouse business module of the PC receives the processing result B.

S818. The keyboard and mouse business module of the PC sends the processing result B to the keyboard and mouse business module of the Android device. Correspondingly, the keyboard and mouse business module of the Android device receives the processing result B.

S819, the keyboard and mouse business module of the PC and the keyboard and mouse business module of the Android device can compare the processing result A with the processing result B to determine whether the keyboard and mouse connection is successful.

If the results in processing result A and processing result B are both successful, the keyboard and mouse business module of the PC and the keyboard and mouse business module of the Android device can determine that the keyboard and mouse connection is successful. If at least one of the results in processing result A and processing result B is a failure, the keyboard and mouse business module of the PC and the keyboard and mouse business module of the Android device can determine that the keyboard and mouse connection is unsuccessful.

If the keyboard and mouse business module of the PC and the keyboard and mouse business module of the Android device are not successfully connected, both will return to the initialization state, that is, the above registration process will be re-executed.

The keyboard and mouse connection method provided by the embodiment of the present application enables keyboard and mouse connection between different devices during data transmission to prepare for subsequent data transmission, which is conducive to the smooth progress of data transmission.

It should be noted that the keyboard and mouse connection between a PC and two Android devices is done in the same way, which is the process shown in method 800 above.

After confirming that the keyboard and mouse connection is successful through the above method 800, the PC and the Android device can transmit data.

Before introducing data transmission, let us first introduce a method for detecting mouse traversal. PC and/or Android devices can monitor mouse traversal based on this method.

Exemplarily, FIG. 9 shows a schematic flow chart of a mouse crossing detection method 900. As shown in Figure 9, the method 900 may include the following steps:

S901. The keyboard virtualization capability module of the PC obtains the mouse position.

The mouse position is the coordinates of the mouse on the screen. The PC's keyboard virtualization capability module can create a two-dimensional coordinate system on the screen. The coordinates of the mouse in the two-dimensional coordinate system are the mouse positions. The mouse position can be represented by (XRaw, YRaw), but the embodiment of the present application is not limited to this.

Exemplarily, FIG. 10 shows a schematic diagram of establishing a screen coordinate system. As shown in Figure 10, screen OABC establishes a coordinate system with point O as the origin, the straight line where OA is located as the X-axis, and the straight line where OC is located as the Y-axis. The screen resolution is 1920*1080, the length of line segment OA is equal to the length of line segment CB, which is equal to 1920, the length of line segment OC is equal to the length of line segment AB, which is equal to 1080, then in the coordinate system, the coordinates of point O are (0,0), A The coordinates of point B are (1920,0), the coordinates of point B are (1920,1080), and the coordinates of point C are (0,1080). The mouse position is the coordinates of the mouse in the coordinate system. For example, the mouse position can be (1920,960).

S902. When the PC's keyboard virtualization capability module detects mouse movement, it obtains the mouse displacement.

Mouse displacement is the distance the mouse moves. Mouse displacement can be expressed as (Lx, Ly). Lx and Ly may be positive values or negative values, which are not limited in the embodiments of the present application.

S903. The keyboard virtualization capability module of the PC calculates the position of the mouse after movement based on the mouse position and mouse displacement.

The position of the mouse after movement can be expressed by (curX, curY). The position of the mouse after movement can be expressed by the following formula: curX=XRaw+Lx; curY=YRaw+Ly.

S904. The keyboard virtualization capability module of the PC determines whether the position of the mouse after movement exceeds the screen.

If curX is less than the minimum value of the screen on the X-axis or greater than the maximum value of the screen on the X-axis, the PC's keyboard virtualization capability module can determine that the mouse exceeds the screen. If curY is less than the minimum value of the screen on the Y-axis or greater than the maximum value of the screen on the Y-axis, the PC's keyboard virtualization capability module can determine that the mouse exceeds the screen.

If the moved position of the mouse exceeds the screen, the mouse crossing can be determined, that is, S905 is executed. If the position of the mouse after movement does not exceed the screen, the position after movement of the mouse can be determined as the current position, and the mouse movement continues to be obtained, that is, S902 is executed.

S905. If the position of the mouse after movement exceeds the screen, the keyboard virtualization capability module of the PC can determine the mouse traversal.

The PC can also determine the crossing direction of the mouse, for example, the crossing direction is left crossing, right crossing, up crossing, or down crossing.

Illustratively, in the example shown in FIG. 10 above, if curX is less than 0, the PC can determine that the crossing direction of the mouse is left crossing. If curX is greater than 1920, the PC can determine that the mouse's crossing direction is right crossing. If curY is less than 0, the PC's keyboard virtualization capability module can determine that the mouse's traversing direction is up. If curX is greater than 1080, the PC can determine that the mouse's crossing direction is downward crossing.

The mouse crossing detection method provided by the embodiment of the present application can determine whether the mouse exceeds the screen through the mouse position and mouse displacement, and determine the crossing direction, which is beneficial to improving the accuracy of detecting mouse crossing.

The data transmission method provided by the embodiment of this application will be introduced below.

Exemplarily, FIG. 11 shows a schematic flow chart of a data transmission method 1100. The method 1100 can be applied to a communication system including a PC and an Android device, where the Android device includes Android device 1 and Android device 2 . For example, in the above communication system 100, the PC is the computer 101, but the embodiment of the present application is not limited thereto. The software architecture diagram of the PC can be shown in Figure 6, and the software architecture diagram of the Android device can be shown in Figure 7. The embodiments of the present application are not limited thereto.

The method 1100 may include the following steps:

S1101. The application of Android device 1 detects the user's operation of dragging out data.

The application program may be at least one of a gallery, a chat, or a file manager, but the embodiment of the present application is not limited to the gallery, a chat, or a file manager. The operation of the user dragging out the data may be the operation of the user dragging the data through the mouse. The data dragged out by the user can be pictures, files, texts, compressed packages, emails, music, videos, etc. It can be understood that the data dragged out by the user can be any data that supports drag and drop, and the embodiments of this application do not do this. limited.

The Android device 1 may be the above-mentioned mobile phone 102 or tablet 103, which is not limited in the embodiment of the present application.

Illustratively, in the example shown in FIG. 5 above, the Android device 1 may be a tablet 103, the application may be a file manager, and the file manager detects the user's operation of dragging out a document.

S1102. In response to the user's operation of dragging out data, the application program of Android device 1 sends data dragging information to the dragging framework of Android device 1. Correspondingly, the dragging framework of Android device 1 receives the data dragging information.

S1103. The drag and drop framework of Android device 1 sends data drag to the drag and drop module of Android device 1 based on the information of data drag. Correspondingly, the drag module of Android device 1 receives the information dragged out by the data.

S1104. The Android device 1 drag and drop module obtains the universal resource identifier (URI) of the dragged data based on the information dragged out.

URI is used to represent the data to be operated on.

S1105. The application of Android device 1 receives the user's operation of dragging out of the screen.

The application of Android device 1 may determine whether the user drags data off the screen based on the above method 900 .

S1106. The application program of Android device 1 sends a drag-out instruction to the drag module of the PC. Correspondingly, the drag module of the PC receives the instruction to drag out the screen.

The PC may be the above-mentioned computer 101, but the embodiment of the present application is not limited thereto.

The command of dragging out of the screen is used to inform the PC's drag module that the data has been dragged into the PC. The instruction to drag out of the screen can be expressed by an identification bit, but the embodiment of the present application is not limited to this. For example, the instruction to drag out the screen may include an identification bit 1 to indicate that the data has been dragged into the PC.

It should be noted that S1106 is a simplified way of writing. The application program of Android device 1 cannot communicate directly with the drag and drop module of PC. The application program of Android device 1 can send the drag-and-drop command of Android device 1 to the drag-and-drop module of Android device 1. The frame is transmitted from the drag frame of Android device 1 to the drag module of Android device 1, and then the drag module of Android device 1 sends the instruction of dragging out of the screen to the communication module of Android device 1. After the communication module of the Android device 1 receives the instruction of dragging out of the screen, it can transmit it to the communication module of the PC. Finally, the communication module of the PC sends the instruction of dragging out of the screen to the drag module of the PC.

S1107. The drag-and-drop module of the PC can record the drag-and-drop status based on the command of dragging out of the screen.

The dragging status can be any one of dragging completed, dragging to PC, dragging to Android device 1 or dragging to Android device 2.

The drag-and-drop module of PC is based on the command of dragging out of the screen, and can record the drag-and-drop status as drag-and-drop to PC. If the drag-and-drop module of the PC detects the user's operation of dragging in data, the drag-and-drop status can be recorded (or updated) as drag-and-drop completion. If the drag module of the PC detects the user's dragging operation out of the screen, the drag status can be recorded (or updated) as drag to Android device 2.

S1108. The drag module of the PC detects the user's drag operation out of the screen.

S1109. The drag and drop module of the PC can update the drag and drop status in response to the user's dragging operation out of the screen.

In response to the user's dragging operation out of the screen, the PC's drag module can update the drag status to drag to Android device 2.

S1110. The drag module of the PC sends the instruction information of dragging out of the screen to the drag module of the Android device 2. Correspondingly, the drag module of the Android device 2 receives the instruction information of dragging out of the screen.

It should be noted that S1110 is a simplified way of writing. The drag and drop module of the PC cannot directly communicate with the drag and drop module of the Android device 2. The drag and drop module of the PC can first send the instruction information of dragging out of the screen to the communication of the PC. module, then the communication module of the PC sends the instruction information for dragging out of the screen to the communication module of Android device 2, and finally the communication module of Android device 2 sends the instruction information for dragging out of the screen to the drag module of Android device 2.

In the above examples shown in Figure 2, Figure 3, Figure 4 or Figure 5, if Android device 1 is a mobile phone 102, then Android device 2 is a tablet 103; if Android device 1 is a tablet 103, then Android device 2 is a mobile phone 102 , but the embodiment of the present application is not limited to this.

S1111. Based on the instruction information of dragging out of the screen, the drag module of Android device 2 calls the interface provided by the drag framework of Android device 2 to initiate dragging, and draws an icon according to the image (bitmap) corresponding to the dragged out data.

The drag and drop module of Android device 2 calls the drag and drop framework to support the drag and drop function. The drag-and-drop module of Android device 2 can display an icon at the mouse location based on the image (bitmap) corresponding to the dragged data.

The drag and drop module of Android device 2 can preset multiple data types and their corresponding bitmaps. For example, data types may include pictures, files, text, videos, and music.

The drag and drop module of Android device 2 can determine the data type of the dragged data based on the instruction information of dragging out of the screen, and determine the bitmap based on the data type. The drag and drop module of Android device 2 can display icons at the mouse location based on bitmap.

The icon may be the drag icon B in Figure 2, Figure 3, Figure 4 or Figure 5, but the embodiment of the present application is not limited thereto.

S1112. The drag frame block of Android device 2 determines whether it is dragged into the draggable area.

The draggable area refers to the area that allows data to be dragged in. If the user drags data into the draggable area, the application can display the dragged data in the draggable area. If the user does not drag the data into the draggable area, the application does not allow the data to be dragged in, and the user's drag operation fails.

S1113. If dragged into the draggable area, the dragging framework of Android device 2 sends business callback information to the application program of Android device 2. Correspondingly, the application program of Android device 2 receives the business callback information. The application of Android device 2 performs business callback based on the business callback information, that is, executes the business after being dragged in.

The data transmission method provided by the embodiment of the present application can support users to drag and drop from Android device 1 to Android device 2 via PC, realizing data transmission across multiple devices. There is no need to drag and drop from Android device 1 to PC first, and then from PC to Android device 1. Dragging and dropping to an Android device 2 reduces PC transfers, helps improve the efficiency of data transmission, avoids cumbersome operations, and improves user experience.

If the user drags the dragged data from Android device 1 to Android device 2 via PC, Android device 2 can obtain the data from Android device 1. The embodiments of this application provide two methods of obtaining data.

The first method of obtaining data is that Android device 1 first sends the data to the PC, and the PC then sends the data to Android device 2.

By way of example, FIG. 12 shows a schematic flowchart of a method 1200 for obtaining data. As shown in Figure 12, the method 1200 includes the following steps:

S1201. The application of Android device 2 detects the user's operation of dragging in data.

The application program may be at least one of a gallery, a chat, or a file manager, but the embodiment of the present application is not limited to the gallery, a chat, or a file manager. The application program of Android device 1 and the application program of Android device 2 may be the same or different, and this is not limited in the embodiment of the present application.

Illustratively, in the above example shown in Figure 3, the application program of the Android device 2 is a chat application.

S1202. In response to the user's operation of dragging in data, the application program of Android device 2 sends information requesting data to the drag module of Android device 2. Correspondingly, the drag module of Android device 2 receives the information requesting data.

The information for requesting data is used to request the dragged-in data from the drag-and-drop module of Android device 2.

It should be noted that in response to the user's operation of dragging in data, the application program of Android device 2 can first send the information requesting data to the drag and drop framework of Android device 2, and then the drag and drop framework of Android device 2 will send the information requesting data. Drag and drop module sent to Android device 2.

S1203. Based on the information of the requested data, the drag and drop module of the Android device 2 sends the information of the requested data to the drag and drop module of the PC. Correspondingly, the drag and drop module of the PC receives the information of the requested data.

It should be noted that based on the requested data information, the drag and drop module of Android device 2 can first request the The communication module sends information requesting data, and then the communication module of the Android device 2 sends the information requesting data to the communication module of the PC. Finally, the communication module of the PC sends the information requesting data to the drag module of the PC.

S1204. Based on the information of the request data, the drag and drop module of the PC determines whether it is a cross-PC drag and drop operation according to the drag and drop status.

In the above method 900, the dragging state is dragging to the Android device 2, and the dragging module of the PC can determine that the dragging operation is a cross-PC dragging operation.

S1205. The drag and drop module of the PC sends information requesting data to the drag and drop module of Android device 1. Correspondingly, the drag and drop module of Android device 1 receives the information requesting data.

It should be noted that the drag and drop module of the PC can first send the information requesting data to the communication module of the PC, and then the communication module of the PC sends the information requesting the data to the communication module of the Android device 1, and finally the communication module of the Android device 1 Send a message requesting data to the drag and drop module of Android device 1.

S1206. The drag and drop module of Android device 1 determines the drag and drop data based on the URI of the data based on the information of the requested data.

The drag data may be a binary string, but the embodiment of the present application is not limited to this.

S1207. The drag and drop module of Android device 1 sends drag and drop data to the drag and drop module of the PC. Correspondingly, the drag and drop module of the PC receives the drag and drop data.

It can be understood that the drag and drop module of Android device 1 can first send drag and drop data to the communication module of the PC, and then the communication module of the PC sends the drag and drop data to the communication module of Android device 2, and finally the communication module of Android device 2 Send drag data to the drag module of Android device 2.

S1208. The drag and drop module of the PC is based on the drag and drop data and saves the drag and drop data.

S1209. The drag and drop module of the PC sends the drag and drop data to the communication module of the Android device 2. Correspondingly, the communication module of the Android device 2 receives the drag and drop data.

It can be understood that the drag and drop module of the PC can first send the drag and drop data to the communication module of the PC, and then the communication module of the PC sends the drag and drop data to the communication module of the Android device 2 .

S1210. The communication module of the Android device 2 sends the data reception success message to the drag and drop module of the Android device 2. Correspondingly, the drag and drop module of the Android device 2 receives the data reception success message.

The information of successful data reception is used to indicate that the communication module of the Android device 2 has successfully received the communication data.

The information of successful data reception may also include drag and drop data, so that the drag and drop module of the Android device 2 can obtain the drag and drop data.

S1211. The drag-and-drop module of Android device 2 sends drag-and-drop data to the application program based on the information that data reception is successful. Correspondingly, the application program sends drag-and-drop data.

Applications can also display drag data in the interface.

S1212. Based on the information of successful data reception, the drag-and-drop module of the Android device 2 can also send the information of successful data reception to the drag-and-drop module of the PC. Correspondingly, the drag-and-drop module of the PC receives the information of successful data reception.

The embodiment of the present application does not limit the execution order of S1211 and S1212.

S1213. The drag and drop module of the PC clears the drag and drop data based on the information that data reception is successful.

The PC drag and drop module clears the drag and drop data based on the information of successful data reception, and can also update the drag and drop status to drag and drop completed.

According to the method of obtaining data provided by the embodiment of this application, when Android device 2 requests to obtain the dragged-in data, Android device 1 can first transmit the data to the PC, and then transmit the data from the PC to Android device 2, using the PC for data transfer, which is equivalent to First Drag data from Android device 1 to PC, and then drag data from PC to Android device 2. You can reuse the existing data transmission method with minimal changes, which is conducive to application promotion.

Optionally, if the communication module of Android device 2 fails to receive drag and drop data, it can request data again from the drag and drop module of PC. The drag and drop module of PC can send data to the communication module of Android device 2 based on the saved data. Saving the steps to obtain data will help improve data transmission efficiency.

It can be understood that if the user drags data from Android device 2 to Android device 1 via PC, the above method 1200 can also be used, as long as Android device 1 is changed to Android device 2, and Android device 2 is changed to Android device 1 That’s it.

In the second method of obtaining data, Android device 1 directly sends data to Android device 2, that is, the data does not pass through the PC.

By way of example, FIG. 13 shows a schematic flowchart of a method 1300 for obtaining data. As shown in Figure 13, the method 1300 may include the above-mentioned S1201 to S1205, and may also include the following steps:

S1301. Based on the request data information, the drag module of Android device 1 sends instruction information for establishing a transmission channel to the communication module of Android device 1. Correspondingly, the communication module of Android device 1 receives the instruction information for establishing a transmission channel.

The instruction information for establishing a transmission channel is used to instruct the communication module of Android device 1 and the communication module of Android device 2 to establish a transmission channel.

S1302. The communication module of Android device 1 establishes a data transmission channel with the communication module of Android device 2 based on the instruction information for establishing a transmission channel.

S1303. After the data transmission channel is established, the drag and drop module of Android device 1 sends drag and drop data to the communication module of Android device 1. Correspondingly, the communication module of Android device 1 receives the drag and drop data.

S1304. The communication module of Android device 1 sends drag and drop data to the communication module of Android device 2 through the data transmission channel. Correspondingly, the communication module of Android device 2 receives the drag and drop data.

S1305. The communication module of the Android device 2 sends the data reception success message to the drag and drop module of the Android device 2. Correspondingly, the drag and drop module of the Android device 2 receives the data reception success message.

S1306. The drag-and-drop module of Android device 2 sends drag-and-drop data to the application program based on the information that data reception is successful. Correspondingly, the application program sends drag-and-drop data.

Applications can also display drag data in the interface.

S1307. Based on the information of successful data reception, the drag-and-drop module of Android device 2 can also send the information of successful data reception to the drag-and-drop module of the PC. Correspondingly, the drag-and-drop module of the PC receives the information of successful data reception.

The embodiment of the present application does not limit the execution order of S1306 and S1307.

S1308. The drag and drop module of the PC updates the drag and drop status based on the information of successful data reception.

Based on the information of successful data reception, the PC's drag and drop module updates the drag and drop status to drag and drop completed.

S1309. The drag and drop module of the PC sends a drag and drop completion message to the drag and drop module of the Android device 1. Correspondingly, the drag and drop module of the Android device 1 receives the drag and drop completion message.

The drag completion message is used to indicate that the drag has been completed.

S1310. Based on the drag completion message, the drag module of Android device 1 sends the instruction information of the disassembly channel to the communication module of Android device 1. Correspondingly, the communication module of Android device 1 receives the instruction information of the dismantling channel, and dismantles the instruction information based on the disassembly. Channel indication information, remove the data transmission channel.

The instruction information to remove the channel is used to instruct the communication module of the Android device 1 to remove the channel.

According to the method of obtaining data provided by the embodiment of this application, when Android device 2 requests to obtain the dragged-in data, Android device 1 can transmit the data to Android device 2 through the data transmission channel between Android device 1 and Android device 2, without the need for a PC. Data transfer deliberately reduces the data transmission process and improves data transmission efficiency.

The size of the serial numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.

The method provided by the embodiment of the present application is described in detail above with reference to Figures 1 to 13. The device provided by the embodiment of the present application will be described in detail below with reference to Figures 14 and 15.

Figure 14 shows a schematic diagram of a terminal device 1400 provided by an embodiment of the present application. The terminal device 1400 includes: a processing module 1410 and a transceiver module 1420.

In a possible implementation, the terminal device 1400 can perform the steps performed by the Android device 2 in the above embodiment.

Among them, the processing module 1410 is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the third device to the second device through the mouse, and the third device and the second device support keyboard and mouse traversal. , the second device supports keyboard and mouse traversal; the transceiver module 1420 is configured to: in response to the first operation, send information requesting target data to the third device through the second device; and receive target data from the third device.

In another possible implementation, the terminal device 1400 can perform the steps performed by the Android device 1 in the above embodiment.

Among them, the processing module 1410 is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the second device to the first device through the mouse, and the second device supports keyboard and mouse traversal, and the second The device and the first device support keyboard and mouse traversal; the transceiver module 1420 is configured to: in response to the first operation, receive information requesting target data from the first device through the second device; and send the target data to the first device.

In another possible implementation, the terminal device 1400 can perform the steps performed by the PC in the above embodiment.

Among them, the processing module 1410 is used to: detect the user's first operation, the first operation is used to move the identification of the target data from the third device to the first device through the mouse, the third device supports keyboard and mouse traversal, and the third device A device supports keyboard and mouse traversal; the transceiver module 1420 is configured to: in response to the first operation, receive information requesting target data from the first device; and send information requesting target data to a third device.

It should be understood that the terminal device 1400 here is embodied in the form of a functional module. The term "module" as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor, or a group of processors) for executing one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality. In an optional example, those skilled in the art can understand that the terminal device 1400 can be specifically the Android device 2, PC or Android device 1 in the above method embodiment, or the Android device 2, PC or Android device 1 in the above method embodiment. The functions of the Android device 1 can be integrated in the terminal device 1400, and the terminal device 1400 can be used to perform various processes and/or steps corresponding to the Android device 2, PC or Android device 1 in the above method embodiments. To avoid duplication, here No longer.

The above terminal device 1400 has the function of implementing the corresponding steps performed by the Android device 2, PC or Android device 1 in the above method embodiment; the above functions can be implemented by hardware, or can also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

In this embodiment of the present application, the terminal device 1400 in Figure 14 may also be a chip or a chip system, such as a system on chip (SoC).

Figure 15 is a schematic block diagram of another terminal device 1500 provided by an embodiment of the present application. The terminal device 1500 includes a processor 1510, a transceiver 1520 and a memory 1530. Among them, the processor 1510, the transceiver 1520 and the memory 1530 communicate with each other through internal connection paths. The memory 1530 is used to store instructions, and the processor 1520 is used to execute the instructions stored in the memory 1530 to control the transceiver 1520 to send signals and /or receive a signal.

It should be understood that the terminal device 1500 can be specifically the Android device 2, PC or Android device 1 in the above method embodiment, or the functions of the Android device 2, PC or Android device 1 in the above method embodiment can be integrated into the terminal device 1500. , the terminal device 1500 can be used to execute various steps and/or processes corresponding to the Android device 2, PC or Android device 1 in the above method embodiment. Optionally, the memory 1530 may include read-only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 1510 can be used to execute instructions stored in the memory, and when the processor executes the instructions, the processor can execute various steps and/or processes corresponding to the terminal device in the above method embodiment.

It should be understood that in this embodiment of the present application, the processor 1510 may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), or application specific integrated circuits (ASICs). ), 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, etc.

During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor executes the instructions in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

This application also provides a computer-readable storage medium, which is used to store a computer program. The computer program is used to implement the method corresponding to the Android device 2, PC or Android device 1 in the above method embodiment.

This application also provides a chip system, which is used to support the Android device 2, PC or Android device 1 in the above method embodiment to implement the functions shown in the embodiment of this application.

This application also provides a computer program product. The computer program product includes a computer program (which can also be called a code, or an instruction). When the computer program is run on a computer, the computer can execute the steps shown in the above method embodiments. Corresponding method for Android device 2, PC or Android device 1.

Those of ordinary skill in the art can appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with 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 specific application, but such implementations should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and modules described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of modules is only a logical function division. In actual implementation, there may be other division methods. For example, multiple modules or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, indirect coupling or communication connection of devices or modules, and may be in electrical, mechanical or other forms.

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

In addition, each functional module in each embodiment of the present application can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

The above are only specific implementation modes of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes within the technical scope disclosed in the embodiments of the present application. or replacement, all should be covered by the protection scope of the embodiments of this application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

A data transmission method, characterized by including:

The first device detects the user's first operation, which is used to move the identification of the target data from the third device to the first device through the second device through the mouse, and the third device and the third device The second device supports keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal;

In response to the first operation, the first device sends information requesting the target data to the third device through the second device;

The first device receives the target data from the third device.
The method of claim 1, wherein the first device receiving the target data from the third device includes:

The first device establishes a data transmission channel with the third device;

The first device receives the target data from the third device through the data transmission channel.
The method according to claim 2, characterized in that, after the first device receives the target data from the third device through the data transmission channel, the method further includes:

The first device removes the data transmission channel.
The method of claim 1, wherein the first device receiving the target data from the third device includes:

The first device receives the target data from the third device through the second device.
The method according to any one of claims 1 to 4, characterized in that, before sending the information requesting the target data to the third device through the second device, the method further includes:

The first device determines whether the area into which the mouse drags the identification of the target data is a preset area;

The sending of information requesting the target data through the second device to the third device includes:

When the area into which the identifier of the target data is dragged is the preset area, the first device sends information requesting the target data to the third device through the second device.
The method according to any one of claims 1 to 5, characterized in that the target data includes at least one of the following:

Text data, image data, document data, email data, compressed package data, music data or video data.
A data transmission method, characterized by including:

The third device detects the user's first operation, which is used to move the identification of the target data from the third device to the first device through the second device through the mouse, and the third device and the third device The second device supports keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal;

In response to the first operation, the third device receives, through the second device, information requesting the target data from the first device;

The third device sends the target data to the first device.
The method of claim 7, wherein the third device sends the target data to the first device, including:

The third device establishes a data transmission channel with the first device;

The third device sends the target data to the first device through the data transmission channel.
The method according to claim 8, characterized in that when the third device uses the data transmission channel After sending the target data to the first device, the method further includes:

The third device removes the data transmission channel.
The method of claim 7, wherein the third device sends the target data to the first device, including:

The third device sends the target data to the first device through the second device.
The method according to any one of claims 7 to 10, characterized in that, before receiving the information requesting the target data from the first device through the second device, the method further includes:

In response to the first operation, the third device obtains the universal resource identifier URI identified by the target data;

The third device determines the data corresponding to the URI as the target data.
The method according to any one of claims 7 to 11, characterized in that the target data includes at least one of the following:

Text data, image data, document data, email data, compressed package data, music data or video data.
A data transmission method, characterized by including:

The second device detects the user's first operation, which is used to move the identification of the target data from the third device to the first device through the second device through the mouse, and the third device is connected to the first device. The second device supports keyboard and mouse traversal, and the second device and the first device support keyboard and mouse traversal;

In response to the first operation, the second device receives information from the first device requesting the target data;

The second device sends information requesting the target data to the third device.
The method according to claim 13, characterized in that, before the second device sends the information requesting the target data to the third device, the method further includes:

The second device determines the movement state as moving from the third device to the first device in response to the first operation;

The second device sends information requesting the target data to the third device, including:

The second device sends information requesting the target data to the third device based on the information requesting the target data and the movement status.
The method according to claim 13 or 14, characterized in that the method further includes:

The second device receives the target data from the third device;

The second device sends the target data to the first device.
The method according to any one of claims 13 to 15, characterized in that the target data includes at least one of the following:

Text data, image data, document data, email data, compressed package data, music data or video data.
A terminal device, characterized in that it includes: a processor, the processor is coupled to a memory, the memory is used to store a computer program, and when the processor calls the computer program, the terminal device is caused to execute as follows: Claims 1 to 6, performing claims 7 to 12 or performing the method according to any one of claims 13 to 16.
A computer-readable storage medium, characterized in that it is used to store a computer program, and the computer program includes a computer program for implementing any one of claims 1 to 6, claims 7 to 12, or claims 13 to 16. instructions for the method described.
A computer program product, characterized in that the computer program product includes computer program code. When the computer program code is run on a computer, the computer implements claims 1 to 6, claims 7 to 12, or A method as claimed in any one of claims 13 to 16.