Software wire arrangement method and device and electronic equipment

Abstract

The embodiment of the invention provides a software wire arrangement method and device and electronic equipment, and the method comprises the steps that wire arrangement information of the equipment is acquired, the wire arrangement information is displayed on a wire arrangement interface, and the wire arrangement information comprises physical line connection information between a first equipment element and a second equipment element of the equipment; when monitoring that the physical line connection information is wrong, responding to a line arrangement operation for a line arrangement interface, performing virtual line connection on a target second equipment element matched with the first equipment element, and generating a group address; and realizing the device function of the device according to the group address. According to the technical scheme, virtual line connection is carried out on the equipment elements, and the unique group address is generated, so that when line connection between the equipment elements is wrong, manual physical line connection does not need to be carried out again, the equipment function can be realized, the workload and the cost are greatly reduced, and normal operation and operation efficiency of the equipment are effectively maintained.

Description

Technical Field

[0001] Embodiments of the present invention relate to the technical field of device management and configuration, and in particular, to a method, device, and electronic device for software cable management. Background Art

[0002] In modern complex electronic device systems, the wiring connections between device components have become increasingly cumbersome and complex. Traditional cable management methods rely on manual operation, which is not only time-consuming and laborious but also error-prone. Especially in environments such as large-scale device systems or data centers, the number of wiring connections between device components is huge, and the management difficulty is extremely high. Once a wiring connection error occurs, it often requires manual reconnection of the wiring, which not only increases the workload and cost but also seriously affects the normal operation and operating efficiency of the device. Summary of the Invention

[0003] In view of this, in order to effectively solve the technical problems that the existing device component wiring connection errors require manual reconnection, resulting in increased workload and cost, and seriously affecting the normal operation and operating efficiency of the device, embodiments of the present invention provide a method, device, and electronic device for software cable management.

[0004] In a first aspect, embodiments of the present invention provide a method for software cable management, the method including:

[0005] Obtain the cable management information of the device and display the cable management information on the cable management interface, where the cable management information includes the physical wiring connection information between the first device component and the second device component of the device;

[0006] In the case where it is detected that the physical wiring connection information is incorrect, in response to the cable management operation on the cable management interface, perform a virtual wiring connection between the target second device component matching the first device component and the first device component, and generate a group address;

[0007] Implement the device function of the device according to the group address.

[0008] In a possible implementation manner, the cable management information further includes the first device function name corresponding to the first device component and the second device function name corresponding to the second device component;

[0009] Detecting that the physical wiring connection information is incorrect includes:

[0010] Determine whether the first device function name is the same as the second device function name;

[0011] In the case where it is determined that the first device function name is not the same as the second device function name, it is detected that the physical wiring connection information is incorrect.

[0012] In a possible implementation, in response to a cable management operation on the cable management interface, performing a virtual circuit connection between a target second device element that matches a first device element and the first device element, includes:

[0013] In response to a first cable management operation on a second icon control corresponding to a second device element in the cable management interface, disconnecting a first icon control corresponding to the first device element from the second icon control corresponding to the second device element;

[0014] Automatically recycling the second icon control corresponding to the second device element into a preset icon list in the cable management interface;

[0015] Determining a target second device element that matches the first device element from the icon list;

[0016] In response to a second cable management operation on a target second icon control corresponding to the target second device element, connecting the first icon control of the first device element to the target second icon control of the target second device element, to implement a virtual circuit connection between the first device element and the target second device element.

[0017] In a possible implementation, the method further includes:

[0018] Setting the second icon control displayed in the icon list to a first control style.

[0019] In a possible implementation, determining a target second device element that matches the first device element from the icon list, includes:

[0020] Querying, from the icon list, a target second device function name that matches the first device function name;

[0021] Determining the second device element corresponding to the target second device function name as the target second device element that matches the first device element.

[0022] In a possible implementation, the method further includes:

[0023] Setting the target second icon control connected to the first icon control to a second control style.

[0024] In a possible implementation, the method further includes:

[0025] In response to a trigger operation on a save control in the cable management interface, obtaining first element attribute information of the first device element and second element attribute information of the target second device element;

[0026] Sending the first element attribute information, the second element attribute information, and the group address to a specified database for saving.

[0027] In a possible implementation manner, the device functions of a device are implemented based on device networking, including:

[0028] In response to a triggering operation on a control widget issued in the cable management interface, obtain the first device address of the first device component and the second device address of the target second device component;

[0029] Send the group address to the first device corresponding to the first device address and the second device corresponding to the second device address, and construct a device network based on the first device address, the second device address, and the group address;

[0030] Send control information to the first device, so that when the first device receives the control information, it sends the control information to the device network, and controls the first device component to perform corresponding operations based on the control information. The device network sends the control information to the second device subscribing to the group address, so that the second device controls the target second device component to perform corresponding operations based on the control information, and the device function of the first device is realized.

[0031] In a second aspect, an embodiment of the present invention provides a device for software cable management. The device includes:

[0032] An acquisition display module, configured to acquire the cable management information of the device and display the cable management information on the cable management interface, where the cable management information includes the physical line connection information between the first device component and the second device component of the device;

[0033] A cable management module, configured to, in the case of detecting that the physical line connection information is incorrect, in response to the cable management operation on the cable management interface, perform virtual line connection between the target second device component matching the first device component and the first device component, and generate a group address;

[0034] A function implementation module, which implements the device functions of the device according to the group address.

[0035] In a third aspect, an embodiment of the present invention provides an electronic device, which includes: a processor and a memory, and the processor is configured to execute a software cable management program stored in the memory to implement the above-mentioned software cable management method.

[0036] In a fourth aspect, an embodiment of the present invention provides a storage medium, where the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the above-mentioned software cable management method.

[0037] The method, apparatus, and electronic device for software cable management provided by the embodiments of the present invention. The method includes: obtaining the cable management information of the device and displaying the cable management information on the cable management interface, where the cable management information includes the physical line connection information between the first device component and the second device component of the device; in the case where the physical line connection information is detected to be incorrect, responding to the cable management operation on the cable management interface, performing virtual line connection on the target second device component that matches the first device component, and generating a group address; and implementing the device function according to the group address. In the above technical solution, by automatically obtaining the cable management information of the device components and visually displaying it on the cable management interface, the user can quickly understand the physical line connection situation between the device components. When the connection information is detected to be incorrect, the user can perform convenient cable management operations through the cable management interface, implement virtual line connection between the device components, and generate a unique group address. This feature enables the user to flexibly adjust the connection relationship between the device components according to physical requirements, realize the dynamic configuration of the device components, so that when the line connection between the device components is incorrect, the device function can be realized without manually reconnecting the physical lines, greatly reducing the workload and cost, and effectively maintaining the normal operation and operation efficiency of the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a flowchart of an embodiment of a method for software cable management provided by an embodiment of the present invention;

[0039] Figure 2 It is a schematic diagram of a cable management interface provided by an embodiment of the present invention;

[0040] Figure 3 It is a schematic diagram of another cable management interface provided by an embodiment of the present invention;

[0041] Figure 4 It is a flowchart of an embodiment of another method for software cable management provided by an embodiment of the present invention;

[0042] Figure 5 It is a schematic diagram of another cable management interface provided by an embodiment of the present invention;

[0043] Figure 6 It is a flowchart of an embodiment of another method for software cable management provided by an embodiment of the present invention;

[0044] Figure 7 It is a block diagram of an embodiment of a device for software cable management provided by an embodiment of the present invention;

[0045] Figure 8 It is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0046] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0047] To facilitate the understanding of the embodiments of the present invention, the following will further explain and illustrate with specific embodiments in conjunction with the accompanying drawings. The embodiments do not constitute a limitation to the embodiments of the present invention.

[0048] The embodiments of the present invention provide a method for software cable management. This method is applied to an electronic device with an image display screen, such as terminal devices like mobile phones, computers, tablets, etc., which will not be listed one by one here. The electronic device can communicate and connect with the following devices through communication methods such as Bluetooth, wifi (Wireless Fidelity), zigbee (cellular network technology), PLC (Programmable Logic Controller), RS-485 (Recommended Standard 485), and KNX (Konnex, home and building automation system). Refer to Figure 1 , Figure 1 which is a flowchart of an embodiment of a method for software cable management provided by the embodiments of the present invention. Figure 1 The shown process may include the following steps:

[0049] Step 101: Obtain the cable management information of the device and display the cable management information on the cable management interface, where the cable management information includes the physical line connection information between the first device component and the second device component of the device;

[0050] Here, obtaining the cable management information of the device means obtaining the cable management information of all devices for which line connections are made. For example, if the currently line-connected devices are a two-position control panel and a three-position control panel, then the cable management information of the two-position control panel and the three-position control panel needs to be obtained.

[0051] Among them, the cable management information can be obtained through methods such as network management protocols, device configuration files, or the status query interface of the device itself, or manual input, which is not limited here.

[0052] The physical line connection information included in the cable management information is used to indicate the actual physical line connection situation between device components in each device. Among them, the two device components for physical line connection can be respectively called the first device component and the second device component, and it can be understood that the first device component and the second device component are relative concepts.

[0053] For example, if the corridor light button in the two-position control panel is physically connected to the downlight relay in the three-position control panel, then the corridor light button can be called the first device component and the downlight relay can be called the second device component, or the downlight relay can be called the first device component and the corridor light button can be called the second device component.

[0054] In order to enable users to understand the physical line connection situation between device components, the obtained cable management information can be visually displayed on the cable management interface of the image display screen. For the sake of easy understanding, as Figure 2 shown, the physical line connection information of the buttons and relays in the two-position control panel and the three-position control panel is displayed on the cable management interface. Among them, the left square box represents the button, and the circle represents the relay. In order to facilitate distinguishing which button is physically connected to which relay, the cable management information also includes the first device function name corresponding to the first device component and the second device function name corresponding to the second device component. The device function name is the function name for the device component to implement the device function. For example, if the device uses the first device component to control the corridor light, then the first device function name corresponding to the first device component can be the corridor light.

[0055] Through the above description, the device function names corresponding to the device components can be written in the box and the circle. From the Figure 2 cable management information, it can be known that the corridor light button in the two-position control panel is actually physically connected to the downlight relay in the three-position control panel, the spotlight button in the two-position control panel is actually physically connected to the spotlight relay in the two-position control panel, the downlight button in the three-position control panel is actually physically connected to the corridor light relay in the two-position control panel, the ceiling light button in the three-position control panel is actually physically connected to the ceiling light relay in the three-position control panel, the ceiling light button in the three-position control panel is actually physically connected to the ceiling light relay in the three-position control panel, and the chandelier button in the three-position control panel is actually physically connected to the chandelier relay in the three-position control panel. Among them, each button can be called the first device component, and each relay can be called the second device component.

[0056] Step 102, in the case where the physical line connection information is incorrect, in response to the cable management operation on the cable management interface, virtually connect the target second device element matching the first device element to the first device element, and generate a group address;

[0057] The incorrect physical connection information means that the physical line connection between the first device element and the second device element cannot realize the device function. For example, the corridor light button on the above two-position control panel should be physically connected to the corridor light relay on the two-position control panel to achieve the purpose of controlling the corridor light. However, in fact, the corridor light button on the two-position control panel is physically connected to the downlight relay on the three-position control panel, and the corridor light control cannot be realized. Therefore, there is a situation where the physical connection information is incorrect. In order to effectively avoid the series of problems brought by the need for manual reconnection of physical lines due to incorrect physical line connections between device elements, in this embodiment, the first device element and the target second device element can be virtually connected through the corresponding cable management operation on the cable management interface, so as to achieve the purpose of realizing the device function without manually reconnecting the first device element and the target second device element physically.

[0058] The target second device element can be understood as the second device element that can realize the device function when connected to the first device element. For example, if the first device element is the corridor light button, then the target second device element matching the corridor light button is the corridor light relay. By virtually connecting the corridor light button and the corridor light relay, the control of the corridor light can be realized. On Figure 2 this basis, as Figure 3 shown, for the connection situation between device elements after the cable management operation on the cable management interface for device elements with incorrect physical line connection information in Figure 2 , it can be seen that after the cable management operation on the cable management interface, the corridor light button and the corridor light relay are virtually connected, and the downlight button and the downlight relay are virtually connected, so as to realize the virtual connection of the target second device element matching the first device element, and correct the incorrect physical line connection between the first device element and the second device element.

[0059] Among them, the virtual line connection means using virtualization technology to establish a connection between the first device element and the target second device element in the network environment, rather than relying on the actual physical line for connection.

[0060] Specifically, in order to facilitate the identification and management of virtual line connections, a unique group address needs to be generated. Through the group address, not only can the device elements of virtual line connections and their connection status be efficiently tracked, monitored and managed, but also the flexibility and scalability of the device can be improved for easy application.

[0061] Step 103: Implement the device function of the device according to the group address.

[0062] Multicast communication between devices can be achieved through group addresses, so that the device can control the first device element and the target second device element to perform actions to achieve corresponding device functions. It can be understood that when the line management interface is not used to perform the line management function of virtual line connection, the first device element and the second device element that are physically connected appear to be in an integrated state. When there is no physical line connection error between the first device element and the second device element, when the device receives control information, it can control the first device element and the second device element to perform actions to achieve device functions; when the line management interface is used to manage the device elements, the device elements of the device will be separated and integrated. At this time, there is no need to consider the actual physical line connection. When the device receives control information, the device of the first device element will no longer control the action of the target second device element, but will send control information to the device that subscribes to the group address after the line management to control the action of the target second device element to achieve the device function of the device.

[0063] For example, the corridor light button and the corridor light relay are connected by a virtual line, but in fact, since the corridor light relay is physically connected to the downlight button of the three-digit control panel, the corridor light relay is controlled by the three-digit control panel. Therefore, when the corridor light needs to be turned on or off, the multicast communication of the group address enables the two-control panel to control the corridor light button and the three-digit control panel to control the corridor light relay, so as to achieve the purpose of lighting or turning off the corridor light.

[0064] Through the method provided in this embodiment, the acquired wiring information of the device components can be intuitively displayed on the wiring interface, so that the user can quickly understand the physical line connection status between the device components. When the connection information is detected to be incorrect, the user can perform convenient wiring operations through the wiring interface to realize virtual line connection between the device components and generate a unique group address. This feature allows the user to flexibly adjust the connection relationship between the device components according to physical requirements and realize dynamic configuration of the device components. When the line connection between the device components is incorrect, there is no need to manually reconnect the physical line to realize the device function, which greatly reduces the workload and cost and effectively maintains the normal operation and efficiency of the equipment.

[0065] In addition, the method provided in this embodiment is only used for software wiring arrangement. Functions such as scene configuration in the whole house intelligence are still configured using the existing configuration method. Wire management is a prerequisite for configuring the scene. The present invention aims to complete the line inspection and verification work before scene configuration to improve the efficiency of scene configuration. This has no direct relationship with scene control and does not conflict with each other.

[0066] In one embodiment, since device components are distinguished by corresponding device function names, it can be understood that when there is a physical line connection between device components with the same device function name, it indicates that the physical line connection is correct. Conversely, when there is a physical line connection between device components with different device function names, it indicates that the physical line connection is incorrect. Based on this, the process of detecting incorrect physical line connection information includes: determining whether the first device function name is the same as the second device function name; in the case where it is determined that the first device function name is different from the second device function name, incorrect physical line connection information is detected. As Figure 2 shown, since the first device function name of the porch light button is porch light, and the second device function name of the downlight relay is downlight, it can be understood that the porch light button is for controlling the porch light, and the downlight relay is for controlling the downlight. Thus, it can be seen that since the device function names of the porch light button and the downlight relay are different, that is, the device functions achieved are different, therefore, the physical line connection between the porch light button and the downlight relay is incorrect, that is, the physical line connection information is incorrect. Conversely, in the case where the first device function name is the same as the second device function name, it is detected that the physical line connection information is correct, that is, the first device component and the second device component have a correct physical line connection and can directly achieve the device function of the device. Therefore, there is no need to re-perform virtual line connection through the cable management operation on the cable management interface.

[0067] As Figure 4 shown, as an optional embodiment, like the aforementioned method, in step 102, responding to the cable management operation on the cable management interface and performing virtual line connection between the target second device component matching the first device component and the first device component includes the following steps:

[0068] Step 401, in response to the first cable management operation on the second icon control corresponding to the second device component in the cable management interface, disconnect the first icon control corresponding to the first device component from the second icon control corresponding to the second device component;

[0069] Both the above-mentioned first device component and second device component have a corresponding icon control on the cable management interface to facilitate operating the first device component or the second device component through the icon control. In actual application, the user can select the second icon control corresponding to the second device component to be disconnected in the cable management interface through a mouse, a touch screen or other input devices, and perform the first cable management operation (such as clicking, dragging, etc.) to disconnect the first icon control corresponding to the first device component from the second icon control corresponding to the second device component, thereby indicating that the first device component and the second device component with incorrect physical line connection are logically disconnected, rather than physically cutting the line.

[0070] For ease of understanding, as Figure 2As shown, the square box is the icon control corresponding to the button, and the circle is the icon control corresponding to the relay. Since the corridor light button is physically connected to the downlight relay incorrectly, in order to correct the incorrect physical connection between the corridor light button and the downlight relay, it is necessary to perform a first cable management operation such as clicking or dragging the circle of the downlight relay to disconnect the two icon controls. After disconnection, the corridor light button loses the relay, that is, as Figure 5 shown.

[0071] In another embodiment, the first cable management operation can also be performed on the first icon control of the first device element to achieve the purpose of disconnecting the first icon control corresponding to the first device element from the second icon control corresponding to the second device element.

[0072] Step 402, automatically recycle the second icon control corresponding to the second device element into the preset icon list in the cable management interface;

[0073] As Figure 2 shown, the long bar on the right side of the cable management interface is the icon list (the specific position of the icon list on the cable management interface is not limited). The icon list is used to store the second icon control corresponding to the second device element that is disconnected from the first device element through the first cable management operation. For ease of understanding, as Figure 5 shown, the icon control corresponding to the downlight relay can be disconnected from the icon control corresponding to the corridor light button and stored in the icon list. Similarly, the icon control corresponding to the corridor light relay can be disconnected from the icon control corresponding to the downlight button and stored in the icon list.

[0074] In actual application, for easy highlighting, the second icon control that can be displayed in the icon list can be set to the first control style. The first control style is not limited to color style, control shape, etc. For example, the color of the second icon control displayed in the icon list can be set to red.

[0075] Step 403, determine the target second device element that matches the first device element from the icon list;

[0076] Specifically, query the target second device function name that matches the first device function name from the icon list; determine the second device element corresponding to the target second device function name as the target second device element that matches the first device element.

[0077] Step 404, in response to the second cable management operation for the target second icon control corresponding to the target second device element, connect the first icon control of the first device element to the target second icon control of the target second device element to realize the virtual circuit connection between the first device element and the target second device element.

[0078] In actual application, the user can perform a second cable management operation (such as clicking, dragging, etc.) on the target second icon control corresponding to the target second device component in the icon list to connect the first icon control corresponding to the first device component with the target second icon control corresponding to the target second device component, so as to represent the establishment of a logical connection between the first device component and the target second device component, rather than a physical circuit connection.

[0079] As Figure 5 shown, a dragging operation can be performed on the icon control corresponding to the corridor lamp relay corresponding to the corridor lamp button to drag the corridor lamp relay out of the icon list and drag the corridor lamp relay to the position of the bar box where the corridor lamp button is located in the direction of the dotted arrow to achieve the virtual circuit connection between the corridor lamp button and the corridor lamp relay. Similarly, the process of virtual circuit connection for the downlight button and the downlight relay is the same as above and will not be elaborated here. The connection situation of all device components after cable management through the cable management interface is Figure 3 shown.

[0080] In actual application, in order to facilitate highlighting which device components have undergone cable management through the cable management interface, the target second icon control connected to the first icon control can be set to a second control style, and this second control style is not limited to color style, control shape, etc. For example, the color of the target second icon control of the target second device component connected to the first device component through a virtual circuit is set to dark yellow.

[0081] In actual application, in order to facilitate the user to quickly distinguish whether the physical circuit connection is correct or incorrect, after obtaining the cable management information of the device, different control styles can be displayed for the second icon control of the second device component on the cable management interface. For example, the color of the second icon control of the second device component with a correct physical circuit connection is displayed as green on the cable management interface, and the color of the second icon control of the second device component with an incorrect physical circuit connection is displayed as red. In this embodiment, the specific control style displayed for the second icon control of the second device component on the cable management interface is not limited.

[0082] As Figure 6 shown, as an optional implementation manner, for the method as described above, step 103 for implementing the device function of the device based on device networking includes the following steps:

[0083] Step 601, in response to a trigger operation for the issued control on the cable management interface, obtain the first device address of the first device component and the second device address of the target second device component;

[0084] As Figure 2As shown, a distribution control is set at the lower right corner of the cable management interface (the position of the distribution control on the cable management interface is not limited here). When a triggering operation such as a single click or double click is performed on the distribution control, the first device address of the first device component and the second device address of the target second device component can be obtained. It can be understood that the obtained first device address is the device address of the first device that can control the action of the first device component, and the second device address is the device address of the second device that can control the action of the target second device component.

[0085] Continuing the previous example, since the corridor lamp button is controlled by a two - position control panel, and the corridor lamp relay is physically connected to the downlight button, the corridor lamp relay is controlled by a three - position control panel. Therefore, when triggering the distribution control, the device addresses of the two - position control panel and the three - position control panel need to be obtained.

[0086] Step 602: Send the group address to the first device corresponding to the first device address and the second device corresponding to the second device address, and construct a device network based on the first device address, the second device address, and the group address.

[0087] After triggering the distribution control to obtain the first device address and the second device address, the group address needs to be sent to the first device corresponding to the first device address and to the second device corresponding to the second device address to ensure that all relevant devices can receive the group address and thus know which device network the device is assigned to.

[0088] In actual application, other communication keyword field information except the group address groupaddr can also be sent to the device to facilitate the device to clarify relevant communication information. Among them, the other communication keyword field information includes but is not limited to the message sequence number seq, the command cmd, the attribute attr (such as data type, data format, priority, etc.), the device address addr, and the data length len.

[0089] For easy understanding, Table 1 shows the format table of the distribution information including the group address and other communication keyword field information sent to the device after triggering the distribution control:

[0090] Table 1

[0091]

[0092] It should be noted that only an example of the distribution information is shown in Table 1, and the specific distribution information can be set according to actual needs and is not limited here.

[0093] In specific implementation, when constructing a device network based on the first device address, the second device address, and the group address, it is necessary to determine the communication path between devices, set the network topology structure, allocate network resources, etc., to ensure that the device network can operate efficiently and stably.

[0094] Step 603: Send control information to the first device, so that when the first device receives the control information, it sends the control information to the device network and controls the first device component to perform corresponding operations based on the control information. The device network sends the control information to the second device subscribing to the group address, so that the second device controls the target second device component to perform corresponding operations based on the control information, realizing the device function of the first device.

[0095] The control information can be sent through an electronic device or by manually operating the control button of the first device, and is not limited here.

[0096] First, the control information is sent to the first device. This control information contains the operation instructions or relevant data that the first device needs to execute. When the first device receives this control information, it not only responds to this information but also further sends this control information to the device network it belongs to.

[0097] In the device network, there may be multiple devices. These devices are connected to each other in a certain way (such as network protocols, communication links, etc.) to form a system that can communicate and cooperate with each other. When the first device sends the control information to the device network, this information will be received or sensed by other devices in the network.

[0098] Specifically, for the second device subscribing to the group address, when the device network sends out control information that matches the group address, the second device will receive this information. Then, based on the received control information, the second device will control its target second device component to perform corresponding operations.

[0099] At the same time, after the first device sends the control information to the device network, it will also control the first device component to perform corresponding operations based on this control information, thereby realizing the device function of the first device. This process reflects the process of the first device component performing virtual line connection and the target second device component working together in the device network.

[0100] The data format of the specific control information sent by the device network to the second device is shown in Table 2:

[0101] Table 2

[0102] seq cmd len groupaddr Onoff 1 byte 1 byte 1 byte 2 bytes 1 byte 0Xxx 0Xxx 0Xxx 0Xxxxx 0Xxx

[0103] The Onoff in Table 2 is the specific switch control quantity for the control panel in the control information, and the indicator light controlled by the control panel is turned on or off according to this control quantity Onoff. It should be noted that only an example of the control information is shown in Table 2, and the specific control information can be set according to actual needs and is not limited here.

[0104] This application allows users to perform virtual line connections on the cable management interface and generate corresponding group addresses. This means that even if there are errors in the connection relationship of the physical lines, users can correct the connection relationship through simple software operations without actually reconnecting the physical lines, and can realize device functions through the device networking constructed by the group addresses. This greatly enhances the flexibility of the connection relationship between device components to adapt to the changes in more scenario requirements.

[0105] In actual applications, in addition to sending the issued information to the first device and the second device to construct a device network to realize device functions, the issued information can also not be sent to the first device and the second device, but the cable management information is managed by the electronic device itself. When sending control information to the first device through the electronic device, the control information is simultaneously sent to the second device that has also subscribed to the group address, so as to control the corresponding device components to realize device functions.

[0106] In one implementation, in order to avoid the loss of information of the device components after cable management, it is necessary to save the information of the device components after cable management. In this embodiment, in response to the trigger operation for the save control in the cable management interface, the first component attribute information of the first device component and the second component attribute information of the target second device component are obtained; the first component attribute information, the second component attribute information, and the group address are sent to the specified database for storage.

[0107] As Figure 2 shown, a save control is set at the lower left corner of the cable management interface (the position of the save control on the cable management interface is not limited here). When a trigger operation such as a single click or double click is performed on the save control, the first component attribute information of the first device component and the second component attribute information of the target second device component can be obtained. It can be understood that the first component attribute information is the information related to the first device component after cable management. Taking the corridor light button as an example, its component attribute information includes but is not limited to: button number: 1, button name: switch_1, device function name: corridor light, belonging to the control panel: 9069d5491322 (mac), panel naming: two-position control panel, group address: 1, physical model: {"property": "Switch_1", "value": 1, "modelId": 4096}. The component attribute information corresponding to the above corridor light button can also have an English version corresponding to the Chinese version, which is not exemplified here.

[0108] Similarly, the second component attribute information is the information related to the target second device component after the wiring. Taking the corridor light relay as an example, its component attribute information includes but is not limited to: relay number: 1, relay name: relay_1, device function name: corridor light, control panel: 9069d5491323 (mac), panel name: three-digit control panel, group address: 1, object model: {"property": "relay_1", "value": 1, "modelId": 4097}. The component attribute information corresponding to the corridor light relay can also have an English version corresponding to the Chinese version, which is not shown here.

[0109] The first component attribute information, the second component attribute information and the group address are sent to a database corresponding to the electronic device or a designated database such as a cloud database for storage, so that if the relevant information of the device components after wiring is lost, it can be queried and obtained again from the designated database for easy use.

[0110] See also Figure 7 , is a block diagram of an embodiment of a software line management device provided by an embodiment of the present invention. Figure 7 As shown, the device comprises:

[0111] An acquisition and display module 701 is used to acquire the wiring information of the device and display the wiring information on the wiring interface, wherein the wiring information includes the physical line connection information between the first device element and the second device element of the device;

[0112] The line management module 702 is used to, when detecting that the physical line connection information is incorrect, respond to the line management operation on the line management interface, connect the target second device element matched with the first device element with a virtual line, and generate a group address;

[0113] The function realization module 703 realizes the device function of the device according to the group address.

[0114] The software wiring management device provided by this embodiment can intuitively display the wiring management information of the acquired device components on the wiring management interface, so that the user can quickly understand the physical line connection status between the device components. When the connection information is detected to be incorrect, the user can perform convenient wiring management operations through the wiring management interface to realize virtual line connection between the device components and generate a unique group address. This feature allows the user to flexibly adjust the connection relationship between the device components according to physical requirements and realize dynamic configuration of the device components. When the line connection between the device components is incorrect, there is no need to manually reconnect the physical line to realize the device function, which greatly reduces the workload and cost and effectively maintains the normal operation and efficiency of the equipment.

[0115] Figure 8 A structural schematic diagram of an electronic device provided by an embodiment of the present invention Figure 8 The illustrated electronic device 500 includes: at least one processor 501, a memory 502, at least one network interface 504, and other user interfaces 503. Each component in the electronic device 500 is coupled together through a bus system 505. It can be understood that the bus system 505 is used to implement connection and communication between these components. In addition to including a data bus, the bus system 505 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 8 all kinds of buses are labeled as the bus system 505.

[0116] Among them, the user interface 503 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a touchpad, or a touch screen, etc.).

[0117] It can be understood that the memory 502 in the embodiment of the present invention may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory 502 described herein is intended to include but not be limited to these and any other suitable types of memory.

[0118] In some embodiments, the memory 502 stores the following elements, executable units or data structures, or subsets thereof, or extended sets thereof: the operating system 5021 and the application programs 5022.

[0119] Among them, the operating system 5021 includes various system programs, such as the framework layer, the core library layer, the driver layer, etc., which are used to implement various basic services and process hardware-based tasks. The application programs 5022 include various application programs, such as a Media Player, a Browser, etc., which are used to implement various application services. The program for implementing the method of the embodiment of the present invention may be included in the application programs 5022.

[0120] In the embodiment of the present invention, by invoking the program or instruction stored in the memory 502, specifically, the program or instruction stored in the application programs 5022, the processor 501 is used to execute the method steps provided by each method embodiment.

[0121] The method disclosed in the above embodiment of the present invention can be applied to the processor 501 or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor 501 or the instruction in the form of software. The above processor 501 may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiment of the present invention can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software units in the decoding processor. The software unit may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 502, and the processor 501 reads the information in the memory 502 and combines its hardware to complete the steps of the above method.

[0122] It will be appreciated that the embodiments described herein can be implemented using hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processing unit can be implemented in one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this application, or any combination thereof.

[0123] For software implementation, the technologies described herein can be implemented by units that execute the functions described herein. The software code can be stored in a memory and executed by a processor. The memory can be implemented within the processor or externally to the processor.

[0124] The electronic device provided in this embodiment can be an electronic device as shown in Figure 8 and can execute all the steps of the software wire management method as shown in Figure 1 , 4 , 6, thereby achieving the technical effects of the software wire management method as shown in Figure 1 , 4 , 6. For specific details, please refer to the relevant descriptions in Figure 1 , 4 , 6. For the sake of brevity, no further details will be provided here.

[0125] The embodiments of the present invention also provide a storage medium (computer-readable storage medium). The storage medium stores one or more programs. Here, the storage medium can include volatile memory, such as random access memory; the memory can also include non-volatile memory, such as read-only memory, flash memory, hard disk, or solid-state drive; the memory can also include a combination of the above types of memory.

[0126] When one or more programs in the storage medium can be executed by one or more processors to implement the above software wire management method.

[0127] The processor is used to execute the software wire management program stored in the memory to implement the steps of the software wire management method.

[0128] Those skilled in the art should also be able to further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0129] The steps of the methods or algorithms described in combination with the embodiments disclosed herein can be implemented by hardware, software modules executed by a processor, or a combination of the two. The software modules can be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium well-known in the technical field.

[0130] The specific embodiments described above have further elaborated on the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only for the specific embodiments of the present invention and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A software cable management method, characterized in that: The method comprises: Acquire wiring information of a device, and display the wiring information on a wiring interface, wherein the wiring information includes physical line connection information between a first device element and a second device element of the device; In the case where the physical line connection information is detected to be incorrect, in response to the line management operation on the line management interface, a target second device element matching the first device element is connected to the first device element through a virtual line, and a group address is generated; A device function of the device is implemented according to the group address.

2. The method according to claim 1, characterized in that The wiring information also includes a first device function name corresponding to the first device element and a second device function name corresponding to the second device element; The monitoring that the physical line connection information is incorrect includes: Determining whether the first device function name is consistent with the second device function name; When it is determined that the first device function name is inconsistent with the second device function name, it is detected that the physical line connection information is incorrect.

3. The method according to claim 2, characterized in that The step of responding to the wire management operation of the wire management interface and connecting a target second device element matching the first device element with the first device element through a virtual line includes: In response to a first line management operation on a second icon control corresponding to the second device element in the line management interface, disconnecting a first icon control corresponding to the first device element from a second icon control corresponding to the second device element; Automatically reclaiming the second icon control corresponding to the second device element into a preset icon list in the cable management interface; determining a target second device element matching the first device element from the icon list; In response to a second line management operation on a target second icon control corresponding to the target second device element, the first icon control of the first device element is connected with the target second icon control of the target second device element to achieve a virtual line connection between the first device element and the target second device element.

4. The method according to claim 3, characterized in that The method further comprises: The second icon control displayed in the icon list is set to the first control style.

5. The method according to claim 3, characterized in that: Determining a target second device element matching the first device element from the icon list includes: Querying the icon list for a target second device function name that matches the first device function name; The second device element corresponding to the target second device function name is determined as the target second device element matching the first device element.

6. The method according to claim 1, characterized in that The method further comprises: The target second icon control connected to the first icon control is set to a second control style.

7. The method according to claim 1, characterized in that The method further comprises: In response to a trigger operation for saving a control in the wiring management interface, obtaining first component attribute information of the first device component and second component attribute information of the target second device component; The first component attribute information, the second component attribute information and the group address are sent to a designated database for storage.

8. The method according to claim 1, characterized in that: The implementing the device function of the device based on the device networking includes: In response to a trigger operation for sending a control in the cable management interface, obtaining a first device address of the first device element and a second device address of the target second device element; Sending the group address to a first device corresponding to the first device address and a second device corresponding to the second device address, and building a device network based on the first device address, the second device address and the group address; Send control information to the first device, so that the first device sends the control information to the device network when receiving the control information, and controls the first device component to perform corresponding operations based on the control information. The device network sends the control information to the second device that subscribes to the group address, so that the second device controls the target second device component to perform corresponding operations based on the control information, thereby realizing the device function of the first device.

9. A software cable management device, characterized in that: The device comprises: An acquisition and display module is used to acquire the wiring information of the device and display the wiring information on the wiring interface, wherein the wiring information includes the physical line connection information between the first device element and the second device element of the device; A line management module, configured to, when detecting that the physical line connection information is incorrect, respond to a line management operation on the line management interface, connect a target second device element matching the first device element with the first device element through a virtual line, and generate a group address; A function implementation module implements the device function of the device according to the group address.

10. An electronic device, characterized in that: include: A processor and a memory, wherein the processor is used to execute a software wiring management program stored in the memory to implement the software wiring management method according to any one of claims 1 to 8.

Images