CN116886691A

CN116886691A - File management control method, device, system and storage medium

Info

Publication number: CN116886691A
Application number: CN202311153984.2A
Authority: CN
Inventors: 陈运华; 刘竹军; 谢高强; 孟庆振; 卢山
Original assignee: Lansi System Integration Co ltd
Current assignee: Lansi System Integration Co ltd
Priority date: 2023-09-08
Filing date: 2023-09-08
Publication date: 2023-10-13
Anticipated expiration: 2043-09-08
Also published as: CN116886691B

Abstract

The invention provides a file management control method, a device, a system and a storage medium, which relate to the technical field of file synchronization and comprise the following steps: acquiring management task information and confirming target equipment to be operated in batches and task types; generating task execution information based on task data corresponding to management task information according to the task type; and establishing communication connection with the target equipment based on the task execution information and executing task data of the task execution information. The invention improves the transmission efficiency, realizes the transmission safety, reduces the transmission error probability, obviously lightens the working intensity of operators, can realize remote checking, management, batch operation and batch transmission of related files, and obviously improves the production efficiency, thereby ensuring that the file management becomes orderly, the file transmission is efficient and safe, simultaneously reduces the production cost and realizes the cost reduction and synergy for enterprises.

Description

File management control method, device, system and storage medium

Technical Field

The present invention relates to the field of file synchronization technologies, and in particular, to a method, an apparatus, a system, and a storage medium for file management control.

Background

The equipment files, such as production and processing files, are generated by computer programs and used for controlling the machine equipment to carry out production, generally mainly comprise information such as processing programs, tool paths, processing parameters, process flows and the like, and can help operators to send instructions to the machine equipment in the production process so as to realize production tasks such as processing, assembling and assembling of parts. The production and processing files can not only improve the automation degree of the production process of the machine equipment, but also better control the processing precision and quality, and reduce the production error and loss.

In the manufacturing industry, the equipment production processing file becomes an indispensable part in the intelligent manufacturing process, and in order to ensure the precision, accuracy and real-time performance of product processing, the production processing file is often required to be quickly and reliably transmitted to corresponding processing equipment in production, so that the processing equipment can quickly and accurately process high-quality products according to the equipment production processing file.

The main transmission management modes at present comprise the following steps:

(1) Transmission via a removable storage medium: and copying and storing the production and processing files into the mobile storage medium by using the mobile storage medium, such as a USB flash disk, a mobile hard disk and the like, carrying the production and processing files to a production equipment site, inserting the mobile storage medium into processing equipment, and copying the production and processing files in the storage medium into a system catalog corresponding to the machine equipment. The method is simple to operate, but needs technicians to go to a production workshop to copy the copies on a device-by-device basis, and has long operation time and low working efficiency. In addition, the file management is difficult, the copied file is damaged or the copied file version is wrongly out of date easily caused by negligence, and the workload of all updating once is large under the condition of more devices. For the scene with high confidentiality of the product, the information security risk is easy to occur, and the product information is easy to leak;

(2) Pulling from a file server through a network at a processing equipment end: the enterprise uploads the production and processing files to a file server (such as a file sharing server, an FTP file server, a dedicated file server of equipment and the like), and sets access rights, and the machine equipment accesses the file server through a network, so that the production and processing files can be downloaded from the server to a system directory corresponding to the machine equipment. In the method, a technician is required to go to a production workshop site to operate the production and processing files from a file server to machine equipment, so that the operation time is long and the working efficiency is low. The file server side is difficult to manage due to different conditions of supporting file servers by equipment of different manufacturers, and file servers (such as a file sharing server, an FTP file server, a dedicated file server of equipment and the like) in various modes are required to be built.

In summary, the transmission management in the management mode of the existing equipment production process file for producing and manufacturing equipment is an important link in the whole production process, and is also a key step of directly interacting with the equipment. The management and the transmission of the existing production files mainly adopt a manual operation mode and a one-by-one operation process, the labor intensity is high, the working efficiency is low, the equipment and file management difficulty is high, the safety and confidentiality of the transmission process cannot be guaranteed, the operation errors are easy to occur, the production quality of products is influenced, and therefore the production cost is increased.

Disclosure of Invention

In view of the above, the present invention provides a file management control method, which includes:

acquiring management task information, and confirming target equipment to be operated in batches and corresponding task types according to the management task information;

generating task execution information aiming at the target equipment based on task data corresponding to the management task information according to the task type;

and establishing communication connection with each target device based on the task execution information, and executing the task data corresponding to the task execution information.

Preferably, the generating task execution information for the target device based on the task data corresponding to the management task information according to the task type includes:

based on the task type, determining directory information and/or file information corresponding to the target equipment to be batched operated according to the management task information; and writing the catalog information and/or the file information and the task type into the task execution information.

Preferably, the task type is based, and directory information and/or file information corresponding to each target device to be batched are determined according to the management task information; and writing the catalog information and/or file information and the task type into the task execution information, wherein the method comprises the following steps:

Determining directory information and/or file information corresponding to the target equipment according to the management task information, taking the directory information and/or the file information as task log detail data, and writing the task log detail data into an execution log table;

packaging an execution log table corresponding to the target equipment into one message data in an MQ message queue;

the message data is sent to a theme in the MQ message queue, and a task ID corresponding to the management task information is put into an execution progress monitoring list;

inquiring the completion condition of the corresponding task in the execution log table according to the task ID, and counting the total number, the completed number and the failure number of the tasks corresponding to the task ID;

judging whether the completed number is not smaller than the total number of tasks;

if yes, removing the task corresponding to the task ID from the progress monitoring list;

if not, returning to execute the completion condition of the corresponding task in the execution log table according to the task ID, and counting the total number, the completed number and the failure number of the tasks corresponding to the task ID.

Preferably, the establishing a communication connection with each target device based on the task execution information and executing the task data corresponding to the task execution information includes:

Acquiring the task execution information, analyzing the task execution information, and establishing communication connection with the target equipment according to the task execution information;

and carrying out data processing on task data on the target equipment according to the task execution information based on the task type.

Preferably, the obtaining the task execution information and analyzing the task execution information, and establishing a communication connection with the target device according to the task execution information, includes:

analyzing the task execution information to obtain the equipment identifier of the target equipment;

acquiring file transmission protocol information and configuration information corresponding to the target equipment according to the equipment identifier;

and establishing communication connection with the target equipment according to the file transfer protocol information and the configuration information.

Preferably, the data processing of the task data on the target device according to the task execution information based on the task type includes:

judging whether the task type is an issuing task or not;

if the task type is a delivery task, creating a target directory corresponding to a delivery file on the target device based on file transfer protocol information and configuration information of the target device;

And acquiring a file stream from a file server, and writing the file in the file stream into the target directory corresponding to the target device.

Preferably, after determining whether the task type is a task to be issued, the method further includes:

if the task type is not the issuing task, judging that the task type is a deleting task, and determining a corresponding target directory and/or a target file based on the task execution information;

and deleting the target directory and/or the target file on the target equipment according to the file transmission protocol information and the configuration information of the target equipment.

Preferably, the file management control method further includes:

receiving a device newly-added instruction, and judging whether a system end supports the transmission protocol type of corresponding amplification device according to the device newly-added instruction;

if the system end supports the transmission protocol type, saving the equipment identifier, the equipment name and the transmission protocol type which are confirmed to be supported by the amplification equipment as configuration information corresponding to the amplification equipment;

if the system end does not support the transmission protocol type, executing a transmission protocol expansion flow for the amplification equipment, returning to execute the new instruction of the receiving equipment, and judging whether the system end supports the transmission protocol type of the corresponding amplification equipment according to the new instruction of the equipment.

Preferably, the transmission protocol extension procedure includes:

acquiring transmission protocol definition information corresponding to the amplification equipment;

and establishing a transmission protocol and protocol information storage model corresponding to the amplification equipment according to the transmission protocol definition information, and performing code adaptation expansion according to the transmission protocol.

In addition, in order to solve the above problems, the present invention also provides a file management control apparatus, including:

the confirmation module is used for acquiring management task information and confirming target equipment to be operated in batches and corresponding task types according to the management task information;

the generation module is used for generating task execution information aiming at the target equipment based on task data corresponding to the management task information according to the task type;

and the execution module is used for establishing communication connection with each target device based on the task execution information and executing the task data corresponding to the task execution information.

In addition, in order to solve the above-mentioned problem, the present invention also provides a file management control system, which includes a memory and a processor, wherein the memory stores a file management control program, and the processor runs the file management control program to make the file management control system execute the file management control method as described above.

In addition, in order to solve the above-mentioned problems, the present invention also provides a computer-readable storage medium having stored thereon a file management control program which, when executed by a processor, implements the file management control method as described above.

The invention provides a file management control method, a device, a system and a storage medium, wherein the method comprises the following steps: acquiring management task information, and confirming target equipment to be operated in batches and corresponding task types according to the management task information; generating task execution information aiming at the target equipment based on task data corresponding to the management task information according to the task type; and establishing communication connection with each target device based on the task execution information, and executing the task data corresponding to the task execution information.

According to the invention, after the target equipment is determined, the task execution information is generated through the task type, and the communication connection with the target equipment is established according to the task execution information, so that task data corresponding to the task execution information is executed, the simplified transmission operation of a task automatic management mode is formed, the transmission efficiency and the transmission safety are improved, the transmission error probability is reduced, the working intensity of operators is remarkably reduced, the remote checking, management, batch operation and batch transmission of files on the machine equipment are realized, and the production efficiency, the processing precision and the production quality are remarkably improved, thereby ensuring that the file management becomes orderly, the file transmission is efficient and safe, the production cost is reduced, and the cost and the efficiency of an enterprise are reduced.

Drawings

FIG. 1 is a schematic diagram of a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a flowchart of an embodiment 1 of a file management control method according to the present invention;

FIG. 3 is a flowchart of an embodiment 2 of a file management control method according to the present invention;

FIG. 4 is a flowchart illustrating the refinement of step S210 in embodiment 2 of the file management control method according to the present invention;

FIG. 5 is a flowchart illustrating a refinement of step S300 in the 3 rd embodiment of the file management control method according to the present invention;

FIG. 6 is a flowchart illustrating a refinement of step S310 in embodiment 3 of the file management control method according to the present invention;

FIG. 7 is a flowchart illustrating the refinement of step S320 in embodiment 3 of the file management control method according to the present invention;

FIG. 8 is a flowchart of a complementary scheme including steps S400-S600 in embodiment 4 of the file management control method of the present invention;

FIG. 9 is a flowchart illustrating a refinement of step S600 in the embodiment 4 of the file management control method according to the present invention;

FIG. 10 is a schematic diagram showing the connection of modules of a file management control device according to the present invention;

FIG. 11 is a schematic diagram illustrating a module connection of the file management control system according to the present invention.

The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

Embodiments of the present invention are described in detail below, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present invention, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

In the present invention, unless explicitly specified and limited otherwise, the terms "mounted," "connected," "secured," and the like are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communicated with the inside of two elements or the interaction relationship of the two elements. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.

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

Fig. 1 is a schematic structural diagram of a hardware operating environment of a terminal according to an embodiment of the present invention.

The file management control system of the embodiment of the invention can be a PC, a mobile terminal device such as a smart phone, a tablet computer or a portable computer, and the like. The file management control system may include: a processor 1001, e.g. a CPU, a network interface 1004, a user interface 1003, a memory 1005 and a communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a display screen, an input unit such as a keyboard, a remote control, and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a stable memory such as a disk memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above. Optionally, the file management control system may further include an RF (Radio Frequency) circuit, an audio circuit, a WiFi module, and the like. In addition, the file management control system can be further configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor and the like, which are not described herein.

Those skilled in the art will appreciate that the file management control system shown in FIG. 1 is not limiting and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

The file management control system of the invention is not limited in application field, and can be suitable for production and processing file management, office file management and the like. As shown in fig. 1, an operating system, a data interface control program, a network connection program, and a file management control program may be included in a memory 1005 as one type of computer-readable storage medium.

In a word, the invention generates task execution information through the task type after determining the target equipment, establishes communication connection with the target equipment according to the task execution information, executes task data corresponding to the task execution information, forms simplified transmission operation of a task automatic management mode, improves transmission efficiency and transmission safety, reduces transmission error probability, obviously reduces working intensity of operators, realizes remote checking, management, batch operation and batch transmission of files on machine equipment, and obviously improves production efficiency, processing precision and production quality, thereby ensuring that file management becomes orderly, file transmission is efficient and safe, simultaneously reduces production cost, and realizes cost reduction and synergy for enterprises.

In order to better explain the present invention, the following will illustrate production process file management, but is not intended to limit the present invention.

Example 1:

referring to fig. 2, an embodiment of the present invention provides a file management control method, including:

step S100, acquiring management task information, and confirming target equipment to be operated in batches and corresponding task types according to the management task information;

the embodiment can be applied to a system end and at least one target device connected with the system end. The target equipment and the system end are connected through a network.

And the system end can be provided with a file management control program for managing the production and processing files in the target equipment. There may be several functional modules at the system end, for example, it may include: the device management module, the file management module, the task management module, the edge execution module and the MQ message middleware are used for realizing management control of files of the target device, such as batch file transmission, file distribution, file deletion and the like, through the cooperation of the device management module, the file management module, the task management module, the edge execution module and the MQ message middleware.

It should be noted that, for the management between devices, the system end adopts a device management module, is responsible for the management of the relevant information of the machine device and the file transmission protocol, adapts to the file transmission mode of the machine device, defines a unique device file transmission protocol type, when the device joins the module, the device needs to specify the transmission protocol type used by the device, and the information such as account passwords relevant to the protocol, so as to realize the remote unified viewing and management of the files on the machine device, including the operations of inquiring the list of the file catalogues on the device, entering the catalogues, creating the files, obtaining the file contents, deleting the file catalogues, and the like.

And a file management module is adopted to replace a USB flash disk and a scattered file server and is responsible for providing unified file service at a cloud end for managing files. The module is used for storing and managing the processing files and supporting the functions of inquiring, creating, deleting, uploading and the like of the files and the catalogs.

The task management module is used for being responsible for configuration management of operation tasks of the machine equipment, and comprises the following components: querying, viewing, creating, deleting and executing tasks.

The edge execution module is in charge of adapting the file transmission protocol type of the equipment, acquiring equipment protocol information from the equipment management module according to the protocol type, realizing the establishment of a file transmission channel with the machine equipment, executing specific file interaction operation, and comprising the operations of inquiring, creating and deleting the file catalogue.

The MQ message middleware is responsible for the transfer of task messages between the task management module and the edge execution module and ensures the reliability of the messages.

The system end and the target equipment can be connected through a wired network or a wireless network, and in addition, one-to-many connection can be realized through other modes such as Bluetooth or infrared.

The management task information may be task information generated by a manager through relevant configuration information input by a system end, and the management task information is used as management task information. The information may include, but is not limited to, information such as specific task types required by the system side, for example, file distribution, file editing, and the like, specific data, specific target devices targeted, communication protocols between the target devices, and the like.

Step S200, generating task execution information for the target device based on the task data corresponding to the management task information according to the task type.

The task management module generates the task execution information according to the task type and based on specific task data corresponding to the management task information, so that the edge execution module can execute the task execution information conveniently.

The task types may include, for example, file delivery, file deletion, and the like. The task data can be the number of the target device corresponding to the task, the address of the file to be edited or written, and the like.

And step S300, based on the task execution information, establishing communication connection with each target device, and executing the task data corresponding to the task execution information.

The edge execution module is utilized to respectively establish communication connection with one or more corresponding target devices through a specific communication protocol in the task execution information, and then execute the task execution information according to the task data, so that management control of files in each target device is realized.

In this embodiment, after the target device is determined, task execution information is generated through the task type, communication connection with the target device is established according to the task execution information, task data corresponding to the task execution information is executed, a simplified transmission operation of a task automation management mode is formed, transmission efficiency and transmission safety are improved, the probability of transmission errors is reduced, the working intensity of operators is remarkably reduced, remote checking, management, batch operation and batch transmission of files (production and processing files) on machine devices are realized, production efficiency, processing precision and production quality are remarkably improved, file management of the machine devices and the devices becomes ordered, file transmission of the devices is efficient and safe, production cost is reduced, and enterprises realize cost reduction and synergy.

Example 2:

referring to fig. 3, embodiment 2 of the present invention provides a file management control method, based on embodiment 1 above, the step S200, according to the task type, generating task execution information for the target device based on task data corresponding to the management task information, including:

step S210, based on the task type, determining directory information and/or file information corresponding to each target device to be batched according to the management task information; and writing the catalog information and/or the file information and the task type into the task execution information.

The task data includes directory information and/or file information corresponding to the target device to be operated in batch.

By task type, two types of tasks may be included, but are not limited to:

(1) Deleting the file task;

(2) Issuing the file task.

Further, for example, editing file tasks, file name renaming, and the like may also be included.

On the basis of the task type, the task management module firstly determines directory information and/or file information corresponding to target equipment needing to be operated.

For example, the task type is a file deletion task, so that the task management module needs to determine the directory information corresponding to the target device a needing to be operated, and specifically, the directory address needing to be deleted.

And the catalog information and/or the file information and the task type are stored together, and task execution information is written in and obtained so as to further execute the task.

Further, referring to fig. 4, step S210 is configured to determine, based on the task type, directory information and/or file information corresponding to the target device to be batched according to the management task information; and writing the catalog information and/or file information and the task type into the task execution information, wherein the method comprises the following steps:

step S211, according to the management task information, determining directory information and/or file information corresponding to the target equipment, and writing the directory information and/or the file information into an execution log table as task log detail data;

in the above steps, the purpose is to obtain the information required by the target device during the task execution, including the related directory and file information. And writing the catalog information and/or the file information into an execution log table as task log detail data so as to be further executed by an edge execution module and facilitate the follow-up task execution monitoring and statistical analysis. By constructing the execution log table, detailed record and tracking of the task execution process are provided, and the task execution process is helpful for troubleshooting and analyzing the execution result.

In addition, in the task state, the present step may first modify the state to be executing. And then, according to the task configuration data, namely the management task information, obtaining task log detail data, changing the state into to-be-executed, and writing the to-be-executed state into an execution log table.

Step S212, packaging the execution log table corresponding to the target equipment into one message data in an MQ message queue;

the above, for a target device, packages its execution log table into one message data in the MQ message queue.

Step S213, the message data is sent to the theme in the MQ message queue, and the task ID corresponding to the management task information is put into an execution progress monitoring list;

when executing the operation task for the file, for example, issuing the task, the module integrates and packages the task configuration information into a message, merges the task of the same device into an MQ message, and pushes the MQ message into the MQ message middleware one by one for the edge execution module to acquire and execute.

Step S214, inquiring the completion condition of the corresponding task in the execution log table according to the task ID, and counting the total number, the completed number and the failure number of the tasks corresponding to the task ID;

And each task is correspondingly provided with a task ID, and according to the task ID, the completion condition of the code task log can be inquired, and statistics of the total number, the completed number and the failure number of the tasks can be carried out.

And acquiring the completion condition and statistical information in the task execution process according to the task ID, and monitoring and counting the task execution progress. Specifically, the relevant execution records are queried in the execution log table according to the task ID. The total number of tasks, the number of completed tasks and the number of failures are counted. And the completion condition and the statistical information of the task are acquired by inquiring the execution log table, so that the execution progress and the result of the task can be monitored in real time. Real-time monitoring and statistical analysis of task execution conditions are provided to help users understand the state and result of task execution.

Step S215, judging whether the completed number is not less than the total number of tasks;

in the step, the execution condition of the task is judged, whether the task is completed or not is judged, and the execution condition of the task is judged by comparing the magnitude relation between the completed number and the total number of the tasks. Specifically, whether all the tasks are executed is determined by judging whether the completed number reaches the total number of the tasks. The step can simply and intuitively judge the task execution condition, and is convenient for subsequent task processing and progress updating.

Step S216, if yes, removing the task corresponding to the task ID from the progress monitoring list;

In this embodiment, real-time monitoring of the task execution state can be achieved: by recording the execution log details of the tasks in the execution log table and packaging related information into messages and sending the messages to the MQ message queue, the real-time monitoring of the task execution state is realized. The system administrator or other related personnel can query the execution log table according to the task ID to acquire the completion condition and statistical information of the task and quickly know the progress and result of the task. Collaborative processing of a distributed system: the use of message queues as middleware for data transfer provides the co-processing capability of a distributed system. And the different modules communicate in a mode of publishing and subscribing information, so that decoupling and asynchronous processing are realized. This may improve the scalability and stability of the system. Statistical analysis and problem investigation: by performing statistical analysis on the data in the execution log table, information such as the total number of tasks, the number of completed tasks, the number of failures and the like can be known. The information is helpful for evaluating the task execution efficiency, finding problems in task execution in time, and conducting problem investigation and processing. Efficient utilization of system resources: by judging whether the completed number reaches the total number of tasks and timely removing the completed tasks from the progress monitoring list, redundant monitoring and processing are avoided, and the resource utilization efficiency of the system is improved. The reliability and stability of the system are improved: by means of asynchronous processing and message queue, the message transmission and processing of task execution are decoupled, and the task execution is prevented from being influenced by single-point faults. Meanwhile, problems in task execution are found and processed in time through real-time monitoring and statistical analysis, and the reliability and stability of the system are improved.

In summary, the design and execution of these steps make task execution more controllable, monitorable and reliable, which is helpful to improve the efficiency and expandability of the system, and is convenient for the user to track and manage the execution state of the task.

Example 3:

referring to fig. 5, embodiment 3 of the present invention provides a file management control method, based on embodiment 1 above, the step S300, based on the task execution information, establishes a communication connection with each of the target devices, and executes the task data corresponding to the task execution information, including:

step S310, acquiring the task execution information and analyzing the task execution information, and establishing communication connection with the target equipment according to the task execution information;

according to the task execution information, the communication connection mode can be determined, so that the establishment of the communication connection with the target equipment is realized.

Step S320, performing data processing on the task data on the target device according to the task execution information based on the task type.

Further, referring to fig. 6, the step S310 of obtaining the task execution information and analyzing the task execution information, and establishing a communication connection with the target device according to the task execution information includes:

Step S311, analyzing the task execution information to obtain the device identification of the target device;

step S312, according to the equipment identification, acquiring file transmission protocol information and configuration information corresponding to the target equipment;

step S313, establishing a communication connection with the target device according to the file transfer protocol information and the configuration information.

The device identifier may be a number, a model number and related device information corresponding to the device, and different devices may adopt the same or different file transfer protocols and configuration information. Therefore, according to the equipment identification, the corresponding file transfer protocol and configuration information can be acquired.

The communication connection between the server and the target device can be realized based on the file transfer protocol and the configuration information.

Further, referring to fig. 7, in step S320, performing data processing on task data on the target device according to the task execution information based on the task type includes:

step S321, judging whether the task type is an issuing task;

step S322, if the task type is the issuing task, creating a target catalog corresponding to the issuing file on the target equipment based on the file transfer protocol information and the configuration information of the target equipment;

Step S323, obtaining a file stream from a file server, and writing the file in the file stream into the target directory corresponding to the target device.

Further, in step S321, after determining whether the task type is the task to be issued, the method further includes:

step S324, if the task type is not the issuing task, judging that the task type is a deleting task, and determining a corresponding target directory and/or a target file based on the task execution information;

step S325, deleting the target directory and/or the target file on the target device according to the file transfer protocol information and the configuration information of the target device.

In the above-mentioned process, when data processing is performed, it is necessary to first determine the task type, and different processing flows corresponding to different task types.

If the task type is the issuing task, firstly, a target directory corresponding to the issuing file is required to be created on the target device through the transmission protocol information and the configuration information, then a file stream is acquired from the file server, a file is created at the position of the directory corresponding to the device, and the file content in the file stream is written into the target directory of the target device.

If the task type is a deletion task, firstly deleting a file or a directory appointed in a message on the equipment through a protocol, then updating the task execution log state and the execution time, and if the execution is successful, updating the state to be successful; if execution fails, the state update "fails" and the update failure information is synchronized.

The system end defines the operation on the target equipment as an operation task, wherein the operation task can comprise a deletion task and a issuing task:

(1) The deleting task is used for realizing the function of deleting the file catalogs on a plurality of devices in batches;

(2) And issuing tasks for sending the file catalogs to the machine equipment in batches.

By the manual repeated operation systemization of the task, the manual operation processing of equipment by equipment is not needed, the task is used for managing a plurality of equipment in batches, and a plurality of files and catalogues are operated on a plurality of machine equipment by one task.

When the issuing operation is executed, the module integrates and packages the task configuration information into a message, merges the tasks of the same device into an MQ message, and pushes the MQ message into an MQ message middleware one by one for the edge execution module to acquire and execute;

and monitoring the completion condition of the task in real time until the task is completed, counting the execution progress of the task in real time, wherein the execution result comprises the information of the total number of the task, the completed number, the failure reason and the like, and particularly comprises each file or each catalog of each device.

The task management module conceptual model may include the following information:

(1) Tasks: task ID, type (delete task, issue task), target path, status (to be executed, in execution, done), creator, creation time;

(2) Task equipment: task device ID, task ID, device code;

(3) Task file: task file ID, task ID, file or directory path, type (file, directory);

(4) Task execution log: task log ID, task ID, device code, file or directory path, type (file, directory), status (to be executed, success, failure), execution time, failure information;

(5) The MQ message format is referenced below:

{

taskId: 156,

deviceCode: 'CNC45329801',

targetPath: '/pro',

task type 1,//1 issue task, 2 delete task

dirs:[

{logId: 421, path:'/xxx/xxx/x'}

],

files:[

{logId: 422, path:'/xxx/xxx/xx.NC'}

]

}

In a specific embodiment, the server performs batch deletion on the files on the target device, and specifically may perform the following method:

(1) Accessing equipment on the enterprise site to a network;

(2) Adding networking equipment into an equipment management module, configuring a connection protocol type and related information, confirming that communication connection can be established with the equipment, and normally browsing catalogues and files on the equipment through a system;

(3) Creating a deletion task, selecting a device list to be deleted in batches, selecting a target directory and a file list to be deleted from one device, and storing the task, wherein the task state is to be executed;

(4) Selecting a task to be executed, clicking a task execution button, starting to execute the task, and converting the task state into execution. Meanwhile, the task management module generates a task execution log according to the task configuration, and the log state is to be executed. The task logs of the same device are packaged into messages and sent to the MQ message middleware theme;

(5) The task management module puts the task ID into a monitoring list, starts to monitor the task execution progress, inquires the total number of tasks in a task log according to the task ID, completes the number of failures, updates the task state data into a cache state, and is used for calling and inquiring an external web interface;

(6) The edge execution module monitors the message in the MQ message middleware, judges the type of the message as a deletion task after receiving the message, and acquires the equipment code from the task, and a list of the task log list of the catalog and the file to be deleted. And acquiring the equipment protocol connection related information from the equipment management module through the equipment code, and establishing communication connection with equipment. Executing task log details in the task message one by one, deleting files or catalogues on the equipment, updating the task log state in the task management module according to the task detail ID to be successful or failed after the operation is completed, and synchronously updating failure information when the failure occurs;

(7) The task management module monitors the task completion condition according to the task ID polling, when the task log states of all tasks under the task ID become successful or fail, the task is completed, the task management module updates the task states according to the task ID to be completed, removes the task ID from the task state monitoring list, and the task execution is ended.

In a specific embodiment, the server side performs batch sending of the processing files on the file server to the target device, and specifically may perform the following method:

(1) Connecting the equipment of the enterprise site into the network in advance;

(3) Creating a task to be issued, selecting files and catalogs to be issued in batches from a file server, selecting target equipment to be issued in batches, selecting a position of the target catalogs to be issued from one piece of equipment, and storing the task, wherein the task state is to be executed;

(4) Selecting a task to be executed, clicking a task execution button, starting to execute the task, and converting the task state into execution. Meanwhile, the task management module generates a task execution log according to the task configuration, and the log state is to be executed. The task logs of the same device are packaged into messages and sent to an MQ message middleware;

(6) The edge execution module monitors the message in the MQ message middleware, judges the task type as a issuing task after receiving the message, acquires the equipment code from the task, and needs to issue a catalog and a file task log detail list to be issued and needs to issue a target path to the equipment. And acquiring the equipment protocol connection related information from the equipment management module through the equipment code, and establishing communication connection with equipment. Executing task log details in the task message one by one, creating a catalog in an equipment catalog path, copying file contents from a file server and writing the file contents into a target position corresponding to equipment, updating the task log state in a task management module according to the task detail ID to be successful or failed after the operation is finished, and synchronously updating failure information when the operation fails;

In this embodiment, the data processing is performed on the corresponding file in the designated file or directory by continuously establishing a communication connection with the target device that needs to perform the data processing, and then executing the task data corresponding to the task execution information, specifically, the device identifier is obtained by analyzing the task execution information, and the file transmission protocol information and the configuration information are obtained by the device identifier, so that the communication connection between the server and the target device is established, and then, based on the communication connection, the corresponding processing is performed on the file of the target device according to the different task types, thereby realizing the automatic execution of the task and improving the task execution efficiency.

Example 4:

referring to fig. 8, embodiment 4 of the present invention provides a file management control method, based on embodiment 1 above, the file management control method further includes:

step S400, receiving a device newly-added instruction, and judging whether a system end supports the transmission protocol type of corresponding amplification device according to the device newly-added instruction;

step S500, if the system end supports the transmission protocol type, saving the equipment identifier, the equipment name and the transmission protocol type which are confirmed to be supported by the amplification equipment as configuration information corresponding to the amplification equipment;

Step S600, if the system end does not support the transmission protocol type, executing a transmission protocol expansion flow for the amplification equipment, returning to execute the new instruction of the receiving equipment, and judging whether the system end supports the transmission protocol type of the corresponding amplification equipment according to the new instruction of the equipment.

The device management module is used for managing related information of the machine device and the file transmission protocol, adapting the file transmission mode of the machine device, defining a unique device file transmission protocol type, designating the transmission protocol type used by the device when the device joins the module, and information such as account passwords related to the protocol, so as to realize remote unified viewing and management of the files on the machine device, including operations of inquiring a file catalog list on the device, entering the catalog, creating the file, acquiring file contents, deleting the file catalog, and the like.

When a new device is needed, the device identifier, the device name, the transmission protocol and the information related to the protocol need to be maintained by the device management module, and specifically, the device management module conceptual model may include the following information:

(1) The device comprises: device identification, device name, transport protocol type (FTP or FOCAS);

(2) FTP transfer protocol: the device identification, the IP address, the protocol (FTP or SFTP), the protocol port, the transmission mode (active or passive), the user name, the password;

(3) FOCAS transport protocol: it is necessary to include device identification, IP address, protocol port, timeout time.

When a new device is needed, based on the method in this embodiment, the following procedure may be adopted:

a manager logs in a system end and enters an equipment management module to operate newly-added equipment;

judging whether the transmission protocol type of the system end for the newly added equipment is supported or not;

if so, entering a device identifier, a device name and a protocol type of the device;

and according to the selected protocol type, inputting relevant information corresponding to the equipment, and storing equipment and protocol configuration, namely configuration information corresponding to the amplification equipment.

If not, the operation is carried out according to the transmission protocol expansion flow, the expansion protocol is adjusted to the code of the equipment management module and the code of the edge execution module, and the manager is required to log in the system again, and the equipment management module is entered to operate the newly added equipment until the type of the transmission protocol is supported.

Further, referring to fig. 9, in the step S600, a transmission protocol expansion procedure includes:

Step S610, acquiring transmission protocol definition information corresponding to the amplification equipment;

step S620, a transmission protocol and a protocol information storage model corresponding to the augmentation device are established according to the transmission protocol definition information, and code adaptation extension is performed according to the transmission protocol.

In the transmission protocol expansion flow, firstly, a transmission protocol definition, such as FTP or SFTP, is newly added through a device management module; then, a transmission protocol and a protocol information storage model are newly added through a device management module, and codes are adapted to expand and store relevant information of a management protocol; and finally, performing code adaptation expansion on the newly added protocol by utilizing an edge execution module, so as to realize the operations of supporting inquiry, viewing, creation, deletion and the like of files and catalogs.

In a specific embodiment, the server performs FTP file transfer protocol adaptation extension, which specifically may adopt the following operation method:

(1) The file transmission type of the equipment is judged in advance, the relevant information of the protocol is confirmed, and whether the protocol supports basic operations such as inquiring, adding, deleting and the like of the file catalogue or not. In this embodiment, the protocol supported by the target device is an FTP protocol, but the system end does not support the FTP protocol temporarily, and needs to perform adaptation expansion;

(2) Connecting the equipment on the enterprise site into a network in advance, and if the equipment is not supported, upgrading and reforming in a mode of adding a network IO module;

(3) The method comprises the steps that an FTP transmission protocol type is newly added to a device management module, an FTP related information storage table is newly added, the FTP related information storage table comprises device codes, IP, ports, accounts, passwords, transmission modes (active or passive) and the like, and an expansion adaptation FTP code is used for storing transmission protocol configuration information of each device;

(4) The edge execution module carries out code transformation aiming at the transmission protocol, and the adaptive code of the FTP transmission protocol is newly added to realize logic, so that the directory and the file on the equipment can be remotely operated through the edge execution module, and the operations such as directory file inquiry, checking, new creation, deletion and the like are included;

(5) The protocol adaptation of the FTP is completed through the steps, equipment can be added into the equipment management module, a file transfer protocol is designated as the FTP, the equipment catalogue and the file information which can be remotely operated can be verified on an interface, the operations including inquiring, viewing, newly-built, deleting and the like are included, and the FTP protocol adaptation expansion is completed.

In addition, referring to fig. 10, the present embodiment further provides a file management control apparatus, including:

the confirmation module 10 is used for acquiring management task information and confirming target equipment to be operated in batches and corresponding task types according to the management task information;

A generating module 20, configured to generate task execution information for the target device based on task data corresponding to the management task information according to the task type;

and the execution module 30 is used for establishing communication connection with each target device based on the task execution information and executing the task data corresponding to the task execution information.

In addition, the embodiment also provides a file management control system, which comprises a memory and a processor, wherein the memory stores a file management control program, and the processor runs the file management control program to enable the file management control system to execute the file management control method.

Further, referring to fig. 11, in the file management control system, the following functional modules may be included: the device management module, the file management module, the task management module, the edge execution module and the MQ message middleware.

(1) Device management module 40: the method is responsible for managing relevant information of machine equipment and file transmission protocols, adapts to the file transmission mode of the machine equipment, defines a unique equipment file transmission protocol type, and when the equipment joins a module, the equipment needs to specify the transmission protocol type used by the equipment, and information such as account passwords relevant to the protocol, so that the remote unified viewing and management of the files on the machine equipment is realized.

(2) File management module 50: and the USB flash disk and the scattered file servers are replaced, and are responsible for providing unified file service at the cloud end and managing related files. The existing file system or file server can be adopted to provide basic function service for storing and managing files, and the functions of inquiring, creating, deleting, uploading and the like of the files and the catalogs are supported by the module.

(3) Task management module 60: configuration management responsible for the operating tasks of a machine device, comprising: querying, viewing, creating, deleting and executing tasks.

(4) Edge execution module 70: the method is in charge of adapting to the file transmission protocol type of the equipment, acquiring equipment protocol information from an equipment management module according to the protocol type, realizing the establishment of a file transmission channel with the machine equipment, and executing specific file interaction operation including the inquiry, creation and deletion operations of a file directory; receiving an operation task sent by a cloud task management module; analyzing the task; after establishing connection with the task equipment, executing the operation in the task; after the operation is finished, updating the task execution result in the task database, and recording the failure reason when the execution is successful or failed, so that the server side can conveniently collect and display the task execution progress and the task execution result.

(5) MQ message middleware 80: and the task management module and the edge execution module are responsible for transferring task messages and ensuring the reliability of the messages.

In addition, the present embodiment also provides a computer-readable storage medium having stored thereon a file management control program which, when executed by a processor, implements the file management control method as described above.

In a word, the invention generates task execution information through the task type after determining the target equipment, establishes communication connection with the target equipment according to the task execution information, executes task data corresponding to the task execution information, forms simplified transmission operation of a task automation management mode, improves transmission efficiency and transmission safety, reduces transmission error probability, obviously lightens working intensity of operators, realizes remote checking, management, batch operation and batch transmission of related files, obviously improves production efficiency, thereby ensuring that file management becomes orderly, file transmission is efficient and safe, simultaneously reduces production cost, and realizes cost reduction and synergy for enterprises.

The file management control method provided by the invention can realize unified equipment management, eliminates the difference in file transmission operation between different equipment in a protocol expansion adaptation mode, realizes unified management, and is safer and more convenient for remotely browsing files on the operation equipment; unified processing file management can be realized, management confusion and safe transmission problems caused by various file servers among different devices are solved, and management is ordered; the unified transmission operation can be realized, the transmission operation is simplified in a task automatic transmission mode, the transmission efficiency and the transmission safety are improved, the transmission error probability is reduced, and the working intensity of operators is remarkably reduced.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention. The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. A file management control method, characterized by comprising:

determining directory information and/or file information corresponding to each target device to be batched according to the management task information based on the task type; writing the catalog information and/or the file information and the task type into the task execution information;

if not, returning to execute the completion condition of the corresponding task in the execution log table according to the task ID, and counting the total number, the completed number and the failure number of the tasks corresponding to the task ID;

2. The file management control method according to claim 1, wherein said establishing a communication connection with each of said target devices based on said task execution information and executing said task data corresponding to said task execution information, comprises:

3. The file management control method according to claim 2, wherein said acquiring the task execution information and parsing the task execution information, establishing a communication connection with the target device based on the task execution information, comprises:

4. The file management control method according to claim 2, wherein said performing data processing of task data on said target device according to said task execution information based on said task type includes:

judging whether the task type is an issuing task or not;

5. The method for controlling file management according to claim 4, wherein after said determining whether said task type is an issuing task, further comprising:

6. The file management control method according to claim 4, wherein said file management control method further comprises:

7. The file management control method according to claim 6, wherein said transmission protocol extension flow includes:

8. A file management control apparatus, comprising:

9. A file management control system comprising a memory in which a file management control program is stored, and a processor that runs the file management control program to cause the file management control system to execute the file management control method according to any one of claims 1 to 7.

10. A computer-readable storage medium, wherein a file management control program is stored on the computer-readable storage medium, which when executed by a processor, implements the file management control method according to any one of claims 1 to 7.