Document collaborative interaction method and system

By monitoring user operations and automatically managing document collaborative interaction status, complex operations in the existing technology are solved, and the functions of editing and browsing documents without interrupting perspective follow-up are realized, improving user experience and work efficiency.

CN119987620APending Publication Date: 2025-05-13EEO EDUCATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510063271.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-01-15
Publication Date
2025-05-13

AI Technical Summary

Technical Problem

The collaborative interaction of existing documents is complicated. Users need to manually close the collaborative state when editing or viewing other parts. After completing the editing, they start the synchronous view again, and the operation process is cumbersome.

Method used

A document collaborative interaction method is proposed. By monitoring user operations, it automatically enters the viewing angle following state, temporarily leaves the viewing angle following state or closes the viewing angle following state, and updates the user interface in real time, allowing users to operate and browse documents without interrupting viewing angle following.

Benefits of technology

The user operation path is simplified, and users can edit and browse documents without interrupting the perspective of following, automatically and quickly return to the perspective of following state, improving collaboration experience and work efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119987620A_ABST
    Figure CN119987620A_ABST
Patent Text Reader

Abstract

The invention provides a document collaborative interaction method and system, and the method comprises the steps: entering a visual angle following state when monitoring that a user requests visual angle following, displaying a document browsing region of a collaborative member on a user interface, and updating the display of the user interface in real time according to the operation of the collaborative member; when it is monitored that the user performs a set pause operation, entering a temporary separation state, continuing to record the document browsing area data of the collaborative members, but not sending the browsing area data of the collaborative members to the user any more; when it is monitored that the user carries out setting recovery following operation, recovering the visual angle following state; and when it is monitored that the user performs a set stop following operation, entering a closed view angle following state, and not sending browse area data of the collaborative members to the user any more. The method has the advantages that the collaborative document content can be operated and the area except the view angle following can be browsed by not closing and interrupting the view angle following, and the view angle following can be automatically and quickly returned.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of document collaboration technology, and specifically relates to a document collaborative interaction method and system. Background Art

[0002] Document view tracking is a very convenient technical means in collaborative work. Document view tracking means that in a multi-person collaborative environment, when a user chooses to view the current view of another collaborative member, the system automatically adjusts the user's view to the same area as the selected member and enables the collaborative members to view the content synchronously. This makes it convenient for team members to quickly understand each other's work progress, discuss specific content, or review content together.

[0003] Existing perspective tracking technologies (such as Figma) have the following functions: (1) In the system interface, each online collaborator will display a small avatar, usually located in the upper right corner of the top of the file. These avatars indicate whether other members are currently online and their position in the file. (2) When a user clicks on the avatar of a collaborator, the system captures the member's current view state, including information such as the design area they are viewing and the zoom level. (3) The system then smoothly transitions the user's view to the same view state as the selected member, ensuring that the user can see what the selected member is focusing on.

[0004] With the development of remote collaboration and online editing tools, users need more efficient ways to collaborate with multiple people in real time. Existing collaborative editing platforms (such as Figma) provide basic perspective following functions, allowing users to synchronize their views by clicking on the avatars of other collaborative members. However, once the user needs to edit the document or view other parts, they need to manually close the collaborative state before operating; when the editing is completed, the collaborative operation needs to be triggered again to start synchronizing the view. Summary of the invention

[0005] The purpose of this application is to overcome the defects of complex collaborative interaction operations of existing documents.

[0006] In order to achieve the above objectives, this application proposes a document collaborative interaction method, including:

[0007] When a user request for view following is detected, the view following state is entered, the document content location data of the collaborative member and the relative position of the current scrolling area are sent to the user, the document browsing area of ​​the collaborative member is displayed on the user interface, and the user interface display is updated in real time according to the collaborative member's operation;

[0008] When the user sets a pause operation, the system enters a temporary detachment state and continues to record the collaborative member's document browsing area data, but no longer sends the collaborative member's browsing area data to the user;

[0009] When the user is detected to perform the set follow-up operation, the view-following state is restored;

[0010] When it is detected that the user has set a stop following operation, the view following state is closed and the browsing area data of the collaborative members is no longer sent to the user.

[0011] As an improvement of the above method, the setting of the pause operation includes: mouse scrolling, shortcut keys or document editing operations.

[0012] As an improvement of the above method, the setting recovery follow-up operation includes: mouse gesture, clicking a setting button, shortcut key or no action for more than a set time.

[0013] As an improvement to the above method, the method further includes: displaying the identifications of all users who operate on the current document on the user interface.

[0014] The present application also provides a document collaborative interaction system, which is implemented based on the above method, and the system includes:

[0015] The interface display module is used to display document content, collaborative member identification and function buttons in the interface;

[0016] A document collaboration module, used to send the document location data of the collaboration member and the relative location of the current scrolling area to the user who initiates the follow-up in real time; and

[0017] The action monitoring module is used to monitor user operations on the interface and perform corresponding actions.

[0018] Compared with the prior art, the advantages of this application are:

[0019] This application allows users to operate collaborative document content and browse areas outside of the view following function without closing or interrupting the view following function, and can automatically and quickly return to the view following function. This technical solution can be extended to scenarios where collaborative software view following functions are required, shortening the user's operation path and improving a wide range of software user experiences. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 Shown is a flow chart of the document collaborative interaction method;

[0021] Figure 2 The figure shows a schematic diagram of the view following state of the document collaborative interaction system interface; the characters in the interface are schematic characters and have no specific meaning;

[0022] Figure 3 Shown is a schematic diagram of the document collaborative interaction system interface temporarily disconnected from the state; the characters in the interface are schematic and have no specific meaning. DETAILED DESCRIPTION

[0023] The technical solution of the present application is described in detail below with reference to the accompanying drawings.

[0024] like Figure 1 As shown, this application proposes a document collaborative interaction method and system, aiming to improve the user's collaborative experience and work efficiency. The method includes:

[0025] 1. Document content display and navigation;

[0026] like Figure 2 As shown in the figure, the areas displayed on the interface during document collaboration include:

[0027] Content display area: Gets the document content from the server based on the current user ID and renders it to the content display area of ​​the user interface.

[0028] Navigation bar area: The IDs of the online members of the current document are obtained through the server, and these members are displayed in the navigation bar area so that users can quickly select the perspective of the collaborative member to follow.

[0029] 2. Perspective following initialization;

[0030] After the user selects a collaboration member through the navigation bar and confirms it, the client sends a collaboration request to the server.

[0031] After receiving the request, the server records the document content location data of the selected collaborative member and the relative position of the current scrolling area, and sends these data to the user who initiated the follow-up to ensure that the displayed content is consistent with the collaborative member in real time.

[0032] 3. View following status;

[0033] After receiving the data returned by the server, the user enters the perspective following state. At this time, the server continuously synchronizes the real-time data of the document content location of the collaborative members to keep the user's view consistent with that of the collaborative members.

[0034] The system notifies the user that they are currently in the viewfollowing state and provides options to watch, exit follow, and enter temporary detachment mode.

[0035] 4. Temporarily exit the mode;

[0036] like Figure 3 As shown, when it is detected that the user performs a specific mouse event (such as scrolling, editing content) or a keyboard event (such as a set key combination), the system determines that the user needs to enter a temporary separation state and notifies the user that the following state has been currently separated.

[0037] In this mode, the server continues to record the user's current page location and the page location of the collaborative members, but no longer synchronizes changes between the two.

[0038] The system provides users with an operation button or shortcut key to resume following, allowing users to resynchronize back to the perspective of collaborative members at any time.

[0039] 5. Automatic recovery and following;

[0040] If the system detects that the user has no operation (such as scrolling, editing content) for more than a preset time (e.g. 5 seconds) in the temporary detached state, or the user actively triggers the resumption of follow-up, the server will resynchronize the document content location data of the collaborative members to make the user's view consistent with that of the collaborative members. Actively triggered actions include: mouse gestures, clicking set buttons or shortcut keys, etc.

[0041] 6. Stop following

[0042] The user can choose to turn off view tracking, and the system will determine that the tracking is over and stop all related data synchronization operations.

[0043] The present application also provides a document collaborative interaction system, which is implemented based on the above method and includes:

[0044] The interface display module is used to display the document content, collaborative member identification and function buttons in the interface. The document content status is divided into perspective following status, temporary detachment status and closed perspective following status. Function buttons include resume following and close following. Collaborative members include members who are currently editing or viewing the same document online.

[0045] The document collaboration module is used to send the collaborative member's document location data and the relative position of the current scrolling area to the user who initiates the follow-up in real time.

[0046] The monitoring action module is used to monitor the user's operations on the interface and perform corresponding actions, including: monitoring the user's selection of the collaborative member logo to enter the perspective following state, monitoring the mouse or shortcut key actions or editing operations to enter the temporary separation state, monitoring the mouse gestures or clicking buttons or shortcut key actions or no action timeout to enter the perspective following state, and monitoring the mouse or shortcut key actions to enter the closed perspective following state.

[0047] This application allows users to operate collaborative document content and browse areas outside of the view following mode without closing or interrupting the view following mode, and can automatically and quickly return to the view following mode. This technical solution can be extended to scenarios where collaborative software view following is required, shortening the user's operation path and improving a wide range of software user experiences.

[0048] The present application may also provide a computer device, comprising: at least one processor, a memory, at least one network interface and a user interface. The various components in the device are coupled together through a bus system. It is understood that the bus system is used to achieve connection and communication between these components. In addition to the data bus, the bus system also includes a power bus, a control bus and a status signal bus.

[0049] The user interface may include a display, a keyboard or a pointing device, such as a mouse, a trackball, a touch pad or a touch screen.

[0050] It is understood that the memory in the embodiments disclosed in the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). The memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0051] In some embodiments, the memory stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system and applications.

[0052] The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present disclosure can be included in the application.

[0053] In the above embodiment, the processor may also call a program or instruction stored in the memory, specifically, a program or instruction stored in an application program, and is used to:

[0054] Execute the steps of the above method.

[0055] The above method can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The above-disclosed methods, steps and logic block diagrams can be implemented or executed. The general processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the above-disclosed method can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor are combined to execute. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0056] It is understood that the embodiments described in the present application can be implemented by hardware, software, firmware, middleware, microcode or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application or a combination thereof.

[0057] For software implementation, the technology of the present application can be implemented by executing the functional modules (such as procedures, functions, etc.) of the present application. The software code can be stored in a memory and executed by a processor. The memory can be implemented in the processor or outside the processor.

[0058] The present application may also provide a non-volatile storage medium for storing a computer program. When the computer program is executed by a processor, each step in the above method embodiment can be implemented.

[0059] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present application and are not intended to limit it. Although the present application is described in detail with reference to the embodiments, a person skilled in the art should understand that any modification or equivalent replacement of the technical solution of the present application does not depart from the spirit and scope of the technical solution of the present application and should be included in the scope of the claims of the present application.

Claims

1. A document collaborative interaction method, comprising: When a user request for view following is detected, the view following state is entered, the document content location data of the collaborative member and the relative position of the current scrolling area are sent to the user, the document browsing area of ​​the collaborative member is displayed on the user interface, and the user interface display is updated in real time according to the collaborative member's operation; When the user sets a pause operation, the system enters a temporary detachment state and continues to record the collaborative member's document browsing area data, but no longer sends the collaborative member's browsing area data to the user; When the user is detected to perform the set follow-up operation, the view-following state is restored; When it is detected that the user has set a stop following operation, the view following state is closed and the browsing area data of the collaborative members is no longer sent to the user.

2. The document collaborative interaction method according to claim 1, characterized in that: The setting of the pause operation includes: mouse scrolling, shortcut keys or document editing operations.

3. The document collaborative interaction method according to claim 1, characterized in that: The setting recovery follow operation includes: mouse gesture, clicking a setting button, shortcut key or no action for a set time.

4. The document collaborative interaction method according to claim 1, characterized in that: Also includes: Displays the IDs of all users who have performed operations on the current document in the user interface.

5. A document collaborative interaction system, implemented based on the method described in any one of claims 1 to 4, characterized in that: The system comprises: The interface display module is used to display document content, collaborative member identification and function buttons in the interface; A document collaboration module, used to send the document location data of the collaboration member and the relative location of the current scrolling area to the user who initiates the follow-up in real time; and The action monitoring module is used to monitor user operations on the interface and perform corresponding actions.