A cross-device data transmission method and device

Abstract

The one or more embodiments of the specification provide a cross-device data transmission method and device, the method comprising: generating, by a first client of a target application deployed on a first device, a resource acquisition request for a second device on which a second client of the target application is deployed; sending the resource acquisition request to a server of the target application to send a resource selection notification to the second client by the server of the target application; and receiving, by the first client, a target resource returned by the second client in response to the resource selection notification.

Description

Technical Field

[0001] This specification relates to the field of data transmission through one or more embodiments, and more particularly to a method and apparatus for data transmission across devices. Background Technology

[0002] Cross-device data transfer refers to the transfer of locally maintained resources from one device to another.

[0003] In related technologies, to achieve cross-device data transmission, users can repeatedly send and transfer the resources to be transmitted using communication software; alternatively, users can pre-implement trusted interconnection between devices, enabling two trusted devices to share service resources. Of these two implementation methods, the former is highly complex and inefficient; the latter's trusted interconnection requires devices to be uniformly equipped with specific hardware, resulting in numerous constraints and significant implementation difficulties. Summary of the Invention

[0004] In view of this, one or more embodiments of this specification provide a cross-device data transmission method and apparatus, which can solve the shortcomings existing in the related art.

[0005] To achieve the above objectives, one or more embodiments of this specification provide the following technical solutions:

[0006] According to a first aspect of one or more embodiments of this specification, a method for data transmission across devices is provided, the method comprising:

[0007] A resource acquisition request for a second device is generated using a first client of the target application deployed on a first device, wherein a second client of the target application is deployed on the second device.

[0008] The resource acquisition request is sent to the server of the target application, so that the server of the target application sends a resource selection notification to the second client; wherein, the resource selection notification is used to instruct the second client to: display a resource selection interface for the resources maintained by the second device, and return the target resource selected through the resource selection interface to the first client;

[0009] The first client receives the target resource returned by the second client in response to the resource selection notification.

[0010] According to a second aspect of one or more embodiments of this specification, a method for data transmission across devices is provided, the method comprising:

[0011] The second client of the target application deployed on the second device receives a resource selection notification sent by the server of the target application; wherein the resource selection notification is sent by the server of the target application in response to a resource acquisition request generated by the first client of the target application deployed on the first device.

[0012] In response to the resource selection notification, the target resource selected from the second device through the second client is returned to the first client.

[0013] According to a third aspect of one or more embodiments of this specification, a cross-device data transmission apparatus is provided, the apparatus comprising:

[0014] Generation unit: Generates a resource acquisition request for a second device by using a first client of the target application deployed on a first device, wherein a second client of the target application is deployed on the second device;

[0015] Sending unit: sends the resource acquisition request to the server of the target application, so that the server of the target application sends a resource selection notification to the second client; wherein, the resource selection notification is used to instruct the second client to: display a resource selection interface for the resources maintained by the second device, and return the target resource selected through the resource selection interface to the first client;

[0016] Receiving unit: Receives the target resource returned by the second client in response to the resource selection notification through the first client.

[0017] According to a fourth aspect of one or more embodiments of this specification, a cross-device data transmission apparatus is provided, the apparatus comprising:

[0018] Receiving unit: Receives a resource selection notification sent by the server of the target application through a second client of the target application deployed on the second device; wherein the resource selection notification is sent by the server of the target application in response to a resource acquisition request generated by a first client of the target application deployed on the first device;

[0019] Return unit: In response to the resource selection notification, the target resource selected from the second device through the second client is returned to the first client.

[0020] According to a fifth aspect of one or more embodiments of this specification, an electronic device is provided, comprising:

[0021] processor;

[0022] Memory used to store processor-executable instructions;

[0023] The processor implements the steps of the method as described in the first or second aspect by running the executable instructions.

[0024] According to a sixth aspect of one or more embodiments of this specification, a computer-readable storage medium is provided that stores computer instructions thereon, which, when executed by a processor, implement the steps of the method as described in the first or second aspect.

[0025] According to a seventh aspect of one or more embodiments of this specification, a computer program is provided that, when executed by a processor, implements the steps of the method as described in the first or second aspect.

[0026] As can be seen from the above technical solutions, the cross-device data transmission method provided in one or more embodiments of this specification, on the one hand, achieves the acquisition of target resources through a first client of the target application deployed on a first device, a second client of the target application deployed on a second device, and a server of the target application, thereby realizing data transmission between devices without configuring specific hardware; on the other hand, through the resource acquisition request generated by the first client of the target application, the server of the target application sends a resource selection notification to the second client, and then, based on the response of the second client of the target application to the resource selection notification, returns the target resources maintained by the second device to the first client. The above process only involves the target application, without requiring the user to switch between different applications, and since the second client can respond to the resource selection notification sent by the server and return the target resources to the first client, the user on the second client does not need to focus on operations such as selection on the first client, thereby simplifying the complexity of the operation and improving the efficiency of data transmission. Attached Figure Description

[0027] Figure 1a This is an exemplary embodiment of an architecture diagram of a cross-device data transmission system.

[0028] Figure 1b This is an exemplary embodiment of an architecture diagram of another cross-device data transmission system.

[0029] Figure 2 This is a flowchart illustrating a cross-device data transmission method as provided in an exemplary embodiment.

[0030] Figure 3a This is a schematic diagram of a communication interface for a first client provided in an exemplary embodiment.

[0031] Figure 3b This is a schematic diagram of another communication interface of a first client provided in an exemplary embodiment.

[0032] Figure 3cThis is a schematic diagram of inserting a target resource into a first interface, provided as an exemplary embodiment.

[0033] Figure 4a This is a schematic diagram of a communication interface for a second client provided in an exemplary embodiment.

[0034] Figure 4b This is a schematic diagram of a resource selection notification details interface provided in an exemplary embodiment.

[0035] Figure 4c This is a schematic diagram of an album interface provided in an exemplary embodiment.

[0036] Figure 5 This is a schematic diagram of a method for returning a target resource provided in an exemplary embodiment.

[0037] Figure 6a This is a schematic diagram illustrating another resource selection notification detail provided in an exemplary embodiment.

[0038] Figure 6b This is a schematic diagram of a document storage interface provided in an exemplary embodiment.

[0039] Figure 7 This is a flowchart of another cross-device data transfer method provided in an exemplary embodiment.

[0040] Figure 8 This is a schematic diagram illustrating yet another resource selection notification detail provided in an exemplary embodiment.

[0041] Figure 9 This is a schematic diagram of an editing interface provided in an exemplary embodiment.

[0042] Figure 10 This is a schematic structural diagram of a device provided in an exemplary embodiment.

[0043] Figure 11 This is a block diagram of a cross-device data transmission apparatus provided in an exemplary embodiment.

[0044] Figure 12 This is a block diagram of another cross-device data transmission apparatus provided in an exemplary embodiment. Detailed Implementation

[0045] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0046] It should be noted that the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification in other embodiments. In some other embodiments, the methods may include more or fewer steps than described in this specification. Furthermore, a single step described in this specification may be broken down into multiple steps in other embodiments; and multiple steps described in this specification may be combined into a single step in other embodiments.

[0047] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0048] To further illustrate one or more embodiments of this specification, the following embodiments are provided:

[0049] Figure 1a This is an exemplary embodiment of an architecture diagram of a cross-device data transmission system, such as... Figure 1a As shown in the diagram, the architecture includes: a first device 11, a server 12, and a second device 13.

[0050] The first device 11 and the second device 13 can be any type of electronic device that the user can use, such as mobile phones, tablets, laptops, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smartwatches, etc.), etc., and this specification does not limit them. The two devices can be the same type of electronic device or different types of electronic devices.

[0051] Server 12 can be a physical server containing a single host, or server 12 can be a virtual server hosted on a host cluster.

[0052] In related technologies, users can repeatedly send and save resources to be transmitted using communication software. For example... Figure 1a As shown, the first device 11 can deploy a first client of the communication software, the second device 13 can deploy a second client 13 of the communication software, and the server 12 can deploy a server of the communication software. The second device 13 maintains the target resources required by the first device 11. The user needs to send a message to the second client through the first client to instruct the user corresponding to the second client to: open the resource selection interface on the second device 13, select the target resource, and send the selected target resource to the server of the communication software. The server of the communication software forwards the resource to the first client, and the first client stores it locally on the first device 11, thereby completing the cross-device data transmission. The above resource acquisition process is very cumbersome and requires the user to perform multiple operations, resulting in low efficiency.

[0053] Alternatively, users can pre-implement trusted interconnection between devices, enabling two trusted devices to share service resources. For example... Figure 1b The first device 11 and the second device 13 can achieve trusted interconnection based on a user-centric identity authentication system. With trusted interconnection pre-implemented, the first device 11 and the second device 13 can exchange data via a local area network (LAN) or near-field communication (NFC). However, the aforementioned identity authentication system is based on specific hardware, which requires both devices to be uniformly configured with this specific hardware, resulting in numerous constraints and significant implementation difficulties.

[0054] To address the problems existing in related technologies, this specification proposes a new method for cross-device data transmission.

[0055] In the cross-device data transmission method proposed in this specification, a first client of the target application can be deployed on the first device 11, a second client of the target application can be deployed on the second device 13, and a server of the target application can be deployed on the server 12. The target application can be the communication software mentioned above or any other application software. The first client on the first device 11 can generate a resource acquisition request for the second device 13 and send the resource acquisition request to the server of the target application on the server 12. The server of the target application then sends a resource selection notification to the second client, causing the second client to return the target resource in response to the resource selection notification.

[0056] Based on a new cross-device data transmission method, on the one hand, the target resource is acquired through a first client of the target application deployed on a first device, a second client of the target application deployed on a second device, and a server of the target application, thus achieving data transmission between devices without the need to configure specific hardware. On the other hand, the resource acquisition request generated by the first client of the target application causes the server of the target application to send a resource selection notification to the second client. Then, based on the response of the second client to the resource selection notification, the target resource maintained by the second device is returned to the first client. The above process only involves the target application and does not require the user to switch between different applications. Furthermore, since the second client can respond to the resource selection notification sent by the server and return the target resource to the first client, the user on the second client does not need to focus on operations such as selection on the first client, thereby simplifying the complexity of the operation and improving the efficiency of data transmission.

[0057] Figure 2 This is a flowchart illustrating a cross-device data transmission method as provided in an exemplary embodiment. For example... Figure 2 As shown, the method may include the following steps:

[0058] Step 202: Generate a resource acquisition request for the second device by using the first client of the target application deployed on the first device, wherein the second client of the target application is deployed on the second device.

[0059] The first device can be any type of electronic device that the user can use, such as mobile phones, tablets, laptops, PDAs, wearable devices (such as smart glasses, smartwatches, etc.), etc., and this specification does not limit this. The second device is an electronic device that is different from the first device. The two devices can be the same type of electronic device or different types of electronic devices.

[0060] The target application can be any application software running on an electronic device, such as a communication application. Specifically, it can be an instant messaging application, including enterprise instant messaging applications and social instant messaging applications. This specification does not limit this.

[0061] The first client can respond to a user's triggering action on a certain interface and generate a resource acquisition request. Figure 3a This is a schematic diagram of a communication interface for a first client provided in an exemplary embodiment, such as... Figure 3aAs shown, the communication interface 301 includes a message display box 302 and a message editing box 303. The message display box 303 has four buttons: an emoticon button 304, a cut button 305, a file send button 306, and a message send button 307. Users can click the emoticon button 304 to add emoticons to the message editing box 303, click the cut button 305 to cut the message content in the message editing box 303, and click the message send button 307 to send the message content in the message editing box 303. When the user clicks the file send button 306, the communication interface 301 will display a menu 308, which includes two options: option 309 and option 310. Users can click option 309 to send locally maintained resources or click option 310 to retrieve resources from a different location. When the user clicks option 310, as shown... Figure 3b As shown, the communication interface 301 displays a menu 311, which shows two alternative options 312 and 313 for the second device. Option 312 corresponds to "Xiaobai's mobile phone," and option 313 corresponds to "Xiaohei's tablet." Each option has a selection button to its left; selection button 314 is selected, and selection button 315 is unselected. After selecting the second device, the user can click the "OK" button 316 to confirm the selection. The first client can generate a resource acquisition request for the second device based on the user's selection.

[0062] This embodiment provides a method for generating a resource acquisition request. By clicking a button on the communication interface and selecting an option from the menu, a resource acquisition request can be generated, thus notifying the second client to select resources without sending a message to the second client on the second device. On the one hand, since the message needs to be forwarded by the target application's server, this method avoids server-side message forwarding, thereby reducing the waste of storage space caused by server-side message forwarding. On the other hand, it simplifies the operation by eliminating the need for user editing of the message; simply clicking a button simplifies the process.

[0063] Step 204: Send the resource acquisition request to the server of the target application, so that the server of the target application can send a resource selection notification to the second client.

[0064] The resource acquisition request can include the IP address of the second client, and the server of the target application can send the resource acquisition notification to the second client based on the IP address.

[0065] In one embodiment, the resource selection notification is used to instruct the second client to display a resource selection interface for the resources maintained by the second device, and to return the target resource selected through the resource selection interface to the first client.

[0066] Figure 4a This is a schematic diagram of a communication interface for a second client provided in an exemplary embodiment. The communication interface 401 displays a message list 402, which contains messages 403-405. Message 403 corresponds to a resource selection notification, while messages 404 and 405 correspond to other messages. Clicking on message 403 allows viewing the details of the resource selection notification, such as... Figure 4b As shown, the details screen 406 of the resource selection notification includes a cancel button 407 and a go-to-select button 408. Clicking the cancel button 407 will reject the resource selection request from the first client, and clicking the go-to-select button 408 will redirect to the following page. Figure 4c The album interface 409 shown can be a resource selection interface, displaying photos "0001.jpg", "0002.jpg", "0003.jpg", "0004.jpg", "0005.jpg", "0006.jpg", "0007.jpg", and "0008.jpg". Clicking on any photo will display a selection box 410, indicating that the photo has been selected as the target resource. Clicking again will confirm the selection. After the resource selection is complete, clicking the "OK" button 411 will confirm the target resource.

[0067] This embodiment instructs the second client via a resource selection notification to display a resource selection interface for resources maintained by the second device, and returns the target resource selected through the resource selection interface to the first client. This allows the user to open the resource selection interface on the second client, and after selecting the target resource, directly return the target resource to the first client according to the resource selection notification. On the one hand, since the above operations are completed on the first client, there is no need to switch applications, simplifying the complexity of the operation; on the other hand, by using the first client of the target application deployed on the first device, the second client of the target application deployed on the second device, and the server of the target application, the target resource is obtained, thereby realizing data transmission between different devices without configuring specific hardware.

[0068] Step 206: Receive the target resource returned by the second client in response to the resource selection notification through the first client.

[0069] The resource selection notification can include the IP address of the first client, and the second client can return the target resource to the first client based on the IP address of the first client.

[0070] This embodiment, on the one hand, achieves the acquisition of target resources through a first client of the target application deployed on a first device, a second client of the target application deployed on a second device, and a server of the target application, thereby realizing data transmission between devices without configuring specific hardware. On the other hand, the resource acquisition request generated by the first client of the target application causes the server of the target application to send a resource selection notification to the second client. Then, based on the response of the second client of the target application to the resource selection notification, the target resources maintained by the second device are returned to the first client. The above process only involves the target application and does not require the user to switch between different applications. Furthermore, since the second client can respond to the resource selection notification sent by the server and return the target resources to the first client, the user on the second client does not need to focus on operations such as selection on the first client, thereby simplifying the complexity of the operation and improving the efficiency of data transmission.

[0071] In one embodiment, the first device can obtain device information of the device logged into by the target account from the server of the target application; in response to the received device selection instruction, the second device is selected from the obtained device information.

[0072] by Figure 1a For example, after identifying the target account, the first device 11 can send a device selection command carrying the target account's identification information to the server 12. The server 12 deploys the target application's server-side software, which maintains device information for all accounts logged into the target application. This device information may include the device's IP address and name. The server-side software can determine the device information of the logged-in device corresponding to the target account based on the target account's identification information and return the determined device information to the first client. Figure 3b As shown, menu 311 will display the name information from the device information for selection.

[0073] This embodiment obtains the device information of the device logged into by the target account through the server of the target application, so that the selection of the second device can be completed in one interface of the first client without switching interfaces, thus simplifying the complexity of operation.

[0074] Furthermore, the target account is a logged-in account on the first client; or, the target account is an associated account of a logged-in account on the first device.

[0075] The associated account is the account already logged into on the first client. Specifically, the two can be automatically associated based on the organizational structure (company / school, department / grade / class, project team / group), or based on group member relationships or friend relationships already established in the target application, or based on the address book on the first device. This manual does not impose any limitations on this.

[0076] This embodiment expands the scope of resource acquisition devices by identifying the associated account as the target account, so that the target of resource acquisition is no longer limited to the devices controlled by the user.

[0077] The second client can send the selected target resource to the target application's server, which will then forward the target resource to the first client. Alternatively, the second client can also return the target resource using other methods.

[0078] In one embodiment, the first client includes a first collaboration module, and the second client includes a second collaboration module. The first collaboration module and the second collaboration module correspond to a collaboration server. Receiving the target resource returned by the second client in response to the resource selection notification through the first client includes: receiving the target resource sent to the first collaboration module by the collaboration server through the first client. The target resource is sent to the collaboration server by the second client through the second collaboration module.

[0079] like Figure 5 As shown, the first client 51 includes a first collaboration module 501, and the second client 52 includes a second collaboration module 502. The first client 51 and the second client 52 correspond to the server 53 of the target application, and the first collaboration module 501 and the second collaboration module 502 correspond to the collaboration server 54. The server 53 of the target application and the collaboration server 54 can be deployed on the same device or on different devices; this specification does not impose any restrictions on this.

[0080] The first client 51 can generate a resource acquisition request for the second device and send the request to the server 53 of the target application. In response to the resource acquisition request, the server 53 of the target application can send a resource selection notification to the second client 52. This notification instructs the second client 52 to display a resource selection interface for the resources maintained by the second device and return the target resource selected through the interface to the first client 51. After selecting the target resource, the second client 52 can send it to the collaboration server 54 through the first collaboration module 501. The collaboration server 54 can then forward the received target resource to the first collaboration module 501.

[0081] This embodiment achieves cross-device target resource transmission through a collaboration module and a collaboration server. Since the collaboration server only temporarily stores the received target resources and clears the temporarily stored target resources after forwarding, this embodiment can avoid the target resources occupying cloud storage space and reduce the waste of storage resources.

[0082] In one embodiment, when the resource acquisition request is created on a first interface on the first client, the resource acquisition request includes identification information of the first interface; the method further includes: in response to the second client returning the identification information of the first interface in association with the target resource, displaying or inserting the target resource in the first interface.

[0083] The identification information can be the interface ID of the first screen. Figure 3a , 3c For example, the resource acquisition request sent by the first client to the server can include the interface ID of communication interface 301. The server can associate the interface ID of communication interface 301 with the resource selection notification and send it to the second client. After selecting the target resource, the second client can return the associated interface ID of communication interface 301 to the first client. Figure 3c As shown, the first client can directly insert the target resource 317 into the message editing box 303 based on the received interface ID. Alternatively, the first client can also send the target resource 317 to the message display box 302.

[0084] This embodiment uses the identification information of the first interface included in the resource acquisition request to enable the target resource returned by the second client to be directly displayed or inserted into the first interface. This not only avoids information confusion caused by inserting the target resource into other interfaces of the first client, but also improves the efficiency of resource acquisition.

[0085] In one embodiment, the first client may determine the type of the target resource and add the type of the target resource to the resource acquisition request, so that the second client displays a resource selection interface that matches the type of the target resource.

[0086] The target resource type can include any resource type such as documents, photos, and audio. Different resource types correspond to different resource selection interfaces. For example, documents can correspond to the document storage interface on the second device, photos can correspond to the photo album interface on the second device, and audio can correspond to the photo album interface or audio software interface on the second device. The resource selection notification can determine the corresponding resource selection interface based on the type of target resource included in the resource acquisition request.

[0087] like Figure 4b , 4c As shown, the target resource type is photos, the corresponding resource selection interface is the album interface 409, and the text displayed on the resource selection notification 406 is "Select pictures or videos from the album, they will be transferred to the desktop input box for easy sending." Figure 6a , 6bAs shown, the target resource type is document, the corresponding resource selection interface is document storage interface 602, and the text displayed on resource selection notification 604 is "Select documents in document storage, they will be transferred to the desktop input box for easy sending".

[0088] This embodiment enables the second client to display a resource selection interface matching the type of the target resource by including the type of the target resource in the resource selection request. This eliminates the need for the user to switch applications or select a corresponding resource selection interface, simplifying the operation and improving the efficiency of resource selection.

[0089] Figure 7 This is a flowchart illustrating a cross-device data transmission method as provided in an exemplary embodiment. For example... Figure 7 As shown, the method may include the following steps:

[0090] Step 702: Receive a resource selection notification sent by the server of the target application through a second client of the target application deployed on the second device; wherein the resource selection notification is sent by the server of the target application in response to a resource acquisition request generated by a first client of the target application deployed on the first device.

[0091] Step 704: In response to the resource selection notification, the target resource selected from the second device through the second client is returned to the first client.

[0092] In this embodiment, on the one hand, the target resource is acquired through a first client of the target application deployed on a first device, a second client of the target application deployed on a second device, and a server of the target application, thereby achieving data transmission between devices without the need to configure specific hardware. On the other hand, the resource acquisition request generated by the first client of the target application causes the server of the target application to send a resource selection notification to the second client. Then, based on the response of the second client of the target application to the resource selection notification, the target resource maintained by the second device is returned to the first client. The above process only involves the target application and does not require the user to switch between different applications. Furthermore, since the second client can respond to the resource selection notification sent by the server and return the target resource to the first client, the user on the second client does not need to focus on operations such as selection on the first client, thereby simplifying the complexity of the operation and improving the efficiency of data transmission.

[0093] As previously stated, the first client includes a first collaboration module, the second client includes a second collaboration module, and the first collaboration module and the second collaboration module correspond to a collaboration server; the step of returning the target resource selected from the second device through the second client to the first client includes: sending the target resource to the collaboration server through the second collaboration module included in the second client, so that the collaboration server forwards the target resource to the first collaboration module.

[0094] This embodiment achieves cross-device target resource transmission through a collaboration module and a collaboration server. Since the collaboration server only temporarily stores the received target resources and clears the temporarily stored target resources after forwarding, this embodiment can avoid the target resources occupying cloud storage space and reduce the waste of storage resources.

[0095] As mentioned above, the resource acquisition request also includes the type of the target resource; displaying the resource selection interface for the resources maintained by the second device on the second client includes: displaying a resource selection interface on the second client that matches the type of the target resource.

[0096] This embodiment enables the second client to display a resource selection interface matching the type of the target resource by including the type of the target resource in the resource selection request. This eliminates the need for the user to switch applications or select a corresponding resource selection interface, simplifying the operation and improving the efficiency of resource selection.

[0097] Alternatively, displaying the resource selection interface for the resources maintained by the second device on the second client includes: displaying interface entries corresponding to different resource types, and displaying the corresponding resource selection interface according to the selected interface entry.

[0098] like Figure 8 As shown, the details interface 801 of the resource selection notification includes buttons 802-804. Buttons 802-804 are the interface entries for different resource selection interfaces. Button 802 corresponds to the photo album interface, button 803 corresponds to the document storage interface, button 804 corresponds to the audio software interface, and button 805 is the cancel button. Clicking button 802 will redirect to the following interface: Figure 4c The album interface shown will redirect to the 804 page if the button is clicked. Figure 6b The document storage interface shown.

[0099] This embodiment displays interface entries for resource selection interfaces of different resource types, allowing the second client to display the corresponding resource selection interface based on the selected interface entry. This eliminates the need for users to switch applications or select a specific resource selection interface, simplifying the operation and improving the efficiency of resource selection.

[0100] In one embodiment, the second device may also display an editing interface for the target resource through the second client; the step of returning the target resource selected from the second device through the second client to the first client includes: returning the target resource edited through the editing interface to the first client.

[0101] like Figure 9 As shown, after selecting the target resource, the second client can display an editing interface 901, which includes buttons 902-906. Users can click button 902 to mark the target resource with a pen; click button 903 to erase edited marks with an eraser; click button 904 to add text to the target resource; click button 905 to zoom in on the target resource; and click button 906 to save the edits and return the edited target resource to the first client.

[0102] This embodiment allows the second client to edit the target resource before returning it through an editing interface, and then return the edited target resource.

[0103] In one embodiment, the method further includes: displaying a resource selection interface for resources maintained by the second device on the second client; the step of returning the target resource selected from the second device through the second client to the first client includes: returning the target resource selected through the resource selection interface to the first client.

[0104] This embodiment instructs the second client to display a resource selection interface for resources maintained by the second device via a resource selection notification, and returns the target resource selected through the resource selection interface to the first client. This allows the user to open the resource selection interface on the second client, and after selecting the target resource, directly return the target resource to the first client according to the resource selection notification. On one hand, the target resource is acquired through the first client of the target application deployed on the first device, the second client of the target application deployed on the second device, and the server of the target application, thereby achieving data transmission between devices without configuring specific hardware. On the other hand, the resource acquisition request generated by the first client of the target application causes the server of the target application to send a resource selection notification to the second client. Then, based on the response of the second client to the resource selection notification, the target resource maintained by the second device is returned to the first client. The above process only involves the target application, without requiring the user to switch between different applications. Furthermore, since the second client can respond to the resource selection notification sent by the server and return the target resource to the first client, the user on the second client does not need to focus on operations such as selection on the first client, thereby simplifying the complexity of the operation and improving the efficiency of data transmission.

[0105] Figure 10 This is a schematic structural diagram of a device provided in an exemplary embodiment. Please refer to... Figure 10 At the hardware level, the device includes a processor 1002, an internal bus 1004, a network interface 1006, memory 1009, and non-volatile memory 1010, and may also include other hardware required for its functions. One or more embodiments of this specification can be implemented in software, for example, the processor 1002 reads the corresponding computer program from the non-volatile memory 1010 into memory 1008 and then runs it. Of course, besides software implementation, one or more embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution entity of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0106] Please refer to Figure 11 A cross-device data transmission device can be applied to, for example... Figure 11 The device shown, in order to implement the technical solution of this specification, may include:

[0107] The generation unit 1102 is used to generate a resource acquisition request for a second device by using a first client of a target application deployed on a first device, wherein a second client of the target application is deployed on the second device.

[0108] The sending unit 1104 is used to send the resource acquisition request to the server of the target application, so that the server of the target application can send a resource selection notification to the second client.

[0109] The receiving unit 1106 is configured to receive, through the first client, the target resource returned by the second client in response to the resource selection notification.

[0110] Optional, also includes:

[0111] The first acquisition unit 1108 is used to acquire device information of the device logged in by the target account from the server of the target application;

[0112] The second acquisition unit 1110 is used to select the second device from the acquired device information in response to a received device selection instruction.

[0113] Optionally, the target account is a logged-in account on the first device; or, the target account is an associated account of a logged-in account on the first client.

[0114] Optionally, the first client includes a first collaboration module, and the second client includes a second collaboration module; the first collaboration module and the second collaboration module correspond to a collaboration server; the receiving unit 1106 is specifically used for:

[0115] The first client receives the target resource sent to the first collaboration module by the collaboration server, and the target resource is sent to the collaboration server by the second client through the second collaboration module.

[0116] Optionally, if the resource acquisition request is created on a first interface on the first client, the resource acquisition request includes the identification information of the first interface; the method further includes:

[0117] Insertion unit 1112 is used to display or insert the target resource in the first interface in response to the second client returning identification information of the first interface in association with the target resource.

[0118] Optionally, the resource selection notification is used to instruct the second client to display a resource selection interface for the resources maintained by the second device, and to return the target resource selected through the resource selection interface to the first client.

[0119] Optional, also includes:

[0120] The determining unit 1114 is used to determine the type of the target resource and add the type of the target resource to the resource acquisition request so that the second client displays a resource selection interface that matches the type of the target resource.

[0121] Please refer to Figure 12 Another type of cross-device data transmission device can be applied to, for example... Figure 12 The device shown, in order to implement the technical solution of this specification, may include:

[0122] The receiving unit 1202 is configured to receive a resource selection notification sent by the server of the target application through a second client of the target application deployed on the second device; wherein the resource selection notification is sent by the server of the target application in response to a resource acquisition request generated by a first client of the target application deployed on the first device;

[0123] The return unit 1204 is used to return the target resource selected from the second device through the second client to the first client in response to the resource selection notification.

[0124] Optionally, the first client includes a first collaboration module, the second client includes a second collaboration module, and the first collaboration module and the second collaboration module correspond to a collaboration server; the return unit 1204 is specifically used for:

[0125] The target resource is sent to the collaboration server through the second collaboration module included in the second client, so that the collaboration server can forward the target resource to the first collaboration module.

[0126] Optional,

[0127] The method further includes: a first display unit 1206, used to display a resource selection interface for the resources maintained by the second device on the second client;

[0128] The return unit 1204 is specifically used to: return the target resource selected through the resource selection interface to the first client.

[0129] Optional,

[0130] The resource acquisition request also includes the type of the target resource; the first display unit 1206 is specifically used to display a resource selection interface matching the type of the target resource on the second client; or,

[0131] The first display unit 1206 is specifically used to display the interface entry corresponding to the resource selection interface for different resource types, and to display the corresponding resource selection interface according to the selected interface entry.

[0132] Optional,

[0133] The method further includes: a second display unit 1208, used to display an editing interface for the target resource through the second client;

[0134] The return unit 1204 is specifically used to return the target resource edited through the editing interface to the first client.

[0135] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0136] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0137] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0138] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0139] The computer-readable medium (or computer-readable storage medium) described above or in any other form may store computer instructions that, when executed by a processor, implement one or more of the embodiments described above, thereby realizing the technical solutions of this specification.

[0140] This specification also provides a computer program that, when executed by a processor, implements one or more of the embodiments described above, thereby achieving the technical solutions of this specification. This computer program may be specifically recorded on the computer-readable medium described above or in any other form, and this specification does not impose any limitations on this.

[0141] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0142] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0143] The terminology used in one or more embodiments of this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this specification. The singular forms “a,” “described,” and “the” used in one or more embodiments of this specification and in the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0144] It should be understood that although the terms first, second, third, etc., may be used to describe various information in one or more embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of one or more embodiments of this specification, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "in response to a determination," or "when," or "in the event of a determination."

[0145] The above description is merely a preferred embodiment of one or more embodiments of this specification and is not intended to limit the scope of one or more embodiments of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of one or more embodiments of this specification should be included within the scope of protection of one or more embodiments of this specification.

Claims

1. A method for data transmission across devices, characterized in that, The method includes: Obtain device information of the device logged into by the target account from the server of the target application; In response to the received device selection command, a second device is selected from the acquired device information; A resource acquisition request for a second device is generated using a first client of the target application deployed on a first device, wherein a second client of the target application is deployed on the second device. The resource acquisition request is sent to the server of the target application, so that the server of the target application sends a resource selection notification to the second client. The resource selection notification is used to instruct the second client to display a resource selection interface for the resources maintained by the second device and return the target resource selected through the resource selection interface to the first client. The first client receives the target resource selected by the second client through the resource selection interface.

2. The method according to claim 1, characterized in that, The target account is a logged-in account on the first device; or, the target account is an associated account of a logged-in account on the first client.

3. The method according to claim 1, characterized in that, The first client includes a first collaboration module, and the second client includes a second collaboration module. The first and second collaboration modules each have a corresponding collaboration server. Receiving the target resource returned by the second client through the first client includes: The first client receives the target resource sent to the first collaboration module by the collaboration server, and the target resource is sent to the collaboration server by the second client through the second collaboration module.

4. The method according to claim 1, characterized in that, When the resource acquisition request is created on a first interface of the first client, the resource acquisition request includes the identification information of the first interface; the method further includes: In response to the second client returning identification information of the first interface in association with the target resource, the target resource is displayed or inserted in the first interface.

5. The method according to claim 1, characterized in that, Also includes: The type of the target resource is determined and added to the resource acquisition request so that the second client displays a resource selection interface that matches the type of the target resource.

6. A method for data transmission across devices, characterized in that, The method includes: The second client of the target application deployed on the second device receives a resource selection notification sent by the server of the target application; wherein the resource selection notification is sent by the server of the target application in response to a resource acquisition request generated by the first client of the target application deployed on the first device. In response to the resource selection notification, a resource selection interface for the resources maintained by the second device is displayed on the second client. The target resource selected through the resource selection interface will be returned to the first client.

7. The method according to claim 6, characterized in that, The first client includes a first collaboration module, and the second client includes a second collaboration module. The first collaboration module and the second collaboration module each have a corresponding collaboration server. The step of returning the target resource selected from the second device via the second client to the first client includes: The target resource is sent to the collaboration server through the second collaboration module included in the second client, so that the collaboration server can forward the target resource to the first collaboration module.

8. The method according to claim 6, characterized in that, The resource acquisition request further includes the type of the target resource; displaying the resource selection interface for the resources maintained by the second device on the second client includes: displaying a resource selection interface on the second client that matches the type of the target resource; or, The step of displaying a resource selection interface for the resources maintained by the second device on the second client includes: displaying interface entries corresponding to different resource types, and displaying the corresponding resource selection interface according to the selected interface entry.

9. The method according to claim 6, characterized in that, The method further includes: displaying an editing interface for the target resource through the second client; The step of returning the target resource selected from the second device through the second client to the first client includes: returning the target resource edited through the editing interface to the first client.

10. An electronic device, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor implements the steps of the method as described in any one of claims 1-9 by running the executable instructions.

11. A computer-readable storage medium storing computer instructions thereon, characterized in that, When executed by the processor, this instruction implements the steps of the method as described in any one of claims 1-9.

12. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the steps of the method as described in any one of claims 1-9.

Images