A cross-architecture communication method and system based on SRv6 deterministic networks

Abstract

This invention belongs to the field of computer network communication technology and discloses a cross-architecture communication method and system based on SRv6 deterministic networks. It includes: a source node acquiring a service flow, constructing an IPv6 packet, and inserting an extension header into the packet header; assigning a deterministic service identifier to the service flow based on its SLA metrics, and assigning a periodic label based on a local synchronization clock and a scheduling period Tc algorithm; constructing a deterministic flow identifier option based on the deterministic service identifier and the periodic label, and writing it into the extension header; a forwarding node acquiring and parsing the IPv6 packet, querying a locally pre-configured resource mapping table based on the deterministic service identifier to map the IPv6 packet to the forwarding node's QoS queue; sending the IPv6 packets in the QoS queue to the corresponding periodic resource unit based on the periodic label; and forwarding the IPv6 packets in the periodic resource unit according to a preset SRv6 path. This invention can achieve high-precision resource interconnection and interoperability across architectures.

Description

Technical Field

[0001] This invention relates to the field of computer network communication technology, and specifically to a cross-architecture communication method and system based on SRv6 deterministic networks. Background Technology

[0002] Deterministic networking is a network technology designed to eliminate uncertainty in data transmission. Due to its advantages such as low latency, zero packet loss, and low jitter, it is widely used in business scenarios such as industrial control, 5G fronthaul / backhaul, and vehicle networking.

[0003] Existing deterministic network types include: TSN deterministic networks, FlexE deterministic networks, 5GDN deterministic networks, and SRv6 deterministic networks. Among them, SRv6 deterministic networks, as a next-generation network technology, combine segment routing and IPv6 technology. By carrying segmented routing headers in IPv6 packet headers to specify paths, they provide flexible path control capabilities for deterministic services, thus playing an important role in cross-regional data transmission.

[0004] When transmitting data across regions using SRv6 deterministic networks, the network architectures adopted by the source node, each forwarding node, and the tail node are not entirely the same (for example, they may be: the IETF-based DetNet standard architecture, the IEEE 802.1Q / TSN time-sensitive network architecture, or private or semi-private architectures such as DIP and DetNet). However, regardless of the architecture used, the IP 5-tuple identifier or a specific SID identifier set in the SRH extension header is usually used to achieve accurate identification of service flows and resource reservation. However, these identifiers cannot directly provide the abstract service level information and time information required for high-precision scheduling in cross-vendor and cross-architecture situations. This leads to the following technical defects when transmitting data across regions: (1) Lack of unified flow identifiers: The core of deterministic networks lies in the accurate identification of service flows and resource reservation. However, the existing identifiers cannot directly provide the abstract service level information and time information required for high-precision scheduling that are uniformly identified across vendors and cross-architectures. (2) Poor heterogeneous interoperability: Due to the significant differences in underlying resource reservation, queue management, and scheduling mechanisms between different architectures. Therefore, when deterministic service flows need to cross devices from different vendors or with different architectures, the lack of a unified data plane field to guide resource mapping for devices along the way makes it impossible to achieve end-to-end deterministic QoS guarantee. (3) Poor high-precision performance: Achieving microsecond-level jitter requires time synchronization scheduling mechanisms such as TCQF, making it difficult to coordinate and implement high-precision scheduling across vendors or across architecture devices. Summary of the Invention

[0005] The purpose of this invention is to provide a cross-architecture communication method and system based on SRv6 deterministic networks, so as to simultaneously solve the technical problems of lack of unified flow identifier, poor heterogeneous interoperability and poor high-precision scheduling in the current cross-architecture data transmission based on SRv6 deterministic networks.

[0006] To achieve the above objectives, the present invention proposes the following technical solution:

[0007] Firstly, a cross-architecture communication method based on SRv6 deterministic networks is provided. A forwarding module is set up in the router of the SRv6 backbone network, and the forwarding module stores a resource mapping table. The resource mapping table is uniformly configured by the network controller and is used to store various forwarding processing resources corresponding to any deterministic service identifier.

[0008] Includes the following steps:

[0009] The source node obtains the service flow, constructs an IPv6 packet corresponding to the service flow, and inserts a preset type of extension header into the IPv6 packet.

[0010] The network controller assigns a unique deterministic service identifier to the service flow based on its SLA metrics, and the source node assigns a periodic label to the service flow based on its local synchronization clock and scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label, and written into the extension header;

[0011] The forwarding module of the forwarding node obtains the IPv6 packet, parses the deterministic flow identifier option in it, queries the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and sends the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock.

[0012] The IPv6 packets within the periodic resource unit are forwarded to the next forwarding node or tail node according to the preset SRv6 path.

[0013] Furthermore, including:

[0014] Based on the scheduling period Tc algorithm and the queue length, the remaining delay budget identifier is allocated to the service flow and written into the extension header;

[0015] The forwarding module of the forwarding node parses the remaining latency budget identifier and, if it determines that the remaining latency budget is lower than the threshold, sends the corresponding IPv6 packet to the low latency queue.

[0016] Further includes:

[0017] Assign a replication elimination flag to the service flow and write it to the extension header;

[0018] Based on the replication elimination identifier, the IPv6 packet corresponding to the service flow is replicated to obtain several clone packets, and each clone packet is forwarded and transmitted simultaneously based on the corresponding transmission path; wherein, each clone packet is assigned the same sequence number.

[0019] The replication elimination flag retains the earliest arriving clone message at the aggregation node and deletes all subsequent clone messages belonging to the same sequence number.

[0020] Furthermore, before the source node obtains the service flow, it includes:

[0021] PTP clock synchronization is used to synchronize the source node, each forwarding node, and the tail node to ensure that jitter meets transmission requirements.

[0022] Furthermore, the source node acquires the service flow, constructs an IPv6 packet corresponding to the service flow, and inserts a preset type of extension header into the IPv6 packet, including:

[0023] When it is determined that the data size of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets.

[0024] In this context, the deterministic service identifier in any IPv6 sub-packet is consistent with that in the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

[0025] Secondly, a cross-architecture communication system based on SRv6 deterministic networks is provided. A forwarding module is configured within the routers of the SRv6 backbone network, and the forwarding module stores a resource mapping table. This resource mapping table is uniformly configured by the network controller and is used to store various forwarding processing resources corresponding to any deterministic service identifier; including:

[0026] The message pre-construction module is used by the source node to obtain the service flow, construct the IPv6 message corresponding to the service flow, and insert an extension header of a preset type into the IPv6 message.

[0027] The flow identifier addition module is used by the network controller to assign a unique deterministic service identifier to the service flow based on the SLA index of the service flow, and by the source node to assign a periodic label to the service flow based on the local synchronization clock and the scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label and written into the extension header;

[0028] The resource abstraction module is used by the forwarding module of the forwarding node to obtain the IPv6 packet, parse the deterministic flow identifier option in it, query the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and send the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock.

[0029] The packet forwarding module is used to forward IPv6 packets within a periodic resource unit to the next forwarding node or tail node according to a preset SRv6 path.

[0030] Furthermore, including:

[0031] The clock synchronization module is used to synchronize the source node, each forwarding node and the tail node based on PTP clock synchronization to ensure that jitter meets the transmission requirements.

[0032] Furthermore, including:

[0033] The packet slicing module is used to determine that when the data volume of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets.

[0034] In this context, the deterministic service identifier in any IPv6 sub-packet is consistent with that in the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

[0035] Thirdly, an electronic device is provided, including at least one processor coupled to a memory storing a computer program configured to be executed by the processor when run.

[0036] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, the computer program being executed by a processor to implement the method.

[0037] Beneficial effects:

[0038] As can be seen from the above technical solutions, the technical solution of the present invention provides a cross-architecture communication method based on SRv6 deterministic networks to solve the defects of lack of unified identification, poor heterogeneous interoperability and poor high-precision scheduling in the current cross-architecture data transmission based on SRv6 deterministic networks.

[0039] This technical solution addresses the fundamental issue of the lack of unified identification and poor heterogeneous interoperability in deterministic network transmission, which stems from the fact that various device architectures can only perform resource mapping based on their own identifiers. Therefore, after the source node acquires the service flow and constructs the corresponding IPv6 packet, a preset type of extension header is inserted into the IPv6 packet header. Simultaneously, a unique deterministic service identifier is assigned to the service flow based on its SLA (Service Level Agreement) metrics. During packet forwarding, the deterministic service identifier acts as a resource abstraction interface between heterogeneous devices, mapping to a resource mapping table reserved for each node by the controller for service flow identification, confirmation, and forwarding. At this point, devices of various architectures can uniformly identify services through the deterministic service identifier, eliminating the need for service flow identification based on the node's own identifier, thus overcoming the limitations imposed by architecture type on service identification and forwarding.

[0040] To eliminate reliance on time-synchronization scheduling mechanisms like TCQF for precise scheduling during transmission, a periodic label is assigned to the service flow based on a local synchronization clock and the scheduling period Tc algorithm, and written into the extended header. When a forwarding node queries its pre-configured resource mapping table based on the deterministic service identifier to map the IPv6 packet to its target QoS queue, it then sends the IPv6 packet from the target QoS queue to the corresponding periodic resource unit based on the periodic label and the local synchronization clock. In this process, the periodic label coordinates the forwarding time of all nodes along the route. Therefore, even if the underlying scheduler details differ between nodes, packets can be processed within the required time window during forwarding at each node, ensuring the elimination of queuing jitter and guaranteeing high-precision end-to-end performance.

[0041] In summary, this technical solution defines a new option structure that carries a deterministic service identifier and a periodic label in the extended header of an SRv6 deterministic network. It utilizes the deterministic service identifier as an abstraction layer and achieves unified triggering of resource reservation and scheduling policies across different vendors' (e.g., between DIP and DetNet) deterministic network architectures through a resource mapping table. Simultaneously, it leverages the periodic label to coordinate time synchronization scheduling mechanisms (e.g., TCQF) along the route, enabling hop-by-hop time-window coordinated forwarding of deterministic packets, thereby ensuring microsecond-level low jitter and low latency performance.

[0042] It should be understood that all combinations of the foregoing concepts and the additional concepts described in more detail below can be considered part of the inventive subject matter of this disclosure, provided that such concepts do not contradict each other.

[0043] The foregoing and other aspects, embodiments, and features of the teachings of the present invention will be more fully understood from the following description in conjunction with the accompanying drawings. Other additional aspects of the invention, such as features and / or beneficial effects of exemplary embodiments, will become apparent from the following description or may be learned through practice of specific embodiments according to the teachings of the present invention. Attached Figure Description

[0044] The accompanying drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component shown in the various figures may be denoted by the same reference numeral. For clarity, not every component is labeled in each figure. Embodiments of various aspects of the invention will now be described by way of example and with reference to the accompanying drawings, wherein:

[0045] Figure 1 A schematic diagram of the structure of the forwarding device within any forwarding node;

[0046] Figure 2 This is a flowchart of the cross-architecture communication method based on SRv6 deterministic networks described in this embodiment;

[0047] Figure 3 This is a structural diagram of the HBH extension header as defined in this embodiment;

[0048] Figure 4 The execution flowchart corresponding to the remaining delay budget identifier;

[0049] Figure 5 The execution flowchart corresponding to the copy elimination flag;

[0050] Figure 6 This is a block diagram of the cross-architecture communication system based on SRv6 deterministic networks described in this embodiment;

[0051] Figure 7 This is a structural block diagram of the electronic device described in this embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the described embodiments of the present invention without creative effort are within the scope of protection of the present invention. Unless otherwise defined, the technical or scientific terms used herein should have the ordinary meaning understood by those skilled in the art to which this invention pertains.

[0053] The terms "first," "second," and similar words used in this application specification and claims do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Similarly, unless the context clearly indicates otherwise, the singular forms of "an," "a," or "the," etc., do not indicate a quantity limitation, but rather indicate the presence of at least one. Terms such as "comprising" or "including" mean that the element or object preceding "comprising" encompasses the features, integrals, steps, operations, elements, and / or components listed following "comprising" or "including," and do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or sets thereof. Terms such as "upper," "lower," "left," and "right" are used only to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0054] Deterministic networking aims to provide SLA guarantees of extremely low latency, extremely low jitter, and zero packet loss for critical services such as industrial control, 5G fronthaul / backhaul, and vehicle networking. As a new generation of network technology, SRv6 deterministic networking technology can specify the path by carrying a segmented routing header in the IPv6 packet header, providing flexible path control capabilities for deterministic services. However, the following key technical problems exist in the existing technology for deterministic service flows in SRv6 bearer networks: (1) Lack of unified flow identifiers: The core of deterministic networking lies in the accurate identification and resource reservation of service flows. Existing solutions usually use IP 5-tuples or specific SID sets in SRH to identify flows, but these identifiers cannot directly provide abstract service level information and time information required for high-precision scheduling that can be uniformly identified across vendors and architectures. (2) Poor heterogeneous interoperability: Different architectures often have significant differences in underlying resource reservation, queue management, and scheduling mechanisms. When deterministic service flows need to cross devices from different vendors or with different architectures, the lack of a unified data plane field to guide resource mapping for devices along the way makes it impossible to achieve unified, end-to-end deterministic QoS guarantees. (3) High precision performance is highly dependent: Achieving microsecond-level jitter requires time synchronization scheduling mechanisms such as TCQF. This makes high-precision scheduling difficult to coordinate and implement across vendor devices. Based on this, this embodiment aims to provide a cross-architecture communication method based on SRv6 deterministic networks to simultaneously improve the above-mentioned defects.

[0055] The cross-architecture communication method based on SRv6 deterministic networks described in this embodiment will be specifically introduced below with reference to the accompanying drawings.

[0056] Combination Figure 1As shown, a forwarding module is pre-configured in each router. This forwarding module stores a resource mapping table. This resource mapping table, uniformly configured by the network controller, stores various forwarding processing resources corresponding to any deterministic service identifier. Specifically, the forwarding module includes a receiving unit, a parsing unit, a mapping unit, a synchronization unit, a scheduling unit, and a forwarding unit. The receiving unit receives SRv6 packets. The parsing unit parses the extension header and extracts the deterministic service identifier and periodic label. The mapping unit queries the resource mapping table based on the deterministic service identifier to link to the corresponding local forwarding processing resource. Specifically, the resource mapping table includes interface resources, bandwidth limits, etc. The synchronization unit provides a high-precision synchronization clock signal. The scheduling unit integrates the periodic label and the local clock to perform TCQF or deterministic scheduling. The forwarding unit sends packets based on the tunnel path and scheduling results.

[0057] Specifically, in combination Figure 2 As shown, the method includes:

[0058] Step S202: The source node obtains the service flow, constructs an IPv6 packet corresponding to the service flow, and inserts an extension header of a preset type into the IPv6 packet.

[0059] In this step, the extension header can be an HBH extension header or an SRH extension header. Its purpose is to encapsulate subsequent deterministic stream identification options. Therefore, any other TLV format that meets the requirements can also be used. This embodiment specifically uses an HBH extension header.

[0060] As a specific implementation method, in order to ensure the smooth progress of subsequent forwarding, the following is included before step S202:

[0061] Step 200: Based on PTP clock synchronization, perform clock synchronization on the source node, each forwarding node and the tail node to ensure that jitter meets the transmission requirements.

[0062] At this point, step S200 can ensure the effectiveness of jitter protection and avoid downgrading to the normal priority scheduling mode due to synchronization failure.

[0063] Step S204: The network controller assigns a unique deterministic service identifier to the service flow based on the SLA index of the service flow, and the source node assigns a periodic label to the service flow based on the local synchronization clock and the scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label, and written into the extension header.

[0064] Specifically, in this embodiment, the naming deterministic service identifier is DSC-ID, the naming periodicity label is CT, and the naming deterministic flow identifier option is DFIO. As a specific implementation, the structure of the HBH extension header defined in this embodiment is as follows: Figure 3 As shown in Table 1, it includes three fields. The first field is the type option, specifically DFIO (i.e., the deterministic flow identifier option defined in this embodiment); the second field is the option data length; and the third field is the option data. The option data fields in this embodiment specifically include: control flag bit, DSC-ID high field, DSC-ID low field, CT high field, CT middle field, and CT low field.

[0065] Table 1 HBH Extension Header Description

[0066]

[0067] As a specific implementation method, considering that the data volume of IPv6 packets may exceed the Maximum Transmission Unit (MTU) after adding the extension header, thus leading to abnormal data transmission, the following is also included:

[0068] Step S205: When it is determined that the data volume of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets.

[0069] In practice, the deterministic service identifier in any IPv6 sub-packet is consistent with the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

[0070] Continuing, the following operations are performed on the IPv6 packet or each IPv6 sub-packet:

[0071] Step S206: The forwarding module of the forwarding node obtains the IPv6 packet, parses the deterministic flow identifier option in it, queries the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and sends the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock.

[0072] In practical implementation, the DSC-ID acts as a resource abstraction interface between heterogeneous devices. Forwarding nodes map service flows to their internally reserved deterministic resources based on the DSC-ID. For example, if it's a DIP device from vendor A, it's mapped to a reserved DIP service chain; if it's a DetNet device from vendor B, it's mapped to a reserved DetNet QoS queue. CT coordinates the forwarding time of all nodes along the route, ensuring that packets are processed within the same time window even if the underlying scheduler details differ, thus eliminating queuing jitter and guaranteeing high-precision end-to-end performance. The periodic resource unit can specifically be a periodic forwarding queue or a time window.

[0073] As a preferred implementation method, combined with Figure 4 As shown, to further reduce jitter and meet latency requirements, the following steps are also included:

[0074] Step 2042: Allocate the remaining delay budget identifier to the service flow based on the scheduling period Tc algorithm and the queue length, and write it into the extension header.

[0075] Step 2062: The forwarding module of the forwarding node parses the remaining latency budget identifier and, if it determines that the remaining latency budget is lower than the threshold, sends the corresponding IPv6 packet to the low latency queue.

[0076] At this point, based on steps S2042 to S2062, the available delay can be synchronously budgeted according to the message forwarding process by adding a remaining delay budget identifier, thereby adjusting the forwarding strategy to meet the SLA requirements of the service.

[0077] Step S208: Forward the IPv6 packets in the periodic resource unit to the next forwarding node or tail node according to the preset SRv6 path.

[0078] As another preferred implementation method, combined with Figure 5 As shown, to ensure the reliability of data forwarding and transmission, the following steps are also included:

[0079] Step S2044: Assign a replication elimination identifier to the service flow and write it to the extension header.

[0080] Step S2064: Based on the replication elimination identifier, the IPv6 packet corresponding to the service flow is replicated to obtain several clone packets, and each clone packet is forwarded and transmitted simultaneously based on the corresponding transmission path.

[0081] In practice, each cloned message is assigned the same sequence number. The message corresponding to the service flow is copied to obtain two cloned messages, which are then forwarded based on the primary path and the backup path, respectively.

[0082] Step S2084: The replication elimination flag retains the earliest arriving clone message at the aggregation node and deletes each subsequent clone message that belongs to the same sequence number.

[0083] At this point, based on steps S2044 to S2084, deterministic dual-transmission and reception can be supported by adding a replication elimination flag, thereby improving the reliability of the deterministic network.

[0084] In summary, this embodiment defines and encapsulates flow identifiers in a unified manner, and uses flow identifiers as interfaces for abstract mapping and high-precision scheduling of heterogeneous resources. Ultimately, it achieves interconnection and interoperability between heterogeneous networks, ensures high-precision scheduling during the interconnection and interoperability process, and guarantees microsecond-level low jitter and low latency performance.

[0085] The aforementioned program can run in a processor or be stored in memory (or a computer-readable storage medium). Computer-readable media includes both permanent and non-permanent, removable and non-removable media, and information storage can be achieved by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media, such as modulated data signals and carrier waves.

[0086] These computer programs may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes can be implemented using different modules, and different steps can be implemented using different modules.

[0087] This embodiment also provides a cross-architecture communication system based on SRv6 deterministic networks. It includes a forwarding module within the routers of the SRv6 backbone network, which stores a resource mapping table. This resource mapping table is uniformly configured by the network controller and stores various forwarding processing resources corresponding to any given deterministic service identifier. Furthermore, it combines... Figure 6 As shown, it includes the following virtual software functional modules:

[0088] The message pre-construction module is used by the source node to obtain the service flow, construct the IPv6 message corresponding to the service flow, and insert an extension header of a preset type into the IPv6 message.

[0089] The flow identifier addition module is used by the network controller to assign a unique deterministic service identifier to the service flow based on the SLA index of the service flow, and the source node to assign a periodic label to the service flow based on the local synchronization clock and the scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label and written into the extension header.

[0090] The resource abstraction module is used by the forwarding module of the forwarding node to obtain the IPv6 packet, parse the deterministic flow identifier option in it, query the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and send the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock.

[0091] The packet forwarding module is used to forward IPv6 packets within a periodic resource unit to the next forwarding node or tail node according to a preset SRv6 path.

[0092] Since the system is built based on the method described above, the above description will not be repeated here.

[0093] For example, it also includes:

[0094] The clock synchronization module is used to synchronize the source node, each forwarding node and the tail node based on PTP clock synchronization to ensure that jitter meets the transmission requirements.

[0095] For example, it also includes:

[0096] The packet slicing module is used to determine that when the data volume of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets; wherein, the deterministic service identifier in any IPv6 sub-packet is consistent with the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

[0097] This embodiment also provides an electronic device, combined with Figure 7 As shown, it includes at least one processor coupled to a memory storing a computer program configured to be executed by the processor when run.

[0098] Additionally, a computer-readable storage medium is provided having a computer program stored thereon, the computer program being executed by a processor to implement the method.

[0099] Since the system, electronic devices, and storage media are all used to implement the method or are built based on the method, the differences between underlying heterogeneous deterministic network architectures (such as DIP and DetNet) can be shielded in practical applications, enabling unified abstract mapping and interconnection of resources for deterministic service flows across networks of different equipment vendors. Furthermore, by providing the hop-by-hop coordination field (CT field) required to support high-precision, time-synchronized scheduling mechanisms such as TCQF / CQF, ultra-low latency and microsecond-level jitter performance can be effectively guaranteed.

[0100] While the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the invention. Those skilled in the art can make various modifications and refinements without departing from the spirit and scope of the invention. Therefore, the scope of protection of the present invention shall be determined by the claims.

Claims

1. A cross-architecture communication method based on SRv6 deterministic networks, characterized in that, A forwarding module is installed in the router of the SRv6 backbone network, and the forwarding module stores a resource mapping table; wherein, the resource mapping table is uniformly configured by the network controller and is used to store various forwarding processing resources corresponding to any deterministic service identifier; Includes the following steps: The source node obtains the service flow, constructs an IPv6 packet corresponding to the service flow, and inserts a preset type of extension header into the IPv6 packet. The network controller assigns a unique deterministic service identifier to the service flow based on its SLA metrics, and the source node assigns a periodic label to the service flow based on its local synchronization clock and scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label, and written into the extension header; The forwarding module of the forwarding node obtains the IPv6 packet, parses the deterministic flow identifier option in it, queries the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and sends the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock. The IPv6 packets within the periodic resource unit are forwarded to the next forwarding node or tail node according to the preset SRv6 path.

2. The cross-architecture communication method based on SRv6 deterministic networks according to claim 1, characterized in that, include: Based on the scheduling period Tc algorithm and the queue length, the remaining delay budget identifier is allocated to the service flow and written into the extension header; The forwarding module of the forwarding node parses the remaining latency budget identifier and, if it determines that the remaining latency budget is lower than the threshold, sends the corresponding IPv6 packet to the low latency queue.

3. The cross-architecture communication method based on SRv6 deterministic networks according to claim 1, characterized in that, include: Assign a replication elimination flag to the service flow and write it to the extension header; Based on the replication elimination identifier, the IPv6 packet corresponding to the service flow is replicated to obtain several clone packets, and each clone packet is forwarded and transmitted simultaneously based on the corresponding transmission path; wherein, each clone packet is assigned the same sequence number. The replication elimination flag retains the earliest arriving clone message at the aggregation node and deletes all subsequent clone messages belonging to the same sequence number.

4. The cross-architecture communication method based on SRv6 deterministic networks according to claim 1, characterized in that, Before the source node obtains the service flow, it includes: PTP clock synchronization is used to synchronize the source node, each forwarding node, and the tail node to ensure that jitter meets transmission requirements.

5. The cross-architecture communication method based on SRv6 deterministic networks according to claim 1, characterized in that, The source node acquires the service flow and constructs an IPv6 packet corresponding to the service flow; After inserting a preset type of extension header into the IPv6 packet, it includes: When it is determined that the data size of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets. In this context, the deterministic service identifier in any IPv6 sub-packet is consistent with that in the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

6. A cross-architecture communication system based on SRv6 deterministic networks, characterized in that, A forwarding module is installed within the routers of the SRv6 backbone network. This forwarding module stores a resource mapping table. This resource mapping table is uniformly configured by the network controller and is used to store various forwarding processing resources corresponding to any deterministic service identifier; including: The message pre-construction module is used by the source node to obtain the service flow, construct the IPv6 message corresponding to the service flow, and insert an extension header of a preset type into the IPv6 message. The flow identifier addition module is used by the network controller to assign a unique deterministic service identifier to the service flow based on the SLA index of the service flow, and by the source node to assign a periodic label to the service flow based on the local synchronization clock and the scheduling period Tc algorithm; then, a deterministic flow identifier option is constructed based on the deterministic service identifier and the periodic label and written into the extension header; The resource abstraction module is used by the forwarding module of the forwarding node to obtain the IPv6 packet, parse the deterministic flow identifier option in it, query the locally pre-configured resource mapping table based on the deterministic service identifier to map and store the IPv6 packet into the target QoS queue of this forwarding node; and send the IPv6 packet in the target QoS queue into the corresponding periodic resource unit of this forwarding node based on the periodic tag and the local synchronization clock. The packet forwarding module is used to forward IPv6 packets within a periodic resource unit to the next forwarding node or tail node according to a preset SRv6 path.

7. The cross-architecture communication system based on SRv6 deterministic networks according to claim 6, characterized in that, include: The clock synchronization module is used to synchronize the source node, each forwarding node and the tail node based on PTP clock synchronization to ensure that jitter meets the transmission requirements.

8. The cross-architecture communication system based on SRv6 deterministic networks according to claim 6, characterized in that, include: The packet slicing module is used to determine that when the data volume of the IPv6 packet is greater than the maximum transmission unit allowed by the transmission path, the IPv6 packet is sliced ​​based on the maximum transmission unit to generate several IPv6 sub-packets. In this context, the deterministic service identifier in any IPv6 sub-packet is consistent with that in the IPv6 packet, and the periodic label in any IPv6 sub-packet is calculated and allocated based on the local synchronization clock and the scheduling period Tc algorithm.

9. An electronic device, characterized in that, It includes at least one processor coupled to a memory storing a computer program configured to be executed by the processor to perform the method of any one of claims 1-5.

10. A computer-readable storage medium, characterized in that, It stores a computer program thereon, which is used to be executed by a processor to implement the method of any one of claims 1-5.

Images