Remote distribution system and remote distribution method

Abstract

The invention discloses a remote distribution system and a remote distribution method, and belongs to the field of automatic production lines. The remote distribution system comprises a centralized management server and a client agent module deployed on production line terminal equipment. And the centralized management server is used for storing a control platform software installation package and a production formula file, generating a distribution task in response to a management instruction, and issuing the distribution task and an associated file to the target production line terminal equipment. The client agent module is in communication connection with the centralized management server and is used for receiving a distribution task, downloading an associated file and calling an operating system authority according to a task type to automatically execute installation updating of a control platform software installation package and / or synchronous deployment of a production formula file; and after the operation is completed, the execution state and the current version information are fed back to the centralized management server. Therefore, the problems of low efficiency, poor consistency and the like caused by the fact that distribution and updating of platforms and formulas in an automatic production line depend on manual one-by-one operation can be solved.

Description

Technical Field

[0001] This application relates to the field of automated production line technology, and in particular to a remote distribution system and remote distribution method. Background Technology

[0002] In discrete manufacturing and process industries, the control of automated production lines relies on control platform software (referred to as "platform") installed on various production line terminals (such as industrial computers, human-machine interfaces, and industrial control computers) and a set of parameters (referred to as "recipes") that define specific production processes. Currently, the distribution and updating of platforms and recipes in automated production lines depend on manual operation on a per-unit basis, resulting in problems such as low efficiency and poor consistency. Summary of the Invention

[0003] This application provides a remote distribution system and a remote distribution method to solve at least one of the aforementioned technical problems.

[0004] The remote distribution system according to the embodiments of this application includes a centralized management server and a client agent module deployed on production line terminal equipment; The centralized management server is used to store the control platform software installation package and production formula files, and generates distribution tasks in response to management instructions, and sends the distribution tasks and associated files to the target production line terminal equipment. The client agent module communicates with the centralized management server, receives the distribution task and downloads the associated file, automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of the production formula file according to the task type and operating system permissions, and reports the execution status and current version information to the centralized management server after the operation is completed.

[0005] In some implementations, the centralized management server includes: A digital asset library is used to store different versions of the control platform software installation packages and their corresponding silent execution scripts, as well as different versions of the production formula files; The equipment management module is used to maintain the registration and grouping information of production line terminal equipment; The task scheduling engine is used to create the distribution task according to the management instructions. The distribution task includes at least one of platform-issued tasks and recipe synchronization tasks, and is responsible for distributing the distribution task and the associated files to the target production line terminal equipment.

[0006] In some implementations, the centralized management server includes a secure communication gateway that establishes a communication connection with the client agent module based on a predetermined encryption protocol to transmit the distribution task and the associated files, and to receive heartbeat packets sent by the client agent module to monitor the online status of the client agent module.

[0007] In some implementations, the distribution task includes a platform-issued task, and the client agent module includes a platform management engine, which is used for: Download the control platform software installation package and the corresponding silent execution script from the centralized management server; The silent execution script is executed by invoking operating system privileges to stop the current service, back up the old version, decompress and install the new version, update the configuration, and restart the service, thereby realizing the installation and update of the control platform software installation package; The platform management engine is also equipped with a rollback mechanism. If the control platform software installation package fails to install, the production line control platform application running on the target production line terminal equipment will be automatically restored to the version before installation.

[0008] In some implementations, the distribution task includes the recipe synchronization task, and the client agent module includes a recipe management engine, which is used for: Download the production formula file from the centralized management server; Back up the currently used formula file and deploy the production formula file to a preset path or database; A reload signal is sent to the production line control platform application running on the target production line terminal device through inter-process communication or application programming interface (API) calls, triggering the production line control platform application to load the production formula file to achieve formula hot switching.

[0009] In some implementations, the distribution task includes a production line cloning task package, which in turn includes a platform-issued task and a recipe synchronization task, and the client agent module includes a platform management engine and a recipe management engine. The platform management engine and the formula management engine are used to invoke operating system permissions to sequentially execute the installation and update of the control platform software installation package and the synchronous deployment of the production formula files.

[0010] In some implementations, the remote distribution system also includes an administrator console; The administrator console is communicatively connected to the centralized management server, providing a visual interactive interface and an operation entry point for triggering the management commands.

[0011] The remote distribution method of this application is applied to a remote distribution system, which includes a centralized management server and a client agent module deployed on production line terminal equipment. The client agent module is communicatively connected to the centralized management server. The remote distribution method includes: The centralized management server stores the control platform software installation package and production formula files; The centralized management server generates a distribution task in response to the management command, and sends the distribution task and associated files to the target production line terminal equipment. The client agent module receives the distribution task and downloads the associated file; The client agent module automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of the production formula file based on the task type and by invoking operating system permissions. After completing the operation, the client agent module reports the execution status and current version information to the centralized management server.

[0012] In some implementations, the distribution task includes a platform-issued task, the client agent module includes a platform management engine, and the client agent module performs the installation and update of the control platform software installation package, including: The platform management engine downloads the control platform software installation package and the corresponding silent execution script from the centralized management server. The platform management engine invokes operating system permissions to execute the silent execution script to stop the current service, back up the old version, decompress and install the new version, update the configuration and restart the service, thereby realizing the installation and update of the control platform software installation package; The platform management engine is also equipped with a rollback mechanism. If the control platform software installation package fails to install, the production line control platform application running on the target production line terminal equipment will be automatically restored to the version before installation.

[0013] In some implementations, the distribution task includes a recipe synchronization task, the client agent module includes a recipe management engine, and the client agent module performs the synchronous deployment of the production recipe file, including: The formula management engine downloads the production formula file from the centralized management server; The formula management engine backs up the currently used formula files and deploys the production formula files to a preset path or database; The formula management engine sends a reload signal to the production line control platform application running on the target production line terminal device through inter-process communication or application programming interface (API) calls, triggering the production line control platform application to load the production formula file to achieve formula hot switching.

[0014] In the remote distribution system and method of this application, the centralized management server generates a distribution task in response to a management command and distributes the distribution task and associated files to the target production line terminal equipment. The client agent module receives the distribution task and downloads the associated files, and automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. This solves the problems of low efficiency and poor consistency caused by manual operation on each machine in automated production lines for platform and formula distribution and updates.

[0015] Additional aspects and advantages of embodiments of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of embodiments of this application. Attached Figure Description

[0016] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein: Figure 1 This is a schematic diagram of the modules of a remote distribution system according to certain embodiments of this application; Figure 2 This is a schematic diagram of the modules of the centralized management server in some embodiments of this application; Figure 3 This is a schematic diagram of a client proxy module according to certain embodiments of this application; Figure 4 This is a flowchart illustrating a remote distribution method according to certain embodiments of this application; Figure 5 This is a schematic diagram of the modules of an electronic device according to certain embodiments of this application; Figure 6 This is a schematic diagram illustrating the connection state between a computer-readable storage medium and a processor according to certain embodiments of this application.

[0017] Explanation of reference numerals in the attached figures: Remote distribution system 1000, centralized management server 100, digital asset library 110, device management module 120, task scheduling engine 130, secure communication gateway 140, client agent module 200, instruction receiver and parser 210, platform management engine 220, recipe management engine 230, status monitoring and reporting device 240, administrator console 300, electronic device 400, processor 410, memory 420, computer-readable storage medium 500, computer program 510, processor 520. Detailed Implementation

[0018] The embodiments of this application will be further described below with reference to the accompanying drawings. The same or similar reference numerals in the drawings denote the same or similar elements or elements having the same or similar functions throughout. Furthermore, the embodiments of this application described below with reference to the accompanying drawings are exemplary and are only used to explain the embodiments of this application, and should not be construed as limiting this application.

[0019] In discrete manufacturing and process industries, the control of automated production lines relies on control platform software (referred to as the "platform") installed on various production line terminals (such as industrial computers, human-machine interfaces, and industrial control computers) and a set of parameters defining specific production processes (referred to as the "recipe"). In related technologies, the management of the platform and the recipe typically employs the following methods: (1) Offline manual copying: Technicians use portable storage devices (such as USB flash drives or portable hard drives) to carry the platform installation package or recipe files to each device site to manually copy, install, or import them. Platform installation usually requires technicians to interactively execute the installation wizard, while recipe updates require manual importing or modification on the device's specific software interface.

[0020] (2) Decentralized management: Each production line, and even each piece of equipment, is an independent information island. There is no unified central node to manage and record the software and recipe versions of all equipment.

[0021] (3) Semi-manual operation based on simple network sharing: Some factories may have set up internal file servers to store platform installation packages or recipe files in network shared folders. However, the operation process still requires technicians to log in to each device, manually access the shared path, and perform download and installation / overwrite operations. In essence, it is still manual operation on a per-device basis and fails to achieve automation.

[0022] The related technologies have the following drawbacks: (1) Extremely low work efficiency: The production line equipment is large in number and geographically dispersed. Technicians need to spend a lot of time traveling back and forth and repeating operations. The platform upgrade or formula switching cycle is long and cannot respond quickly to changes in production needs.

[0023] (2) Version consistency is difficult to guarantee: Since it relies entirely on manual operation, it is very easy to miss, misinstall, or select the wrong version. This leads to inconsistencies in the operating environment of equipment within the same production line or between different production lines, which is a potential risk to cause fluctuations in production quality and abnormal equipment operation.

[0024] (3) Poor traceability: When product quality problems occur, it is difficult to quickly and accurately trace back to the specific platform version and formula version that were running on each piece of equipment when the product was produced, which brings great difficulties to problem location and root cause analysis.

[0025] (4) High dependence on highly skilled personnel: The operation process requires technical personnel to be familiar with the operation procedures of each piece of equipment, resulting in high training costs, and personnel turnover can easily lead to the loss or error of operating procedures.

[0026] (5) High cost and long cycle of new production line deployment and replication: When building or replicating a production line, it is necessary to repeat the platform installation and formula configuration of all equipment, which makes it impossible to quickly clone the software environment and seriously restricts the rapid expansion of production capacity.

[0027] In view of this, the embodiments of this application provide a remote distribution system and a remote distribution method to overcome the problems of low efficiency, poor consistency, and lack of traceability caused by the reliance on manual operation on a machine-by-machine basis for the distribution and updating of platforms and recipes in automated production lines. Specifically, the embodiments of this application can solve the following technical problems: (1) How to achieve remote, batch, and automated installation and upgrade of platform software to a large number of production line terminals.

[0028] (2) How to achieve centralized, one-click, precise synchronization and switching of production formula to designated equipment groups (single or multiple production lines).

[0029] (3) How to ensure that the platform version and recipe version on all target devices remain consistent and meet expectations.

[0030] (4) How to establish a complete version management and operation log system to achieve full-process visual monitoring and traceability.

[0031] (5) How to achieve rapid replication of mature production line software environment to support agile deployment of new production lines.

[0032] Please see Figure 1The remote distribution system 1000 of this application includes a centralized management server 100 and a client agent module 200 deployed on production line terminal equipment. The centralized management server 100 stores the control platform software installation package and production formula files, and generates distribution tasks in response to management instructions, distributing the distribution tasks and associated files to the target production line terminal equipment. The client agent module 200 is communicatively connected to the centralized management server 100, receives distribution tasks and downloads associated files, automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions, and reports the execution status and current version information to the centralized management server 100 after the operation is completed.

[0033] In the remote distribution system 1000 of this application, the centralized management server 100 generates distribution tasks in response to management instructions and distributes the distribution tasks and associated files to the target production line terminal devices. The client agent module 200 receives the distribution tasks and downloads the associated files, and automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. This solves the problems of low efficiency and poor consistency caused by manual operation on each machine in automated production lines for the distribution and updating of platforms and formulas.

[0034] Specifically, the remote distribution system 1000 includes a centralized management server 100 and a client agent module 200 deployed on production line terminal equipment.

[0035] In the embodiments of this application, the centralized management server 100 is used to store the control platform software installation package and production formula files, and generates distribution tasks in response to management instructions, and sends the distribution tasks and associated files to the target production line terminal equipment.

[0036] The centralized management server 100 is the core control node of the remote distribution system 1000. Physically, it can be a high-performance server deployed in the factory data center or a virtual computing instance on a cloud platform, responsible for all management logic and data storage.

[0037] The control platform software installation package can be a compressed archive containing executable files, library files, and dependencies, such as in the `.zip` format; or a standardized installer, such as in the Microsoft Installer (MSI) format.

[0038] A production recipe file is a data file that defines the process flow and parameters for a specific product model. In some embodiments, the production recipe file may be in the format of Extensible Markup Language (XML) or JavaScript Object Notation (JSON).

[0039] Management commands can be issued by authorized users through the administrator console 300 described below. Upon receiving the management command, the centralized management server 100 can generate a structured distribution task. In some embodiments, this distribution task may contain all the information required to execute the task, such as: a unique task identifier, task type (e.g., platform-issued task and / or recipe synchronization task), a list of target production line terminal devices, and the download address and hash checksum of the file to be distributed.

[0040] The centralized management server 100 can push the generated distribution tasks and associated files to the target production line terminal devices through a stable and reliable network communication protocol. Specifically, when the distribution task is a platform-issued task, the associated file can be the control platform software installation package; when the distribution task is a recipe synchronization task, the associated file can be the production recipe file.

[0041] In the embodiments of this application, the client agent module 200 is communicatively connected to the centralized management server 100, and is used to receive and distribute tasks and download associated files, automatically execute the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files according to the task type, and report the execution status and current version information to the centralized management server 100 after the operation is completed.

[0042] The client agent module 200 can be a lightweight, resident program pre-installed on each production line terminal device that needs to be managed, and is responsible for executing the instructions issued by the centralized management server 100.

[0043] In some embodiments, the client agent module 200 can continuously listen for instructions from the centralized management server 100. Once a distribution task is received, the client agent module 200 first parses the task content; then, using the download address provided in the distribution task, it retrieves the associated file from the centralized management server 100; after the download is complete, the client agent module 200 can calculate the hash value of the downloaded file and compare it with the hash check value carried in the distribution task to ensure that the file has not been damaged or tampered with during transmission.

[0044] When the task being distributed is a platform-issued task, the client agent module 200 automatically executes the installation and update of the control platform software installation package by invoking operating system privileges. When the task being distributed is a recipe synchronization task, the client agent module 200 automatically executes the synchronous deployment of the production recipe files by invoking operating system privileges. The above process requires the client agent module 200 to run with an account possessing sufficient system privileges to perform operations such as file writing and service start / stop.

[0045] After completing the above operations, the client agent module 200 sends an execution result report to the centralized management server 100, including the execution status and current version information. The execution status clearly indicates whether the task was successful or failed. If the task fails, the report may include specific error codes or descriptive information to facilitate remote diagnosis. The current version information is the latest version number obtained by the client agent module 200 after the task succeeds by reading the metadata of the local software version file or recipe file. After receiving the above feedback, the centralized management server 100 can also update the records of the corresponding devices, thus forming a complete, closed-loop operation and status monitoring process.

[0046] The above technical solution constructs a remote distribution system 1000 based on a centralized management server 100 and a client agent module 200 architecture. The centralized management server 100 is responsible for the unified storage, management, and distribution of software and recipe update tasks, while the client agent module 200 autonomously and automatically executes these tasks on production line terminal devices and provides result feedback. This remote distribution system 1000 transforms the originally scattered and manual update operations into a centralized and automated process, fundamentally solving the problems of difficulty in ensuring version consistency and low operational efficiency, and providing an efficient and reliable technical foundation for the maintenance of software environments in large-scale industrial production lines.

[0047] Please see Figure 2 In some implementations, the centralized management server 100 includes a digital asset library 110, an equipment management module 120, and a task scheduling engine 130. The digital asset library 110 stores different versions of control platform software installation packages and corresponding silent execution scripts, as well as different versions of production recipe files. The equipment management module 120 maintains the registration and grouping information of production line terminal equipment. The task scheduling engine 130 creates and distributes tasks according to management instructions. These tasks include at least one of platform-issued tasks and recipe synchronization tasks, and it is responsible for distributing the tasks and associated files to the target production line terminal equipment.

[0048] Specifically, the centralized management server 100 includes a digital asset library 110, a device management module 120, and a task scheduling engine 130.

[0049] In the embodiments of this application, the digital asset library 110 is used to store different versions of control platform software installation packages and corresponding silent execution scripts, as well as different versions of production formula files.

[0050] The digital asset repository 110 can be a highly structured storage component within the centralized management server 100, responsible for the unified and versioned management of all file resources related to production line deployment.

[0051] For example, the digital asset library 110 can store different versions of control platform software installation packages and their corresponding silent execution scripts. For each uploaded control platform software installation package, the digital asset library 110 can assign it a unique version identifier and associate it with a silent execution script. This silent execution script can encapsulate some necessary instructions and parameter configurations during the installation process, enabling the installation process to be completed automatically without any manual interaction.

[0052] In some embodiments, the silent execution script can be a PowerShell script for Windows or a Bash script for Linux. The digital asset repository 110 binds and stores the control platform software installation package with its corresponding silent execution script, ensuring that both can be retrieved and distributed together when a task is issued. Furthermore, the silent execution script can be further divided into silent installation scripts and silent uninstallation scripts.

[0053] For example, the digital asset repository 110 can store different versions of production recipe files. When storing, each production recipe file can be associated with metadata, such as the applicable product model, a unique version number, and a file hash checksum, to ensure the integrity and traceability of the files.

[0054] In the embodiments of this application, the device management module 120 is used to maintain the registration information and grouping information of the production line terminal devices.

[0055] Equipment management module 120 is a digital mapping and management center for all managed production line terminal equipment, which is centrally managed by server 100.

[0056] For example, the equipment management module 120 can maintain the registration information of production line terminal equipment. The registration information can be in the form of a registry. Whenever a client agent module 200 on a new production line terminal device establishes a connection with the centralized management server 100 for the first time, it needs to register with the equipment management module 120. The registration information may include the device's unique identifier (ID), IP address, device name, production line / region, and physical location. In addition, the registration information can also record continuously tracked device dynamic information, such as the current platform version, the current activated recipe version, and the device status (online / offline).

[0057] For example, the equipment management module 120 can maintain grouping information for production line terminal equipment. The equipment management module 120 supports administrators in creating equipment groups based on business logic. In some embodiments, the equipment management module 120 can group production line terminal equipment according to welding lines, assembly lines, and testing stations. Equipment grouping capability is a prerequisite for achieving batch and precise task assignment; administrators can operate on a group without having to select equipment individually.

[0058] In the embodiments of this application, the task scheduling engine 130 is used to create distribution tasks according to management instructions. The distribution tasks include at least one of platform-issued tasks and recipe synchronization tasks, and is responsible for distributing the distribution tasks and associated files to the target production line terminal equipment.

[0059] The task scheduling engine 130 is the core logic unit that executes administrator intentions and drives the automated operation of the entire distribution process. When the administrator selects a target production line terminal device (the target range can be specified, which can be a single device, a group of devices, or all devices in the plant; the following explanation uses a group of devices as an example) on the administrator console 300, and specifies a control platform software installation package version or a production recipe file version for distribution, this operation constitutes a management instruction. The task scheduling engine 130 receives this management instruction and transforms it into a specific distribution task. Among them, the platform distribution task instructs the client agent module 200 to perform the platform software installation or update task. The recipe synchronization task instructs the client agent module 200 to perform the production recipe file synchronization and switching task.

[0060] Next, the task scheduling engine 130 queries the device management module 120 to obtain a list of all devices in the selected device group. Then, it retrieves the files required for the task (i.e., associated files, such as the control platform software installation package and its corresponding silent execution script, or production recipe files) from the digital asset library 110. Finally, it pushes the task and associated files to the target production line terminal devices. In addition, the task scheduling engine 130 can also manage the task queue, handle task priority and concurrent execution, etc., to ensure the orderly and efficient distribution process.

[0061] In the above technical solution, by establishing a digital asset library 110, an equipment management module 120, and a task scheduling engine 130, this modular architecture makes the centralized management server 100 functionally clear and highly scalable, providing a solid system foundation for realizing complex and large-scale automated management of production line software.

[0062] Please see Figure 2In some implementations, the centralized management server 100 includes a secure communication gateway 140. The secure communication gateway 140 establishes a communication connection with the client agent module 200 based on a predetermined encryption protocol to transmit and distribute tasks and associated files, and receives heartbeat packets sent by the client agent module 200 to monitor the online status of the client agent module 200.

[0063] Specifically, the secure communication gateway 140 is a key component in the centralized management server 100 that ensures communication security and reliability. It is responsible for handling communication interactions with the client agent module 200 and achieving a stable and efficient long-term connection with the client agent module 200.

[0064] In the embodiments of this application, the secure communication gateway 140 establishes a communication connection with the client agent module 200 based on a predetermined encryption protocol to transmit and distribute tasks and associated files.

[0065] Understandably, to prevent the risk of instructions being eavesdropped on, tampered with, or forged during data transmission, the secure communication gateway 140 restricts communication to an encrypted channel. In some embodiments, the predetermined encryption protocol may be Transport Layer Security (TLS) or Secure Sockets Layer (SSL).

[0066] In some embodiments, when establishing a communication connection, the secure communication gateway 140 and the client agent module 200 also need to perform two-way authentication based on digital certificates. That is, the centralized management server 100 needs to verify the legitimacy of the client agent module 200's certificate, and the client agent module 200 also needs to verify the legitimacy of the centralized management server 100's certificate. Only after both parties' identities are confirmed will an encrypted communication session be established. This mechanism ensures that only authorized client agent modules 200 with pre-installed legitimate certificates can access the centralized management server 100, fundamentally eliminating the risk of unauthorized devices accessing the server.

[0067] Once the encrypted connection is established, all subsequent data, including task distribution and associated files, will be transmitted within this encrypted channel to ensure data transmission security.

[0068] In embodiments of this application, the secure communication gateway 140 also receives heartbeat packets sent by the client agent module 200 to monitor the online status of the client agent module 200.

[0069] A heartbeat is a short data packet that the client agent module 200 actively sends to the secure communication gateway 140 at fixed time intervals. The heartbeat indicates that the client agent module 200 is still online and the network is functioning correctly. In one example, the heartbeat may contain only a unique identifier for the client agent module 200 and a timestamp to minimize network overhead.

[0070] The secure communication gateway 140 internally maintains an online status table for all registered devices (the online status of the client agent module 200, i.e., the online status of the production line terminal devices). Whenever a heartbeat packet is received from a device, the last heartbeat time recorded for that device is updated. Simultaneously, the secure communication gateway 140 can run a periodic check task. This task iterates through the status table, and if it finds that the last heartbeat time of a device exceeds a preset threshold (e.g., multiple consecutive heartbeat cycles), it determines that the device has lost connection or malfunctioned.

[0071] At this time, the secure communication gateway 140 updates the device's status to offline and can synchronize it with other modules of the centralized management server 100 (such as the device management module 120), so that the administrator can understand the device's online / offline status on the administrator console 300 and respond in a timely manner when the device goes offline abnormally.

[0072] In the above technical solution, by introducing a dedicated secure communication gateway 140 into the centralized management server 100, two major challenges faced by the remote distribution system 1000 in an open network environment are solved: communication security and real-time awareness of device status. Encryption protocols and two-way authentication ensure secure transmission of instructions and data, while a heartbeat mechanism enables low-overhead, high-efficiency online status monitoring of a large number of terminal devices, thus constructing a secure and reliable remote control communication foundation.

[0073] Please see Figure 3 In some embodiments, the client agent module 200 includes an instruction receiver and parser 210. The instruction receiver and parser 210 is used to continuously listen for instructions from the centralized management server 100, and to receive and parse task content (such as task type, file download link, execution parameters, etc.).

[0074] Please see Figure 3In some implementations, the distribution task includes a platform-issued task. The client agent module 200 includes a platform management engine 220. The platform management engine 220 is used to: download the control platform software installation package and the corresponding silent execution script from the centralized management server 100; execute the silent execution script by invoking operating system privileges to stop the current service, back up the old version, decompress and install the new version, update the configuration, and restart the service, thereby realizing the installation and update of the control platform software installation package; wherein, the platform management engine 220 is also configured with a rollback mechanism, if the installation of the control platform software installation package fails, it will automatically restore the production line control platform application running on the target production line terminal equipment to the version before installation.

[0075] Specifically, when the task type corresponding to the distribution task received and parsed by the instruction receiver and parser 210 is a platform-issued task, the platform management engine 220 will take over the execution of the subsequent installation and update process of the control platform software installation package. The platform management engine 220 is the core functional unit responsible for handling the lifecycle (installation, update, uninstallation) of the control platform software.

[0076] First, the platform management engine 220 downloads two key files from the centralized management server 100: the control platform software installation package and the corresponding silent execution script. The control platform software installation package contains all the program files for the new version of the software, and the silent execution script is an automation script that strictly corresponds to the version of the installation package; it is crucial for achieving fully automated installation. During the download process, the platform management engine 220 can also verify the integrity of the files to ensure that the downloaded files are not corrupted.

[0077] After the file is downloaded and verified successfully, the platform management engine 220, with system administrator or equivalent privileges, can start and execute the silent execution script. The silent execution script can be configured with a series of automated commands to ensure the stability and reliability of the update process.

[0078] In some embodiments, when the platform management engine 220 executes the silent execution script, it can perform the following operations in sequence: (1) Stop the current service: The first step of the script can send an instruction to the operating system manager to smoothly stop the main service or process of the running old version control platform software to release file usage and prepare for the update. (2) Backup the old version: Before making any modifications, the script can automatically compress and package the entire installation directory or key configuration files of the old version control platform software and store them in a preset backup path. This backup file can be named with a version number and timestamp to provide a basis for possible rollback operations. (3) Decompress and install the new version: The script can execute the decompression and installation commands of the installation package to overwrite the files of the new version in the target installation directory. (4) Update the configuration: If the new version needs to update the configuration files (such as database connection strings), the script can automatically perform the corresponding modification operations. (5) Restart the service: After all files and configurations are updated, the script can restart the service of the control platform software to complete the entire update process.

[0079] By executing the series of standardized operations embedded in the scripts, the platform management engine 220 ensures that the software update process on every terminal device is completely consistent and automated, avoiding errors that may be introduced by human operation.

[0080] To address potential issues during the update process (such as incompatible installation packages, insufficient disk space, or missing dependencies), the Platform Management Engine 220 also includes a built-in rollback mechanism to ensure continuous and stable operation of the production line.

[0081] In some embodiments, the platform management engine 220 can determine whether the installation was successful by monitoring the exit codes of the silently executed scripts. For example, by standard convention, an exit code of 0 indicates success, while any non-zero value is considered an installation failure. Once an installation failure is determined, a rollback mechanism is immediately triggered. The platform management engine 220 can automatically execute a rollback sequence that is the reverse of the installation, such as stopping and uninstalling the newly installed version (if it was partially installed), deleting the new version's files, then extracting the old version's files and configurations from a previously created backup file, restoring them to their original location, and finally restarting the old version's service. This rollback process is also fully automatic and requires no manual intervention.

[0082] This rollback mechanism ensures that even if the upgrade fails, the production line terminal equipment can automatically return to the last stable working state before the upgrade in a short time, thereby minimizing disruption to production.

[0083] In the above technical solution, a dedicated platform management engine 220 is designed for the client agent module 200. This engine achieves a standardized and fully automated software update process by executing a silent execution script bound to the installation package. Furthermore, through a built-in, backup-based automatic rollback mechanism, the robustness and security of remote batch upgrade operations are greatly improved, resolving the production line downtime problem caused by failures during large-scale software upgrades.

[0084] Please see Figure 3 In some implementations, the distribution task includes a formula synchronization task. The client agent module 200 includes a formula management engine 230. The formula management engine 230 is used to: download production formula files from the centralized management server 100; back up currently used formula files and deploy them to a preset path or database; and send a reload signal to the production line control platform application running on the target production line terminal device via inter-process communication or application programming interface (API) calls, triggering the production line control platform application to load the production formula files to achieve hot formula switching.

[0085] Specifically, when the task type corresponding to the distribution task received and parsed by the instruction receiver and parser 210 is a recipe synchronization task, the recipe management engine 230 will take over the process of synchronously deploying the subsequent production recipe files. The recipe management engine 230 is the core functional unit responsible for handling the deployment, backup, and activation of production recipe files.

[0086] First, the formula management engine 230 downloads the production formula file from the centralized management server 100. After the download is complete, the formula management engine 230 can also verify the hash value of the file to ensure that no data errors occurred during the transmission of the production formula file, thereby guaranteeing the accuracy of subsequent production process parameters.

[0087] Once the recipe file is verified to be correct, the recipe management engine 230 can execute a secure deployment process to ensure the reversibility of the operation and the integrity of the data.

[0088] (1) Before overwriting an old recipe with a new one, the recipe management engine 230 can locate the recipe file currently being used by the production line control platform application, then copy or rename the file, append information such as version number and timestamp, and save it as a backup copy. This step ensures that the recipe can be quickly restored to the previous stable state under any circumstances.

[0089] (2) Deploy the production formula file to a preset path or database. The deployment method may depend on the formula loading mechanism of the production line control platform application.

[0090] In some embodiments, the production line control platform application reads the recipe from a fixed file path (e.g., `D:\Configs\CurrentRecipe.xml`). The recipe management engine 230 then copies the newly downloaded recipe file to that path, replacing the existing file.

[0091] In other embodiments, the production line control platform application reads recipe parameters from a database. At this time, the recipe management engine 230 connects to the specified database and executes Structured Query Language (SQL) commands to update or insert data, writing the parameters of the new recipe into the corresponding tables.

[0092] (3) Send a reload signal to the production line control platform application running on the target production line terminal device through inter-process communication or application interface call, triggering the production line control platform application to load the production formula file to achieve formula hot switching.

[0093] It is understandable that simply replacing the aforementioned files or updating the database is insufficient; it is also necessary to proactively notify the running production line control platform application to load the new recipe. This is the key to achieving hot recipe switching (i.e., updating process parameters without interrupting production or restarting the application).

[0094] After deploying the production formula file, the formula management engine 230 can send a reload configuration signal to the control platform application through a pre-agreed communication mechanism. This communication mechanism can be inter-process communication (IPC) or application programming interface (API) calls.

[0095] The production line control platform application can be internally designed with a listener for overload signals. Once the signal is received, its internal recipe loading logic is immediately executed, retrieving the latest recipe parameters from the preset path or database and applying them to the current production process.

[0096] Through the aforementioned proactive notification mechanism, formula switching can be completed instantly, greatly improving the production line's flexibility and response speed to changes in production plans.

[0097] In the above technical solution, a dedicated recipe management engine 230 is designed for the client agent module 200. This engine not only enables secure backup and deployment of recipe files, but also establishes a direct notification link from deployment to application response through inter-process communication or API calls. This mechanism successfully solves the technical challenge of seamlessly and in real-time updating of production recipes during continuous production line operation, providing strong technical support for flexible manufacturing and rapid product changeover.

[0098] Please see Figure 3 In some implementations, the distribution task includes a production line cloning task package. The production line cloning task package also includes platform-issued tasks and recipe synchronization tasks. The client agent module 200 includes a platform management engine 220 and a recipe management engine 230. The platform management engine 220 and the recipe management engine 230 are used to invoke operating system privileges to sequentially execute the installation and update of the control platform software installation package and the synchronous deployment of production recipe files.

[0099] Specifically, a production line cloning task package is a composite task type that aims to quickly and completely configure one or more production line terminal devices (which may be brand new, unconfigured devices, or devices that need to be restored to a standard state) into a predefined, standard device that can be put into production immediately.

[0100] The production line cloning task package includes both platform-issued tasks and formula synchronization tasks. It should be noted that the detailed schemes for the platform management engine 220 to install and update the control platform software installation package and the formula management engine 230 to synchronously deploy production formula files, as described in the aforementioned embodiments, are also applicable to the embodiments of this application and will not be elaborated upon here. The difference lies in that, in the embodiments of this application, the platform management engine 220 and the formula management engine 230 sequentially execute the installation and update of the control platform software installation package and the synchronous deployment of production formula files. Thus, the composite task is executed in sequence to ensure the logical correctness and compatibility of the system configuration. Because in industrial practice, the format and content of production formula files are often compatible with specific versions of the control platform software, it is necessary to ensure the correct software environment before deploying the corresponding formula, avoiding production anomalies or equipment failures that may result from software version incompatibility with the formula.

[0101] In the above technical solution, a rigorous and serialized collaborative workflow was designed among multiple engines within the client agent module 200 for the production line cloning task package. This mechanism solves the complex operation problem of configuring a production line device from scratch or restoring the device to a standard baseline. It packages multiple independent steps into a highly cohesive operation, ensuring the integrity of the deployment and the correctness of version compatibility, and greatly improving the efficiency and reliability of new production line deployment and standardized production line maintenance.

[0102] Please see Figure 3 In some embodiments, the client agent module 200 includes a status monitoring and reporting device 240. The status monitoring and reporting device 240 can be used to periodically collect the device's health information (CPU, memory usage), control platform software installation package version information, and production formula document version information. The status monitoring and reporting device 240 can also periodically report the above information to the centralized management server 100; and after the task is completed, it immediately reports the task execution result to the centralized management server 100, including whether the task was successful or failed, and if it failed, it further reports the reason for the failure.

[0103] Please see Figure 1 In some implementations, the remote distribution system 1000 also includes an administrator console 300. The administrator console 300 is communicatively connected to the centralized management server 100 and provides a visual interactive interface as well as an operation entry point for triggering management commands.

[0104] Specifically, this embodiment adds a human-computer interaction layer for administrators, namely the administrator console 300, to the system architecture of the centralized management server 100 and the client agent module 200. The administrator console 300 serves as the command and monitoring center of the remote distribution system 1000.

[0105] In the embodiments of this application, the administrator console 300 is communicatively connected to the centralized management server 100.

[0106] The administrator console 300 can be a web-based application. Authorized administrators can access and operate the administrator console 300 from any location via a web browser. The administrator console 300 and the centralized management server 100 can communicate securely via an application programming interface (API, such as a RESTful API) based on Hypertext Transfer Protocol (HTTPS) to ensure the security of management operations.

[0107] In the embodiments of this application, the administrator console 300 provides a visual interactive interface that presents the complex underlying system status and data to the user in an intuitive and easy-to-understand graphical manner. For example, the visual interactive interface has the following functions: providing a dashboard that can visually display device online rate, task success rate, and version distribution; providing an interface for uploading or deleting platform packages and recipes, and editing their metadata; providing a drag-and-drop or point-and-click interface to facilitate users in creating and managing assigned tasks, while also displaying task progress bars and the execution status of each device in real time; and providing complete operation logs, audit trails, and version history query functions.

[0108] In embodiments of this application, the administrator console 300 may also provide an operation entry point for triggering management commands. Through this operation entry point, the administrator can convert management intentions into executable management command inputs, and then the administrator console 300 will send the management commands to the centralized management server 100.

[0109] In the above technical solution, the introduction of the administrator console 300 provides a centralized, visual, and controllable management entry point for the automated remote distribution system 1000. Production line managers can easily, accurately, and securely execute large-scale software and recipe distribution tasks, greatly reducing the barrier to entry for the system and improving management efficiency and operational standardization.

[0110] Please see Figures 1 to 3 The workflow of the remote distribution system 1000 according to the embodiments of this application will be described below with reference to specific examples.

[0111] (1) Platform distribution process: The administrator logs into the administrator console 300 and uploads the control platform software installation package Platform_v2.1.0.zip and the corresponding silent execution script install_v2.1.0.ps1 to the digital asset library 110.

[0112] In the administrator console 300, the administrator selects all terminal devices of "Production Line A" to create a platform-issued task (in the form of a management command).

[0113] The task scheduling engine 130 pushes the tasks and associated files issued by the platform to all online client agent modules 200 of "Production Line A".

[0114] Download the client agent module 200 control platform software installation package Platform_v2.1.0.zip and the corresponding silent execution script install_v2.1.0.ps1, and call PowerShell to execute the silent execution script install_v2.1.0.ps1.

[0115] The script executes silently to complete the installation automatically. After the client agent module 200 restarts the production line control platform application, it reports the new version v2.1.0 to the centralized management server 100.

[0116] The administrator can see in real time on the administrator console that the status of all terminal devices has changed to "v2.1.0-Running".

[0117] (2) Formula synchronization process The administrator logs into the administrator console 300 and uploads the production recipe file Recipe_ModelX_v1.5.xml to the digital asset library 110.

[0118] The administrator creates a recipe synchronization task in the administrator console 300, with the target production line terminal devices being all terminal devices of "Production Line B" and "Production Line C".

[0119] The client agent module 200 downloads the production recipe file Recipe_ModelX_v1.5.xml, copies it to the D:\ProgramData\LineConfig\ directory, and renames the old recipe Recipe_ModelY_v1.4.xml to a backup file.

[0120] The client agent module 200 sends a "ConfigReload" signal to the production line control platform application through a predefined TCP port or a local API.

[0121] After receiving the "ConfigReload" signal, the production line control platform application reloads the production recipe file under D:\ProgramData\LineConfig\ to complete the recipe switch.

[0122] The client agent module 200 reported that the activation recipe file has been changed to ModelX_v1.5.

[0123] (3) Production line cloning process: The administrator registers all terminal devices for the new production line "Production Line D" in the device management module 120.

[0124] The administrator creates a production line cloning task package in the administrator console (300). This task package contains: A platform issues a task: pointing to the Platform_v2.1.0 installation package of the control platform software currently used by the "standard production line".

[0125] A recipe synchronization task: points to the production recipe file Recipe_ModelX_v1.5 currently used by the "Standard Production Line".

[0126] The production line cloning task package is distributed to all online client agent modules 200 of "Production Line D".

[0127] The client agent module 200 of "Production Line D" will automatically and sequentially install and update the control platform software installation package and synchronously deploy the production formula files, and within a few hours it will have software and production environment completely consistent with the "Standard Production Line".

[0128] In summary, the remote distribution system 1000 of this application has at least the following innovative features: (1) System architecture: The remote distribution system 1000 for production line platform and formula distribution is composed of a centralized management server 100, a client agent module 200, and an administrator console 300.

[0129] (2) Silent installation and automatic rollback mechanism: The client agent module 200 achieves fully automatic installation by executing the silent execution script associated with the control platform software installation package, and automatically rolls back to the previous stable state when the installation fails.

[0130] (3) Hot switching and notification mechanism of formula: After deploying a new formula, the client agent module 200 actively notifies the production line control platform application to reload the production formula file through inter-process communication or API call to achieve seamless switching of formula.

[0131] (4) Combination Tasks and Production Line Cloning: By creating a combination task or task package that includes platform-issued tasks and recipe synchronization tasks, and issuing it to the new equipment group with one click, the entire production line software environment can be quickly copied.

[0132] (5) End-to-end status tracking: Provides a visual monitoring and logging mechanism for the entire process from task creation, distribution, client execution to final status reporting, ensuring the traceability of operations.

[0133] The remote distribution system 1000 according to the embodiments of this application has at least the following beneficial effects: (1) Revolutionary efficiency improvement: The manual operation of each machine is transformed into automated batch processing, which improves the efficiency of platform deployment and formula update by several orders of magnitude, shortening the time from "person-day / person-week" to "minute", greatly freeing up human resources.

[0134] (2) Ensure absolute consistency: By centrally managing the server 100 to uniformly distribute version files, the problem of version inconsistency caused by human error is fundamentally eliminated, providing a key guarantee for the stability of production quality.

[0135] (3) Achieve full traceability: All operations are recorded and the version history is clearly traceable, establishing a complete data chain from product to production software environment, meeting the stringent requirements of high-end manufacturing industry for quality traceability and compliance.

[0136] (4) Improve system robustness: The automated rollback mechanism and backup strategy reduce the risk of production line downtime due to upgrade failure and enhance the stability and reliability of the entire production system.

[0137] (5) Enable flexible manufacturing: Supports rapid and accurate synchronization of formulas across production line equipment groups, enabling enterprises to respond quickly to changes in production plans and easily achieve a flexible production mode with multiple varieties and small batches.

[0138] (6) Lowering the technical threshold and total cost of ownership: The operation process is simplified, and the technical requirements for front-line operators are reduced. At the same time, the rapid production line cloning capability significantly shortens the deployment cycle of new production lines and reduces overall operating and expansion costs.

[0139] Please see Figures 1 to 4 The remote distribution method of this application is applied to a remote distribution system 1000. The remote distribution system 1000 includes a centralized management server 100 and client agent modules 200 deployed on production line terminal equipment. The client agent modules 200 are communicatively connected to the centralized management server 100. The remote distribution method includes: S10: Centralized management server 100 storage control platform software installation package and production formula documents; S20: The centralized management server 100 responds to management commands by generating distribution tasks and sending the distribution tasks and associated files to the target production line terminal devices; S30: Client agent module 200 receives the distribution task and downloads the associated file; S40: The client agent module 200 automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. S50: After the operation is completed, the client agent module 200 reports the execution status and current version information to the centralized management server 100.

[0140] In some implementations, the distribution task includes a platform-issued task. The client agent module 200 includes a platform management engine 220. The client agent module 200 performs the installation and update of the control platform software installation package, including: The platform management engine 220 downloads the control platform software installation package and the corresponding silent execution script from the centralized management server 100; The platform management engine 220 calls the operating system privileges to execute a silent script to stop the current service, back up the old version, decompress and install the new version, update the configuration and restart the service, thereby controlling the installation and update of the platform software installation package; The platform management engine 220 is also equipped with a rollback mechanism. If the control platform software installation package fails to install, the production line control platform application running on the target production line terminal equipment will be automatically restored to the version before installation.

[0141] In some implementations, the distribution task includes a recipe synchronization task. Client agent module 200 includes recipe management engine 230. Client agent module 200 performs the synchronous deployment of production recipe files, including: Formula management engine 230 downloads production formula files from centralized management server 100; The recipe management engine 230 backs up the currently used recipe files and deploys the production recipe files to a preset path or database; The recipe management engine 230 sends a reload signal to the production line control platform application running on the target production line terminal device through inter-process communication or application programming interface calls, triggering the production line control platform application to load the production recipe file to achieve hot recipe switching.

[0142] In some implementations, the distribution task includes a production line cloning task package. The production line cloning task package includes both platform-issued tasks and recipe synchronization tasks. The client agent module 200 includes a platform management engine 220 and a recipe management engine 230. The client agent module 200 invokes operating system privileges to automatically execute the installation and update of the control platform software installation package and the synchronous deployment of production recipe files, including: Platform management engine 220 and formula management engine 230 invoke operating system permissions to sequentially execute the installation and update of the control platform software installation package and the synchronous deployment of production formula files.

[0143] It should be noted that the explanation of the remote distribution system 1000 in the foregoing embodiments also applies to the remote distribution method in the embodiments of this application, and will not be elaborated here.

[0144] Please see Figure 5 The electronic device 400 of this application includes one or more processors 410 and a memory 420, wherein the memory 420 stores a computer program. When the computer program is executed by the processor 410, the remote distribution method of any of the above embodiments is implemented.

[0145] For example, when a computer program is executed by processor 410, the following remote distribution method is implemented: S10: Centralized management server 100 storage control platform software installation package and production formula documents; S20: The centralized management server 100 responds to management commands by generating distribution tasks and sending the distribution tasks and associated files to the target production line terminal devices; S30: Client agent module 200 receives the distribution task and downloads the associated file; S40: The client agent module 200 automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. S50: After the operation is completed, the client agent module 200 reports the execution status and current version information to the centralized management server 100.

[0146] It should be noted that the explanation of the remote distribution method in the foregoing embodiments also applies to the electronic device 400 of the embodiments of this application, and will not be elaborated here.

[0147] Please see Figure 6 The computer-readable storage medium 500 of this application embodiment stores a computer program 510 thereon. When the program is executed by the processor 520, it implements the remote distribution method of any of the above embodiments.

[0148] For example, when the program is executed by processor 520, the following remote distribution method is implemented: S10: Centralized management server 100 storage control platform software installation package and production formula documents; S20: The centralized management server 100 responds to management commands by generating distribution tasks and sending the distribution tasks and associated files to the target production line terminal devices; S30: Client agent module 200 receives the distribution task and downloads the associated file; S40: The client agent module 200 automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. S50: After the operation is completed, the client agent module 200 reports the execution status and current version information to the centralized management server 100.

[0149] It should be noted that the explanation of the remote distribution method in the foregoing embodiments also applies to the computer-readable storage medium 500 in the embodiments of this application, and will not be elaborated here.

[0150] In summary, in the remote distribution system 1000, remote distribution method, electronic device 400, and computer-readable storage medium 500 of this application, the centralized management server 100 generates distribution tasks in response to management instructions and distributes the distribution tasks and associated files to the target production line terminal devices. The client agent module 200 receives the distribution tasks and downloads the associated files, and automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of production formula files based on the task type and operating system permissions. This solves the problems of low efficiency and poor consistency caused by manual operation on each machine in automated production lines for platform and formula distribution and updates.

[0151] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0152] Any process or method described in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the function involved, as will be understood by those skilled in the art to which embodiments of this application pertain.

[0153] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable storage medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, a computer-readable storage medium can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and programmable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable storage medium could be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0154] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0155] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it includes one or a combination of the steps of the method embodiments. Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc.

[0156] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application, the scope of which is defined by the claims and their equivalents.

Claims

1. A remote distribution system, characterized in that, This includes a centralized management server and a client agent module deployed on production line terminal equipment; The centralized management server is used to store the control platform software installation package and production formula files, and generates distribution tasks in response to management instructions, and sends the distribution tasks and associated files to the target production line terminal equipment. The client agent module communicates with the centralized management server, receives the distribution task and downloads the associated file, automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of the production formula file according to the task type and operating system permissions, and reports the execution status and current version information to the centralized management server after the operation is completed.

2. The remote distribution system according to claim 1, characterized in that, The centralized management server includes: A digital asset library is used to store different versions of the control platform software installation packages and corresponding silent execution scripts, as well as different versions of the production formula files; The equipment management module is used to maintain the registration and grouping information of production line terminal equipment; The task scheduling engine is used to create the distribution task according to the management instructions. The distribution task includes at least one of platform-issued tasks and recipe synchronization tasks, and is responsible for distributing the distribution task and the associated files to the target production line terminal equipment.

3. The remote distribution system according to claim 1, characterized in that, The centralized management server includes a secure communication gateway, which establishes a communication connection with the client agent module based on a predetermined encryption protocol to transmit the distribution task and the associated file, and receives heartbeat packets sent by the client agent module to monitor the online status of the client agent module.

4. The remote distribution system according to claim 2, characterized in that, The distribution task includes the platform-issued task, and the client agent module includes a platform management engine, which is used for: Download the control platform software installation package and the corresponding silent execution script from the centralized management server; The silent execution script is executed by invoking operating system privileges to stop the current service, back up the old version, decompress and install the new version, update the configuration, and restart the service, thereby realizing the installation and update of the control platform software installation package; The platform management engine is also equipped with a rollback mechanism. If the control platform software installation package fails to install, the production line control platform application running on the target production line terminal equipment will be automatically restored to the version before installation.

5. The remote distribution system according to claim 2, characterized in that, The distribution task includes the recipe synchronization task, and the client agent module includes a recipe management engine, which is used for: Download the production formula file from the centralized management server; Back up the currently used formula file and deploy the production formula file to a preset path or database; A reload signal is sent to the production line control platform application running on the target production line terminal device through inter-process communication or application programming interface (API) calls, triggering the production line control platform application to load the production formula file to achieve formula hot switching.

6. The remote distribution system according to claim 1, characterized in that, The distribution task includes a production line cloning task package, which includes both platform-issued tasks and recipe synchronization tasks. The client agent module includes a platform management engine and a recipe management engine. The platform management engine and the formula management engine are used to invoke operating system permissions to sequentially execute the installation and update of the control platform software installation package and the synchronous deployment of the production formula files.

7. The remote distribution system according to any one of claims 1-6, characterized in that, The remote distribution system also includes an administrator console; The administrator console is communicatively connected to the centralized management server, providing a visual interactive interface and an operation entry point for triggering the management commands.

8. A remote distribution method, characterized in that, The method is applied to a remote distribution system, which includes a centralized management server and client agent modules deployed on production line terminal equipment. The client agent modules are communicatively connected to the centralized management server. The centralized management server stores the control platform software installation package and production formula files; The centralized management server generates a distribution task in response to the management command, and sends the distribution task and associated files to the target production line terminal equipment. The client agent module receives the distribution task and downloads the associated file; The client agent module automatically executes the installation and update of the control platform software installation package and / or the synchronous deployment of the production formula file based on the task type and by invoking operating system permissions. After completing the operation, the client agent module reports the execution status and current version information to the centralized management server.

9. The remote distribution method according to claim 8, characterized in that, The distribution task includes platform-issued tasks, the client agent module includes a platform management engine, and the client agent module executes the installation and update of the control platform software installation package, including: The platform management engine downloads the control platform software installation package and the corresponding silent execution script from the centralized management server. The platform management engine invokes operating system permissions to execute the silent execution script to stop the current service, back up the old version, decompress and install the new version, update the configuration and restart the service, thereby realizing the installation and update of the control platform software installation package; The platform management engine is also equipped with a rollback mechanism. If the control platform software installation package fails to install, the production line control platform application running on the target production line terminal equipment will be automatically restored to the version before installation.

10. The remote distribution method according to claim 8, characterized in that, The distribution task includes a recipe synchronization task, and the client agent module includes a recipe management engine. The client agent module executes the synchronous deployment of the production recipe file, including: The formula management engine downloads the production formula file from the centralized management server; The formula management engine backs up the currently used formula files and deploys the production formula files to a preset path or database; The formula management engine sends a reload signal to the production line control platform application running on the target production line terminal device through inter-process communication or application programming interface (API) calls, triggering the production line control platform application to load the production formula file to achieve formula hot switching.

Images