LED display system equipment topology editing method, device and electronic equipment

Abstract

The present application is applicable to the technical field of topology editing of LED display system equipment, and provides a method, device and electronic device for topology editing of LED display system equipment, wherein the above method includes: loading preset configuration rules, wherein the preset configuration rules are used to characterize the topology configuration between virtual devices corresponding to physical devices in the LED display system; obtaining the device type and device quantity of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices; according to the device type and device quantity of several target physical devices, adding several target virtual devices corresponding to the target physical devices to the configuration interface; performing automatic topology operations on the target virtual devices according to the preset configuration rules to obtain an initial device topology map; and generating a target device topology map in response to an editing operation instruction performed on the initial device topology map.

Description

Technical Field

[0001] The present application relates to the technical field of topology editing of LED display system equipment, and in particular to a method, device and electronic equipment for topology editing of LED display system equipment. Background Art

[0002] At present, in the field of LED display, it is rather cumbersome to generate a device topology map, and configuration personnel are required to manually generate the device topology map. After the device topology map is generated, the generated device topology map cannot be edited and modified, which may lead to errors in the generated device topology map, and then topology errors may occur in the process of device topology of the physical device.

[0003] It can be seen that the LED display system device topology editing method in the related art has the problem of physical device topology errors caused by errors in the generated device topology map. Summary of the invention

[0004] In view of this, an embodiment of the present application provides a method, device and electronic device for editing the topology of an LED display system device, which solves the problem of an error in the physical device topology caused by an error in the generated device topology diagram in the LED display system device topology editing method in the related art.

[0005] The first aspect of an embodiment of the present application provides a method, comprising: loading preset configuration rules, wherein the preset configuration rules are used to characterize the topological configuration between virtual devices corresponding to physical devices in the LED display system; obtaining the device type and device quantity of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices; adding several target virtual devices corresponding to the target physical devices to a configuration interface according to the device type and device quantity of the several target physical devices; performing automatic topological operations on the target virtual devices according to the preset configuration rules to obtain an initial device topology map; and generating a target device topology map in response to an editing operation instruction performed on the initial device topology map.

[0006] The second aspect of an embodiment of the present application provides a device, including: a loading unit, used to load preset configuration rules, wherein the preset configuration rules are used to characterize the topological configuration between virtual devices corresponding to the physical devices in the LED display system; an acquisition unit, used to acquire the device type and device quantity of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices; an adding unit, used to add several target virtual devices corresponding to the target physical devices to the configuration interface according to the device type and device quantity of the several target physical devices; a topology unit, used to perform automatic topological operations on the target virtual devices according to the preset configuration rules to obtain an initial device topology map; and a generation unit, used to generate a target device topology map in response to an editing operation instruction performed on the initial device topology map.

[0007] A third aspect of an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in the first aspect when executing the computer program.

[0008] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in the first aspect above is implemented.

[0009] A fifth aspect of the embodiments of the present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes any one of the methods described in the first aspect.

[0010] Compared with the prior art, the embodiments of the present application have the following beneficial effects: first, according to the loaded preset configuration rules, an automatic topology operation is performed on the target virtual device to obtain an initial device topology map, and then an editing operation is performed on the initial device topology map to generate a target device topology map, by loading the preset configuration rules, wherein the preset configuration rules are used to characterize the topology configuration between the virtual devices corresponding to the physical devices in the LED display system; the device type and the number of devices of several target physical devices to be configured are obtained, wherein the target physical device is all or part of the preset physical devices; according to the device type and the number of devices of the several target physical devices, several target virtual devices corresponding to the target physical devices are added to the configuration interface; according to the preset configuration rules, an automatic topology operation is performed on the target virtual device to obtain an initial device topology map; in response to the editing operation instruction performed on the initial device topology map, a target device topology map is generated, because after the initial device topology map is automatically generated, the initial device topology map can be edited, thereby reducing the probability of errors in the generated target device topology map, thereby reducing the occurrence of physical device topology errors, thereby solving the problem of physical device topology errors caused by errors in the generated device topology map in the LED display system device topology editing method in the related art. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.

[0012] Figure 1 It is a schematic diagram of a hardware environment of an optional LED display system device topology editing method according to an embodiment of the present application;

[0013] Figure 2 It is a flowchart of an optional LED display system device topology editing method according to an embodiment of the present application;

[0014] Figure 3 is a schematic diagram of an optional device automatic topology process according to an embodiment of the present application;

[0015] Figure 4 is a schematic diagram of an optional adaptive canvas display according to an embodiment of the present application;

[0016] Figure 5 is a schematic diagram of an optional topology structure displayed through an eagle view according to an embodiment of the present application;

[0017] Figure 6 is a schematic diagram of an optional device topology editor interface according to an embodiment of the present application;

[0018] Figure 7It is a structural block diagram of an optional LED display system equipment topology editing device according to an embodiment of the present application;

[0019] Figure 8 It is a schematic diagram of the structure of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0021] In order to illustrate the technical solution described in this application, a specific embodiment is provided below for illustration.

[0022] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0023] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0024] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0025] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0026] In addition, in the description of the present application, the terms "first", "second", "third", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0027] According to one aspect of an embodiment of the present application, a method for editing a topology of an LED display system device is provided. Optionally, in this embodiment, the method for editing a topology of an LED display system device can be applied to Figure 1 In the hardware environment shown, which is composed of a host computer, a video processing device, a sending device, a receiving device and an LED screen, the above-mentioned host computer, video processing device, sending device, receiving device and LED screen can all be connected to the server through a network, and the server can be used to provide services (such as application services, etc.) for the clients installed on these devices.

[0028] The above network may include but is not limited to at least one of the following: wired network, wireless network. The above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth.

[0029] Figure 2 is a flow chart of an optional method for editing the topology of a device in an LED display system according to an embodiment of the present application, such as Figure 2 As shown, the process of the method may include the following steps:

[0030] Step S202 , loading a preset configuration rule, wherein the preset configuration rule is used to characterize a topological configuration between virtual devices corresponding to physical devices in the LED display system.

[0031] The LED display system device topology editing method in this embodiment can be applied to the scenario of generating a device topology diagram. The above-mentioned preset configuration rules can be configuration rules between physical devices in the LED display system, or they can be configuration rules between virtual devices corresponding to the above-mentioned physical devices. This is not limited in this embodiment.

[0032] Optionally, the process of loading the preset configuration rules may be: first generate configuration parameters according to the preset configuration rules, and then send the configuration parameters to the configuration software on the terminal device, so that the configuration software can reload and store the preset configuration rules in the software according to the configuration parameters.

[0033] Optionally, the above preset configuration rules can also be used as a reference for on-site personnel to perform topology editing on-site LED display devices. For example, on-site personnel can perform topology configuration on-site LED display devices according to the preset configuration rules (i.e., connect the interfaces of specified types of devices).

[0034] Optionally, the above-mentioned preset configuration rules may include preset entity device types, and may also include configuration relationships between preset entity device types, which is not limited in this embodiment.

[0035] Step S204, obtaining device types and device quantities of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices.

[0036] Optionally, after loading the preset configuration rules, the device type and device quantity of several target entity devices to be configured can be obtained, the above-mentioned target entity devices are all or part of the preset entity devices, and the above-mentioned preset entity devices can be entity devices included in the preset configuration rules, that is, the above-mentioned preset configuration rules are composed of preset entity devices and configuration relationships between preset entity devices.

[0037] Optionally, the process of obtaining the device type and device quantity of several target entity devices to be configured may be: first, performing image acquisition on the several target entity devices through an image acquisition device to obtain device topology images corresponding to the several target entity devices, and then performing image recognition on the device topology images to determine the device type and device quantity of the target entity devices. The above-mentioned image acquisition device may be a camera or a camera. In this embodiment, there is no limitation on the device type of the image acquisition device.

[0038] Step S206: adding a plurality of target virtual devices corresponding to the target physical devices to the configuration interface according to the device types and device quantities of the plurality of target physical devices.

[0039] In this embodiment, after obtaining the device types and device quantities of several target physical devices to be configured, several target virtual devices corresponding to the target physical devices may be added to the configuration interface according to the device types and device quantities of the several target physical devices.

[0040] Optionally, the process of adding several target virtual devices corresponding to the target physical devices to the configuration interface according to the device types and device quantities of the target physical devices may be: firstly determining the target virtual device from multiple preset virtual devices according to the device identification of the target physical device, and then adding the determined target virtual device to the configuration interface, wherein the target virtual device has the same device identification as the target physical device. For example, when the target physical device is an LED display control device, the virtual device corresponding to the LED display control device may be added to the configuration interface.

[0041] Optionally, data can be exchanged between the target virtual device and the target physical device. For example, when some parameters of the target physical device are changed, the target virtual device will also modify the above parameters accordingly, so that the target virtual device can reflect the status of the target physical device in real time.

[0042] Step S208: performing automatic topology operations on the target virtual device according to preset configuration rules to obtain an initial device topology map.

[0043] In various scenarios in the LED (Light Emitting Diode) industry, related technologies require on-site machines to view the real-time operating status of the equipment, and each time on-site support is required to view the real-time operating status of the equipment and the connection relationship between various on-site devices before the device topology structure can be generated. As a result, the steps for generating the device topology structure are cumbersome, which in turn leads to a long time spent on generating the device topology structure.

[0044] Optionally, in this embodiment, after adding several target virtual devices corresponding to the target physical device to the configuration interface, topological operations are automatically performed on the several target virtual devices according to the preset configuration rules to obtain the initial device topology structure, thereby simplifying the steps of generating the device topology structure and achieving the technical effect of reducing the time consumption of generating the device topology structure. Figure 3 As shown, after device A, device B, and device C are added to the canvas, device topology operations can be automatically performed on device A, device B, and device C to generate a device topology map.

[0045] Optionally, in order to more clearly reflect the topological relationship between the target virtual devices, the above device topology structure can be a device topology map corresponding to the target virtual devices, that is, the device topology map is used to more intuitively display the device topology results between the target virtual devices.

[0046] It should be noted that after the user adds the target virtual device to the configuration interface, if the user clicks the location area where the target virtual device is located, the device information corresponding to the target virtual device can be displayed to facilitate the user to easily obtain the device information of the target virtual device.

[0047] Step S210, generating a target device topology map in response to an editing operation instruction executed on the initial device topology map.

[0048] Since there may be topology errors in the automatically generated initial device topology map, optionally, after the initial device topology map is generated, the initial device topology map can be edited to generate a target device topology map to reduce the probability of topology errors in the generated target device topology map.

[0049] Optionally, the process of editing the initial device topology map to generate the target device topology map may be: generating the target device topology map in response to an editing operation instruction executed on the initial device topology map.

[0050] Optionally, the editing operation instruction may be an instruction for editing a preset configuration rule, or an instruction for editing a target virtual device in a configuration interface, which is not limited in this embodiment. For example, the editing operation instruction may be used to increase or decrease a target virtual device in a configuration interface.

[0051] Through the above steps S202 to S210, preset configuration rules are loaded, wherein the preset configuration rules are used to characterize the topological configuration between virtual devices corresponding to physical devices in the LED display system; the device type and device quantity of several target physical devices to be configured are obtained, wherein the target physical devices are all or part of the preset physical devices; according to the device type and device quantity of the several target physical devices, several target virtual devices corresponding to the target physical devices are added to the configuration interface; according to the preset configuration rules, automatic topological operations are performed on the target virtual devices to obtain an initial device topology map; in response to the editing operation instructions performed on the initial device topology map, a target device topology map is generated, which solves the problem of physical device topology errors caused by errors in the generated device topology map in the LED display system device topology editing method in the related art, thereby reducing the topological errors of the physical devices.

[0052] In an exemplary embodiment, loading preset configuration rules includes: sending a device configuration information acquisition instruction to a preset entity device, wherein the device configuration information acquisition instruction is used to obtain configuration information between preset entity devices; receiving device configuration information, wherein the device configuration information includes at least one of the following: connection interface information between preset entity devices, interface connection types between preset entity devices, and device identification of preset entity devices; generating preset configuration rules based on the device configuration information, and loading the preset configuration rules.

[0053] In this embodiment, the process of loading the preset configuration rules may be: first sending a device configuration information acquisition instruction to the preset entity device, then receiving the device configuration information, and finally generating the preset configuration rules according to the device configuration information, and loading the preset configuration rules. Optionally, the preset entity device may be connected to a host computer, and the process of sending the device configuration information acquisition instruction to the preset entity device may be: sending the device configuration information acquisition instruction to the host computer connected to the preset entity device, and then the host computer acquires the configuration information between the preset entity devices.

[0054] Optionally, the process of receiving the device configuration information may be that the host computer sends the device configuration information to the terminal device after acquiring the device configuration information. Optionally, since information leakage may occur during the process of the host computer sending the device configuration information to the terminal device, in order to protect the security of the device configuration information, the device configuration information may be encrypted before being sent to the terminal device.

[0055] Optionally, the process of generating preset configuration rules according to the device configuration information may be: determining preset entity devices and topological relationships between preset entity devices according to the device configuration information, wherein the preset configuration rules include preset entity devices and topological relationships between preset entity devices.

[0056] Optionally, the process of loading the preset configuration rules is similar to the process of loading the preset configuration rules, which will not be described in detail in this embodiment.

[0057] Through this embodiment, a device configuration information acquisition instruction is first sent to the preset physical device to obtain the device configuration information, and then the preset configuration rules are generated and loaded according to the device configuration information. This can improve the accuracy of the determined preset configuration rules and thus improve the accuracy of the generated target device topology map.

[0058] In an exemplary embodiment, the device type and device quantity of several target entity devices to be configured are obtained, including: performing image acquisition on the target entity devices through an image acquisition device to obtain a device topology image corresponding to the target entity devices; performing an image recognition operation on the device topology image to determine the device type, device quantity and topological relationship of the target entity devices.

[0059] Optionally, after loading the preset configuration rules, the device types and device quantities of the target entity devices to be configured may be obtained, or the device types and device quantities of the target entity devices to be configured may be obtained while loading the preset configuration rules. This is not limited in this embodiment.

[0060] Optionally, the above process of obtaining the device type and device quantity of several target entity devices to be configured can be: first, image acquisition is performed on the target entity device through an image acquisition device to obtain a device topology image corresponding to the target entity device, and then an image recognition operation is performed on the device topology image to determine the device type, device quantity and topological relationship of the target entity device.

[0061] Optionally, the above-mentioned process of performing image recognition operation on the device topology image to determine the device type, device quantity and topological relationship of the target entity device can be: using an image recognition algorithm to perform image recognition on the device topology image to determine the device type, device quantity and topological relationship of the target entity device. The above-mentioned topological relationship can be the connection relationship between the target entity devices (that is, the connection type between the target entity devices, the connection ports between the target entity devices, etc.).

[0062] Optionally, the above-mentioned image recognition algorithm can be an image feature recognition algorithm, and the above-mentioned image features can be image feature geometric features (position and direction, perimeter, area, major axis and minor axis, distance (Euclidean distance, block distance, chessboard distance)); it can also be shape features (geometric morphology analysis: rectangularity, circularity, invariant moment, eccentricity, polygon description, curve description); it can also be amplitude features (moment, projection), histogram features (mean, variance, energy, entropy, L1 norm, L2 norm, etc.), color features (color histogram, color moment) and local binary pattern features.

[0063] Through this embodiment, by performing image recognition on the device topology image corresponding to the target entity device, the device type, device quantity and topological relationship of the target entity device can be determined, which can simplify the process of determining the device type and device quantity of the target entity device and thereby improve the accuracy of the determined device type and device quantity.

[0064] In an exemplary embodiment, the preset entity device includes at least one of the following: an LED display control device, an LED display screen receiving device, and an LED video processing device.

[0065] In this embodiment, the above-mentioned preset entity device may include at least one of the following: an LED display control device, an LED display screen receiving device, and an LED video processing device.

[0066] It should be noted that, in addition to the above-mentioned devices, physical devices belonging to the field of LED display systems can also be preset physical devices.

[0067] Through this embodiment, the preset entity devices are limited to entity devices in the field of LED display systems, and a device topology map in the LED field can be generated in a targeted manner, thereby improving the accuracy of the generated target device topology map.

[0068] In an exemplary embodiment, in response to an editing operation instruction executed on an initial device topology map, a target device topology map is generated, including: when the editing operation instruction is an instruction to edit a preset configuration rule in the initial device topology map, editing the preset configuration rule in accordance with the editing operation instruction to obtain an updated configuration rule; re-performing an automatic topology operation on the target virtual device in accordance with the updated configuration rule to obtain a target device topology map; when the editing operation instruction is an instruction to edit a virtual device in the initial device topology map, updating the virtual device in the configuration interface; performing an automatic topology operation on the updated virtual device in accordance with the preset configuration rule to obtain a target device topology map.

[0069] Optionally, in the process of generating the target device topology map in response to the editing operation instruction executed on the initial device topology map, the target device topology map may be generated in different ways according to different editing operation instructions.

[0070] As an optional example, when the editing operation instruction is an instruction to edit the preset configuration rules in the initial device topology map, the preset configuration rules can be edited according to the editing operation instruction to obtain updated configuration rules; then the automatic topology operation is re-executed on the target virtual device according to the updated configuration rules to obtain the target device topology map.

[0071] For example, when the configuration rule before the update is to connect the LED display control device with the LED video processing device, and the configuration rule after the update is to no longer connect the LED display control device with the LED video processing device, the target virtual device can be automatically topologically operated again according to the updated configuration rule to generate a target device topology map (that is, the connection between the LED display control device and the LED video processing device is disconnected).

[0072] As another optional example, when the editing operation instruction is an instruction to edit the virtual device in the initial device topology map, the virtual device in the configuration interface can be updated; according to the preset configuration rules, automatic topology operations are performed on the updated virtual device to obtain the target device topology map.

[0073] Optionally, the updating of the virtual devices in the configuration interface may be to increase or decrease the target virtual devices in the configuration interface. For example, after adding other virtual devices to the configuration interface, the target device topology map may be generated again based on the virtual devices in the configuration interface.

[0074] Through this embodiment, different methods are used to generate target device topology maps for different types of editing operation instructions, which can improve the accuracy of the generated target device topology map.

[0075] In an exemplary embodiment, according to the device types and device quantities of the target physical devices, several target virtual devices corresponding to the target physical devices are added to the configuration interface, including: according to the device types and device quantities of the target physical devices, the target virtual devices are determined from preset virtual devices to obtain several target virtual devices, wherein the device type of the target virtual device is the same as the device type of the target physical device; and the several target virtual devices are added to the configuration interface.

[0076] In this embodiment, after the device types and device quantities of a plurality of target physical devices are determined, a plurality of target virtual devices corresponding to the target physical devices may be added to the configuration interface.

[0077] Optionally, the above process of adding several target virtual devices corresponding to the target physical devices to the configuration interface can be: first determine the target virtual devices from the preset virtual devices according to the device types and device quantities of the several target physical devices, obtain several target virtual devices, and then add the several target virtual devices to the configuration interface, and the device types of the above target virtual devices are the same as the device types of the target physical devices.

[0078] Optionally, the above process of determining the target virtual device from preset virtual devices based on the device type and device quantity of several target physical devices to obtain several target virtual devices can be: first determine the device type of the target virtual device based on the device type of the target physical device, and then determine the number of target virtual devices of each device type based on the number of devices, thereby obtaining several target virtual devices.

[0079] Through this embodiment, according to the device type and device quantity of several target physical devices, several target virtual devices corresponding to the target physical devices are added to the configuration interface, and the target virtual devices can be accurately added to the configuration interface, thereby improving the accuracy of the determined target device topology map.

[0080] In an exemplary embodiment, device types and device quantities of several target entity devices to be configured are obtained, including: after determining a target preset scene, determining several target scene devices within the target preset scene as several target entity devices, wherein the target scene device is a preset entity device within the target scene; determining the device types and device quantities of the several target scene devices as the device types and device quantities of the several target entity devices.

[0081] In this embodiment, in order to speed up the process of generating a target device topology map, multiple preset scenarios can be pre-set, each preset scenario includes multiple preset physical devices. After the user determines the target scene from multiple preset scenarios, the target device topology map can be generated according to the preset physical devices included in the target scene.

[0082] Optionally, after determining the target preset scene from multiple preset scenes, several target scene devices within the target preset scene can be determined as several target entity devices, the above-mentioned target scene devices are preset entity devices within the target scene, and the device types and device quantities of the several target scene devices are determined as the device types and device quantities of the several target entity devices.

[0083] Through this embodiment, the scene device within the target preset scene is determined as the target entity device, and the device type and device quantity of several target scene devices are determined as the device type and device quantity of several target entity devices, which can simplify the process of determining the device type and device quantity of the target entity device.

[0084] The following is an explanation of the LED display system device topology editing method in the embodiment of the present application in conjunction with an optional example. In this optional example, the configuration interface is a canvas.

[0085] This optional example provides a device topology editor that allows users to monitor device status in real time and improves the convenience of drawing topologies through automatic topology patching.

[0086] Combination Figure 4 As shown, the device topology editor in this optional example can be divided into two parts, wherein the left part is the menu bar and the right area is the canvas.

[0087] The device topology editor may include a variety of different functions, such as previous step, next step, zoom in, zoom out, fit to canvas, actual size, up one layer, down one layer, box selection, grouping, ungrouping, open / close Eagle view, delete, clear canvas and the like.

[0088] Previous step and next step: First, the stack operation is used to record the behavior of each user operation, including node position movement, line modification, grouping and other operations, and each operation is stored in the array in the form of a data snapshot, and an index is maintained. When the user performs the previous step and next step, the snapshot data is obtained by moving the index (increase / decrease) to restore and implement the stack operation, and then return to the previous step or next step.

[0089] Zoom in and out function: This function can render the device in the canvas in a proportionally enlarged or reduced manner.

[0090] Adapt to canvas: Figure 5 As shown, when the user clicks the Fit Canvas button, the x and y coordinates of four points (since the area is a rectangular area, these four points refer to the four vertices of the rectangle) of the critical value of the canvas area (i.e., the minimum area including all devices in the canvas) can be calculated, and the coordinates of the four points obtained can be used as the basis for scaling.

[0091] Actual Size: Renders the device in the canvas at its actual size.

[0092] Up one layer, down one layer: The hierarchy determines the rendering order of nodes. Nodes with smaller hierarchies will be rendered first, and nodes rendered later will overwrite previous nodes, thus realizing the hierarchy function.

[0093] Box selection and grouping: Box selection forms a rectangular area starting from the mouse press point and ending at the release point. Devices that overlap with the rectangular area are grouped together.

[0094] Eagle View: As Figure 6 As shown, when the user clicks the Eagle View button, the main canvas and the devices in the canvas can be reduced by a preset multiple and then displayed in full view.

[0095] Automatic topology logic: After the user adds devices to the canvas, they can be arranged in the form of automatic topology recommended by the system. A set of arrangement and wiring rule algorithms are maintained inside the device topology editor. The arrangement and wiring rule algorithms can be used to automatically perform topology on the devices in the canvas and generate a topology diagram.

[0096] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0097] Corresponding to the LED display system device topology editing method described in the above embodiment, Figure 7 A structural block diagram of a topology editing device for an LED display system provided in an embodiment of the present application is shown. For ease of explanation, only the parts related to the embodiment of the present application are shown.

[0098] According to another aspect of the embodiments of the present application, there is also provided a device for editing topology of an LED display system device for implementing the above-mentioned method for editing topology of an LED display system device. Figure 7 is a structural block diagram of an optional LED display system device topology editing device according to an embodiment of the present application, such as Figure 7 As shown, the device may include:

[0099] A loading unit 702, used for loading a preset configuration rule, wherein the preset configuration rule is used to characterize a topological configuration between virtual devices corresponding to physical devices in the LED display system;

[0100] An acquisition unit 704, connected to the loading unit 702, is used to acquire device types and device quantities of a plurality of target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices;

[0101] An adding unit 706, connected to the acquiring unit 704, is used to add a number of target virtual devices corresponding to the target physical devices to the configuration interface according to the device types and device quantities of the target physical devices;

[0102] A topology unit 708, connected to the adding unit 706, is used to perform automatic topology operations on the target virtual device according to a preset configuration rule to obtain an initial device topology map;

[0103] The generating unit 710 is connected to the topology unit 708 and is used to generate a target device topology map in response to an editing operation instruction executed on the initial device topology map.

[0104] It should be noted that the loading unit 702 in this embodiment can be used to execute the above step S202, the acquisition unit 704 in this embodiment can be used to execute the above step S204, the adding unit 706 in this embodiment can be used to execute the above step S206, the topology unit 708 in this embodiment can be used to execute the above step S208, and the generation unit 710 in this embodiment can be used to execute the above step S210.

[0105] Through the above module, preset configuration rules are loaded, wherein the preset configuration rules are used to characterize the topological configuration between virtual devices corresponding to physical devices in the LED display system; the device type and device quantity of several target physical devices to be configured are obtained, wherein the target physical devices are all or part of the preset physical devices; according to the device type and device quantity of several target physical devices, several target virtual devices corresponding to the target physical devices are added to the configuration interface; according to the preset configuration rules, automatic topological operations are performed on the target virtual devices to obtain an initial device topology map; in response to the editing operation instructions performed on the initial device topology map, a target device topology map is generated, which solves the problem of physical device topology errors caused by errors in the generated device topology map in the LED display system device topology editing method in the related art, thereby reducing the topological errors of the physical devices.

[0106] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0107] According to another aspect of the embodiments of the present application, a storage medium is further provided. Optionally, in this embodiment, the storage medium can be used to execute the program code of any of the above-mentioned methods for editing the topology of the LED display system device in the embodiments of the present application.

[0108] Optionally, in this embodiment, the storage medium may be located on at least one network device among a plurality of network devices in the network shown in the above embodiment.

[0109] Optionally, in this embodiment, the storage medium is configured to store program codes for executing the following steps S202, S204, S206, S208 and S210. Optionally, the specific examples in this embodiment can refer to the examples described in the above embodiments, which will not be repeated in this embodiment.

[0110] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a ROM, a RAM, a mobile hard disk, a magnetic disk, or an optical disk.

[0111] Figure 8 1 is a schematic diagram of an optional electronic device according to an embodiment of the present application. The electronic device may be a computing device such as a desktop computer, a notebook, a PDA, and a cloud server.

[0112] like Figure 8 As shown, the electronic device of this embodiment includes: a processor 11, a memory 12, and a computer program 13 stored in the memory 12 and executable on the processor 11. When the processor 11 executes the computer program 13, steps S202, S204, S206, S208, and S210 in the above-mentioned LED display system device topology editing method embodiment are implemented. Alternatively, when the processor 11 executes the computer program 13, the functions of each module / unit in the above-mentioned device embodiments are implemented, such as Figure 7 The functions of the loading unit 702 , the obtaining unit 704 , the adding unit 706 , the topology unit 708 and the generating unit 710 are shown.

[0113] Exemplarily, the computer program 13 may be divided into one or more modules / units, which are stored in the memory 12 and executed by the processor 11 to complete the present application. The one or more modules / units may be a series of computer program instruction segments capable of completing specific functions, which are used to describe the execution process of the computer program 13 in the electronic device.

[0114] Those skilled in the art will understand that Figure 8 These are merely examples of electronic devices and do not constitute a limitation of the electronic device. The electronic device may include more or fewer components than those shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0115] The processor 11 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.

[0116] The memory 12 may be an internal storage unit of the electronic device, such as a hard disk or memory of the electronic device. The memory 12 may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device. Further, the memory 12 may also include both an internal storage unit of the electronic device and an external storage device. The memory 12 is used to store the computer program and other programs and data required by the electronic device. The memory 12 may also be used to temporarily store data that has been output or is to be output.

[0117] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0118] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0119] In the embodiments provided in the present application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0121] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0122] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electrical carrier signal, telecommunication signal and software distribution medium, etc.

[0123] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0124] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for editing the topology of an LED display system device, characterized in that: include: Loading a preset configuration rule, wherein the preset configuration rule is used to characterize a topological configuration between virtual devices corresponding to physical devices in the LED display system; Obtaining device types and device quantities of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices; According to the device types and device quantities of the target physical devices, adding a number of target virtual devices corresponding to the target physical devices to the configuration interface; According to the preset configuration rules, automatic topology operations are performed on the target virtual device to obtain an initial device topology diagram; In response to an edit operation instruction executed on the initial device topology map, a target device topology map is generated; The loading of preset configuration rules includes: Sending a device configuration information acquisition instruction to a host computer connected to the preset physical device, wherein the device configuration information acquisition instruction is used to acquire configuration information between the preset physical devices, and the host computer and the preset physical device are both connected to a server; Receiving the device configuration information acquired by the host computer, wherein the device configuration information includes at least one of the following: connection interface information between the preset entity devices, interface connection types between the preset entity devices, and device identifiers of the preset entity devices; Generate the preset configuration rule according to the device configuration information, and load the preset configuration rule; The obtaining of device types and device quantities of the plurality of target entity devices to be configured includes: After determining a target preset scene, determining a plurality of target scene devices in the target preset scene as a plurality of target entity devices, wherein the target scene devices are the preset entity devices in the target scene; The device types and device quantities of the target scene devices are determined as the device types and device quantities of the target entity devices.

2. The LED display system device topology editing method according to claim 1, characterized in that: The obtaining of device types and device quantities of the target entity devices to be configured includes: Capturing an image of the target entity device through an image acquisition device to obtain a device topology image corresponding to the target entity device; An image recognition operation is performed on the device topology image to determine the device type, device quantity, and topological relationship of the target entity device.

3. The LED display system device topology editing method according to claim 1, characterized in that: The preset entity device includes at least one of the following: LED display control device, LED display screen receiving device, LED video processing device.

4. The LED display system device topology editing method according to claim 1, characterized in that: The step of generating a target device topology map in response to an edit operation instruction executed on the initial device topology map comprises: In the case where the editing operation instruction is an instruction to edit the preset configuration rule in the initial device topology map, the preset configuration rule is edited according to the editing operation instruction to obtain an updated configuration rule; and the automatic topology operation is re-executed on the target virtual device according to the updated configuration rule to obtain the target device topology map; When the editing operation instruction is an instruction to edit the virtual device in the initial device topology map, the virtual device in the configuration interface is updated; according to the preset configuration rule, the automatic topology operation is performed on the updated virtual device to obtain the target device topology map.

5. The method for editing the topology of an LED display system device according to claim 1, characterized in that: The adding a plurality of target virtual devices corresponding to the target physical devices to the configuration interface according to the device types and device quantities of the plurality of target physical devices comprises: According to the device types and device quantities of the target physical devices, the target virtual device is determined from preset virtual devices to obtain the target virtual devices, wherein the device type of the target virtual device is the same as the device type of the target physical device; Adding a plurality of the target virtual devices to the configuration interface.

6. A device for editing topology of LED display system equipment, characterized in that: include: A loading unit, used to load a preset configuration rule, wherein the preset configuration rule is used to characterize a topological configuration between virtual devices corresponding to physical devices in the LED display system; An acquisition unit, used to acquire device types and device quantities of several target physical devices to be configured, wherein the target physical devices are all or part of the preset physical devices; An adding unit, configured to add a plurality of target virtual devices corresponding to the target physical devices to the configuration interface according to the device types and device quantities of the plurality of target physical devices; A topology unit, configured to perform automatic topology operations on the target virtual device according to the preset configuration rules to obtain an initial device topology diagram; A generating unit, configured to generate a target device topology map in response to an editing operation instruction executed on the initial device topology map; The loading of the preset configuration rule includes: sending a device configuration information acquisition instruction to a host computer connected to the preset entity device, wherein the device configuration information acquisition instruction is used to acquire configuration information between the preset entity devices, and the host computer and the preset entity device are both connected to a server; receiving the device configuration information acquired by the host computer, wherein the device configuration information includes at least one of the following: connection interface information between the preset entity devices, interface connection types between the preset entity devices, and device identifications of the preset entity devices; generating the preset configuration rule according to the device configuration information, and loading the preset configuration rule; The obtaining of device types and device quantities of several target entity devices to be configured includes: after determining a target preset scene, determining several target scene devices within the target preset scene as several target entity devices, wherein the target scene devices are the preset entity devices within the target scene; determining the device types and device quantities of several target scene devices as the device types and device quantities of several target entity devices.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images