A system for realizing document sharing and notification by DingDing integrated cloud document

Abstract

The application discloses a system for realizing document sharing and notification by solving the integration of Dingding and cloud documents, comprising an API gateway module, a user information management module and a cloud document and data sharing module; the API gateway module is used for connecting and communicating data between the chat software used by the user and multiple cloud document platforms; the user information management module is used for managing user data information and matching the user data information with the cloud documents that need to be edited and viewed; the cloud document and data sharing module is used for managing and storing cloud documents, automatically uploading and storing the cloud documents after being edited by the user, and supporting online editing of the user; the application solves technical problems such as file format compatibility, real-time collaboration, multi-device synchronization, version management, security control and the like, realizes seamless file intercommunication and collaborative editing through the integration of cloud document technology, a real-time synchronization mechanism and permission management, and improves operation convenience and team collaboration efficiency.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, specifically to a system for integrating DingTalk with cloud documents to achieve document sharing and notification. Background Technology

[0002] Traditional chat applications primarily offer file transfer functionality, allowing users to send and receive files in various formats (such as Word, PDF, images, and videos) through the chat window. File transfer is typically one-way; the recipient needs to download the file to their local machine, edit it using other software, and then re-upload or send the modified file. This disconnect between file transfer and editing necessitates frequent downloads and uploads, making the process cumbersome. Furthermore, it cannot support real-time collaborative editing by multiple users, resulting in low collaboration efficiency. File version management is also often disorganized, leading to frequent version conflicts.

[0003] With the widespread adoption of mobile work, users need to seamlessly switch between different devices (such as mobile phones, tablets, and computers) to view and edit files. Traditional file transfer methods cannot support multi-device collaboration, requiring users to manually synchronize files across different devices. These obstacles to multi-device collaboration lead to cumbersome operations and low collaboration efficiency. Synchronizing and managing files across different devices is difficult, easily resulting in file loss or version inconsistencies.

[0004] In team collaboration, real-time collaboration is key to improving efficiency. For example, multiple team members need to edit a document simultaneously and view each other's changes in real time. Traditional file transfer methods cannot support real-time collaboration among multiple people; users need to frequently send and receive files, leading to low collaboration efficiency. The lack of real-time collaboration results in low team collaboration efficiency, especially in remote work scenarios. Disorganized file version management also easily leads to version conflicts.

[0005] In enterprise environments, file security and privacy are paramount. Users need to ensure that files are not accessed by unauthorized individuals during transmission and storage. Traditional file transfer methods fail to provide sufficient security, and files may be stolen or tampered with during transmission. The security of file transmission and storage is difficult to guarantee, making data leaks or malicious attacks a possibility. File access permission management is challenging, making it impossible to precisely control the scope of file access.

[0006] Existing multi-device collaborative document processing methods (such as QQ online document editing) usually require additional requests for editing permissions from the document sender upon login, and the security of document transmission and storage is difficult to guarantee, making it prone to data leakage or malicious attacks. Summary of the Invention

[0007] To address the aforementioned issues, this invention provides a system for integrating DingTalk with cloud documents to achieve document sharing and notifications, comprising an API gateway module, a user information management module, a cloud document and data sharing module, and a permission management and recognition module. The API gateway module is used to connect and communicate data between the user's chat software and multiple cloud document platforms. The user information management module is used to manage user data information and match user data information with cloud documents that need to be edited and viewed; The cloud document and data sharing module is used to manage and store cloud documents. It automatically uploads and stores cloud documents after the user edits them, and supports online editing by the user. The permission management and identification module is used to allocate and manage permissions based on user data information, and automatically verify permissions after the user logs in.

[0008] Furthermore, the API gateway module is equipped with an F5 load balancer in the backend to distribute user-uploaded files to multiple backend service instances.

[0009] Furthermore, the cloud document platform specifically includes: Google Docs, Microsoft Office Online, and WPS Cloud Documents.

[0010] Furthermore, the user data information managed in the user information management module specifically includes: username, unique identifier ID, chat history, password, and document modification history.

[0011] Furthermore, the cloud document and data sharing module specifically includes the following sub-modules: document storage sub-module, document preview and editing sub-module, data encryption sub-module, data sharing sub-module, and format conversion sub-module; The document storage submodule is used to store user-uploaded documents and automatically upload and record each modification made by the user to the document content. It stores files and cloud documents in the cloud and supports file archiving, backup and classification management. The document preview and editing submodule is used to directly view, edit, and annotate user-uploaded documents, and supports multiple users to view, edit, and annotate documents simultaneously. The data encryption submodule is used to encrypt the edited document content and the data content to be shared; it is configured with a sandbox environment to isolate and execute suspicious files. The data sharing submodule is used to generate a shared link or shared QR code for the document to be edited, and send it to the corresponding user's chat software through the API gateway module; The format conversion submodule is used to convert the format of opened / edited or already edited documents.

[0012] Furthermore, the document types that the cloud document and data sharing module supports viewing, editing, and annotation operations specifically include: Word, Excel, PPT, PDF, and images.

[0013] Furthermore, the document preview and editing submodule is configured to: open the file in the built-in editor of the chat application in response to the user's click operation on the file in the chat window; and automatically save the edited file to the cloud after detecting the editing completion event.

[0014] Furthermore, the format conversion submodule supports format conversions including PDF to image and Word to HTML, and the conversion process is executed on a cloud server, with the converted files pushed to the client in a browser-compatible format.

[0015] Furthermore, it also includes a log recording module and a message queue module; the log recording module is used to record and store each user operation, and when the document is converted into a format, it stores the file information and the converted information into a MySQL database; The message queue module is used to send conversion status information to the message queue after the file format conversion is completed, so that the client can consume it asynchronously.

[0016] Furthermore, the workflow of the system includes: Users log into the chat software and connect and communicate with the cloud document platform via the API gateway module. Another user uploaded a document file that needed to be edited to the cloud document platform via a chat application; The system automatically identifies and detects whether the user has the permission to view and edit the document based on the user's current permissions. When the system detects that the user has the relevant permissions, the system pushes the document file to the user's chat window for viewing and editing. Specifically, the system automatically detects whether a user has the permission to view or edit the document based on their current permissions. This means that the system automatically detects whether the user has permission to edit the entire document or permission to edit part of the document. If the user only has permission to edit part of the document, the system automatically locks the editing permission for the non-permitted content, allowing only viewing.

[0017] This invention provides a system for integrating DingTalk with cloud documents to achieve document sharing and notifications, which has the following beneficial effects: This invention, by integrating cloud document technology, solves technical problems such as file format compatibility, real-time collaboration, multi-device synchronization, version management, and security control, achieving seamless interoperability and editing between files and cloud documents. Users can directly open, edit, and share files within the chat application, supporting real-time multi-user collaboration, automatic version management, and ensuring file security. Multi-device synchronization and format conversion functions enhance ease of use and team collaboration efficiency, providing users with an efficient, secure, and convenient file management and collaboration experience. Detailed Implementation

[0018] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0019] The following detailed description is based on the implementation method of the present invention. The description is only a part of the embodiments, not all of the embodiments. For clarity, representations and descriptions unrelated to the present invention are omitted in the description.

[0020] To provide a clearer understanding of the technical features, objectives, and beneficial effects of this invention, the following detailed description of the technical solution is provided. Obviously, the described embodiments are only a portion of the embodiments of this invention, not all of them, and should not be construed as limiting the scope of implementation of this invention. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without inventive effort are within the protection scope of this invention.

[0021] This invention provides a system for integrating DingTalk with cloud documents to achieve document sharing and notifications, including an API gateway module, a user information management module, a cloud document and data sharing module, and a permission management and recognition module.

[0022] The API gateway module connects and facilitates data communication between the user's chat software and multiple cloud document platforms (Google Docs, Microsoft Office Online, WPS Cloud Docs). Edited content in files and cloud documents can be synchronized in real time across different devices, allowing users to seamlessly switch between mobile phones, tablets, computers, and other devices.

[0023] The user information management module is used to manage user data (username, unique identifier ID, chat history, password, document modification history, user permissions) and match user data with cloud documents that need to be edited and viewed.

[0024] The cloud document and data sharing module is used to manage and store cloud documents. It automatically uploads and stores documents after users edit them, supporting online editing. Specifically, it includes the following sub-modules: document storage, document preview and editing, data encryption, data sharing, and format conversion.

[0025] The document storage submodule stores user-uploaded documents and automatically records each modification made by the user. Files and cloud documents are stored uniformly in the cloud, and users can directly manage and search for files through the chat application. Users can view the storage location and status of all files and cloud documents within the chat application. It supports file archiving, backup, and categorization management, allowing users to quickly organize and find files.

[0026] The document preview and editing submodule allows users to directly view, edit, and annotate user-uploaded documents (Word, Excel, PPT, PDF, images), supporting simultaneous viewing, editing, and annotation by multiple users. When a user clicks on a file in the chat window, the file automatically opens in the chat application's built-in editor. Direct editing of various file types (such as Word, Excel, PPT, PDF, images, etc.) is supported. After editing, the file is automatically saved to the cloud, eliminating the need for manual upload. Simultaneous editing of files or cloud documents by multiple users is supported, with all participants' modifications synchronized in real time, allowing users to view each other's edits. Multiple file types, including documents, spreadsheets, and presentations, are supported.

[0027] The data encryption submodule is used to encrypt the content of edited documents and data that needs to be shared. It supports file sandboxing technology to prevent attacks from malicious files.

[0028] The data sharing submodule is used to generate a sharing link or QR code for the document to be edited, and send it to the corresponding user's chat software through the API gateway module.

[0029] The format conversion submodule is used to convert the format of opened / edited or already edited documents (such as PDF to image, Word to HTML). Files received by users in the chat are automatically converted to browser-supported formats, allowing viewing and editing without the need for specific software installation. The file format conversion process is completed in the cloud, requiring no manual operation from the user. It receives user-uploaded Office files and distributes them to the backend service via F5 load balancing; the backend service converts the Office files to PDF files, or further converts PDFs to images; after conversion, the conversion information is sent to a message queue (MQ) for client confirmation; during the conversion process, file information and converted information are stored in a MySQL database.

[0030] File conversion: Users upload Office files, which are then transmitted to the backend service via API gateway and F5 load balancer. The backend service converts the files into PDF files.

[0031] Image conversion: Users upload Office files, which are then transmitted to the backend service via API gateway and F5 load balancer. The backend service converts the files into PDF files, and then converts the PDF files into images.

[0032] Message notification: The backend service performs file and image conversion. After the conversion is completed, it sends the converted information to the message queue (MQ). Users can confirm the completion of the conversion by consuming MQ messages.

[0033] The permission management and identification module is used to allocate and manage permissions based on user data information, and automatically verify permissions after the user logs in.

[0034] It also includes a logging module to record and store each user operation, and to store file information and converted information in a MySQL database during document format conversion. The backend service performs file and image conversion, storing file information and converted information in a MySQL database during the conversion process, and provides query functions for normal and abnormal logs.

[0035] The specific workflow of the system described in this invention is as follows: One user logs into the chat software and connects to the cloud document platform via the API gateway module for data communication. Another user uploads a document file to be edited to the cloud document platform through the chat software. The system automatically identifies and detects whether the user has the permission to view and edit the document based on their current permissions. If the system detects that the user has the relevant permissions, it pushes the document file to the user's chat window for viewing and editing. Specifically, the system automatically detects whether the user has the permission to edit the entire document or only a portion of it. If the user only has the permission to edit a portion of the document, the system automatically locks the editing permissions for the non-permitted content, allowing only viewing.

[0036] This invention, by integrating cloud document technology, solves technical problems such as file format compatibility, real-time collaboration, multi-device synchronization, version management, and security control, achieving seamless interoperability and editing between files and cloud documents. Users can directly open, edit, and share files within the chat application, supporting real-time multi-user collaboration, automatic version management, and ensuring file security. Multi-device synchronization and format conversion functions enhance ease of use and team collaboration efficiency, providing users with an efficient, secure, and convenient file management and collaboration experience.

[0037] The above description is merely a preferred embodiment of the present invention. It should be understood that the present invention is not limited to the forms disclosed herein and should not be construed as excluding other embodiments. It can be used in various other combinations, modifications, and environments, and can be altered within the scope of the concept described herein through the above teachings or related technologies or knowledge. Modifications and variations made by those skilled in the art that do not depart from the spirit and scope of the present invention should be within the protection scope of the appended claims.

Claims

1. A system for integrating DingTalk with cloud documents to achieve document sharing and notifications, characterized in that, It includes an API gateway module, a user information management module, a cloud document and data sharing module, and a permission management and recognition module; The API gateway module is used to connect and communicate data between the user's chat software and multiple cloud document platforms. The user information management module is used to manage user data information and match user data information with cloud documents that need to be edited and viewed; The cloud document and data sharing module is used to manage and store cloud documents. It automatically uploads and stores cloud documents after the user edits them, and supports online editing by the user. The permission management and identification module is used to allocate and manage permissions based on user data information, and automatically verify permissions after the user logs in.

2. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 1, characterized in that, The API gateway module is equipped with an F5 load balancer in the backend, which is used to distribute user-uploaded files to multiple backend service instances.

3. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 1, characterized in that, The cloud document platforms specifically include: Google Docs, Microsoft Office Online, and WPS Cloud Documents.

4. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 1, characterized in that, The user data information managed in the user information management module specifically includes: username, unique identifier ID, chat history, password, and document modification history.

5. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 1, characterized in that, The cloud document and data sharing module specifically includes the following sub-modules: document storage sub-module, document preview and editing sub-module, data encryption sub-module, data sharing sub-module, and format conversion sub-module; The document storage submodule is used to store user-uploaded documents and automatically upload and record each modification made by the user to the document content. It stores files and cloud documents in the cloud and supports file archiving, backup and classification management. The document preview and editing submodule is used to directly view, edit, and annotate user-uploaded documents, and supports multiple users to view, edit, and annotate documents simultaneously. The data encryption submodule is used to encrypt the edited document content and the data content to be shared; it is configured with a sandbox environment to isolate and execute suspicious files. The data sharing submodule is used to generate a shared link or shared QR code for the document to be edited, and send it to the corresponding user's chat software through the API gateway module; The format conversion submodule is used to convert the format of opened / edited or already edited documents.

6. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 5, characterized in that, The document types that the cloud document and data sharing module supports viewing, editing, and annotation include: Word, Excel, PPT, PDF, and images.

7. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 5, characterized in that, The document preview and editing submodule is configured to: open the file in the built-in editor of the chat application in response to the user's click operation on the file in the chat window; and automatically save the edited file to the cloud after detecting the editing completion event.

8. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 5, characterized in that, The format conversion submodule supports format conversions including PDF to image and Word to HTML. The conversion process is executed on a cloud server, and the converted files are pushed to the client in a browser-compatible format.

9. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 5, characterized in that, It also includes a log recording module and a message queue module; the log recording module is used to record and store each user operation, and when the document is converted into a format, it stores the file information and the converted information into a MySQL database; The message queue module is used to send conversion status information to the message queue after the file format conversion is completed, so that the client can consume it asynchronously.

10. The system for solving the problem of document sharing and notification by integrating DingTalk with cloud documents according to claim 1, characterized in that, The system's workflow includes: Users log into the chat software and connect and communicate with the cloud document platform via the API gateway module. Another user uploaded a document file that needed to be edited to the cloud document platform via a chat application; The system automatically identifies and detects whether the user has the permission to view and edit the document based on the user's current permissions. When the system detects that the user has the relevant permissions, the system pushes the document file to the user's chat window for viewing and editing. Specifically, the system automatically detects whether a user has the permission to view or edit the document based on their current permissions. This means that the system automatically detects whether the user has permission to edit the entire document or permission to edit part of the document. If the user only has permission to edit part of the document, the system automatically locks the editing permission for the non-permitted content, allowing only viewing.