LED field interconnection networking method

Abstract

The invention provides an LED field interconnection networking method, and the method comprises the steps: S1, carrying out the multi-board splicing of LED display screen CPU boards through a USB interface according to an actual application scene, and carrying out the serial connection type multi-board splicing and parallel connection type multi-board splicing; and S2, after splicing is completed, network communication of the multiple CPU boards is achieved by installing an RNDIS drive program and a BRIDGE drive program on each CPU board and configuring a brctl application, a DHCP drive program and configuring a udhcpd application and a udhcpc application. According to the method, the installation and maintenance cost caused by a large number of Ethernet wires is greatly reduced, physical connection between devices is simplified, the CPU board can be designed to be lighter and thinner due to the miniaturization characteristic of the USB interface, and the requirements of more application scenes are met.

Description

Technical Field

[0001] This invention belongs to the field of LED display interconnection and networking technology, and specifically relates to an interconnection and networking method in the LED field. Background Technology

[0002] In current technology, with the rapid development of science and technology, LED displays have been widely used in various fields such as advertising, stage performances, and information dissemination due to their superior performance. LED displays, with their high brightness, rich colors, and clear display effects, have become the preferred technology for modern visual displays. However, despite the many advantages of LED displays, traditional LED displays primarily rely on Ethernet connections for communication and synchronized playback between multiple screens. While this connection method provides relatively stable signal transmission and ensures the synchronization of video content, it also has some significant drawbacks, such as complex wiring, high cost, and bulky driving devices. Especially in applications requiring frequent adjustments to the display layout, excessive cabling not only increases equipment deployment costs but can also negatively impact the overall aesthetics and system flexibility.

[0003] In other words, the most common method for interconnecting LED display CPU boards in current networking technology is through Ethernet connection. This method relies on the standard TCP / IP protocol stack for communication between devices, offering high stability, but it also has its drawbacks.

[0004] The main drawbacks of existing technologies are:

[0005] The extensive use of RJ45 interfaces results in a thicker CPU board for driving the LED screen, affecting its aesthetics. Furthermore, the extensive use of Ethernet cables leads to high installation costs in large-scale projects.

[0006] In addition, the technical terms in this field include:

[0007] RJ45: A type of connector for information outlets (i.e., communication leads) in cabling systems. The connector consists of a plug (connector, crystal head) and a socket (module). The plug has 8 grooves and 8 contacts.

[0008] Ethernet: A computer local area network (LAN) technology. The IEEE 802.3 standard, organized by the IEEE, defines the technical standard for Ethernet, specifying the physical layer wiring, electronic signals, and media access layer protocols. Ethernet is the most widely used LAN technology, replacing other LAN technologies such as Token Ring, FDDI, and ARCNET.

[0009] TCP / IP: Transmission Control Protocol / Internet Protocol, refers to a suite of protocols that enables information transmission between multiple different networks.

[0010] RNDIS stands for Remote Network Driver Interface Specification. Implementing RNDIS over USB is essentially TCP / IP over USB, running TCP / IP on a USB device and making it appear like a network card.

[0011] BRIDGE: A network bridge, a store-and-forward device that connects two local area networks (LANs), also known as a bridge. DHCP: Dynamic Host Configuration Protocol, a network management protocol used to dynamically assign IP addresses and other network configuration parameters to devices in a network. It allows network administrators to centrally manage IP addresses and other network parameters without manually configuring each device. Summary of the Invention

[0012] To address the aforementioned issues, this application aims to resolve the problems of complex wiring, high costs, and bulky modules inherent in existing CPU board interconnection networking technologies for LED displays. By innovatively applying a USB interface to the interconnection networking between CPU boards in LED displays, a simpler and more cost-effective solution is provided.

[0013] Specifically, the present invention provides an interconnection and networking method in the field of LED, the method comprising: S1, according to the actual application scenario, performing multi-board splicing of LED display CPU boards through a USB interface, including serial multi-board splicing and parallel multi-board splicing;

[0014] The series-type multi-board splicing and parallel-type multi-board splicing can be used individually or in combination, depending on the actual application scenario, including:

[0015] When there are fewer CPU boards to drive, that is, when the driven LED screens are distributed in a strip shape, meaning that only one CPU board needs to be driven in height and no less than two CPU boards in width, the wiring will be simpler, and serial multi-board splicing technology can be used.

[0016] When there are many CPU boards that need to be driven, that is, when the driven LED screens are distributed in a divergent manner, that is, when at least five CPU boards need to be driven in height and at least five CPU boards in width, the wiring will be more complicated. Parallel multi-board splicing technology can be used.

[0017] When the number of CPU boards to be driven is moderate, that is, when the height of the LED screen to be driven requires two to four CPU boards and the width is not less than two CPU boards, the wiring will also be moderate. It is recommended to use a multi-board splicing technology that combines the two.

[0018] S2. After completing the above splicing, network communication between multiple CPU boards is achieved by installing the RNDIS driver and BRIDGE driver on each CPU board and configuring the brctl application, and configuring the DHCP driver and udhcpd and udhcpc applications.

[0019] In the described serial multi-board splicing scheme, assuming the data transmission direction is from left to right, the left USB interface of each CPU board is the data input interface, and the right USB interface is the data output interface. Data from the first CPU board is transmitted to the second CPU board through the USB output interface and USB cable. At this time, the USB input interface of the second CPU board receives the data. Similarly, the third CPU board can also receive data from the second CPU board. And so on, with an unlimited number of CPU boards that can be added at both ends.

[0020] The serial multi-board splicing method, assuming the first CPU board is A, the second CPU board is B, the third CPU board is C, and so on, specifically operates as follows: CPU board A transmits data to the USB input interface of CPU board B through its USB output interface; after receiving the data, CPU board B processes the data through software and transmits the data to the USB input interface of CPU board C through its USB output interface. This serial method allows multiple CPU boards to be spliced ​​at both ends to achieve the multi-board splicing function.

[0021] In the parallel multi-board splicing scheme, it is assumed that the left USB interface of the CPU board is the data input interface, and its upper, lower and right USB interfaces are the data output interfaces.

[0022] The first CPU board transmits data to the third CPU board via the right USB output interface and a USB cable. At this time, the USB input interface of the third CPU board receives the data and transmits it to the top, bottom, and right output interfaces of the third CPU board. The top output interface of the third CPU board transmits the data to the input interface of the second CPU board via the USB cable, the bottom output interface of the third CPU board transmits the data to the input interface of the fourth CPU board via the USB cable, and the right output interface of the third CPU board transmits the data to the input interface of the fifth CPU board via the USB cable. And so on, this method can be used to connect multiple CPU boards in an unlimited number of directions.

[0023] The parallel multi-board splicing method, assuming the first CPU board is designated as A, the second CPU board as B, the third CPU board as C, and so on, operates as follows: CPU board A transmits data to the USB input interface of CPU board C via its right-side USB output interface; after receiving the data, CPU board C processes the data through software and transmits it to the input interfaces of CPU board B, CPU board D, and CPU board E respectively via its upper and lower right-side USB output interfaces; this parallel method allows multiple CPU boards to be spliced ​​in multiple directions to achieve a more flexible multi-board splicing function.

[0024] In the scheme combining the serial multi-board splicing and the parallel multi-board splicing, the combined use includes: assuming CPU board A, CPU board B, CPU board C, and CPU board D form a parallel multi-board splicing; CPU board C, CPU board F, and CPU board I form a serial multi-board splicing; CPU board B, CPU board E, and CPU board H form a serial multi-board splicing; and CPU board D, CPU board G, and CPU board J form a serial multi-board splicing. Regarding data transmission, CPU board A transmits data to CPU board B via the right USB output interface and a USB cable. At this time, CPU board B's USB input interface receives the data, processes it through software, and transmits it to the top, bottom, and right output interfaces of CPU board B; wherein the top output... The interface transmits data via USB cable to the input interface of CPU board C. After software processing, the data is then transmitted to CPU board F via the right output structure of CPU board C. After further software processing, the data is then transmitted to CPU board I via the right output structure of CPU board F. Similarly, data from CPU board A is transmitted via USB cable to the input interface of CPU board B via the right output interface of USB. After software processing, the data is then transmitted to CPU board E via the right output structure of CPU board B. After further software processing, the data is then transmitted to CPU board H via the right output structure of CPU board E. Likewise, CPU boards D, G, and J also receive data from the CPU boards. This process continues, creating multiple serial data transmission paths. These paths can be combined with parallel multi-board splicing to form a multi-board splicing technology that combines parallel and serial connections.

[0025] The software processing described is virtual networking technology. This technology can make IP addresses from different network segments appear to be on the same network segment by configuring a virtual environment. This includes building a bridge to create a virtual network within the same network segment. Assuming four virtual devices, the bridging command is as follows: `brctl addbr br0`

[0026] brctl stp br0 1

[0027] brctl addif br0 usb0

[0028] brctl addif br0 usb1

[0029] brctl addif br0 usb2

[0030] brctl addif br0 usb3;

[0031] The four virtual network devices here, namely usb0, usb1, usb2, and usb3, are closer to the application scenario of parallel multi-board splicing.

[0032] Step S2 further includes:

[0033] S2.1. Install the RNDIS driver on each CPU board. This driver is responsible for recognizing the USB connection and emulating it as a network interface.

[0034] Among the CPU's peripheral modules is a USB 2.0 module. The RNDIS driver, located in the kernel space, is responsible for communicating directly with the CPU's USB 2.0 module.

[0035] The RNDIS driver can interact with the CPU processor. The CPU executes code in the kernel space, including the RNDIS driver code. When data needs to be sent or received, the CPU executes relevant instructions to handle these tasks. These instructions include data transfer instructions (Load / Store), arithmetic logic instructions (Add / Subtract / Multiply / Divide / Bitwise operations), control flow instructions (Jump / Branch / Call / Return), interrupt handling instructions, and memory management instructions.

[0036] When an RNDIS-enabled CPU board (slave device) is connected to another RNDIS-enabled CPU board (master device) via USB, the USB subsystem detects the slave device and attempts to identify its type. If both CPU boards support RNDIS, the USB subsystem loads the corresponding kernel module, such as rndis_host. After loading the driver, the master CPU board performs a series of handshake operations with the slave CPU board to determine whether the device truly supports RNDIS. This includes setting up control pipes and other necessary configuration information. Once the device is successfully initialized, the RNDIS driver creates a virtual network interface that can be recognized in the network protocol stack. Any data sent to this interface will be captured by the RNDIS driver and sent to the device via USB. Data packets received by the slave device are also passed to the RNDIS driver via USB, and then handed over to the network protocol stack in the kernel for processing. The network protocol stack parses the data packets and passes them to the corresponding application based on the destination process.

[0037] S2.2. Install the BRIDGE driver on each CPU board and configure the brctl application in the file system. This driver and application are responsible for integrating multiple network interfaces into one network interface. The BRIDGE driver is located in the kernel space and is responsible for communicating directly with the CPU's USB 2.0 module.

[0038] The BRIDGE driver can interact with the CPU processor. The BRIDGE driver sets up memory-mapped I / O, which is a method that allows the CPU to directly access device registers. By mapping device registers to memory address space, the CPU can access these registers through ordinary read and write instructions and handle access requests from the CPU. These access requests include read and write requests, configuration requests, interrupt service requests (ISR), status query requests, and reset requests.

[0039] In the file system, the brctl application can be compiled by enabling the CONFIG_BRCTL configuration in buildroot's busybox;

[0040] The following command can be used to combine multiple networks on the same network segment into one network;

[0041] S2.3. Install the DHCP driver on each CPU board and configure the udhcpd and udhcpc applications in the file system. These drivers and applications are responsible for automatically obtaining IP addresses.

[0042] DHCP is a network protocol used to automatically assign IP addresses to devices on a network. DHCP functionality requires operating system support, and the operating system can interact with the CPU to execute DHCP tasks, including instruction execution, memory management, and interrupt handling.

[0043] In the file system, the udhcpd and udhcpc applications can be compiled by opening the CONFIG_UDHCPD and CONFIG_UDHCPC configurations through buildroot’s busybox;

[0044] Execute the udhcpd command on the master device. This command will read the udpchd.conf file. The contents of udpchd.conf include the range of IP addresses assigned to slave devices, the domain names provided to slave devices, and routing address information. Execute udhcpc -i br0 on the slave device to automatically assign an IP address to the bridged virtual network device br0. The range of IP addresses is provided by the aforementioned udpchd.conf file.

[0045] In step S2.2, the process of integrating multiple networks on the same network segment into one network using the following command includes: Assuming two virtual network devices, usb0 and usb1, the command would be: brctl addbr br0

[0046] brctl stp br0 1

[0047] brctl addif br0 usb0

[0048] brctl addif br0 usb1;

[0049] The two virtual network devices formed by usb0 and usb1 here are closer to the application scenario of serial multi-board splicing.

[0050] The USB interface is either a USB Type-A or a USB Type-C interface.

[0051] Therefore, the advantage of this application is:

[0052] Using USB interconnects to form a local area network (LAN) replaces the traditional bulky Ethernet cables, allowing CPU boards to be made very thin and light, and reducing cable costs. This method significantly reduces installation and maintenance costs associated with numerous Ethernet cables, simplifies physical connections between devices, and the miniaturization of the USB interface also enables the CPU board to be designed to be thinner and lighter, adapting to the needs of more application scenarios. Attached Figure Description

[0053] The accompanying drawings, which are provided to further illustrate the invention and form part of this application, are not intended to limit the scope of the invention.

[0054] Figure 1 This is a flowchart illustrating the method described in this application.

[0055] Figure 2 This is a schematic diagram of a series-connected multi-plate splicing method.

[0056] Figure 3 This is a schematic diagram of a parallel multi-plate splicing method.

[0057] Figure 4 This is a schematic diagram of a method for splicing multiple boards in series and parallel. Detailed Implementation

[0058] To better understand the technical content and advantages of the present invention, the present invention will now be described in further detail with reference to the accompanying drawings.

[0059] This invention enables the splicing and interconnection of multiple LED CPU boards via USB, such as... Figure 1 As shown, the method includes:

[0060] S1, depending on the actual application scenario, uses the USB interface to splice multiple boards of the LED display CPU board, including serial multi-board splicing and parallel multi-board splicing;

[0061] S2. After completing the above splicing, network communication between multiple CPU boards is achieved by installing the RNDIS driver and BRIDGE driver on each CPU board and configuring the brctl application, and configuring the DHCP driver and udhcpd and udhcpc applications.

[0062] Specifically, step S1 of this method provides two approaches: series-connected multi-board splicing and parallel-connected multi-board splicing. Depending on the actual application scenario, one approach or a combination of the two can be selected.

[0063] Figure 2 In the schematic diagram of the serial multi-board splicing scheme, the USB interface can be either USB Type-A or USB Type-C.

[0064] In this scheme, assuming data transmission direction is from left to right, the left-side USB port of each CPU board is the data input interface, and the right-side USB port is the data output interface. Data from the first CPU board is transmitted to the second CPU board via the USB output interface and USB cable. At this time, the USB input interface of the second CPU board receives the data. Similarly, the third CPU board can also receive data from the second CPU board. And so on, with an unlimited number of CPU boards that can be added at both ends.

[0065] like Figure 2 As shown, the specific operation is as follows: CPU board A transmits data to the USB input interface of CPU board B via its USB output interface; after receiving the data, CPU board B processes the data through software and then transmits the data to the USB input interface of CPU board C via its USB output interface. This serial connection method allows multiple CPU boards to be spliced ​​at both ends to achieve multi-board splicing functionality.

[0066] Figure 3 In the schematic diagram of the parallel multi-board splicing scheme, the USB interface can also be either a USB Type-A or USB Type-C interface. In this scheme, the USB interface on the left is the data input interface, and the USB interfaces on the top, bottom, and right are the data output interfaces.

[0067] The first CPU board transmits data to the third CPU board via its right USB output port and a USB cable. The third CPU board's USB input port receives the data and transmits it to its top, bottom, and right output ports. The top output port transmits data to the second CPU board's input port via USB, the bottom output port transmits data to the fourth CPU board's input port via USB, and the right output port transmits data to the fifth CPU board's input port via USB. This method allows for the unlimited number of CPU boards to be connected in multiple directions.

[0068] like Figure 3 As shown, the specific operation is as follows: CPU board A transmits data to the USB input interface of CPU board C via its right-side USB output interface; after receiving the data, CPU board C processes the data through software and then transmits the data to the input interfaces of CPU board B, CPU board D, and CPU board E respectively via its upper and lower right-side USB output interfaces. This parallel connection method allows multiple CPU boards to be spliced ​​in multiple directions to achieve a more flexible multi-board splicing function.

[0069] like Figure 4 As shown, in the combination of the series-connected multi-panel splicing and the parallel-connected multi-panel splicing schemes, it is worth noting that... Figure 4 This connection method is not unique; it is just one example. CPU boards A, B, C, and D form a parallel multi-board configuration; CPU boards C, F, and I form a series multi-board configuration; CPU boards B, E, and H form a series multi-board configuration; and CPU boards D, G, and J form a series multi-board configuration. For data transmission, CPU board A transmits data to CPU board B via the right USB output interface and a USB cable. CPU board B's USB input interface receives the data, processes it through software, and then transmits it to the top, bottom, and right output interfaces of CPU board B. The upper output interface transmits data via USB to the input interface of CPU board C. After software processing, the data is then transmitted to CPU board F via the right output structure of CPU board C, and after further software processing, it is transmitted to CPU board I via the right output structure of CPU board F. Similarly, data from CPU board A is transmitted via USB to the input interface of CPU board B via the right output interface. After software processing, the data is transmitted to CPU board E via the right output structure of CPU board B, and after further software processing, it is transmitted to CPU board H via the right output structure of CPU board E. Likewise, CPU boards D, G, and J also receive data from the CPU boards. This process continues, creating multiple serial data transmission paths. Combining these with parallel multi-board splicing techniques creates a multi-board splicing technology that combines parallel and serial connections.

[0070] After completing the above assembly, the next step S2 is to implement network communication across the multi-CPU boards. The specific steps are as follows:

[0071] S2.1. Install the RNDIS driver on each CPU board. This driver is responsible for recognizing the USB connection and emulating it as a network interface.

[0072] S2.2. Install the BRIDGE driver on each CPU board and configure the brctl application in the file system. This driver and application are responsible for integrating multiple network interfaces into one network interface.

[0073] S2.3. Install the DHCP driver on each CPU board and configure the udhcpd and udhcpc applications in the file system. These drivers and applications are responsible for automatically obtaining IP addresses.

[0074] Through the above steps, multiple CPU boards were spliced ​​and interconnected, and networking functionality was achieved.

[0075] Furthermore, including:

[0076] S2.1. Install the RNDIS driver on each CPU board. This driver is responsible for recognizing the USB connection and emulating it as a network interface.

[0077] Among the CPU's peripheral modules is a USB 2.0 module. The RNDIS driver, located in the kernel space, is responsible for communicating directly with the CPU's USB 2.0 module.

[0078] The RNDIS driver can interact with the CPU processor. The CPU executes code in the kernel space, including the RNDIS driver code. When data needs to be sent or received, the CPU executes relevant instructions to handle these tasks. These instructions include data transfer instructions (Load / Store), arithmetic logic instructions (Add / Subtract / Multiply / Divide / Bitwise operations), control flow instructions (Jump / Branch / Call / Return), interrupt handling instructions, memory management instructions, and so on.

[0079] When an RNDIS-enabled CPU board (slave device) is connected to another RNDIS-enabled CPU board (master device) via USB, the USB subsystem detects the slave device and attempts to identify its type. If both CPU boards support RNDIS, the USB subsystem loads the corresponding kernel module, such as rndis_host. After loading the driver, the master CPU board performs a series of handshake operations with the slave CPU board to determine whether the device truly supports RNDIS. This includes setting up control pipes and other necessary configuration information. Once the device is successfully initialized, the RNDIS driver creates a virtual network interface that can be recognized in the network protocol stack. Any data sent to this interface will be captured by the RNDIS driver and sent to the device via USB. Data packets received by the slave device are also passed to the RNDIS driver via USB, and then handed over to the network protocol stack in the kernel for processing. The network protocol stack parses the data packets and passes them to the corresponding application based on the destination process.

[0080] S2.2. Install the BRIDGE driver on each CPU board and configure the brctl application in the file system. This driver and application are responsible for integrating multiple network interfaces into one network interface. The BRIDGE driver is located in the kernel space and is responsible for communicating directly with the CPU's USB 2.0 module.

[0081] The BRIDGE driver can interact with the CPU processor. The BRIDGE driver sets up memory-mapped I / O (MMIO), which is a method that allows the CPU to directly access device registers. By mapping device registers to memory address space, the CPU can access these registers through ordinary read and write instructions and handle access requests from the CPU. These access requests include read / write requests, configuration requests, interrupt service requests (ISR), status query requests, reset requests, etc.

[0082] In the file system, the brctl application can be compiled by enabling the CONFIG_BRCTL configuration in buildroot's busybox;

[0083] The following command can be used to combine multiple networks on the same network segment into one network; here, we take two virtual network devices, usb0 and usb1, as an example:

[0084] brctl addbr br0

[0085] brctl stp br0 1

[0086] brctl addif br0 usb0

[0087] brctl addif br0 usb1.

[0088] S2.3. Install the DHCP driver on each CPU board and configure the udhcpd and udhcpc applications in the file system. These drivers and applications are responsible for automatically obtaining IP addresses.

[0089] DHCP is a network protocol used to automatically assign IP addresses to devices on a network. It is not a hardware driver, nor is it software that directly interacts with the CPU. DHCP functionality requires operating system support, and the operating system can interact with the CPU to execute DHCP tasks, including instruction execution, memory management, and interrupt handling.

[0090] In the file system, the udhcpd and udhcpc applications can be compiled by opening the CONFIG_UDHCPD and CONFIG_UDHCPC configurations through buildroot’s busybox;

[0091] Execute the udhcpd command on the master device. This command will read the udpchd.conf file. The contents of udpchd.conf include information such as the range of IP addresses assigned to slave devices, the domain names provided to slave devices, and routing addresses. Execute udhcpc -i br0 on the slave device to automatically assign an IP address to the bridged virtual network device br0. The range of IP addresses is provided by the aforementioned udpchd.conf file.

[0092] The following example uses the Beijing Junzheng Halley7 development board as an illustration: The Halley7 development board has two USB Type-C ports and does not use RJ45 network ports, which allows for the construction of a series-connected multi-CPU board. Assuming the upper USB Type-C port is for data input and the lower USB Type-C port is for data output, this method is also used in the actual construction process. Eighteen development boards are connected together via USB cables using series-connection technology. The hardware construction is complete. Now, we will build the software. Enable the RNDIS driver, BRIDGE driver, and DHCP driver. Compile the brctl, udhcpd, and udhcpc applications into the file system. Add the following command to the startup script to build the bridge and automatically obtain an IP address: `brctl addbr br0`

[0093] brctl stp br0 1

[0094] brctl addif br0 usb0

[0095] brctl addif br0 usb1

[0096] brctl addif br0 usb2

[0097] brctl addif br0 usb3

[0098] udhcpc-i br0

[0099] The firmware was burned onto the 18 development boards, and the boards were then powered on. A ping command was successfully used to ping any two development boards, indicating that the software setup was complete. This proves that this approach is feasible.

[0100] This solution connects multiple development boards via USB cables instead of Ethernet cables, as Ethernet cables are more expensive. This cost-saving approach is particularly noticeable in large projects. Using USB Type-C connections instead of RJ45 Ethernet ports, with USB Type-C ports being only 2.5mm thick and RJ45 ports only 13.2mm thick, reduces the thickness of the CPU board, allowing for a thinner and lighter design.

[0101] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, various modifications and variations can be made to the embodiments of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for interconnecting and networking LED systems, characterized in that: The method includes: S1, depending on the actual application scenario, uses the USB interface to splice multiple boards of the LED display CPU board, including serial multi-board splicing and parallel multi-board splicing; The series-type multi-board splicing and parallel-type multi-board splicing can be used individually or in combination, depending on the actual application scenario, including: When there are fewer CPU boards to drive, that is, when the driven LED screens are distributed in a strip shape, meaning that only one CPU board needs to be driven in height and no less than two CPU boards in width, the wiring will be simpler, and serial multi-board splicing technology can be used. When there are many CPU boards that need to be driven, that is, when the driven LED screens are distributed in a divergent manner, that is, when at least five CPU boards need to be driven in height and at least five CPU boards in width, the wiring will be more complicated. Parallel multi-board splicing technology can be used. When the number of CPU boards to be driven is moderate, that is, when the height of the LED screen to be driven requires two to four CPU boards and the width is not less than two CPU boards, the wiring will also be moderate. It is recommended to use a multi-board splicing technology that combines the two. S2. After completing the above splicing, network communication between multiple CPU boards is achieved by installing the RNDIS driver and BRIDGE driver on each CPU board and configuring the brctl application, and configuring the DHCP driver and udhcpd and udhcpc applications.

2. The LED interconnection and networking method according to claim 1, characterized in that, In the aforementioned serial multi-board splicing scheme, assuming the data transmission direction is from left to right, the left USB interface of each CPU board is the data input interface, and the right USB interface is the data output interface; the data of the first CPU board is transmitted to the second CPU board through the USB output interface and USB cable. At this time, the USB input interface of the second CPU board receives the data. Similarly, the third CPU board can also receive the data from the second CPU board; and so on, multiple CPU boards can be infinitely expanded at both ends.

3. The LED interconnection and networking method according to claim 2, characterized in that, The serial multi-board splicing method, assuming the first CPU board is A, the second CPU board is B, the third CPU board is C, and so on, specifically operates as follows: CPU board A transmits data to the USB input interface of CPU board B through its USB output interface; after receiving the data, CPU board B processes the data through software and transmits the data to the USB input interface of CPU board C through its USB output interface. This serial method allows multiple CPU boards to be spliced ​​at both ends to achieve multi-board splicing functionality.

4. The LED interconnection and networking method according to claim 2, characterized in that, In the parallel multi-board splicing scheme, it is assumed that the left USB interface of the CPU board is the data input interface, and its upper, lower and right USB interfaces are the data output interfaces. The first CPU board transmits data to the third CPU board via the right USB output interface and a USB cable. At this time, the USB input interface of the third CPU board receives the data and transmits it to the top, bottom, and right output interfaces of the third CPU board. The top output interface of the third CPU board transmits the data to the input interface of the second CPU board via the USB cable, the bottom output interface of the third CPU board transmits the data to the input interface of the fourth CPU board via the USB cable, and the right output interface of the third CPU board transmits the data to the input interface of the fifth CPU board via the USB cable. And so on, this method can be used to connect multiple CPU boards in an unlimited number of directions.

5. The LED interconnection and networking method according to claim 4, characterized in that, The parallel multi-board splicing method, assuming the first CPU board is designated as A, the second CPU board as B, the third CPU board as C, and so on, operates as follows: CPU board A transmits data to the USB input interface of CPU board C via its right-side USB output interface; after receiving the data, CPU board C processes the data through software and transmits it to the input interfaces of CPU board B, CPU board D, and CPU board E respectively via its upper and lower right-side USB output interfaces; this parallel method allows multiple CPU boards to be spliced ​​in multiple directions to achieve a more flexible multi-board splicing function.

6. The LED interconnection and networking method according to claim 2, characterized in that, In the scheme combining the serial multi-board splicing and the parallel multi-board splicing, the combined use includes: assuming CPU board A, CPU board B, CPU board C, and CPU board D form a parallel multi-board splicing; CPU board C, CPU board F, and CPU board I form a serial multi-board splicing; CPU board B, CPU board E, and CPU board H form a serial multi-board splicing; and CPU board D, CPU board G, and CPU board J form a serial multi-board splicing. Regarding data transmission, CPU board A transmits data to CPU board B via the right USB output interface and a USB cable. At this time, CPU board B's USB input interface receives the data, processes it through software, and transmits it to the top, bottom, and right output interfaces of CPU board B. The top output interface transmits data to the CPU board via the USB cable. The input interface of CPU board C, after software processing, transmits data to CPU board F via the right output structure of CPU board C. After further software processing, the data is then transmitted to CPU board I via the right output structure of CPU board F. Data from CPU board A is transmitted via USB cable to the input interface of CPU board B through the right output interface of USB. After software processing, the data is transmitted to CPU board E via the right output structure of CPU board B. After further software processing, the data is then transmitted to CPU board H via the right output structure of CPU board E. Similarly, CPU boards D, G, and J also receive data from the CPU board. This process can be repeated to form multiple serial data transmission paths. When combined with parallel multi-board splicing, a multi-board splicing technology that combines parallel and serial connections can be formed.

7. A method for interconnecting and networking LED systems according to claim 3, 5, or 6, characterized in that, The software processing described is virtual network technology. This technology can make IP addresses from different network segments appear to be on the same network segment by configuring a virtual environment. This includes setting up a bridge to create a virtual network on the same network segment. Assuming four virtual devices, the bridging command is as follows: brctl addbr br0 brctl stp br0 1 brctl addif br0 usb0 brctl addif br0 usb1 brctl addif br0 usb2 brctl addif br0 usb3; The four virtual network devices here, namely usb0, usb1, usb2, and usb3, are closer to the application scenario of parallel multi-board splicing.

8. The LED interconnection and networking method according to claim 1, characterized in that, Step S2 further includes: S2.

1. Install the RNDIS driver on each CPU board. This driver is responsible for recognizing the USB connection and emulating it as a network interface. Among the CPU's peripheral modules is a USB 2.0 module. The RNDIS driver, located in the kernel space, is responsible for communicating directly with the CPU's USB 2.0 module. The RNDIS driver can interact with the CPU processor. The CPU executes code in the kernel space, including the RNDIS driver code. When data needs to be sent or received, the CPU executes relevant instructions to handle these tasks. These instructions include data transfer instructions (Load / Store), arithmetic logic instructions (Add / Subtract / Multiply / Divide / Bitwise operations), control flow instructions (Jump / Branch / Call / Return), interrupt handling instructions, and memory management instructions. When an RNDIS-enabled CPU board (slave device) is connected to another RNDIS-enabled CPU board (master device) via USB, the USB subsystem detects the slave device and attempts to identify its type. If both CPU boards support RNDIS, the USB subsystem loads the corresponding kernel module, such as rndis_host. After loading the driver, the master CPU board performs a series of handshake operations with the slave CPU board to determine whether the device truly supports RNDIS. This includes setting up control pipes and other necessary configuration information. Once the device is successfully initialized, the RNDIS driver creates a virtual network interface that can be recognized in the network protocol stack. Any data sent to this interface will be captured by the RNDIS driver and sent to the device via USB. Data packets received by the slave device are also passed to the RNDIS driver via USB, and then handed over to the network protocol stack in the kernel for processing. The network protocol stack parses the data packets and passes them to the corresponding application based on the destination process. S2.

2. Install the BRIDGE driver on each CPU board and configure the brctl application in the file system. This driver and application are responsible for integrating multiple network interfaces into one network interface. The BRIDGE driver resides in kernel space and is responsible for communicating directly with the CPU's USB 2.0 module; The BRIDGE driver can interact with the CPU processor. The BRIDGE driver sets up memory-mapped I / O, which is a method that allows the CPU to directly access device registers. By mapping device registers to memory address space, the CPU can access these registers through ordinary read and write instructions and handle access requests from the CPU. These access requests include read and write requests, configuration requests, interrupt service requests (ISR), status query requests, and reset requests. In the file system, the brctl application can be compiled by enabling the CONFIG_BRCTL configuration in buildroot's busybox; The following command can be used to combine multiple networks on the same network segment into one network; S2.

3. Install the DHCP driver on each CPU board and configure the udhcpd and udhcpc applications in the file system. These drivers and applications are responsible for automatically obtaining IP addresses. DHCP is a network protocol used to automatically assign IP addresses to devices on a network. DHCP functionality requires operating system support, and the operating system can interact with the CPU to execute DHCP tasks, including instruction execution, memory management, and interrupt handling. In the file system, the udhcpd and udhcpc applications can be compiled by opening the CONFIG_UDHCPD and CONFIG_UDHCPC configurations through buildroot’s busybox; Execute the udhcpd command on the master device. This command will read the udpchd.conf file. The contents of udpchd.conf include the range of IP addresses assigned to slave devices, the domain names provided to slave devices, and routing address information. Execute udhcpc -i br0 on the slave device to automatically assign an IP address to the bridged virtual network device br0. The range of IP addresses is provided by the aforementioned udpchd.conf file.

9. A method for interconnecting and networking LED systems according to claim 8, characterized in that, In step S2.2, the integration of multiple networks in the same network segment into one network can be achieved through the following command: Assuming two virtual network devices, usb0 and usb1, then: brctl addbr br0 brctl stp br0 1 brctl addif br0 usb0 brctl addif br0 usb1; The two virtual network devices formed by usb0 and usb1 here are closer to the application scenario of serial multi-board splicing.

10. The LED interconnection and networking method according to claim 1, characterized in that, The USB interface is either a USB Type-A or a USB Type-C interface.

Images