Resource scheduling system, method and device of TSN, medium and product

Abstract

The embodiment of the invention provides a TSN resource scheduling system, method and device, a medium and a product, relates to the technical field of communication equipment, and aims to solve the problem that a general resource scheduling method cannot ensure low delay and low jitter of a TSN. The resource scheduling system of the TSN comprises a TSN controller and a plurality of network nodes, the plurality of network nodes comprise 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 for collecting service demand information of a node to which the TCB client belongs, and sending the service demand information to the TSN controller; and the TSN controller is used for carrying out resource scheduling according to the service demand information.

Description

Technical Field

[0001] The present application relates to the technical field of communication equipment, and in particular to a TSN resource scheduling system, method, device, medium and product. Background Art

[0002] Time-Sensitive Networking (TSN) is a communication network that provides deterministic low latency and low jitter over Ethernet.

[0003] At present, the end devices (i.e., the starting node and the destination node) of the time-sensitive network generally cannot communicate directly with the Centralized User Configuration (CUC), but collect the service requirements of the end devices manually 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 the Centralized Network Configuration (CNC) so that the CNC can schedule resources according to the service requirements.

[0004] The existing resource scheduling method relies on manual labor, and data transmission is required between CUC and CNC, which cannot guarantee the low latency and low jitter of TSN. Summary of the invention

[0005] The embodiments of the present disclosure provide a TSN resource scheduling system, method, device, medium, and product to solve the problem that general resource scheduling methods cannot guarantee low latency and low jitter of TSN.

[0006] In order to achieve the above objectives, this 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 include a starting node and a destination node; the starting node and the destination node are configured with a TSN configuration agent TCB client;

[0009] The TCB client is used to collect the service demand information of the TCB client's home node and send the service demand information to the TSN controller;

[0010] The TSN controller is used to schedule resources based on business demand information.

[0011] Optionally, the TSN controller includes: a TCB server, a central user configuration CUC and a central network configuration CNC;

[0012] The TCB server is used to obtain business demand information through the TCB client and send the business demand information to the CUC;

[0013] CUC is used to generate a traffic scheduling strategy based on the service demand information and send the traffic scheduling strategy to CNC; the traffic scheduling strategy is used to schedule the service flow corresponding to the service demand information;

[0014] The CNC is used to generate a service path for a service flow according to a traffic scheduling strategy and collected topology information of multiple network nodes.

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

[0016] Optionally, the CNC is further used to send network node configuration information corresponding to the service path to multiple network nodes; the network node configuration information is used to indicate configuration parameters of the network node configuration corresponding to the service path.

[0017] Optionally, the CNC is also used to periodically update topology information of multiple network nodes and / or configuration parameters of network nodes in the multiple network nodes.

[0018] Optionally, the CNC is also used to periodically update node information of multiple network nodes.

[0019] Optionally, the CUC is also used to manage a traffic scheduling algorithm for generating a traffic scheduling policy.

[0020] Optionally, the CUC is also used to display and manage node information of the TCB client's home node.

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

[0022] Receiving the service demand information of the TCB client belonging node sent by the TCB client; the TCB client is a client configured in the start node and the destination node; the start node and the destination node belong to multiple network nodes in the TSN network;

[0023] Resource scheduling is performed based on business demand information.

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

[0025] The communication unit is used to receive the service demand information of the TCB client belonging node sent by the TCB client; the TCB client is a client configured in the starting node and the destination node; the starting node and the destination node belong to multiple network nodes in the TSN network;

[0026] The processing unit is used to schedule resources according to business demand information.

[0027] In a fourth aspect, a computer-readable storage medium is provided, the computer-readable storage medium comprising computer execution instructions, and when the computer execution instructions are executed on a computer, the computer executes the resource scheduling method described in the second aspect.

[0028] In a fifth aspect, a computer program product is also provided. The computer program product includes a computer program or instructions. When the computer instructions are executed on a resource scheduling device, the resource scheduling device executes the resource scheduling method as described in the second aspect above.

[0029] It should be noted that the above computer instructions may be stored in whole or in part on a computer-readable storage medium, wherein the computer-readable storage medium may be packaged together with the processor of the resource scheduling device, or may be packaged separately from the processor of the resource scheduling device, which is not limited in the embodiments of the present application.

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

[0031] In the embodiments of the present application, the name of the resource scheduling device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear with other names. For example, the receiving unit may also be called 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 fall within the scope of the claims of the present application and their equivalent technologies.

[0032] The technical solution provided by this application brings at least the following beneficial effects:

[0033] Based on any of the above aspects, an embodiment of the present application provides a TSN resource scheduling system, including: 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 (TSN Configuration Broker, TCB) client. The TCB client is used to collect the business demand information of the TCB client's home node and send the business demand information to the TSN controller; the TSN controller is used to perform resource scheduling according to the business demand information.

[0034] As can be seen from the above, since the starting node and the destination node are configured with TCB clients, the TSN controller can collect the business demand information of the TCB client's node through the TCB client without manual operation, which improves the efficiency of resource scheduling. Secondly, the TSN controller can perform resource scheduling based on business demand information within itself, without the need for data transmission between CUC and CNC to perform resource scheduling, which further improves the efficiency of resource scheduling and ensures the low latency and low jitter of TSN.

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

[0036] Figure 1 It is a structural diagram of a general resource scheduling system;

[0037] Figure 2 A schematic diagram of the structure of a resource scheduling system provided in an embodiment of the present application;

[0038] Figure 3 A schematic diagram of the structure of another resource scheduling system provided in an embodiment of the present application;

[0039] Figure 4 A schematic diagram of the structure of another resource scheduling system provided in an embodiment of the present application;

[0040] Figure 5 A schematic diagram of the structure of another resource scheduling system provided in an embodiment of the present application;

[0041] Figure 6 A schematic diagram of a hardware structure of a communication device provided in an embodiment of the present application;

[0042] Figure 7 A schematic diagram of a resource scheduling method provided in an embodiment of the present application;

[0043] Figure 8 A flowchart of another resource scheduling method provided in an embodiment of the present application;

[0044] Fig. 9 A schematic diagram of the structure of a resource scheduling device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] It should be noted that, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0047] In order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and order of execution.

[0048] As described in the background art, TSN is a communication network that provides deterministic low latency and low jitter over Ethernet.

[0049] Figure 1 FIG. 1 shows a schematic diagram of the structure of a general TSN resource scheduling system. Figure 1 As shown, a general TSN resource scheduling system includes: multiple network nodes, CUC (for user management) and CNC (for network management).

[0050] The multiple network nodes may include: a starting node (also called a starting terminal, talker, etc.), an intermediate node and a destination node (also called a destination terminal, listener, etc.).

[0051] The starting node and the destination node can be control terminals in various scenarios, such as control equipment or control machines in industrial production, or switches in the scenario (some switches can also serve as initiators or receivers of business flows).

[0052] Intermediate nodes can be intermediate devices such as switches and gateways in various scenarios, such as TSN switches.

[0053] The staff can obtain the business flow requirements (such as periodicity, latency, etc.) of the starting node and the destination node through historical data or user needs, summarize the traffic characteristics, and enter the business flow requirements on the CUC configuration interface.

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

[0055] CNC can collect topology information, device port capabilities and other information of multiple network nodes, and perform resource scheduling based on the business requirements sent by CUC, that is, calculate the optimal gating scheduling solution for these business flows from the sending end to the receiving end based on the goals and constraints of these business flows.

[0056] Subsequently, CNC can send the above-mentioned gating scheduling scheme to each network node in the TSN network, and send the scheduling table (i.e., resource scheduling strategy) to CUC, which forwards it to the starting node and the destination node so that the starting node and the destination node can interact with each other in data flow.

[0057] As can be seen from the above, the existing resource scheduling method relies on manual work, which is time-consuming and labor-intensive, and has low efficiency. In addition, 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] In view of the above problems, an embodiment of the present application provides a TSN resource scheduling system, including: 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 (TSN Configuration Broker, TCB) client. The TCB client is used to collect the business demand information of the TCB client's home node and send the business demand information to the TSN controller; the TSN controller is used to perform resource scheduling according to the business demand information.

[0059] As can be seen from the above, since the starting node and the destination node are configured with TCB clients, the TSN controller can collect the business demand information of the TCB client's node through the TCB client without manual operation, which improves the efficiency of resource scheduling. Secondly, the TSN controller can perform resource scheduling based on business demand information within itself, without the need for data transmission between CUC and CNC to perform resource scheduling, which further improves the efficiency of resource scheduling and ensures the low latency and low jitter of TSN.

[0060] Figure 2 FIG. 1 shows a schematic diagram of a resource scheduling system for TSN provided by an embodiment of the present application. Figure 2 As shown, the TSN resource scheduling system includes: a TSN controller and multiple network nodes.

[0061] The plurality of network nodes include a starting node (eg Figure 2 Talker) and destination node (e.g. Figure 2 The start node and the destination node are configured with TCB clients.

[0062] Optionally, the start node and the destination node are also configured with a user program to receive information input by the user.

[0063] Optionally, the plurality of network nodes also include intermediate nodes, such as Figure 2 A TSN switch is shown.

[0064] The TCB client is used to collect the service demand information of the TCB client's home node and send the service demand information to the TSN controller.

[0065] The TSN controller is used to schedule resources based on business demand information.

[0066] Specifically, by deploying TCB clients on the start node and the destination node (also referred to as end devices), the start node and the destination node can communicate with each other, such as implementing 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 that is primarily used to exchange information in industrial automation systems. It is a service-based communication protocol that enables interoperability between a variety of different systems and devices.

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

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

[0070] Specifically, the TCB server can communicate with the TCB client on the end device to obtain the service traffic demand on the Talker and feed back the traffic 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 the service data flow information (i.e. service demand information) including source address, destination address, traffic characteristics such as protocol, time period, maximum number of messages per period, maximum message length, and delay requirements and send it to the TCB server in the TSN controller. The TCB server can store the above information in the library.

[0073] For example, assuming that the above-mentioned business data flow information is the business data flow information transmitted between various control devices in the factory, the source address and the destination address can be the addresses of various control devices in the factory, the protocol can be the transmission protocol between various control devices in the factory, and the time period can be the period for data transmission by various control devices in the factory, etc.

[0074] Another exemplary example is Figure 3 As shown, the TCB client can upload traffic demand and terminal information to the TCB server. The TCB server can interact with the CUC to obtain traffic scheduling calculation results and send the traffic scheduling calculation results 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. The two perform receiving and sending communications.

[0076] The UDP method is simple and easy to use, can be implemented using programming in a variety of languages, has low requirements for the peer device, and is easy to deploy.

[0077] Optionally, the terminal information collected by the TCB client and sent to the TCB server includes: the talker's network card IP, the number of ports and the MAC of each port, the port status, etc. The TCB client can use special fields to identify the terminal information.

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

[0079] After receiving the information sent by the TCB client, the TCB server can call the internal interface with the user configuration information received from the TCB client to notify the CUC of the addition or deletion of traffic, and save the data into the database or delete it.

[0080] The TCB server may also send traffic scheduling calculation results including flow identifiers, calculation scheduling results, etc. to the end device based on the TCB client.

[0081] The CUC is used to generate a traffic scheduling strategy based on the service demand 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 demand information.

[0082] Specifically, CUC can provide functions such as management interface, calculation scheduling, etc. of user business traffic.

[0083] In some embodiments, the CUC is also used to manage a traffic scheduling algorithm that generates a traffic scheduling policy.

[0084] In some embodiments, the CUC is also used to display and manage node information of the TCB client's home node.

[0085] For example, Figure 4 As shown, CUC may include a terminal management module, a traffic management module, a calculation scheduling module and an algorithm management module.

[0086] The traffic management module is used to provide a visual interface, display the collected traffic demands stored in the database in a table, and provide an interface for operations such as adding, deleting, modifying, and checking traffic.

[0087] The calculation scheduling module is used to provide a visual interface, perform scheduling calculations on the selected traffic selection algorithm, display the scheduling calculation results, and display the configuration data of each related TSN switch in a tabular form.

[0088] Optionally, the calculation scheduling module can also implement manual calculation scheduling and automatic calculation scheduling by setting switches.

[0089] When manually calculating and scheduling, the calculation and scheduling module can first select the required flow and perform calculation and scheduling.

[0090] When automatic calculation and scheduling is performed, all traffic can be automatically calculated when traffic is added or deleted, or a ring switch occurs in the topology, or a CUC port is linkdown or linkup.

[0091] The algorithm management module can provide a visual interface for selecting an algorithm manufacturer and importing an algorithm. Optionally, the algorithm management module can display the imported algorithm in a table format.

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

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

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

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

[0096] In some embodiments, the CNC is further used to send network node configuration information corresponding to the service path to multiple network nodes. The network node configuration information is used to indicate that the network node configures configuration parameters corresponding to the service path.

[0097] In some embodiments, the CNC is further used 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 also used to periodically update node information of multiple network nodes.

[0099] For example, Figure 5 As shown, the CNC may 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.

[0100] The topology discovery module is used to obtain TSN network device information (i.e., topology information of multiple network nodes) through the southbound interface of the controller, such as Netconf or SNMP, and obtain topological connection relationships through LLDP. Compare with the initial network to determine whether the topology has changed.

[0101] The network update module is used to update the network element and connection information into the database and update the network when the topology changes. When the network element configuration changes, it saves and updates the network configuration library.

[0102] The path calculation module is used to calculate the path based on manual or automatic invocation, input topology information and traffic demand information, and output path calculation results and configuration information.

[0103] The network configuration module is used to send the configuration information of each TSN switch to the switch and update the network configuration library when the path calculation has a solution.

[0104] The node management module and the node monitoring module are used to monitor and manage multiple network nodes.

[0105] like Figure 5 As shown, the database of the TCB server also includes: a network element information table, a connection table, a flow information table, a network element configuration data table and a terminal table.

[0106] In the embodiment of the present application, when the traffic management module of the CUC monitors the traffic demand change, it can send the traffic demand change information to the path calculation module of the CNC. In addition, when the calculation scheduling module of the CUC performs the scheduling calculation, it can also send the scheduling calculation result to the path calculation module of the CNC. In addition, when the network update module of the CNC monitors the topology change of the network node, it can also send the topology change information to the path calculation module of the CNC. In addition, the path calculation module can also obtain the device and topology information from the network element information table and the connection table, and obtain the flow information from the flow information table.

[0107] Subsequently, the path calculation module may perform path calculation according to the various types of information obtained above, and send the path calculation result to the network configuration module.

[0108] The network configuration module can notify the network update module to update the path network configuration according to the path calculation result.

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

[0110] The traffic management module can store the changed information in the traffic information table when the traffic changes (such as addition, deletion, or modification).

[0111] The terminal management module can store the changed information in the terminal table when a terminal changes (such as adding, deleting, or modifying).

[0112] When a node changes (such as adding, deleting, or modifying), the node management module can store the changed information in the network element information table and the connection table.

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

[0114] Each node or module in the above TSN resource scheduling system includes Figure 6 The communication device shown in FIG. Figure 6 Taking the communication device shown in the figure as an example, the hardware structure of the TSN resource scheduling system is introduced.

[0115] Figure 6 FIG. 1 is a schematic diagram showing a hardware structure of a communication device provided in an embodiment of the present application. 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 may be connected via the bus 64.

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

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

[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, or 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 can be accessed by a computer, but is not limited to these.

[0119] In a possible implementation, the memory 62 may exist independently of the processor 61, and the memory 62 may be connected to the processor 61 via a bus 64 to store instructions or program codes. When the processor 61 calls and executes the instructions or program codes stored in the memory 62, the resource scheduling method provided in the following embodiment of the present invention can be implemented.

[0120] In the embodiment of the present application, for the communication device, the software programs stored in the memory 62 are different, so the functions implemented by the communication device are different. The functions performed by each device will be described in conjunction with the following flowchart.

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

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

[0123] The bus 64 may be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0124] It should be pointed out that Figure 6 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 6 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0125] The resource scheduling method provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0126] An embodiment of the present application provides a resource scheduling method, which can be applied to a TSN controller in the above-mentioned TSN resource scheduling system.

[0127] Figure 7 A schematic diagram of a resource scheduling method provided in an embodiment of the present application is shown. Figure 7 As shown, under the premise of TSN network clock synchronization, the resource scheduling method includes:

[0128] S701. The TSN controller receives service demand information of a TCB client home node sent by a 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 multiple network nodes in the TSN network.

[0130] S702. The TSN controller performs resource scheduling according to the service demand information.

[0131] Figure 8 A schematic diagram of a process flow of another resource scheduling method provided in an embodiment of the present application is shown. Figure 8 As shown, under the premise of TSN network clock synchronization, the resource scheduling method includes:

[0132] S801. The terminal device calls the TCB client interface and inputs traffic demand (ie, business demand information).

[0133] S802. The TCB client communicates with the TCB server and reports traffic demand.

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

[0135] S804. CUC collects the flow demand of the terminal device and reports the flow demand to CNC through the internal interface.

[0136] S805. The CNC obtains topology information and device port capabilities.

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

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

[0139] S808. CNC obtains the scheduling calculation result and feeds it back to CUC, and sends the relevant device configuration information to the TSN switch (i.e., network node) to support the traffic requirements of the end device.

[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 terminal device.

[0143] S812: The starting node application sends the flow, and the destination node receives the flow.

[0144] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, it includes hardware structures and / or software modules corresponding to the 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 herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0145] The embodiment of the present application can divide the resource scheduling device into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. Optionally, the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0146] Fig. 9 FIG. 1 shows a schematic diagram of a resource scheduling device provided in an embodiment of the present application. Fig. 9 As shown, the resource scheduling device is applied to the TSN controller in the above resource scheduling system; the resource scheduling device includes: a communication unit 901 and a processing unit 902.

[0147] The communication unit 901 is used to receive the service demand information of the TCB client belonging node sent by the TCB client; the TCB client is the client configured in the starting node and the destination node; the starting node and the destination node belong to multiple network nodes in the TSN network.

[0148] The processing unit 902 is used to perform resource scheduling according to business demand information.

[0149] An embodiment of the present application also provides a computer-readable storage medium, which includes computer-executable instructions. When the computer-executable instructions are executed on a computer, the computer executes the resource scheduling method provided in the above embodiment.

[0150] The embodiment of the present application also provides a computer program, which can be directly loaded into a memory and contains software code. After being loaded and executed by a computer, the computer program can implement the resource scheduling method provided in the above embodiment.

[0151] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media can be any available media that can be accessed by general or special-purpose computers.

[0152] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be 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 devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the coupling or direct coupling or communication connection between each other shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may be a physical unit or multiple physical units, that is, it may be located in one place, or it may be distributed in multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0154] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on such an understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the general technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a U disk, a mobile hard disk, a ROM, a RAM, a disk, or an optical disk.

[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 changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on 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 include a starting node and a destination node; The starting node and the destination node are configured with a TSN configuration agent TCB client; The TCB client is used to collect the service demand information of the TCB client's home node and send the service demand information to the TSN controller; The TSN controller is used to perform resource scheduling according to the service demand information.

2. The resource scheduling system according to claim 1, characterized in that: 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 service requirement information through the TCB client and send the service requirement information to the CUC; The CUC is used 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 used to schedule the service flow corresponding to the service demand information; The CNC is used to generate a service path of the service flow according to the traffic scheduling strategy and the collected topology information of multiple network nodes.

3. The resource scheduling system according to claim 2, characterized in that: The CNC is further configured to send the service path to the TCB client home node through the CNC, the TCB server and the TCB client.

4. The resource scheduling system according to claim 2, characterized in that: The CNC is further used to send network node configuration information corresponding to the service path to the multiple network nodes; the network node configuration information is used to instruct the network nodes to configure configuration parameters corresponding to the service path.

5. The resource scheduling system according to claim 2, characterized in that: The CNC is also used to periodically update the topology information of the multiple network nodes and / or the configuration parameters of the network nodes in the multiple network nodes.

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

7. The resource scheduling system according to claim 2, characterized in that: The CUC is also used to manage a traffic scheduling algorithm that generates a traffic scheduling policy.

8. The resource scheduling system according to claim 2, characterized in that: The CUC is also used to display and manage node information of the TCB client's home node.

9. A resource scheduling method, characterized in that: A TSN controller applied to a resource scheduling system according to any one of claims 1 to 8; the method comprising: Receiving service demand information of a node to which the TCB client belongs, which is 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 the TSN network; Resources are scheduled according to the business demand information.

10. A resource scheduling device, characterized in that: A TSN controller applied to a resource scheduling system according to any one of claims 1 to 8; the resource scheduling device comprises: a communication unit and a processing unit; The communication unit is used to receive the service demand information of the TCB client belonging node sent by the TCB client; the TCB client is a client configured in the starting node and the destination node; the starting node and the destination node belong to multiple network nodes in the TSN network; The processing unit is used to perform resource scheduling according to the business demand information.

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

12. A computer program product, characterized in that The computer program product comprises: a computer program or instructions, which, when executed on a computer, causes the computer to perform the method according to claim 9 .

Images