Digital cooperative office method and system based on modular deployment and storage medium

Abstract

The invention relates to the technical field of office automation, and discloses a digital cooperative office method and system based on modular deployment and a storage medium, and the method comprises the steps: configuring a modular deployment strategy for an organization unit through an authority center, so as to define an available function module and manage an access authority; presenting a corresponding operation interface to the user terminal according to the strategy; when a user initiates cooperative operation related to office documents, calling a document management service to process all document requests in a centralized manner; and meanwhile, a service event is monitored through an event driving engine, and the event is automatically distributed to other functional modules for response and processing according to a predefined process arrangement rule, so that cross-module collaboration is realized. The system and the storage medium both correspond to the method. According to the method, the problems of system function stiffness, data isolation and flow splitting are solved, flexible configuration, unified management and automatic driving are realized, and the efficiency and the intelligent level of collaborative office are improved.

Description

Technical Field

[0001] This application relates to the field of office automation technology, specifically a digital collaborative office method, system, and storage medium based on modular deployment. Background Technology

[0002] As enterprises deepen their digital transformation, collaborative office systems have become a core platform supporting daily operations.

[0003] Currently, most common collaborative office systems adopt either an integrated or loosely integrated architecture. Integrated architecture systems have fixed functions, making it difficult to flexibly configure and tailor them to the individual needs of different departments within an enterprise (such as human resources, finance, and project management), resulting in system bloat or functional deficiencies. On the other hand, loosely integrated solutions using multiple independent systems generally suffer from data and process fragmentation: documents and data generated by different business modules are difficult to share, forming data silos; cross-departmental workflows cannot be automatically connected, heavily relying on manual offline coordination and transfer, leading to low collaboration efficiency, delayed information transmission, and a high risk of errors. Furthermore, existing systems typically require complex secondary development to cope with organizational restructuring or business scenario expansion, posing challenges to system scalability, adaptability, and operational costs.

[0004] Therefore, how to build an office platform that can flexibly adapt to diverse business units and achieve deep integration and automatic collaboration of data and processes is a technical problem that urgently needs to be solved in this field. Summary of the Invention

[0005] The purpose of this application is to provide a digital collaborative office method, system, and storage medium based on modular deployment to solve the technical problems mentioned in the background.

[0006] To achieve the above objectives, this application discloses the following technical solutions: Firstly, this application discloses a digital collaborative office method based on modular deployment, the method comprising: The collaborative office platform deployed on the server responds to the administrator's configuration instructions and configures a modular deployment strategy for at least one organizational unit in the permission center of the collaborative office platform; wherein, the modular deployment strategy defines one or more functional modules that the organizational unit can enable, and each functional module corresponds to a collaborative office business scenario; According to the modular deployment strategy, the collaborative office platform presents the operation interface corresponding to the enabled functional module to the user terminal under the organizational unit, and manages the user's access permissions to the resources within the functional module based on the permission center. When a user initiates a collaborative operation involving office documents through the operation interface, the collaborative office platform calls the document management service to centrally process document processing requests from all functional modules and perform full lifecycle management of the office documents; wherein, the collaborative operation includes editing, sharing or approving the same office document through at least two different types of terminals; The collaborative office platform listens for business events triggered by the collaborative operation through an event-driven engine, and distributes the business events to one or more other functional modules for automated response and processing according to predefined process orchestration rules, so as to achieve cross-functional module collaboration.

[0007] Optionally, configuring a modular deployment strategy for at least one organizational unit includes: The collaborative office platform provides a module configuration interface in the permission center. The module configuration interface displays a list of multiple selectable functional modules, which include at least a document management module, a meeting management module, and a project management module. The collaborative office platform receives the selection operation on the module configuration interface and binds the selected functional module to the specified organizational unit. The collaborative office platform dynamically assigns corresponding data access and operation permissions to users within the organizational unit based on the bound functional modules.

[0008] Optionally, the invocation of the document management service to centrally process document processing requests from all functional modules and perform full lifecycle management of the office documents includes: The collaborative office platform receives document processing requests from the document management module, the meeting management module, or the project management module through the document management service. The document management service standardizes the storage of office documents and generates unique document identifiers and global access links for each office document. The document management service records all collaborative operation logs surrounding the office document and controls the version of the office document based on the document identifier.

[0009] Optionally, the step of invoking the document management service to centrally process document processing requests from all functional modules and perform full lifecycle management of the office documents further includes: When presenting the office document to the user terminal, the document management service dynamically generates and overlays an invisible watermark associated with the user's identity based on the user identity information and document attributes issued by the permission center. The document management service performs real-time permission verification on document access requests initiated through the global access link. Access to the document content is only permitted if the requester's permissions match the policy defined in the permission center.

[0010] Optionally, the document management service is also used to enable cross-platform collaboration, including: Configure the collaborative office platform with a bidirectional connection channel to at least one third-party office application platform; When a user initiates an operation on the office document through the third-party office application platform, the collaborative office platform converts the operation command into a standard collaborative operation command within the collaborative office platform through the two-way connection channel, and forwards it to the document management service for execution.

[0011] Optionally, the step of listening to the business events triggered by the collaborative operation through the event-driven engine includes: The collaborative office platform defines a standardized event format, which includes event type, event source module identifier, triggering user identity, associated document identifier, and event payload data. When a predefined business action occurs in any functional module within the collaborative office platform, the functional module generates a business event conforming to the standardized format and publishes the business event to the event-driven engine.

[0012] Optionally, the step of distributing the business event to one or more corresponding functional modules for automated response and processing according to predefined process orchestration rules includes: The collaborative office platform provides a workflow orchestration and configuration interface, allowing administrators to visually define rules. The rules predefine specified event types and response actions. When a business event belonging to the specified event type is detected, processing instructions are automatically sent to one or more target functional modules or a pending task is created. The event-driven engine matches the received business events with the rules. Upon successful matching, it automatically invokes the application programming interface provided by the target functional module or submits task data to the message queue of the target functional module.

[0013] Optionally, the collaborative office platform, permission center, document management service, and event-driven engine are deployed in a hybrid cloud architecture, wherein: The metadata of the permission center, the modular deployment strategy, and the process orchestration rules are deployed in a private cloud environment. The document management service, which handles non-sensitive office document content and high-concurrency collaborative operation requests for user terminals, is deployed in a public cloud environment and synchronizes data with the private cloud environment via an encrypted link.

[0014] Secondly, this application discloses a modularly deployed digital collaborative office system, applying the modularly deployed digital collaborative office method described above. The system includes: The permission center, deployed on the server, is used to respond to the administrator's configuration instructions and configure a modular deployment strategy for at least one organizational unit; wherein, the modular deployment strategy defines one or more functional modules that the organizational unit can enable, and each functional module corresponds to a collaborative office business scenario; Multiple functional modules are communicatively connected to the permission center, and are used to present an operation interface to the corresponding user terminal according to the modular deployment strategy, and respond to business operations initiated by the user through the operation interface based on the access permissions managed by the permission center; wherein, the business operations include collaborative operations involving office documents; The document management service module is used to centrally receive and process document processing requests from all functional modules, and to manage the office documents throughout their entire lifecycle. The event-driven engine is used to listen for business events triggered by the collaborative operation, and distribute the business events to one or more other functional modules for automated response and processing according to predefined process orchestration rules, so as to realize cross-functional module collaboration.

[0015] Thirdly, this application discloses a computer-readable storage medium storing a computer program that can be executed by a processor. When the computer program is executed by the processor, it implements the modularly deployed digital collaborative office method described above.

[0016] Beneficial effects: The modular deployment-based digital collaborative office method, system, and storage medium of this application achieve flexible matching between system functions and organizational structure through a modular deployment strategy, improving the system's configurability and adaptability; through a unified document management service, it breaks down data barriers between various business modules, ensuring consistent management and seamless flow of office documents across the entire platform; through an event-driven engine and predefined rules, it enables automated triggering and execution of business processes across functional modules, transforming previously manual cross-departmental collaboration into efficient and accurate automated system collaboration, thereby improving the overall operational efficiency, management refinement, and digital collaboration capabilities of enterprises. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a modularly deployed digital collaborative office method provided in this application embodiment; Figure 2 This is a structural block diagram of a modularly deployed digital collaborative office system provided in an embodiment of this application. Detailed Implementation

[0019] To facilitate understanding of the technical solutions provided in the embodiments of this application, the background technology involved in the embodiments of this application will be described below.

[0020] In modern enterprise operations, digital collaborative office systems play a crucial role, aiming to integrate various resources, optimize business processes, and improve organizational efficiency. In practice, the choice of technical architecture for such systems directly impacts their effectiveness and adaptability. Currently, mainstream solutions can be broadly categorized into two types, but both have inherent limitations.

[0021] The first type is the monolithic architecture system, which is integrated and fully functional. This type of system pre-packages numerous functions such as document processing, meeting management, project management, and human resource management into a large, tightly coupled software system. While its internal data consistency is high, its biggest problem lies in its severe lack of flexibility. Different departments within an enterprise (e.g., R&D departments versus administrative and logistical departments) have significantly different business priorities and process requirements. Faced with this diversity, integrated systems often have to provide all functions in a "one-size-fits-all" manner, leading to irrelevant functions interfering with certain departments, resulting in a complex system interface and cumbersome operation—the so-called "system bloat." Conversely, if the system does not include specific functions required by a particular department, it results in "functional gaps." Under this architecture, enterprises find it difficult to perform refined and differentiated function configuration and tailoring according to their own organizational characteristics and development stage, thus significantly reducing user experience and actual management efficiency.

[0022] The second approach involves loosely integrating multiple independent, business-specific systems. For example, a company might deploy separate document management systems, customer relationship management systems, and project task systems. While this approach satisfies the specialized functional requirements to some extent, it introduces more intractable problems of "data silos" and "process fragmentation." Each system typically has its own independent database, user structure, and operational logic, leading to inconsistent data formats and interface standards. A design document generated in a project system cannot be directly referenced or linked in an administrative department's meeting management system; important information requires repeated manual downloading, uploading, and format conversion, which is not only inefficient but also prone to version inconsistencies. More importantly, cross-departmental business processes are artificially fragmented. For instance, a complete process from project initiation to procurement approval and contract archiving, involving different systems, cannot form an automated workflow and heavily relies on employees manually identifying, forwarding, and following up through offline communication (such as email and instant messaging). This model results in low collaboration efficiency, excessively long and error-prone information transmission chains, and poor process transparency and controllability.

[0023] Furthermore, regardless of the architecture mentioned above, all exhibit poor adaptability when facing adjustments to the enterprise's organizational structure (such as departmental splitting and merging), expansion of business scope, or the emergence of new business scenarios. For integrated systems, any addition, removal, or modification of functions can have far-reaching consequences, requiring complex and expensive customized secondary development, which is time-consuming and risky. For multi-system integration solutions, this means developing new and more complex inter-system interfaces, leading to an exponential increase in integration and maintenance costs. Therefore, system scalability, adaptability, and long-term operational costs have become significant challenges for enterprises' continued digital transformation.

[0024] Based on this, the embodiments of this application construct an intelligent, efficient and sustainably evolving digital collaborative office platform.

[0025] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application. Secondly, in this document, the term "comprising" is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements, but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus.

[0026] Firstly, this embodiment provides a digital collaborative office method based on modular deployment, such as... Figure 1 As shown, the method includes the following steps in sequence: S1 - The collaborative office platform deployed on the server responds to the administrator's configuration instructions and configures a modular deployment strategy for at least one organizational unit in the permission center of the collaborative office platform; wherein, the modular deployment strategy defines one or more functional modules that the organizational unit can enable, and each functional module corresponds to a collaborative office business scenario.

[0027] Based on a modular deployment strategy, the S2-Collaborative Office Platform presents the operation interface corresponding to the enabled functional modules to user terminals under the organizational unit, and manages user access permissions to resources within the functional modules based on the permission center.

[0028] S3 - When a user initiates a collaborative operation involving office documents through the user interface, the collaborative office platform calls the document management service to centrally process document processing requests from all functional modules and manage office documents throughout their entire lifecycle. The collaborative operation includes editing, sharing, or approving the same office document through at least two different types of terminals.

[0029] The S4-Collaborative Office Platform uses an event-driven engine to listen for business events triggered by collaborative operations. Based on predefined process orchestration rules, it distributes these business events to one or more other functional modules for automated response and processing, thereby achieving cross-functional module collaboration.

[0030] In practice, this method is executed by a collaborative office platform deployed on a server cluster. Organizational units can be logical entities within an enterprise, such as branch offices, departments, or project teams. The permission center is the core component built on role-based access control (RBAC), responsible for the storage, management, and adjudication of all policies and permissions. The modular deployment strategy defines the mapping relationship between organizational units and functional modules. This strategy can be stored using a data structure, for example, a possible pseudocode is: { "org_unit_id":"dept_001", "enabled_modules":["module_doc","module_meeting","module_project"], "policy_version":"v1.0" } Each identifier in the `enabled_modules` list corresponds to an independently deployed, dynamically loadable functional module microservice, such as a document management microservice or a meeting management microservice. When a user accesses the platform via a browser (desktop) or a mobile application (phone), the platform gateway queries this policy based on the user's organizational unit and loads and displays only the corresponding functional module interface.

[0031] In addition, the document management service is a standalone middleware built with a microservice architecture, providing unified document storage, retrieval, and processing capabilities across the entire platform. It receives document requests from all functional modules through a defined RESTful API, ensuring a single entry point and consistency for document data. The "event-driven engine" is a message middleware (such as Apache Kafka or RabbitMQ) based on a publish-subscribe pattern, responsible for event collection, routing, and distribution.

[0032] Based on the above, this embodiment changes the architecture of traditional integrated or loosely integrated systems through a modular deployment strategy with unified configuration in the permission center, achieving flexible matching of functional modules with organizational needs. Administrators can enable different functions for different departments like building blocks, realizing on-demand system tailoring and solving the problems of system bloat or missing functions. By building an independent document management service as the sole hub for all document processing, the platform forces all document data generated by business modules to converge and standardize here, breaking down data silos and laying the data foundation for cross-module document flow. Furthermore, through an event-driven engine and process orchestration rules, user operations within a module (such as finalizing meeting minutes) are automatically transformed into a standardized business event, which can automatically trigger subsequent actions in other modules (such as creating to-do tasks in the project management module). This mechanism transforms cross-departmental collaboration processes that previously relied on manual communication and transmission into digital processes that are automatically driven and precisely executed by the system, achieving deep integration and automatic collaboration of data and processes, and improving organizational operational efficiency and response speed.

[0033] As an optional implementation of this embodiment, a modular deployment strategy is configured for at least one organizational unit, including: The collaborative office platform provides a module configuration interface in the permission center. The module configuration interface displays a list of multiple functional modules to choose from. The functional modules include at least the document management module, the meeting management module, and the project management module. The collaborative office platform receives selections from the module configuration interface and binds the selected functional modules to the specified organizational units; The collaborative office platform dynamically assigns corresponding data access and operation permissions to users within an organizational unit based on the bound functional modules.

[0034] In practice, the module configuration interface is a web-based management backend developed using front-end frameworks such as Vue.js or React. It dynamically retrieves a list of available functional modules by calling the API of the permission center. Each module item in the list includes a module name, identifier, version, and functional description. When an administrator selects modules and clicks "Bind," the front-end sends the organizational unit ID and the list of selected module identifiers to the back-end. The back-end service first updates the modular deployment strategy storage record (e.g., updating the `enabled_modules` field in the pseudocode above), and then triggers the permission synchronization process. Dynamic permission assignment means that the permission center maintains a role-module-permission mapping matrix. After the binding operation is completed, the system automatically associates the default user role under the organizational unit (e.g., "department employee") with the basic permission set associated with the newly added module (e.g., the "View Meetings" and "Apply for Meeting Rooms" permissions for the "Meeting Management Module"), and this takes effect in real time without requiring manual configuration.

[0035] Based on the above, this embodiment simplifies complex system customization and permission management through a visual configuration interface and an automated permission granting mechanism. Administrators can flexibly combine and deploy functional modules without technical background, achieving low-code configuration of enterprise-level software, reducing the difficulty and cost of system management, and ensuring the timeliness and accuracy of permission configuration, thus supporting the system's flexibility and security from a management perspective.

[0036] Building upon the aforementioned modular deployment strategy, as a further optional implementation method in this embodiment, a document management service is invoked to centrally process document processing requests from all functional modules, enabling full lifecycle management of office documents, including: The collaborative office platform receives document processing requests from the document management module, meeting management module, or project management module through document management services; The document management service standardizes the storage of office documents and generates unique document identifiers and global access links for each document. The document management service records all collaborative operation logs surrounding office documents and controls the versions of office documents based on document identifiers.

[0037] In practice, each functional module submits documents by calling the unified upload API of the document management service (e.g., POST / api / v1 / documents). Upon receiving the document stream and metadata (e.g., uploader, source module, original filename), the service performs standardized processing: converting the documents to PDF / A format for archiving while retaining the original files. A unique document identifier is generated using a globally unique identifier (UUID) algorithm, in the format doc_9a8b7c6d5e4f3g2h. A global access link is built based on this identifier, in the form of https: / / doc-platform.com / access / doc_9a8b7c6d5e4f3g2h, which can be accessed by any user who possesses the link and passes authorization verification.

[0038] Secondly, version control employs a combination of linear incrementing and branch snapshots. Each document update (such as saving after editing) generates a new version number. The system saves complete document snapshots and maintains a lightweight version change log describing the differences between versions. To optimize storage and improve retrieval efficiency, the document management service employs a content-aware similar version merging algorithm. When creating a new version, this algorithm not only stores the file but also calculates the feature vector of the document content. If consecutive versions have extremely high semantic similarity, incremental storage is used on the backend, recording only the version number in the metadata, while the physical file points to the base version and the difference block, thus saving storage space. (Document feature vector) The calculation is based on a weighted combination of the document's TF-IDF vector and pre-trained word vectors: in, Representative document Effective vocabulary in It is the word Pre-trained vectors (such as vectors generated by Word2Vec or BERT). It is the word TF-IDF weights on the current document set. It is a vector encoded from document metadata (such as document type, size, and creator department). and The weighting coefficients are used to balance the influence of text content and metadata.

[0039] Two document versions and semantic similarity We obtain this by calculating the cosine similarity of their feature vectors: when Exceeding the preset threshold When the version is 0.95 (e.g., 0.95), the system triggers the logic to merge and store similar versions.

[0040] Based on the above, this embodiment constructs a platform-level unified document data layer through a unified API entry point, mandatory standardized storage, and UUID-based global identification, ensuring unique document sources, unique identifiers, and consistent storage formats. Furthermore, by implementing a content-aware similar version merging algorithm, it intelligently optimizes storage resource consumption while ensuring the complete traceability of version history. The combination of global access links and version control enables a document to be securely and accurately referenced and traced in different scenarios such as official documents, meetings, and projects, achieving manageable and collaborative document assets across the entire platform and providing robust data consistency guarantees for complex business processes.

[0041] Building upon the aforementioned document management service, as a further optional implementation of this embodiment, the document management service is invoked to centrally process document processing requests from all functional modules, enabling full lifecycle management of office documents. This further includes: When presenting office documents to user terminals, the document management service dynamically generates and overlays an invisible watermark associated with the user's identity based on the user's identity information and document attributes issued by the permission center. The document management service performs real-time permission verification on document access requests initiated through global access links. Access to document content is only permitted if the requester's permissions match the policies defined in the permission center.

[0042] In practical implementation, dynamic invisible watermarking technology is generated and applied in real time when the document is previewed or downloaded. The watermark information typically includes the current user's name, employee ID, and access timestamp. To enhance the robustness and invisibility of the watermark, this embodiment employs a hybrid domain adaptive watermark embedding algorithm based on Discrete Wavelet Transform (DWT) and Singular Value Decomposition (SVD). First, the document page image to be presented... Perform a 3-level discrete wavelet transform decomposition to obtain the low-frequency subband. And multiple high-frequency subbands. Select mid-frequency subbands with moderate texture complexity (such as the original image). The second-level horizontal high-frequency and vertical low-frequency subbands obtained by the second-level DWT decomposition Original image Two-level vertical high-frequency and horizontal low-frequency subbands obtained by two-level DWT decomposition Perform singular value decomposition: in, This represents the selected sub-band matrix. Sub-band matrix The left singular matrix, Sub-band matrix The singular value matrix, Sub-band matrix The right singular matrix, for The transpose of the watermark information W (encrypted and encoded user identity information, typically a binary / normalized numerical sequence (values ​​[0,1]) is adaptively embedded into the singular value matrix. Medium. And embedding strength It is not fixed, but dynamically adjusted based on the local features of the image patch: in, The basic embedding strength (preset baseline value) has an empirical range of [0.001, 0.01], which can be adjusted according to the image resolution; This is the edge density adjustment factor, a negative constant (values ​​[-0.5, -0.1]), used to weaken the embedding strength of edge regions; Sub-band matrix The edge density of the corresponding image patch is calculated using Canny edge detection and takes values ​​[0,1] (0 represents no edge, 1 represents full edge). Weaker embedding is used in densely edged regions to maintain visual quality, while stronger embedding is used in smooth regions to improve robustness. The embedding formula is: in, The singular value matrix updated after embedding the watermark is modified only on the diagonal singular values; the off-diagonal elements remain 0. Then, using... , And the revised Perform inverse SVD transformation ( The image containing the hidden watermark is obtained by performing a DWT inverse transform. .

[0043] In addition, the permission verification process is performed at the document access gateway. When a user clicks the global access link, the gateway intercepts the request, extracts the identity token (such as JWT) and document identifier from the request, and initiates a real-time authentication query to the permission center. The permission center makes a decision based on the user's role, organizational unit, and document access control list (ACL), and returns the result (allow / deny) and user identity information to the document management service for dynamically generating watermarks or directly denying access.

[0044] Based on the above, this embodiment deeply integrates fine-grained security control capabilities on the basis of unified document management. Dynamic invisible watermarking technology, without excessively affecting the visual experience, imprints a traceable user mark on each distributed document, forming a powerful deterrent and post-event traceability capability, effectively preventing the leakage of sensitive information through screenshots, photos, etc. A real-time permission verification mechanism ensures that global access links are not the same as public access links; each access must be authorized in real time by the central permission center, achieving a balance between convenient sharing and strict control, and enhancing the security level of enterprise digital assets.

[0045] Based on the aforementioned document management service, as a further optional implementation method of this embodiment, the document management service is also used to achieve cross-platform collaboration, including: Configure a two-way connection channel between the collaborative office platform and at least one third-party office application platform; When a user initiates an operation on an office document through a third-party office application platform, the collaborative office platform converts the operation instruction into a standard collaborative operation instruction within the collaborative office platform through a two-way connection channel, and then forwards it to the document management service for execution.

[0046] In practical implementation, third-party office application platforms include, but are not limited to, mainstream platforms such as WeChat Work, DingTalk, Lark, or Microsoft Teams. A two-way connection channel is typically established through the following methods: 1) Registering the application as a self-built application on the third-party platform to obtain API call credentials (such as corporate secret); 2) Configuring the credentials and callback address (Webhook URL) in this invention's platform; 3) Implementing the message encryption / decryption and signature verification protocols required by the third-party platform. After the channel is established, this platform deploys a protocol converter microservice.

[0047] When a user clicks the "Approve" button on a message containing a link to a document from this invention platform within WeChat Work, WeChat Work pushes this "click to approve event" to the configured Webhook URL. Upon receiving the event, the protocol converter first parses out the event type (approval_action), the operator's user ID (within the WeChat Work ecosystem), and the document link. Then, it performs two crucial conversion steps: First, through the bound user mapping relationship, it converts the third-party user ID into a unified user identifier within the platform; second, according to a predefined instruction mapping rule base, it maps the "WeChat Work approval action" into a "standard collaborative operation instruction" that the platform's internal document management service can understand. The data structure is: {"action":"approve_document", "document_id": "doc_xxx", "operator": "user_yyy", "comment": "..."}. Finally, the protocol converter, using this unified user identity, initiates the corresponding API call to the document management service.

[0048] Based on the above, this embodiment breaks down the barriers between this platform and mainstream external office ecosystems, enhancing collaborative capabilities. Users can perform secure and controllable operations on the platform's core document assets within a familiar third-party platform environment without switching applications. This not only improves user experience and ease of use but also extends the platform's document collaboration capabilities to a wider range of business touchpoints, forming a collaborative network centered on unified documents and extending to multiple platform front-ends, further consolidating and expanding the platform's value as an enterprise collaboration hub.

[0049] As an optional implementation of this embodiment, the event-driven engine listens for business events triggered by collaborative operations, including: The collaborative office platform defines a standardized event format, which includes event type, event source module identifier, triggering user identity, associated document identifier, and event payload data; When a predefined business action occurs in any functional module within the collaborative office platform, the functional module generates a business event that conforms to a standardized format and publishes the business event to the event-driven engine.

[0050] In practice, the standardized event format is defined and validated using JSON Schema. An example of pseudocode is as follows: { "event_id": "evt_202310271200001", "event_type": "DOCUMENT_FINALIZED", "source_module": "module_doc", "trigger_user": "user_123", "timestamp": "2023-10-27T12:00:00Z", "related_document_id": "doc_9a8b7c6d5e4f3g2h", “payload”: { “document_title”: “Q3 Project Retrospective Report” "final_version": "v3.0" } } Here, `event_type` is an enumeration value, such as `DOCUMENT_FINALIZED` (document finalized), `MEETING_COMPLETED` (meeting ended), `TASK_OVERDUE` (task timed out), etc. Each functional module predefines which business actions (such as "clicking the finalized button" or "marking the meeting status as completed") will trigger the corresponding event. When these actions occur, the module's business code calls a lightweight "event publishing client SDK" to construct the event message in the above format and send it to the specified Topic in the event-driven engine (such as Kafka).

[0051] Based on the above, this embodiment defines a unified and structured business event standard across the entire platform, transforming business-meaning state changes occurring within each functional module into standardized messages that the platform can recognize and circulate. This establishes a unified language mechanism for communication between modules that were originally discrete and closed, and is a key technological foundation for achieving a loosely coupled, highly cohesive microservice architecture and subsequent automated process orchestration.

[0052] Building upon the aforementioned event-driven engine listening, as a further optional implementation of this embodiment, business events are distributed to one or more corresponding functional modules for automated response and processing according to predefined process orchestration rules, including: The collaborative office platform provides a workflow orchestration and configuration interface, allowing administrators to visually define rules. The rules predefine specified event types and response actions. When a business event belonging to the specified event type is detected, the platform automatically sends processing instructions to one or more target functional modules or creates a pending task. The event-driven engine matches the received business events with the rules. If a match is successful, it automatically calls the application programming interface provided by the target functional module or sends task data to the message queue of the target functional module.

[0053] In practical implementation, the process orchestration configuration interface provides a drag-and-drop canvas, allowing administrators to draw logical flowcharts such as "when [Event A] occurs, execute [Action X] and [Action Y]". These rules are persisted as rule description files. On the event-driven engine side, a "rule engine" component (such as Drools or a self-developed state machine engine) continuously consumes the event stream. When a new event is detected, the rule engine matches its event_type with the triggering conditions of all rules. If a match is successful, the engine executes the response action defined in the rule. For example, an exemplary rule might be defined as: ON EVENT(DOCUMENT_FINALIZED) WHERE source_module='module_doc' DO CREATE_TASK('module_project', 'review_document', $event.related_document_id, $event.trigger_user). When this action is executed, the rule engine calls a specific API of the project management module (module_project) or inserts a task data entry into the task queue of the project management module, containing information such as the document ID and the user to be reviewed. The task data format is also standardized.

[0054] Based on the above, this embodiment liberates cross-module business logic from hard-coding, transforming it into configurable and manageable processes. Administrators can define complex automated workflows (such as "automatically creating review tasks and notifying project members after document finalization") without developing code, achieving agile and intelligent business responses. This reduces process breakpoints caused by manual handover, forgetfulness, or delays, ensuring smooth and automated execution of cross-departmental business processes, and is a core automation method for improving overall operational efficiency.

[0055] As an optional implementation method in this embodiment, the collaborative office platform, permission center, document management service, and event-driven engine are deployed in a hybrid cloud architecture, wherein: The metadata, modular deployment strategies, and process orchestration rules of the permission center are deployed in a private cloud environment. The document management service handles non-sensitive office document content and high-concurrency collaborative operation requests for user terminals. It is deployed in a public cloud environment and synchronizes data with a private cloud environment through an encrypted link.

[0056] In practical implementation, the hybrid cloud architecture divides system components according to data sensitivity and computing needs. The permission center and databases storing core policies and rules are deployed in the enterprise's private cloud (or on-premises data center) to ensure the highest level of data sovereignty and security isolation. In document management services, compute-intensive and I / O-intensive business components involving document content storage (object storage), format conversion, and large-scale concurrent preview / download are deployed in public clouds (such as Alibaba Cloud and AWS) to leverage their elastic scaling and CDN capabilities to handle access surges. The event-driven engine's broker nodes can also be deployed in the public cloud to achieve high-throughput message processing capabilities.

[0057] An encrypted communication tunnel is established between the two environments via an IPSec VPN or dedicated line. Data synchronization is bidirectional: 1) The private cloud synchronizes the permission decision results, user identity information, etc., to the relevant services of the public cloud in real time; 2) The public cloud asynchronously transmits the document access logs, operation logs, etc., back to the audit database of the private cloud.

[0058] To ensure consistency and reliability of synchronization, this embodiment employs an eventual consistency synchronization protocol based on vector clocks. Each critical data object (such as a permission policy) is associated with a vector clock stamp. This is used to resolve potential update conflicts during cross-cloud synchronization, ensuring the correct evolution of data state across all endpoints. This indicates the identifier of the node participating in cross-cloud synchronization (such as the service node ID of a private cloud / public cloud). Indicates the corresponding node The update count for the current data object is incremented by 1 each time the node updates the data, reflecting the version evolution of the data at that node.

[0059] Based on the above, this embodiment achieves an optimal balance between security and performance through a hybrid cloud deployment architecture. It firmly controls the enterprise's most core and sensitive permission and policy data in a private environment, meeting stringent compliance requirements; while placing the computationally demanding and traffic-fluctuating document processing and service access layers in an elastic public cloud, reducing IT infrastructure costs and achieving excellent system scalability and user experience. This architectural design allows the solution to flexibly adapt to the complex IT environments of enterprises of different sizes and with varying compliance requirements, possessing broad applicability and strong implementation capabilities.

[0060] Secondly, this embodiment provides a modularly deployed digital collaborative office system, applying the modularly deployed digital collaborative office method described above, such as... Figure 2 As shown, the system includes: The permission center, deployed on the server, is used to respond to the administrator's configuration instructions and configure a modular deployment strategy for at least one organizational unit. The modular deployment strategy defines one or more functional modules that can be enabled by the organizational unit, and each functional module corresponds to a collaborative office business scenario. Multiple functional modules communicate with the permission center to present an operation interface to the corresponding user terminal according to the modular deployment strategy, and respond to business operations initiated by users through the operation interface based on the access permissions managed by the permission center; among them, business operations include collaborative operations involving office documents; The document management service module is used to centrally receive and process document processing requests from all functional modules, and to manage office documents throughout their entire lifecycle. The event-driven engine listens for business events triggered by collaborative operations and distributes them to one or more other functional modules for automated response and processing according to predefined process orchestration rules, thereby achieving cross-functional module collaboration.

[0061] Thirdly, this embodiment provides a computer-readable storage medium storing a computer program that can be executed by a processor. When the computer program is executed by the processor, the modular deployment-based digital collaborative office method described above is implemented.

[0062] It should be noted that the modularly deployed digital collaborative office system and storage medium of this embodiment correspond to the aforementioned modularly deployed digital collaborative office method. Therefore, the parts of the modularly deployed digital collaborative office system and storage medium that are not described in detail (including but not limited to specific technical means and technical effects) can be referred to the relevant descriptions in the aforementioned modularly deployed digital collaborative office method, and will not be repeated here.

[0063] In the embodiments provided in this application, it should be understood that the embodiments described herein can be implemented in hardware, software, firmware, middleware, code, or any suitable combination thereof. For hardware implementation, the processor may be implemented in one or more of the following: application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to implement the functions described herein, or combinations thereof. For software implementation, some or all of the processes of the embodiments may be performed by a computer program instructing the associated hardware. During implementation, the program may be stored in a computer-readable storage medium or transmitted as one or more instructions or code on a computer-readable storage medium. Computer-readable storage media include computer storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media may be any available medium accessible to a computer. Computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code having the form of instructions or data structures and accessible to a computer.

[0064] Finally, it should be noted that the above description is only a preferred embodiment of this application and is not intended to limit this application. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A digital collaborative office method based on modular deployment, characterized in that, The method includes: The collaborative office platform deployed on the server responds to the administrator's configuration instructions and configures a modular deployment strategy for at least one organizational unit in the permission center of the collaborative office platform; wherein, the modular deployment strategy defines one or more functional modules that the organizational unit can enable, and each functional module corresponds to a collaborative office business scenario; According to the modular deployment strategy, the collaborative office platform presents the operation interface corresponding to the enabled functional module to the user terminal under the organizational unit, and manages the user's access permissions to the resources within the functional module based on the permission center. When a user initiates a collaborative operation involving office documents through the operation interface, the collaborative office platform calls the document management service to centrally process document processing requests from all functional modules and perform full lifecycle management of the office documents; wherein, the collaborative operation includes editing, sharing or approving the same office document through at least two different types of terminals; The collaborative office platform listens for business events triggered by the collaborative operation through an event-driven engine, and distributes the business events to one or more other functional modules for automated response and processing according to predefined process orchestration rules, so as to achieve cross-functional module collaboration.

2. The modular deployment-based digital collaborative office method according to claim 1, characterized in that, Configuring a modular deployment strategy for at least one organizational unit includes: The collaborative office platform provides a module configuration interface in the permission center. The module configuration interface displays a list of multiple selectable functional modules, which include at least a document management module, a meeting management module, and a project management module. The collaborative office platform receives the selection operation on the module configuration interface and binds the selected functional module to the specified organizational unit. The collaborative office platform dynamically assigns corresponding data access and operation permissions to users within the organizational unit based on the bound functional modules.

3. The modular deployment-based digital collaborative office method according to claim 2, characterized in that, The aforementioned invocation of the document management service is used to centrally process document processing requests from all functional modules and to perform full lifecycle management of the office documents, including: The collaborative office platform receives document processing requests from the document management module, the meeting management module, or the project management module through the document management service. The document management service standardizes the storage of office documents and generates unique document identifiers and global access links for each office document. The document management service records all collaborative operation logs surrounding the office document and controls the version of the office document based on the document identifier.

4. The modular deployment-based digital collaborative office method according to claim 3, characterized in that, The invocation of the document management service to centrally process document processing requests from all functional modules and to perform full lifecycle management of the office documents also includes: When presenting the office document to the user terminal, the document management service dynamically generates and overlays an invisible watermark associated with the user's identity based on the user identity information and document attributes issued by the permission center. The document management service performs real-time permission verification on document access requests initiated through the global access link. Access to the document content is only permitted if the requester's permissions match the policy defined in the permission center.

5. The modular deployment-based digital collaborative office method according to claim 3, characterized in that, The document management service is also used to enable cross-platform collaboration, including: Configure the collaborative office platform with a bidirectional connection channel to at least one third-party office application platform; When a user initiates an operation on the office document through the third-party office application platform, the collaborative office platform converts the operation command into a standard collaborative operation command within the collaborative office platform through the two-way connection channel, and forwards it to the document management service for execution.

6. The digital collaborative office method based on modular deployment according to claim 1, characterized in that, The process of listening to business events triggered by the collaborative operation through an event-driven engine includes: The collaborative office platform defines a standardized event format, which includes event type, event source module identifier, triggering user identity, associated document identifier, and event payload data. When a predefined business action occurs in any functional module within the collaborative office platform, the functional module generates a business event conforming to the standardized format and publishes the business event to the event-driven engine.

7. The digital collaborative office method based on modular deployment according to claim 6, characterized in that, The step of distributing the business events to one or more corresponding functional modules for automated response and processing according to predefined process orchestration rules includes: The collaborative office platform provides a workflow orchestration and configuration interface, allowing administrators to visually define rules. The rules predefine specified event types and response actions. When a business event belonging to the specified event type is detected, processing instructions are automatically sent to one or more target functional modules or a pending task is created. The event-driven engine matches the received business events with the rules. If a match is successful, it automatically calls the application programming interface provided by the target functional module or sends task data to the message queue of the target functional module.

8. The digital collaborative office method based on modular deployment according to claim 1, characterized in that, The collaborative office platform, permission center, document management service, and event-driven engine are deployed in a hybrid cloud architecture, wherein: The metadata of the permission center, the modular deployment strategy, and the process orchestration rules are deployed in a private cloud environment. The document management service, which handles non-sensitive office document content and high-concurrency collaborative operation requests for user terminals, is deployed in a public cloud environment and synchronizes data with the private cloud environment via an encrypted link.

9. A modularly deployed digital collaborative office system, employing the modularly deployed digital collaborative office method as described in any one of claims 1-8, characterized in that, The system includes: The permission center, deployed on the server, is used to respond to the administrator's configuration instructions and configure a modular deployment strategy for at least one organizational unit; wherein, the modular deployment strategy defines one or more functional modules that the organizational unit can enable, and each functional module corresponds to a collaborative office business scenario; Multiple functional modules are communicatively connected to the permission center, and are used to present an operation interface to the corresponding user terminal according to the modular deployment strategy, and respond to business operations initiated by the user through the operation interface based on the access permissions managed by the permission center; wherein, the business operations include collaborative operations involving office documents; The document management service module is used to centrally receive and process document processing requests from all functional modules, and to manage the office documents throughout their entire lifecycle. The event-driven engine is used to listen for business events triggered by the collaborative operation, and distribute the business events to one or more other functional modules for automated response and processing according to predefined process orchestration rules, so as to realize cross-functional module collaboration.

10. A computer-readable storage medium, characterized in that, It stores a computer program that can be executed by a processor, and when the computer program is executed by the processor, it implements the digital collaborative office method based on modular deployment as described in any one of claims 1-8.

Images