Cloud collaborative configuration method, device, equipment and medium

Abstract

The invention relates to the technical field of industrial automation, and provides a cloud collaborative configuration method, device and equipment and a medium, and the method comprises the steps: in response to a template selection instruction of a user, selecting a target function template corresponding to a target item from a preset function template library; according to a template combination rule, initial template combination is carried out, and combined template resources are loaded to a user working space; constructing a multi-user real-time cooperation channel, carrying out concurrency control and conflict resolution on configuration editing operations simultaneously initiated by multiple users aiming at the combined templates, synchronizing editing and modification of any user on the templates to user working spaces corresponding to all cooperation users in real time, and synchronously recording operation logs and project version information; and in response to a configuration editing completion instruction of the user, generating a configuration scheme file, performing testing, and storing the file into a preset database after the testing is passed. Through the technical scheme, the project delivery cycle is shortened, and the expandability and cross-scene adaptation capability of the system are improved.

Description

Technical Field

[0001] This application relates to the field of industrial automation technology, and in particular to a cloud-based collaborative configuration method, apparatus, equipment, and medium. Background Technology

[0002] In the field of industrial automation, configuration technology, as a core means of realizing digital control of production processes, is widely used in scenarios such as production line automation, equipment monitoring, and process optimization. However, the configuration process of traditional industrial automation systems still has many technical pain points, making it difficult to adapt to the current industrial digital transformation's demand for efficient, collaborative, and flexible configuration.

[0003] First, traditional configuration methods heavily rely on manual operation by professional engineers and lack standardized, universal template systems. Because the process requirements, equipment configurations, and control logic vary significantly across different industrial scenarios (such as chemical, automotive manufacturing, and energy production), engineers must design configuration processes and build functional modules from scratch for each project. This not only requires a significant investment of time in repetitive development (for example, similar basic configuration modules for equipment monitoring and parameter acquisition are often repeatedly built in different production line projects), but also easily leads to deviations in the format uniformity and functional completeness of configuration solutions due to the subjectivity of manual operation, significantly increasing labor costs and project risks.

[0004] Secondly, collaborative efficiency is low in multi-person scenarios due to the lack of version management and information synchronization mechanisms. Industrial automation configuration projects often require cross-disciplinary and cross-regional team members (such as process engineers, control engineers, and maintenance personnel). However, in the traditional model, team members rely heavily on local file transfers (such as email and instant messaging tools to share documents) for collaboration. This not only fails to achieve real-time synchronization of configuration editing operations but also easily leads to problems such as "multi-version file conflicts" and "difficulty in tracing operation records." For example, if a member's modified configuration parameters are not synchronized with other members in a timely manner, subsequent development will be based on the old version of the file, ultimately causing logical contradictions in the overall configuration solution. This requires additional time to investigate and correct, significantly extending the project delivery cycle and increasing project costs.

[0005] Furthermore, traditional local configuration methods lack flexibility and scalability, making it difficult to respond to rapidly changing market demands. With the advancement of Industry 4.0, industrial automation systems need to frequently adjust configuration schemes according to production needs (such as production line capacity upgrades and equipment replacement). However, in local configuration mode, configuration resources (such as templates and logic modules) are mostly stored on local devices, making it impossible to achieve resource reuse and rapid retrieval across projects and teams. Moreover, team members need to work on fixed equipment, limiting the spatial flexibility of collaboration and resulting in a lag in the response speed of configuration scheme adjustments, making it difficult to meet the high requirements of industrial production for configuration efficiency.

[0006] In summary, traditional industrial automation configuration technologies suffer from poor versatility, low collaboration efficiency, and insufficient flexibility, which have become key bottlenecks restricting the efficient advancement of industrial automation projects and hindering the process of industrial digital transformation. Summary of the Invention

[0007] This application provides a cloud-based collaborative configuration method, apparatus, device, and medium, aiming to solve many technical problems in related technologies, such as poor versatility, low collaboration efficiency, and insufficient flexibility.

[0008] In a first aspect, embodiments of this application provide a cloud-based collaborative configuration method, the method comprising: In response to the user's template selection command, select the target function template corresponding to the target project from the preset function template library; Based on the received template combination rules and the target function template, an initial template combination is performed, and the combined template resources are loaded into the user workspace. Construct a multi-user real-time collaboration channel to perform concurrent control and conflict resolution on configuration editing operations initiated simultaneously by multiple users on the combined template. Real-time synchronization of any user's edits to the combined template to the user workspaces of all collaborating users, and simultaneous recording of operation logs and project version information. In response to receiving a configuration editing completion instruction from the user, a configuration scheme file is generated based on the combined template and the configuration editing operation performed on the combined template; The configuration scheme file is tested, and after the test is passed, the configuration scheme file is stored in a preset database.

[0009] In one embodiment, optionally, the method further includes: Real-time monitoring of computing resource utilization, storage resource utilization, data transmission rate, and number of concurrent users during project configuration; When any of the following indicators exceeds a preset threshold: resource utilization rate, storage resource utilization rate, data transmission rate, and number of concurrent users, the computing nodes will be automatically expanded or spare storage resources will be allocated.

[0010] In one embodiment, optionally, the method further includes: In response to a user's login request, complete identity authentication and assign corresponding template selection permissions, editing permissions, and data viewing permissions based on the user's identity; The user workspace is initialized based on the project information created by the user, so as to realize the isolated storage and access control of different project data.

[0011] In one embodiment, optionally, the creation process of the preset function template library includes: Based on the functional scenarios of industrial automation systems, the system is broken down into multiple functional modules, and the functional boundaries and interface requirements of each module are determined. For each functional module, determine the parameterized configuration structure, preset adjustable parameter items (i.e., parameter value ranges), and formulate parameter validation rules; Define a unified input / output interface, data interaction format, and module calling protocol for all functional templates; Each functional template is tested, and the functional templates that pass the test are classified and stored according to functional type, application scenario and version number. A template retrieval index is established and the template attribute information is entered to obtain the preset functional template library.

[0012] In one embodiment, optionally, the template combination rules include at least one of the following: template compatibility verification rules, interface matching rules, and functional module combination priority rules, and the project version information includes version number, modification time, modification user, and modification content summary.

[0013] In one embodiment, optionally, the concurrency control and conflict resolution include: The configuration editing operations of multiple users are time-sequentially ordered, and optimistic locking is used to mark the template being edited. When a conflicting operation is detected, the latest edited version is retained, and the user who initiated the conflict is prompted to perform a comparative analysis.

[0014] In one embodiment, optionally, the preset database adopts a distributed storage architecture to encrypt and back up configuration scheme files, template data, user operation data, and project version information.

[0015] Secondly, embodiments of this application provide a cloud-based collaborative configuration device, comprising: The selection module is used to respond to the user's template selection command and select the target function template corresponding to the target project from the preset function template library; The combination module is used to perform initial template combination according to the received template combination rules and the target function template, and load the combined template resources into the user workspace; The processing module is used to build a multi-user real-time collaboration channel, perform concurrent control and conflict resolution on configuration editing operations initiated by multiple users simultaneously on the combined template, synchronize any user's editing modifications to the combined template to the user workspaces of all collaborating users in real time, and synchronously record operation logs and project version information. The generation module is used to generate a configuration scheme file in response to receiving a configuration editing completion instruction from the user, based on the combined template and the configuration editing operation for the combined template; The storage module is used to test the configuration scheme file and, after the test is passed, store the configuration scheme file in a preset database.

[0016] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the cloud-based collaborative configuration method described above.

[0017] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the aforementioned cloud-based collaborative configuration method.

[0018] In the above-described cloud-based collaborative configuration method, device, equipment, and medium, in response to a user's template selection command, a target function template corresponding to the target project is selected from a preset function template library; based on the received template combination rules and the target function template, an initial template combination is performed, and the combined template resources are loaded into the user's workspace; a multi-user real-time collaboration channel is constructed to perform concurrent control and conflict resolution on configuration editing operations initiated simultaneously by multiple users for the combined template, and to synchronize any user's editing modifications to the combined template to the workspaces of all collaborating users in real time, while simultaneously recording operation logs and project version information; in response to receiving a user's configuration editing completion command, a configuration scheme file is generated based on the combined template and the configuration editing operations performed on the combined template; the configuration scheme file is tested, and after passing the test, the configuration scheme file is stored in a preset database. The above-mentioned technical solution of the present invention, with the help of a preset functional template library and a precise matching mechanism, eliminates the need for users to build functional modules from scratch, significantly reducing repetitive development work. Combined with automated verification and integration of template combination rules, it effectively avoids compatibility conflicts between templates, quickly generating initial template resources adapted to the target project and loading them into a dedicated workspace, significantly shortening the configuration preparation cycle. By constructing a multi-user real-time collaboration channel, coupled with concurrent control and conflict resolution mechanisms such as time-series sorting and optimistic locking, it supports multi-user remote synchronous editing while ensuring the consistency of operation data, enabling real-time synchronized editing and complete recording of operations. Logs and project version information make the configuration process traceable and reversible, significantly improving the collaboration efficiency of complex projects. After configuration editing is completed, template resources and editing operations are automatically integrated to generate standardized configuration solution files. After multi-dimensional testing and verification to ensure functional reliability, the files are stored in a preset database for secure storage. The fully automated process greatly reduces operational errors caused by human intervention, improving the accuracy and stability of configuration solutions. At the same time, the integrated design of template reuse, collaborative work and secure storage adapts to the configuration needs of various scenarios such as industrial automation, significantly reducing project implementation costs and improving the scalability and maintainability of configuration work. Attached Figure Description

[0019] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments 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.

[0020] Figure 1 A schematic flowchart of a cloud-based collaborative configuration method according to an embodiment of this application is shown.

[0021] Figure 2A schematic flowchart of a cloud-based collaborative configuration method according to another embodiment of this application is shown.

[0022] Figure 3 A schematic flowchart of a cloud-based collaborative configuration method according to yet another embodiment of this application is shown.

[0023] Figure 4 A schematic flowchart illustrating the creation process of a preset function template library according to an embodiment of this application is shown.

[0024] Figure 5 A block diagram of a cloud-based collaborative configuration device according to an embodiment of this application is shown.

[0025] Figure 6 A block diagram of a computer device according to one embodiment of this application is shown. Detailed Implementation

[0026] To better understand the technical solution of this application, the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0027] It should be understood that the described embodiments are merely some, not all, of the embodiments in this application. All other embodiments obtained by those skilled in the art based on the embodiments in this application without inventive effort are within the scope of protection of this application.

[0028] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. The singular forms “a,” “the,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise.

[0029] The following detailed description of some embodiments of this application is provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0030] Please see Figure 1 , Figure 1 A schematic flowchart of a cloud-based collaborative configuration method according to an embodiment of this application is shown.

[0031] like Figure 1 As shown, the cloud-based collaborative configuration method includes: Step S101: In response to the user's template selection instruction, select the target function template corresponding to the target project from the preset function template library.

[0032] Template selection instructions are initiated by users through the front-end interface (such as button clicks or menu selections) to specify the required functional templates for the target project. They include key information such as project identifiers and required functional types.

[0033] The preset function template library is a standardized collection of pre-built templates covering common functions in scenarios such as industrial automation. Each template contains fixed functional logic, configurable parameters and interface definitions, and supports quick invocation according to project requirements.

[0034] The target function template is a template selected from the template library that precisely matches the functional requirements of the target project. It serves as the basis for subsequent template combinations and configuration editing.

[0035] First, the system monitors user operations in real time. When a template selection instruction is detected, it parses the target project information (such as project type and control scenario) carried in the instruction. Then, based on the project information, it traverses the preset functional template library and filters out the target functional templates that meet the requirements through keyword matching, scenario feature comparison, and other methods. During the filtering process, the compatibility between the template and the project needs to be verified. Finally, the list of target functional templates is returned to the user interface for the user to confirm and complete the selection.

[0036] This avoids the tedious process of building functional modules from scratch in traditional configuration, and significantly shortens the initial configuration cycle through template reuse; standardized templates ensure the standardization and reliability of functional logic, reducing the risk of logical loopholes caused by custom functional design; and a precise template matching mechanism improves project adaptation efficiency, reduces invalid user operations, and lays an efficient foundation for subsequent template combinations.

[0037] Step S102: Based on the received template combination rules and the target function template, perform initial template combination and load the combined template resources into the user workspace.

[0038] Template combination rules are a standardized set of rules used to guide the collaborative combination of multiple target function templates, ensuring that the combined templates are compatible in terms of function, interface, and logic, and avoiding conflicts.

[0039] The initial template combination is a set of templates that are associated and integrated with multiple target function templates according to the combination rules, forming a complete set of preliminary functions. It is the core object of configuration editing.

[0040] A user workspace is a dedicated virtual work environment allocated to each user. It is used to store, display, and edit combined template resources, and supports personalized layouts and operation record tracking.

[0041] First, the system reads the preset template combination rules (such as compatibility checks and interface matching requirements); based on the rules, it checks each selected target function template one by one, such as checking whether the interface data formats between templates are consistent and whether there are conflicts in functional logic (such as conflicts in parameter value ranges and contradictions in control timing); after the verification is passed, the system automatically establishes the association relationship between templates (such as signal transmission paths and data interaction logic) to complete the initial combination; finally, the combined template resources (including functional logic, parameter configuration interface, and interface definition) are loaded into the user's workspace, supporting users to view and perform preliminary operations in real time.

[0042] By using standardized combinations, compatibility issues between templates are avoided, reducing the risk of rework in subsequent configuration editing; automatic association of template relationships eliminates the need for manual connection operations, improving combination efficiency; isolated storage in the user workspace ensures the security and independence of template resources, avoids data confusion between different projects, and provides a basic environment for subsequent multi-user collaboration.

[0043] Step S103: Construct a multi-user real-time collaboration channel to perform concurrent control and conflict resolution on configuration editing operations initiated simultaneously by multiple users on the combined template. Real-time synchronization of any user's editing modifications to the combined template to the user workspaces of all collaborating users, and simultaneous recording of operation logs and project version information.

[0044] The multi-user real-time collaboration channel is a virtual channel built on real-time communication technologies such as WebSocket, which supports multiple users to access the same project's template resources at the same time, enabling real-time interaction of operations and data.

[0045] Concurrency control is a technical mechanism used to manage simultaneous editing operations by multiple users, ensuring that multiple operations are executed in an orderly manner in terms of time and resource consumption, and avoiding data chaos caused by resource contention.

[0046] Conflict resolution is a technical means used to coordinate and ensure data consistency when multiple users initiate conflicting edits to the same template resource (such as simultaneously modifying the same parameter).

[0047] Operation logs are structured data that records user editing operations in detail, including information such as the operator, operation time, operation content, and operation result, for traceability and auditing.

[0048] Project version information is a record of version identifiers and changes at different editing stages of a project. It supports version backtracking, comparison, and recovery, ensuring that the configuration process is controllable.

[0049] First, the system builds a collaboration channel based on a real-time communication protocol, assigns a unique identifier to each collaborating user, and establishes a binding relationship between the user and the workspace. When multiple users initiate editing operations simultaneously, a concurrency control mechanism sorts the operations in chronological order (e.g., by operation initiation timestamp) and uses a locking mechanism (e.g., optimistic locking) to mark the resource being edited. If a conflicting operation is detected (e.g., two users modifying the same parameter simultaneously), a conflict resolution mechanism is triggered, preserving the latest edited version and pushing a differentiated comparison interface (displaying the modifications made by different users) to the user who initiated the conflict. Simultaneously, each editing operation is synchronized in real-time to the workspaces of all collaborating users to ensure visual consistency. Figure 1 Consistency; Synchronously records operation logs and project version information, including version number, modification time, modification user, and content summary, supporting subsequent version management.

[0050] This breaks through the limitations of traditional single-machine configuration, supports real-time collaboration among multiple users in different locations, and significantly improves the configuration efficiency of complex projects; the concurrency control and conflict resolution mechanisms ensure data consistency for multi-user operations and avoid logical errors or data loss caused by collaboration; operation logs and version information provide a basis for project traceability, problem investigation and responsibility definition, and improve the controllability and security of the configuration process.

[0051] Step S104: In response to receiving the user's configuration editing completion instruction, generate a configuration scheme file based on the combined template and the configuration editing operation for the combined template.

[0052] The configuration editing completion command is initiated by the user through the front-end interface (such as the "Submit" button) after completing all configuration editing operations, and is used to trigger the generation of the configuration scheme file.

[0053] The configuration scheme file is a standardized file that contains the complete functional logic, parameter configuration, interface definition, and user editing and modification records of the combined template. It is the core carrier of the configuration results and can be directly used for subsequent testing and deployment.

[0054] This step is crucial for solidifying the configuration results, and its core is to transform scattered editing operations into a unified solution file. First, the system listens for user operations. When it receives an editing completion instruction, it automatically collects the basic information of the combined template (functional modules, interface definitions) and the user's editing records (parameter modifications, logic adjustments, and new functional nodes). The information is then structured and integrated according to a preset file format (such as XML or JSON) to ensure the file contains complete content including "functional description - parameter configuration - logical relationships - interface descriptions." During integration, the completeness of the information is verified (e.g., whether there are any unconfigured required parameters, and whether the logical relationships are closed-loop). After successful verification, a configuration solution file is generated, and a preview interface is provided for user confirmation.

[0055] This solution automatically integrates the editing results, avoiding the tedious operation and risk of omissions in manually compiling solution documents; the standardized file format ensures that the solution documents can be recognized and compatible by subsequent testing modules and deployment systems, improving cross-stage adaptability; the preview confirmation mechanism provides users with a final verification opportunity, further ensuring the accuracy of the solution documents and reducing rework costs in subsequent testing and deployment.

[0056] Step S105: Test the configuration scheme file, and after the test is passed, store the configuration scheme file in a preset database.

[0057] Configuration file testing is the process of verifying the functional integrity, logical correctness, interface compatibility, and operational stability of configuration file, ensuring that the configuration file can be deployed and run normally.

[0058] The default database is a specialized database used to store configuration scheme files, template data, user operation records, and other information. It features high availability, security, and fast retrieval capabilities.

[0059] In this step, the configuration scheme file is first imported into a dedicated testing module. The tests include: functional integrity verification (whether it covers all functions required by the project), logical correctness verification (simulating input signals to verify whether the output results meet expectations), interface compatibility verification (whether the interface data interaction with the target device / system is normal), and abnormal operating condition stability verification (simulating scenarios such as parameter over-limit and signal interruption to verify whether the scheme has fault tolerance capabilities). If the test fails, a test report (marking the error location and reason) is returned for the user to modify and retest. If the test passes, the system automatically encrypts the scheme file, stores it in a preset database, and creates an index (such as project identifier, scheme name, and version number) to support subsequent quick retrieval and retrieval.

[0060] Multi-dimensional testing helps identify potential problems in solution documents in advance, preventing functional failures after deployment and ensuring the safe operation of industrial systems; encrypted storage and database management ensure the security and manageability of solution documents, preventing data leakage or loss; and an indexing mechanism improves the retrieval efficiency of solution documents, facilitating reuse or modification in subsequent projects and reducing repetitive development costs.

[0061] like Figure 2 As shown, in one embodiment, optionally, the method further includes: Step S201: Monitor the computing resource utilization rate, storage resource utilization rate, data transmission rate, and number of concurrent users in real time during the project configuration process.

[0062] Computing resource utilization rate is the proportion of resources used by computing hardware such as CPU and memory during the configuration process, reflecting the system's load in processing data and performing operations.

[0063] Storage resource utilization rate is the proportion of storage media such as hard drives and cloud storage used to store template resources, solution documents and other data, reflecting the remaining storage capacity.

[0064] Data transmission rate refers to the speed at which information such as editing operations and data synchronization is transmitted over the network during multi-user collaboration, affecting the real-time performance of the collaboration.

[0065] The number of concurrent users is the total number of users accessing the same project and editing its configuration at the same time, which directly affects the system's resource load.

[0066] This embodiment focuses on resource management to ensure a smooth configuration process. The system deploys a resource monitoring module that collects real-time operational data from the operating system, network devices, and applications. This data includes computing resource utilization (e.g., CPU usage, memory usage), storage resource utilization (e.g., disk space usage percentage), data transfer rate (e.g., amount of data synchronized per unit time), and the number of concurrent users. The monitoring frequency can be dynamically adjusted based on project scale (e.g., monitoring every 10 seconds for large projects and every 30 seconds for small projects). Monitoring data is uploaded to the resource management platform in real-time, generating a visual monitoring dashboard for administrators.

[0067] Real-time monitoring of system resource operation status allows for early identification of resource bottleneck risks (such as high CPU utilization causing operational lag), preventing configuration efficiency from being affected by insufficient resources; visual monitoring enables administrators to intuitively understand system load, providing data support for resource optimization and improving the initiative and accuracy of system operation and maintenance.

[0068] Step S202: When any one of the following indicators exceeds a preset threshold: resource occupancy rate, storage resource utilization rate, data transmission rate, and number of concurrent users, the computing nodes are automatically expanded or spare storage resources are allocated.

[0069] The preset thresholds are resource warning values ​​set based on system performance testing and engineering practice, such as a CPU utilization threshold of 80%, a storage resource utilization threshold of 85%, and a minimum data transfer rate threshold of 1Mbps. Exceeding the threshold indicates that the system resources may not be able to meet the current demand.

[0070] Automatic scaling of computing nodes leverages the elastic scaling capabilities of the cloud platform to automatically increase the number of computing nodes such as CPUs and memory, thereby enhancing the system's data processing capabilities.

[0071] Backup storage resources are pre-reserved additional storage space (such as backup cloud disks or distributed storage nodes) to cope with insufficient storage resources, and can be quickly allocated and used.

[0072] This embodiment describes the execution phase of dynamic resource scheduling. The resource management platform compares real-time monitored metrics with preset thresholds. If any metric exceeds the threshold (e.g., CPU utilization reaches 85%, data transfer rate drops to 0.8Mbps), the resource scheduling mechanism is automatically triggered: for insufficient computing resources, the elastic scaling service is invoked through the cloud platform API to increase the number of computing nodes (e.g., expanding from 2 CPU cores to 4); for insufficient storage resources, backup storage resources are automatically mounted (e.g., allocating a backup cloud disk to the current project's storage directory); for excessively low data transfer rates, network routing is optimized or bandwidth resources are increased; after resource scheduling is completed, the scheduling results are fed back to the monitoring dashboard in real time and the administrator is notified.

[0073] This embodiment enables dynamic on-demand allocation of resources, avoiding problems such as configuration operation lag and data synchronization delay caused by insufficient resources, ensuring the smoothness of multi-user collaboration and complex project configuration; automated scheduling reduces manual intervention, lowers the management and maintenance costs, and avoids excessive resource idleness, thereby improving resource utilization efficiency.

[0074] like Figure 3 As shown, in one embodiment, optionally, the method further includes: Step S301: In response to the user's login request, complete identity authentication and assign corresponding template selection permissions, editing permissions and data viewing permissions according to the user's identity; A login request is an access request initiated by a user by entering their account password, verification code, etc., to enter the system, and contains user identification information.

[0075] Identity authentication is the process of verifying the legitimacy of a user's identity. It involves comparing the user's input information with the identity data stored in the system (such as password hashes and role information) to confirm whether the user has permission to access the system.

[0076] Permission allocation is the process of assigning system operation permissions to users based on their identity (such as administrator, engineer, operator), ensuring that users can only perform operations that match their roles.

[0077] First, the system receives a user login request and parses the identity information (such as username and password) in the request. It then compares the password with the encrypted data stored in the system database using an encryption algorithm (such as SHA-256), and verifies the account status (such as whether it is frozen or expired) to complete identity authentication. After successful authentication, permissions are assigned according to the user's preset role (such as administrator or regular engineer): administrators have permission to modify the template library and view all project data; engineers have permission to select templates and edit configurations; operators only have data viewing permissions. The permission assignment results are bound to the user session in real time, ensuring that the user can only perform authorized operations during this login cycle.

[0078] Strict identity authentication prevents unauthorized users from entering the system, ensuring system security; fine-grained permission allocation avoids unauthorized user operations (such as operators modifying configuration logic), reducing the risk of data leakage and misoperation; role-based permission management simplifies the permission configuration process, improves system operation and maintenance efficiency, and complies with the security management standards of industrial systems.

[0079] Step S302: Initialize the corresponding user workspace based on the project information created by the user to achieve isolated storage and access control of different project data.

[0080] Project information is the basic information that users fill in when creating a project, such as project name, project type, list of participating users, project duration, etc., which is used to identify the uniqueness of the project.

[0081] Workspace initialization is the process of creating a dedicated virtual work environment for users based on project information, including configurations such as project data storage directory, user interface layout, and resource access paths.

[0082] Data isolation storage is a mechanism that separates template resources, editing records, scheme files, and other data from different projects and stores them in independent directories or database partitions to ensure that project data does not interfere with each other.

[0083] This embodiment represents the core component for achieving parallel management of multiple projects. After a user creates a project and submits project information, the system generates a unique project identifier (such as a project ID) based on the project information. Based on the project identifier, an independent storage directory and database partition are created on the server to store all data for that project (template resources, operation logs, and solution files). Simultaneously, the user's workspace is initialized, an interface layout matching the project type is loaded (e.g., loading an equipment control component library for an industrial control project), and the project data access path is bound. At the access control level, only users participating in the project (based on the participant list in the project information) are allowed to access the project's workspace; other users have no access rights, ensuring data isolation.

[0084] Data isolation storage avoids data confusion between different projects (e.g., a template from project A is mistakenly modified by project B), ensuring the independence and security of project data; dedicated workspaces provide users with a personalized operating environment, improving the convenience of configuration operations; fine-grained access control ensures that project data is only accessible to authorized users, preventing data leakage, while supporting parallel configuration of multiple projects, improving system resource utilization.

[0085] like Figure 4 As shown, in one embodiment, optionally, the creation process of the preset function template library includes: Step S401: Based on the functional scenarios of the industrial automation system, decompose it into multiple functional modules and determine the functional boundaries and interface requirements of each functional module.

[0086] Industrial automation system functional scenarios are common automation control scenarios in industrial production, such as production line equipment control, data acquisition and monitoring, and process parameter adjustment, and serve as the basis for the functional design of the template library.

[0087] A functional module is the smallest unit with independent function formed by breaking down functional scenarios, such as a data acquisition module, a PID control module, and an alarm processing module.

[0088] Functional boundaries define the core functional scope and non-responsibility scope of a functional module, avoiding functional overlap or omission between modules.

[0089] Interface requirements define the format, protocol, and parameters for data interaction between functional modules and external entities (other modules, devices, systems) to ensure compatibility between modules.

[0090] First, the system analyzes typical functional scenarios in the field of industrial automation (such as automation needs in industries like power, chemical, and automotive manufacturing). Complex scenarios are broken down into multiple independent functional modules using demand decomposition methods (such as flowcharts and use case analysis). For each module, its functional boundaries are clearly defined (e.g., a data acquisition module is only responsible for signal acquisition and does not include data processing). Simultaneously, interface requirements are defined, including input / output data formats (e.g., analog signal range 0-10V, digital signal 0 / 1), data interaction protocols (e.g., Modbus, Profinet), and interface parameters (e.g., sampling frequency, data precision), forming a module design document.

[0091] Scenario-based decomposition ensures that the template library covers the core needs of industrial automation, improving the versatility and practicality of the templates; clear functional boundaries and interface requirements avoid module redundancy or conflicts, laying the foundation for subsequent template combination and compatibility; standardized interface design reduces the difficulty of integration between modules and improves the scalability of the template library.

[0092] Step S402: For each functional module, determine the parameterized configuration structure, preset the adjustable parameter items (i.e., the parameter value range), and formulate parameter verification rules.

[0093] A parameterized configuration structure defines how adjustable parameters are organized within a functional module, such as parameter categories (basic parameters, advanced parameters) and parameter hierarchies (module-level parameters, sub-functional-level parameters), facilitating quick configuration by users.

[0094] Adjustable parameters are parameters in the functional modules that allow users to modify according to project requirements, such as the proportional coefficient, integral time, and derivative time of the PID control module.

[0095] The parameter value range is a set range of legal values ​​for each adjustable parameter to prevent users from inputting invalid parameters, which could cause module malfunctions.

[0096] Parameter validation rules are rules used to verify whether user input parameters conform to the value range and format requirements, such as numerical range validation and data type validation.

[0097] For each functional module, a parameterized configuration structure is determined based on its functional logic. For example, the parameters of the data acquisition module are divided into basic parameters (sampling frequency, signal type) and advanced parameters (filter coefficient, alarm threshold). Core parameters are selected as adjustable parameters, and parameter value ranges are set in combination with industrial standards and module functional requirements (such as sampling frequency range of 1-1000Hz, filter coefficient range of 0-1). At the same time, parameter verification rules are formulated, such as numerical range verification (input value must be within the range), format verification (parameter must be numeric, not text), and correlation verification (such as alarm upper limit must be greater than alarm lower limit), to ensure that user input parameters are legal and valid.

[0098] Parameterized configuration allows templates to adapt to different project requirements without modifying the core logic, greatly improving template reusability; clear parameter value ranges and validation rules prevent module function failures caused by incorrect parameter configuration, reducing configuration difficulty; and the structured parameter organization improves user configuration efficiency and reduces invalid operations.

[0099] Step S403: Set a unified input / output interface, data interaction format, and module calling protocol for all functional templates.

[0100] The unified input / output interface is a standardized interface format set for all functional templates, ensuring that the input and output methods of different templates are consistent and facilitating inter-module communication.

[0101] Data exchange format defines the format standard for data transmission between templates and between templates and external systems, such as XML, JSON, and binary formats, to ensure that data can be correctly parsed.

[0102] The module calling protocol specifies the process, instruction format, and response mechanism when a template is called by other modules or systems, such as the call request format, return result format, and error handling method.

[0103] First, based on common standards in the field of industrial automation (such as IEC 61131-3), a unified input / output interface type (such as analog input interface, digital output interface, and communication interface) is set for all functional templates; a standardized data interaction format is defined, clarifying the meaning, data type, and length of data fields (such as using JSON format, including parameter name - parameter value - data type - timestamp fields); a module calling protocol is formulated to standardize the calling process (such as the caller sending a request containing template ID and parameters → the template executing the function → returning the result), and an error handling mechanism (such as returning an error code for call timeout and returning a prompt message for parameter errors), ensuring smooth interaction between different templates and between templates and external systems (such as DCS systems).

[0104] Unified interfaces and formats eliminate compatibility barriers between different templates, enabling flexible combination of any templates and enhancing the flexibility and scalability of the template library; standardized calling protocols ensure that templates can be compatible with different external systems, expanding the application scenarios of the template library (such as simultaneously adapting to multiple brands of DCS systems); reducing user learning costs, users do not need to adjust their operating habits due to differences in template interfaces, improving configuration efficiency.

[0105] Step S404: Test each functional template, classify and store the functional templates that pass the test according to function type, application scenario and version number, establish a template retrieval index, and enter the template attribute information to obtain the preset functional template library.

[0106] Functional template testing: The process of verifying the correctness of the function of the functional template, interface compatibility, parameter configuration flexibility and fault tolerance, to ensure that the template can be used normally.

[0107] Categorized storage: This method stores tested templates into different directories or database categories according to preset dimensions (function type, application scenario, version number), facilitating management and retrieval.

[0108] Template retrieval index: An index structure built based on template attribute information (such as function name, application scenario, parameter range), supporting quick query and filtering of templates.

[0109] Template attribute information: Structured data describing the core features of the template, such as template name, function description, application scenario, adjustable parameters, interface type, version number, update time, etc.

[0110] First, each functional template undergoes multi-dimensional testing: functional correctness testing (simulating input to verify if the output meets expectations), interface compatibility testing (interfacing with other templates or systems to verify if data interaction is normal), parameter configuration testing (modifying parameters to verify if the template function can be flexibly adjusted), and anomaly testing (simulating parameter overruns and interface interruptions to verify the template's fault tolerance). After passing the tests, the templates are categorized and stored according to functional type (e.g., data acquisition, control, alarm), application scenario (e.g., power industry, chemical industry), and version number (e.g., V1.0, V1.1). A search index (e.g., keyword index, scenario classification index) is built based on template attribute information (e.g., template name, application scenario). Finally, the template attribute information is entered into the template library management system, allowing users to quickly retrieve templates through the index and complete the construction of a preset functional template library.

[0111] Multi-dimensional testing ensures the reliability of template functions and reduces the risk of failure when users use templates; categorized storage and retrieval indexes greatly improve template search efficiency (e.g., users can quickly locate templates by chemical industry - temperature control), reducing invalid searches; complete template attribute information helps users quickly understand template characteristics, improves the accuracy of template selection, and lays an efficient foundation for subsequent configuration processes.

[0112] In one embodiment, optionally, the template combination rules include at least one of the following: template compatibility verification rules, interface matching rules, and functional module combination priority rules, and the project version information includes version number, modification time, modification user, and modification content summary.

[0113] Template compatibility verification rules: Rules used to verify whether multiple templates are compatible in terms of functional logic, parameter range, and operating environment, such as "the signal type of the data acquisition template must be consistent with the input type of the control template".

[0114] Interface matching rules: rules to ensure that the interface data format, protocol and number of parameters are consistent between templates, such as "the output data format of template A must be the same as the input data format of template B".

[0115] Functional module combination priority rules: Define the order or importance of multiple templates when combining them, such as core control templates taking precedence over auxiliary alarm templates, to ensure that the functional logic of the combined templates is orderly.

[0116] Version number: Used to uniquely identify different editing stages of a project (such as V1.0, V1.1), supporting version differentiation and traceability.

[0117] Summary of Changes: Briefly describe the core changes in this version (e.g., "adjusted PID parameter range, added alarm module") to help users quickly understand the version changes.

[0118] During the template combination phase, the system performs sequential verification according to rules: First, it checks for functional logic conflicts between templates using compatibility verification rules (e.g., high-speed acquisition templates cannot be combined with low-precision control templates) and parameter range matching (e.g., the signal range of the acquisition template must include the input range of the control template); then, it verifies whether the data format (e.g., XML / JSON), protocol (e.g., Modbus / TCP), and parameter quantity are consistent between templates using interface matching rules. If they do not match, the system automatically prompts the user to adjust; finally, it determines the template combination order according to combination priority rules, ensuring that core function templates are loaded first and avoiding auxiliary templates from affecting core logic. During the version management phase, project version information is recorded in real time: version numbers are generated according to major version number and minor version number rules (e.g., initial edit is V1.0, minor modification is V1.1); modification time records the precise time the operation was completed (e.g., 2024-10-01 14:30:00); modification user records the operator's account; modification content summary concisely summarizes the changes (e.g., adding a temperature alarm threshold parameter). All information is synchronously stored in the version management module.

[0119] Multi-dimensional combination rules ensure the compatibility and logic of template combinations, avoiding functional failures after combination (such as signal transmission failure due to data format mismatch), and reducing subsequent editing and rework; standardized version information makes changes at each stage of the project clearly traceable, making it easy for users to compare differences between different versions, roll back erroneous versions, and provide a basis for version synchronization when multiple users collaborate, thereby improving project management efficiency.

[0120] In one embodiment, optionally, the concurrency control and conflict resolution include: The configuration editing operations of multiple users are time-sequentially ordered, and optimistic locking is used to mark the template being edited.

[0121] Time-series sorting assigns a unique timestamp to each operation based on the order in which multiple users initiate editing operations, thus determining the order in which operations are executed and avoiding resource contention.

[0122] Optimistic locking mechanism: a lock-free concurrency control technology that adds version numbers or timestamps to resources (such as templates) and only checks whether the resource has been modified when the operation is committed, without locking the resource in advance. It is suitable for low-conflict scenarios.

[0123] First, the system assigns a unique timestamp-based sequence identifier (e.g., 20241001143000_UserA) to each user's edit operation, arranging the operation queue in timestamp order to ensure that operations initiated earlier are executed first. Simultaneously, an optimistic locking mechanism is used to add temporary markers (e.g., version number and editor user identifier) ​​to the template resource being edited. This marker information is synchronized in real-time to the workspaces of all collaborating users, alerting other users that "this template is being edited." During operation execution, the resource is not locked; other users are allowed to view it but editing is restricted. The system only checks whether the template markers have changed (e.g., whether it has been modified by another user) when the operation is submitted.

[0124] Sequential sorting ensures that multi-user operations are executed in an orderly manner, avoiding data chaos caused by parallel operations; the optimistic locking mechanism eliminates the need to lock resources in advance, reducing operation waiting time (e.g., users can view templates without waiting for others to release locks), and improving the efficiency of multi-user collaboration; real-time marking prompts help users understand the resource editing status, reduce the probability of conflicting operations, and reduce the pressure of subsequent conflict resolution.

[0125] When a conflicting operation is detected, the latest edited version is retained, and the user who initiated the conflict is prompted to perform a comparative analysis.

[0126] Conflicting operations: When multiple users initiate editing operations on the same part of the same template resource (such as the same parameter or the same logical node) at the same time, it will lead to inconsistent data.

[0127] Latest edited version: Among multiple conflicting operations, the last submitted edit that passes verification is the version ultimately retained by the system.

[0128] Differential Comparison: This feature compares the changes made by the user who initiated the conflict with the latest edited version, displaying the differences (such as parameter values ​​before and after modification, and the addition / deletion of logical nodes).

[0129] The system monitors operation submission requests in real time. When it detects multiple users editing the same part of the same template resource (e.g., User A and User B simultaneously modifying the PID ratio coefficient), it triggers a conflict detection mechanism. Based on the operation submission timestamp and version number, it determines the latest edited version (e.g., if User B's operation submission time is later and the version number is higher, User B's modification is retained). Simultaneously, it pushes a conflict notification to the user who initiated the conflict (e.g., User A), including the name of the conflicting resource, the latest editing user, and a comparison entry point. After the user clicks the entry point, the system displays a comparison interface between "User's Modified Content" and "Latest Version Content" (e.g., user's modifications are highlighted in red, and the latest version's modifications are highlighted in green), clearly presenting the differences and allowing the user to determine whether they need to modify based on the latest version.

[0130] Retaining the latest edited version ensures data consistency and prevents the loss of editing results due to conflicts; differential comparison provides users with clear conflict information, helping them quickly understand the content modified by others and reducing repetitive work (such as locating differences without having to review the entire template again); the conflict prompt mechanism promptly informs users of the operation status, preventing users from continuing to edit ineffectively due to not noticing conflicts, thus improving collaboration efficiency and user experience.

[0131] In one embodiment, optionally, the preset database adopts a distributed storage architecture to encrypt and back up configuration scheme files, template data, user operation data, and project version information.

[0132] Distributed storage architecture: A database architecture that distributes data across multiple independent storage nodes (such as storage devices on different servers or in different regions), improving storage reliability and access speed through data sharding and redundancy.

[0133] Encrypted storage: A mechanism that uses encryption algorithms (such as AES-256, RSA) to encrypt data before storing it, ensuring that the data cannot be deciphered even if it is illegally obtained.

[0134] Multiple replica backup: A mechanism that replicates data into multiple identical copies and stores them on different storage nodes to address the risk of data loss due to storage node failure.

[0135] This embodiment represents a core design element ensuring data security and high availability. The default database employs a distributed storage architecture, sharding configuration files, template data, user operation data, and project version information according to data type and access frequency (e.g., frequently accessed template data is stored on nodes closer to users, while infrequently accessed historical version data is stored on remote nodes). Each shard is synchronized across multiple storage nodes (e.g., at least three nodes). Simultaneously, all data is encrypted: SSL / TLS encryption is used during transmission, and AES-256 encryption is used during storage. The keys are stored in an independent key management system to prevent key leakage. Furthermore, a multi-replica backup function is enabled, automatically generating at least three replicas for each data shard and storing them on storage nodes in different regions or with different hardware. When one node fails, the system automatically uses other replicas to ensure no data loss.

[0136] Distributed storage architecture improves data access speed (e.g., users retrieve template data from the nearest node) and supports elastic expansion of storage capacity to meet the storage needs of massive project data; encrypted storage ensures data security during transmission and storage, preventing data leakage (e.g., configuration scheme files being illegally stolen), and complies with industrial data security standards; multiple backups significantly improve data availability, and even in the event of hardware failure or natural disasters, data can be quickly recovered, avoiding project interruption due to data loss and ensuring the continuity of the configuration process.

[0137] Figure 5 A block diagram of a cloud-based collaborative configuration device according to an embodiment of this application is shown.

[0138] like Figure 5 As shown, in a second aspect, embodiments of this application provide a cloud-based collaborative configuration device 50, comprising: The selection module 51 is used to select the target function template corresponding to the target project from the preset function template library in response to the user's template selection command. The combination module 52 is used to perform initial template combination according to the received template combination rules and the target function template, and load the combined template resources into the user workspace. The processing module 53 is used to build a multi-user real-time collaboration channel, perform concurrent control and conflict resolution on configuration editing operations initiated by multiple users simultaneously on the combined template, synchronize any user's editing modifications to the combined template to the user workspaces of all collaborating users in real time, and synchronously record operation logs and project version information. The generation module 54 is used to generate a configuration scheme file in response to receiving a configuration editing completion instruction from the user, based on the combined template and the configuration editing operation for the combined template; The storage module 55 is used to test the configuration scheme file and, after the test is passed, store the configuration scheme file in a preset database.

[0139] In one embodiment, optionally, the apparatus further includes: The computing module is used to monitor the computing resource utilization, storage resource utilization, data transmission rate, and number of concurrent users in real time during the project configuration process. The resource allocation module is used to automatically expand computing nodes or allocate spare storage resources when any of the following indicators exceeds a preset threshold: resource occupancy rate, storage resource utilization rate, data transmission rate, and number of concurrent users.

[0140] In one embodiment, optionally, the apparatus further includes: The permission allocation module is used to complete identity authentication in response to user login requests, and to assign corresponding template selection permissions, editing permissions, and data viewing permissions according to the user's identity; The control module is used to initialize the corresponding user workspace based on the project information created by the user, so as to realize the isolated storage and access control of different project data.

[0141] In one embodiment, optionally, the creation process of the preset function template library includes: Based on the functional scenarios of industrial automation systems, the system is broken down into multiple functional modules, and the functional boundaries and interface requirements of each module are determined. For each functional module, determine the parameterized configuration structure, preset adjustable parameter items (i.e., parameter value ranges), and formulate parameter validation rules; Define a unified input / output interface, data interaction format, and module calling protocol for all functional templates; Each functional template is tested, and the functional templates that pass the test are classified and stored according to functional type, application scenario and version number. A template retrieval index is established and the template attribute information is entered to obtain the preset functional template library.

[0142] In one embodiment, optionally, the template combination rules include at least one of the following: template compatibility verification rules, interface matching rules, and functional module combination priority rules, and the project version information includes version number, modification time, modification user, and modification content summary.

[0143] In one embodiment, optionally, the concurrency control and conflict resolution include: The configuration editing operations of multiple users are time-sequentially ordered, and optimistic locking is used to mark the template being edited. When a conflicting operation is detected, the latest edited version is retained, and the user who initiated the conflict is prompted to perform a comparative analysis.

[0144] In one embodiment, optionally, the preset database adopts a distributed storage architecture to encrypt and back up configuration scheme files, template data, user operation data, and project version information.

[0145] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the cloud-based collaborative configuration method described above.

[0146] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the aforementioned cloud-based collaborative configuration method.

[0147] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the cloud-based collaborative configuration device and its modules described above can be referred to the corresponding processes in the aforementioned cloud-based collaborative configuration method embodiments, and will not be repeated here.

[0148] It should be noted that those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the model training device and each module described above can be referred to the corresponding processes in the aforementioned cloud-based collaborative configuration method embodiments, and will not be repeated here.

[0149] The aforementioned cloud-based collaborative configuration device can be implemented as a computer program, which can be used in, for example... Figure 6 It runs on the computer device shown.

[0150] Figure 6 A block diagram of a computer device according to one embodiment of this application is shown.

[0151] See Figure 6 The computer device includes a processor, memory, and network interface connected via a system bus, wherein the memory may include storage media and internal memory.

[0152] The storage medium may store an operating system and a computer program. The computer program includes program instructions that, when executed, cause the processor to perform any of the cloud-based collaborative configuration methods for multi-source data provided in the embodiments of this application.

[0153] The processor provides computing and control capabilities, supporting the operation of the entire computer device.

[0154] The internal memory provides an environment for the execution of computer programs stored in the storage medium. When executed by a processor, this computer program enables the processor to perform any cloud-based collaborative configuration method for multi-source data. The storage medium can be non-volatile or volatile.

[0155] This network interface is used for network communication, such as sending assigned tasks. Those skilled in the art will understand that... Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0156] It should be understood that the processor can be a Central Processing Unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among these, a general-purpose processor can be a microprocessor or any conventional processor.

[0157] In addition, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions for performing the steps of the method in the first aspect embodiment.

[0158] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or electronic device described above can be referred to the relevant descriptions in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0159] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0160] It should be understood that although the terms "first," "second," etc., may be used to describe the setting units in the embodiments of this application, these setting units should not be limited to these terms. These terms are only used to distinguish the setting units from each other. For example, without departing from the scope of the embodiments of this application, the first setting unit may also be referred to as the second setting unit, and similarly, the second setting unit may also be referred to as the first setting unit.

[0161] Depending on the context, the word "if" as used here can be interpreted as "when," "when," "in response to determination," or "in response to detection." Similarly, depending on the context, the phrase "if determination" or "if detection (of the stated condition or event)" can be interpreted as "when determination," "in response to determination," "when detection (of the stated condition or event)," or "in response to detection (of the stated condition or event)."

[0162] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0163] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0164] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0165] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A cloud-based collaborative configuration method, characterized in that, The method includes: In response to the user's template selection command, select the target function template corresponding to the target project from the preset function template library; Based on the received template combination rules and the target function template, an initial template combination is performed, and the combined template resources are loaded into the user workspace. Construct a multi-user real-time collaboration channel to perform concurrent control and conflict resolution on configuration editing operations initiated simultaneously by multiple users on the combined template. Real-time synchronization of any user's edits to the combined template to the user workspaces of all collaborating users, and simultaneous recording of operation logs and project version information. In response to receiving a configuration editing completion instruction from the user, a configuration scheme file is generated based on the combined template and the configuration editing operation performed on the combined template; The configuration scheme file is tested, and after the test is passed, the configuration scheme file is stored in a preset database.

2. The method according to claim 1, characterized in that, The method further includes: Real-time monitoring of computing resource utilization, storage resource utilization, data transmission rate, and number of concurrent users during project configuration; When any of the following indicators exceeds a preset threshold: resource utilization rate, storage resource utilization rate, data transmission rate, and number of concurrent users, the computing nodes will be automatically expanded or spare storage resources will be allocated.

3. The method according to claim 1, characterized in that, The method further includes: In response to a user's login request, complete identity authentication and assign corresponding template selection permissions, editing permissions, and data viewing permissions based on the user's identity; The user workspace is initialized based on the project information created by the user, so as to realize the isolated storage and access control of different project data.

4. The method according to claim 1, characterized in that, The creation process of the preset function template library includes: Based on the functional scenarios of industrial automation systems, the system is broken down into multiple functional modules, and the functional boundaries and interface requirements of each module are determined. For each functional module, determine the parameterized configuration structure, preset adjustable parameter items (i.e., parameter value ranges), and formulate parameter validation rules; Define a unified input / output interface, data interaction format, and module calling protocol for all functional templates; Each functional template is tested, and the functional templates that pass the test are classified and stored according to functional type, application scenario and version number. A template retrieval index is established and the template attribute information is entered to obtain the preset functional template library.

5. The method according to claim 1, characterized in that, The template combination rules include at least one of the following: template compatibility verification rules, interface matching rules, and functional module combination priority rules. The project version information includes version number, modification time, modification user, and modification content summary.

6. The method according to claim 1, characterized in that, The concurrency control and conflict resolution include: The configuration editing operations of multiple users are time-sequentially ordered, and optimistic locking is used to mark the template being edited. When a conflicting operation is detected, the latest edited version is retained, and the user who initiated the conflict is prompted to perform a comparative analysis.

7. The method according to claim 1, characterized in that, The preset database adopts a distributed storage architecture to encrypt and back up configuration scheme files, template data, user operation data, and project version information.

8. A cloud-based collaborative configuration device, characterized in that, include: The selection module is used to respond to the user's template selection command and select the target function template corresponding to the target project from the preset function template library; The combination module is used to perform initial template combination according to the received template combination rules and the target function template, and load the combined template resources into the user workspace; The processing module is used to build a multi-user real-time collaboration channel, perform concurrent control and conflict resolution on configuration editing operations initiated by multiple users simultaneously on the combined template, synchronize any user's editing modifications to the combined template to the user workspaces of all collaborating users in real time, and synchronously record operation logs and project version information. The generation module is used to generate a configuration scheme file in response to receiving a configuration editing completion instruction from the user, based on the combined template and the configuration editing operation for the combined template; The storage module is used to test the configuration scheme file and, after the test is passed, store the configuration scheme file in a preset database.

9. A computer device, characterized in that, include: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions executable by the at least one processor, the instructions being configured to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The device stores computer-executable instructions for performing the method as described in any one of claims 1 to 7.

Images