Controller system scheduling method, system and non-volatile storage medium

Abstract

The present invention discloses a controller system scheduling method, system and non-volatile storage medium. The method includes: a main controller receives a device association request; the main controller responds to the device association request, and based on global configuration information, the main controller determines the first domain controller to which the first domain device belongs, and the second domain controller to which the second domain device belongs from multiple domain controllers; the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device. The present invention solves the technical problems existing in the related art that the computing efficiency is not ideal and the interaction efficiency is low due to the limitations of the computing power of the controller system.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular to a controller system scheduling method, system and non-volatile storage medium. Background Art

[0002] Currently, the controller system generates forwarding scheduling parameters by calculating the internal topology and transmission configuration, and controls the communication and interaction between devices based on the generated forwarding scheduling parameters. However, as the complexity of the network topology and transmission configuration increases, the corresponding amount of calculation increases exponentially, placing a burden on the controller system. Especially for time-sensitive network type application scenarios, the calculation scheduling time requirements for the controller system are high. Insufficient computing power will cause the calculation scheduling time to time out, resulting in the inability to complete interactive control within the specified time, which in turn affects the normal operation of the time-sensitive network type controller system.

[0003] Currently, no effective solution has been proposed for the above-mentioned problems. Summary of the invention

[0004] The embodiments of the present invention provide a controller system scheduling method, system and non-volatile storage medium to at least solve the technical problems existing in the related art that the computing efficiency is not ideal and the interaction efficiency is low due to the limitation of the computing power of the controller system.

[0005] According to one aspect of an embodiment of the present invention, a controller system scheduling method is provided, comprising: a main controller receives a device association request, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, wherein the controller system at least includes the main controller and multiple domain controllers corresponding to the main controller; the main controller responds to the device association request, and determines, based on global configuration information, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device, the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation, and the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation.

[0006] According to another aspect of an embodiment of the present invention, a controller system scheduling method is provided, comprising: a first domain controller receives a first instruction, wherein the first instruction is obtained when a main controller receives a device association request requesting the main controller to perform a data transmission operation between a first domain device and a second domain device in the controller system, the main controller responds to the device association request, based on global configuration information, and determines from multiple domain controllers the first domain controller to which the first domain device belongs, the controller system at least includes the main controller and the multiple domain controllers corresponding to the main controller, the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; based on the first instruction, the first domain controller generates a first domain device and a second domain device. The first configuration information for association is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation; the second domain controller receives a second instruction, wherein the second instruction is obtained by the main controller responding to the device association request, based on the global configuration information, and determining the second domain controller to which the second domain device belongs from the multiple domain controllers when the main controller receives the device association request requesting the main controller to perform the data transmission operation on the first domain device and the second domain device in the controller system; based on the second instruction, the second domain controller generates the second configuration information for associating the first domain device and the second domain device, wherein the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation.

[0007] According to another aspect of an embodiment of the present invention, a controller system scheduling method is provided, comprising: a first domain device executes scheduling based on first configuration information to perform a data transmission operation with a second domain device, wherein the first configuration information is a first instruction obtained after a main controller receives a device association request requesting the main controller to associate the first domain device with the second domain device in a controller system, and determines a first domain controller to which the first domain device belongs from multiple domain controllers based on global configuration information in response to the device association request, and the first domain controller generates a first instruction for associating the first domain device with the second domain device based on the first instruction, the controller system at least comprising the main controller and the multiple domain controllers corresponding to the main controller, and the global configuration information The information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; the second domain device executes scheduling based on the second configuration information to perform the data transmission operation with the first domain device, wherein the second configuration information is obtained when the main controller receives the device association request requesting the main controller to perform the data transmission operation between the first domain device and the second domain device in the controller system, and responds to the device association request, based on the global configuration information, and determines from the multiple domain controllers that the second domain device belongs to the second domain controller. The second domain controller generates the second instruction for associating the first domain device with the second domain device based on the second instruction.

[0008] According to another aspect of an embodiment of the present invention, a controller system scheduling method is provided, comprising: a main controller receives a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, and the controller system includes at least the main controller and multiple domain controllers corresponding to the main controller; the main controller responds to the device association request and determines, based on global configuration information, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; the main controller sends a first instruction to the first domain controller and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate an instruction to associate the first domain device with the second domain device. first configuration information, the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device; based on the first instruction, the first domain controller generates the first configuration information, wherein the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform a data transmission operation; based on the second instruction, the second domain controller generates the second configuration information, wherein the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation; based on the first configuration information and the second configuration information, the first domain controller and the second domain controller respectively schedule the first domain device and the second domain device to perform the data transmission operation; the first domain device executes the scheduling based on the first configuration information to perform the data transmission operation with the second domain device; the second domain device executes the scheduling based on the second configuration information to perform the data transmission operation with the first domain device.

[0009] According to another aspect of an embodiment of the present invention, a controller system scheduling system is provided, comprising: a main controller, configured to receive a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, wherein the controller system at least comprises the main controller and a plurality of domain controllers corresponding to the main controller; in response to the device association request, determining, based on global configuration information, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the plurality of domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information comprises at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; sending a first instruction to the first domain controller, and sending a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate first configuration information for associating the first domain device with the second domain device second configuration information associated with the second domain device; the first domain controller is connected to the main controller and is used to generate the first configuration information based on the first instruction, wherein the first configuration information is used by the first domain controller to schedule the first domain device to perform a data transmission operation with the second domain device; the second domain controller is connected to the main controller and is used to generate the second configuration information based on the second instruction, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device; the first domain controller and the second domain controller are also used to schedule the first domain device to perform the data transmission operation with the second domain device based on the first configuration information and the second configuration information respectively; the first domain device is connected to the first domain controller and is used to perform scheduling based on the first configuration information and perform the data transmission operation with the second domain device; the second domain device is connected to the second domain controller and is used to perform scheduling based on the second configuration information and perform the data transmission operation with the first domain device.

[0010] According to another aspect of an embodiment of the present invention, a non-volatile storage medium is provided, wherein the non-volatile storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing any one of the controller system scheduling methods.

[0011] In an embodiment of the present invention, a distributed concept is adopted, and a device association request is received through a main controller, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, and the controller system at least includes the main controller and multiple domain controllers corresponding to the main controller; the main controller responds to the device association request, and based on global configuration information, determines a first domain controller to which the first domain device belongs, and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information at least includes any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device, and the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation, and the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation. The purpose of dividing domain controllers, reducing network complexity, and optimizing computing efficiency is achieved, and the technical effect of reducing computing time and improving interactive scheduling efficiency is realized, thereby solving the technical problems existing in related technologies that are due to the limitations of the computing power of the controller system, resulting in unsatisfactory computing efficiency and low interactive efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0013] Figure 1 It is a schematic diagram of an optional centralized configuration management architecture provided according to the relevant technology;

[0014] Figure 2 is a flow chart of an optional controller system scheduling method provided according to an embodiment of the present invention;

[0015] Figure 3 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention;

[0016] Figure 4 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention;

[0017] Figure 5 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention;

[0018] Figure 6 is an architectural block diagram of an optional controller system scheduling method provided according to an embodiment of the present invention;

[0019] Figure 7 is a schematic diagram of a network architecture of an optional controller system scheduling method provided according to an embodiment of the present invention;

[0020] Figure 8 is a data processing schematic diagram of an optional controller system scheduling method provided according to an embodiment of the present invention;

[0021] Fig. 9 is a schematic diagram of a configuration flow of an optional controller system scheduling method provided according to an embodiment of the present invention;

[0022] Fig.10 is a schematic diagram of an optional controller system scheduling system provided according to an embodiment of the present invention. DETAILED DESCRIPTION

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

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

[0025] For the convenience of description, some nouns or terms involved in the embodiments of the present application are explained below:

[0026] Time-Sensitive Network (TSN) is a set of protocol standards developed by the IEEE (Institute of Electrical and Electronics Engineers) 802.1 working group to build a more reliable, low-latency, and low-jitter Ethernet. It adds determinism to standard Ethernet to ensure real-time, deterministic, and reliable data transmission.

[0027] CUC (Centralized User Configuration) refers to the user's requirements for global network topology and traffic configuration.

[0028] CNC (Centralized Network Configuration) refers to centralized network planning and scheduling.

[0029] Software Define Network (SDN) is a network architecture that separates the control plane from the data plane of network devices to achieve flexible control of network traffic, making the network more intelligent and providing a good platform for core networks and applications.

[0030] The East-West Interface Protocol (East-West Bridge) is a special expression in the architecture based on software-defined networking. It is defined as a communication method between heterogeneous controllers to achieve the interaction of control information, thereby specifying strategies based on global network information and achieving logical centralized control.

[0031] The southbound interface protocol (southbound bridge) is a special expression in the architecture based on software-defined networking, which is used to control the lower-level network devices in the network.

[0032] The Northbound Interface Protocol (Northbound Bridge) is a special expression in the architecture based on software-defined networking, which is used to provide interactive functions between users and controller systems, enabling network managers to design and manage the network.

[0033] NETCONF (Network Configuration Protocol) is a protocol for communication between network management and network devices. Network management uses NETCONF protocol to issue, modify, and delete the configuration of remote devices. Network devices provide standardized application programming interfaces, and network management can manage network devices through NETCONF.

[0034] SNMP (Simple Network Management Protocol) is a protocol that can support network management systems to monitor the status of devices connected to the network.

[0035] REST API (REST Application Programming Interface) is an application programming interface that complies with the design principles of the representational state transfer architectural style.

[0036] OT network (Operational Technology) is an industrial network that realizes automated control of equipment and systems.

[0037] Figure 1 It is an optional centralized configuration management architecture diagram provided according to relevant technologies. The controller of the time-sensitive network implements centralized network planning and scheduling (CNC) based on the user's global network topology and traffic configuration requirements (CUC), and completes the rapid conversion and distribution of the business model to the time-sensitive network forwarding model.

[0038] At present, since the controller system of the time-sensitive network generates forwarding scheduling parameters by calculating the topology structure and traffic configuration, the time-sensitive network calculation scheduling algorithm is a non-deterministic polynomial problem, which increases exponentially with the increase of the complexity of the network topology and traffic configuration. In application scenarios such as industrial control or intelligent driving, there are strict requirements on the calculation scheduling time of the time-sensitive network controller. As the network scale and traffic configuration increase, the problem of exponential growth of calculation time limits the actual application.

[0039] In the typical architecture of software-defined networks, the controller system is divided into an application layer, a control layer, and a link layer. Among them, the control layer controls the global resources of the controller system, mainly controls the forwarding and transmission functions of the link layer, and is the core of control. Therefore, the computing power of the control layer has a great impact on the performance of the overall controller system. In related technologies, a single controller is often used to schedule network devices in the link layer. In actual applications, a single controller faces a large amount of computing. In the case of insufficient computing power, it is obviously easy to have a decrease in scheduling capability, which in turn affects the transmission capacity of network devices.

[0040] In response to the above problems, an embodiment of the present invention provides a method embodiment of a controller system scheduling method. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0041] Figure 2 is a flow chart of an optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 2 As shown, the method comprises the following steps:

[0042] Step S202, the main controller receives a device association request, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, wherein the controller system at least includes the main controller and a plurality of domain controllers corresponding to the main controller;

[0043] Step S204, the main controller determines, in response to the device association request, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers based on the global configuration information, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information;

[0044] Step S206: The main controller sends a first instruction to the first domain controller and a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device, and the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation, and the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation.

[0045] Through the above steps, the purpose of dividing domain controllers, reducing network complexity, and optimizing computing efficiency can be achieved, and the technical effect of reducing computing time and improving interactive scheduling efficiency can be achieved, thereby solving the technical problems existing in related technologies that are caused by the limitations of the computing power of the controller system, resulting in unsatisfactory computing efficiency and low interactive efficiency.

[0046] It should be noted that the above-mentioned execution subject is the main controller.

[0047] In the controller system scheduling method provided in the embodiment of the present invention, first, the main controller receives a device association request for requesting a first domain device to associate with a second domain device. Afterwards, the main controller responds to the device association request and determines a first domain controller of the first domain device and a second domain controller of the second domain device. The main controller sends a first instruction to the first domain controller and a second instruction to the second domain controller, the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device.

[0048] Optionally, the device association request can be multiple, for example, obtaining human-computer interaction information from the application layer through the northbound interface protocol. For ease of understanding, a specific example is given, for example, a network administrator issues an association request between a first domain device and a second domain device through a human-computer interaction device, the first domain device is, for example, computer 1, the second domain device is, for example, a printer, and the obtained human-computer interaction information is to execute document printing in computer 1. Through the application layer, the controller system accepts the device association request and associates computer 1 with the printer.

[0049] Optionally, there may be multiple ways to send the first instruction and the second instruction, for example, through an east-west interface protocol, the main controller communicates with multiple domain controllers in the control layer. It should be noted that the main controller, the first domain controller, and the second domain controller are located in the control layer of the software-defined network architecture. Compared with the single controller of the control layer in the related art, the embodiment of the present invention performs layered processing, and the control layer is divided into a main controller and multiple domain controllers, which embodies the distributed concept, and some of the computing and execution functions in the main controller are delegated to multiple domain controllers. In addition, through domain division processing, multiple domain devices are used to control domain devices in different domains respectively, and cross-domain interaction is achieved through the main controller, which divides a complex system into multiple subsystems, which is conducive to reducing the complexity of the controller system, reducing the scale of the overall system, and improving computing efficiency.

[0050] In an optional embodiment, when the above-mentioned global configuration information includes: the above-mentioned global topology configuration information; accordingly, the above-mentioned main controller sends a first instruction to the above-mentioned first domain controller, and sends a second instruction to the above-mentioned second domain controller, including: the above-mentioned main controller determines the first domain identifier corresponding to the above-mentioned first domain controller, and the second domain identifier corresponding to the above-mentioned second domain controller based on the above-mentioned global topology configuration information; the above-mentioned main controller determines the first transmission channel corresponding to the above-mentioned first domain identifier, and the second transmission channel corresponding to the above-mentioned second domain identifier; the above-mentioned main controller sends the above-mentioned first instruction to the above-mentioned first domain controller through the above-mentioned first transmission channel, and sends the above-mentioned second instruction to the above-mentioned second domain controller through the above-mentioned second transmission channel.

[0051] It can be understood that for each domain controller, it only controls one or more domain devices in the corresponding domain, and there is no need to obtain a domain identifier. For the main controller, it controls multiple domain controllers, and it is necessary to use domain identifiers to distinguish different domain controllers. Since the domain controller does not carry a domain identifier, the main controller determines the first transmission channel and the domain controller corresponding to the first transmission channel through the first domain identifier, and transmits the first instruction to the corresponding first domain controller via the first transmission channel. The second domain controller is processed in the same way.

[0052] Optionally, the first instruction and the second instruction have multiple forms, for example, the first instruction and the second instruction are information from which domain identifiers have been stripped.

[0053] It should be noted that the domain controller itself does not need to manage the corresponding domain identifier, which is conducive to reducing system complexity and improving computing efficiency. It should be noted that the main controller identifies the domain controller by identifying the transmission channel between the domain controller and the main controller, without querying the domain controller, which is conducive to reducing the processing time of the main controller.

[0054] In an optional embodiment, before the main controller determines, in response to the device association request and based on the global configuration information, the first domain controller to which the first domain device belongs and the second domain controller to which the second domain device belongs from the multiple domain controllers, it also includes: the main controller obtains preset configuration information and / or access configuration information, wherein the preset configuration information is configuration information of the controller system obtained through human-computer interaction, and the access configuration information is configuration information obtained by searching for domain devices connected to the controller system; the main controller generates the global configuration information according to the preset configuration information and / or the access configuration information.

[0055] It can be understood that, corresponding to a typical software-defined network architecture, the control layer is the core of computing scheduling. In the embodiment of the present invention, the control layer is divided into a main controller and multiple domain controllers, and the main controller controls multiple domain controllers. Therefore, the main controller is the core of the controller system in the embodiment of the present invention. The main controller obtains the preset configuration information obtained through human-computer interaction, and the configuration information obtained by searching for domain devices of the access controller system, such as link exploration. Based on the preset configuration information and / or the above-mentioned access configuration information, global configuration information is generated.

[0056] Optionally, the preset configuration information includes but is not limited to the following information: network configuration information, topology configuration information, and traffic configuration information between the main controller and the domain controller, and between the domain controller and multiple domain devices corresponding to the domain, which can be obtained through the application layer in the software-defined network architecture.

[0057] Optionally, the access configuration information includes but is not limited to the following information: network configuration information and topology configuration information of domain devices accessing the controller system. Since there are new access domain devices in the controller system, the new access domain devices are not configured through preset configuration information at this time, and link exploration and other methods are used to obtain the information through the link layer in the software-defined network architecture. This is conducive to the real-time update of global configuration information and improves the accuracy of global configuration information.

[0058] Optionally, the above-mentioned preset configuration information can be obtained in a variety of ways, such as: front-end static configuration, etc., configured by network management personnel, preset network configuration information in the control system, and topology configuration information. For ease of understanding, a specific example is given, for example: according to the application scenario of the controller system, such as industrial control scenario, intelligent driving scenario, etc., the multiple devices corresponding to the controller system are divided into domains, such as different application logics such as device location, device function, etc. are divided into different domains, and the corresponding domain controllers perform domain management respectively. Therefore, the topology configuration information in the preset configuration information at least includes: the topology configuration between the main controller and multiple domain controllers, and the topology configuration between the domain controller and the corresponding multiple domain devices in the domain. The network configuration information in the preset configuration information at least includes: the network configuration between the main controller and multiple domain controllers, and the network configuration between the domain controller and the corresponding multiple domain devices in the domain. The network configuration information also includes at least two aspects: time-sensitive network configuration and basic network feature configuration, wherein the network configuration of the time-sensitive network feature includes: clock synchronization configuration and time-sensitive network traffic import, and the basic network configuration includes: Layer 2 virtual LAN, media access control address and port virtual LAN configuration.

[0059] Optionally, the access configuration information can be obtained in a variety of ways, for example: through a southbound interface protocol (such as a network configuration protocol), using the back-end automatic link discovery function to obtain access configuration information, using the link layer discovery protocol (LLDP, Link Layer Discovery Protocol), broadcast domain discovery protocol (BDDP, Broadcast Domain Discovery Protocol) and other methods to perform network topology detection of time-sensitive networks, and for devices that are newly connected to the controller system, automatically complete the network configuration and topology configuration, and synchronize the new network configuration and new topology configuration from the corresponding domain controller to the main controller. For ease of understanding, a specific example is given, for example: through the southbound interface of the network configuration protocol of the domain controller to achieve communication with the underlying (link layer) switch, after a new device establishes a new physical connection with the controller system, through the back-end automatic link discovery function, the main controller obtains the network configuration information and topology configuration of the new device via the switch and the domain controller, and updates the existing global configuration information.

[0060] Optionally, the above-mentioned global configuration information may be multiple, for example: when the access configuration information is obtained through the back-end automatic link discovery method, the global configuration information is generated based on the preset configuration information and the above-mentioned access configuration information. When the access configuration information cannot be obtained through the back-end automatic link discovery method, the global configuration information is directly generated based on the preset configuration information. When the preset configuration information cannot be obtained through the front-end static configuration method, the global configuration information is generated based on the access configuration information.

[0061] It should be noted that, through the above method, the main controller centrally stores and maintains global configuration information, which is conducive to the network administrator directly obtaining the configuration information between any devices in the controller system, making it easier to change and distribute the configuration.

[0062] In an optional embodiment, the main controller obtains the access configuration information, including: the main controller obtains first access information, wherein the first access information is configuration information without a domain identifier obtained by searching for domain devices accessing the controller system; the main controller determines a third transmission channel corresponding to the first access information, and a third domain identifier corresponding to the third transmission channel, wherein the third domain identifier is used to distinguish between the multiple domain controllers, and the third transmission channel is used to transmit configuration information between the main controller and the multiple domain controllers; the main controller adds the third domain identifier to the first access information to obtain second access information, and uses the second access information as the access configuration information.

[0063] It can be understood that since there is no corresponding identification information in the domain controller, the first access information obtained by the main controller through the domain controller also has no corresponding identification information. In order to facilitate storage and maintenance by the main controller, domain identification processing needs to be added. The first access information is sent to the main controller through the third transmission channel. The main controller determines the third domain identification corresponding to the third transmission channel, and adds the third domain identification to the first access information, and obtains the access configuration information after encapsulation.

[0064] It should be noted that in order to facilitate unified storage by the main controller, the access configuration information needs to carry domain identification information. Since the configuration obtained by the back-end automatic link discovery does not carry a domain identification, the domain identification is only valid for the main controller. Therefore, by adding domain identification processing to the access configuration information, it is helpful to simplify the complexity of the controller system and facilitate the corresponding storage of the main controller.

[0065] In an optional embodiment, when the above-mentioned global configuration information includes: the above-mentioned global topology configuration information; accordingly, the above-mentioned main controller sends a first instruction to the above-mentioned first domain controller, and sends a second instruction to the above-mentioned second domain controller, including: the above-mentioned main controller determines whether the above-mentioned first domain controller and the second domain controller are the same; if the above-mentioned first domain controller and the second domain controller are not the same, then the above-mentioned main controller obtains the first port number corresponding to the above-mentioned first domain device through the above-mentioned first domain controller based on the above-mentioned global topology configuration information, and obtains the second port number corresponding to the above-mentioned second domain device through the above-mentioned second domain controller; the above-mentioned main controller establishes a mapping relationship between the above-mentioned first port number and the above-mentioned second port number; based on the above-mentioned mapping relationship, the above-mentioned main controller sends the above-mentioned first instruction to the above-mentioned first domain controller, and sends the above-mentioned second instruction to the above-mentioned second domain controller.

[0066] It can be understood that multiple domain controllers are associated through a main controller. When the first domain controller and the second domain controller are different, it is regarded as performing cross-domain scheduling. Since the domain controllers cannot communicate directly with each other, a mapping relationship between the first port number and the second port number is established through the main controller. Based on the mapping relationship and the device association request, a first instruction is sent to the first domain controller, and a second instruction is sent to the second domain controller.

[0067] Optionally, if the first domain controller and the second domain controller are the same, the first instruction is the same as the second instruction. The first domain controller and the first instruction are used as an example below: based on the global topology configuration information, the first domain controller uses the first instruction to generate first configuration information for associating the first domain device and the second domain device in the domain. The first domain controller can be replaced by the second domain controller, and the first instruction can be replaced by the second instruction.

[0068] It should be noted that, in the case of cross-domain scheduling, if the first domain device has an association relationship with multiple domain devices, wherein the multiple domain devices are in different domains from the first domain device, and the multiple domain devices can be in the same domain or in different domains, then the main controller obtains the port numbers corresponding to the multiple domain devices respectively through the corresponding domain controllers, and establishes a mapping relationship between the first port numbers corresponding to the first domain device.

[0069] It is still necessary to explain that since the scheduling between domain controllers needs to be implemented through the main controller, in order to reduce complexity, when scheduling across domains, it is only necessary to obtain the corresponding port number and implement cross-domain scheduling by establishing a mapping relationship. When the control layer is hierarchical and domain-divided by the main controller and the domain controller, establishing a port number mapping to perform cross-domain scheduling is conducive to reducing the complexity of the controller system and optimizing the call calculation method.

[0070] In an optional embodiment, when the above-mentioned global configuration information includes: the above-mentioned global traffic configuration information; accordingly, the above-mentioned main controller sends a first instruction to the above-mentioned first domain controller, and sends a second instruction to the above-mentioned second domain controller, including: the above-mentioned main controller determines whether the above-mentioned first domain controller and the above-mentioned second domain controller are the same; if the above-mentioned first domain controller and the above-mentioned second domain controller are the same, then the above-mentioned main controller obtains the target transmission information as the above-mentioned first instruction based on the above-mentioned device association request and the above-mentioned global traffic configuration information, and sends the above-mentioned first instruction to the above-mentioned first domain controller, wherein the above-mentioned target transmission information is used to instruct the above-mentioned first domain controller to generate the first configuration information for controlling the association between the first domain device and the second domain device.

[0071] It can be understood that the above-mentioned device association request makes an association request for certain domain devices, and the above-mentioned traffic configuration information is used to configure the data transmission processing between the domain devices in the controller system. Based on the above-mentioned device association request and the above-mentioned traffic configuration information, the target transmission information can be obtained. When the domain devices with an associated relationship correspond to the same domain controller, the target transmission information is directly used as the first instruction. It should be noted that when the first domain controller and the second domain controller are the same, the first instruction is the same as the second instruction. That is, the first instruction (second instruction) is sent to the above-mentioned first domain controller (second domain controller), and the first instruction (second instruction) is used to instruct the first domain controller (second domain controller) to generate the first configuration information for associating the first domain device with the second domain device. It should still be noted that the above-mentioned target transmission information is obtained by the main controller based on the device association request and the traffic configuration information, and is used to generate the first instruction. The first instruction is sent by the main controller to the first domain controller, and the first domain controller generates the first configuration information based on the first instruction.

[0072] Optionally, the first configuration information may be of multiple types, for example, the first configuration information includes: the association relationship between the first domain device and the second domain device, that is, the topology configuration information of the first domain device and the second domain device; the transmission path after the first domain device and the second domain device establish an association, the transmission traffic setting, that is, the traffic configuration information of the first domain device and the second domain device; the network configuration between the first domain device and the second domain device.

[0073] Optionally, the above traffic configuration information may include multiple forms, such as traffic allocation information when data is transmitted between multiple domain devices included in the controller system, or setting a threshold for transmission time when multiple domain devices transmit data, etc.

[0074] Optionally, in order to facilitate understanding, a specific example is given of the process of using the target transmission information as the first instruction. For example, in the case where the domain devices in the same domain controller control the domain to transmit data, the main controller will obtain the first instruction based on the target transmission information, and the main controller will directly transmit the first instruction to the corresponding domain controller. The above first instruction is sent by the main controller to the first domain controller for actually performing the transmission operation within the domain through the corresponding domain controller. The first instruction may also include clock synchronization information between the main controller and the first domain controller. Using the first instruction for synchronization is conducive to improving the accuracy of control of the main controller and the corresponding domain controller.

[0075] It should be noted that in order to simplify the system and reduce the computing pressure of the main controller, multiple domain controllers are used to share part of the processing. The main controller instructs the corresponding domain controller to perform data transmission through the target transmission information, and does not directly control multiple domain devices to perform data transmission. According to the distributed idea, the computing efficiency is effectively improved and the computing time is reduced.

[0076] In an optional embodiment, the method further includes: if the first domain controller and the second domain controller are not the same, the main controller determines the target transmission path in the target transmission information; the main controller divides the target transmission path into a first sub-path and a second sub-path according to the first domain controller and the second domain controller; the main controller determines the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the first sub-path and the second sub-path respectively; the main controller determines the first sub-transmission configuration information corresponding to the first sub-path, and the second sub-transmission configuration information corresponding to the second sub-path based on the target transmission information, the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the first sub-path and the second sub-path respectively; the main controller uses the first sub-transmission configuration information as the first instruction, and uses the second sub-transmission configuration information as the second instruction; the main controller sends the first instruction to the first domain controller, and sends the second instruction to the second domain controller.

[0077] It can be understood that, due to the cross-domain transmission, the main controller uses different domain controllers to schedule the corresponding domain devices, and the target transmission information needs to be processed, and the processed sub-transmission configuration information is used to generate instructions sent to the corresponding domain controller. First, the target transmission path in the target transmission information is determined, and the target transmission path is divided into a first sub-path and a second sub-path according to the number of different domain controllers, and each sub-path corresponds to its own sub-transmission configuration information. In order to obtain the first sub-transmission configuration information corresponding to the first sub-path, and the second sub-transmission configuration information corresponding to the second sub-path, based on the target transmission path, the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the first sub-path and the second sub-path, respectively, the above formula is used to calculate, and Q1 is obtained as the first sub-transmission configuration information corresponding to the first sub-path, and Q2 is obtained as the second sub-transmission configuration information corresponding to the second sub-path. The first sub-transmission configuration information is used as the first instruction, and the second sub-transmission configuration information is used as the second instruction. The first instruction is sent to the first domain controller, and the second instruction is sent to the second domain controller.

[0078] Optionally, the target transmission information can be multiple. For example, it can be known from the above that the target transmission information is obtained by the device association request and the global traffic configuration information. The device association request at least provides the transmission start point and the transmission end point in the target transmission information, as well as the transmission path of the transmission process. The transmission start point and the transmission end point are both domain devices. The global traffic configuration information is based on the transmission start point and the transmission end point, and at least provides the transmission configuration information corresponding to the traffic allocation of the transmission process in the target transmission information. Therefore, the target transmission information at least includes the target transmission path and the corresponding transmission configuration information.

[0079] In an optional embodiment, it is characterized in that the main controller determines the first sub-transmission configuration information corresponding to the first sub-path and the second sub-transmission configuration information corresponding to the second sub-path based on the total number of switches corresponding to the target transmission path of the target transmission information and the number of switches corresponding to the first sub-path and the second sub-path respectively, including: the main controller determines the first sub-transmission configuration information corresponding to the first sub-path and the second sub-transmission configuration information corresponding to the second sub-path based on the total number of switches corresponding to the target transmission path of the target transmission information and the number of switches corresponding to the first sub-path and the second sub-path respectively in the following manner:

[0080] Q i =Q×P i / P

[0081] Among them, Q i is the i-th sub-transmission configuration information corresponding to the i-th sub-path; Q is the above target transmission information; P i is the number of switches corresponding to the i-th sub-path; P is the total number of switches corresponding to the above target transmission path.

[0082] It can be understood that the sub-transmission configuration information corresponding to each sub-path can be obtained through the above mathematical expression.

[0083] It should be noted that in actual data transmission, some domain devices belong to the same domain controller, while other domain devices belong to multiple other domain controllers. For ease of understanding, a specific example is given. For example, according to the received device association request, when the main controller instructs multiple different domain controllers to perform cross-domain transmission, data is transmitted between domain devices 1, domain device 2...domain device n, where domain device 1, domain device 2, and domain device 3 correspond to the first domain controller, domain device 4 corresponds to the second domain controller...domain device n corresponds to the n-2th domain controller. Based on the association request information, the target transmission information corresponding to the data transmission between domain devices 1, domain device 2...domain device n is obtained. Since the number of domain controllers involved is n-2, the target transmission path is divided into corresponding n-2 sub-paths, the first domain controller corresponds to the first sub-path, the second domain controller corresponds to the second sub-path...the n-2th domain controller corresponds to the n-2th sub-path. Afterwards, the total number of switches corresponding to the target transmission path is determined to be P, the number of switches corresponding to the first sub-path is P1, the number of switches corresponding to the second sub-path is P2...the number of switches corresponding to the n-2th sub-path is P n-2 Based on the target transmission information, the first sub-configuration information is obtained in the following manner:

[0084] Q1=Q×P1 / P

[0085] Among them, Q1 is the first sub-transmission configuration information corresponding to the first sub-path; Q is the above-mentioned target transmission information. Similarly, Q2 is the second sub-transmission configuration information corresponding to the second sub-path, until Q n-2 The n-2 transmission configuration information corresponding to the n-2 subpath. The first sub-configuration information is used as the first instruction, the second sub-transmission configuration information is used as the second instruction, until the n-2 sub-transmission configuration information is used as the above n-2 instruction. The first instruction is sent to the first domain controller until the n-2 domain controller sends the above n-2 instruction. The first instruction is used to instruct the first domain controller to generate the first configuration information for associating domain device 1, domain device 2, domain device 3 and domain device 4, and the second instruction is used to instruct the second domain controller to generate the second configuration information for associating domain device 4 with domain device 5, and so on.

[0086] It is still necessary to explain that when performing cross-domain transmission, that is, when multiple domain controllers are involved, if the target transmission information is directly used as the corresponding instruction sent to each domain controller involved, it will cause a transmission error. This is because the target transmission information corresponds to the entire transmission process, that is, the multiple domain controllers involved can be regarded as a whole, and the target transmission information is an instruction to the above multiple controllers as a whole. Therefore, based on the number of domains passed through, that is, the number of domain controllers involved, the target transmission path in the target transmission information is divided, and the above processing is used to obtain the sub-transmission configuration information corresponding to each sub-path. It can be regarded as dividing the target transmission information into sub-transmission configuration information, and using the sub-transmission configuration information as an instruction sent to the corresponding domain controller. Through the above processing, it is beneficial to ensure the reliability and accuracy of transmission in the case of cross-domain transmission.

[0087] Figure 3 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 3 As shown, the method comprises the following steps:

[0088] Step S302, the first domain controller receives a first instruction, wherein the first instruction is obtained when the main controller receives a device association request requesting the main controller to perform a data transmission operation between a first domain device and a second domain device in the controller system, and the main controller responds to the device association request, based on global configuration information, and determines from multiple domain controllers the first domain controller to which the first domain device belongs, wherein the controller system at least includes the main controller and the multiple domain controllers corresponding to the main controller, the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information;

[0089] Step S304: Based on the first instruction, the first domain controller generates first configuration information for associating the first domain device with the second domain device, wherein the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation;

[0090] Step S306, the second domain controller receives a second instruction, wherein the second instruction is obtained after the main controller responds to the device association request and determines the second domain controller to which the second domain device belongs from the multiple domain controllers based on the global configuration information, when the main controller receives the device association request requesting the main controller to perform the data transmission operation on the first domain device in the controller system with the second domain device.

[0091] Step S308: Based on the second instruction, the second domain controller generates second configuration information for associating the first domain device with the second domain device, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device.

[0092] It should be noted that the above execution entities are the first domain controller and the second domain controller.

[0093] Through the above steps S302 to S308, the domain controller (including the first domain controller and the second domain controller) executes the corresponding instructions issued by the main controller. For the first domain controller, the first configuration information is generated based on the first instruction, and for the second domain controller, the second configuration information is generated based on the second instruction. The first domain controller and the second domain controller share the calculation and processing process of the main controller by receiving the corresponding instructions, and schedule the domain devices in the domain by generating corresponding configuration information. Therefore, the main controller does not directly schedule each domain device, but issues corresponding instructions, which are processed by the domain controller, reflecting the idea of ​​​​layering and domain division, achieving the purpose of reducing network complexity and optimizing computing efficiency, and achieving the technical effect of reducing computing time and improving interactive scheduling efficiency, thereby solving the technical problems existing in the related technology that the computing efficiency is not ideal and the interactive efficiency is low due to the limitations of the computing power of the controller system.

[0094] Figure 4 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 4 As shown, the method comprises the following steps:

[0095] Step S402, the first domain device executes scheduling based on the first configuration information to perform a data transmission operation with the second domain device, wherein the first configuration information is obtained when the main controller receives a device association request requesting the main controller to associate the first domain device in the controller system with the second domain device for the data transmission operation, and responds to the device association request, based on the global configuration information, and determines from multiple domain controllers the first domain controller to which the first domain device belongs. The first domain controller generates, based on the first instruction, a first instruction for associating the first domain device with the second domain device, the controller system at least includes the main controller and the multiple domain controllers corresponding to the main controller, the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information;

[0096] Step S404, the second domain device executes scheduling based on the second configuration information to perform the data transmission operation with the first domain device, wherein the second configuration information is obtained after the main controller receives the device association request requesting the main controller to perform the data transmission operation between the first domain device in the controller system and the second domain device, and responds to the device association request, based on the global configuration information, and determines from the multiple domain controllers the second domain controller to which the second domain device belongs. Based on the second instruction, the second domain controller generates the second instruction for associating the first domain device with the second domain device.

[0097] It should be noted that the above execution subjects are the first domain device and the second domain device.

[0098] Through the above steps S402 to S404, it can be understood that the subject performing data transmission is the domain device (including the first domain device and the second domain device), and the main controller and the domain controller perform computing processing to jointly complete the scheduling of the domain devices. The technical effect of improving the efficiency of interactive scheduling solves the technical problems existing in the related art that the computing efficiency is not ideal and the interaction efficiency is low due to the limitations of the computing power of the controller system.

[0099] Figure 5 is a flowchart of another optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 5 As shown, the method comprises the following steps:

[0100] Step S502: The main controller receives a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, wherein the controller system at least includes the main controller and a plurality of domain controllers corresponding to the main controller;

[0101] Step S504, the main controller determines, in response to the device association request, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers based on the global configuration information, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information;

[0102] Step S506: the main controller sends a first instruction to the first domain controller and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device;

[0103] Step S508: Based on the first instruction, the first domain controller generates the first configuration information, wherein the first configuration information is used by the first domain controller to schedule the first domain device to perform a data transmission operation with the second domain device;

[0104] Step S510: Based on the second instruction, the second domain controller generates the second configuration information, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device;

[0105] Step S512: Based on the first configuration information and the second configuration information, the first domain controller and the second domain controller respectively schedule the first domain device and the second domain device to perform the data transmission operation;

[0106] Step S514, the first domain device executes scheduling based on the first configuration information, and performs the data transmission operation with the second domain device;

[0107] Step S516: the second domain device executes scheduling based on the second configuration information, and performs the data transmission operation with the first domain device.

[0108] It should be noted that in steps S502 to S516, the execution entities are the main controller, the first domain controller, the second domain controller, the first domain device, and the second domain device.

[0109] Through the above steps, the purpose of dividing domain controllers, reducing network complexity, and optimizing computing efficiency can be achieved, and the technical effect of reducing computing time and improving interactive scheduling efficiency can be achieved, thereby solving the technical problems existing in related technologies that are caused by the limitations of the computing power of the controller system, resulting in unsatisfactory computing efficiency and low interactive efficiency.

[0110] In the controller system scheduling method provided in an embodiment of the present invention, first, the main controller receives a device association request for requesting the first domain device to associate with the second domain device. Afterwards, the main controller responds to the device association request and determines the first domain controller of the first domain device and the second domain controller of the second domain device. The main controller sends a first instruction to the first domain controller and a second instruction to the second domain controller, the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device. The first domain controller generates the first configuration information, and the second domain controller generates the second configuration information. The first domain controller uses the first configuration information to control the first domain device, and the second domain controller uses the second configuration information to control the second domain device, and performs the association operation between the first domain device and the second domain device.

[0111] Based on the above embodiments and optional embodiments, the present invention proposes an optional implementation mode. For the sake of ease of understanding, specific examples are given. For example: the application scenario is set as follows: the controller system is a time-sensitive network system, which adopts a software-defined network architecture design and complies with the software-defined network concept to separate the data plane and the control plane. Through centralized control and distributed forwarding, flexible on-demand deployment of transmission scheduling is achieved. Figure 6 is an architectural block diagram of an optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 6 As shown, the controller system in this embodiment is divided into three parts: application layer, control layer and link layer. The application layer mainly provides human-computer interaction functions through network servers. The control layer is mainly the main controller and the domain controller through the east-west interface protocol to realize the specific control function of the time-sensitive network controller system. The control layer in the controller system of the time-sensitive network divides the main controller and the domain controller. The main controller is used to manage the domain controller and perform global configuration, including at least global topology configuration and global network configuration, which is reflected in hierarchical control processing. The domain controller controls more than domain devices with different application properties, which reflects the domain control processing. The time-sensitive network controller system performs hierarchical and domain processing, which is conducive to improving processing capabilities and is the core of control. The link layer is composed of a time-sensitive network switch and a time-sensitive network domain device. The control layer and the application layer use the RESTAPI interface to realize functions such as human-computer interaction, such as: application module development and resource orchestration, support topology discovery, user authentication, traffic management, path planning and other functions. The southbound interface protocols such as SNMP and NETCONF are used between the control layer and the link layer to realize the network configuration capability of OT network devices.

[0112] Figure 7is a schematic diagram of a network architecture of an optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 7 As shown in the figure, the hierarchical and domain-based time-sensitive network controller system is logically divided into multiple domains according to the application scenarios such as industrial control and intelligent driving, and the domain controller manages the domain controller, and the main controller manages the domain controller and maintains the global topology and network configuration information. In the field of industrial control, the two-layer and three-level network architecture of the traditional factory is gradually developing towards flattening and internet interconnection through time-sensitive networks. Under the flat network architecture, the field-level, workshop-level and factory-level networks can be divided into functional domains, and each functional domain can be further divided into smaller network domains according to the function and network flow. The field level can be further divided according to the production line. These domains have the same level, and the domain controller focuses on the control of data transmission within the domain. In the field of industrial control, reasonable division according to the existing network functions can realize the transmission of the main traffic within the domain, and at the same time, it can realize the rapid scheduling of cross-domain traffic. In the field of intelligent driving, the traditional bus network transmission structure is gradually transformed into the Ethernet co-line transmission mode of the time-sensitive network. At the same time, with the development of vehicle intelligence, whether it is the domain controller-based network architecture, the location-based management architecture based on the central computing management platform, or the distributed computing network architecture, they are gradually developing in the direction of domain division. Therefore, the domain division control of time-sensitive networks can better meet the actual application needs.

[0113] The main controller is the core of the control system scheduling. For the main controller, the data of the controller system is maintained based on the domain identifier. The domain identifier is used to index the corresponding domain controller. The main controller manages the domain controllers in a unified manner, and the domain controllers share part of the processing. When creating a new domain controller, the main controller establishes a connection with the domain controller and starts a thread to continue listening. Figure 8 is a data processing schematic diagram of an optional controller system scheduling method provided according to an embodiment of the present invention, such as Figure 8 As shown in the figure, based on the time-sensitive network controller system, the main controller and the domain controller in the control layer adopt the east-west interface protocol. In order to simplify the complexity of the system, after the main controller establishes the east-west protocol channel, it focuses on the processing of the information in and out of the transmission channel, and performs corresponding encapsulation and analysis, as shown in the figure. Figure 8 The stripping of domain identifiers and the encapsulation of domain identifiers are performed.

[0114] Fig. 9 is a schematic diagram of a configuration flow of an optional controller system scheduling method provided according to an embodiment of the present invention, such as Fig. 9As shown, there are two processing modes between the main controller and the domain controller, namely forward and reverse. The process of the main controller sending to the domain controller is regarded as forward processing, which is as follows: the main controller receives preset configuration information, which can be obtained through human-computer interaction at the application layer. The main controller selects a transmission channel with the domain controller according to the domain identifier, and sends the global configuration information after stripping the domain identifier to the corresponding domain controller through the corresponding transmission channel.

[0115] The process of sending from the domain controller to the main controller is considered as reverse processing, specifically: the domain controller obtains access information through link exploration, and link exploration includes link dynamic discovery and monitoring collection functions. Since the domain controller itself does not store the domain identifier, the corresponding domain identifier is stored in the main controller. Since the access information sent to the main controller does not carry the domain identifier, in order to facilitate the main controller to maintain global configuration information, the main controller needs to process the access information and obtain the access configuration information. The main controller determines the domain identifier corresponding to the transmission channel that sends the access information, adds the domain identifier to the access information, and obtains the processed access information as the access configuration information.

[0116] Based on the preset configuration information and the access configuration information, the main controller generates global configuration information. In the absence of any of the preset configuration information or the access configuration information, the main controller generates global configuration information based on one of them. After obtaining the global configuration information, the main controller can at least obtain the topology configuration and network configuration of any domain device in the time-sensitive network controller system. Based on the global configuration information, respond to the device association request to the main controller, determine the domain controller corresponding to the domain device, and send a control instruction to the corresponding domain controller. Since the domain devices are obtained after the domain division according to the actual devices of different application properties, under the actual transmission requirements, there are multiple domain devices in the same domain for data transmission, or there are multiple domain devices in different domains for data transmission. In the case of data transmission in the same domain, all domain devices in the same domain are scheduled and controlled by the domain controller, and the main controller sends the corresponding control instruction to the corresponding domain controller, and the corresponding domain controller executes the interaction processing between the control domain devices. In the case of cross-domain data transmission in different domains, since the target transmission information obtained by the main controller corresponds to the actual transmission demand, and each domain controller only controls the domain devices in the domain, for the multiple domain controllers involved in the cross-domain transmission process, directly sending the target transmission information to the corresponding multiple domain controllers will cause transmission scheduling errors. Therefore, the target transmission path in the target transmission information is determined, and divided according to the number of domain controllers passed by the target transmission path to obtain multiple sub-paths. Based on the target transmission information, the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the sub-paths, multiple sub-transmission configuration information corresponding to the multiple sub-paths is determined, and corresponding control instructions are generated based on the multiple sub-transmission configuration information. The main controller sends multiple control instructions to the corresponding domain controller, so that the domain controller generates configuration information for the devices in the domain, and based on the configuration information, the domain controller schedules the domain devices to complete the data transmission process.

[0117] The above optional implementation method can achieve at least one of the following effects: a time-sensitive network controller system with a hierarchical and domain-based architecture can be realized, supporting the abstraction and synchronization of topology information and network information from the main controller to the domain controller and from the domain controller to the main controller, thereby realizing that the main controller can provide global configuration information and quickly obtain intuitive topology and network information of the entire controller system. The processing pressure of the main controller can be shared through the domain controller, and the domain controller can be scheduled to perform scheduling processing within the domain, such as: gated computing, and the information exchange with the link layer switch can be realized through the NETCONF southbound interface protocol of the domain controller, which greatly reduces the network scale and transmission complexity, thereby improving computing efficiency and improving the efficiency of information exchange with the link layer switch.

[0118] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0119] A controller system scheduling system is also provided in an embodiment of the present invention. The controller system scheduling system provided in an embodiment of the present invention is introduced below.

[0120] Fig.10 is a schematic diagram of an optional controller system scheduling system provided according to an embodiment of the present invention, such as Fig.10 As shown, the system includes: a main controller 1002, a first domain controller 1004, a second domain controller 1006, a first domain device 1008, and a second domain device 1010, and the system is described below.

[0121] The main controller 1002 is used to receive a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, and the controller system at least includes the main controller and multiple domain controllers corresponding to the main controller; in response to the device association request, based on global configuration information, determine a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; send a first instruction to the first domain controller, and send a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device;

[0122] The first domain controller 1004 is connected to the main controller 1002 and is used to generate the first configuration information based on the first instruction, wherein the first configuration information is used by the first domain controller to schedule the first domain device to perform data transmission operations with the second domain device;

[0123] The second domain controller 1006 is connected to the main controller 1002, and is used to generate the second configuration information based on the second instruction, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device;

[0124] The first domain controller 1004 and the second domain controller 1006 are further configured to respectively schedule the first domain device and the second domain device to perform the data transmission operation based on the first configuration information and the second configuration information;

[0125] The first domain device 1008 is connected to the first domain controller 1004 and is used to execute the scheduling based on the first configuration information and perform the data transmission operation with the second domain device;

[0126] The second domain device 1010 is connected to the second domain controller 1006 and is used to execute scheduling based on the second configuration information and perform the data transmission operation with the first domain device.

[0127] In a controller system scheduling system provided by an embodiment of the present invention, through the main controller 1002, the first domain controller 1004, the second domain controller 1006, the first domain device 1008, and the second domain device 1010, the purpose of dividing the domain controller, reducing network complexity, and optimizing computing efficiency is achieved, and the technical effect of reducing computing time and improving interactive scheduling efficiency is achieved, thereby solving the technical problems existing in the related art that the computing efficiency is not ideal and the interactive efficiency is low due to the limitations of the computing power of the controller system.

[0128] It should be noted that the optional or preferred implementation of this embodiment can refer to the relevant description in the embodiment, which will not be repeated here.

[0129] An embodiment of the present invention provides a non-volatile storage medium on which a program is stored. When the program is executed by a processor, a controller system scheduling method is implemented.

[0130] An embodiment of the present invention provides an electronic device, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, the following steps are implemented: a main controller receives a device association request, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, wherein the controller system at least includes the main controller and multiple domain controllers corresponding to the main controller; the main controller responds to the device association request and determines, based on global configuration information, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information is global configuration information of the controller system. The information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; the above-mentioned main controller sends a first instruction to the above-mentioned first domain controller, and sends a second instruction to the above-mentioned second domain controller, wherein the above-mentioned first instruction is used to instruct the above-mentioned first domain controller to generate the first configuration information for associating the above-mentioned first domain device with the above-mentioned second domain device, and the above-mentioned second instruction is used to instruct the above-mentioned second domain controller to generate the second configuration information for associating the above-mentioned first domain device with the above-mentioned second domain device, and the above-mentioned first configuration information is used for the above-mentioned first domain controller to schedule the above-mentioned first domain device and the above-mentioned second domain device to perform the above-mentioned data transmission operation, and the above-mentioned second configuration information is used for the above-mentioned second domain controller to schedule the above-mentioned second domain device and the above-mentioned first domain device to perform the above-mentioned data transmission operation. The device in this article can be a server, a PC (computer), etc.

[0131] The present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that is initialized with the following method steps: a main controller receives a device association request, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, wherein the controller system at least includes the main controller and multiple domain controllers corresponding to the main controller; the main controller responds to the device association request and determines, based on global configuration information, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information at least includes any of the following: Meaning: global network configuration information, global topology configuration information, and global traffic configuration information; the above-mentioned main controller sends a first instruction to the above-mentioned first domain controller, and sends a second instruction to the above-mentioned second domain controller, wherein the above-mentioned first instruction is used to instruct the above-mentioned first domain controller to generate first configuration information for associating the above-mentioned first domain device with the above-mentioned second domain device, and the above-mentioned second instruction is used to instruct the above-mentioned second domain controller to generate second configuration information for associating the above-mentioned first domain device with the above-mentioned second domain device, and the above-mentioned first configuration information is used by the above-mentioned first domain controller to schedule the above-mentioned first domain device and the above-mentioned second domain device to perform the above-mentioned data transmission operation, and the above-mentioned second configuration information is used by the above-mentioned second domain controller to schedule the above-mentioned second domain device and the above-mentioned first domain device to perform the above-mentioned data transmission operation.

[0132] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0133] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0134] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0135] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory. The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0136] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0137] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0138] The above are only embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A controller system scheduling method, characterized in that: include: The main controller receives a device association request, wherein the device association request is used to request the main controller to perform a data transmission operation between a first domain device and a second domain device in a controller system, wherein the controller system at least includes the main controller and a plurality of domain controllers corresponding to the main controller; The main controller determines, in response to the device association request, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers based on global configuration information, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; The main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device, the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation, and the second configuration information is used by the second domain controller to schedule the second domain device and the first domain device to perform the data transmission operation.

2. The method according to claim 1, characterized in that In the case where the global configuration information includes: the global topology configuration information; Accordingly, the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, including: The main controller determines, based on the global topology configuration information, a first domain identifier corresponding to the first domain controller and a second domain identifier corresponding to the second domain controller; The main controller determines a first transmission channel corresponding to the first domain identifier and a second transmission channel corresponding to the second domain identifier; The main controller sends the first instruction to the first domain controller through the first transmission channel, and sends the second instruction to the second domain controller through the second transmission channel.

3. The method according to claim 1, characterized in that: Before the main controller determines, in response to the device association request, based on global configuration information, from the multiple domain controllers a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs, the further comprising: The main controller obtains preset configuration information and / or access configuration information, wherein the preset configuration information is configuration information of the controller system obtained through human-computer interaction, and the access configuration information is configuration information obtained by searching for domain devices connected to the controller system; The main controller generates the global configuration information according to the preset configuration information and / or the access configuration information.

4. The method according to claim 3, characterized in that The main controller obtains the access configuration information, including: The main controller acquires first access information, wherein the first access information is configuration information without a domain identifier obtained by searching for a domain device connected to the controller system; The main controller determines a third transmission channel corresponding to the first access information and a third domain identifier corresponding to the third transmission channel, wherein the third domain identifier is used to distinguish the multiple domain controllers, and the third transmission channel is used to transmit configuration information between the main controller and the multiple domain controllers; The main controller adds the third domain identifier to the first access information to obtain second access information, and uses the second access information as the access configuration information.

5. The method according to claim 1, characterized in that In the case where the global configuration information includes: the global topology configuration information; Accordingly, the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, including: The main controller determines whether the first domain controller and the second domain controller are the same; If the first domain controller and the second domain controller are different, the main controller obtains the first port number corresponding to the first domain device through the first domain controller and obtains the second port number corresponding to the second domain device through the second domain controller based on the global topology configuration information; The main controller establishes a mapping relationship between the first port number and the second port number; Based on the mapping relationship, the main controller sends the first instruction to the first domain controller, and sends the second instruction to the second domain controller.

6. The method according to claim 1, characterized in that In the case where the global configuration information includes: the global traffic configuration information; Accordingly, the main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, including: The main controller determines whether the first domain controller and the second domain controller are the same; If the first domain controller and the second domain controller are the same, the main controller obtains target transmission information as the first instruction based on the device association request and the global traffic configuration information, and sends the first instruction to the first domain controller, wherein the target transmission information is used to instruct the first domain controller to generate first configuration information for controlling the association between the first domain device and the second domain device.

7. The method according to claim 6, characterized in that The method further comprises: If the first domain controller and the second domain controller are different, the main controller determines the target transmission path in the target transmission information; The main controller divides the target transmission path into a first sub-path and a second sub-path according to the first domain controller and the second domain controller; The main controller determines the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the first sub-path and the second sub-path respectively; The main controller determines, based on the target transmission information, the total number of switches corresponding to the target transmission path, and the number of switches corresponding to the first sub-path and the second sub-path, respectively, first sub-transmission configuration information corresponding to the first sub-path and second sub-transmission configuration information corresponding to the second sub-path; The main controller uses the first sub-transmission configuration information as the first instruction and uses the second sub-transmission configuration information as the second instruction; The main controller sends the first instruction to the first domain controller, and sends the second instruction to the second domain controller.

8. The method according to claim 7, characterized in that The main controller determines, based on the total number of switches corresponding to the target transmission path of the target transmission information and the number of switches corresponding to the first sub-path and the second sub-path, first sub-transmission configuration information corresponding to the first sub-path and second sub-transmission configuration information corresponding to the second sub-path, including: The main controller determines, based on the total number of switches corresponding to the target transmission path of the target transmission information and the number of switches corresponding to the first sub-path and the second sub-path, first sub-transmission configuration information corresponding to the first sub-path and second sub-transmission configuration information corresponding to the second sub-path in the following manner: Q i =Q×P i / P Among them, Q i is the i-th sub-transmission configuration information corresponding to the i-th sub-path; Q is the target transmission information; P i is the number of switches corresponding to the i-th sub-path; and P is the total number of switches corresponding to the target transmission path.

9. A controller system scheduling method, characterized in that: include: The first domain controller receives a first instruction, wherein the first instruction is obtained by the main controller in response to the device association request when the main controller receives a device association request requesting the main controller to perform a data transmission operation between a first domain device and a second domain device in the controller system, based on global configuration information, and determining the first domain controller to which the first domain device belongs from multiple domain controllers, the controller system at least includes the main controller and the multiple domain controllers corresponding to the main controller, the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; Based on the first instruction, the first domain controller generates first configuration information for associating the first domain device with the second domain device, wherein the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform the data transmission operation; The second domain controller receives a second instruction, wherein the second instruction is obtained after the main controller responds to the device association request and determines the second domain controller to which the second domain device belongs from the multiple domain controllers based on the global configuration information, when the main controller receives the device association request requesting the main controller to perform the data transmission operation on the first domain device in the controller system with the second domain device; Based on the second instruction, the second domain controller generates second configuration information for associating the first domain device with the second domain device, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device.

10. A controller system scheduling method, characterized in that: include: The first domain device executes scheduling based on first configuration information to perform a data transmission operation with the second domain device, wherein the first configuration information is a first instruction obtained after the main controller receives a device association request requesting the main controller to perform the data transmission operation on the first domain device and the second domain device in the controller system, and determines the first domain controller to which the first domain device belongs from multiple domain controllers based on global configuration information in response to the device association request, and the first domain controller generates a first instruction for associating the first domain device with the second domain device based on the first instruction, the controller system at least includes the main controller and the multiple domain controllers corresponding to the main controller, the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; The second domain device executes scheduling based on second configuration information to perform the data transmission operation with the first domain device, wherein the second configuration information is a second instruction obtained after the main controller receives the device association request requesting the main controller to perform the data transmission operation between the first domain device and the second domain device in the controller system, and responds to the device association request, based on global configuration information, and determines from the multiple domain controllers the second domain controller to which the second domain device belongs, and the second domain controller generates the second instruction for associating the first domain device with the second domain device.

11. A controller system scheduling method, characterized in that: include: The main controller receives a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, wherein the controller system at least includes the main controller and a plurality of domain controllers corresponding to the main controller; The main controller determines, in response to the device association request, a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers based on global configuration information, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; The main controller sends a first instruction to the first domain controller, and sends a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device; Based on the first instruction, the first domain controller generates the first configuration information, wherein the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform a data transmission operation; Based on the second instruction, the second domain controller generates the second configuration information, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device; Based on the first configuration information and the second configuration information, the first domain controller and the second domain controller respectively schedule the first domain device and the second domain device to perform the data transmission operation; The first domain device executes scheduling based on the first configuration information to perform the data transmission operation with the second domain device; The second domain device executes scheduling based on the second configuration information, and performs the data transmission operation with the first domain device.

12. A controller system scheduling system, characterized in that: include: A main controller, configured to receive a device association request, wherein the device association request is used to request the main controller to associate a first domain device with a second domain device in a controller system, wherein the controller system includes at least the main controller and multiple domain controllers corresponding to the main controller; in response to the device association request, based on global configuration information, determining a first domain controller to which the first domain device belongs and a second domain controller to which the second domain device belongs from the multiple domain controllers, wherein the global configuration information is global configuration information of the controller system, and the global configuration information includes at least any one of the following: global network configuration information, global topology configuration information, and global traffic configuration information; sending a first instruction to the first domain controller, and sending a second instruction to the second domain controller, wherein the first instruction is used to instruct the first domain controller to generate first configuration information for associating the first domain device with the second domain device, and the second instruction is used to instruct the second domain controller to generate second configuration information for associating the first domain device with the second domain device; The first domain controller is connected to the main controller and is used to generate the first configuration information based on the first instruction, wherein the first configuration information is used by the first domain controller to schedule the first domain device and the second domain device to perform a data transmission operation; The second domain controller is connected to the main controller and is used to generate the second configuration information based on the second instruction, wherein the second configuration information is used by the second domain controller to schedule the second domain device to perform the data transmission operation with the first domain device; The first domain controller and the second domain controller are further configured to respectively schedule the first domain device and the second domain device to perform the data transmission operation based on the first configuration information and the second configuration information; The first domain device is connected to the first domain controller and is used to execute scheduling based on the first configuration information and perform the data transmission operation with the second domain device; The second domain device is connected to the second domain controller, and is used to execute scheduling based on the second configuration information to perform the data transmission operation with the first domain device.

13. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the controller system scheduling method described in any one of claims 1 to 11.

Images