Cross-equipment collaborative operation method and device, electronic equipment and storage medium

Abstract

The invention relates to a cross-device collaborative operation method and device, electronic equipment and a storage medium, and the method comprises the steps: responding to a cross-device collaborative operation request of first equipment for a target document, and determining at least one collaborative device; determining collaboration contents of the collaboration devices from the target document, and sending the collaboration contents to the collaboration devices; and acquiring collaborative editing information for the collaborative content on at least one collaborative device, and synchronizing the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information. Therefore, cross-device collaborative operation can be efficiently carried out on the same document.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a cross-device collaborative operation method, apparatus, electronic device and storage medium. Background Art

[0002] Currently, document processing is mainly concentrated on a single device. If you want to process documents collaboratively on multiple devices, you need to transfer the document to a designated device.

[0003] In this regard, in the prior art, a connection between two or more devices can be established through Bluetooth connection or by adding the devices as friends on social software, so as to provide a basis for the flow of documents between the devices.

[0004] However, the conventional method of establishing a connection between two devices is cumbersome, has many limitations, and provides a poor user experience. In addition, collaborative processing of documents cannot be performed after the document is transferred. Summary of the invention

[0005] The present application provides a cross-device collaborative operation method, apparatus, electronic device and storage medium to solve the technical problem that the prior art cannot achieve collaborative operation of multiple devices on the same document.

[0006] In a first aspect, the present application provides a cross-device collaborative operation method, the method comprising:

[0007] In response to a cross-device collaborative operation request for a target document from a first device, determining at least one collaborative device;

[0008] Determine collaborative content of each collaborative device from the target document, and send the collaborative content to each collaborative device;

[0009] Acquire collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

[0010] In an optional implementation, after sending the collaborative content to each collaborative device, the method further includes:

[0011] The main editing information of the first device for the collaborative content in the target document is acquired, and the main editing information is sent to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0012] In an optional implementation manner, sending the primary editing information to the collaborative device includes:

[0013] Sending the main editing information to the selected collaborative device;

[0014] Alternatively, the selected main editing information is sent to the selected collaborative device;

[0015] Alternatively, the selected main editing information is sent to the collaborative device corresponding to the selected collaborative content.

[0016] In an optional implementation, after sending the main editing information to the collaborative device, the method further includes:

[0017] In response to the first device canceling the target editing operation on the collaborative content, a cancellation instruction is sent to the collaborative device, so that the collaborative device cancels the target editing operation on the collaborative content on the collaborative device according to the cancellation instruction.

[0018] In an optional implementation, the determining at least one collaborative device includes:

[0019] Parsing at least one target device identifier from the cross-device collaborative operation request;

[0020] The device associated with the target device identifier is determined as the collaborative device.

[0021] In an optional implementation, the determining at least one collaborative device includes:

[0022] Acquire a list of associated devices of the first device, wherein the list of associated devices includes device identifiers of devices associated with the first device;

[0023] The devices in the associated device list are determined as cooperative devices.

[0024] In an optional implementation, the acquiring collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronizing the collaborative editing information to the first device so that the first device edits the target document according to the collaborative editing information, includes:

[0025] receiving collaborative editing information from at least one of the collaborative devices, wherein the collaborative device obtains operation information of the editing operation in response to an editing operation on the collaborative content on the collaborative device, and sends the editing information as collaborative editing information to the server;

[0026] The collaborative editing information is synchronized to the first device, so that the first device edits the target document according to the collaborative editing information.

[0027] In an optional implementation manner, determining the collaborative content of each collaborative device from the target document includes:

[0028] determining all the contents in the target document as the collaborative contents of each collaborative device; or,

[0029] For each of the collaborative devices, part of the content in the target document is determined as the collaborative content of the collaborative device.

[0030] In an optional implementation, the determining, for each of the collaborative devices, part of the content in the target document as the collaborative content of the collaborative device includes:

[0031] Get the target document splitting strategy;

[0032] Splitting the target document based on the target document splitting strategy to obtain multiple sub-documents;

[0033] The contents in different sub-documents are determined as collaborative contents of different collaborative devices.

[0034] In an optional implementation, the acquiring the target document splitting strategy includes:

[0035] Parsing a target document splitting strategy from the cross-device collaborative operation request;

[0036] Alternatively, the document type of the target document is identified, and a document splitting strategy matching the document type of the target document is determined from a preset document splitting strategy set as the target document splitting strategy.

[0037] In an optional implementation manner, the sending the collaborative content to each collaborative device includes:

[0038] Determine the order of document flow;

[0039] The collaborative content is sent to each collaborative device in sequence according to the document flow order, wherein when it is determined that the current collaborative device has completed editing of the collaborative content, the collaborative content is sent to the next collaborative device in the document flow order.

[0040] In an optional implementation manner, the sending the collaborative content to each collaborative device includes:

[0041] Determine the order of document flow;

[0042] Setting the collaborative content of each collaborative device to a locked state, and synchronously sending the collaborative content in the locked state to each collaborative device;

[0043] An unlocking instruction is sent to each of the collaborative devices in sequence according to the document flow order, so that the collaborative device unlocks the collaborative content in a locked state according to the unlocking instruction, wherein, when it is determined that the current collaborative device has completed editing the collaborative content, the unlocking instruction is sent to the next collaborative device in the document flow order, and the collaborative content is allowed to be viewed and / or edited in an unlocked state.

[0044] In a second aspect, the present application provides another cross-device collaborative operation method, the method comprising:

[0045] Get the target document;

[0046] In response to a trigger operation on the target document, a cross-device collaborative operation request for the target document is sent to a server, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content on at least one collaborative device, and synchronizes the collaborative editing information to the first device;

[0047] The collaborative editing information of the collaborative content is received on at least one of the collaborative devices, and the target document is edited according to the collaborative editing information.

[0048] In an optional implementation, after the server sends the corresponding collaborative content to each collaborative device, the method further includes:

[0049] The main editing information of the first device for the collaborative content in the target document is sent to the server, so that the server sends the main editing information to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0050] In an optional implementation, in response to the triggering operation on the target document, sending a cross-device collaborative operation request for the target document to the server includes:

[0051] In response to a triggering operation on the target document, presenting an associated device list, wherein the associated device list includes device identifiers of devices associated with the first device;

[0052] The device identifier selected in the associated device list is determined as the target device identifier and carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server, so that the server determines the at least one collaborative device according to the target device identifier.

[0053] In an optional implementation, in response to the triggering operation on the target document, sending a cross-device collaborative operation request for the target document to the server includes:

[0054] In response to a device push request from a server, determining that a trigger operation on the target document is detected, wherein the server responds to a collaboration request sent by the second device when shaking, and in the case where it is determined that the geographical location relationship between the first device and the second device meets a set condition, sends the device push request to the first device, wherein the device push request carries a device identifier of the second device;

[0055] In response to a trigger operation on the target document, the device identifier of the second device is parsed from the device push request, and the device identifier of the second device is determined as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server, so that the server determines the second device as a collaborative device according to the target device identifier.

[0056] In an optional implementation, in response to the triggering operation on the target document, sending a cross-device collaborative operation request for the target document to the server includes:

[0057] In response to establishing a near field connection with a second device, determining that a triggering operation on the target document is detected;

[0058] In response to a trigger operation on the target document, the device identifier of the second device is determined as the target device identifier and carried in a cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server so that the server determines the second device as a collaborative device based on the target device identifier.

[0059] In an optional implementation, after sending the cross-device collaborative operation request to the server, the method further includes:

[0060] The second device is determined as an associated device of the first device, and a device identifier of the second device is added to an associated device list of the first device.

[0061] In a third aspect, the present application provides a cross-device collaborative operation apparatus, the apparatus comprising:

[0062] A device determination module, configured to determine at least one collaborative device in response to a cross-device collaborative operation request for a target document from a first device;

[0063] A content determination module, used to determine the collaborative content of each collaborative device from the target document;

[0064] A content sending module, used for sending the collaborative content to each collaborative device;

[0065] The first synchronous editing module is used to obtain collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

[0066] In an optional embodiment, the device further comprises:

[0067] A third synchronous editing module is used to obtain the main editing information of the first device for the collaborative content in the target document after sending the collaborative content to each of the collaborative devices, and send the main editing information to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0068] In an optional implementation manner, the third synchronous editing module is specifically used to:

[0069] Sending the main editing information to the selected collaborative device;

[0070] Alternatively, the selected main editing information is sent to the selected collaborative device;

[0071] Alternatively, the selected main editing information is sent to the collaborative device corresponding to the selected collaborative content.

[0072] In an optional embodiment, the device comprises:

[0073] An operation undo module is used to send an undo instruction to the collaborative device in response to the first device undoing the target editing operation on the collaborative content after the main editing information is sent to the collaborative device, so that the collaborative device cancels the target editing operation on the collaborative content on the collaborative device according to the undo instruction.

[0074] In an optional implementation manner, the device determination module is specifically used to:

[0075] Parsing at least one target device identifier from the cross-device collaborative operation request;

[0076] The device associated with the target device identifier is determined as the collaborative device.

[0077] In an optional implementation manner, the device determination module is specifically used to:

[0078] Acquire a list of associated devices of the first device, wherein the list of associated devices includes device identifiers of devices associated with the first device;

[0079] The devices in the associated device list are determined as cooperative devices.

[0080] In an optional implementation manner, the first synchronous editing module is specifically used to:

[0081] receiving collaborative editing information from at least one of the collaborative devices, wherein the collaborative device obtains operation information of the editing operation in response to an editing operation on the collaborative content on the collaborative device, and sends the editing information as collaborative editing information to the server;

[0082] The collaborative editing information is synchronized to the first device, so that the first device edits the target document according to the collaborative editing information.

[0083] In an optional implementation manner, the content determination module is specifically configured to:

[0084] determining all the contents in the target document as the collaborative contents of each collaborative device; or,

[0085] For each of the collaborative devices, part of the content in the target document is determined as the collaborative content of the collaborative device.

[0086] In an optional implementation, the content determination module includes:

[0087] A strategy acquisition unit, used for acquiring a target document splitting strategy;

[0088] A document splitting unit, used for splitting the target document based on the target document splitting strategy to obtain multiple sub-documents;

[0089] The first determining unit is configured to determine the contents in different sub-documents as collaborative contents of different collaborative devices.

[0090] In an optional implementation manner, the policy acquisition unit is specifically configured to:

[0091] Parsing a target document splitting strategy from the cross-device collaborative operation request;

[0092] In an optional implementation, the policy acquisition unit includes:

[0093] A type identification unit, used to identify the document type of the target document;

[0094] The matching subunit is used to determine a document splitting strategy that matches the document type of the target document from a preset document splitting strategy set as a target document splitting strategy.

[0095] In an optional implementation, the content sending module includes:

[0096] A second determining unit, used to determine the document flow order;

[0097] The first circulation unit is configured to send the corresponding collaborative content to each collaborative device in sequence according to the document circulation order, wherein when it is determined that the current collaborative device has completed editing the collaborative content, the collaborative content is sent to the next collaborative device in the document circulation order.

[0098] In an optional implementation, the content sending module includes:

[0099] A third determining unit, used to determine the document flow order;

[0100] A locking unit, used to set the collaborative content of each collaborative device to a locked state;

[0101] A second transfer unit, configured to synchronously send the collaborative content in a locked state to each of the collaborative devices;

[0102] An unlocking control unit is used to send unlocking instructions to each of the collaborative devices in sequence according to the document flow order, so that the collaborative device unlocks the collaborative content in a locked state according to the unlocking instructions, wherein, when it is determined that the current collaborative device has completed editing the collaborative content, the unlocking instruction is sent to the next collaborative device in the document flow order, and the collaborative content is allowed to be viewed and / or edited in an unlocked state.

[0103] In a fourth aspect, the present application provides another cross-device collaborative operation apparatus, the apparatus comprising:

[0104] A document acquisition module is used to acquire target documents;

[0105] A request sending module, configured to send a cross-device collaborative operation request for the target document to a server in response to a trigger operation on the target document, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content by at least one collaborative device, and synchronizes the collaborative editing information to the first device;

[0106] The second synchronous editing module is used to receive collaborative editing information of the collaborative content from at least one of the collaborative devices, and edit the target document according to the collaborative editing information.

[0107] In an optional embodiment, the device further comprises:

[0108] A fourth synchronous editing module is used to send the main editing information of the first device for the collaborative content in the target document to the server after the server sends the corresponding collaborative content to each collaborative device, so that the server sends the main editing information to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0109] In an optional implementation, the request sending module includes:

[0110] a list presenting unit, configured to present, in response to a triggering operation on the target document, a list of associated devices, wherein the list of associated devices includes device identifiers of devices associated with the first device;

[0111] A target determination unit is used to determine the device identifier selected in the associated device list as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and send the cross-device collaborative operation request to the server so that the server determines at least one collaborative device according to the target device identifier.

[0112] In an optional implementation manner, the request sending module is specifically used to:

[0113] In response to a device push request from a server, determining that a trigger operation on the target document is detected, wherein the server responds to a collaboration request sent by the second device when shaking, and in the case where it is determined that the geographical location relationship between the first device and the second device meets a set condition, sends the device push request to the first device, wherein the device push request carries a device identifier of the second device;

[0114] In response to a trigger operation on the target document, the device identifier of the second device is parsed from the device push request, and the device identifier of the second device is determined as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server, so that the server determines the second device as a collaborative device according to the target device identifier.

[0115] In an optional implementation manner, the request sending module is specifically used to:

[0116] In response to establishing a near field connection with a second device, determining that a triggering operation on the target document is detected;

[0117] In response to a trigger operation on the target document, the device identifier of the second device is determined as the target device identifier and carried in a cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server so that the server determines the second device as a collaborative device based on the target device identifier.

[0118] In an optional embodiment, the device further comprises:

[0119] An association module is used to determine the second device as an associated device of the first device and add a device identifier of the second device to an associated device list of the first device after the cross-device collaborative operation request is sent to the server.

[0120] In a fifth aspect, the present application provides an electronic device comprising: a processor and a memory, wherein the processor is used to execute a cross-device collaborative operation program stored in the memory to implement the cross-device collaborative operation method described in any one of the first aspect or the second aspect.

[0121] In a sixth aspect, the present application provides a storage medium storing one or more programs, which can be executed by one or more processors to implement the cross-device collaborative operation method described in any one of the first aspect or the second aspect.

[0122] The above-mentioned technical scheme provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application, through the server responding to the cross-device collaborative operation request of the first device for the target document, determines at least one collaborative device, determines the collaborative content corresponding to each collaborative device from the target document, and sends its corresponding collaborative content to each collaborative device, obtains the collaborative editing information of at least one collaborative device for its corresponding collaborative content, and sends the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information, thereby realizing cross-device collaborative operations for the same document, and because the collaborative device can be determined through extremely simple operations, and then the collaborative content can be assigned to the collaborative device, the process of establishing connections between devices is greatly simplified, and the editing information can be directly synchronized between the first device and its collaborative device without introducing other carriers to realize collaborative editing of the same document between different devices, thereby improving the efficiency of cross-device collaborative operations for the same document.

[0123] In response to a trigger operation on a target document, the first device sends a cross-device collaborative operation request for the target document to a server, so that the server responds to the cross-device collaborative operation request, determines at least one collaborative device, determines the collaborative content corresponding to each collaborative device from the target document, sends the corresponding collaborative content to each collaborative device, and receives collaborative editing information of the corresponding collaborative content from at least one collaborative device, edits the target document according to the collaborative editing information, and realizes cross-device collaborative operations on the same document. In addition, since the collaborative device can be determined through extremely simple operations and the collaborative content can be assigned to the collaborative device, the process of establishing connections between devices is greatly simplified, and the editing information can be directly synchronized between the first device and its collaborative device without introducing other carriers to realize collaborative editing of the same document between different devices, thereby improving the efficiency of cross-device collaborative operations on the same document. BRIEF DESCRIPTION OF THE DRAWINGS

[0124] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0125] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0126] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0127] Figure 1 A schematic diagram of an application scenario involved in an embodiment of the present application;

[0128] Figure 2 A flowchart of an embodiment of a cross-device collaborative operation method provided in an embodiment of the present application;

[0129] Figure 3 A schematic diagram of another application scenario involved in an embodiment of the present application;

[0130] Figure 4 This is a schematic diagram of another application scenario involved in the embodiment of the present application;

[0131] Figure 5 A flowchart of another embodiment of a cross-device collaborative operation method provided in an embodiment of the present application;

[0132] Figure 6 This is a schematic diagram of another application scenario involved in the embodiment of the present application;

[0133] Figure 7 A flowchart of another embodiment of a cross-device collaborative operation method provided in an embodiment of the present application;

[0134] Figure 8 A block diagram of an embodiment of a cross-device collaborative operation apparatus provided in an embodiment of the present application;

[0135] Fig. 9 A block diagram of another embodiment of a cross-device collaborative operation apparatus provided in an embodiment of the present application;

[0136] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0137] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0138] The disclosure below provides many different embodiments or examples to implement different structures of the present invention. In order to simplify the disclosure of the present invention, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present invention. In addition, the present invention can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0139] In order to solve the technical problem in the prior art that multiple devices cannot collaborate on the same document, the present application provides a cross-device collaborative working method, which can enable multiple devices to collaborate on the same document, and through simple operations, the document can be circulated between multiple devices, so as to realize cross-device collaborative working.

[0140] To facilitate understanding of the cross-device collaborative operation method provided by the embodiments of the present application, an exemplary description of the application scenarios involved in the embodiments of the present application is first given below.

[0141] Figure 1 Schematic diagram of an application scenario involved in the embodiment of the present application. Figure 1The application scenario shown includes devices 101~103, wherein devices 101~103 can be various electronic devices supporting display screens, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, projection devices, etc., and devices 101~103 can be devices of the same type or devices of different types, which is not limited in the embodiments of the present application.

[0142] Figure 1 In the application scenario shown, device 101 is editing a slide. When you want to initiate a cross-device collaborative operation for the slide, you can apply the method provided in the embodiment of the present application to dispatch the slide to device 102 and device 103, so that device 102 and device 103 can synchronously display the slide and edit the slide. Here, the editing operations and editing results of the slide by device 102 and device 103 can be synchronously displayed on device 101 in real time, thereby realizing cross-device collaborative operations for the slide. Further optionally, the editing operations and editing results of the slide by device 101 can also be synchronously displayed on device 102 and device 103 in real time, which further enhances the effect of cross-device collaborative operations.

[0143] Figure 2 The flowchart of an embodiment of a cross-device collaborative operation method provided in an embodiment of the present application. In one embodiment, the method is applied to a first device, where the first device refers to an initiating device of the cross-device collaborative operation, for example Figure 1 The device 101 shown in FIG. Figure 2 As shown, the following steps are included:

[0144] Step 201: The first device obtains a target document.

[0145] The target document may be a document in any format such as .doc, .docx, .xlsx, .xls, or .ppt. Optionally, the target document is a document currently being edited by the first device. Optionally, the target document may also be a document stored locally on the first device, or obtained from an external device (e.g., the Internet or other devices). For the latter, the target document may be specified by a user on the first device.

[0146] Step 202: The first device sends a cross-device collaborative operation request for the target document to the server in response to a trigger operation on the target document, so that the server responds to the cross-device collaborative operation request and determines at least one collaborative device; determines the collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device.

[0147] The cross-device collaborative operation request for the target document is used to instruct cross-device collaborative operation on the target document, such as cross-device collaborative editing of the target document. The cross-device collaborative editing mentioned here refers to collaborative editing of the target document on different devices, such as Figure 1 In the illustrated application scenario, a designated slide is collaboratively edited on the device 101 and the device 102 .

[0148] In one embodiment, the user of the first device can manually trigger the first device to initiate a cross-device collaborative work request for the target document and manually select a collaborative device. Here, one or more collaborative devices can be selected, for example, Figure 1 The example application scenario includes two collaborative devices, namely device 102 and device 103.

[0149] Among them, as an optional implementation method, the specific implementation of the first device being manually triggered by the user to initiate a cross-device collaborative operation for the target document and select a collaborative device includes: the first device responds to the trigger operation on the target document and presents a list of associated devices, the list of associated devices includes the device identifiers of the devices associated with the first device, and then the first device determines the device identifier selected in the list of associated devices as the target device identifier carried in the cross-device collaborative operation request for the target document, and sends the cross-device collaborative operation request to the server, so that the server can parse the target device identifier from the cross-device collaborative operation request, and determine at least one collaborative device based on the target device identifier, and execute subsequent processes for the at least one collaborative device to realize the cross-device collaborative operation for the target document. It can be seen that this realizes that the first device responds to the trigger operation on the target document and sends a cross-device collaborative operation request for the target document to the server.

[0150] The above-mentioned trigger operation on the target document can be a trigger operation on a control encapsulated on the first device that triggers the cross-device collaborative operation function. When the first device detects the trigger operation, it can initiate a cross-device collaborative operation on the target document currently being edited by the first device by default, and then send a cross-device collaborative operation request for the target document to the server.

[0151] The above-mentioned associated device list includes the device identification of the device associated with the first device. Optionally, the devices associated with the first device include other devices logged in by the user account currently logged in on the first device. The login mentioned here is not limited to simultaneous login, and can also include sequential login. For example, user account A has logged in to device 101 and device 102 successively, then the association relationship between device 101 and device 102 can be automatically established, and the device identification of device 102 will exist in the associated device list of device 101. Similarly, the device identification of device 101 will exist in the associated device list of device 102. Through this processing, devices logged in by the same user account can automatically appear in the associated device list, and the document can be repeatedly transferred between the devices logged in by the same user without the user performing additional operations. This greatly simplifies user operations and improves user experience.

[0152] Optionally, the devices associated with the first device also include other devices authenticated by the first device. Here, the first device may authenticate other devices by displaying authentication information, such as a QR code, a digital code, etc., and the other devices establish an authentication relationship with the first device by scanning the authentication information.

[0153] Through this processing, it is possible to implement repeated document transfers between previously authenticated devices by only performing authentication once, which greatly simplifies user operations and improves user experience.

[0154] Optionally, the devices associated with the first device also include devices logged in by other user accounts belonging to the same team as the user account currently logged in on the first device. Figure 3 In the scenario illustrated, a user account in team 3 is logged into the first device (device 1). In response to the trigger operation on the target document, the first device presents a list of associated devices, which only includes the device identifiers of device 7 and device 8, but does not include devices 2 to 6 corresponding to team 1 and team 2. In addition, in one example, when the first device initiates a cross-device collaborative operation for a target document, the server can also default the devices logged in by other user accounts belonging to the same team as the user account currently logged in on the first device as collaborative devices, so that users of the same team can perform cross-device collaborative operations on the same target document. This makes it possible to intelligently initiate document transfers between team members and perform cross-device collaborative operations without the user having to perform additional device association operations, thereby greatly simplifying user operations and improving user experience.

[0155] Here, one more thing to add is that the above-mentioned associated device list may include other user accounts that have a collaborative relationship with the user account currently logged in on the first device, so the user on the first device side will select the user account in the associated device list, and the user account carried in the above-mentioned cross-device collaborative operation request will also be the selected user account. At this time, the server can parse at least one user account from the cross-device collaborative operation request, and then determine the device currently logged in by the user account, thereby obtaining at least one target device identifier.

[0156] Furthermore, the first device initiates a cross-device collaborative operation request for the target document, and the cross-device collaborative operation request may not carry any target device identification. The server receives the cross-device collaborative operation request, obtains the associated device list of the first device, and determines the device in the associated device list as a collaborative device by default. It can be seen that the embodiment of the present application can determine the collaborative device through extremely simple operations, and then perform cross-device collaborative operations.

[0157] Optionally, the devices associated with the first device may also be manually specified by the user, that is, the associated device list of the first device is manually set by the user.

[0158] Here is another point to add: the list of associated devices for each device can be maintained by the device itself, by the server, or by both the device itself and the server. The specific maintenance method is related to the business scenario. For example, for the above-mentioned association relationship established through authentication, the list of associated devices can be maintained by the device itself, while for the above-mentioned association relationship established through the team, it is maintained by the server. This is because the team relationship between multiple user accounts is usually recorded on the server side. Similarly, the above-mentioned association relationship established through the same user account is also maintained by the server. The device can obtain its associated device list from the server side when needed. Of course, after obtaining its associated device list from the server side, the device can also save the associated device list locally for subsequent application. Furthermore, the device can also update the locally stored associated device list regularly or in a real-time synchronization manner to ensure that the locally stored associated device list is consistent with the associated device list on the server side as much as possible.

[0159] In another embodiment, the first device may automatically trigger the initiation of a cross-device collaborative operation for a target document and automatically select a collaborative device, which can simplify user operations and improve user experience.

[0160] Among them, as an optional implementation method, the specific implementation of the first device being manually triggered by the user to initiate a cross-device collaborative operation for the target document and select a collaborative device includes: the first device responds to a device push request from the server, determines that a trigger operation on the target document is detected, wherein the server responds to the collaborative request sent by the second device when shaking, and sends a device push request to the first device when it determines that the geographical location relationship between the first device and the second device meets the set conditions, and the device push request carries the device identifier of the second device; the first device responds to the trigger operation on the target document, parses the device identifier of the second device from the device push request, and determines the device identifier of the second device as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and sends the cross-device collaborative operation request to the server, so that the server determines the second device as a collaborative device according to the target device identifier. It can be seen that this realizes that the first device responds to the trigger operation on the target document and sends a cross-device collaborative operation request for the target document to the server.

[0161] Combine the following Figure 4 The example application scenario explains the above implementation method:

[0162] Figure 4 The application scenario shown includes an initiating device (i.e., the first device) and device 2 (i.e., the second device), wherein device 2 has a built-in gyroscope. When the user shakes device 2, the built-in gyroscope of device 2 detects that device 2 is shaking, triggering device 2 to send a collaborative request to the server, which may carry the device identification of device 2 and the current geographic location information of device 2. After receiving the collaborative request, the server parses the device identification of device 2 and the current geographic location information of device 2, and then finds the first device whose geographic location relationship with device 2 meets the set conditions based on the current geographic location information of device 2. The set conditions here are, for example, that the distance between the two devices is within a set distance range (e.g., 50 meters, 100 meters, etc.), and then sends a device push request to the first device, which carries the device identification of device 2. At this point, the initiating device receives the device push request carrying the device identification of device 2.

[0163] After the initiating device receives the above-mentioned device push request, it automatically triggers the cross-device collaborative operation for the target document. That is to say, after the initiating device receives the above-mentioned device push request, it can detect the triggering operation on the target document, and then the initiating device parses the device ID of device 2 from the device push request, and determines the device ID of device 2 as the target device ID to be carried in the cross-device collaborative operation request for the target document, and sends the cross-device collaborative operation request to the server, so that the server determines device 2 as a collaborative device according to the target device ID. It can be seen that this realizes that the first device automatically triggers the initiation of a cross-device collaborative operation for the target document and automatically selects a collaborative device.

[0164] Here is another point to add: after the initiating device receives the above device push request, it can also first display the device identification of device 2 carried therein, so that the user can manually confirm whether to allow device 2 to collaborate on the target document. This can ensure the security of the target document content and make the user experience more friendly.

[0165] As another optional implementation, the specific implementation of the first device being manually triggered by the user to initiate a cross-device collaborative operation for a target document and select a collaborative device includes: the first device responds to establishing a near-field connection with the second device, determines that a trigger operation for the target document is detected, and then responds to the trigger operation for the target document, determines the device identifier of the second device as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and sends the cross-device collaborative operation request to the server, so that the server determines the second device as a collaborative device according to the target device identifier. It can be seen that this implements the first device responding to the trigger operation for the target document and sending a cross-device collaborative operation request for the target document to the server.

[0166] Next, combine Figure 4 The example application scenario explains the above implementation method:

[0167] Figure 4In the application scenario shown, the initiating device (i.e., the first device) and device 3 (i.e., the second device) have built-in near field communication modules, which may be Bluetooth modules, NFC (Near Field Communication) modules, etc. When the user controls device 3 to approach the initiating device, a near field connection is established between device 3 and the initiating device. The initiating device responds to the establishment of a near field connection with device 3, determines that a trigger operation on the target document is detected, and then responds to the trigger operation on the target document, determines the device identifier of device 3 as the target device identifier carried in the cross-device collaborative operation request for the target document, and sends the cross-device collaborative operation request to the server, so that the server determines device 3 as a collaborative device according to the target device identifier. It can be seen that this realizes that the first device responds to the trigger operation on the target document and sends a cross-device collaborative operation request for the target document to the server.

[0168] Here is an additional explanation: when the above-mentioned near-field communication module is an NFC module, when device 3 approaches the initiating device, the initiating device can automatically establish a near-field connection with device 3, and no user operation is required in this process. When the above-mentioned near-field communication module is a Bluetooth module, it is limited by the Bluetooth configuration of the initiating device. When the Bluetooth of the initiating device is configured as an open connection, when device 3 approaches the initiating device, it scans the Bluetooth signal of the initiating device and initiates a connection request to the initiating device. The initiating device responds to the connection request and establishes a Bluetooth connection with device 3 (also a type of near-field connection); when the Bluetooth of the initiating device is configured to verify the connection, when device 3 approaches the initiating device, it scans the Bluetooth signal of the initiating device and obtains the Bluetooth pairing code of the initiating device, and then sends a connection request carrying the Bluetooth pairing code to the initiating device. The initiating device responds to the connection request, parses the Bluetooth pairing code from it and verifies the Bluetooth pairing code. If the verification passes, a Bluetooth connection is established with device 3.

[0169] Regardless of the specific near-field connection form adopted, after establishing a near-field connection between other devices and the initiating device, the initiating device 3 can determine the device identifier of the other device as the target device identifier and carry it in the cross-device collaborative operation request for the target document, and send the cross-device collaborative operation request to the server, so that the server determines the other device as a collaborative device based on the target device identifier.

[0170] Furthermore, in one embodiment, after the first device automatically triggers the initiation of a cross-device collaborative operation for a target document and automatically selects the second device as a collaborative device, the second device may be determined as an associated device of the first device and a device identifier of the second device may be added to the associated device list of the first device. Figure 4In the example application scenario, device 2 and device 3 are determined as associated devices of the initiating device, and the device identifiers of device 2 and device 3 are added to the associated device list of the initiating device. Subsequently, the device identifiers of device 2 and device 3 will be displayed in the associated device list presented by the initiating device, so that the user on the initiating device side can select device 2 and / or device 3 as collaborative devices again.

[0171] Through the above processing, devices that have participated in collaborative work can automatically appear in the list of associated devices, and documents can be transferred between devices repeatedly without repeated association, which greatly simplifies user operations.

[0172] After receiving the cross-device collaborative operation request for the target document, the server parses the target device ID and determines the device corresponding to the target device ID as the collaborative device. Further, the server determines the collaborative content corresponding to each collaborative device from the target document and sends the corresponding collaborative content to each collaborative device. This achieves the cross-device distribution of collaborative content. As for how the server determines the collaborative content corresponding to each collaborative device from the target document and sends the corresponding collaborative content to each collaborative device, it will be described in the following Figure 5 A detailed explanation is given in the illustrated embodiment and will not be described in detail here.

[0173] Step 203: The first device receives collaborative editing information of the corresponding collaborative content from at least one collaborative device, and edits the target document according to the collaborative editing information.

[0174] The above-mentioned collaborative editing information refers to the operation information of the collaborative device for editing the collaborative content on the collaborative device (for the convenience of description, it is referred to as collaborative editing information here), not the content itself. In other words, when the first device and the collaborative device synchronize the collaborative content, what is synchronized is the operation information of the editing operation, not the content itself. The editing mentioned here may include deleting content, modifying content, adding content, annotating content, etc., wherein the modified content includes text modification and text format modification. For example, text modification includes modifying typos, and text format modification includes modifying font color, font size, etc. The operation information of the editing operation may include the location, type, and content of the operation (such as newly added content, annotated content, etc.) of the editing operation.

[0175] In the embodiment of the present application, any collaborative device responds to the editing operation of the collaborative content on the collaborative device, obtains collaborative editing information, and sends the collaborative editing information to the server, so that the server sends the collaborative editing information to the first device. After the first device receives the collaborative editing information, it edits the target document according to the collaborative editing information, so that the editing operation of the collaborative content by other devices and the editing results can be synchronously displayed on the initiating device (i.e., the first device).

[0176] One thing that needs to be explained here is that when the user on the initiating device side initiates a cross-device collaborative operation for the target document, he or she can also manually configure the permissions of each collaborative device. The configurable permissions include: view only, allow view and allow free editing. Based on this, if the collaborative device is configured with the permission of view only, then the collaborative device can only view its corresponding collaborative content and cannot edit it. For example, in Figure 1 In the application scenario shown, device 102 only allows viewing of slides but cannot edit the slides, while device 103 can freely edit the slides.

[0177] Through the above processing, the flexibility of cross-device collaborative operations can be improved, the ability of multi-person, multi-role, and multi-device collaboration can be fully utilized to meet the diverse needs of users and improve user experience.

[0178] In addition, as an optional embodiment, after the server sends the corresponding collaborative content to each collaborative device, the first device may also send the first device's main editing information for the collaborative content in the target document to the server, so that the server sends the main editing information to the collaborative device, allowing the collaborative device to edit the collaborative content on the collaborative device according to the main editing information.

[0179] The above-mentioned main editing information refers to the operation information of the initiating device (i.e., the first device) for editing the collaborative content on the collaborative device (for the convenience of description, it is referred to as the main editing information here), not the content itself. In other words, when the first device and the collaborative device synchronize the collaborative content, what is synchronized is the operation information of the editing operation, not the content itself. The editing mentioned here may include deleting content, modifying content, adding content, annotating content, etc., wherein the modified content includes text modification and text format modification. For example, text modification includes modifying typos, and text format modification includes modifying font color, font size, etc. The operation information of the editing operation may include the location, type, and content of the operation (such as newly added content, annotated content, etc.) of the editing operation.

[0180] Through this embodiment, the editing operation and editing results of the initiating device on the collaborative content can also be synchronously displayed on other devices in real time, which further improves the effect of cross-device collaborative work.

[0181] Here is an additional point. In actual applications, users can choose whether to synchronize the editing operations and editing results of the initiating device on the collaborative content on other devices in real time according to actual business needs. For example, if the user only needs to view the collaborative editing information of the target document by the collaborative device, and does not want to disclose his or her main editing information of the target document to other collaborative devices, then the user can configure the initiating device not to send the above main editing information to the server, so as to ensure the privacy of the editing operations on the local end.

[0182] Further, in one embodiment, the sending of the main editing information to the collaborative device mentioned above means: sending the main editing information to the selected collaborative device. The selection here can be all selected or partly selected. For example, in Figure 1 In the illustrated scenario, both device 102 and device 103 are selected, and the main editing information of the slides on device 101 is sent to device 102 and device 103, so that the slides on device 102 and device 103 can be synchronized with the slides on device 101. Figure 1 In the illustrated scenario, device 102 is selected, and the main editing information of the slides by device 101 is sent to device 102 instead of to device 103 , so that the slides on device 102 can be synchronized with the slides on device 101 .

[0183] In another embodiment, the sending of the main editing information to the collaborative device mentioned above means: sending the selected main editing information to the selected collaborative device. As above, the selection here can be all selection or part selection. For example, in Figure 1 In the scenario shown, assuming that the slideshow has 5 pages, the user on device 101 edits each page, and only page 1 is selected, and both device 102 and device 103 are selected, then only the main editing information of page 1 on device 101 can be sent to devices 102 and 103, so that page 1 of the slideshow on devices 102 and 103 can be synchronized with page 1 of the slideshow on device 101. For another example, in Figure 1 In the scenario shown, device 102 is selected, so the main editing information of device 101 on page 1 can be sent only to device 102 but not to device 103, so that page 1 of the slide on device 102 can be synchronized with page 1 of the slide on device 101.

[0184] It should be noted that different collaborative devices can be selected for different main editing information. Figure 1In the scenario shown, the user on the device 101 side selects device 102 for page 1 and selects device 103 for page 2. Then, the main editing information of device 101 for page 1 can be sent to device 102, and the main editing information of device 101 for page 2 can be sent to device 103, so that page 1 of the slide on device 102 can be synchronized with page 1 of the slide on device 101, and page 2 of the slide on device 103 can be synchronized with page 2 of the slide on device 101.

[0185] In another embodiment, the sending of the main editing information to the collaborative device mentioned above means: sending the selected main editing information to the collaborative device corresponding to the selected collaborative content. The corresponding collaborative device mentioned here can be all the collaborative devices corresponding to the collaborative content, or can be several of the collaborative devices. Figure 1 In the scenario shown, the user on the device 101 side uses page 1 in the slide as the collaborative content of device 102 and device 103. That is, page 1 in the slide corresponds to two collaborative devices, device 102 and device 103. When the user on the device 101 side selects the main editing information for page 1 in the slide, the selected main editing information can be sent to device 102 and / or device 103.

[0186] It can be seen from the above embodiments that in actual applications, users can flexibly choose on which devices the editing operations and editing results of the initiating device on the collaborative content will be synchronously displayed in real time according to actual business needs, and flexibly select the editing operations that need to be synchronously displayed on different devices. This makes the technical solution provided in the embodiments of the present application more flexible and suitable for a variety of collaborative work scenarios.

[0187] In addition, the technical solution provided by the embodiment of the present application also supports synchronous undo operations. Specifically, after the main editing information is sent to the collaborative device, if in response to the first device revoking the editing operation on the collaborative content (hereinafter referred to as the target editing operation, which refers to the revoked editing operation), the execution subject of the embodiment of the present application will send an undo instruction to the collaborative device, so that the collaborative device will revoke the target editing operation on the collaborative content on the collaborative device according to the undo instruction. For example, the first device adds a new annotation to the collaborative content, and the annotation operation is also synchronized to the collaborative device. After that, the first device revokes the annotation operation. Then, by applying the above scheme, the annotation operation made on the collaborative device can be synchronously revoked, so that the collaborative device also deletes the annotation on the collaborative content. This further improves the collaborative flexibility of the technical solution provided by the embodiment of the present application.

[0188] The technical solution provided by the embodiment of the present application is that the first device responds to the trigger operation on the target document and sends a cross-device collaborative operation request for the target document to the server, so that the server responds to the cross-device collaborative operation request, determines at least one collaborative device, determines the collaborative content of each collaborative device from the target document, sends the collaborative content to each collaborative device, and receives collaborative editing information of the collaborative content from at least one collaborative device, edits the target document according to the collaborative editing information, thereby realizing cross-device collaborative operations on the same document. Moreover, since the collaborative device can be determined through extremely simple operations and the collaborative content can be assigned to the collaborative device, the process of establishing connections between devices is greatly simplified, and the editing information can be directly synchronized between the first device and its collaborative device without introducing other carriers to realize collaborative editing of the same document between different devices, thereby improving the efficiency of cross-device collaborative operations on the same document.

[0189] Figure 5 A flowchart of another embodiment of a cross-device collaborative operation method provided in an embodiment of the present application. In one embodiment, the method is applied to a server, where the server refers to one end that provides cross-device collaborative operation services. The dispatch of collaborative content, device authentication, device status control, etc. involved in the embodiment of the present application are all controlled by the server. Optionally, the server mentioned here can be deployed in the cloud or on any device, including the first device and any collaborative device. Figure 5 As shown, the following steps are included:

[0190] Step 501: The server determines at least one collaborative device in response to a cross-device collaborative operation request for a target document from a first device.

[0191] In one embodiment, the above cross-device collaborative operation request carries at least one target device identifier, based on which, the specific implementation of the server determining at least one collaborative device may include: the server parses at least one target device identifier from the cross-device collaborative operation request, and determines the device associated with each target device identifier as a collaborative device. As for how the first device implements carrying at least one target device identifier in the above cross-device collaborative operation request, please refer to the above Figure 2 The relevant description in the illustrated embodiment will not be repeated here.

[0192] In another embodiment, the cross-device collaborative operation request does not carry any target device identifier. In this case, the specific implementation of the server determining at least one collaborative device may include: the server obtains a list of associated devices of the first device, and determines the device in the list of associated devices as a collaborative device. As for how the above-mentioned list of associated devices is constructed, please refer to the above Figure 2 The relevant description in the illustrated embodiment will not be repeated here.

[0193] Step 502: The server determines collaborative content for each collaborative device from the target document, and sends the collaborative content to each collaborative device.

[0194] In one embodiment, the server determines all the contents in the target document as the collaborative content. In this case, the collaborative contents corresponding to different collaborative devices are the same and are all complete target documents.

[0195] In another embodiment, the server determines, for each collaborative device, part of the content in the target document as the collaborative content corresponding to the collaborative device. Here, the part of the content corresponding to different collaborative devices may be the same or different, and this application does not limit this.

[0196] Among them, the same partial content corresponding to different collaborative devices often occurs in the scenario where the user on the first device side is only allowed to collaborate on part of the content in the target document. For example, when the user on the first device side initiates a cross-device collaborative work request for the target document, he can select part of the content in the target document. The server determines the partial content as the collaborative content corresponding to each collaborative device based on the user's selection operation.

[0197] In order to realize that different collaborative devices correspond to different collaborative contents, the server can split the target document to obtain multiple sub-documents, and determine the contents in different sub-documents as collaborative contents corresponding to different collaborative devices. Specifically, in one embodiment, the server determines part of the contents in the target document as the collaborative contents corresponding to the collaborative devices for each collaborative device, and the specific implementation includes: obtaining a target document splitting strategy, splitting the target document based on the target document splitting strategy to obtain multiple sub-documents, and determining the contents in different sub-documents as collaborative contents corresponding to different collaborative devices.

[0198] In a specific technical implementation, the first device can choose whether to split the target document when initiating a cross-device collaborative operation for the target document. If the target document is not split, each collaborative device can receive the complete target document. If the target document is split, each collaborative device can only receive part of the target document, and the content received by different collaborative devices may be different.

[0199] In the case of choosing to split the target document, as an optional implementation method, the user on the first device side can manually set the above-mentioned target document splitting strategy, for example, the first device provides a user interaction interface, so that the user can set the target document splitting strategy through the user interaction interface. After that, the first device sends the target document splitting strategy manually set by the user to the server, for example, carrying the target document splitting strategy in the cross-device collaborative operation request, so that the server parses the target document splitting strategy from the cross-device collaborative operation request, and splits the target document based on the target document splitting strategy. Here, the target document splitting strategy can not only indicate the splitting method of the target document, but also indicate the distribution method of the sub-documents after the split. For example, the target analysis strategy indicates that the target document is split into 3 sub-documents: sub-document 1, sub-document 2 and sub-document 3, and indicates that sub-document 1 is distributed to device 1, sub-document 2 is distributed to device 2, and sub-document 3 is distributed to device 3.

[0200] As another optional implementation, the server may intelligently determine a target document splitting strategy for the target document, and split the target document based on the target document splitting strategy. Optionally, the server identifies the document type of the target document, and determines a document splitting strategy that matches the document type of the target document from a preset document splitting strategy set as the target document splitting strategy. The above document splitting strategy set includes a correspondence between document types and document splitting strategies, and the above document splitting strategy that matches the document type of the target document refers to the document splitting strategy corresponding to the document type of the target document in the document splitting strategy set.

[0201] For example, for table-type documents, the corresponding document splitting strategies include splitting by sheet, splitting by row, splitting by column, etc. For text-type documents, the corresponding document splitting strategies include splitting by page, splitting by paragraph, splitting by chapter, etc.

[0202] Further optionally, after determining the target splitting strategy, the server can generate a splitting effect preview image according to the target splitting strategy, and return the splitting effect preview image to the first device for display, so that the user can make a final confirmation. After the user confirms, the server splits the target document based on the target splitting strategy confirmed by the user. Through this processing, the document splitting result can meet the user's needs while simplifying the user operation, thereby improving the user experience.

[0203] In addition, for the target document splitting strategy intelligently acquired by the server, when matching the collaborative devices corresponding to the split sub-documents, multiple sub-documents can be matched to multiple collaborative devices in sequence according to the default order of the collaborative devices. For example, there are three collaborative devices, and the default order of the three collaborative devices is device 2, device 3, and device 1. Then sub-document 1 can be matched to device 2, sub-document 2 can be matched to device 3, and sub-document 3 can be matched to device 1. Matching a sub-document to a collaborative device here means determining that the sub-document corresponds to the collaborative device, and then assigning the sub-document to the collaborative device.

[0204] So far, an explanation has been given on how the server determines the collaborative content corresponding to each collaborative device. Now, an explanation will be given on how the server sends the collaborative content corresponding to each collaborative device.

[0205] In one embodiment, the server may concurrently send the corresponding collaborative content to each collaborative device. That is, multiple collaborative devices may receive the collaborative content at the same time. The collaborative content here may be the entire content of the target document or part of the content in the target document, and this application does not make specific limitations on this.

[0206] In another embodiment, the server may asynchronously send the corresponding collaborative content to each collaborative device. For example, in an electronic signature scenario, multiple users are required to sign in a file in turn, so the server may send the file to be signed (i.e., collaborative content) to each collaborative device in turn, and send the file to the next user after the previous user completes the signature. In this regard, as an optional implementation method, the specific implementation of the server sending its corresponding collaborative content to each collaborative device includes: determining the document flow order, and sending its corresponding collaborative content to each collaborative device in turn according to the document flow order, wherein, when it is determined that the current collaborative device has completed editing of its corresponding collaborative content, sending its corresponding collaborative content to the next collaborative device in the document flow order. In this case, only one collaborative device can see and edit the collaborative content at the same time.

[0207] For example, the collaborative devices include devices 1 to 5, and the document flow order is device 1, device 2, device 3, device 4, and device 5. When the initiating device triggers cross-device collaborative signing for the target document, the server determines the target document as the collaborative content of devices 1 to 5, first sends the target document to device 1, and device 1 completes the signing of the target document (that is, completes the editing of the collaborative content). After the trigger document continues to flow, the server continues to send the target document to device 2, and device 2 completes the signing of the target document. After the trigger document continues to flow, the server continues to send the target document to device 3, and so on, until device 5 completes the signing of the target document.

[0208] One thing that needs to be explained here is that after each collaborative device completes signing the target document, the target document will be updated, specifically, the target document will be signed by a new collaborative device. The target document sent by the server to the next collaborative device can be the updated target document, so that the next collaborative device can view the editing results of the target document by the previous collaborative device. In addition, after the last collaborative device completes signing the target document and triggers the document to continue to flow, since the target document will synchronously present the signature of the last collaborative device on the target document, this is equivalent to the target document that has been collaboratively edited returning to the initiating device, forming a closed loop of document flow. Here, when the server is deployed on any collaborative device, it is equivalent to the previous collaborative device sending the collaborative content to the next collaborative device.

[0209] One more point to add is that in the above example, the target document sent by the server to the next collaborative device can also be the original target document, which makes the editing results of the target document by different collaborative devices invisible to each other, thereby meeting the user's confidential editing needs. For example, in a cross-device collaborative voting scenario, users are usually required to vote independently, so that the voting results of different users are invisible to each other, thereby avoiding interference between users.

[0210] The above description is an example of an application scenario in which the target document is circulated sequentially as a whole. In this type of application scenario, the initiating device can specify to circulate sequentially, and then the server will circulate the target document sequentially according to the above embodiment. Alternatively, the server can also intelligently identify the scenario and choose whether to dispatch synchronously or circulate sequentially based on the identification result.

[0211] Among them, as an optional implementation method, the server can extract keywords from the document name of the target document, intelligently identify the scenario based on the keywords, and further select whether to circulate it sequentially. For example, when the document name of the target document includes keywords such as information collection and electronic signature, the application scenario is determined to be a scenario of sequentially circulating documents, and then the target document is circulated sequentially. Here, it should be noted that the server can also use this implementation method to intelligently identify whether the target document needs to be split. For example, when it is identified that the document name of the target document includes keywords such as information collection and partition check, it is determined that the target document needs to be split.

[0212] As another optional implementation, the server may choose whether to circulate sequentially based on the user's usage habits, or the scenarios that the user frequently uses, or the scenarios that the user last used. For example, if the user's usage habits indicate that the user is accustomed to synchronous dispatch, the server will synchronously dispatch the target document. For another example, if the scenario that the user frequently uses is a scenario of sequentially circulating documents, the server will sequentially circulate the target document.

[0213] Here is another point to add. After the server intelligently selects the flow mode (including synchronous dispatch and sequential flow), it can send the selection result to the initiating device so that the user on the initiating device side can make a final confirmation on the flow mode. After that, the server will flow the target document in the flow mode finally confirmed by the user. Through this processing, the target document can be circulated in the most appropriate way possible to meet user needs and improve user experience.

[0214] In actual applications, there are also application scenarios where different parts of the target document are circulated in sequence, such as a scenario of collecting team member information. In this scenario, team members are required to fill in their corresponding personal information lines in sequence. In this regard, as an optional implementation method, the specific implementation of the server sending its corresponding collaborative content to each collaborative device includes: determining the document circulation order, setting the collaborative content corresponding to each collaborative device to a locked state, and synchronously sending its corresponding collaborative content in a locked state to each collaborative device, sending an unlocking instruction to each collaborative device in sequence according to the document circulation order, so that the collaborative device unlocks the collaborative content in a locked state according to the unlocking instruction, wherein, when it is determined that the current collaborative device has completed editing of its corresponding collaborative content, an unlocking instruction is sent to the next collaborative device in the document circulation order, and the collaborative content is allowed to be viewed and / or edited in the unlocked state.

[0215] Combine the following Figure 6 The example application scenario explains the above implementation method:

[0216] Figure 6In the application scenario shown, the initiating device triggers cross-device collaborative form filling, and the server splits the target document (here refers to the form document to be filled in), specifically, each blank line can be split into a sub-document, and then the server sets each sub-document to a locked state, and synchronously sends its corresponding collaborative content in a locked state to the collaborative devices (here including device 1, device 2, and device 3), where the first blank line is sent to device 1, the second blank line is sent to device 2, and the third blank line is sent to device 3. It should be noted here that at this time each sub-document is in a locked state, so each sub-document is not viewable to the corresponding collaborative device. Afterwards, the server first sends an unlock instruction to device 1 in the order of document flow, and device 1 unlocks the first blank line in the locked state according to the unlock instruction. Then device 1 fills in the information in the first blank line, and then device 1 triggers confirmation. After device 1 triggers confirmation, the server considers that the current collaborative device has completed editing of its corresponding collaborative content, and then the server sends an unlock command to device 2 in the order of document flow. Device 2 unlocks the second blank line in the locked state according to the unlock command, and then device 2 fills in the information in the second blank line, and then device 2 triggers confirmation. After device 2 triggers confirmation, the server considers that the current collaborative device has completed editing of its corresponding collaborative content, and then the server sends an unlock command to device 3 in the order of document flow until device 3 completes filling in the information in the third blank line.

[0217] It can be seen that in the above implementation, the server dispatches collaborative content to multiple collaborative devices at the same time, and it adopts a distributed lock control method to realize the sequential flow of different parts of the target document. In addition, since the server dispatches collaborative content to multiple collaborative devices at the same time, and the previous collaborative device can be quickly transferred to the next collaborative device by unlocking after the editing is completed and triggered, the flow efficiency can be improved.

[0218] One more point to be explained here is that the specific handling authority of the collaborative content in a locked state can be manually specified by the user on the initiating device side. For example, the collaborative content in a locked state can be set to only allow viewing but not editing, or not allow viewing. The embodiments of the present application do not limit this.

[0219] The above embodiments involve the document flow order, and a brief description of the setting of the document flow order is given here.

[0220] Among them, as an optional implementation method, the user on the initiating device side can manually specify the document flow order. For example, the team members include four people, A, B, C, and D. The user on the initiating device side can set the document flow order to B, C, A, and D.

[0221] As another optional implementation method, the server can use intelligent sorting to determine the order of document flow. Optionally, the server can determine the intimacy between each collaborative device and the initiating device, and then determine the order of document flow in order of intimacy from high to low, so as to first transfer the target document (or part of its content) to the closest collaborative device, and then transfer it one by one to collaborative devices with lower intimacy. Here, the server can comprehensively judge the intimacy between each collaborative device and the initiating device based on parameters such as account similarity, communication frequency, and recent communication time. The specific determination method is not limited in this application.

[0222] Step 503: The server obtains collaborative editing information of the collaborative content on at least one collaborative device, and synchronizes the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

[0223] The collaborative editing information refers to the operation information of the collaborative device editing the collaborative content on the collaborative device. For the convenience of description, it is referred to as collaborative editing information. The editing mentioned here may include deleting content, modifying content, adding content, annotating content, etc., where the modified content includes text modification and text format modification. For example, text modification includes modifying typos, and text format modification includes modifying font color, font size, etc.

[0224] In the embodiment of the present application, any collaborative device responds to the editing operation of the collaborative content on the collaborative device, obtains the operation information of the editing operation, and sends the editing information as collaborative editing information to the server, so that the server sends the collaborative editing information to the first device. After the first device receives the collaborative editing information, it edits the target document according to the collaborative editing information, so that the editing operation of the collaborative content by other devices and the editing results can be synchronously displayed on the initiating device (i.e., the first device).

[0225] In addition, as an optional embodiment, after the server sends the corresponding collaborative content to each collaborative device, the first device may also send the main editing information of the first device for any collaborative content in the target document to the server. The server can then obtain the main editing information of the first device for any collaborative content in the target document, and send the main editing information to the corresponding collaborative device, so that the collaborative device can edit the collaborative content on the collaborative device according to the main editing information.

[0226] The above-mentioned main editing information refers to the operation information of the initiating device (i.e., the first device) to edit the collaborative content on the collaborative device. For the convenience of description, it is referred to as the main editing information here. The editing mentioned here can include deleting content, modifying content, adding content, annotating content, etc., where the modified content includes text modification and text format modification. For example, text modification includes modifying typos, and text format modification includes modifying font color, font size, etc.

[0227] Through this embodiment, the editing operation and editing results of the initiating device on the collaborative content can also be synchronously displayed on other devices in real time, which further improves the effect of cross-device collaborative work.

[0228] Here is an additional point. In actual applications, users can choose whether to synchronize the editing operations and editing results of the initiating device on the collaborative content on other devices in real time according to actual business needs. For example, if the user only needs to view the collaborative editing information of the target document by the collaborative device, and does not want to disclose his or her main editing information of the target document to other collaborative devices, then the user can configure the initiating device not to send the above main editing information to the server, so as to ensure the privacy of the editing operations on the local end.

[0229] The technical solution provided by the embodiment of the present application determines at least one collaborative device through a server responding to a cross-device collaborative operation request for a target document from a first device, determines the collaborative content corresponding to each collaborative device from the target document, sends the corresponding collaborative content to each collaborative device, obtains collaborative editing information of at least one collaborative device for its corresponding collaborative content, and sends the collaborative editing information to the first device so that the first device edits the target document according to the collaborative editing information, thereby realizing cross-device collaborative operations for the same document. Furthermore, since the collaborative device can be determined through extremely simple operations and the collaborative content can be assigned to the collaborative device, the process of establishing connections between devices is greatly simplified, and the editing information can be directly synchronized between the first device and its collaborative devices without the need to introduce other carriers to realize collaborative editing of the same document between different devices, thereby improving the efficiency of cross-device collaborative operations for the same document.

[0230] Figure 7 A flowchart of an embodiment of another cross-device collaborative operation method provided in an embodiment of the present application. Figure 7 The illustrated process explains the cross-device collaborative operation method provided in the embodiment of the present application from the perspective of the interaction among the first device, the second device and the server.

[0231] like Figure 7 As shown, the following steps are included:

[0232] Step 701: The first device obtains a target document.

[0233] Step 702: In response to a trigger operation on a target document, the first device sends a cross-device collaborative operation request for the target document to the server.

[0234] For the description of step 701 and step 702, please refer to the above Figure 2 The relevant description in the illustrated embodiment will not be repeated here.

[0235] Step 703: The server determines that the second device is a collaborative device in response to the cross-device collaborative operation request.

[0236] In one embodiment, the cross-device collaborative operation request carries the device identification of the second device, so that the server determines the second device as a collaborative device.

[0237] In another embodiment, the associated device list of the first device includes the device identification of the second device, so that the server determines the second device as a collaborative device.

[0238] For a more detailed explanation of step 703, please refer to the above Figure 2 and Figure 5 The relevant descriptions in the illustrated embodiment will not be repeated here.

[0239] Step 704 : The server determines the collaborative content corresponding to the second device from the target document, and sends the collaborative content corresponding to the second device; and continues to execute step 705 and / or step 707 .

[0240] Step 705: The second device sends collaborative editing information of the corresponding collaborative content by the second device to the server.

[0241] Step 706: The server sends the collaborative editing information to the first device.

[0242] Step 707: The first device edits the target document according to the collaborative editing information, and the process ends.

[0243] Step 708: The first device sends the primary editing information of the first device for the collaborative content in the target document to the server.

[0244] Step 709: The server sends the primary editing information to the second device.

[0245] Step 710: The second device edits the collaborative content on the second device according to the main editing information.

[0246] For a more detailed explanation of steps 704 to 708, please refer to the above Figure 2 and Figure 5The relevant descriptions in the illustrated embodiment will not be repeated here.

[0247] In addition, in one embodiment, the server can also monitor the status of any collaborative device. If it is found that a collaborative device is disconnected, the server can return the status of the collaborative device to the initiating device, so that the initiating device can re-initiate a cross-device collaborative operation request with the collaborative device, thereby restoring the connection between the initiating device and the collaborative device.

[0248] The technical solution provided in the embodiment of the present application realizes cross-device collaborative work on the same document, and because the collaborative device can be determined through extremely simple operations and the collaborative content can be assigned to the collaborative device, the process of establishing a connection between devices is greatly simplified, and editing information can be directly synchronized between the first device and its collaborative device without introducing other carriers to realize collaborative editing of the same document between different devices, thereby improving the efficiency of cross-device collaborative work on the same document.

[0249] Figure 8 This is a block diagram of an embodiment of a cross-device collaborative operation apparatus provided in an embodiment of the present application. Figure 8 As shown, the device comprises:

[0250] A device determining module 81, configured to determine at least one collaborative device in response to a cross-device collaborative operation request for a target document from a first device;

[0251] A content determination module 82, configured to determine the collaborative content of each collaborative device from the target document;

[0252] A content sending module 83, configured to send the collaborative content to each collaborative device;

[0253] The first synchronous editing module 84 is configured to obtain collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

[0254] In an optional embodiment, the device further comprises:

[0255] A third synchronous editing module is used to obtain the main editing information of the first device for the collaborative content in the target document after sending the collaborative content to each of the collaborative devices, and send the main editing information to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0256] In an optional implementation manner, the third synchronous editing module is specifically used to:

[0257] Sending the main editing information to the selected collaborative device;

[0258] Alternatively, the selected main editing information is sent to the selected collaborative device;

[0259] Alternatively, the selected main editing information is sent to the collaborative device corresponding to the selected collaborative content.

[0260] In an optional embodiment, the device comprises:

[0261] An operation undo module is used to send an undo instruction to the collaborative device in response to the first device undoing the target editing operation on the collaborative content after the main editing information is sent to the collaborative device, so that the collaborative device cancels the target editing operation on the collaborative content on the collaborative device according to the undo instruction.

[0262] In an optional implementation manner, the device determination module 81 is specifically configured to:

[0263] Parsing at least one target device identifier from the cross-device collaborative operation request;

[0264] The device associated with the target device identifier is determined as the collaborative device.

[0265] In an optional implementation manner, the device determination module 81 is specifically configured to:

[0266] Acquire a list of associated devices of the first device, wherein the list of associated devices includes device identifiers of devices associated with the first device;

[0267] The devices in the associated device list are determined as cooperative devices.

[0268] In an optional implementation, the first synchronization editing module 84 is specifically used to:

[0269] receiving collaborative editing information from at least one of the collaborative devices, wherein the collaborative device obtains operation information of the editing operation in response to an editing operation on the collaborative content on the collaborative device, and sends the editing information as collaborative editing information to the server;

[0270] The collaborative editing information is synchronized to the first device, so that the first device edits the target document according to the collaborative editing information.

[0271] In an optional implementation manner, the content determination module 82 is specifically configured to:

[0272] determining all the contents in the target document as the collaborative contents of each collaborative device; or,

[0273] For each of the collaborative devices, part of the content in the target document is determined as the collaborative content of the collaborative device.

[0274] In an optional implementation, the content determination module 82 includes:

[0275] A strategy acquisition unit, used for acquiring a target document splitting strategy;

[0276] A document splitting unit, used for splitting the target document based on the target document splitting strategy to obtain multiple sub-documents;

[0277] The first determining unit is configured to determine the contents in different sub-documents as collaborative contents of different collaborative devices.

[0278] In an optional implementation manner, the policy acquisition unit is specifically configured to:

[0279] Parsing a target document splitting strategy from the cross-device collaborative operation request;

[0280] In an optional implementation, the policy acquisition unit includes:

[0281] A type identification unit, used to identify the document type of the target document;

[0282] The matching subunit is used to determine a document splitting strategy that matches the document type of the target document from a preset document splitting strategy set as a target document splitting strategy.

[0283] In an optional implementation, the content sending module 83 includes:

[0284] A second determining unit, used to determine the document flow order;

[0285] The first circulation unit is configured to send the corresponding collaborative content to each collaborative device in sequence according to the document circulation order, wherein when it is determined that the current collaborative device has completed editing the collaborative content, the collaborative content is sent to the next collaborative device in the document circulation order.

[0286] In an optional implementation, the content sending module 83 includes:

[0287] A third determining unit, used to determine the document flow order;

[0288] A locking unit, used to set the collaborative content of each collaborative device to a locked state;

[0289] A second transfer unit, configured to synchronously send the collaborative content in a locked state to each of the collaborative devices;

[0290] An unlocking control unit is used to send unlocking instructions to each of the collaborative devices in sequence according to the document flow order, so that the collaborative device unlocks the collaborative content in a locked state according to the unlocking instructions, wherein, when it is determined that the current collaborative device has completed editing the collaborative content, the unlocking instruction is sent to the next collaborative device in the document flow order, and the collaborative content is allowed to be viewed and / or edited in an unlocked state.

[0291] Fig. 9 This is a block diagram of another embodiment of a cross-device collaborative operation apparatus provided in an embodiment of the present application. Fig. 9 As shown, the device comprises:

[0292] The document acquisition module 91 is used to acquire the target document;

[0293] A request sending module 92 is used to send a cross-device collaborative operation request for the target document to the server in response to a trigger operation on the target document, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines the collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content by at least one collaborative device, and synchronizes the collaborative editing information to the first device;

[0294] The second synchronous editing module 93 is configured to receive collaborative editing information of the collaborative content from at least one collaborative device, and edit the target document according to the collaborative editing information.

[0295] In an optional embodiment, the device further comprises:

[0296] A fourth synchronous editing module is used to send the main editing information of the first device for the collaborative content in the target document to the server after the server sends the corresponding collaborative content to each collaborative device, so that the server sends the main editing information to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

[0297] In an optional implementation, the request sending module 92 includes:

[0298] a list presenting unit, configured to present, in response to a triggering operation on the target document, a list of associated devices, wherein the list of associated devices includes device identifiers of devices associated with the first device;

[0299] A target determination unit is used to determine the device identifier selected in the associated device list as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and send the cross-device collaborative operation request to the server so that the server determines at least one collaborative device according to the target device identifier.

[0300] In an optional implementation manner, the request sending module 92 is specifically configured to:

[0301] In response to a device push request from a server, determining that a trigger operation on the target document is detected, wherein the server responds to a collaboration request sent by the second device when shaking, and in the case where it is determined that the geographical location relationship between the first device and the second device meets a set condition, sends the device push request to the first device, wherein the device push request carries a device identifier of the second device;

[0302] In response to a trigger operation on the target document, the device identifier of the second device is parsed from the device push request, and the device identifier of the second device is determined as the target device identifier to be carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server, so that the server determines the second device as a collaborative device according to the target device identifier.

[0303] In an optional implementation manner, the request sending module 92 is specifically configured to:

[0304] In response to establishing a near field connection with a second device, determining that a triggering operation on the target document is detected;

[0305] In response to a trigger operation on the target document, the device identifier of the second device is determined as the target device identifier and carried in a cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server so that the server determines the second device as a collaborative device based on the target device identifier.

[0306] In an optional embodiment, the device further comprises:

[0307] An association module is used to determine the second device as an associated device of the first device and add a device identifier of the second device to an associated device list of the first device after the cross-device collaborative operation request is sent to the server.

[0308] like Fig.10As shown, an embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0309] Memory 113, used for storing computer programs;

[0310] In one embodiment of the present application, the processor 111 is used to implement the cross-device collaborative operation method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 113, including:

[0311] In response to a cross-device collaborative operation request for a target document from a first device, determining at least one collaborative device;

[0312] Determine collaborative content of each collaborative device from the target document, and send the collaborative content to each collaborative device;

[0313] Acquire collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

[0314] or,

[0315] Get the target document;

[0316] In response to a trigger operation on the target document, a cross-device collaborative operation request for the target document is sent to a server, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content on at least one collaborative device, and synchronizes the collaborative editing information to the first device;

[0317] Receive collaborative editing information of the corresponding collaborative content from at least one of the collaborative devices, and edit the target document according to the collaborative editing information.

[0318] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the steps of the cross-device collaborative operation method provided by any of the aforementioned method embodiments are implemented.

[0319] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0320] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0321] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0322] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A cross-device collaborative operation method, characterized in that: The method comprises: In response to a cross-device collaborative operation request for a target document from a first device, determining at least one collaborative device; Determine collaborative content of each collaborative device from the target document, and send the collaborative content to each collaborative device; Acquire collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

2. The method according to claim 1, characterized in that After sending the collaborative content to each collaborative device, the method further includes: The main editing information of the first device for the collaborative content in the target document is acquired, and the main editing information is sent to the collaborative device, so that the collaborative device edits the collaborative content on the collaborative device according to the main editing information.

3. The method according to claim 2, characterized in that The sending the main editing information to the collaborative device includes: Sending the main editing information to the selected collaborative device; Alternatively, the selected main editing information is sent to the selected collaborative device; Alternatively, the selected main editing information is sent to the collaborative device corresponding to the selected collaborative content.

4. The method according to claim 2, characterized in that: After sending the main editing information to the collaborative device, the method further includes: In response to the first device canceling the target editing operation on the collaborative content, a cancellation instruction is sent to the collaborative device, so that the collaborative device cancels the target editing operation on the collaborative content on the collaborative device according to the cancellation instruction.

5. The method according to claim 1, characterized in that The determining of at least one collaborative device includes: Parsing at least one target device identifier from the cross-device collaborative operation request; determining a device associated with the target device identifier as the collaborative device; Alternatively, a list of associated devices of the first device is obtained, wherein the list of associated devices includes device identifiers of devices associated with the first device; and the devices in the list of associated devices are determined as collaborative devices.

6. The method according to claim 1, characterized in that The acquiring collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronizing the collaborative editing information to the first device so that the first device edits the target document according to the collaborative editing information, includes: receiving collaborative editing information from at least one of the collaborative devices, wherein the collaborative device, in response to an editing operation on the collaborative content on the collaborative device, obtains operation information of the editing operation, and sends the operation information as the collaborative editing information to the server; The collaborative editing information is synchronized to the first device, so that the first device edits the target document according to the collaborative editing information.

7. The method according to claim 1, characterized in that The determining the collaborative content of each collaborative device from the target document includes: determining all the contents in the target document as the collaborative contents of each collaborative device; or, For each of the collaborative devices, part of the content in the target document is determined as the collaborative content of the collaborative device.

8. The method according to claim 7, characterized in that The determining, for each of the collaborative devices, part of the content in the target document as collaborative content of the collaborative device includes: Get the target document splitting strategy; Splitting the target document based on the target document splitting strategy to obtain multiple sub-documents; The contents in different sub-documents are determined as collaborative contents of different collaborative devices.

9. The method according to claim 8, characterized in that The step of obtaining the target document splitting strategy includes: Parsing a target document splitting strategy from the cross-device collaborative operation request; Alternatively, the document type of the target document is identified, and a document splitting strategy matching the document type of the target document is determined from a preset document splitting strategy set as the target document splitting strategy.

10. The method according to claim 1, characterized in that The sending the collaborative content to each collaborative device includes: Determine the order of document flow; The collaborative content is sent to each collaborative device in sequence according to the document flow order, wherein when it is determined that the current collaborative device has completed editing of the collaborative content, the collaborative content is sent to the next collaborative device in the document flow order.

11. The method according to claim 1, characterized in that: The sending the collaborative content to each collaborative device includes: Determine the order of document flow; Setting the collaborative content of each collaborative device to a locked state, and synchronously sending the collaborative content in the locked state to each collaborative device; An unlocking instruction is sent to each of the collaborative devices in sequence according to the document flow order, so that the collaborative device unlocks the collaborative content in a locked state according to the unlocking instruction, wherein, when it is determined that the current collaborative device has completed editing the collaborative content, the unlocking instruction is sent to the next collaborative device in the document flow order, and the collaborative content is allowed to be viewed and / or edited in an unlocked state.

12. A cross-device collaborative operation method, characterized in that: The method comprises: Get the target document; In response to a trigger operation on the target document, a cross-device collaborative operation request for the target document is sent to a server, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content on at least one collaborative device, and synchronizes the collaborative editing information to the first device; The collaborative editing information of the collaborative content is received on at least one of the collaborative devices, and the target document is edited according to the collaborative editing information.

13. The method according to claim 12, characterized in that After the server sends the collaborative content to each of the collaborative devices, the method further includes: The main editing information of the first device for the collaborative content in the target document is sent to the server, so that the server sends the main editing information to the collaborative device.

14. The method according to claim 12, characterized in that The step of sending a cross-device collaborative operation request for the target document to a server in response to a trigger operation on the target document includes: In response to a triggering operation on the target document, presenting a list of associated devices; The device identifier selected in the associated device list is determined as the target device identifier and carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server.

15. The method according to claim 12, characterized in that The step of sending a cross-device collaborative operation request for the target document to a server in response to a trigger operation on the target document includes: In response to a device push request from a server, determining that a trigger operation on the target document is detected; Parsing the device identifier of the second device from the device push request; The device identification of the second device is determined as the target device identification to be carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server.

16. The method according to claim 12, characterized in that The step of sending a cross-device collaborative operation request for the target document to a server in response to a trigger operation on the target document includes: In response to establishing a near field connection with a second device, determining that a triggering operation on the target document is detected; The device identification of the second device is determined as the target device identification to be carried in the cross-device collaborative operation request for the target document, and the cross-device collaborative operation request is sent to the server.

17. A cross-device collaborative operation device, characterized in that: The device comprises: A device determination module, configured to determine at least one collaborative device in response to a cross-device collaborative operation request from a first device for a target document; A content determination module, used to determine the collaborative content of each collaborative device from the target document; A content sending module, used for sending the collaborative content to each collaborative device; The first synchronous editing module is used to obtain collaborative editing information of the collaborative content on at least one of the collaborative devices, and synchronize the collaborative editing information to the first device, so that the first device edits the target document according to the collaborative editing information.

18. A cross-device collaborative operation device, characterized in that: The device comprises: A document acquisition module is used to acquire target documents; A request sending module, configured to send a cross-device collaborative operation request for the target document to a server in response to a trigger operation on the target document, so that the server determines at least one collaborative device in response to the cross-device collaborative operation request; determines collaborative content of each collaborative device from the target document, and sends the collaborative content to each collaborative device; and obtains collaborative editing information of the collaborative content on at least one collaborative device, and synchronizes the collaborative editing information to the first device; The second synchronous editing module is configured to receive collaborative editing information of the collaborative content from at least one of the collaborative devices, and edit the target document according to the collaborative editing information.

19. An electronic device, characterized in that: include: A processor and a memory, wherein the processor is used to execute a cross-device collaborative operation program stored in the memory to implement the cross-device collaborative operation method according to any one of claims 1 to 11 or claims 12 to 16.

20. A storage medium, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the cross-device collaborative operation method described in any one of claims 1 to 11 or claims 12 to 16.

Images