Network communication system and communication method for CPS

Abstract

The invention relates to the technical field of communication, and provides a network communication system and method for CPS, and the system comprises a plurality of network nodes, and each network node carries out the following steps: after receiving a request, sending a receiving feedback signal to an upper-level network node, and forwarding the request to a lower-level network node, waiting for a receiving feedback signal and an execution feedback signal fed back by the next-level network node; and after the execution feedback signal is received, the execution feedback signal is transmitted to the upper-level network node once. According to the scheme, the feedback mechanism is optimized, redundant signal transmission is reduced, the communication overhead of the CPS system can be remarkably reduced, and the response speed and reliability of the system are improved.

Description

Technical Field

[0001] The present disclosure belongs to the field of communication technology, and in particular to a network communication system and a communication method for CPS. Background Art

[0002] In current wireless communication networks, in the actual application of CPS, the system usually adopts a layered network architecture, and service requests need to be processed and fed back across multiple network nodes.

[0003] To ensure the accuracy and reliability of business operations, existing CPS real-time networks generally use RPC (Remote Procedure Call) agents and dual feedback mechanisms (see Figure 4 ). That is, for each business operation request, the RPC proxy will first return a "received" feedback, and then return a "completed" feedback after the target service completes the operation. This feedback process needs to be repeated at each layer of network nodes.

[0004] However, as the scale of CPS systems increases and the number of network layers increases, the communication overhead caused by this dual feedback mechanism increases exponentially (see Figure 5 ); There are the following obvious disadvantages: 1) Communication overhead increases exponentially; each layer of network nodes requires two responses (received, completed). In an N-layer structure, the total number of responses is as high as N(N+1). As the system scales up and the number of layers increases, the communication volume expands rapidly, greatly increasing the network load. 2) Increased system response delays and reduced real-time performance: Multi-level and repeated feedback lengthens the overall business process and increases end-to-end response time, making it difficult to meet the high real-time performance requirements of CPS. 3) It is easy to cause network congestion and service blockage. A large number of redundant feedback messages transmitted in the network may cause network congestion and even service blockage, affecting system reliability and stability. Existing methods such as data compression, batch processing, and message merging mainly target the data itself. They are powerless against the structural redundancy caused by protocol mechanisms (such as dual feedback) and cannot fundamentally solve the problem. Although optimizing the network topology or simplifying the protocol can reduce the load, it usually requires large-scale system transformation, which has high implementation costs and poor compatibility. Summary of the Invention

[0005] To solve the above problems, the present disclosure provides a network communication system and communication method for CPS, which adopts a hierarchical task management and feedback merging mechanism, and can compress the N(N+1) signal interactions of the traditional dual feedback mechanism to 2N times, thereby reducing the network load; and improving communication efficiency while ensuring reliability.

[0006] The following is the technical content of this disclosure: A network communication system for CPS, comprising: Multiple network nodes, each network node performs the following steps: After receiving the request, it sends a reception feedback signal to its upper-level network node, and forwards the request to the lower-level network node, waiting for the reception feedback signal and execution feedback signal fed back by the lower-level network node; After receiving the execution feedback signal, the execution feedback signal is transmitted to the upper level network node.

[0007] Further, After receiving the request, the network node sets a timeout period for receiving the feedback signal in the network node; If the time for the network node to receive the feedback signal times out, the request is forwarded to the next level network node again.

[0008] Further, When the network node receives a request from an upper layer, it generates a task in the node and generates a unique task ID for the task; the operations of the network node and all its subordinate network nodes are managed by a unified task; When the network node receives the execution feedback, it ends the task and transmits the execution feedback signal to the upper-level network node.

[0009] Further, After the network node receives the feedback signal, a reception timeout period for executing the feedback signal is set in the network node; If the time for the network node to receive the execution feedback signal times out, the task is terminated and no execution feedback signal is sent to the next higher level network node.

[0010] Further, After receiving the execution feedback signal, the network node sets an execution feedback signal flag in the network node.

[0011] Further, After receiving the reception feedback signal, the network node sets a reception feedback signal flag in the network node.

[0012] Further, The network nodes include a top-level control center, a middle network layer, and a bottom-level terminal; The top-level control center is used to receive requests sent by the client and send them down to the middle network layer; the middle network layer is composed of multiple levels of network nodes and is used to forward the requests sent by the client to the bottom-level terminal; the bottom-level terminal is used to perform specific operations according to the request and pass the execution feedback signal to the middle network layer.

[0013] Further, The top-level control center also records the information of each node and forms a global operation log with the information of each node; The node information includes: task ID, exception type, and operation status.

[0014] A communication method based on the network communication system for CPS, comprising: When any network node receives a request from an upper layer, it performs the following steps: Generate a unique task ID and set a timeout for receiving feedback for the task; Return a reception feedback signal carrying the task ID to the upper-level node that sent the request; Forward the request and task ID to the next level node and start the feedback receiving timeout timer; If the receiving feedback signal from the next-level node is received within the timeout period, the execution feedback timeout period is set and the execution feedback signal carrying the task ID is continued to be waited for; If no response is received within the feedback timeout, the request is forwarded to the next level node at most M times and the timer is reset; After receiving the execution feedback signal from the next-level node, the consistency of the task ID is verified. If it matches, the execution feedback signal is forwarded to its upper-level node and the task is marked as completed.

[0015] Further, When the network node processes the execution feedback signal, the following steps are also included: Verify that the task ID carried in the execution feedback signal is consistent with the task ID recorded locally; If the task ID matches and the signal is received within the execution feedback timeout, the task status is updated to completed and the receive feedback timeout timer is deleted; If the task ID does not match or the execution feedback timeout period has expired without receiving a signal, the task is marked as abnormal and an error log containing the error code and timestamp is recorded. The abnormal information is not passed to the upper-level node. Based on the task status reported periodically by each node, a global operation log is generated containing the task ID, processing node, completion time, and exception type.

[0016] Compared with the prior art, the present disclosure has the following advantages: The present invention solves the technical problems in the background technology through an innovative feedback mechanism design, and changes the signal interaction logic between network nodes; When any network node receives a request, it immediately sends a reception feedback signal to the upper-level node to confirm receipt of the request and forwards the request to the lower-level node. This design synchronizes the transmission of the reception feedback signal with the request forwarding process, avoiding the redundant waiting for execution results in the traditional dual feedback mechanism and reducing unnecessary signal retention time. After receiving the execution feedback signal from the next-level node, the node only needs to transmit the execution feedback signal once to the previous-level node. By constructing transactions at each layer and introducing a timeout mechanism and notification flag, multiple replies can be merged and returned in one go, significantly reducing the number of signal interactions. This mechanism optimizes the traditional N(N+1) signal interactions in which each node needs to return two feedbacks (receive and execute) to 2N times through hierarchical processing of reception feedback and execution feedback, fundamentally reducing the exponential growth of communication overhead caused by the increase in layers. At the same time, the instant sending of reception feedback and the parallel processing of request forwarding reduce the serial waiting links in the business process, shorten the end-to-end response time, and improve the real-time performance of the system.

[0017] Other features and advantages of the present disclosure will be described in the following description, and in part will become apparent from the description, or will be understood by practicing the present disclosure. The purposes and other advantages of the present disclosure can be realized and obtained by the structures indicated in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 Shown is a schematic diagram of the system of the present invention; Figure 2 A schematic diagram of the information interaction method of the present invention is shown; Figure 3 Shown is a flow chart of the network node RPC proxy of the present invention; Figure 4 A schematic diagram of an existing RPC proxy and dual feedback mechanism is shown; Figure 5 A schematic diagram of information interaction in an existing dual feedback mechanism is shown. DETAILED DESCRIPTION

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0021] The system architecture of the present disclosure is as follows Figure 1 As shown, including: A top-level control center, an intermediate network layer, and bottom-level terminals; the top-level control center receives requests from clients and sends them to the intermediate network layer; the intermediate network layer, composed of multiple levels of network nodes, forwards requests from clients to the bottom-level terminals; the bottom-level terminals execute specific operations based on the requests and transmit execution feedback signals to the middle network layer; in, The top-level control center is typically a high-performance server cluster deployed in the CPS system room. Its functions include: serving as the entry point for client requests, managing task ID generation, maintaining the network-wide node registry (including metadata such as node IP, port, load status, and communication protocol version), enabling real-time storage and retrieval of global operation logs, and supporting fault location and performance analysis. The middle network layer consists of edge computing nodes or industrial gateways, deployed in production lines, substations and other on-site environments. Its functions are: serving as an intermediate station for request forwarding; The underlying endpoint is used to execute client requests.

[0022] The top-level control center, the middle network layer and the bottom-level terminal are all network nodes in the communication system. Their information interaction is as follows: Figure 2 As shown, specifically: Step 1: Client request initiated: The client sends the business operation request to the top-level control center of the CPS system; Step 2: Task initialization and ID generation: After receiving the request, the RPC proxy creates a root task and sets the global timeout T0; The top-level control center generates a unique task ID and associates the ID with all subtasks of this request; Step 3: Receive feedback confirmation: The RPC proxy returns an initial response to the client indicating that the request has been received, including the task ID. Step 4: Request layer-by-layer forwarding and receipt confirmation: The top-level control center forwards the request to the middle network layer and starts the receiving feedback timeout timer T1; The middle network layer receives the request and generates a subtask ID; The middle network layer returns the reception feedback with the subtask ID to the upper layer, forwards the request to the bottom terminal, and starts the reception feedback timeout timer T2; The bottom terminal repeats similar operations; Step 5: Execute feedback timeout settings: After receiving the feedback from the lower layer, each node sets the execution feedback timeout T3 (T3 ≤ global timeout T0) and records the feedback status (such as "acknowledgement received from the lower layer"). Step 6: Business execution and result feedback: The bottom terminal executes the business logic and generates the execution result. The bottom terminal returns the execution feedback (including task ID and operation result) to the middle network layer. Step 7: Execute feedback layer by layer and end the task: The task ID in the intermediate network layer verification execution feedback: If it matches and has not timed out, mark the subtask as "completed" and delete the receive feedback timer.

[0023] If there is no match or timeout, it is marked as "abnormal" and an error log (including error code and timestamp) is recorded; The middle network layer returns execution feedback to the upper layer, which includes the processing results of this layer; The top-level control center repeats the above verification process and finally returns the complete execution results to the client; Step 8: Timeout and exception handling: If the waiting time for the lower layer to receive feedback times out: retry the forwarding request (up to M times), resetting the timer each time; if there is still no response after all retries are exhausted, mark the task as "forwarding failed" and return an error code to the upper layer; If the waiting time for execution feedback times out (T3): the task is marked as "execution timed out", a log is recorded but the timeout information is not actively passed to the upper layer; If the task ID verification fails: it is marked as "ID inconsistent" and the exception is only recorded locally; Effect: The existing solution has deficiencies in anomaly detection and timeout handling, making it difficult to achieve both high reliability and high efficiency. Step 8 can effectively perform anomaly detection and timeout handling.

[0024] Step 9: Global Logging and Monitoring: The top-level control center collects the task status of each node (including task ID, processing node, timestamp, and exception type); and generates a global operation log for system auditing, performance analysis, and fault tracing.

[0025] Figure 3 The following is a flowchart of the network node RPC proxy based on the above system, specifically including: When any network node receives a request from an upper layer, it performs the following steps: Generate a unique task ID and set a timeout for receiving feedback for the task; Return a reception feedback signal carrying the task ID to the upper-level node that sent the request; Forward the request and task ID to the next level node and start the feedback receiving timeout timer; If the receiving feedback signal from the next-level node is received within the timeout period, the execution feedback timeout period is set and the execution feedback signal carrying the task ID is continued to be waited for; If no response is received within the feedback timeout, the request is forwarded to the next level node at most M times and the timer is reset; After receiving the execution feedback signal from the next-level node, the consistency of the task ID is verified. If it matches, the execution feedback signal is forwarded to its upper-level node and the task is marked as completed.

[0026] The following are significant technological advancements brought about by the disclosed technical solution: 1) Significantly reduced communication overhead: Through layered transactions and feedback merging, the original N(N+1) feedbacks are compressed to 2N times, significantly reducing network load and improving system throughput.

[0027] 2) Improved response speed and real-time performance: Optimizing feedback paths and reducing redundant waiting significantly shortens the end-to-end response time of business operations, meeting the strict real-time requirements of CPS.

[0028] 3) Enhanced system stability and reliability: Timeout mechanisms and transaction rollbacks ensure that the system can self-heal in abnormal situations, improving overall robustness.

[0029] 4) Comprehensive security improvement: Multiple security mechanisms prevent data leakage, illegal operations and malicious attacks, and ensure business continuity.

[0030] 5) Strong versatility and scalability: The technical solution is applicable to various CPS real-time network scenarios and can be flexibly expanded to system environments of different scales and structures.

[0031] Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A network communication system for CPS, characterized in that: include: Multiple network nodes, each network node performs the following steps: After receiving the request, it sends a reception feedback signal to its upper-level network node, and forwards the request to the lower-level network node, waiting for the reception feedback signal and execution feedback signal fed back by the lower-level network node; After receiving the execution feedback signal, the execution feedback signal is transmitted to the upper level network node.

2. The system according to claim 1, wherein: After receiving the request, the network node sets a timeout period for receiving the feedback signal in the network node; If the time for the network node to receive the feedback signal times out, the request is forwarded to the next level network node again.

3. The system according to claim 1, wherein: When the network node receives a request from an upper layer, it generates a task in the node and generates a unique task ID for the task; the operations of the network node and all its subordinate network nodes are managed by a unified task; When the network node receives the execution feedback, it ends the task and transmits the execution feedback signal to the upper-level network node.

4. The system according to claim 3, characterized in that After the network node receives the feedback signal, a reception timeout period for executing the feedback signal is set in the network node; If the time for the network node to receive the execution feedback signal times out, the task is terminated and no execution feedback signal is sent to the next higher level network node.

5. The system according to claim 1, wherein: After receiving the execution feedback signal, the network node sets an execution feedback signal flag in the network node.

6. The system according to claim 1, wherein: After receiving the reception feedback signal, the network node sets a reception feedback signal flag in the network node.

7. The system according to claim 1, wherein: The network nodes include a top-level control center, a middle network layer, and a bottom-level terminal; The top-level control center is used to receive requests sent by the client and send them down to the middle network layer; the middle network layer is composed of multiple levels of network nodes and is used to forward the requests sent by the client to the bottom-level terminal; the bottom-level terminal is used to perform specific operations according to the request and pass the execution feedback signal to the middle network layer.

8. The system according to claim 7, characterized in that The top-level control center also records the information of each node and forms a global operation log with the information of each node; The node information includes: task ID, exception type, and operation status.

9. A communication method for a network communication system for CPS according to claim 1, characterized in that: include: When any network node receives a request from an upper layer, it performs the following steps: Generate a unique task ID and set a timeout for receiving feedback for the task; Return a reception feedback signal carrying the task ID to the upper-level node that sent the request; Forward the request and task ID to the next level node and start the feedback receiving timeout timer; If the receiving feedback signal from the next-level node is received within the timeout period, the execution feedback timeout period is set and the execution feedback signal carrying the task ID is continued to be waited for; If no response is received within the feedback timeout, the request is forwarded to the next level node at most M times and the timer is reset; After receiving the execution feedback signal from the next-level node, the consistency of the task ID is verified. If it matches, the execution feedback signal is forwarded to its upper-level node and the task is marked as completed.

10. The method according to claim 9, characterized in that When the network node processes the execution feedback signal, the following steps are also included: Verify that the task ID carried in the execution feedback signal is consistent with the task ID recorded locally; If the task ID matches and the signal is received within the execution feedback timeout, the task status is updated to completed and the receive feedback timeout timer is deleted; If the task ID does not match or the execution feedback timeout period has expired without receiving a signal, the task is marked as abnormal and an error log containing the error code and timestamp is recorded. The abnormal information is not passed to the upper-level node. Based on the task status reported periodically by each node, a global operation log is generated containing the task ID, processing node, completion time, and exception type.

Images