Tsn online planning method and device adaptive to link change

Abstract

The application discloses a TSN online planning method and device suitable for link changes, and the method steps comprise the following: obtaining initial network topology structure information and traffic information, generating initial gating configuration information, and storing the gating configuration information into a historical data management module; listening to link change announcement information sent by a network controller; when the link change announcement information is listened to, updating a network topology structure according to an announcement type in the link change announcement information and historical network topology structure information and traffic information obtained from the historical data management module, and if the announcement type is a link failure, re-planning a traffic path according to the updated network topology structure; and when the link failure is listened to, re-allocating time slot resources of the re-planned path in the updated network topology structure. The application can automatically update a network topology, re-plan a traffic path and re-allocate time slot resources in response to dynamic changes of links, and high availability and stability of the network are realized.

Description

Technical Field

[0001] The present invention relates to the technical field of Time-Sensitive Networking (TSN), and in particular to a TSN online planning method and device that adapts to link changes. Background Art

[0002] Time-Sensitive Networking (TSN), an emerging deterministic Ethernet technology, boasts low latency, high reliability, and deterministic transmission. It is being increasingly adopted in high-end equipment applications such as industrial manufacturing systems, rail transit, automotive, and aerospace equipment, where real-time and reliability requirements are paramount. The stable operation of TSN networks is crucial in these applications. Traffic planning plays a central role in the deployment and operation of TSN networks, generating network configurations. The network controller then applies these configurations to network devices to ensure efficient and stable network operation.

[0003] Existing TSN planning and configuration methods typically employ static planning and configuration. These methods primarily generate a network configuration based on pre-set traffic requirements and network topology during the initial deployment phase and then apply it to network devices. However, in real-world scenarios, environmental factors, device failures, or human intervention can cause link changes. Traditional static TSN planning and configuration methods lack dynamic adaptation mechanisms for these link changes. Consequently, once a link change occurs, traditional approaches often require suspending network operations, manually modifying requirements, rerunning the planner, and manually applying the updated configuration to network devices. This not only increases operational complexity and costs but also leads to significant delays in system response, making it difficult to ensure network stability and reliability. Furthermore, traditional static TSN planning and configuration methods lack flexibility in updating network configurations when links change. They fail to fully utilize historical information and real-time link change notifications, making it difficult to dynamically adjust network resource allocation. This significantly limits the TSN network's adaptability in complex and changing environments and also impacts network availability and stability, making it difficult to achieve high availability and stability. Summary of the Invention

[0004] The technical problem to be solved by the present invention is: In response to the technical problems existing in the prior art, the present invention provides a TSN online planning method and device that adapts to link changes. By introducing a dynamic adjustment mechanism, it can automatically update the network topology in response to dynamic changes in links, re-plan traffic paths and reallocate time slot resources, so that the network after dynamic changes in links can still meet the transmission requirements of traffic, thereby achieving high availability and stability of the network.

[0005] To solve the above technical problems, the technical scheme provided by the present application is:

[0006] A TSN online planning method suitable for link changes, comprising the following steps:

[0007] Obtain initial network topology information and traffic information, and generate initial gating configuration information according to the obtained initial network topology information and traffic information, store the initial network topology information, traffic information and corresponding gating configuration information into a historical data management module, and the gating configuration information includes time slot allocation strategies for different traffic on each link;

[0008] Listen to link change announcement information sent by a network controller, the link change announcement information is generated by the network controller when a network link fails or a new link is accessed, the link change announcement information includes announcement types and attribute information of changed links, and the announcement types include link addition and link failure;

[0009] When the link change announcement information is listened to, update the network topology according to the announcement type in the link change announcement information and the historical network topology information and traffic information obtained from the historical data management module, and if the announcement type is link failure, re-plan the traffic path according to the updated network topology after the network topology is updated;

[0010] When the link change announcement information is listened to and the announcement type is link failure, re-allocate time slot resources of the re-planned path after the traffic path is re-planned, and generate new gating configuration information.

[0011] Further, the initial network topology information and traffic information are obtained by reading a predefined static configuration text or receiving an initial planning request transmitted by the network controller and containing a configuration text, the initial network topology includes connection relationships between network nodes and rate attributes of links, and the traffic information includes sizes of traffic, delay requirements and transmission periods.

[0012] Further, the link change announcement information is listened to and received in real time through dynamic network communication interfaces and the network controller, and the dynamic network communication interfaces and the network controller communicate through an inter-process communication or remote procedure call communication mechanism.

[0013] Further, in the network topology updating, if the announcement type is a link addition type, a link addition announcement encapsulating addition link information is received, attribute information of the current addition link is added to the historical network topology information, and the updated network topology information is returned to the historical data management module for storage.

[0014] Further, the re-planning of the traffic path according to the updated network topology after the network topology is updated if the notification type is a link failure includes: if the notification type is a link failure, the link failure notification encapsulating the failure link information sent by the receiving network controller is received, the information of the failure link in the historical network topology information is deleted, the updated network topology information is obtained, and then returned to the historical data management module for storage, and all traffic passing through the failure link is screened out, and the traffic path is re-planned based on the updated network topology information.

[0015] Further, the re-planning of the traffic path according to the updated network topology after the network topology is updated if the notification type is a link failure includes: if the notification type is a link failure, the link failure notification encapsulating the failure link information sent by the receiving network controller is received, the information of the failure link in the historical network topology information is deleted, the updated network topology information is obtained, and then returned to the historical data management module for storage, and all traffic passing through the failure link is screened out, and the traffic path is re-planned based on the updated network topology information.

[0016] The information of the re-planned traffic path is obtained, and the historical gating configuration information is obtained from the historical data management module, the historical gating configuration information including the time slot allocation strategy of each traffic on each link.

[0017] For each traffic path that needs to be re-planned, the available time slot resources are searched along the re-planned new path according to the obtained historical gating configuration information, and the allocated resources can meet the traffic delay requirement condition, the re-allocated time slot resources are obtained, the new gating configuration is generated, and feedback is given to the network controller.

[0018] Further, if the available time slot resources meeting the condition are found for each hop of the path of the traffic that needs to be adjusted, the new gating configuration is successfully generated, and the new gating configuration is transmitted to the historical data management module together with the traffic information of the updated path for storage, and the gating update configuration information of the nodes corresponding to the failure link is returned to the network controller through a dynamic interface; if the available resources meeting the condition cannot be found on the updated path, the traffic is searched for a feasible path.

[0019] A TSN online planning device suitable for link changes includes:

[0020] A historical data management module for storing network topology information, traffic information, and gating configuration information.

[0021] An initial planning module, configured to obtain initial network topology information and traffic information, generate initial gating configuration information based on the obtained initial network topology information and traffic information, and store the initial network topology information, traffic information, and corresponding gating configuration information in a historical data management module, wherein the gating configuration information includes a time slot allocation strategy for different traffic flows on each link;

[0022] A monitoring module, configured to monitor link change notification information sent by a network controller. The link change notification information is generated by the network controller when a network link fails or a new link is added. The link change notification information includes a notification type and attribute information of the changed link. The notification type includes link addition and link failure.

[0023] a path update module configured to, upon receiving the link change notification information, update the network topology according to the notification type in the link change notification information and the historical network topology information and traffic information obtained from the historical data management module; and if the notification type is a link failure, replan the traffic path according to the updated network topology after updating the network topology;

[0024] The resource adjustment module is used to, when monitoring the link change notification information and the notification type is link failure, re-plan the traffic path, reallocate the time slot resources of the re-planned path, and generate new gating configuration information.

[0025] A computer device includes a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program to perform the above method.

[0026] A computer-readable storage medium storing a computer program, wherein the computer program implements the above method when executed by a processor.

[0027] Compared with the prior art, the present invention has the following beneficial effects:

[0028] 1. The present invention realizes dynamic interaction with the network controller by introducing a dynamic adjustment mechanism. During the operation of the network, it dynamically obtains the link change notification information perceived by the network controller, updates the path and adjusts the resources for different types of incoming link change notification information, and finally generates new gating configuration information to realize dynamic TSN online planning and configuration. It can automatically update the network topology, re-plan the traffic path and reallocate time slot resources based on historical information and real-time link change notification information during the operation of the network, ensuring that the network after dynamic link changes can still meet the transmission requirements of the traffic, thereby achieving high availability and stability of the network.

[0029] 2. The present invention not only ensures the network's rapid response and automatic recovery capabilities when facing dynamic changes in links, but also reduces manual intervention, lowers operation and maintenance costs and complexity, and improves the overall stability and reliability of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 This is a schematic diagram of the implementation flow of the TSN online planning method that adapts to link changes in this embodiment.

[0031] Figure 2 Schematic diagram of the structure and principle of the TSN online planning device of this embodiment.

[0032] Figure 3 This is a schematic diagram of the detailed planning and configuration process of the TSN online planning device in this embodiment to adapt to link changes.

[0033] Figure 4 It is a data structure diagram of the basic unit of dynamic interface data transmission and historical data management module data storage in a specific application embodiment. DETAILED DESCRIPTION

[0034] The present invention will be further described below in conjunction with the accompanying drawings and specific preferred embodiments, but the scope of protection of the present invention is not limited thereby.

[0035] like Figure 1 As shown, the steps of the TSN online planning method for adapting to link changes in this embodiment include:

[0036] Step S01: Obtain initial network topology information and traffic information, and generate initial gating configuration information based on the obtained initial network topology information and traffic information. The initial network topology information, traffic information and corresponding gating configuration information are stored in the historical data management module. The gating configuration information includes the time slot allocation strategy for different traffic on each link.

[0037] Specifically, the initial network topology and traffic information can be obtained by reading a predefined static configuration text. The configuration text can be a file in a format such as JSON or XML, which describes the network's initial topology and traffic demand information. Alternatively, the initial network topology and traffic information can be obtained by receiving an initial planning request containing the configuration text transmitted by a network controller. The initial network topology includes information such as the connection relationship between network nodes and the rate attributes of the link, and the traffic information includes information such as the size of the traffic, delay requirements, and sending period. The planning algorithm used can be selected based on the network planning configuration requirements of different types of characteristics, such as an SMT-based algorithm or a heuristic algorithm.

[0038] Furthermore, based on the acquired initial network topology and traffic information, gating configuration information is generated. This gating configuration information includes a time slot allocation strategy for different traffic flows on each link. In time-sensitive networking (TSN), time is divided into a series of time slots. The time slot allocation strategy is the strategy for allocating time slots to traffic flows of different priorities and types to meet traffic transmission requirements. The initial network topology and traffic flow information, along with the corresponding gating configuration information, is stored in a historical data management module, which is responsible for storing historical network topology information, traffic flow information, and gating configuration information.

[0039] Step S02: Monitor the link change notification information sent by the network controller. The link change notification information is generated by the network controller when a network link fails or a new link is added. The link change notification information includes the notification type and attribute information of the changed link. The notification types include link addition and link failure.

[0040] Specifically, the dynamic network communication interface can interact with the network controller in real time to monitor and receive link change notifications. The dynamic network communication interface and the network controller communicate via mechanisms such as inter-process communication (IPC) or remote procedure call (RPC), ensuring efficient information transfer between the network controller and the TSN planner on the same or different hosts. Furthermore, the communication interface can be configured to support multiple data transmission formats, including binary protocols, JSON, and XML, to meet the needs of different scenarios.

[0041] In this embodiment, by monitoring network status changes in real time, link change notifications generated by the network controller are dynamically received when a link is added or a link fails. These notifications include the notification type (new link or link failure) and relevant attributes of the changed link, including the link sequence number, source node, destination node, link rate, number of queues, source port, and destination port. This approach enables real-time response to network status changes via the dynamic network communication interface, ensuring timely acquisition of link change information and corresponding configuration updates, thereby enabling dynamic network planning and management.

[0042] Step S03: When link change notification information is monitored, the network topology is updated according to the notification type in the link change notification information and the historical network topology information and traffic information obtained from the historical data management module. If the notification type is a link failure, after the network topology is updated, the traffic path is re-planned according to the updated network topology.

[0043] In this embodiment, when a link change notification is monitored, the network topology is updated based on the notification type in the link change notification and the historical network topology information and traffic information obtained from the historical data management module to obtain an updated network topology. If a link failure occurs, the traffic path will be replanned after the network topology is updated. Specifically, it includes:

[0044] a) In the updated network topology structure obtained by path update, if the notification type is a link addition type, the link addition notification encapsulated with the new link information sent by the receiving network controller is added, the attribute information of the current new link is added to the historical network topology structure information, and the updated network topology structure information is returned to the historical data management module for storage.

[0045] b) In the updated network topology obtained through path updating, if the notification type is link failure, the network controller receives a link failure notification encapsulated with the faulty link information and deletes the faulty link information from the historical network topology information. The updated network topology information is then returned to the historical data management module for storage. The module then traverses and filters out all traffic passing through the faulty link. Based on the updated network topology information, traffic paths are re-planned for these traffic paths. In other words, if a link failure occurs, traffic paths will be re-planned after the network topology is updated.

[0046] Specifically, when one or more links are added to the TSN network, the network controller detects these changes and generates a link addition notification that encapsulates the newly added link information. After monitoring the link addition notification in real time, the historical network topology information and traffic information are obtained from the historical data management module. The historical network topology information contains detailed information about all known links, such as link rate, node connection relationship, etc., and then the attribute information of the newly added link is added to the historical topology information and the updated topology is returned to the historical data management module for storage. For example, suppose a new link ab is added to the TSN network. After obtaining the historical network topology information, the attribute information of the newly added link ab (such as source node a, destination node b, link rate 1Gbps, etc.) is added to the topology. By updating the network topology after the newly added link is added, the newly added link ab can be fully utilized to replan the traffic path in the event of a subsequent failed link, ensuring the reliability and efficiency of the network.

[0047] If one or more links in a TSN network fail, a link failure notification encapsulated with the faulty link information is received from the network controller. The historical data management module obtains historical topology and traffic information, which includes all historical link information. After deleting the faulty link information, the updated topology is returned to the historical data management module. The traffic information includes the historical distribution path of each flow, which refers to the path information of the flow before the failure. The flow that passed through the faulty link is further traversed and filtered, and feasible paths are searched and adjusted for these flows based on the updated topology. For example, if the path of flow A is a→b→c, and link bc fails, the path update module will traverse all flows that passed through the faulty link and, based on the updated topology (after deleting the faulty link), use a graph search algorithm (such as the Dijkstra algorithm) to re-route the flow to a→d→c.

[0048] Step S04: When link change notification information is monitored and the notification type is link failure, the traffic path is re-planned, the time slot resources of the re-planned path are reallocated, and new gating configuration information is generated.

[0049] In this embodiment, when link change notification information is monitored and the notification type is link failure, after updating the network topology and replanning the traffic path, the time slot resources of the replanned path are further reallocated to generate new gating configuration information, including:

[0050] Step S401: Obtain information about the re-planned traffic path and obtain historical gating configuration information from the historical data management module. The historical gating configuration information includes a time slot allocation strategy for each flow on each link.

[0051] Step S402: For each traffic path that needs to be replanned, search for available time slot resources hop by hop along the replanned new path based on the acquired historical gating configuration information, and ensure that the allocated resources can meet the traffic delay requirement conditions, obtain the reallocated time slot resources, generate a new gating configuration and feed it back to the network controller.

[0052] Specifically, if the link change notification is a link failure, subsequent resource adjustments are required, and the gating response information is returned to the network controller. First, the traffic information of the adjusted path is obtained to reallocate resources. After receiving the traffic information of the updated path, the historical gating configuration information is obtained from the historical data management module. The historical gating configuration information includes the time slot allocation strategy for each flow on each link. For each flow that needs to be re-routed, the available time slot resources are searched hop by hop along its new path, while ensuring that the allocated resources can meet conditions such as traffic delay requirements. In this way, resource allocation can be dynamically adjusted according to the historical gating configuration information, ensuring that the network can still transmit traffic efficiently and reliably after a link failure.

[0053] For example, suppose traffic A originally traveled along links a→b→c, but link bc failed. During a path update, the path is recalculated and the traffic is redirected to a→d→c. Resource adjustment then occurs, obtaining the time slot allocations for links a→d and d→c from historical gating configuration information. A hop-by-hop search for available time slot resources along the new traffic path is performed. For example, links a→d and d→c are sequentially checked for sufficient time slots to accommodate traffic A, ensuring that the time slot allocations meet the traffic's latency requirements. If all time slots on links a→d or d→c fail to meet the traffic's latency requirements or if no time slots are available, the traffic is redirected to alternative backup links. Throughout this process, it is crucial to ensure that the newly allocated time slots meet both the latency and traffic requirements.

[0054] Furthermore, if available time slot resources that meet the requirements are found at each hop of the path for the traffic to be adjusted, a new gating configuration is successfully generated. The process also includes transferring the new gating configuration along with the traffic information for the updated path to the historical data management module for storage. Meanwhile, the updated gating configuration information for the node corresponding to the faulty link is returned to the network controller via the dynamic interface. If no available resources that meet the requirements are found on the updated path, a new feasible path is searched for the traffic. If a response to the updated gating configuration is successfully returned, a determination is made as to whether the dynamic network communication interface needs to be monitored. If so, the process returns to step S02 and continues monitoring. If not, the online planning state is exited.

[0055] The present invention realizes dynamic interaction with the network controller by introducing a dynamic adjustment mechanism. During the operation of the network, the link change notification information perceived by the network controller is dynamically obtained, and the path and resource adjustment are performed for different types of incoming link change notification information. Finally, new gating configuration information is generated and fed back to the network controller for dynamic configuration to the network, realizing dynamic TSN online planning and configuration. It can automatically update the network topology, re-plan the traffic path and reallocate time slot resources based on historical information and real-time link change notification information during the operation of the network, ensuring that the network after the dynamic change of the link can still meet the transmission requirements of the traffic, that is, after the dynamic change of the network link, the configuration is generated online to meet the transmission requirements of the traffic, and the high availability and stability of the network are achieved. Compared with the traditional static planning and configuration method, the present invention can not only ensure the network's rapid response and automatic recovery capabilities when facing dynamic changes in the link, but also reduce manual intervention, reduce operation and maintenance costs and complexity, and improve the overall stability and reliability of the network. It can be flexibly applied to various fields with dynamic needs and high stability, such as industrial automation, rail transportation, aerospace, etc.

[0056] In order to implement the above method, Figure 2 As shown, the TSN online planning device that adapts to link changes in this embodiment includes:

[0057] Historical data management module, used to store network topology information, traffic information and gating configuration information;

[0058] An initial planning module is used to obtain initial network topology information and traffic information, generate initial gating configuration information based on the obtained initial network topology information and traffic information, and store the initial network topology information, traffic information, and corresponding gating configuration information in the historical data management module. The gating configuration information includes the time slot allocation strategy for different traffic flows on each link;

[0059] A monitoring module is used to monitor link change notification information sent by the network controller. Link change notification information is generated by the network controller when a network link fails or a new link is added. The link change notification information includes the notification type and attribute information of the changed link. The notification types include link addition and link failure;

[0060] The path update module is used to update the network topology when a link change notification is monitored, based on the notification type in the link change notification and the historical network topology information and traffic information obtained from the historical data management module. If the notification type is a link failure, after the network topology is updated, the traffic path is replanned according to the updated network topology;

[0061] The resource adjustment module is used to, when link change notification information is monitored and the notification type is link failure, re-plan the traffic path, reallocate the time slot resources of the re-planned path, and generate new gating configuration information.

[0062] like Figure 2 As shown, this embodiment consists of a historical data management module, an initial planning module, a monitoring module, a path update module, and a resource adjustment module to form a TSN planner. The monitoring module can be implemented using a dynamic network communication interface to monitor link change notifications from the network controller and send the updated gating configuration information of the TSN planner to the network controller, thereby realizing dynamic communication between the network controller and the TSN planner.

[0063] Specifically, the network controller is capable of sensing the status of TSN network links. When a network link fails or a new link is added, it proactively invokes the TSN planner, notifying the TSN planner of perceived link changes and continuously awaiting a response from the TSN planner. Upon receiving the gating configuration response from the planner, it deploys updates to the corresponding network devices. The TSN planner is configured to support dynamic invocation by the network controller, allowing it to receive link change notifications from the network controller via a dynamic network communication interface. It dynamically adjusts resources through the collaboration of working modules such as the path update module and the traffic planning module, and returns the updated gating configuration information to the network controller via the dynamic interface. The network controller and the TSN planner communicate via a dynamic communication interface, which can use any format, such as binary protocol, JSON, or XML. The information transmitted via the dynamic communication interface includes link change notifications and updated gating configuration responses. Link change notifications are the core data structure used by the network controller to convey network topology change information to the TSN planner. They consist of the notification type and the relevant attributes of the changed link. Among them, the notification types are divided into link addition and link failure. Link addition indicates that a new physical or logical link is detected to access the network; link failure indicates the interruption or failure of an existing link.

[0064] In this embodiment, the specific configuration of each module in the TSN planner is as follows:

[0065] The initial planning module is configured to obtain initial network topology and traffic information during system startup to generate the initial gating configuration. This information can be obtained by reading static configuration text or receiving dynamic notifications from the network controller. The gating configuration is generated using a planning algorithm based on, for example, SMT.

[0066] The historical data management module is configured to support the storage and modification of historical topology information, traffic information, and gating configuration information, as well as support the interaction of stored information with other working modules. The stored information is stored using the following data structures: Link class, Stream class, and gating table GclTbl class. In a specific application embodiment, the detailed information structure is as follows: Figure 3 shown.

[0067] The path update module is configured to support updating network topology information based on changed link information and historical topology information. For link failure notifications, it can lock all traffic passing through the faulty link based on the path parameters in the historical traffic. Combined with the updated topology information, it uses a graph search algorithm to search for and adjust feasible paths for the traffic that needs to be replanned.

[0068] The resource adjustment module is configured to work only when the link change notification type is link failure. It supports the reallocation of time slot resources for traffic on the updated path based on historical gating configuration information. That is, for each updated traffic, it searches for available time slot resources hop by hop along its replanned path. During the resource adjustment process, it is necessary to ensure that the allocated resources can meet specific conditions, such as traffic delay requirements, etc.

[0069] Based on the above structure, Figure 3 As shown, the detailed process of implementing TSN online planning that adapts to link changes in this embodiment is as follows:

[0070] Step 1: Initial Planning

[0071] The initial planning module of the TSN planner obtains the initial network topology information and traffic information. After obtaining the initial network and application requirements, the TSN planner selects the corresponding traffic planning algorithm to generate the gating configuration based on the characteristics of the network planning configuration requirements.

[0072] For example, for small-scale simple network topologies, algorithms based on SMT solvers can be used to accurately calculate the gating configuration that meets traffic requirements, while for large-scale complex network structures, heuristic algorithms can be used to quickly find approximate optimal solutions and improve planning efficiency.

[0073] After completing the initial planning, the TSN planner passes the initial topology, traffic information and gating configuration information to the historical data management module for storage. The initial topology structure includes node connection relationships, link attributes, etc., the traffic information includes traffic size, delay requirements, sending cycle, etc., and the gating configuration information includes the time slot allocation strategy for different traffic on each link. The detailed composition of this information corresponds to Figure 4 Definition of the basic unit link (Link) class, flow (Stream) class and gating table (GclTbl) class.

[0074] Step 2: Link change notification monitoring

[0075] After the TSN network enters the running state according to the initial configuration information, the TSN planner interacts with the network controller in real time through the dynamic network communication interface to monitor and receive link change notifications. By monitoring network status changes in real time, the TSN planner can dynamically receive link change notifications generated by the network controller when a link is added or a link fails. The notification information includes the notification type (new link or link failure) and the relevant attributes of the changed link. The definitions of these attributes are as follows: Figure 4 The definition of the basic unit link (Link) class in . Specifically, the relevant attributes of the change link are detailed as follows Figure 4 The structure defined by the basic unit link (Link) class in the update gating configuration response is composed of the gating information of the nodes related to the fault link. The detailed composition is as follows Figure 4 The structure defined by the basic unit gate control table (GclTbl) class in the . With this mechanism, the TSN planner can respond to changes in network status in real time through the dynamic network communication interface, ensuring that the TSN planner promptly obtains link change information and performs corresponding configuration updates, thereby achieving dynamic network planning and management.

[0076] Step 3: Path update when link changes

[0077] When one or more new links are added to the TSN network, the network controller detects these changes and generates a new link notification that encapsulates the new link information, and then passes the notification to the TSN planner. After receiving the new link notification, the path update module of the TSN planner obtains the historical topology and traffic information from the historical data management module. The historical topology information contains detailed information of all known links, such as link rate, node connection relationship, etc. After adding the attribute information of the new link to the historical topology information, the path update module returns the updated topology to the historical data management module for storage. The updated topology information is then returned to the historical data management module for storage, so that in the event of a subsequent failed link, the newly added link can be used to re-plan the traffic path to ensure the reliability and efficiency of the network.

[0078] Step 4: Path update and traffic rerouting in case of link failure

[0079] If one or more links in a TSN network fail, the TSN planner receives a link failure notification from the network controller that encapsulates the faulty link information. The path update module obtains historical topology and traffic information from the historical data management module. The topology information contains all historical links. The path update module deletes the information about the failed link and returns the updated topology to the historical data management module. The traffic information contains the historical distribution path for each flow, which refers to the path information of the flow before the failure occurred. The path update module traverses and filters out the traffic that passed through the faulty link. Based on the updated topology, it searches for and adjusts feasible paths for these flows using graph search algorithms and other methods.

[0080] Step 5: Reallocate time slot resources when a link fails

[0081] If the link change notification indicates a link failure, subsequent resource adjustments are required, and a gating response is returned to the network controller. The path update module passes the traffic information for the adjusted path to the resource adjustment module for resource reallocation. After receiving the traffic information for the updated path, the resource adjustment module obtains historical gating configuration information from the historical data management module. This historical gating configuration includes the time slot allocation strategy for each flow on each link. For each flow that requires rerouting, the resource adjustment module searches for available time slot resources hop by hop along the new path, while ensuring that the allocated resources meet conditions such as the flow delay requirement.

[0082] To illustrate how the resource adjustment module works, let's assume that traffic A originally traveled along links a→b→c, but link bc fails. The path update module recalculates the path and adjusts the traffic flow to a→d→c. The resource adjustment module then retrieves the time slot allocations for links a→d and d→c from historical gating configuration information. The resource adjustment module searches for available time slots hop by hop along the new path for traffic A. For example, the module sequentially checks links a→d and d→c to see if they have enough time slots to accommodate traffic A, while also ensuring that the time slot allocations meet the traffic's latency requirements. If all time slots on links a→d or d→c fail to meet the traffic's latency requirements or if no time slots are available, the resource adjustment module attempts to reroute the traffic to alternative backup links. Throughout this process, the resource adjustment module ensures that the newly allocated time slots meet both the latency and requirements of the traffic flow. In this way, the resource adjustment module dynamically adjusts resource allocation based on historical gating configuration information, ensuring that the network can still efficiently and reliably transmit traffic after a link failure.

[0083] Step 6: Gating update configuration information returned

[0084] If the resource adjustment module finds available time slots that meet the requirements for the traffic to be adjusted at each hop on the path, it successfully generates a new gating configuration and passes it along with the traffic information for the updated path to the historical data management module. The updated gating configuration information for the nodes related to the faulty link is also returned to the network controller via the dynamic interface. If no available resources that meet the requirements are found on the updated path, the module returns to step 4 and searches for a feasible path for the traffic again.

[0085] Step 7: If the updated gating configuration response is successfully returned, determine whether it is necessary to continue monitoring the dynamic network communication interface. If so, return to step 2 and continue monitoring; if not, the TSN planner exits the online planning state.

[0086] This embodiment further provides a computer device, including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program to perform the above method.

[0087] It is understandable that the above method of this embodiment can be executed by a single device, such as a computer or server, etc., and can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In the case of a distributed scenario, one of the multiple devices can only execute one or more steps in the above method of this embodiment, and multiple devices interact to complete the above method. The processor can be implemented in the form of a general-purpose CPU, a microprocessor, an application-specific integrated circuit, or one or more integrated circuits, etc., for executing relevant programs to implement the above method of this embodiment. The memory can be implemented in the form of a read-only memory ROM, a random access memory RAM, a static storage device, and a dynamic storage device. The memory can store an operating system and other application programs. When the above method of this embodiment is implemented by software or firmware, the relevant program code is stored in the memory and called and executed by the processor.

[0088] This embodiment further provides a computer-readable storage medium storing a computer program, which implements the above method when executed by a processor.

[0089] Those skilled in the art will appreciate that the above-described embodiments of the present application can be embodied as a method, system, or computer program product. Accordingly, the present application can be embodied in hardware alone, software alone, or in a combination of software and hardware aspects. Furthermore, the present application can take the form of a computer program product on one or more computer-readable storage media (including, but not limited to, disk memory, CD-ROMs, optical storage devices, etc.) embodying computer program instructions. The present application is described in reference to the flow diagrams and / or block diagrams of the methods, apparatus (systems), and computer program products according to embodiments of the application illustrated in the drawings. It will be understood that each flow and / or block in the flow diagrams and / or block diagrams, and combinations of flows and / or blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processing device, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instructions which implement the flow diagrams and / or block diagrams flow or flows and / or block or blocks specified in the flow diagrams and / or block diagrams. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flow diagrams and / or block diagrams flow or flows and / or block or blocks. Accordingly, the present application is not limited to purely hardware embodiments, but also to software embodiments, software in combination with hardware embodiments, virtual implementations, and distributed implementations. Figure 1 one or more flows and / or blocks Figure 1 one or more blocks or a combination of flows and / or blocks Figure 1 one or more flows and / or blocks Figure 1 one or more blocks or a combination of flows and / or blocks Figure 1 one or more flows and / or blocks Figure 1 one or more blocks or a combination of flows and / or blocks

[0090] The foregoing is merely illustrative of the principles of the application, and the application should not be restricted to such specific embodiments thereof. Although the application has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, the application as set forth is not limited to the embodiments described above, but rather is intended to cover any and all alterations, combinations, sub-combinations, equivalents, modifications or adaptations of the application including its steps disclosed in the claims which follow.

Claims

1. A TSN online planning method that adapts to link changes, characterized by the following steps: include: Obtaining initial network topology information and traffic information, generating initial gating configuration information based on the obtained initial network topology information and traffic information, and storing the initial network topology information, traffic information, and corresponding gating configuration information in a historical data management module, wherein the gating configuration information includes a time slot allocation strategy for different traffic flows on each link; Monitor link change notifications sent by the network controller. The link change notifications are generated by the network controller when a network link fails or a new link is added. The link change notifications include a notification type and attribute information of the changed link. The notification types include link addition and link failure. When the link change notification information is monitored, the network topology is updated according to the notification type in the link change notification information and the historical network topology information and traffic information obtained from the historical data management module. If the notification type is a link failure, after the network topology is updated, the traffic path is re-planned according to the updated network topology, including: if the notification type is a link failure, a link failure notification encapsulated with the faulty link information is received from the network controller, and historical topology and traffic information is obtained from the historical data management module, wherein the topology information contains all historical link information, and the traffic information contains the historical distribution path of each traffic flow, and the historical distribution path of each traffic flow refers to the path information of the traffic flow before the failure occurs. After deleting the information of the faulty link, the updated network topology information is returned to the historical data management module for storage, and all traffic passing through the faulty link is traversed and filtered out, and the traffic path is re-planned for the filtered traffic flow based on the updated network structure topology information, so as to search for and adjust a feasible path for the filtered traffic flow; When the link change notification information is monitored and the notification type is a link failure, after re-planning the traffic path, the time slot resources of the re-planned path are reallocated to generate new gating configuration information, including: Obtaining information about the re-planned traffic path and obtaining historical gating configuration information from a historical data management module, wherein the historical gating configuration information includes a time slot allocation strategy for each flow on each link; For each re-planned traffic path, the system searches for available time slot resources hop by hop along the newly re-planned path based on the historical gating configuration information obtained, and ensures that the allocated resources meet the traffic delay requirements. The system obtains the reallocated time slot resources, generates a new gating configuration, and feeds it back to the network controller.

2. The TSN online planning method for adapting to link changes according to claim 1 is characterized in that: By reading the predefined static configuration text or receiving the initial planning request containing the configuration text transmitted by the network controller, the initial network topology information and traffic information are obtained. The initial network topology information includes the connection relationship between network nodes and the rate attributes of the link. The traffic information includes the size of the traffic, delay requirements and sending cycle.

3. The TSN online planning method for adapting to link changes according to claim 1 is characterized in that: The dynamic network communication interface interacts with the network controller in real time to monitor and receive the link change notification information. The dynamic network communication interface and the network controller communicate via an inter-process communication or remote procedure call mechanism.

4. The TSN online planning method for adapting to link changes according to claim 1, characterized in that: During the network topology update, if the notification type is a link addition type, a link addition notification encapsulated with the new link information is received from the network controller, the attribute information of the current new link is added to the historical network topology information, and the updated network topology information is returned to the historical data management module for storage.

5. The TSN online planning method for adapting to link changes according to claim 1, characterized in that: If available time slot resources that meet the requirements are found at each hop of the path for the traffic that needs to be adjusted, a new gating configuration is successfully generated, which also includes transmitting the new gating configuration and the traffic information of the updated path to the historical data management module for storage, and returning the updated gating configuration information of the node corresponding to the faulty link to the network controller through the dynamic interface; If no available resources that meet the conditions can be found on the updated path, a feasible path is searched for the traffic again.

6. A TSN online planning device that adapts to link changes, characterized in that: include: Historical data management module, used to store network topology information, traffic information and gating configuration information; An initial planning module, configured to obtain initial network topology information and traffic information, generate initial gating configuration information based on the obtained initial network topology information and traffic information, and store the initial network topology information, traffic information, and corresponding gating configuration information in a historical data management module, wherein the gating configuration information includes a time slot allocation strategy for different traffic flows on each link; A monitoring module, configured to monitor link change notification information sent by a network controller. The link change notification information is generated by the network controller when a network link fails or a new link is added. The link change notification information includes a notification type and attribute information of the changed link. The notification type includes link addition and link failure. A path update module is used to update the network topology structure according to the notification type in the link change notification information and the historical network topology structure information and traffic information obtained from the historical data management module when monitoring the link change notification information. If the notification type is a link failure, after the network topology structure is updated, the traffic path is re-planned according to the updated network topology structure, including: if the notification type is a link failure, receiving a link failure notification encapsulated with the faulty link information sent by the network controller, obtaining historical topology and traffic information from the historical data management module, wherein the topology information contains all historical link information, and the traffic information contains the historical distribution path of each traffic flow, and the historical distribution path of each traffic flow refers to the path information of the traffic flow before the failure occurs, deleting the information of the faulty link, returning the updated network topology structure information to the historical data management module for storage, and traversing and filtering out all traffic passing through the faulty link, and re-planning the traffic path for the filtered traffic flow based on the updated network structure topology information, so as to search for and adjust feasible paths for the filtered traffic flow; The resource adjustment module is configured to, when monitoring the link change notification information and the notification type is a link failure, re-plan the traffic path, reallocate the time slot resources of the re-planned path, and generate new gating configuration information, including: Obtaining information about the re-planned traffic path and obtaining historical gating configuration information from a historical data management module, wherein the historical gating configuration information includes a time slot allocation strategy for each flow on each link; For each re-planned traffic path, the system searches for available time slot resources hop by hop along the newly re-planned path based on the historical gating configuration information obtained, and ensures that the allocated resources meet the traffic delay requirements. The system obtains the reallocated time slot resources, generates a new gating configuration, and feeds it back to the network controller.

7. A computer device comprising a processor and a memory, wherein the memory is used to store a computer program, wherein: The processor is configured to execute the computer program to perform the TSN online planning method adapted to link changes according to any one of claims 1 to 5.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the TSN online planning method that adapts to link changes as claimed in any one of claims 1 to 5 is implemented.

Images