Cross-domain service transmission method, device, equipment, medium and product

Abstract

The invention discloses a cross-domain service transmission method, device and equipment, a medium and a product. The method comprises the following steps: receiving a target service transmission request sent by a source TSN controller; determining a slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the target TSN domain information; determining an end-to-end delay according to a slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information and the target TSN domain information; if the end-to-end time delay is smaller than the time delay threshold value, sending a slice bandwidth corresponding to the target service transmission request to a FlexE controller, so that the FlexE controller divides network slices for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sending the service data to the target TSN controller through the network slice, and through the technical scheme of the invention, end-to-end communication between network devices of different TSN domains can be realized.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of communication technology, and in particular, to a cross-domain service transmission method, device, equipment, medium and product. Background Art

[0002] Traditional industrial control network protocols are numerous, intercommunication is difficult, and different types of data cannot be mixed and carried in the network.

[0003] With the rapid increase in the number of devices in the network, the bandwidth of traditional industrial control networks can no longer meet the transmission needs. Time Sensitive Network (TSN) technology is an extension of Ethernet. Based on clock synchronization, traffic shaping and scheduling, it not only ensures the transmission of high-priority services, but also meets the needs of co-network transmission of various types of traffic.

[0004] However, TSN technology is limited by factors such as clock synchronization accuracy and mainly works in local area networks, which seriously affects the application scope of TSN technology. Therefore, how to achieve end-to-end communication between network devices in different TSN domains has become an urgent problem to be solved. Summary of the invention

[0005] Embodiments of the present invention provide a cross-domain service transmission method, apparatus, device, medium and product to achieve end-to-end communication between network devices in different TSN domains.

[0006] According to one aspect of the present invention, a cross-domain service transmission method is provided, and the cross-domain service transmission method is executed by a global controller in a network system, the network system comprising: a source time-sensitive network TSN controller, a destination TSN controller, a flexible Ethernet FlexE controller and a global controller, the source TSN controller and the destination TSN controller belong to different TSN domains, and the cross-domain service transmission method comprises:

[0007] Receive a target service transmission request sent by a source TSN controller, wherein the target service transmission request includes: service data, source TSN domain information, destination TSN domain information, and a delay threshold;

[0008] Determine a slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information;

[0009] Determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information;

[0010] If the end-to-end delay is less than the delay threshold, the slice bandwidth corresponding to the target service transmission request is sent to the FlexE controller, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

[0011] According to another aspect of the present invention, a cross-domain service transmission device is provided, wherein the cross-domain service transmission device is configured in a global controller of a network system, wherein the network system comprises: a source time-sensitive network TSN controller, a destination TSN controller, a flexible Ethernet FlexE controller, and a global controller, wherein the source TSN controller and the destination TSN controller belong to different TSN domains, and the cross-domain service transmission device comprises:

[0012] A target service transmission request receiving module is used to receive a target service transmission request sent by a source TSN controller, wherein the target service transmission request includes: service data, service transmission start time, source TSN domain information, destination TSN domain information and delay threshold;

[0013] A slice bandwidth determination module, used to determine the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information;

[0014] An end-to-end delay determination module, configured to determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information;

[0015] The service transmission module is used to send the slice bandwidth corresponding to the target service transmission request to the FlexE controller if the end-to-end delay is less than the delay threshold, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

[0016] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0017] at least one processor; and

[0018] a memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the cross-domain service transmission method described in any embodiment of the present invention.

[0020] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the cross-domain service transmission method described in any embodiment of the present invention when executed.

[0021] According to another aspect of the present invention, a computer program product is provided. When the computer program is executed by a processor, the computer program implements the cross-domain service transmission method as described in any embodiment of the present invention.

[0022] The embodiment of the present invention receives a target service transmission request sent by a source TSN controller; determines the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information; determines the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information and the destination TSN domain information; if the end-to-end delay is less than the delay threshold, sends the slice bandwidth corresponding to the target service transmission request to the FlexE controller, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above-mentioned network slice, so as to realize end-to-end communication between network devices in different TSN domains.

[0023] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 is a flow chart of a cross-domain service transmission method in an embodiment of the present invention;

[0026] Figure 2 is a schematic diagram of the structure of a network system in an embodiment of the present invention;

[0027] Figure 3 is a schematic diagram of cross-domain transmission of services in an embodiment of the present invention;

[0028] Figure 4Schematic diagram of TSN intra-domain scheduling in an embodiment of the present invention;

[0029] Figure 5 It is a structural schematic diagram of a cross-domain service transmission device in an embodiment of the present invention;

[0030] Figure 6 It is a structural schematic diagram of an electronic device in an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It is understandable that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, scope of use, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0034] Embodiment 1

[0035] Figure 1 A flowchart of a cross-domain service transmission method provided in an embodiment of the present invention. This embodiment is applicable to the case of cross-domain service transmission. The method can be executed by a cross-domain service transmission device in an embodiment of the present invention. The device can be implemented in software and / or hardware. Figure 1 As shown, the method specifically comprises the following steps:

[0036] S110, receiving a target service transmission request sent by a source TSN controller.

[0037] The target service transmission request includes: service data, source TSN domain information, destination TSN domain information and delay threshold. The target service transmission request may also include: service transmission start time. The super period of the source TSN domain is an integer multiple of the super period of the destination TSN domain. For example, the source TSN domain and the destination TSN domain may have the same super period H.

[0038] In this embodiment, the source TSN domain information includes: the interface bandwidth of the source TSN domain, the source TSN domain information may also include: the service transmission path within the source TSN domain, the destination TSN domain information includes: the interface bandwidth of the destination TSN domain, the destination TSN domain information may also include: the edge device identifier and the destination network device identifier of the destination TSN domain.

[0039] It should be noted that the technical solution provided in the embodiment of the present invention is executed by a global controller in a network system, and the network system includes: a source time-sensitive network TSN controller, a destination TSN controller, a flexible Ethernet (FlexEthernet, FlexE) controller and a global controller, and the source TSN controller and the destination TSN controller belong to different TSN domains. The FlexE controller belongs to the FlexE domain, and the global controller can interact with the TSN controller in the TSN domain, and can also interact with the FlexE controller in the FlexE domain. The TSN domain also includes: network devices, and the network devices at the boundary of the TSN domain are called boundary devices.

[0040] In a specific example, Figure 2As shown, the network system includes: multiple TSN domains, FlexE domains and a global controller. The multiple TSN domains are TSN domain 1, TSN domain 2 and TSN domain 3 on the left side of the FlexE domain, and TSN domain 4 and TSN domain 5 on the right side of the FlexE domain. Each TSN domain can represent a factory / park range, so the communication between each TSN domain and the opposite TSN domain can be regarded as the cross-domain interconnection of the factory / park. Multiple network devices are deployed in each TSN domain, and the network devices deployed at the edge of each TSN domain are called boundary devices. The network devices in the TSN domain on the left side of the FlexE domain can send service data to the network devices in the TSN domain on the right side of the FlexE domain. The network device that sends service data can be called the source network device, and the network device that receives service data can be called the destination network device. For example, the network device A1 in TSN domain 1 can send service data to the network device A2 in TSN domain 4, and the network device A1 is the source network device and the network device A2 is the destination network device. The network device A3 in the TSN domain 2 can send service data to the network device A4 in the TSN domain 4. The network device A3 is a source network device, and the network device A is a destination network device. This embodiment of the present invention does not limit this.

[0041] It should be noted that the TSN domain mainly uses the Time-Aware Shaper (TAS) mechanism to ensure determinism within the domain. The TAS mechanism divides all traffic in the network into 8 priorities (0 to 7, 7 is the highest priority). Each port of the network device in the TSN domain has 8 queues, corresponding to these 8 priorities. Each queue is connected to a transmission control gate. The transmission control gate is opened to allow data transmission in the queue, and the transmission control gate is closed to prevent transmission. The TAS mechanism controls the opening and closing of the transmission control gate according to the gate control list (GCL), so that all traffic can be transmitted in the expected manner. The FlexE domain can flexibly configure the bandwidth of the slice according to the needs of the business, and can provide three functions of bundling, channelization and sub-rate. This embodiment provides a fusion transmission method of the TSN domain and the FlexE domain, which uses the flexible slicing capability of the FlexE domain to realize cross-domain interconnection of the TSN domain, thereby ensuring end-to-end cross-domain deterministic transmission.

[0042] In this embodiment, the source TSN controller collects the initial service transmission request sent by each network device in the source TSN domain, wherein the initial service transmission request includes: service data, source network device identification, destination network device identification, source TSN domain information (source TSN domain information includes: interface bandwidth of the source TSN domain), destination TSN domain information (destination TSN domain information includes: interface bandwidth of the destination TSN domain) and delay threshold; the source TSN controller determines the service transmission path and service transmission start time in the source TSN domain according to the source network device identification, the data volume of the service data, the interface bandwidth of the source TSN domain, the source TSN domain boundary device identification, and the service information being processed in the source TSN domain (the service information includes the transmission start time, the data volume of the service data and the service transmission path); the source TSN controller generates a target service transmission request according to the service data, the service transmission start time, the source TSN domain information, the destination TSN domain information and the delay threshold, and sends the target service transmission request to the global controller, and the global controller receives the target service transmission request sent by the source TSN controller.

[0043] In this embodiment, the source TSN controller collects the initial service transmission request sent by each network device in the source TSN domain, wherein the initial service transmission request includes: service data, source network device identification, destination network device identification, source TSN domain information (source TSN domain information includes: interface bandwidth of the source TSN domain), destination TSN domain information (destination TSN domain information includes: interface bandwidth of the destination TSN domain) and delay threshold; the source TSN controller collects the initial service transmission request sent by each network device in the source TSN domain according to the source network device identification, the data volume of the service data, the interface bandwidth of the source TSN domain, the source TSN domain boundary device identification, and the service information being processed in the source TSN domain (service information Including transmission start time, data volume of business data and business transmission path), determine whether the resources in the source TSN domain meet the transmission requirements. If the transmission requirements are met, the transmission delay of the business in the source TSN domain (the transmission delay of the source TSN domain) is obtained based on the intra-domain synchronization mechanism, and the target business transmission request is generated according to the transmission delay of the source TSN domain, business data and destination TSN domain information, and the target business transmission request is sent to the global controller. After receiving the target business transmission request, the global controller can also receive the transmission delay of the business in the destination TSN domain (the transmission delay of the destination TSN domain) sent by the destination TSN controller.

[0044] It should be noted that after the source TSN controller collects the initial service transmission requests sent by each network device in the source TSN domain, it needs to first determine whether the resources in the source TSN domain meet the transmission requirements. If the resources in the source TSN domain are insufficient, the initial service transmission request is directly rejected. If the resources in the source TSN domain are sufficient, the service transmission path and service transmission start time in the source TSN domain are determined based on the source network device identification, the data volume of the service data, the interface bandwidth of the source TSN domain, the source TSN domain boundary device identification, and the service information being processed in the source TSN domain. The service transmission path in the source TSN domain is the shortest path for service transmission in the source TSN domain, that is, the shortest path from the source network device to the boundary device of the source TSN domain. The rule for determining the service transmission start time is: the service transmission start time of the target service transmission request does not conflict with the service being processed in the source TSN domain.

[0045] In this embodiment, the method for judging whether the resources in the source TSN domain are sufficient can be: judging whether there is a service transmission path in the source TSN domain with a spare time period that meets the service transmission requirements according to the service information being processed in the source TSN domain, the source network device identifier, the boundary device identifier of the source TSN domain, the data volume of the service data, and the interface bandwidth of the source TSN domain. If so, it is determined that the resources in the source TSN domain are sufficient; if not, it is determined that the resources in the source TSN domain are insufficient.

[0046] S120, determining the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information.

[0047] In this embodiment, the method for determining the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information can be: determining the slice bandwidth corresponding to the target service transmission request according to the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain.

[0048] Optionally, the source TSN domain information includes: an interface bandwidth of the source TSN domain, and the destination TSN domain information includes: an interface bandwidth of the destination TSN domain;

[0049] Determining a slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information includes:

[0050] If the remaining bandwidth of the FlexE domain is greater than or equal to the interface bandwidth of the source TSN domain, and the remaining resources of the destination TSN domain are sufficient, the slice bandwidth corresponding to the target service transmission request is determined based on the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain.

[0051] It should be noted that after receiving the target service transmission request sent by the source TSN controller, the global controller needs to first determine whether the transmission requirements are met. The method of determining whether the transmission requirements are met may include: determining whether the remaining bandwidth of the FlexE domain is sufficient, and determining whether the remaining resources of the destination TSN domain are sufficient. If the remaining bandwidth of the FlexE domain is sufficient, and the remaining resources of the destination TSN domain are sufficient, it is determined that the transmission requirements are met. If the remaining bandwidth of the FlexE domain is insufficient, or the remaining resources of the destination TSN domain are insufficient, it is determined that the transmission requirements are not met. If the transmission requirements are not met, the target service transmission request is directly rejected. If the transmission requirements are met, the global controller determines the slice bandwidth corresponding to the target service transmission request based on the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain.

[0052] In this embodiment, the method for determining whether the remaining bandwidth of the FlexE domain is sufficient is as follows: determining whether the remaining bandwidth of the FlexE domain is greater than or equal to the interface bandwidth of the source TSN domain. If the remaining bandwidth of the FlexE domain is greater than or equal to the interface bandwidth of the source TSN domain, it is determined that the remaining bandwidth of the FlexE domain is sufficient. If the remaining bandwidth of the FlexE domain is less than the interface bandwidth of the source TSN domain, it is determined that the remaining bandwidth of the FlexE domain is insufficient.

[0053] In this embodiment, the method for judging whether the remaining resources of the destination TSN domain are sufficient can be: judging whether there is a service transmission path in the destination TSN domain with a spare time period that meets the service transmission requirements based on the service information being processed in the destination TSN domain, the destination network device identifier, the boundary device identifier of the destination TSN domain, the data volume of the service data, and the interface bandwidth of the destination TSN domain. If so, it is determined that the resources in the destination TSN domain are sufficient; if not, it is determined that the resources in the destination TSN domain are insufficient. The service transmission path in the destination TSN domain is the shortest path from the boundary device of the destination TSN domain to the destination network device.

[0054] Optionally, determining the slice bandwidth corresponding to the target service transmission request according to the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain includes:

[0055] If there are multiple target service transmission requests, the destination TSN domains of the multiple target service transmission requests are the same, and the interface bandwidth of the destination TSN domain is greater than or equal to the sum of the interface bandwidths of the source TSN domains of the multiple target service transmission requests, then the interface bandwidth of the destination TSN domain is determined as the slice bandwidth shared by the multiple target service transmission requests;

[0056] If there are multiple target service transmission requests, the source TSN domains of the multiple target service transmission requests are the same, and the interface bandwidth of the source TSN domain is less than or equal to the sum of the interface bandwidths of the destination TSN domains of the multiple target service transmission requests, then the interface bandwidth of the destination TSN domain of each target service transmission request is determined as the slice bandwidth of each target service transmission request.

[0057] In this embodiment, the global controller obtains the source TSN domain and the destination TSN domain of multiple target service transmission requests, and pre-determines whether the source TSN domain and the destination TSN domain of the target service transmission request are the same. If the source TSN domains are the same, it is determined whether the interface bandwidth of the source TSN domain is less than or equal to the sum of the interface bandwidths of the destination TSN domains of the multiple target service transmission requests. If the interface bandwidth of the source TSN domain is less than or equal to the sum of the interface bandwidths of the destination TSN domains of the multiple target service transmission requests, the interface bandwidth of the destination TSN domain of each target service transmission request is determined as the slice bandwidth of each target service transmission request. If the destination TSN domains are the same, it is determined whether the interface bandwidth of the destination TSN domain is greater than or equal to the sum of the interface bandwidths of the source TSN domains of the multiple target service transmission requests. If the interface bandwidth of the destination TSN domain is greater than or equal to the sum of the interface bandwidths of the source TSN domains of the multiple target service transmission requests, the interface bandwidth of the destination TSN domain is determined as the slice bandwidth shared by the multiple target service transmission requests.

[0058] In a specific example, Figure 3 As shown, the interface bandwidth of TSN domain 1 to which the source network device sending service 1 belongs and the interface bandwidth of TSN domain 2 to which the source network device sending service 2 belongs are both 500Mbps, and the destination network device receiving service 1 and the destination network device receiving service 2 both belong to TSN domain 4, then a network slice with a bandwidth of 1Gbps is allocated to service 1 and service 2, and service 1 and service 2 share the above network slice, and the bandwidth of the above network slice is the same as the interface bandwidth of TSN domain 4; the source network device sending service 3 and the source network device sending service 4 both belong to TSN domain 3, and the interface bandwidth of TSN domain 3 is 1Gbps. The destination network device receiving service 3 belongs to TSN domain 5, and the interface bandwidth of TSN domain 5 is 500Mbps. The destination network device receiving service 4 belongs to TSN domain 6, and the interface bandwidth of TSN domain 6 is 500Mbps. A slice with a bandwidth of 500Mbps is allocated to service 3, and a slice with a bandwidth of 500Mbps is allocated to service 4, so as to match the interface bandwidth of the destination TSN domain.

[0059] In this embodiment, the method for determining the slice bandwidth corresponding to the target service transmission request may be: the global controller determines the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information. Alternatively, the FlexE controller determines the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information.

[0060] In an embodiment of the present invention, the flexible slicing function of the FlexE domain is used to solve the transmission delay inconsistency and congestion problems caused by the inconsistent bandwidth of the local area network and the wide area network.

[0061] S130, determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information and the destination TSN domain information.

[0062] In this embodiment, the end-to-end delay is the total delay of sending the service from the source network device in the source TSN domain to the destination network device in the destination TSN domain.

[0063] In this embodiment, the source TSN domain information includes: the interface bandwidth of the source TSN domain, and the source TSN domain information may also include: the service transmission path within the source TSN domain. The destination TSN domain information includes: the interface bandwidth of the destination TSN domain; the destination TSN domain information may also include: the destination network device identifier, or the edge device identifier and the destination network device identifier of the destination TSN domain.

[0064] In this embodiment, the method for determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information and the destination TSN domain information can be: determining the transmission delay of the source TSN domain and the transmission delay of the FlexE domain according to the data volume of the service data, the interface bandwidth of the source TSN domain, the total number of hops of the service transmission path in the source TSN domain and the slice bandwidth corresponding to the target service transmission request; determining the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data and the interface bandwidth of the destination TSN domain; determining the end-to-end delay according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain and the transmission delay of the destination TSN domain. The method of determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information, and the destination TSN domain information may also be: determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information, and the destination TSN domain information, including: determining the transmission delay of the source TSN domain according to the data volume of the service data, the interface bandwidth of the source TSN domain, and the total number of hops of the service transmission path in the source TSN domain; Determine the transmission delay of the FlexE domain according to the data volume of the service data and the slice bandwidth corresponding to the target service transmission request; determine the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data and the interface bandwidth of the destination TSN domain; determine the end-to-end delay according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain and the transmission delay of the destination TSN domain. The method for determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information and the destination TSN domain information can also be: the global controller obtains the transmission delay of the service in the source TSN domain (the transmission delay of the source TSN domain) and the transmission delay of the service in the destination TSN domain (the transmission delay of the destination TSN domain) based on the intra-domain synchronization mechanism, determines the transmission delay of the FlexE domain according to the data volume of the service data and the slice bandwidth corresponding to the target service transmission request, and determines the end-to-end delay according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain and the transmission delay of the destination TSN domain.

[0065] In this embodiment, the source TSN controller is responsible for collecting service transmission requests within the source TSN domain, and extracting information such as the cycle, size, and latency requirements of the flow to perform scheduling calculations within the domain. The source TSN controller also sends the service transmission requests within the source TSN domain to the global controller. The global controller estimates the end-to-end latency based on the remaining resource status and service request view of the entire network, executes traffic admission decisions and transmission resource allocation, and configures network slices of corresponding bandwidth according to the actual transmission requirements of the service. The destination TSN domain is based on the latency estimation of the global controller, and the TSN switches within the destination TSN domain are reasonably configured to ensure that the gating corresponding to the switch port can be opened on time when time-sensitive traffic arrives, so as to achieve end-to-end low-latency deterministic transmission.

[0066] Optionally, the source TSN domain information further includes: a service transmission path within the source TSN domain, and the destination TSN domain information further includes: an edge device identifier and a destination network device identifier of the destination TSN domain;

[0067] Determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service transmission start time, the service data, the source TSN domain information, and the destination TSN domain information, including:

[0068] Determine the transmission delay of the source TSN domain according to the data volume of the service data, the interface bandwidth of the source TSN domain, and the total number of hops of the service transmission path in the source TSN domain;

[0069] Determine a transmission delay of the FlexE domain according to the data volume of the service data and the slice bandwidth corresponding to the target service transmission request;

[0070] Determine the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain;

[0071] An end-to-end delay is determined according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, and the transmission delay of the destination TSN domain.

[0072] In this embodiment, the destination network device identifier is the identifier of the network device receiving the service data in the destination TSN domain. The edge device identifier of the destination TSN domain is the identifier of the edge device of the destination TSN domain through which the service data passes when it is sent from the source network device in the source TSN domain to the destination network device in the destination TSN domain.

[0073] In this embodiment, according to the data volume of the business data, the interface bandwidth of the source TSN domain, and the total number of hops of the business transmission path within the source TSN domain, the transmission delay of the source TSN domain can be determined as follows: the ratio of the data volume of the business data and the interface bandwidth corresponding to the source TSN domain identifier is determined as the delay corresponding to each hop, and then the product of the total number of hops corresponding to the business transmission path within the source TSN domain and the delay corresponding to each hop is determined as the transmission delay of the source TSN domain.

[0074] In this embodiment, according to the data volume of the service data and the slice bandwidth corresponding to the target service transmission request, the method for determining the transmission delay of the FlexE domain can be: the ratio of the data volume of the service data and the slice bandwidth corresponding to the target service transmission request is determined as the transmission delay of the FlexE domain.

[0075] In this embodiment, the transmission delay of the destination TSN domain may be determined according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain: determining the time when the service data arrives at the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, and the transmission delay of the FlexE domain; determining the service transmission path within the destination TSN domain according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier; determining the transmission delay of the destination TSN domain according to the data volume of the service data, the interface bandwidth of the destination TSN domain, and the number of hops corresponding to the service transmission path within the destination TSN domain.

[0076] In this embodiment, according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain and the transmission delay of the destination TSN domain, the end-to-end delay may be determined by taking the sum of the transmission delay of the source TSN domain, the transmission delay of the FlexE domain and the transmission delay of the destination TSN domain as the end-to-end delay.

[0077] Optionally, determining the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain includes:

[0078] Determine the time when the service data arrives at the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, and the transmission delay of the FlexE domain;

[0079] Determine a service transmission path within the destination TSN domain according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier;

[0080] The transmission delay of the destination TSN domain is determined according to the data volume of the service data, the interface bandwidth of the destination TSN domain, and the number of hops corresponding to the service transmission path in the destination TSN domain.

[0081] In this embodiment, according to the service transmission start time, the transmission delay of the source TSN domain and the transmission delay of the FlexE domain, the time when the service data arrives at the destination TSN domain can be determined by taking the sum of the service transmission start time, the transmission delay of the source TSN domain and the transmission delay of the FlexE domain as the time when the service data arrives at the destination TSN domain.

[0082] In this embodiment, according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier, the method for determining the service transmission path within the destination TSN domain can be: determining the initial service transmission path set corresponding to the target service transmission request according to the edge device identifier of the destination TSN domain and the destination network device identifier; filtering the initial service transmission path set according to the time when the service data arrives at the destination TSN domain and the service information being processed in the destination TSN domain to obtain the service transmission path within the destination TSN domain.

[0083] In this embodiment, the transmission delay of the destination TSN domain can be determined based on the data volume of the service data, the interface bandwidth of the destination TSN domain, and the number of hops corresponding to the service transmission path within the destination TSN domain: the ratio of the data volume of the service data to the interface bandwidth of the destination TSN domain is determined as the delay of each hop within the destination TSN domain, and the product of the delay of each hop within the destination TSN domain and the number of hops corresponding to the service transmission path within the destination TSN domain is determined as the transmission delay of the destination TSN domain.

[0084] Optionally, determining a service transmission path within the destination TSN domain according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier includes:

[0085] Obtaining service information being processed in the target TSN domain;

[0086] Determine an initial service transmission path set corresponding to the target service transmission request according to the edge device identifier of the target TSN domain and the target network device identifier;

[0087] The initial service transmission path set is screened according to the time when the service data arrives at the destination TSN domain and the service information being processed in the destination TSN domain to obtain the service transmission path in the destination TSN domain.

[0088] In this embodiment, the service information being processed in the destination TSN domain includes: the transmission start time, transmission path and data volume of the service being processed in the destination TSN domain.

[0089] In this embodiment, the method for determining the initial service transmission path set corresponding to the target service transmission request based on the edge device identifier of the destination TSN domain and the destination network device identifier can be: based on the edge device identifier of the destination TSN domain and the destination network device identifier, multiple transmission paths from the edge device of the destination TSN domain to the destination network device are obtained, and the above multiple transmission paths are determined as the initial service transmission path set corresponding to the target service transmission request.

[0090] In this embodiment, the initial service transmission path set is screened according to the time when the service data arrives at the destination TSN domain and the service information being processed in the destination TSN domain, and the method for obtaining the service transmission path in the destination TSN domain can be: based on the set path screening rules, the initial service transmission path set corresponding to the target service transmission request is screened to obtain the service transmission path in the destination TSN domain. The set path screening rules may include: the service corresponding to the target service transmission request does not conflict with the service being processed in the destination TSN domain, and the service transmission path in the destination TSN domain is the shortest path. It should be noted that whether the service corresponding to the target service transmission request conflicts with the service being processed in the destination TSN domain can be determined based on the time when the service data arrives at the destination TSN domain and the transmission start time of the service being processed in the destination TSN domain. The shortest path is selected from multiple paths that do not conflict with the service being processed in the TSN domain as the service transmission path in the destination TSN domain.

[0091] In this embodiment, after the global controller calculates the time when the service data arrives at the destination TSN domain, the destination TSN domain controller reserves resources according to the time when the service data arrives at the destination TSN domain and configures the gating list.

[0092] S140: If the end-to-end delay is less than the delay threshold, the slice bandwidth corresponding to the target service transmission request is sent to the FlexE controller, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

[0093] In this embodiment, network slicing refers to a logical network (virtual network) obtained by resource planning for a physical network, and resource isolation of different services can be achieved through network slicing. The network slices obtained by resource planning for a physical network include basic slices and business slices. Basic slices are used to carry basic services. Business slices are a complete, autonomous, and independently operated logical network that organizes related business functions, network resources, etc. in a physical network to meet specific user and business needs. Different business slices are used to meet different business needs. Operators usually deploy business slices according to the business needs that business slices need to meet. For example, some business slices are used to meet low-latency business needs, other business slices are used to meet large bandwidth business needs, and some business slices are used to meet high reliability business needs.

[0094] In this embodiment, if the end-to-end delay is less than the delay threshold, the global controller sends the slice bandwidth corresponding to the target service transmission request to the FlexE controller. After receiving the slice bandwidth corresponding to the target service transmission request, the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller in the destination TSN domain through the above-mentioned network slice. The destination TSN controller in the destination TSN domain sends the service data to the destination network device in the destination TSN domain.

[0095] In this embodiment, the destination TSN controller in the destination TSN domain sends the service data to the destination network device in the destination TSN domain according to the specified time configured in the gating list. For example, the service data can be injected into the network at the specified time, enter the specified network slice, and complete the cross-domain end-to-end transmission.

[0096] The bandwidth of a local area network is usually less than 1Gbps, while the bandwidth of a wide area network is usually more than 50Gbps. The inconsistent bandwidth will lead to unstable transmission delay and even congestion of cross-domain interfaces, which seriously affects the performance of the TAS mechanism in the TSN domain. The flexible slicing function of the FlexE domain can slice the network according to business needs. Therefore, using the FlexE domain for cross-domain interconnection of TSN can ensure the consistency of bandwidth of all interfaces on the transmission path and ensure the stability of transmission delay at the interface; in addition, the FlexE domain itself can achieve precise clock synchronization, which makes cross-domain interconnection of TSN domains possible.

[0097] In a specific example, Figure 3As shown, the interface bandwidth of TSN domains 1, 2, 5, and 6 is 500M, and the interface bandwidth of TSN domains 3 and 4 is 1G. There are 4 services in the network. The source network device that sends service 1 belongs to TSN domain 1, and the destination network device that receives service 1 belongs to TSN domain 4. The source network device that sends service 2 belongs to TSN domain 2, and the destination network device that receives service 2 belongs to TSN domain 4. The source network device that sends service 3 belongs to TSN domain 3, and the destination network device that receives service 3 belongs to TSN domain 5. The source network device that sends service 4 belongs to TSN domain 3, and the destination network device that receives service 4 belongs to TSN domain 6. The specific process of service scheduling is as follows:

[0098] 1. The source TSN controller collects the initial service request information sent by the source network device in the source TSN domain, and determines whether the resources in the source TSN domain meet the transmission requirements. If the resources in the source TSN domain are insufficient, the above initial service request information is directly rejected; if the resources in the source TSN domain are sufficient, the transmission resources (the transmission path in the source TSN domain and the service transmission start time) are planned for it, and the target service transmission request is generated according to the transmission path in the source TSN domain, the service transmission start time, the service data, the delay threshold, the service transmission path in the source TSN domain, the edge device identification of the destination TSN domain, the destination network device identification, the interface bandwidth of the source TSN domain, and the interface bandwidth of the destination TSN domain, and the target service transmission request is sent to the global controller.

[0099] 2. After receiving the target service transmission request, the global controller determines whether the transmission requirements are met based on the interface bandwidth of the source TSN domain, the remaining bandwidth of the FlexE domain, the remaining resources of the destination TSN domain, the destination network device identifier, the boundary device identifier of the destination TSN domain, the data volume of the service data, and the interface bandwidth of the destination TSN domain. If the remaining bandwidth of the FlexE domain is insufficient or the remaining resources of the destination TSN domain are insufficient, the above target service transmission request is directly rejected; if the remaining bandwidth of the FlexE domain is sufficient and the remaining resources of the destination TSN domain are sufficient, the global controller obtains the transmission delay of the source TSN domain and the transmission delay of the FlexE domain corresponding to the target service transmission request.

[0100] 3. According to the transmission delay of the source TSN domain STSN ), transmission delay in the FlexE domain FlexE ) and the service transmission start time (t start ), calculate the time (t arrive ):

[0101] That is: t arrive =t start +Delay STSN +Delay FlexE;

[0102] According to t arrive , the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain, and determine the transmission delay of the destination TSN domain. DTSN ) and calculate the end-to-end delay (Delay E2E ): Delay E2E =Delay STSN +Delay FlexE +Delay DTSN ; If Delay E2E If the delay is less than the delay threshold, the scheduling is successful, otherwise the scheduling fails. The delay threshold is the maximum delay required by the service.

[0103] 4. The global controller determines the slice bandwidth allocated to each target service transmission request based on the interface bandwidth of the destination TSN domain, the interface bandwidth of the source TSN domain, and the number of interfaces, performs network slicing based on the slice bandwidth allocated to each service transmission request, and sends the service data to the destination network device in the destination TSN domain through the network slicing.

[0104] If bandwidth is allocated through the FlexE controller, the global controller needs to first send the interface bandwidth of the source TSN domain and the interface bandwidth of the destination TSN domain of all cross-domain services to the FlexE controller, and the FlexE controller will then analyze the overall bandwidth requirements and calculate and execute the network slicing solution. (For example, in Figure 3 In the example, the interface bandwidth of TSN domain 1 to which the source network device that sends service 1 belongs and the interface bandwidth of TSN domain 2 to which the source network device that sends service 2 belongs are both 500Mbps, and the destination network device that receives service 1 and the destination network device that receives service 2 both belong to TSN domain 4. A network slice with a bandwidth of 1G is configured for service 1 and service 2, and the bandwidth of this network slice is consistent with the interface bandwidth of TSN domain 4. The source network device that sends service 3 and the source network device that sends service 4 both belong to TSN domain 3, and the interface bandwidth of TSN domain 3 is 1Gbps. The destination network device that receives service 3 belongs to TSN domain 5, and the interface bandwidth of TSN domain 5 is 500Mbps. The destination network device that receives service 4 belongs to TSN domain 6, and the interface bandwidth of TSN domain 6 is 500Mbps. A slice with a bandwidth of 500Mbps is allocated to service 3, and a slice with a bandwidth of 500Mbps is allocated to service 4 to match the interface bandwidth of the destination TSN domain.

[0105] 5. After completing cross-domain scheduling, the entire network updates the remaining resource status to the TSN controller, FlexE controller, and global controller.

[0106] In a specific example, Figure 4 As shown in the figure, in order to better illustrate the cross-domain scheduling of TSN traffic, specific traffic conditions are used for demonstration. Among them, the traffic super period of TSN domains 1 to 6 is H, and all TSN domains use the TAS scheduling mechanism. There are 4 target service transmission requests in the network. Assuming that these 4 target service transmission requests are successfully scheduled, the data volume of the service data of the 4 target service transmission requests is D1 to D4.

[0107]

[0108]

[0109]

[0110]

[0111]

[0112] Among them, t start1 ~t start4 Represents the transmission start time of services 1 to 4, t arrive14 ,t arrive24 They represent the positions of the time when service 1 and service 2 arrive at TSN domain 4 in the super cycle, t arrive35 represents the position of the time when service 3 arrives at TSN domain 5 in the super cycle, t arrive46 Represents the position of the time when service 4 arrives at TSN domain 6 in the super cycle. i is the data volume of service i, and the slice bandwidth of service i is B FlexEi , Delay FlexEi Delay is the transmission delay of service i in the FlexE domain, and i is in the range of [1,4]. TSN1 Delay is the transmission delay of service 1 in the source TSN domain. TSN2 Delay is the transmission delay of service 2 in the source TSN domain. TSN3 Delay is the transmission delay of service 3 in the source TSN domain. TSN4 is the transmission delay of service 4 in the source TSN domain.

[0113] Based on the network interface bandwidth, there are:

[0114] B FlexE1 =B FlexE2 =1Gbps;

[0115] B FlexE3 =500Mbps;

[0116] B FlexE4=500Mbps.

[0117] The destination TSN domain reasonably configures the gating list according to the service size and the time when the service arrives at the destination TSN domain to ensure that the service data can be transmitted smoothly without conflict.

[0118] It should be noted that the source TSN controller, the destination TSN controller and the FlexE controller sense the resource status in their respective domains and report it to the global controller.

[0119] The technical solution of this embodiment, by integrating FlexE flexible slicing technology with TSN technology working within the scope of the local area network, can realize cross-domain interconnection of multiple TSN domains, and provide a solution for deterministic communication across wide area network factories / parks. The FlexE slice bandwidth is flexibly configured according to the service status in the network and the interface bandwidth of the TSN domain, which can avoid the instability of transmission delay or congestion of cross-domain interfaces caused by inconsistent bandwidth, and is conducive to the stable transmission of time-sensitive flows. In addition, it can ensure the low-latency transmission of key services across the wide area network, which is conducive to expanding the application scope of TSN technology and promoting the further development of TSN.

[0120] Embodiment 2

[0121] Figure 5 This is a schematic diagram of the structure of a cross-domain service transmission device provided by an embodiment of the present invention. This embodiment is applicable to the case of cross-domain service transmission. The device can be implemented in software and / or hardware. The device can be integrated in any device that provides a cross-domain service transmission function, such as Figure 5 As shown, the cross-domain service transmission device specifically includes: a target service transmission request receiving module 510, a slice bandwidth determination module 520, an end-to-end delay determination module 530 and a service transmission module 540.

[0122] The target service transmission request receiving module is used to receive the target service transmission request sent by the source TSN controller, wherein the target service transmission request includes: service data, service transmission start time, source TSN domain information, destination TSN domain information and delay threshold;

[0123] A slice bandwidth determination module, used to determine the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information;

[0124] An end-to-end delay determination module, configured to determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information;

[0125] The service transmission module is used to send the slice bandwidth corresponding to the target service transmission request to the FlexE controller if the end-to-end delay is less than the delay threshold, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

[0126] The above-mentioned product can execute the method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0127] Embodiment 3

[0128] Figure 6 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0129] like Figure 6 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0130] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0131] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The processor 11 executes the various methods and processes described above, such as a cross-domain service transmission method.

[0132] In some embodiments, the cross-domain business transmission method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the cross-domain business transmission method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the cross-domain business transmission method in any other appropriate manner (e.g., by means of firmware).

[0133] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0134] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0135] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0136] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0137] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0138] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0139] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0140] An embodiment of the present invention further provides a computer program product, including a computer program, and when the computer program is executed by a processor, the cross-domain service transmission method according to any embodiment of the present invention is implemented.

[0141] In the process of implementation, the computer program product can be written in one or more programming languages ​​or a combination thereof to perform the computer program code of the present invention, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider to connect through the Internet).

[0142] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A cross-domain service transmission method, characterized in that: The cross-domain service transmission method is executed by a global controller in a network system, wherein the network system includes: a source time-sensitive network TSN controller, a destination TSN controller, a flexible Ethernet FlexE controller, and a global controller, wherein the source TSN controller and the destination TSN controller belong to different TSN domains, and the cross-domain service transmission method includes: Receive a target service transmission request sent by a source TSN controller, wherein the target service transmission request includes: service data, source TSN domain information, destination TSN domain information, and a delay threshold; Determine a slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information; Determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information; If the end-to-end delay is less than the delay threshold, the slice bandwidth corresponding to the target service transmission request is sent to the FlexE controller, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

2. The method according to claim 1, characterized in that The source TSN domain information includes: the interface bandwidth of the source TSN domain, and the destination TSN domain information includes: the interface bandwidth of the destination TSN domain; Determining a slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information includes: If the remaining bandwidth of the FlexE domain is greater than or equal to the interface bandwidth of the source TSN domain, and the remaining resources of the destination TSN domain are sufficient, the slice bandwidth corresponding to the target service transmission request is determined based on the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain.

3. The method according to claim 2, characterized in that Determining a slice bandwidth corresponding to the target service transmission request according to the interface bandwidth of the destination TSN domain and the interface bandwidth of the source TSN domain includes: If there are multiple target service transmission requests, the destination TSN domains of the multiple target service transmission requests are the same, and the interface bandwidth of the destination TSN domain is greater than or equal to the sum of the interface bandwidths of the source TSN domains of the multiple target service transmission requests, then the interface bandwidth of the destination TSN domain is determined as the slice bandwidth shared by the multiple target service transmission requests; If there are multiple target service transmission requests, the source TSN domains of the multiple target service transmission requests are the same, and the interface bandwidth of the source TSN domain is less than or equal to the sum of the interface bandwidths of the destination TSN domains of the multiple target service transmission requests, then the interface bandwidth of the destination TSN domain of each target service transmission request is determined as the slice bandwidth of each target service transmission request.

4. The method according to claim 2, characterized in that: The target service transmission request further includes: service transmission start time, the source TSN domain information further includes: service transmission path within the source TSN domain, and the destination TSN domain information further includes: edge device identifier and destination network device identifier of the destination TSN domain; Determining the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information, including: Determine the transmission delay of the source TSN domain according to the data volume of the service data, the interface bandwidth of the source TSN domain, and the total number of hops of the service transmission path in the source TSN domain; Determine a transmission delay of the FlexE domain according to the data volume of the service data and the slice bandwidth corresponding to the target service transmission request; Determine the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain; An end-to-end delay is determined according to the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, and the transmission delay of the destination TSN domain.

5. The method according to claim 4, characterized in that Determining the transmission delay of the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, the transmission delay of the FlexE domain, the edge device identifier of the destination TSN domain, the destination network device identifier, the data volume of the service data, and the interface bandwidth of the destination TSN domain, including: Determine the time when the service data arrives at the destination TSN domain according to the service transmission start time, the transmission delay of the source TSN domain, and the transmission delay of the FlexE domain; Determine a service transmission path within the destination TSN domain according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier; The transmission delay of the destination TSN domain is determined according to the data volume of the service data, the interface bandwidth of the destination TSN domain, and the number of hops corresponding to the service transmission path in the destination TSN domain.

6. The method according to claim 5, characterized in that Determining a service transmission path within the destination TSN domain according to the time when the service data arrives at the destination TSN domain, the edge device identifier of the destination TSN domain, and the destination network device identifier, including: Obtaining service information being processed in the target TSN domain; Determine an initial service transmission path set corresponding to the target service transmission request according to the edge device identifier of the target TSN domain and the target network device identifier; The initial service transmission path set is screened according to the time when the service data arrives at the destination TSN domain and the service information being processed in the destination TSN domain to obtain the service transmission path in the destination TSN domain.

7. A cross-domain service transmission device, characterized in that: The cross-domain service transmission device is configured in a global controller of a network system, the network system comprising: a source time-sensitive network TSN controller, a destination TSN controller, a flexible Ethernet FlexE controller and a global controller, the source TSN controller and the destination TSN controller belong to different TSN domains, and the cross-domain service transmission device comprises: A target service transmission request receiving module is used to receive a target service transmission request sent by a source TSN controller, wherein the target service transmission request includes: service data, service transmission start time, source TSN domain information, destination TSN domain information and delay threshold; A slice bandwidth determination module, used to determine the slice bandwidth corresponding to the target service transmission request according to the source TSN domain information and the destination TSN domain information; An end-to-end delay determination module, configured to determine the end-to-end delay according to the slice bandwidth corresponding to the target service transmission request, the service data, the source TSN domain information, and the destination TSN domain information; The service transmission module is used to send the slice bandwidth corresponding to the target service transmission request to the FlexE controller if the end-to-end delay is less than the delay threshold, so that the FlexE controller divides the network slice for the target service transmission request according to the slice bandwidth corresponding to the target service transmission request, and sends the service data to the destination TSN controller through the above network slice.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the cross-domain service transmission method described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the cross-domain service transmission method described in any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the computer program implements the cross-domain service transmission method according to any one of claims 1 to 6.

Images