Resource scheduling system, method, device, medium and product for time sensitive networking (TSN)

Abstract

Embodiments of the present disclosure provide a TSN resource scheduling system, method, device, medium and product, relating to the technical field of communication devices, to solve the problem that a general resource scheduling method cannot guarantee low delay and low jitter of TSN. The TSN resource scheduling system comprises a TSN controller and a plurality of network nodes; the plurality of network nodes comprise a start node and a destination node; the start node and the destination node are configured with a TSN configuration agent (TCB) client; the TCB client is configured to collect service requirement information of a node to which the TCB client belongs, and send the service requirement information to the TSN controller; and the TSN controller is configured to perform resource scheduling according to the service requirement information.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication devices, and in particular to a resource scheduling system, method and device for a time-sensitive network (TSN), a medium and a product. BACKGROUND

[0002] A time-sensitive network (TSN) is a communication network that provides deterministic low latency and low jitter based on Ethernet.

[0003] Currently, end devices (i.e., start nodes and destination nodes) of a time-sensitive network cannot directly communicate with a centralized user configuration (CUC), but instead collect service requirements of the end devices in an artificial manner and configure the service requirements of the end devices in the CUC. Subsequently, the CUC can send the service requirements of the end devices to a centralized network configuration (CNC) so that the CNC performs resource scheduling according to the service requirements.

[0004] Existing resource scheduling methods rely on manual work and data transmission between the CUC and the CNC, which cannot guarantee low latency and low jitter of the TSN. SUMMARY

[0005] Embodiments of the present disclosure provide a resource scheduling system, method and device for a time-sensitive network (TSN), and a medium and a product to solve the problem that general resource scheduling methods cannot guarantee low latency and low jitter of the TSN.

[0006] To achieve the above object, the present application adopts the following technical solutions:

[0007] In a first aspect, a resource scheduling system for a time-sensitive network (TSN) is provided, comprising a TSN controller and a plurality of network nodes.

[0008] The plurality of network nodes comprises start nodes and destination nodes, and the start nodes and the destination nodes are configured with a TSN configuration broker (TCB) client.

[0009] The TCB client is configured to collect service requirement information of a node to which the TCB client belongs and send the service requirement information to the TSN controller.

[0010] The TSN controller is configured to perform resource scheduling according to the service requirement information.

[0011] Optionally, the TSN controller comprises a TCB server, a centralized user configuration (CUC) and a centralized network configuration (CNC).

[0012] The TCB server is configured to acquire service requirement information through the TCB client, and send the service requirement information to the CUC.

[0013] The CUC is configured to generate a traffic scheduling strategy according to the service requirement information, and send the traffic scheduling strategy to the CNC; the traffic scheduling strategy is configured to schedule a service flow corresponding to the service requirement information.

[0014] The CNC is configured to generate a service path of the service flow according to the traffic scheduling strategy and topology information of the plurality of network nodes.

[0015] Optionally, the CNC is further configured to send the service path to a TCB client home node through the CNC, the TCB server and the TCB client.

[0016] Optionally, the CNC is further configured to send network node configuration information corresponding to the service path to the plurality of network nodes; the network node configuration information is configured to instruct the network nodes to configure configuration parameters corresponding to the service path.

[0017] Optionally, the CNC is further configured to periodically update topology information of the plurality of network nodes, and / or configuration parameters of the network nodes in the plurality of network nodes.

[0018] Optionally, the CNC is further configured to periodically update node information of the plurality of network nodes.

[0019] Optionally, the CUC is further configured to manage a traffic scheduling algorithm for generating the traffic scheduling strategy.

[0020] Optionally, the CUC is further configured to display and manage node information of the TCB client home node.

[0021] In a second aspect, a resource scheduling method is provided, and is applied to a TSN controller in the resource scheduling system in the first aspect; the method comprises:

[0022] receiving service requirement information of a TCB client home node sent by a TCB client; the TCB client is a client configured in a start node and a destination node; the start node and the destination node belong to a plurality of network nodes in a TSN network;

[0023] performing resource scheduling according to the service requirement information.

[0024] In a third aspect, a resource scheduling device is provided, and is applied to a TSN controller in the resource scheduling system in the first aspect; the resource scheduling device comprises a communication unit and a processing unit.

[0025] a communication unit configured to receive traffic demand information of a TCB client home node from a TCB client, the TCB client being a client configured in a start node and a destination node, the start node and the destination node belonging to a plurality of network nodes in a TSN network;

[0026] a processing unit configured to perform resource scheduling according to the traffic demand information.

[0027] In a fourth aspect, a computer-readable storage medium is provided, which includes computer-executable instructions that, when executed on a computer, cause the computer to perform the resource scheduling method of the second aspect.

[0028] In a fifth aspect, a computer program product is also provided, which includes computer programs or instructions that, when executed on a resource scheduling apparatus, cause the resource scheduling apparatus to perform the resource scheduling method of the second aspect.

[0029] It should be noted that the computer instructions described above can be stored on the computer-readable storage medium in whole or in part. The computer-readable storage medium can be packaged together with the processor of the resource scheduling apparatus, or can be packaged separately from the processor of the resource scheduling apparatus, and the embodiments of the present application do not limit this.

[0030] The third aspect, the fourth aspect, and the fifth aspect of the present application can refer to the detailed description of the first aspect and the second aspect.

[0031] In the embodiments of the present application, the name of the resource scheduling apparatus described above does not constitute a limitation on the device or functional module itself, and in actual implementation, these devices or functional modules can appear with other names. For example, the receiving unit can also be referred to as a receiving module, a receiver, etc. As long as the functions of each device or functional module are similar to those of the present application, they belong to the scope of the claims of the present application and their equivalents.

[0032] The technical solutions provided by the present application at least bring the following beneficial effects:

[0033] Based on any of the above aspects, the embodiments of the present application provide a resource scheduling system of a TSN, which includes a TSN controller and a plurality of network nodes; wherein the plurality of network nodes include a start node and a destination node; the start node and the destination node are configured with a TSN configuration broker (TCB) client. The TCB client is configured to collect traffic demand information of a TCB client home node, and send the traffic demand information to the TSN controller; the TSN controller is configured to perform resource scheduling according to the traffic demand information.

[0034] From the above, since the start node and the destination node are configured with the TCB client, the TSN controller can collect the service requirement information of the TCB client belonging node through the TCB client, without manual operation, thereby improving the efficiency of resource scheduling. Secondly, the TSN controller can perform resource scheduling according to the service requirement information in its internal, without performing resource scheduling through data transmission between the CUC and the CNC, thereby further improving the efficiency of resource scheduling, and ensuring low delay and low jitter of the TSN.

[0035] The beneficial effects of the first aspect, the second aspect, the third aspect, the fourth aspect and the fifth aspect of the present application can refer to the analysis of the beneficial effects above, and will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1 FIG. 1 is a structural schematic diagram of a general resource scheduling system;

[0037] Figure 2 FIG. 2 is a structural schematic diagram of a resource scheduling system provided by an embodiment of the present application;

[0038] Figure 3 FIG. 3 is a structural schematic diagram of another resource scheduling system provided by an embodiment of the present application;

[0039] Figure 4 FIG. 4 is a structural schematic diagram of another resource scheduling system provided by an embodiment of the present application;

[0040] Figure 5 FIG. 5 is a structural schematic diagram of another resource scheduling system provided by an embodiment of the present application;

[0041] Figure 6 FIG. 6 is a hardware structural schematic diagram of a communication device provided by an embodiment of the present application;

[0042] Figure 7 FIG. 7 is a flow schematic diagram of a resource scheduling method provided by an embodiment of the present application;

[0043] Figure 8 FIG. 8 is a flow schematic diagram of another resource scheduling method provided by an embodiment of the present application;

[0044] Figure 9 FIG. 9 is a structural schematic diagram of a resource scheduling device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0045] With reference to the drawings and the embodiments of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by a person of ordinary skill in the art without creative effort are within the protection scope of the present application.

[0046] It should be noted that in the embodiments of the present application, the words such as “exemplary” or “for example” are used to represent an example, illustration or description. Any embodiment or design scheme described as “exemplary” or “for example” in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words such as “exemplary” or “for example” are intended to present the relevant concept in a specific manner.

[0047] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words such as “first”, “second” are used to distinguish the same items or similar items with basically the same function and role, and a person of ordinary skill in the art can understand that the words such as “first”, “second” are not used to limit the quantity and execution order.

[0048] As described in the background, TSN is a communication network that provides low delay and low jitter with determinism based on Ethernet.

[0049] Figure 1 The structure of a general TSN resource scheduling system is shown. As shown in Figure 1 The general TSN resource scheduling system includes a plurality of network nodes, a CUC (for user management) and a CNC (for network management).

[0050] The plurality of network nodes can include a start node (also referred to as a start terminal, talker, etc.), an intermediate node and a destination node (also referred to as a destination terminal, listener, etc.).

[0051] The start node and the destination node can be control terminals in various scenarios, such as control devices or control machines in industrial production, or switches (some switches can also act as initiators or receivers of service flows) in the scenario, etc.

[0052] The intermediate node can be an intermediate device such as a switch or a gateway in various scenarios, for example, a TSN switch.

[0053] The worker can obtain the service flow requirements (such as periodicity, delay requirements, etc.) of the start node and the destination node through historical data or user demand, summarize the traffic characteristics, and input the service flow requirements on the configuration interface of the CUC.

[0054] The CUC can send the service requirements of the terminal device to the CNC through the user network interface (UNI).

[0055] CNC can collect information such as the topology and device port capabilities of multiple network nodes, and perform resource scheduling based on the service requirements sent by CNC. That is, it calculates the optimal gating scheduling scheme for the service flow from the sending end to the receiving end by combining the target and constraints of these service flows.

[0056] Subsequently, the CNC can distribute the above-mentioned gating scheduling scheme to each network node in the TSN network, and send the scheduling table (i.e., resource scheduling policy) to the CUC. The CUC will then forward it to the starting node and the destination node, enabling the starting node and the destination node to interact with each other's data streams.

[0057] As can be seen from the above, existing resource scheduling methods rely on manual labor, which is time-consuming, labor-intensive, and inefficient. Furthermore, CUC and CNC are two independent devices, and data transmission is required between CUC and CNC, which cannot guarantee the low latency and low jitter of TSN.

[0058] To address the aforementioned issues, this application provides a resource scheduling system for a TSN, comprising: a TSN controller and multiple network nodes; wherein the multiple network nodes include a starting node and a destination node; the starting node and the destination node are configured with a TSN Configuration Broker (TCB) client. The TCB client is used to collect service requirement information from the node to which the TCB client belongs and to send the service requirement information to the TSN controller; the TSN controller is used to perform resource scheduling based on the service requirement information.

[0059] As shown above, since both the starting and destination nodes are configured with TCB clients, the TSN controller can directly collect the service demand information of the TCB client's home node through the TCB client without manual operation, thus improving the efficiency of resource scheduling. Secondly, the TSN controller can perform resource scheduling internally based on service demand information, without needing to perform resource scheduling through data transmission between the CUC and CNC, further improving the efficiency of resource scheduling and ensuring the low latency and low jitter of the TSN.

[0060] Figure 2 A schematic diagram of the structure of the resource scheduling system for TSN provided in an embodiment of this application is shown. Figure 2 As shown, the resource scheduling system of this TSN includes: a TSN controller and multiple network nodes.

[0061] Multiple network nodes include the starting node (e.g.) Figure 2 Talker in the middle) and destination node (e.g.Figure 2 The starting node and the destination node are configured with a TCB client.

[0062] Optionally, the starting node and the destination node are further configured with a user program, which can receive information input by a user.

[0063] Optionally, the plurality of network nodes further include an intermediate node, for example Figure 2 The TSN switch is shown.

[0064] The TCB client is configured to collect traffic demand information of a TCB client home node and send the traffic demand information to a TSN controller.

[0065] The TSN controller is configured to perform resource scheduling according to the traffic demand information.

[0066] Specifically, on the starting node and the destination node (which can also be referred to as an end device), by deploying a TCB client, the starting node and the destination node can interact and communicate, for example, to implement an OPC UA (Open Platform Communications Unified Architecture) based system application based on the OPC UA protocol.

[0067] OPC UA is an industrial communication protocol mainly used for exchanging information in industrial automation systems. It is a service-based communication protocol that enables interoperability between various systems and devices.

[0068] In some embodiments, the TSN controller includes a TCB server, a CUC, and a CNC.

[0069] The TCB server is configured to obtain traffic demand information through the TCB client and send the traffic demand information to the CUC.

[0070] Specifically, the TCB server can communicate with the TCB client on the end device, obtain traffic flow demand on the Talker, and feed back the flow scheduling result to the Talker.

[0071] The TCB client can communicate with the TCB server in the TSN controller and provide an interface to communicate with the user program.

[0072] The TCB client can describe and send traffic data stream information (i.e., traffic demand information) including source address, target address, traffic characteristics such as protocol, time period, maximum number of messages per period, maximum message length, and delay requirements to the TCB server in the TSN controller. The TCB server can store the above information into a database.

[0073] For example, assuming that the service data stream information is the service data stream information transmitted between various control devices in a factory, the source address and the destination address can be the addresses of various control devices in the factory, the protocol can be a transmission protocol between various control devices in the factory, and the time period can be a data transmission period of various control devices in the factory.

[0074] For another example, as shown in Figure 3 The TCB client can upload traffic demand and terminal information to the TCB server. The TCB server can interact with the CUC to obtain a traffic scheduling calculation result and send the traffic scheduling calculation result to the TCB client.

[0075] When the TCB client communicates with the TCB server in the TSN controller, the communication protocol can use UDP, the TCB server listens on port number 9002, and the TCB client listens on port number 8002, and the two perform receiving and sending communication.

[0076] The UDP method is simple and easy to use, can be programmed in multiple languages, and has low requirements for the end device, facilitating deployment.

[0077] Optionally, the terminal information collected by the TCB client and sent to the TCB server includes the IP of the network card of the talker, the number of ports, the MAC of each port, the state of the port, and the like. The TCB client can use a special field to identify the terminal information.

[0078] The user configuration information collected by the TCB client and sent to the TCB server includes the related information of the talker and the QoS demand of the flow, specifically including: flow identification, source MAC, flow destination MAC, VLAN ID, priority, delay requirement, jitter requirement, maximum frame number, maximum frame length, flow operation identification (addition, deletion), and the like.

[0079] After receiving the information sent by the TCB client, the TCB server can call an internal interface to notify the CUC of the addition or deletion of traffic and save the data in the database or delete the data.

[0080] The TCB server can also send the traffic scheduling calculation result to the end device based on the TCB client, including the flow identification and the calculation scheduling result.

[0081] The CUC is configured to generate a traffic scheduling strategy according to the service demand information and send the traffic scheduling strategy to the CNC. The traffic scheduling strategy is configured to schedule a service flow corresponding to the service demand information.

[0082] Specifically, the CUC can provide a user service traffic management interface and a calculation scheduling function.

[0083] In some embodiments, the CUC is further configured to manage a traffic scheduling algorithm for generating a traffic scheduling policy.

[0084] In some embodiments, the CUC is further configured to display and manage node information of a TCB client home node.

[0085] As shown in Figure 4 the CUC can include a terminal management module, a traffic management module, a computing scheduling module, and an algorithm management module.

[0086] The traffic management module is configured to provide a visual interface, display collected traffic demands stored in a database in a table, and provide an interface for adding, deleting, modifying, and querying traffic.

[0087] The computing scheduling module is configured to provide a visual interface, select an algorithm for selected traffic, perform scheduling computation, display scheduling computation results, and display configuration data of each related TSN switch in a table.

[0088] Optionally, the computing scheduling module can also implement manual and automatic scheduling computation by setting a switch.

[0089] When performing manual scheduling computation, the computing scheduling module can first select required traffic for scheduling computation.

[0090] When performing automatic scheduling computation, when traffic is added or deleted, or when topology switching occurs, a link of the CUC is down or up, all traffic can be automatically computed.

[0091] The algorithm management module can provide a visual interface for importing algorithms selected by an algorithm vendor. Optionally, the algorithm management module can display the imported algorithms in a table.

[0092] The terminal management module is configured to discover terminals (i.e., end devices), provide a visual interface, and display terminal information and network card port information in a table.

[0093] The CNC is configured to generate a service path of a service flow according to a traffic scheduling policy and collected topology information of multiple network nodes.

[0094] Specifically, the CNC can provide management of TSN switches (i.e., multiple network nodes) and TSN-related configuration distribution.

[0095] In some embodiments, the CNC is further configured to send a service path to a TCB client home node through the CNC, a TCB server, and a TCB client.

[0096] In some embodiments, the CNC is further configured to send network node configuration information corresponding to the traffic path to the plurality of network nodes. The network node configuration information is configured to instruct the network nodes to configure configuration parameters corresponding to the traffic path.

[0097] In some embodiments, the CNC is further configured to periodically update topology information of the plurality of network nodes, and / or configuration parameters of the network nodes in the plurality of network nodes.

[0098] In some embodiments, the CNC is further configured to periodically update node information of the plurality of network nodes.

[0099] As shown in FIG. 1, the CNC can include a network update module, a topology discovery module, a path calculation module, a network configuration module, a node management module, and a node monitoring module. Figure 5 The topology discovery module is configured to obtain TSN network device information (i.e., topology information of the plurality of network nodes) through a southbound interface of the controller, such as Netconf or SNMP, and obtain topology connection relationships through LLDP. The topology discovery module is configured to compare the initial network and determine whether there is a topology change.

[0100] The network update module is configured to update the network element and connection information in the database and update the network when there is a topology change. The network update module is configured to save and update the network configuration database when there is a change in the network element configuration.

[0101] The path calculation module is configured to perform manual or automatic path calculation based on input topology information and traffic demand information, and output path calculation results and configuration information.

[0102] The network configuration module is configured to send configuration information of each TSN switch to the switch and update the network configuration database when there is a solution to the path calculation.

[0103] The node management module and the node monitoring module are configured to monitor and manage the plurality of network nodes.

[0104] As shown in FIG. 2, the database of the TCB server further includes a network element information table, a connection table, a traffic information table, a network element configuration data table, and a terminal table.

[0105] Figure 5

[0106] ​​In this embodiment, when the CUC's traffic management module detects a change in traffic demand, it can send the traffic demand change information to the CNC's path calculation module. Furthermore, when the CUC's calculation and scheduling module performs scheduling calculations, it can also send the scheduling calculation results to the CNC's path calculation module. Additionally, when the CNC's network update module monitors a topology change in a network node, it can also send topology change information to the CNC's path calculation module. Moreover, the path calculation module can also obtain device and topology information from the network element information table and the connection table, as well as traffic information from the traffic information table.

[0107] Subsequently, the path calculation module can perform path calculations based on the various types of information obtained above, and send the path calculation results to the network configuration module.

[0108] The network configuration module can notify the network update module to update the path network configuration based on the path calculation results.

[0109] The network update module can store topology information in the database, that is, store topology information in the network element information table and connection table, and can also store configuration information in the database, that is, store configuration information in the network element configuration data table.

[0110] The traffic management module can store the changed information in the traffic information table when traffic changes occur (e.g., additions, deletions, or modifications).

[0111] The terminal management module can store the changed information in the terminal table when there are changes to the terminal (such as additions, deletions, or modifications).

[0112] The node management module can store the changed information in the network element information table and connection table when a node changes (e.g., adding, deleting, or modifying).

[0113] The node monitoring module can monitor node information through the network element information table and the connection table.

[0114] Each node or module in the aforementioned TSN resource scheduling system includes Figure 6 The components included in the communication device shown. The following are examples... Figure 6 Taking the communication device shown as an example, the hardware structure of the TSN resource scheduling system is introduced.

[0115] Figure 6 A schematic diagram of a hardware structure of a communication device provided in an embodiment of this application is shown. Figure 6 As shown, the communication device includes a processor 61, a memory 62, a communication interface 63, and a bus 64. The processor 61, the memory 62, and the communication interface 63 can be connected via the bus 64.

[0116] The processor 61 is a control center of the communication device, which can be one processor or a collective term of multiple processing elements. For example, the processor 61 can be a general-purpose CPU, or other general-purpose processors, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0117] As an embodiment, the processor 61 can include one or more CPUs, such as the CPU 0 and the CPU 1 shown in FIG. 6. Figure 6

[0118] The memory 62 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.

[0119] In a possible implementation, the memory 62 can exist independently of the processor 61, and the memory 62 can be connected to the processor 61 through the bus 64, for storing instructions or program codes. When the processor 61 invokes and executes the instructions or program codes stored in the memory 62, the resource scheduling method provided in the embodiments of the present application can be implemented.

[0120] In the embodiments of the present application, the software programs stored in the memory 62 of the communication device are different, and therefore the functions implemented by the communication device are different. The functions performed by each device will be described in conjunction with the flowcharts below.

[0121] In another possible implementation, the memory 62 can also be integrated with the processor 61.

[0122] The communication interface 63 is used for connecting the communication device with other devices through a communication network, which can be an Ethernet, a wireless access network, a wireless local area network (WLAN), etc. The communication interface 63 can include a receiving unit for receiving data, and a sending unit for sending data.

[0123] ​The bus 64 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 6 In the drawings, only one thick line is used to represent the bus, but it does not mean that there is only one bus or only one type of bus.

[0124] It should be noted that, Figure 6 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 6 The communication device can include more or fewer components than shown, or combine certain components, or different component arrangements, in addition to the components shown.

[0125] The resource scheduling method provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0126] The embodiments of the present application provide a resource scheduling method, which can be applied to the TSN controller in the resource scheduling system of the TSN.

[0127] Figure 7 A flowchart of a resource scheduling method provided by the embodiments of the present application is shown, as Figure 7 Under the premise of TSN network clock synchronization, the resource scheduling method includes:

[0128] S701, the TSN controller receives the service requirement information of the TCB client home node sent by the TCB client.

[0129] The TCB client is a client configured in the start node and the destination node; the start node and the destination node belong to a plurality of network nodes in the TSN network.

[0130] S702, the TSN controller performs resource scheduling according to the service requirement information.

[0131] Figure 8 A flowchart of another resource scheduling method provided by the embodiments of the present application is shown, as Figure 8 Under the premise of TSN network clock synchronization, the resource scheduling method includes:

[0132] S801, the end device calls the TCB client interface and inputs the traffic demand (i.e. service requirement information).

[0133] S802, the TCB client communicates with the TCB server to report traffic demand.

[0134] S803, the TCB server reports traffic demand to the CUC.

[0135] S804, the CUC collects traffic demand of end devices and reports traffic demand to the CNC through an internal interface.

[0136] S805, the CNC acquires topology information and device port capability.

[0137] S806, the CNC inputs traffic demand information, whole-network topology information, TSN switch capability and port traffic information, etc. required for scheduling calculation through the input interface of the calculation and scheduling module.

[0138] S807, the calculation and scheduling module acquires network model, traffic model, obtains scheduling constraint information, selects scheduling target and scheduling algorithm for calculation. If path calculation result is obtained, the calculation result is output through the scheduling calculation result output interface, and related device configuration information is output through the configuration data interface.

[0139] S808, the CNC feeds back the scheduling calculation result to the CUC, and issues related device configuration information to the TSN switch (i.e. network node) to support traffic demand of end devices.

[0140] S809, the CUC feeds back the traffic demand calculation result to the TCB server.

[0141] S810, the TCB server feeds back the traffic demand calculation result to the TCB client.

[0142] S811, the TCB client feeds back the traffic demand calculation result to the end device.

[0143] S812, the start node application sends a stream, and the destination node receives the stream.

[0144] The above mainly describes the scheme provided by the embodiments of the application from the perspective of method. To implement the above functions, it contains hardware structure and / or software module corresponding to execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in the present text, the application can be realized in the form of hardware or combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on specific application and design constraint conditions of the technical scheme. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the application.

[0145] The embodiments of the present application can divide the functional modules of the resource scheduling device according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module. Optionally, the division of the modules in the embodiments of the present application is illustrative, and is only a logical function division. In actual implementation, another division manner can be used.

[0146] Figure 9 A structure diagram of a resource scheduling device provided by an embodiment of the present application is shown. As shown in the figure, the resource scheduling device is applied to a TSN controller in the above resource scheduling system; the resource scheduling device comprises a communication unit 901 and a processing unit 902. Figure 9

[0147] The communication unit 901 is configured to receive service demand information of a TCB client home node sent by a TCB client; the TCB client is a client configured in a start node and a destination node; the start node and the destination node belong to a plurality of network nodes in a TSN network.

[0148] The processing unit 902 is configured to perform resource scheduling according to the service demand information.

[0149] The embodiments of the present application further provide a computer readable storage medium, which comprises computer execution instructions. When the computer execution instructions run on a computer, the computer execution instructions make the computer execute the resource scheduling method provided by the above embodiments.

[0150] The embodiments of the present application further provide a computer program, which can be directly loaded into a memory and contains software codes. The computer program can be loaded and executed by a computer to realize the resource scheduling method provided by the above embodiments.

[0151] Those skilled in the art should realize that, in one or more of the above examples, the functions described in the present application can be realized by hardware, software, firmware or any combination thereof. When realized by software, the functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium. The computer readable medium includes a computer readable storage medium and a communication medium, wherein the communication medium includes any medium that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0152] ​Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above division of functional modules is taken as an example, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0153] In several embodiments provided in the present application, it should be understood that the disclosed device and method can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner. For example, a plurality of units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units or components shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms. The units described as separate components can be or can not be physically separated, and the components shown as units can be one physical unit or a plurality of physical units, that is, can be located in one place, or can be distributed to a plurality of different places. Some or all units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0154] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of software functional unit. When the integrated unit is realized in the form of software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such understanding, the technical scheme of the embodiment of the present application essentially or the part of the common technology which makes contribution or the whole or part of the technical scheme can be embodied in the form of software product, which is stored in a storage medium and includes a plurality of instructions for making a device (which can be a single chip, a chip, etc.) or a processor execute all or part of the steps of the method described in each embodiment of the present application. The storage medium mentioned above includes: U disk, mobile hard disk, ROM, RAM, magnetic disk or optical disk and various program code storage media.

[0155] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto, any skilled person in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A resource scheduling system for a Time-Sensitive Network (TSN), characterized in that, include: TSN controller and multiple network nodes; The plurality of network nodes includes a starting node and a destination node; The starting node and the destination node are configured with a TSN configuration proxy TCB client; The TCB client is used to collect the service requirement information of the node to which the TCB client belongs, and send the service requirement information to the TSN controller; The TSN controller is used to perform resource scheduling based on the service requirement information; The TSN controller includes: a TCB server, a central user configuration CUC, and a central network configuration CNC; The TCB server is used to obtain the business requirement information through the TCB client and send the business requirement information to the CUC. The CUC is used to generate a traffic scheduling strategy based on the service requirement information and send the traffic scheduling strategy to the CNC; the traffic scheduling strategy is used to schedule the service flow corresponding to the service requirement information. The CNC is used to generate the service path of the service flow based on the traffic scheduling strategy and the collected topology information of multiple network nodes.

2. The resource scheduling system according to claim 1, characterized in that, The CNC is also used to send the service path to the home node of the TCB client through the CNC, the TCB server, and the TCB client.

3. The resource scheduling system according to claim 1, characterized in that, The CNC is also used to send network node configuration information corresponding to the service path to the plurality of network nodes; the network node configuration information is used to instruct the network nodes to configure configuration parameters corresponding to the service path.

4. The resource scheduling system according to claim 1, characterized in that, The CNC is also used to periodically update the topology information of the plurality of network nodes, and / or the configuration parameters of the network nodes among the plurality of network nodes.

5. The resource scheduling system according to claim 1, characterized in that, The CNC is also used to periodically update the node information of the multiple network nodes.

6. The resource scheduling system according to claim 1, characterized in that, The CUC is also used to manage the traffic scheduling algorithm that generates traffic scheduling policies.

7. The resource scheduling system according to claim 1, characterized in that, The CUC is also used to display and manage the node information of the node to which the TCB client belongs.

8. A resource scheduling method, characterized in that, The method is applied to a TSN controller in the resource scheduling system according to any one of claims 1-7; the method includes: The system receives service requirement information from the TCB client's home node; the TCB client is a client configured in the originating node and the destination node; the originating node and the destination node belong to multiple network nodes in the TSN network. Resource scheduling is performed based on the aforementioned business requirements information; The TSN controller includes: a TCB server, a central user configuration CUC, and a central network configuration CNC; The TCB server is used to obtain the business requirement information through the TCB client and send the business requirement information to the CUC. The CUC is used to generate a traffic scheduling strategy based on the service requirement information and send the traffic scheduling strategy to the CNC; the traffic scheduling strategy is used to schedule the service flow corresponding to the service requirement information. The CNC is used to generate the service path of the service flow based on the traffic scheduling strategy and the collected topology information of multiple network nodes.

9. A resource scheduling device, characterized in that, A TSN controller applied to the resource scheduling system according to any one of claims 1-7; the resource scheduling device includes: a communication unit and a processing unit; The communication unit is used to receive service requirement information of the TCB client's home node sent by the TCB client; the TCB client is a client configured in the originating node and the destination node; the originating node and the destination node belong to multiple network nodes in the TSN network; The processing unit is used to perform resource scheduling based on the business requirement information; The TSN controller includes: a TCB server, a central user configuration CUC, and a central network configuration CNC; The TCB server is used to obtain the business requirement information through the TCB client and send the business requirement information to the CUC. The CUC is used to generate a traffic scheduling strategy based on the service requirement information and send the traffic scheduling strategy to the CNC; the traffic scheduling strategy is used to schedule the service flow corresponding to the service requirement information. The CNC is used to generate the service path of the service flow based on the traffic scheduling strategy and the collected topology information of multiple network nodes.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer-executable instructions that, when executed on a computer, cause the computer to perform the method of claim 8.

11. A computer program product, characterized in that, The computer program product includes: a computer program or instructions that, when run on a computer, cause the computer to perform the method as described in claim 8.

Images