A file processing method and system for upstream and downstream intelligent collaboration

The target files and their identifiers are sent through the multicast network, and merged and analyzed after downstream customers generate feedback files, solving the problem of inefficient file processing in the existing technology, realizing intelligent collaboration between upstream and downstream, and simplifying file processing The process and improves collaborative efficiency.

CN118524101BActive Publication Date: 2024-11-26HANGZHOU MEDICAL BEE TRANSFORMATION INTELLIGENT TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410997122.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-24
Publication Date
2024-11-26
Estimated Expiration
2044-07-24

AI Technical Summary

Technical Problem

The existing file processing methods are inefficient, resulting in poor information transmission and chaotic data, and lack of efficient solutions for upstream and downstream intelligent collaboration.

Method used

The target file and its identifier are sent to multiple downstream customers through the multicast network. The downstream customers generate feedback files and return them. The upstream designer merges feedback files with similarity higher than the preset threshold. The multicast node analyzes and discards invalid reply. Files to realize intelligent collaboration between upstream and downstream.

Benefits of technology

It simplifies the file processing process, reduces network bandwidth usage, improves the efficiency of collaborative work between upstream and downstream, and ensures data consistency and efficient transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118524101B_ABST
    Figure CN118524101B_ABST
Patent Text Reader

Abstract

The present invention discloses a file processing method and system for upstream and downstream intelligent collaboration, the method comprising: an upstream designer sends a target file and an identifier to a downstream client through a multicast node; the downstream client receives the target file and the identifier, generates a feedback file of the target file and returns it to the upstream multicast node; the multicast node caches each feedback file, merges feedback files with similarity higher than a preset threshold, and sends feedback files with similarity lower than the preset threshold and the merged feedback file to the upstream designer; the upstream designer receives all feedback files and generates reply files respectively, and sends the reply files to the multicast node; the multicast node discards invalid reply files in the reply files, sends the undiscarded reply files to the downstream client, and deletes the corresponding cached feedback files, so as to realize the intelligent collaboration of upstream and downstream. By using the embodiments of the present invention, the file processing process can be simplified, the network bandwidth occupation can be reduced, and the efficiency of upstream and downstream collaborative work can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the technical field of data management, and in particular to a file processing method and system for upstream and downstream intelligent collaboration. Background Art

[0002] With the development of information technology, file processing plays an important role in various fields. In traditional file processing methods, upstream designers usually need to communicate and interact with each downstream customer individually. This method is inefficient, labor-intensive, and prone to poor information transmission and data confusion. Therefore, it is particularly important to study a file processing method for upstream and downstream intelligent collaboration. Summary of the invention

[0003] The purpose of the present invention is to provide a file processing method and system for upstream and downstream intelligent collaboration to address the deficiencies in the prior art, simplify the file processing process, reduce network bandwidth occupancy, and improve the efficiency of upstream and downstream collaborative work.

[0004] An embodiment of the present application provides a file processing method for upstream and downstream intelligent collaboration, the method comprising:

[0005] The upstream designer sends the target file and its identifier to multiple downstream clients through the multicast nodes of the multicast network;

[0006] The downstream client receives the target file and its identifier, generates a feedback file for the target file and returns it to the upstream multicast node;

[0007] The multicast node caches each feedback file, merges the feedback files whose similarity is higher than a preset threshold, and sends the feedback files whose similarity is not higher than the preset threshold and the merged feedback file to the upstream designer;

[0008] The upstream designer receives the feedback files from all downstream customers and generates corresponding reply files respectively, and sends the reply files to the multicast node;

[0009] The multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream customers, and deletes the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0010] Optionally, the multicast network includes: a (S, G) multicast distribution tree, wherein S is the multicast source address of the upstream designer, and G is the multicast group address.

[0011] Optionally, the feedback file includes: feedback, multicast source address, multicast group address, client's own IP address and name, and an identifier of the target file.

[0012] Optionally, the multicast node caches each feedback file, merges feedback files with similarity higher than a preset threshold, and sends feedback files with similarity lower than the preset threshold and the merged feedback file to the upstream designer, including:

[0013] The upstream multicast node compares the feedback opinions in the feedback files containing the same identifier, caches the feedback opinions whose similarity is not higher than the preset threshold, and records the multicast source address, multicast group address, client's own IP address and name, identifier of the target file and port number of the device receiving the feedback opinion;

[0014] The first feedback and the second feedback whose similarity is higher than a preset threshold are regarded as the same feedback, the first feedback is cached, and the multicast source address of the first feedback, the multicast group address, the client's own IP address and name, the identifier of the target file, and the port number of the device receiving the first feedback are recorded;

[0015] Constructing and recording a file of similar opinions of the second feedback, wherein the file of similar opinions includes: a multicast source address, a multicast group address, a client's own IP address and name, an identifier of a target file, a port number information of a device receiving the second feedback, and a name of a client of the first feedback;

[0016] The feedback files corresponding to the feedback opinions whose similarity is not higher than the preset threshold, the feedback files corresponding to the first feedback opinions, and the feedback files that are similar to the second feedback opinions are sent to the upstream designer.

[0017] Optionally, the reply file includes: reply opinions, an identifier of the target file and a customer name;

[0018] The multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream clients, and deletes the corresponding cached feedback files, including:

[0019] The multicast node analyzes whether the customer name and identifier in the reply file match the recorded customer name and identifier simultaneously;

[0020] If they do not match at the same time, the reply file is discarded;

[0021] If there is a match at the same time and the recorded customer name corresponds to only one feedback, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the downstream customer through the corresponding device port, and delete the feedback corresponding to the customer name and identifier;

[0022] If the customer name that is matched and recorded corresponds to a feedback and an opinion-similar file at the same time, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the corresponding downstream customer through the corresponding device port, delete the feedback corresponding to the customer name and identifier, and modify the customer name in the reply file to the customer name in the corresponding opinion-similar file, and send the modified reply file to the corresponding downstream customer through the device port recorded in the opinion-similar file.

[0023] Another embodiment of the present application provides a file processing system with upstream and downstream intelligent collaboration, the system comprising:

[0024] The first sending module is used for the upstream designer to send the target file and its identifier to multiple downstream clients through the multicast node of the multicast network;

[0025] A first generating module, configured for a downstream client to receive the target file and its identifier, generate a feedback file for the target file and return the feedback file to an upstream multicast node;

[0026] A merging module, used for the multicast node to cache various feedback files, merge feedback files with similarity higher than a preset threshold, and send feedback files with similarity not higher than the preset threshold and the merged feedback file to the upstream designer;

[0027] The second generation module is used for the upstream designer to receive the feedback files of all downstream customers and generate corresponding reply files respectively, and send the reply files to the multicast node;

[0028] The second sending module is used for the multicast node to analyze and discard invalid reply files in the reply files, send the reply files that are not discarded to downstream customers, and delete the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0029] Yet another embodiment of the present application provides a storage medium, wherein the storage medium stores a computer program, wherein the computer program is configured to execute any of the above methods when running.

[0030] Yet another embodiment of the present application provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute any of the methods described above.

[0031] Compared with the prior art, the present invention provides a file processing method for upstream and downstream intelligent collaboration, in which an upstream designer sends a target file and an identifier to multiple downstream clients through a multicast node of a multicast network; the downstream clients receive the target file and the identifier, generate a feedback file for the target file and return it to the upstream multicast node; the multicast node caches each feedback file, merges feedback files with a similarity higher than a preset threshold, and sends feedback files with a similarity not higher than the preset threshold and the merged feedback file to the upstream designer; the upstream designer receives feedback files from all downstream clients and generates reply files respectively, and sends the reply files to the multicast node; the multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream clients, and deletes the corresponding cached feedback files to achieve upstream and downstream intelligent collaboration, thereby simplifying the file processing process, reducing network bandwidth occupancy, and improving the efficiency of upstream and downstream collaborative work. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A hardware structure block diagram of a computer terminal for an upstream and downstream intelligent collaborative file processing method provided by an embodiment of the present invention;

[0033] Figure 2 A flowchart of a file processing method for upstream and downstream intelligent collaboration provided by an embodiment of the present invention;

[0034] Figure 3 A structural diagram of an upstream and downstream intelligent collaborative file processing system provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0035] The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, but should not be construed as limiting the present invention.

[0036] The embodiment of the present invention firstly provides a file processing method with upstream and downstream intelligent collaboration, which can be applied to electronic devices such as computer terminals, specifically ordinary computers, etc.

[0037] The following describes it in detail by taking running on a computer terminal as an example. Figure 1 The hardware structure block diagram of a computer terminal for an upstream and downstream intelligent collaborative file processing method provided by an embodiment of the present invention. Figure 1 As shown, the computer terminal may include one or more ( Figure 1 Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. Optionally, the computer terminal may also include a transmission device 106 for communication functions and an input and output device 108. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above-mentioned computer terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0038] The memory 104 can be used to store software programs and modules of application software, such as program instructions / modules corresponding to the upstream and downstream intelligent collaborative file processing method in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the computer terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0039] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of a computer terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0040] See also Figure 2 , an embodiment of the present invention provides a file processing method for upstream and downstream intelligent collaboration, which may include the following steps:

[0041] S201, the upstream designer sends the target file and its identifier to multiple downstream clients through the multicast node of the multicast network;

[0042] Specifically, the multicast network may include: a (S, G) multicast distribution tree, wherein S is the multicast source address of the upstream designer, and G is the multicast group address. The identifier may be a serial number, and the multicast node may be a router node.

[0043] The upstream designer is the party in the system responsible for generating and publishing target files, usually a developer, manager, or a project team. The upstream designer's task is to create or prepare the target files to be transmitted and assign a unique identifier to each target file. This identifier is used to uniquely identify and associate the target file in subsequent processing.

[0044] The target file can be any type of digital file, such as documents, pictures, design drawings, code files, etc. The identifier is a unique mark used to identify and distinguish a specific target file. The target file and its identifier are sent together to ensure that the target file and its related feedback can be correctly associated and processed.

[0045] A multicast network is a network form that supports point-to-multipoint data transmission, enabling the sender (upstream designer) to send the same data to multiple receivers (downstream customers) at the same time, thereby improving network transmission efficiency. A multicast node is a key component in a multicast network. It is responsible for receiving data sent by upstream designers and delivering it to multiple downstream customers. The data delivery process includes:

[0046] 1. Prepare target files and their identifiers: The upstream designer first creates or prepares the target files and assigns a unique identifier to each file.

[0047] 2. Sending data packets: The upstream designer sends data packets containing the target file and identifier to the multicast node through the multicast network.

[0048] 3. Multicast node distribution of data: After receiving the data packet, the multicast node transmits the target file and identifier in the data packet to multiple downstream clients through the multicast network. The multicast distribution tree of the multicast network ensures that the data can be efficiently transmitted to all clients. The significance of the role is:

[0049] Improve transmission efficiency: Multicast network can realize single point to multipoint data transmission, that is, the upstream designer only needs to send data once, and the multicast network can pass the data to all downstream customers. Compared with one-by-one unicast transmission, this greatly improves data transmission efficiency and reduces network bandwidth consumption.

[0050] Ensure data consistency: Through the multicast network, all downstream clients can receive the same target file and its identifier at the same time. This ensures that all participants use the same version of the file during the entire file processing and feedback process, thus avoiding data inconsistency issues.

[0051] Simplify the distribution process: Upstream designers only need to transmit data with the multicast nodes of the multicast network, instead of sending it to each downstream client one by one. This simplifies the data distribution process, reduces the operational burden of upstream designers, and reduces the probability of errors.

[0052] Support for large-scale distribution: Multicast networks are particularly suitable for large-scale file distribution scenarios. Regardless of the number of downstream customers, multicast networks can efficiently distribute data and ensure that each customer can receive the target file and identifier in a timely manner.

[0053] Provide flexibility: The multicast distribution tree ((S, G) tree, where S is the multicast source address of the upstream designer and G is the multicast group address) of the multicast network provides a flexible address management mechanism, making the system easy to expand and manage. The upstream designer only needs to know the multicast group address to distribute data without having to care about the specific address of each downstream customer, which facilitates the dynamic adjustment of downstream customers.

[0054] In summary, sending the target file and its identifier to multiple downstream clients through the multicast nodes of the multicast network not only improves the transmission efficiency and data consistency, but also simplifies the distribution process, adapts to large-scale distribution scenarios, and provides system flexibility, thereby achieving efficient processing and management of files.

[0055] S202, the downstream client receives the target file and its identifier, generates a feedback file for the target file and returns it to the upstream multicast node;

[0056] Specifically, the feedback file may include: feedback, multicast source address, multicast group address, client's own IP address and name, and the identifier of the target file.

[0057] Downstream clients receive the target file and its identifier: Downstream clients are participants in the system who are responsible for processing or reviewing the target file, which may be multiple users, teams or devices. Downstream clients receive the target file and its identifier sent by the upstream designer from the multicast node through the multicast network. This process involves the following key points:

[0058] 1. Receiving the target file and identifier: The multicast node of the multicast network distributes the target file and identifier to all downstream clients. Each downstream client receives the data by subscribing to the multicast address (G). The multicast node ensures efficient transmission of the target file through the multicast distribution tree ((S, G) tree, where S is the multicast source address of the upstream designer and G is the multicast group address).

[0059] 2. File and identifier matching: Each target file is accompanied by a unique identifier to ensure that downstream customers can accurately identify and process the corresponding file. This is an important prerequisite for establishing a feedback mechanism. Generate feedback file After receiving the target file and its identifier, the downstream customer will process or review it accordingly based on the specific needs and the content of the target file, and generate a feedback file. The feedback file contains the following elements:

[0060] 1. Feedback: downstream customers’ processing results, opinions, suggestions or review contents on the target documents.

[0061] 2. Multicast source address and multicast group address: used to identify and track the source and target multicast group of multicast data to ensure the correctness of data communication.

[0062] 3. Customer’s own IP address and name: used to identify specific downstream customers, which helps to accurately distribute subsequent feedback.

[0063] 4. Identifier of the target file: ensures that the feedback file can be uniquely associated with the corresponding target file.

[0064] Return to the upstream multicast node: After the feedback file is generated, the downstream client returns it to the upstream multicast node through the multicast network. The multicast node is responsible for receiving and caching these feedback files to prepare for subsequent processing and merging. The significance of this function is:

[0065] Efficient feedback mechanism: Through the multicast network, downstream clients can quickly and efficiently receive the target file and its identifier, and quickly return the feedback file to the upstream after processing or review. This mechanism greatly reduces the delay in data transmission and improves the overall feedback efficiency.

[0066] Ensure the timeliness and accuracy of feedback: Using multicast networks for data distribution and feedback transmission ensures that all downstream clients can receive the latest target files and their identifiers at the same time. This helps ensure the timeliness and consistency of feedback and avoid feedback errors caused by inconsistent versions.

[0067] Helps with subsequent data processing and analysis: The feedback file contains detailed feedback content and related identification information (such as multicast source address, multicast group address, client IP address and name, target file identifier, etc.), which provides sufficient information support for the subsequent data processing and analysis of upstream designers and multicast nodes. For example, this information can be used to merge feedback opinions, analyze the effectiveness of feedback opinions, and provide personalized replies.

[0068] Simplified management and tracking: By including clear identification information in the feedback file (such as the target file identifier, the customer's own IP address and name, etc.), the system can easily manage and track each feedback file. The multicast distribution tree structure of the multicast network further simplifies data management and transmission, ensuring efficient and traceable communication between downstream customers and upstream designers.

[0069] Support for large-scale feedback collection: Using multicast networks to transmit feedback files is particularly suitable for large-scale distributed systems. In such systems, there are a large number of downstream clients that need to receive files and return feedback at the same time. The efficiency and scalability of multicast networks enable the system to fully cope with the needs of large-scale data transmission and feedback collection.

[0070] Through the multicast nodes of the multicast network, downstream clients can efficiently receive the target file and its identifier, and generate feedback files and return them to the upstream multicast nodes. This process not only improves the efficiency of data transmission and the timeliness of feedback, but also simplifies data management and tracking, adapts to the needs of large-scale feedback collection, and provides a solid foundation for upstream and downstream intelligent collaboration.

[0071] S203, the multicast node caches each feedback file, merges the feedback files whose similarity is higher than a preset threshold, and sends the feedback files whose similarity is not higher than the preset threshold and the merged feedback file to the upstream designer;

[0072] Specifically, the upstream multicast node compares the feedback opinions in the feedback files containing the same identifier, caches the feedback opinions whose similarity is not higher than the preset threshold, and records the multicast source address of the feedback opinion, the multicast group address, the client's own IP address and name, the identifier of the target file, and the port number information of the device receiving the feedback opinion;

[0073] Explanation:

[0074] - Pairwise comparison: The multicast node compares all feedback files containing the same target file identifier one by one to determine the similarity between them.

[0075] - Cache feedback with similarity not higher than a preset threshold: If the similarity between two feedbacks is not higher than a preset threshold, these feedbacks will be cached, which indicates that they are significantly different.

[0076] - Record details: At the same time, the system needs to record the detailed information of these feedbacks, including the multicast source address, multicast group address, client IP address and name, the identifier of the target file, and the port number of the device that received the feedback. These records are convenient for subsequent review, analysis and processing.

[0077] The significance of the function is:

[0078] - Ensure diversity of opinions: By recording feedback whose similarity is not higher than a preset threshold, the system is able to retain all opinions with significant differences, which is very important for fully understanding the views and needs of downstream customers.

[0079] - Facilitate follow-up tracking and management: Completely record the detailed information of feedback to ensure that there is a clear source and person responsible in the subsequent processing, which facilitates more refined management.

[0080] - Data accuracy and completeness: Recording all dissimilar opinions ensures the completeness and accuracy of the data and provides upstream designers with diverse feedback data.

[0081] The first feedback and the second feedback whose similarity is higher than a preset threshold are regarded as the same feedback, the first feedback is cached, and the multicast source address of the first feedback, the multicast group address, the client's own IP address and name, the identifier of the target file, and the port number of the device receiving the first feedback are recorded;

[0082] Explanation:

[0083] - Similarity is higher than the preset threshold: When the similarity between two feedback opinions is higher than the threshold preset by the system, it indicates that their contents are basically the same.

[0084] - Treat as the same feedback: The system treats the two feedbacks as the same and only keeps one of them.

[0085] - Cache the first feedback: select and cache one of the feedbacks, and record its detailed information, including the multicast source address, multicast group address, client IP address and name, identifier of the target file, and device port number information.

[0086] Function and significance:

[0087] - Improve data processing efficiency: By merging similar feedback, the system reduces the amount of data that needs to be processed and improves data processing efficiency.

[0088] - Avoid redundant information: Merging similar opinions avoids the existence of redundant information, allowing upstream designers to analyze and process feedback data more efficiently.

[0089] - Save storage resources: After merging, only one feedback opinion is recorded, which reduces the redundant data stored and saves storage resources.

[0090] Constructing and recording a file of similar opinions of the second feedback, wherein the file of similar opinions includes: a multicast source address, a multicast group address, a client's own IP address and name, an identifier of a target file, a port number information of a device receiving the second feedback, and a name of a client of the first feedback;

[0091] Explanation:

[0092] - Similarity file: The system creates a similarity file for the second feedback to record the detailed information similar to the first feedback.

[0093] - Record details: The identical opinion file contains the multicast source address, multicast group address, customer IP address and name, target file identifier, device port number information of the original second feedback opinion, and the customer name of the first feedback opinion.

[0094] Function and significance:

[0095] - Keep all feedback source information: By recording files with similar opinions, the system retains the source information of all feedback. Although the content is similar, no customer feedback is lost in the record.

[0096] - Facilitate subsequent distribution and processing: The opinion similarity file helps the system to clearly know which feedback contents are the same, as well as their sources and detailed information during the subsequent distribution and processing.

[0097] - Enhanced transparency and traceability of the system: Recording detailed information improves the transparency and traceability of the system, helping upstream designers to fully understand the feedback situation and source.

[0098] The feedback files corresponding to the feedback opinions whose similarity is not higher than the preset threshold, the feedback files corresponding to the first feedback opinions, and the feedback files that are similar to the second feedback opinions are sent to the upstream designer.

[0099] Function and significance:

[0100] - Complete feedback information delivery: All feedback (including different and similar opinions) will be delivered to upstream designers to ensure that upstream designers can obtain comprehensive feedback information.

[0101] - Facilitates comprehensive analysis by upstream designers: Upstream designers can conduct comprehensive analysis based on complete feedback data, understand the opinions and needs of different customers, and make more accurate decisions.

[0102] - Improve work efficiency: The system has preliminarily sorted and classified the feedback, reducing the workload of upstream designers, improving work efficiency, and promoting intelligent collaboration between upstream and downstream.

[0103] By analyzing the similarity, caching, merging and recording detailed information of feedback files, it aims to improve data processing efficiency, avoid information redundancy, save storage resources, and retain information from all feedback sources, improve the transparency and traceability of the system. Ultimately, comprehensive feedback information will be sent to upstream designers to facilitate comprehensive analysis, make more accurate decisions, and achieve intelligent collaboration between upstream and downstream.

[0104] S204, the upstream designer receives the feedback files of all downstream customers and generates corresponding reply files respectively, and sends the reply files to the multicast node;

[0105] Specifically, the reply file may include: reply opinions, an identifier of the target file, and a customer name.

[0106] Upstream designers receive all downstream customer feedback files

[0107] This step involves the upstream designer receiving feedback files sent back by all downstream clients from the multicast node. The feedback files may be processed by the multicast node, including similarity analysis, caching, and merging. Therefore, the feedback files received by the upstream designer include the original feedback files with similarity not higher than the preset threshold and the merged feedback files (the feedback files corresponding to the first feedback and the files with similar opinions corresponding to the second feedback).

[0108] - Receiving feedback files: Upstream designers obtain all feedback files from multicast nodes through network connections. These feedback files have been preliminarily processed and screened to ensure the validity and relevance of the data.

[0109] - Feedback document type: Feedback documents include the specific opinions of downstream customers on the target document, which may include suggestions, review opinions, modification opinions, etc.

[0110] Generate corresponding reply files respectively

[0111] After receiving the feedback files, the upstream designers will generate corresponding reply files according to the content of each feedback file. These reply files are designed to respond to the feedback from downstream customers.

[0112] - Generation of responses: Upstream designers need to write detailed responses based on the specific content of each feedback document, combined with the actual situation and their own design goals. Responses can be explanations of questions raised by downstream customers, or reasons for accepting or rejecting their suggestions.

[0113] - Structure of the reply document: The reply document usually includes the reply comments, the identifier of the original target document and the name of the downstream customer and other key information, so that the reply document can accurately correspond to the original feedback document.

[0114] Send the reply file to the multicast node

[0115] After all reply files are generated, the upstream designer sends them back to the multicast node through the network. The multicast node is responsible for further processing and distributing these reply files to ensure that they can be accurately delivered back to the corresponding downstream customers.

[0116] - Transmission of reply files: The reply files are transmitted to the multicast nodes through the network. The multicast nodes will receive all reply files and proceed to the next step of processing.

[0117] - Purpose of sending to multicast nodes: Multicast nodes are the core nodes in the entire multicast network, responsible for efficient data distribution and management. Sending reply files to multicast nodes can use their efficient multicast distribution capabilities to quickly deliver files to multiple downstream customers.

[0118] The significance of the function is:

[0119] Establish an effective feedback and reply mechanism By receiving feedback files and generating reply files, upstream designers can respond to downstream customers' opinions and suggestions in a timely manner, and establish an effective feedback and reply mechanism. This mechanism facilitates communication and collaboration between upstream and downstream, and improves overall work efficiency.

[0120] - Enhanced communication and understanding: Downstream customers express their opinions and questions through feedback documents, and upstream designers respond through reply documents. This two-way communication method helps both parties better understand each other's needs and views.

[0121] - Improve work efficiency: Timely response to downstream customer feedback can speed up the progress of the entire project and avoid delays caused by poor communication.

[0122] Improve the quality of design and decision-making Upstream designers can obtain more input information and different perspectives by analyzing and responding to feedback from downstream customers, which helps improve the quality of design and decision-making.

[0123] - Comprehensive opinions from multiple parties: After receiving and analyzing feedback from multiple downstream customers, upstream designers can comprehensively consider different opinions and make more comprehensive and fair decisions.

[0124] - Continuous Improvement and Optimization: Through a continuous feedback and response cycle, upstream designers can continuously improve and optimize design solutions to enhance the quality and performance of products or projects.

[0125] Accurate distribution and tracking: The reply files are sent to the multicast nodes. Through the efficient distribution capabilities of the multicast nodes, the reply files can be quickly delivered to the corresponding downstream customers, ensuring that feedback can be responded to and followed up in a timely manner.

[0126] - Efficient distribution: Multicast nodes can efficiently distribute reply files to multiple downstream clients, saving time and bandwidth resources.

[0127] - Accurate tracking: Through the identification information and downstream customer information in the reply files, the multicast node can accurately track and distribute these files to ensure that each downstream customer receives the corresponding reply.

[0128] Promoting intelligent collaboration between upstream and downstream Through this process, intelligent collaborative work is achieved between upstream and downstream. From receiving feedback, generating replies to distributing replies, the entire process is highly automated, reducing manual intervention and improving overall collaborative efficiency.

[0129] - Automated collaboration: Utilize the efficient processing capabilities of multicast networks and multicast nodes to automate the processing of feedback and replies, reduce manual operations, and improve efficiency.

[0130] - Intelligent management: Through intelligent feedback and response management, upstream and downstream can work together more efficiently, respond quickly to needs and changes, and improve overall work quality and efficiency.

[0131] Through this step, upstream designers can obtain feedback information in a timely manner, generate targeted reply files and distribute them efficiently through multicast nodes, ensuring timely delivery and response of information, improving communication efficiency and decision-making quality, and realizing intelligent collaboration between upstream and downstream.

[0132] S205, the multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream customers, and deletes the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0133] Specifically, the multicast node analyzes whether the customer name and identifier in the reply file match the recorded customer name and identifier simultaneously;

[0134] Explanation

[0135] - Analyze customer name and identifier: The multicast node checks the customer name and target file identifier in each reply file and compares them with the previously recorded feedback file information to ensure that the two match.

[0136] - Matching operation: This step is mainly to confirm by comparing the information in the reply file and the feedback record in the cache.

[0137] Function and significance

[0138] - Ensure accuracy: By analyzing and matching customer names and identifiers, we ensure that each reply document is accurately matched to the corresponding feedback document, thus preventing wrong or missed reply documents.

[0139] - Improve data consistency: The matching operation ensures the consistency and integrity of the data and avoids information confusion.

[0140] If they do not match at the same time, the reply file is discarded;

[0141] Explanation

[0142] - No match discard: If the customer name and identifier in the reply file cannot be matched with the previously recorded feedback information at the same time, the system will discard the reply file.

[0143] - Invalid file processing: This step is the processing strategy for invalid reply files, that is, discarding unmatched reply files.

[0144] Function and significance

[0145] - Exclude invalid data: Discarding unmatched response files can exclude invalid and erroneous data, ensuring that the system only processes valid feedback and responses.

[0146] - Improve system efficiency: By discarding invalid files, the system can reduce the time and resources required to process invalid data, thereby improving overall processing efficiency.

[0147] If there is a match at the same time and the recorded customer name corresponds to only one feedback, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the downstream customer through the corresponding device port, and delete the feedback corresponding to the customer name and identifier;

[0148] Explanation

[0149] - Matching a single feedback: If both the customer name and identifier match, and there is only one feedback for that customer on record, the system looks up the device port number information for that customer.

[0150] - Distribute reply files: After finding the corresponding device port number, the system will send the reply files to downstream customers through the corresponding device port.

[0151] - Delete feedback records: After successfully sending the reply file, the system will delete the corresponding feedback in the cache, indicating that the feedback has been processed.

[0152] Function and significance

[0153] - Accurate distribution: Ensure that the reply files can be accurately sent to the corresponding downstream customer devices, improving the accuracy of distribution.

[0154] - Data update: Delete processed feedback to keep the system cache data updated and tidy to avoid duplicate processing.

[0155] If the customer name that is matched and recorded corresponds to a feedback and an opinion-similar file at the same time, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the corresponding downstream customer through the corresponding device port, delete the feedback corresponding to the customer name and identifier, and modify the customer name in the reply file to the customer name in the corresponding opinion-similar file, and send the modified reply file to the corresponding downstream customer through the device port recorded in the opinion-similar file.

[0156] Explanation

[0157] - Matching multiple files: If the customer name and identifier match at the same time, and there is a feedback and a feedback matching file in the customer's record, the system will first look for the device port number information corresponding to the customer.

[0158] - Send the original reply file: The system will first send the reply file to the downstream customer who has the original feedback through the corresponding device port.

[0159] - Delete original feedback record: After sending, the system deletes the original feedback corresponding to the customer and identifier in the cache.

[0160] - Modify and issue identical reply files: Change the customer name in the reply file to the customer name in the file with identical opinions, and issue it again through the device port recorded in the file with identical opinions to ensure that customers with identical opinions can also receive replies.

[0161] Function and significance

[0162] - Double feedback handling: This step ensures that both the original feedback and customers with similar feedback receive corresponding responses, fully covering all relevant feedback.

[0163] - Accurate delivery: Through modification and distribution processing, ensure that all relevant customers can accurately receive the reply documents, improve user experience and system reliability.

[0164] - Data simplification and cleaning: Deleting the original feedback records after processing and modifying the response files sent out will help keep the system data concise and updated and avoid data redundancy.

[0165] By analyzing, matching and processing the reply documents, the system can ensure that the reply documents can be accurately and efficiently delivered to the corresponding downstream customers, while excluding invalid data and simplifying data management. Specific steps include matching reply documents and discarding unmatched documents, accurately distributing reply documents, and processing and distributing reply documents involving multiple feedback opinions. This series of operations further improves the efficiency, accuracy and reliability of the system, and achieves the purpose of intelligent collaboration between upstream and downstream.

[0166] For example, a practical application scenario is as follows:

[0167] After the upstream designer completes the design, he transmits the solution content to N downstream partners in the form of multicast. The partners report the problem to the upstream, and each multicast router node performs content analysis. If the core content is similar, it is merged and sent upstream. After the designer replies, it is sent down to the relevant downstream partners in the form of multicast, and the router is responsible for sending reply files to those who have similar opinions to share the pressure.

[0168] 1. Prerequisites

[0169] After the upstream designer Up-A has designed the first draft, he will send the draft file to the downstream related customers Down-A, Down-B, Down-C, etc. in a multicast manner, including a serial number to identify its uniqueness. All parties agree to send the draft to a certain multicast group address, and all network nodes support the multicast protocol. The downstream related customers participating in the collaborative group will regularly send the IGMP protocol to join the multicast group, so as to achieve the smooth reception of the draft.

[0170] When the upstream designer sends the design draft in the form of multicast (for example, 226.1.1.1), all downstream related clients who join the multicast group will receive it. The multicast distribution forms a (S, G) multicast distribution tree, where S is the unicast IP address of the upstream designer, that is, 100.100.100.100, and G is the multicast group address, that is, 226.1.1.1. Therefore, this is a (100.100.100.100, 226.1.1.1) multicast distribution tree.

[0171] All customers in the collaborative group are required to give feedback on the design draft, and even if they have no opinion, they are required to give feedback and agree. The feedback message contains the above serial number. The designer will reply after receiving feedback from all customers.

[0172] 2. Feedback Messages and Their Processing

[0173] All downstream related customers will submit a feedback file on the design draft, which contains the opinions, multicast source address S=100.100.100.100 and multicast group address G=226.1.1.1, as well as the customer's own IP address and name, and the serial number of the design draft.

[0174] The router is responsible for caching and analyzing the content. For the first feedback with the same sequence number, the router directly sends the file upstream from the inbound interface of the (S, G) multicast forwarding table entry according to the (S, G) information in the message. The feedback is cached and the name of the feedback customer, customer IP address, multicast source IP address and multicast group address, sequence number, and port number of the device receiving the feedback are recorded, for example, "Down-A, 20.20.20.20, 100.100.100.100, 226.1.1.1, 12345678, port-1" are recorded. The cached feedback is bound to the record entry.

[0175] If the router receives a feedback file from the second customer with the same serial number, it will compare the feedback with the cached feedback from the first customer. If they are different, the router will directly send the file upstream from the inbound interface of the (S, G) multicast forwarding table entry based on the (S, G) information in the message, cache it, and record the name of the feedback customer, customer IP address, multicast source IP address and multicast group address, serial number, port number of the device receiving the feedback, etc., for example, "Down-B, 30.30.30.30, 100.100.100.100, 226.1.1.1, 12345678, port-2". The cached feedback is bound to the record entry. The (S, G) multicast forwarding table entry mainly includes: the IP address S of the multicast source, the multicast group address G, the inbound interface (i.e., the interface on which the device receives the multicast stream), the outbound interface list, the upstream neighbor IP address, etc.

[0176] If they are the same, the new feedback is not cached, and the name of the feedback customer, customer IP address, multicast source IP address and multicast group address, sequence number, port number of the device receiving the feedback, and other information are recorded. The customer name that is the same as the feedback is added, for example, "Down-C, 40.40.40.40, 100.100.100.100, 226.1.1.1, 12345678, port-3, Down-A". Then, a message (file) with the same opinion is constructed. The message deletes the opinion content based on the original message, and adds a matching customer name that is the same as the opinion, such as Down-A. According to the (S, G) information in the message, the file is sent upstream from the inbound interface of the (S, G) multicast forwarding entry.

[0177] 3. Reply Message and Its Processing

[0178] After receiving all the feedback from customers, the upstream designer will reply to each type of opinion and generate a multicast reply file, which contains the same serial number as the design draft and the customer's name. For messages with similar opinions, no separate reply file will be generated. In this way, the number of reply files is less than the number of feedback from downstream customers, which reduces pressure and saves bandwidth. It is also sent in the form of multicast 226.1.1.1.

[0179] After receiving the reply, the router first analyzes the customer name and serial number in the reply file. If there is no entry in the local record that matches both the customer name and serial number, the reply file is directly discarded and no longer forwarded downstream - avoiding the forwarding of invalid messages.

[0180] If there is a table entry that matches both the customer name and the serial number, the reply file is sent out from the "device port number" of the corresponding table entry. For example, if the received reply file contains the customer name "Down-B" and the serial number "12345678", the message is sent out from port port-2 according to the record entry to avoid forwarding the message from an irrelevant port. In addition, the cached feedback opinions bound to the record are deleted to avoid wasting storage space.

[0181] If there is not only a table entry that matches both the customer name and the serial number, but also the customer name is the same as the matching customer name of another table entry, for example, the received reply file contains the customer name "Down-A" and the serial number "12345678", then two processes need to be performed. The first is to send the reply file from the "device port number" of the corresponding table entry, such as port-1, as in the previous step. The second is to construct a reply file, modify the customer name in the original reply file to "Down-C", and send the reply file from port-3. In addition, delete the cached feedback bound to the record.

[0182] It can be seen that the upstream designer sends the target file and identifier to multiple downstream customers through the multicast node of the multicast network; the downstream customers receive the target file and identifier, generate a feedback file for the target file and return it to the upstream multicast node; the multicast node caches each feedback file, merges the feedback files with similarity higher than the preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback files to the upstream designer; the upstream designer receives the feedback files of all downstream customers and generates reply files respectively, and sends the reply files to the multicast node; the multicast node analyzes and discards the invalid reply files in the reply files, sends the reply files that are not discarded to the downstream customers, and deletes the corresponding cached feedback files to realize intelligent collaboration between upstream and downstream, thereby simplifying the file processing process, reducing network bandwidth occupancy, and improving the efficiency of upstream and downstream collaborative work.

[0183] Another embodiment of the present invention provides a file processing system for upstream and downstream intelligent collaboration, see Figure 3 , the system may include:

[0184] The first sending module 301 is used for an upstream designer to send a target file and its identifier to multiple downstream clients through a multicast node of a multicast network;

[0185] A first generating module 302, configured for a downstream client to receive the target file and its identifier, generate a feedback file for the target file, and return the feedback file to an upstream multicast node;

[0186] Merging module 303, used for the multicast node to cache each feedback file, merge feedback files with similarity higher than a preset threshold, and send feedback files with similarity lower than the preset threshold and the merged feedback file to the upstream designer;

[0187] The second generation module 304 is used for the upstream designer to receive the feedback files of all downstream customers and generate corresponding reply files respectively, and send the reply files to the multicast node;

[0188] The second sending module 305 is used for the multicast node to analyze and discard invalid reply files in the reply files, send the reply files that are not discarded to downstream customers, and delete the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0189] It can be seen that the upstream designer sends the target file and identifier to multiple downstream customers through the multicast node of the multicast network; the downstream customers receive the target file and identifier, generate a feedback file for the target file and return it to the upstream multicast node; the multicast node caches each feedback file, merges the feedback files with similarity higher than the preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback files to the upstream designer; the upstream designer receives the feedback files of all downstream customers and generates reply files respectively, and sends the reply files to the multicast node; the multicast node analyzes and discards the invalid reply files in the reply files, sends the reply files that are not discarded to the downstream customers, and deletes the corresponding cached feedback files to realize intelligent collaboration between upstream and downstream, thereby simplifying the file processing process, reducing network bandwidth occupancy, and improving the efficiency of upstream and downstream collaborative work.

[0190] An embodiment of the present invention further provides a storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0191] Specifically, in this embodiment, the above storage medium may be configured to store a computer program for performing the following steps:

[0192] S201, the upstream designer sends the target file and its identifier to multiple downstream clients through the multicast node of the multicast network;

[0193] S202, the downstream client receives the target file and its identifier, generates a feedback file for the target file and returns it to the upstream multicast node;

[0194] S203, the multicast node caches each feedback file, merges the feedback files whose similarity is higher than a preset threshold, and sends the feedback files whose similarity is not higher than the preset threshold and the merged feedback file to the upstream designer;

[0195] S204, the upstream designer receives the feedback files of all downstream customers and generates corresponding reply files respectively, and sends the reply files to the multicast node;

[0196] S205, the multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream customers, and deletes the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0197] It can be seen that the upstream designer sends the target file and identifier to multiple downstream customers through the multicast node of the multicast network; the downstream customers receive the target file and identifier, generate a feedback file for the target file and return it to the upstream multicast node; the multicast node caches each feedback file, merges the feedback files with similarity higher than the preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback files to the upstream designer; the upstream designer receives the feedback files of all downstream customers and generates reply files respectively, and sends the reply files to the multicast node; the multicast node analyzes and discards the invalid reply files in the reply files, sends the reply files that are not discarded to the downstream customers, and deletes the corresponding cached feedback files to realize intelligent collaboration between upstream and downstream, thereby simplifying the file processing process, reducing network bandwidth occupancy, and improving the efficiency of upstream and downstream collaborative work.

[0198] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0199] Specifically, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0200] Specifically, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0201] S201, the upstream designer sends the target file and its identifier to multiple downstream clients through the multicast node of the multicast network;

[0202] S202, the downstream client receives the target file and its identifier, generates a feedback file for the target file and returns it to the upstream multicast node;

[0203] S203, the multicast node caches each feedback file, merges the feedback files whose similarity is higher than a preset threshold, and sends the feedback files whose similarity is not higher than the preset threshold and the merged feedback file to the upstream designer;

[0204] S204, the upstream designer receives the feedback files of all downstream customers and generates corresponding reply files respectively, and sends the reply files to the multicast node;

[0205] S205, the multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream customers, and deletes the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

[0206] It can be seen that the upstream designer sends the target file and identifier to multiple downstream customers through the multicast node of the multicast network; the downstream customers receive the target file and identifier, generate a feedback file for the target file and return it to the upstream multicast node; the multicast node caches each feedback file, merges the feedback files with similarity higher than the preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback files to the upstream designer; the upstream designer receives the feedback files of all downstream customers and generates reply files respectively, and sends the reply files to the multicast node; the multicast node analyzes and discards the invalid reply files in the reply files, sends the reply files that are not discarded to the downstream customers, and deletes the corresponding cached feedback files to realize intelligent collaboration between upstream and downstream, thereby simplifying the file processing process, reducing network bandwidth occupancy, and improving the efficiency of upstream and downstream collaborative work.

[0207] The above describes in detail the structure, features and effects of the present invention based on the embodiments shown in the drawings. The above is only a preferred embodiment of the present invention, but the present invention is not limited to the scope of implementation shown in the drawings. Any changes made according to the concept of the present invention, or modifications to equivalent embodiments with equivalent changes, which still do not exceed the spirit covered by the description and drawings, should be within the protection scope of the present invention.

Claims

1. A file processing method for upstream and downstream intelligent collaboration, characterized in that: The method comprises: The upstream designer sends the target file and its identifier to multiple downstream clients through the multicast nodes of the multicast network; The downstream client receives the target file and its identifier, generates a feedback file for the target file and returns it to the upstream multicast node; The multicast node caches each feedback file, merges the feedback files with similarity higher than a preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback file to the upstream designer; the multicast node caches each feedback file, merges the feedback files with similarity higher than a preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback file to the upstream designer, including: The upstream multicast node compares the feedback opinions in the feedback files containing the same identifier, caches the feedback opinions whose similarity is not higher than the preset threshold, and records the multicast source address, multicast group address, client's own IP address and name, identifier of the target file and port number of the device receiving the feedback opinion; The first feedback and the second feedback whose similarity is higher than a preset threshold are regarded as the same feedback, the first feedback is cached, and the multicast source address of the first feedback, the multicast group address, the client's own IP address and name, the identifier of the target file, and the port number of the device receiving the first feedback are recorded; Constructing and recording a file of similar opinions of the second feedback, wherein the file of similar opinions includes: a multicast source address, a multicast group address, a client's own IP address and name, an identifier of a target file, a port number information of a device receiving the second feedback, and a name of a client of the first feedback; Sending feedback files corresponding to feedback opinions whose similarity is not higher than a preset threshold, feedback files corresponding to the first feedback opinions, and feedback files that are identical to the second feedback opinions to the upstream designer; The upstream designer receives the feedback files from all downstream customers and generates corresponding reply files respectively, and sends the reply files to the multicast node; The multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream customers, and deletes the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

2. The method according to claim 1, characterized in that The multicast network includes: a (S, G) multicast distribution tree, wherein S is the multicast source address of the upstream designer, and G is the multicast group address.

3. The method according to claim 2, characterized in that The feedback file includes: feedback, multicast source address, multicast group address, client's own IP address and name, and identifier of target file.

4. The method according to claim 3, characterized in that The reply file includes: reply opinions, identifier of target file and name of client; The multicast node analyzes and discards invalid reply files in the reply files, sends the reply files that are not discarded to downstream clients, and deletes the corresponding cached feedback files, including: The multicast node analyzes whether the customer name and identifier in the reply file match the recorded customer name and identifier simultaneously; If they do not match at the same time, the reply file is discarded; If there is a match at the same time and the recorded customer name corresponds to only one feedback, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the downstream customer through the corresponding device port, and delete the feedback corresponding to the customer name and identifier; If the customer name that is matched and recorded corresponds to a feedback and an opinion-similar file at the same time, find the device port number information corresponding to the recorded customer name and identifier, send the reply file to the corresponding downstream customer through the corresponding device port, delete the feedback corresponding to the customer name and identifier, and modify the customer name in the reply file to the customer name in the corresponding opinion-similar file, and send the modified reply file to the corresponding downstream customer through the device port recorded in the opinion-similar file.

5. A file processing system with upstream and downstream intelligent collaboration, characterized in that: The system comprises: The first sending module is used for the upstream designer to send the target file and its identifier to multiple downstream clients through the multicast node of the multicast network; A first generating module, configured for a downstream client to receive the target file and its identifier, generate a feedback file for the target file and return the feedback file to an upstream multicast node; A merging module is used for the multicast node to cache each feedback file, merge the feedback files with similarity higher than a preset threshold, and send the feedback files with similarity not higher than the preset threshold and the merged feedback file to the upstream designer; the multicast node caches each feedback file, merges the feedback files with similarity higher than the preset threshold, and sends the feedback files with similarity not higher than the preset threshold and the merged feedback file to the upstream designer, including: The upstream multicast node compares the feedback opinions in the feedback files containing the same identifier, caches the feedback opinions whose similarity is not higher than the preset threshold, and records the multicast source address, multicast group address, client's own IP address and name, identifier of the target file and port number of the device receiving the feedback opinion; The first feedback and the second feedback whose similarity is higher than a preset threshold are regarded as the same feedback, the first feedback is cached, and the multicast source address of the first feedback, the multicast group address, the client's own IP address and name, the identifier of the target file, and the port number of the device receiving the first feedback are recorded; Constructing and recording a file of similar opinions of the second feedback, wherein the file of similar opinions includes: a multicast source address, a multicast group address, a client's own IP address and name, an identifier of a target file, a port number information of a device receiving the second feedback, and a name of a client of the first feedback; Sending feedback files corresponding to feedback opinions whose similarity is not higher than a preset threshold, feedback files corresponding to the first feedback opinions, and feedback files that are identical to the second feedback opinions to the upstream designer; The second generation module is used for the upstream designer to receive the feedback files of all downstream customers and generate corresponding reply files respectively, and send the reply files to the multicast node; The second sending module is used for the multicast node to analyze and discard invalid reply files in the reply files, send the reply files that are not discarded to downstream customers, and delete the corresponding cached feedback files to achieve intelligent collaboration between upstream and downstream.

6. The system according to claim 5, characterized in that The multicast network includes: a (S, G) multicast distribution tree, wherein S is the multicast source address of the upstream designer, and G is the multicast group address.

7. The system according to claim 6, characterized in that The feedback file includes: feedback, multicast source address, multicast group address, client's own IP address and name, and identifier of target file.

8. A storage medium, characterized in that: The storage medium stores a computer program, wherein the computer program is configured to execute the method according to any one of claims 1 to 4 when executed.

9. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to run the computer program to perform the method according to any one of claims 1 to 4.