Scheduling method and device of time-sensitive network equipment, equipment and storage medium

Abstract

The invention provides a scheduling method and device of time-sensitive network equipment, equipment and a storage medium, which run in a cluster of a cloud platform, and the method comprises the following steps: obtaining registration information of each TSN equipment in the cluster, and executing synchronization of each TSN equipment when the registration information changes; the TSN-CRD is monitored, a workflow for synchronizing the change is generated when the TSN-CRD is changed, and the TSN-CRD comprises self-defined parameters required by TSN scheduling; and obtaining time slice information of each TSN device in the TSN-CRD through the workflow, generating a YANG configuration file according to the time slice information, data arrival time information defined in the TSN-CRD and registration information of the TSN device, and issuing the YANG configuration file to the corresponding TSN device. According to the invention, information collection, accurate scheduling and automatic configuration of the bottom-layer time-sensitive network equipment are realized based on a cloud scheduling framework.

Description

Technical Field

[0001] The present application relates to the field of industrial control technology, and in particular to a scheduling method, apparatus, device, and storage medium for time-sensitive network equipment. Background Art

[0002] Currently, Time-Sensitive Network (TSN) control is primarily implemented through the Data Distribution Service (DDS) implemented by various vendors. However, with the increasing adoption of TSN in cloud environments, and the numerous devices within the cloud that need to work together, traditional TSN control can no longer meet the requirements for efficient and automated scheduling. While various vendors' Data Distribution Services (DDS) offer some configuration delivery capabilities, they lack a unified scheduling framework and automated mechanisms. Summary of the Invention

[0003] In view of this, the present application proposes a scheduling method, apparatus, device, and storage medium for time-sensitive network devices, which realize information collection, precise scheduling, and automatic configuration of underlying time-sensitive network devices based on a cloud scheduling framework.

[0004] In a first aspect, the present application provides a scheduling method for a time-sensitive network device, which runs in a cluster on a cloud platform, and the method includes:

[0005] Obtain registration information of each TSN device in the cluster, and synchronize each TSN device when the registration information changes;

[0006] Monitor the TSN-CRD and generate a workflow to synchronize the changes when the TSN-CRD changes. The TSN-CRD includes custom parameters required for TSN scheduling.

[0007] The time slice information of each TSN device in the TSN-CRD is obtained through the workflow, and a YANG configuration file is generated according to the time slice information, the data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and is sent to the corresponding TSN device.

[0008] From the above, the method provided by this application runs in the cluster of the cloud platform, and obtains the registration information of each TSN device in the cluster. When the registration information changes, full synchronization of each TSN device is performed to ensure the consistency of the information. By defining TSN-CRD (Time-Sensitive Network-Custom Resource Definitions, time-sensitive network scheduling custom resources) to describe the custom parameters required for TSN scheduling, and monitoring the TSN-CRD, when the TSN-CRD changes, a workflow for synchronizing the changes is generated, so as to generate a YANG configuration file based on the time slice information of each TSN device in the TSN-CRD, the data arrival time information defined in the TSN-CRD, and the synchronized TSN device registration information, and send it to the corresponding TSN device, thereby realizing information collection, precise scheduling and automatic configuration of TSN devices.

[0009] In a possible implementation of the first aspect, the method further includes: receiving an execution response of the TSN device to the YANG configuration file, updating status information of the TSN device that executes the YANG configuration file, and synchronizing the status information to the cluster.

[0010] As shown above, after receiving the YANG configuration file, the TSN device will execute the corresponding configuration and return the execution response. Based on these responses, the device status information is updated and synchronized back to the cluster to ensure that the status information in the cluster is consistent with the actual situation.

[0011] In a possible implementation of the first aspect, the further step further includes: writing registration information of each TSN device into a ConfigMap configuration file;

[0012] Obtaining the registration information of each TSN device in the cluster includes:

[0013] Read the ConfigMap configuration file in the cluster and obtain the registration information of each TSN device in the ConfigMap configuration file.

[0014] As mentioned above, ConfigMap is a cluster resource used to store configuration information. By writing the registration information of TSN devices into the ConfigMap configuration file, the ConfigMap configuration file in the cluster is read when the system starts to obtain the registration information of each TSN device in the ConfigMap configuration file.

[0015] In a possible implementation of the first aspect, generating the YANG configuration file includes:

[0016] The time slice information of each TSN device in the TSN-CRD, the defined data arrival time information, and the registration information of the TSN device are input into the scheduling algorithm, and the model or instruction set output by the scheduling algorithm is converted into the YANG configuration file.

[0017] As described above, the time slice information of each TSN device in TSN-CRD, the defined data arrival time information, and the information of the TSN device are used as the input of the scheduling algorithm, and the model or instruction set output by the scheduling algorithm is converted into a YANG configuration file format that can be understood by the TSN device, thereby realizing the generation process of the YANG configuration file.

[0018] In a possible implementation of the first aspect, the sending to the corresponding TSN device includes:

[0019] The YANG configuration file is converted into a NETCONF request and sent to the corresponding TSN device, where the corresponding TSN device is a TSN device corresponding to the changed TSN-CRD selected based on a scheduling algorithm.

[0020] As mentioned above, NETCONF (Network Configuration Protocol) is a protocol for configuring network devices. It completes link selection based on a scheduling algorithm to determine the TSN device corresponding to the changed TSN-CRD. The generated YANG configuration file is then converted into a NETCONF request and sent to the corresponding TSN device for configuration update.

[0021] In a possible implementation of the first aspect, the TSN-CRD includes a field for storing time slice information, which is used to describe the time scheduling requirements of each TSN device in the time sensitive network.

[0022] In a possible implementation manner of the first aspect, the change in the TSN-CRD includes at least one of the following:

[0023] Time slice reallocation, time slice length adjustment and time slice priority adjustment in the TSN-CRD.

[0024] As mentioned above, TSN-CRD can contain time slice information used to describe the scheduling requirements of each TSN device in the time-sensitive network. When the time slice information in the TSN-CRD changes, such as time slice reallocation, time slice length adjustment, and time slice priority adjustment, the scheduling process can be triggered to generate and distribute the YANG configuration file.

[0025] In a second aspect, the present application provides a scheduling apparatus for a time-sensitive network device, comprising an operation module and a control module deployed in a cluster on a cloud platform;

[0026] The control module is used to obtain the registration information of each TSN device in the cluster and perform synchronization of each TSN device when the registration information changes;

[0027] The operation module is used to monitor the TSN-CRD and generate a workflow that synchronizes the change when the TSN-CRD changes. The TSN-CRD includes custom parameters required for TSN scheduling.

[0028] The control module is further configured to obtain the time slice information of each TSN device in the TSN-CRD through the workflow, generate a YANG configuration file based on the time slice information, the data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and send the YANG configuration file to the corresponding TSN device.

[0029] In a third aspect, the present application provides a computing device, comprising:

[0030] processor;

[0031] a memory for storing one or more programs;

[0032] When the one or more programs are executed by the processor, the processor implements the above-mentioned scheduling method for a time-sensitive network device.

[0033] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the above-mentioned scheduling method for a time-sensitive network device when executed by a computer.

[0034] These and other aspects of the present application will become more apparent from the following description of the embodiment(s). BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 A flowchart of a scheduling method for a time-sensitive network device provided in an embodiment of the present application;

[0036] Figure 2 A structural diagram of a scheduling device for a time-sensitive network device provided in an embodiment of the present application;

[0037] Figure 3 A structural diagram of a computing device provided in an embodiment of the present application.

[0038] It should be understood that the sizes and shapes of the blocks in the above structural diagrams are for reference only and should not constitute an exclusive interpretation of the embodiments of this application. The relative positions and inclusion relationships between the blocks presented in the structural diagrams are only schematic representations of the structural relationships between the blocks, and do not limit the physical connection methods of the embodiments of this application. DETAILED DESCRIPTION

[0039] The technical solution provided by this application is further described below with reference to the accompanying drawings and examples. It should be understood that the system structure and business scenarios provided in the examples of this application are mainly for illustrating possible implementation methods of the technical solution of this application and should not be interpreted as the sole limitation of the technical solution of this application. It is known to those skilled in the art that with the evolution of the system structure and the emergence of new business scenarios, the technical solution provided by this application is also applicable to similar technical problems.

[0040] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art in the art of this application. In the event of any inconsistency, the meaning described in this specification or the meaning derived from the contents recorded in this specification shall prevail. In addition, the terms used herein are only for the purpose of describing the embodiments of the present application and are not intended to limit this application.

[0041] The embodiments of the present application propose a scheduling method, apparatus, device, and storage medium for time-sensitive network devices. The method can be run in a cluster of a cloud platform, including: obtaining registration information of each TSN device in the cluster, and synchronizing each TSN device when the registration information changes; monitoring the TSN-CRD and generating a workflow for synchronizing the change when the TSN-CRD changes, wherein the TSN-CRD includes custom parameters required for TSN scheduling; obtaining time slice information of each TSN device in the TSN-CRD through the workflow, generating a YANG (Yet Another Next Generation) configuration file based on the time slice information, data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and sending the YANG configuration file to the corresponding TSN device.

[0042] The embodiment of the present application obtains the registration information of each TSN device in the cluster and performs full synchronization of each TSN device when the registration information changes to ensure information consistency. The custom parameters required for TSN scheduling are described by defining TSN-CRD, and the TSN-CRD is monitored. When the TSN-CRD changes, a workflow for synchronizing the change is generated, so that a YANG configuration file is generated based on the time slice information of each TSN device in the TSN-CRD, the data arrival time information defined in the TSN-CRD, and the synchronized TSN device registration information, and is sent to the corresponding TSN device, thereby realizing information collection, precise scheduling, and automatic configuration of TSN devices.

[0043] In some embodiments, the cluster of the cloud platform can be implemented using the Kubernetes architecture deployed on the cloud platform. Kubernetes (often referred to as K8s) is an open source container cluster management system whose primary goal is to provide a platform for automating the deployment, scaling, and management of containerized applications. Kubernetes provides a mechanism for application deployment, planning, updating, and maintenance, making the deployment and management of containerized applications simple and efficient. Before introducing this method in detail, the following execution framework is first defined in Kubernetes:

[0044] Define TSN-CRDs: TSN-CRDs (Time-Sensitive Network-Custom Resource Definitions) are used in Kubernetes to describe various parameters required for TSN scheduling, such as time slice configuration, data arrival time, and priority rules. Operators or developers can configure and manage time-sensitive network scheduling by defining TSN-CRD objects.

[0045] Defining TSN-CRD-Operator: The TSN-CRD-Operator is an operational component running in Kubernetes that monitors and manages the state of TSN-CRD objects. When the state of a TSN-CRD object changes, the Operator triggers corresponding actions, such as updating configurations and generating workflows.

[0046] Defining the TSN-SDN-Controller: The TSN-SDN-Controller is the core control component of the time-sensitive network. It runs the scheduling algorithm and generates specific YANG configuration files based on the configuration information in the TSN-CRD and the registration information obtained from the device. The controller is responsible for communicating with TSN devices, issuing configurations, collecting status information, and updating the status of corresponding resources in Kubernetes.

[0047] Defining TSN-Device: TSN-Device represents the actual time-sensitive network device, which can receive and execute the configuration issued by the TSN-SDN-Controller. TSN devices need to support NETCONF or other configuration management protocols to communicate with the controller.

[0048] The following combination Figure 1 This paper introduces a scheduling method for a time-sensitive network device provided in an embodiment of the present application. The method can be specifically run in the Kubernetes architecture of the cloud platform. Kubernetes (usually referred to as K8s) is an open source container cluster management system whose main goal is to provide a platform for automating the deployment, expansion and management of containerized applications. Kubernetes provides a mechanism for application deployment, planning, updating and maintenance, making the deployment and management of containerized applications simple and efficient. Figure 1 As shown, the method includes:

[0049] S110: Obtain registration information of each TSN device in Kubernetes, and synchronize each TSN device when the registration information changes.

[0050] In this embodiment, Kubernetes is located in the cloud platform of the industrial system. When deploying the cloud platform, the available TSN (Time-Sensitive Network) device information can be registered through the Kubernetes ConfigMap resource. Specifically, the registration information of each TSN device can be written into the ConfigMap configuration file, which exists as a Kubernetes resource, and then the Kubernetes is initialized. For example, the ConfigMap configuration file can specifically include information such as the identification, address, and capabilities of the TSN device.

[0051] After the system is started, the ConfigMap configuration file in Kubernetes can be read through the TSN-SDN-Controller to obtain the registration information of each TSN device in the ConfigMap configuration file. When the registration information changes, the full amount of TSN device registration information is synchronized through the TSN-SDN-Controller.

[0052] It should be noted that the full synchronization process of each TSN device in this step is only executed when the registration information of the TSN device changes. When the registration and deployment of each TSN device in the cloud platform are completed, if the registration information does not change, there is no need to perform full synchronization of the TSN device when the system starts.

[0053] S120: Monitor the TSN-CRD, and generate a workflow for synchronizing the change when the TSN-CRD changes.

[0054] In Kubernetes, Custom Resource Definitions (CRD) is a way to extend the Kubernetes API, allowing users to define their own resource types. In this embodiment, by defining TSN-CRD, it can be used to describe the scheduling configuration of the time-sensitive network. The TSN-CRD can include fields, validation rules, etc., usually completed through a YAML file and applied to Kubernetes using the kubectl command. For example, the TSN-CRD can specifically include a field for storing time slice information, which is used to describe the time scheduling requirements of each TSN device in the time-sensitive network.

[0055] This step can be implemented using the TSN-CRD-Operator, which is an operator specifically designed to monitor and manage TSN-CRD resources. It can be written in Go and relies on the Kubernetes client-go library to interact with the API server. The Operator needs to implement the following functions:

[0056] · Monitor TSN-CRD resource change events (such as creation, update, and deletion).

[0057] · Execute corresponding logic according to the event type, such as parsing TSN-CRD configuration information.

[0058] · Generate workflows or call other services to synchronize configurations to the TSN-SDN-Controller.

[0059] After the TSN-CRD-Operator is deployed to Kubernetes in this embodiment, the TSN-CRD resources in Kubernetes can be monitored. When changes are detected in the TSN-CRD resources, such as time slice reallocation, time slice length adjustment, and time slice priority adjustment, the TSN-CRD-Operator can obtain the change and generate a corresponding workflow based on the change. The workflow may include a series of steps, such as verifying the configuration, preparing the environment, calling other services, etc. The TSN-CRD-Operator synchronizes the change information of the TSN-CRD to the TSN-SDN-Controller through the workflow, so that the TSN-SDN-Controller can generate a YANG configuration file based on the change information. Exemplarily, the synchronization process of the workflow can be achieved by calling the API interface provided by the TSN-SDN-Controller, sending messages, or using other communication mechanisms.

[0060] In some embodiments, the TSN-CRD-Operator can also monitor the status of the synchronization process and record relevant log information for troubleshooting and performance optimization.

[0061] S130: Obtain the time slice information of each TSN device in the TSN-CRD through the workflow, generate a YANG configuration file according to the time slice information, the data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and send it to the corresponding TSN device.

[0062] This step can be implemented through the TSN-SDN-Controller. As a controller component, the TSN-SDN-Controller is responsible for receiving the time slice information of each TSN device from the TSN-CRD, and combining it with the data arrival time information defined in the TSN-CRD and the existing TSN device registration information. It generates YANG configuration files through the scheduling algorithm and finally sends these YANG configuration files to specific TSN devices in the form of NETCONF requests. The process of generating YANG configuration files specifically includes:

[0063] The TSN-SDN-Controller takes the collected TSN device registration information, the time slice information of each TSN device in the changed TSN-CRD, and the data arrival time information defined in the TSN-CRD as input and passes it to the scheduling algorithm. The scheduling algorithm calculates the specific time slice that each TSN device should use based on this input information to ensure that data transmission in the TSN network meets the time sensitivity requirements;

[0064] The scheduling algorithm performs link selection to determine the TSN device corresponding to the changed TSN-CRD, and outputs a model or instruction set based on the above-mentioned TSN device registration information, the time slice information of each TSN device in the TSN-CRD, and the data arrival time information defined in the TSN-CRD. These models or instruction sets need to be converted into YANG configuration files that can be understood by specific network devices. The conversion process is performed by the TSN-SDN-Controller to generate a YANG configuration file suitable for the TSN device;

[0065] After generating the YANG configuration file, the TSN-SDN-Controller can convert the YANG configuration file into a NETCONF request and send it to the corresponding TSN device for configuration update. NETCONF (Network Configuration Protocol) is a protocol for network device configuration management that allows network administrators or automated tools to query and modify device configurations through XML-formatted messages.

[0066] In some embodiments, upon receiving a YANG configuration file, the corresponding TSN device parses the YANG configuration file, executes the corresponding configuration, and returns an execution response. Upon receiving the TSN device's execution response to the YANG configuration file, the TSN-SDN-Controller updates the status information of the TSN device executing the YANG configuration file and synchronizes it to Kubernetes, ensuring that the status information in Kubernetes is consistent with the actual situation.

[0067] In summary, the scheduling method for time-sensitive network devices provided by the embodiment of the present application can be run in Kubernetes. By obtaining the registration information of each TSN device in the Kubernetes, full synchronization of each TSN device is performed when the registration information changes to ensure the consistency of the information. By defining TSN-CRD to describe the custom parameters required for TSN scheduling, and monitoring the TSN-CRD, a workflow for synchronizing the changes is generated when the TSN-CRD changes, so as to generate a YANG configuration file based on the time slice information of each TSN device in the TSN-CRD, the data arrival time information defined in the TSN-CRD, and the synchronized TSN device registration information, and send it to the corresponding TSN device, thereby realizing information collection, precise scheduling and automatic configuration of TSN devices. Through the embodiment of the present application, the configuration efficiency and scheduling accuracy of time-sensitive network devices in the cloud environment can be greatly improved, the need for manual intervention can be reduced, and the stability and reliability of the entire system can be improved. At the same time, due to the adoption of a cloud-native technical architecture, the present invention also has good scalability and flexibility, and can adapt to cloud environments of different scales and requirements.

[0068] like Figure 2 As shown, the embodiment of the present application provides a scheduling device for a time-sensitive network device, which can be used to implement the above Figure 1 Any step of a scheduling method for a time-sensitive network device and its optional embodiments shown. Figure 2 As shown, the apparatus includes an operation module 210 and a control module 220 deployed in Kubernetes;

[0069] Among them, the control module 220 is used to obtain the registration information of each TSN device in Kubernetes, and perform synchronization of each TSN device when the registration information changes; the operation module 210 is used to monitor the TSN-CRD and generate a workflow to synchronize the change when the TSN-CRD changes. The TSN-CRD includes the custom parameters required for TSN scheduling; the control module 220 is also used to obtain the time slice information of each TSN device in the TSN-CRD through the workflow, generate a YANG configuration file based on the time slice information, the data arrival time information defined in the TSN-CRD and the information of the TSN device, and send it to the corresponding TSN device.

[0070] In some embodiments, the operation module 210 may be implemented by the TSN-CRD-Operator in the above embodiment, and the control module 220 may be implemented by the TSN-SDN-Controller in the above embodiment.

[0071] It should be understood that the devices or modules in the embodiments of the present application can be implemented by software, for example, they can be implemented by computer programs or instructions having the above functions, and the corresponding computer programs or instructions can be stored in the memory inside the terminal, and the processor reads the corresponding computer programs or instructions in the memory to implement the above functions. Alternatively, the devices or modules in the embodiments of the present application can also be implemented by hardware. Alternatively, the devices or modules in the embodiments of the present application can also be implemented by a combination of a processor and a software module.

[0072] It should be understood that the processing details of the devices or modules in the embodiments of the present application can be referred to Figure 1 The related descriptions of the illustrated embodiment and related extended embodiments will not be repeated in the embodiments of this application.

[0073] Figure 3 5 is a structural diagram of a computing device 500 provided in an embodiment of the present application. The computing device 500 includes: a processor 510, a memory 520, a communication interface 530, and a bus 540.

[0074] It should be understood that Figure 3 The communication interface 530 in the computing device 500 shown can be used to communicate with other devices.

[0075] The processor 510 may be connected to a memory 520. The memory 520 may be used to store the program code and data. Therefore, the memory 520 may be a storage unit within the processor 510, an external storage unit independent of the processor 510, or a component including both a storage unit within the processor 510 and an external storage unit independent of the processor 510.

[0076] Optionally, the computing device 500 may further include a bus 540. The memory 520 and the communication interface 530 may be connected to the processor 510 via the bus 540. The bus 540 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus 540 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 3 The fact that only one line is used does not mean that there is only one bus or one type of bus.

[0077] It should be understood that in the embodiment of the present application, the processor 510 can adopt a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. Alternatively, the processor 510 adopts one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.

[0078] The memory 520 may include a read-only memory and a random access memory, and provides instructions and data to the processor 510. A portion of the processor 510 may also include a non-volatile random access memory. For example, the processor 510 may also store information about the device type.

[0079] When the computing device 500 is running, the processor 510 executes the computer-executable instructions in the memory 520 to perform the operating steps of the above method.

[0080] It should be understood that the computing device 500 according to the embodiment of the present application can correspond to the corresponding subject in executing the method according to each embodiment of the present application, and the above-mentioned other operations and / or functions of each module in the computing device 500 are respectively for implementing the corresponding processes of each method of the present embodiment. For the sake of brevity, they will not be repeated here.

[0081] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software 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 beyond the scope of this application.

[0082] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0083] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection 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.

[0084] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0085] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0086] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute 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 USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0087] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the program is used to execute the above method, which includes at least one of the solutions described in the above embodiments.

[0088] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media.Computer-readable media can be computer-readable signal media or computer-readable storage media.Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or components, or any combination thereof.More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connection with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination thereof.In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0089] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0090] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

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

[0092] It should be noted that the embodiments described in this application are only a part of the embodiments of this application, rather than all of the embodiments. The components of the embodiments of the present application generally described and shown in the accompanying drawings can be arranged and designed in various different configurations. Therefore, the above detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the application for protection, but merely represents selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work are within the scope of protection of this application.

[0093] The words "first, second, third, etc." or module A, module B, module C and other similar terms in the specification and claims are only used to distinguish similar objects and do not represent a specific ordering of the objects. It is understandable that the specific order or sequence can be interchanged where permitted so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0094] In the above description, the numbers representing the steps involved do not necessarily mean that the steps must be executed. Intermediate steps may also be included or replaced by other steps. If permitted, the order of the previous and next steps may be interchanged or executed simultaneously.

[0095] The term "comprising" as used in the specification and claims should not be construed as limiting to what is listed thereafter; it does not exclude other elements or steps. Thus, it should be interpreted as specifying the presence of the features, integers, steps, or components mentioned, but not excluding the presence or addition of one or more other features, integers, steps, or components, or groups thereof. Thus, the expression "a device comprising means A and B" should not be limited to a device consisting solely of components A and B.

[0096] The term "one embodiment" or "an embodiment" mentioned in this specification means that the specific features, structures, or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present application. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing in various places in this specification do not necessarily refer to the same embodiment, but may refer to the same embodiment. In addition, in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0097] Note that the above are only preferred embodiments of the present application and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments, and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present application has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include many other equivalent embodiments without departing from the concept of the present invention, all of which fall within the scope of protection of the present invention.

Claims

1. A scheduling method for a time-sensitive network device, characterized in that: Running in a cluster on a cloud platform, the method includes: Obtain registration information of each TSN device in the cluster, and synchronize each TSN device when the registration information changes; Monitor the TSN-CRD and generate a workflow to synchronize the changes when the TSN-CRD changes. The TSN-CRD includes custom parameters required for TSN scheduling. The time slice information of each TSN device in the TSN-CRD is obtained through the workflow, and a YANG configuration file is generated according to the time slice information, the data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and is sent to the corresponding TSN device.

2. The method according to claim 1, characterized in that Also includes: Receive an execution response of the TSN device to the YANG configuration file, update status information of the TSN device that executes the YANG configuration file, and synchronize it to the cluster.

3. The method according to claim 1, characterized in that Also includes: Write the registration information of each TSN device into the ConfigMap configuration file; Obtaining the registration information of each TSN device in the cluster includes: Read the ConfigMap configuration file in the cluster and obtain the registration information of each TSN device in the ConfigMap configuration file.

4. The method according to claim 1, wherein Generating a YANG configuration file includes: The time slice information of each TSN device in the TSN-CRD, the defined data arrival time information, and the registration information of the TSN device are input into the scheduling algorithm, and the model or instruction set output by the scheduling algorithm is converted into the YANG configuration file.

5. The method according to claim 1, wherein The sending of the data to the corresponding TSN device includes: The YANG configuration file is converted into a NETCONF request and sent to the corresponding TSN device, where the corresponding TSN device is a TSN device corresponding to the changed TSN-CRD selected based on a scheduling algorithm.

6. The method according to claim 1, characterized in that The TSN-CRD includes a field for storing time slice information, which is used to describe the time scheduling requirements of each TSN device in the time sensitive network.

7. The method according to claim 1, characterized in that The TSN-CRD changes include at least one of the following: Time slice reallocation, time slice length adjustment and time slice priority adjustment in the TSN-CRD.

8. A scheduling device for a time-sensitive network device, characterized in that: Includes operation modules and control modules deployed in the cluster of the cloud platform; The control module is used to obtain the registration information of each TSN device in the cluster and perform synchronization of each TSN device when the registration information changes; The operation module is used to monitor the TSN-CRD and generate a workflow that synchronizes the change when the TSN-CRD changes. The TSN-CRD includes custom parameters required for TSN scheduling. The control module is further configured to obtain the time slice information of each TSN device in the TSN-CRD through the workflow, generate a YANG configuration file based on the time slice information, the data arrival time information defined in the TSN-CRD, and the registration information of the TSN device, and send the YANG configuration file to the corresponding TSN device.

9. A computing device, characterized in that include: processor; a memory for storing one or more programs; When the one or more programs are executed by the processor, the processor implements the scheduling method for a time-sensitive network device according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that A computer program is stored thereon, and when the computer program is executed by a computer, the scheduling method for a time-sensitive network device according to any one of claims 1 to 7 is implemented.

Images