Device management method, apparatus, device, and storage medium

Abstract

The application provides a device management method, device, apparatus and storage medium, and is applied to a device installed with a device management platform. The method comprises the following steps: displaying a device management platform interface, wherein the device management platform interface comprises a first area for determining a target device and a second area comprising a function control; determining at least one target device in response to a first operation facing the first area; receiving a second operation facing a target function control in the second area; and remotely controlling the target device to perform an operation corresponding to the target function control in response to the second operation. Thus, remote management of the device is realized, especially when the number of devices is large, remote management of a batch of devices is realized, the convenience of remote management of the device is improved, and a better experience is provided for the user.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a device management method, apparatus, device, and storage medium. Background Technology

[0002] Debugging is a necessary procedure to ensure the normal operation of the provided equipment. One specific implementation of debugging is through a simulator. Simulator debugging requires a one-to-one hardware configuration, meaning one simulator corresponds to one target device.

[0003] Currently, when debugging equipment using a simulator, the debugging personnel need to locate the target device, manually turn it on for debugging, and manually turn it off after debugging. This makes it inconvenient to manage the power on / off and debugging of a large number of target devices. Summary of the Invention

[0004] This application provides a device management method, apparatus, equipment, and storage medium to address the problem of insufficient convenience in remote device management.

[0005] Firstly, this application provides a device management method applied to a device equipped with a device management platform, the device management method comprising:

[0006] Display device management platform interface, the device management platform interface includes a first area for determining the target device and a second area containing functional controls;

[0007] In response to a first operation directed toward the first region, at least one target device is identified;

[0008] Receive a second operation targeting the function control in the second region;

[0009] In response to the second operation, the target device is remotely controlled to perform the operation corresponding to the target function control.

[0010] In one feasible implementation, the first area is used to display a device identifier, and the step of determining at least one target device in response to a first operation targeting the first area includes:

[0011] In response to a device selection operation targeting the first region, the device corresponding to at least one device identifier selected by the device selection operation is determined to be the target device.

[0012] In one feasible implementation, the first area is used to input a device identifier, and the step of determining at least one target device in response to a first operation targeting the first area includes:

[0013] In response to a device input operation targeting the first region, the device corresponding to at least one device identifier input in the device input operation is determined to be the target device.

[0014] In one feasible implementation, the functional control includes a first control for indicating completion of device selection, the target functional control being the first control, and the step of remotely controlling the target device to perform the operation corresponding to the target functional control in response to the second operation includes:

[0015] In response to the second operation, an operation page is displayed, the operation page including a plurality of second controls, including a power-on control and a power-off control;

[0016] In response to a click operation on a target second control among the plurality of second controls, the target device is remotely controlled to perform the operation corresponding to the target second control.

[0017] In one feasible implementation, the target second control is a power-on control, and the step of remotely controlling the target device to perform the operation corresponding to the target second control in response to a click operation on the target second control among the plurality of second controls includes:

[0018] In response to a click operation on the power-on control, the state of the target device is determined;

[0019] If the target device is in an online state, then the target device is restarted remotely.

[0020] In one feasible implementation, the second control further includes a status viewing control, and also includes:

[0021] In response to a click operation on the status viewing control, the status of the target device is displayed, including online status and / or offline status.

[0022] In one feasible implementation, the functional control includes a third control for submitting the target device, the target functional control being the third control, and the step of remotely controlling the target device to perform the operation corresponding to the target functional control in response to the second operation includes:

[0023] In response to the second operation, a remote connection page is displayed, which is used to input user account information and user password;

[0024] In response to the user's input of user account information and user password, remote login to the target device is performed.

[0025] One feasible implementation also includes:

[0026] After remotely logging into the target device, the target device is debugged.

[0027] In one feasible implementation, the debugging of the target device includes:

[0028] In response to the selection of a corresponding application, JTAG debugging or EJTAG debugging of the target device is initiated through the application corresponding to the selection operation.

[0029] Secondly, this application provides an equipment management device for use in equipment equipped with an equipment management platform, the equipment management device comprising:

[0030] The display module is used to display the device management platform interface, which includes a first area for determining the target device and a second area containing functional controls.

[0031] A determination module is configured to determine at least one target device in response to a first operation directed toward the first region;

[0032] The receiving module is used to receive a second operation targeting the function control in the second area;

[0033] A control module is used to remotely control the target device to perform the operation corresponding to the target function control in response to the second operation.

[0034] Thirdly, this application provides an electronic device, including: at least one processor and a memory;

[0035] The memory stores computer-executed instructions;

[0036] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the device management method as described in the first aspect above.

[0037] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the device management method as described in the first aspect above.

[0038] Fifthly, this application provides a computer program product, which, when executed by a processor, implements the device management method as described in the first aspect above.

[0039] The device management method, apparatus, device, and storage medium provided in this application display a device management platform interface on a device equipped with a device management platform. The device management platform interface includes a first area for determining a target device and a second area containing functional controls. In response to an operation on the first area, at least one target device is determined. In response to a second operation on a target functional control in the second area, the target device is remotely controlled to perform the operation corresponding to the target functional control.

[0040] Thus, the equipment management platform enables remote management of equipment, especially when there are a large number of devices, allowing for remote management of batches of equipment without the need for manual on-site location and operation. This improves the convenience of remote equipment management and enhances the user experience. Attached Figure Description

[0041] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0042] Figure 1 Application scenario diagrams provided for embodiments of this application;

[0043] Figure 2 A schematic flowchart illustrating a device management method provided in an embodiment of this application;

[0044] Figure 3 A flowchart illustrating a device management method provided in yet another embodiment of this application;

[0045] Figure 4 A flowchart illustrating a device management method provided in yet another embodiment of this application;

[0046] Figure 5 A flowchart illustrating a device management method provided in yet another embodiment of this application;

[0047] Figure 6 A flowchart illustrating a device management method provided in yet another embodiment of this application;

[0048] Figure 7 This is a schematic diagram of the structure of a device management apparatus provided in an embodiment of this application;

[0049] Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0050] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0051] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0052] Emulator debugging requires a one-to-one hardware configuration. In related technologies, during emulator debugging, the operator can only manually operate one machine at a time. When there are many machines, this method is inconvenient and incurs high labor costs.

[0053] Among them, the simulator can also be called the debugger, which is used to debug the equipment.

[0054] Taking Joint Test Action Group (JTAG) debugging as an example, a JTAG emulator (a device that performs debugging through the JTAG boundary scan port of an ARM chip) is also called a JTAG debugger; taking Enhanced Joint Test Action Group (EJTAG) debugging as an example, an EJTAG emulator is also called an EJTAG debugger.

[0055] To address the aforementioned problems, this application provides a device management method, apparatus, device, and storage medium. This application displays a device management platform interface, which includes a first area for identifying a target device and a second area containing functional controls. In response to a first operation directed to the first area, at least one device is identified. In response to a second operation directed to a target functional control in the second area, the target device is remotely controlled to perform the operation corresponding to the target functional control. Therefore, based on this application, debugging personnel can select at least one device to be debugged on the device management platform interface and remotely control that at least one device without needing to physically locate the device. Thus, this application effectively improves the convenience of device management.

[0056] The equipment management method provided in this application can be applied to Figure 1 The application scenarios shown are as follows. Figure 1 As shown, the application scenario involves management device 101 and multiple remote devices 102. Figure 1(Taking a remote device as an example). Users can install a device management platform on the management device 101 to manage multiple remote devices 102.

[0057] Optionally, multiple remote devices 102 are each connected to a corresponding emulator. Figure 1 (Not shown). The emulator is used for debugging the remote device 102. The user can remotely control the remote device 102 from the management device 101 to debug it using the emulator.

[0058] Among them, the management device 101 and the remote device 102 can be terminals or servers. Figure 1 In this example, we take management device 101 as the terminal and remote device 102 as the server.

[0059] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0060] For example, the execution subject of each method embodiment in this application is a device equipped with a device management platform, which may be a terminal with a display screen or a server.

[0061] The terminal can be a personal digital assistant (PDA) device, a handheld device (such as a smartphone or tablet), a computing device (such as a personal computer or PC), an in-vehicle device, a wearable device (such as a smartwatch or smart bracelet), or a smart home device (such as a smart display device).

[0062] refer to Figure 2 , Figure 2 This is a schematic flowchart of a device management method provided in an embodiment of this application.

[0063] like Figure 2 As shown, the equipment management methods include:

[0064] S201. Display device management platform interface, the device management platform interface includes a first area for identifying the target device and a second area containing functional controls.

[0065] The device management platform is an application installed on the current device, and the device management platform interface is one of the application pages of the device management platform. For example, the application interface of the device management platform may also include a user login interface and a user personal center interface.

[0066] The target device is the device that needs to be remotely managed.

[0067] The functional controls are user interaction controls that correspond to at least one operation (device management operation). Users can perform at least one device management operation on the target device by interacting with the functional controls.

[0068] The second area can contain one or more functional controls, and different functional controls can correspond to different operations (device management operations).

[0069] In this embodiment, after the device management platform is started, the device management platform interface can be displayed on the current device's screen. The device management platform interface includes at least two interface areas: a first area and a second area. The first area is used to identify the target device, providing the user with an interactive area for identifying the target device. The second area displays functional controls, providing the user with an interactive area for managing the target device. Therefore, by reasonably distinguishing between the interface areas for device identification and those for device management, it is easier to manage at least one device and provides the user with a better interactive experience.

[0070] In one possible implementation, the first area and the second area are positioned vertically or horizontally on the device management platform interface.

[0071] In another possible implementation, on the device management platform interface, the first area is located in the middle of the device management platform interface, and the second area is located on at least both sides (e.g., the top and bottom sides) of the first area.

[0072] In one possible implementation, when displaying the device management platform interface, the device management platform interface can be displayed in response to a program startup request for the device management platform.

[0073] In another possible implementation, when displaying the device management platform interface, the device management platform interface can be displayed in response to an access request directed to the device management platform interface.

[0074] In another possible implementation, when displaying the device management platform interface, the interface can be displayed in response to a message indicating that the user has successfully logged into the device management platform.

[0075] S202, in response to a first operation toward a first region, at least one target device is identified.

[0076] The first operation is an interactive operation performed by the user in the first area, used to identify the target device.

[0077] In this embodiment, before remotely managing the device, at least one target device needs to be identified. Therefore, a first operation targeting a first area can be received, from which at least one device identifier can be obtained, and the device corresponding to the at least one device identifier can be identified as the target device.

[0078] S203, Receive the second operation targeting the function control in the second area.

[0079] The second operation is an interactive operation between the user and the target function control in the second area. It is used to trigger the device management command corresponding to the target function control, and then trigger the current device to execute the command.

[0080] The target function control can be one or more.

[0081] The second operation can be, for example, a single click, a double click, a long press, or an Enter key operation.

[0082] In this embodiment, after determining the target device, if the user wants to perform target management operations on the target device, they can determine the target function control corresponding to the target management operation in the second area and perform a second operation on the target function control. Therefore, after determining the target device, the system can receive the user's second operation on the target function control in the second area.

[0083] In one possible implementation, if a first operation targeting the first region is not received before receiving a second operation targeting the target function control in the second region, the target device can be determined to be a preset default device, or the target device can be determined to be the device that was remotely controlled last time. Thus, the user can avoid re-determining the target device each time by setting a default device or retaining the device identifier of the device that was remotely controlled last time, thereby providing a better user experience.

[0084] S204. In response to the second operation, the remote control target device executes the operation corresponding to the target function control.

[0085] In this embodiment, the current device may attempt to establish a communication connection with the target device after identifying at least one target device, or after receiving the second operation. If the current device successfully establishes a communication connection with the target device, it may remotely control the target device to perform the operation corresponding to the target function control in response to the second operation, thereby realizing remote control of at least one device.

[0086] In this embodiment of the application, a device management platform interface is displayed. In response to a first operation in a first area of ​​the interface, at least one target device is determined. In response to a second operation in a second area of ​​the interface, the target device is remotely controlled to perform the operation corresponding to the target function control. Thus, by realizing remote control of at least one target device, the convenience of device management is effectively improved. Users can remotely control one or more other devices on one device without having to perform on-site operation on the device to be controlled.

[0087] In some embodiments, an emulator is configured on the target device. For example, when configuring a debugging environment, the emulator can be connected to an interface (such as a USB interface) on the target device, and the target device and the emulator can be configured on the same local area network. This facilitates remote control of the target device in the debugging scenario.

[0088] Different target devices correspond to different simulators.

[0089] In some embodiments, at least one target device can be determined through a device selection operation or a device input operation targeting a first device. See the description of the following embodiments for details.

[0090] refer to Figure 3 , Figure 3 This is a flowchart illustrating a device management method provided in another embodiment of this application.

[0091] like Figure 3 As shown, the equipment management methods include:

[0092] S301, Display device management platform interface, the device management platform interface includes a first area for identifying the target device and a second area containing functional controls.

[0093] The implementation principle and technical effect of S301 can be referred to the aforementioned embodiments, and will not be repeated here.

[0094] S302, In response to a device selection operation targeting the first region, determine that the device corresponding to at least one device identifier selected by the device selection operation is the target device.

[0095] In this embodiment, at least one device identifier may be displayed in the first area, or a drop-down list may be displayed in the first area. In response to a device selection operation targeting a device identifier displayed in the first area, the device corresponding to the at least one device identifier selected by the device selection operation is determined to be the target device; or, in response to a click operation targeting a drop-down list in the first area, at least one device identifier is displayed in the drop-down list, and in response to a device selection operation targeting a device identifier displayed in the drop-down list, the device corresponding to the at least one device identifier selected by the device selection operation is determined to be the target device.

[0096] In some embodiments, when an emulator is configured on the target device and different target devices correspond to different emulators, the device identifier of the target device and the debugger identifier of the debugger corresponding to the target device can be configured when the debugging environment is initialized. According to the pairwise rule, the device identifier of a target device and the debugger identifier of the debugger corresponding to the target device are recorded as an identifier group in the database. That is, the identifier group contains the device identifier and the emulator identifier corresponding to the device identifier.

[0097] Thus, in one possible implementation, the first area can display at least one group of identifiers. This allows users to understand the correspondence between the target device and the debugger through the identifier groups displayed in the first area, eliminating the need for manual searching. This saves users time when manually searching for devices and their corresponding debuggers, especially when there are many devices, thereby improving the user experience.

[0098] When at least one identifier group is displayed in the first area, in one possible implementation, S302 includes: in response to a device selection operation targeting the first area, determining that the device corresponding to the device identifier in the at least one identifier group selected by the device selection operation is the target device; and / or, in response to a device selection operation targeting the first area, determining that the device corresponding to the device identifier corresponding to the at least one debugger identifier selected by the device selection operation is the target device. Thus, the user can select the target device by selecting an identifier group, selecting a device identifier in an identifier group, selecting a device identifier in an identifier group, or selecting a debugger identifier in an identifier group, thereby improving the flexibility of device selection.

[0099] Optionally, the device identifier can be the device's Internet Protocol (IP) address. Therefore, at least one device IP address can be displayed in the first area, and in response to a device selection operation targeting device IP addresses in the first area, the device corresponding to the at least one device IP address selected by the device selection operation is determined to be the target device.

[0100] Optionally, the debugger identifier can be a debugger IP address. Therefore, at least one identifier group can be displayed in the first area, the identifier group including the device IP address and the debugger IP address corresponding to the device IP address, and in response to a device selection operation targeting the identifier group in the first area, the device corresponding to the device IP address in the at least one identifier group selected by the device selection operation can be determined as the target device.

[0101] S303, Receive a second operation targeting the function control in the second area.

[0102] S304. In response to the second operation, the remote control target device executes the operation corresponding to the target function control.

[0103] The implementation principles and technical effects of S303 and S304 can be referred to in the aforementioned embodiments, and will not be repeated here.

[0104] In this embodiment, a device management platform interface is displayed. In response to a device selection operation in the first area of ​​the interface, at least one target device is determined. In response to a second operation in the second area of ​​the interface, the target device is remotely controlled to perform the operation corresponding to the target function control. Thus, by displaying the device selection function and device control function in separate areas on the device management platform interface, remote control of at least one target device selected by the user is realized, improving the convenience of device management.

[0105] refer to Figure 4 , Figure 4 This is a flowchart illustrating a device management method provided in another embodiment of this application.

[0106] like Figure 4 As shown, the equipment management methods include:

[0107] S401, Display device management platform interface, the device management platform interface includes a first area for identifying the target device and a second area containing functional controls.

[0108] The implementation principle and technical effects of S401 can be referred to in the aforementioned embodiments, and will not be repeated here.

[0109] S402, In response to a device input operation targeting the first area, determine that the device corresponding to at least one device identifier input in the device input operation is the target device.

[0110] The first area displays at least one input box for inputting device identification.

[0111] In this embodiment, after detecting a user's device input operation in the first area, at least one device identifier entered by the user in the input box of the first area can be obtained, and the device corresponding to the at least one device identifier can be determined as the target device. Thus, the target device can be determined by inputting the device identifier.

[0112] Optionally, at least one device identifier may be displayed in the first area. The user can locate the device identifier of the device to be controlled from the device identifiers displayed in the first area and enter that device identifier in the first area.

[0113] Optionally, at least one identifier group is displayed in the first area. The user can locate the device identifier of the device to be controlled in the device group displayed in the first area and enter that device identifier in the first area. The meaning and content of the identifier group are as described in the foregoing embodiments and will not be repeated here.

[0114] Optionally, the device identifier is the device IP address.

[0115] S403, Receive a second operation targeting the function control in the second area.

[0116] S404. In response to the second operation, an operation page is displayed. The operation page includes multiple second controls, including a power-on control and a power-off control.

[0117] The implementation principles and technical effects of S403 and S404 can be referred to the aforementioned embodiments, and will not be repeated here.

[0118] In this embodiment, a device management platform interface is displayed. In response to a device input operation in the first area of ​​the interface, at least one target device is identified. In response to a second operation in the second area of ​​the interface, the target device is remotely controlled to perform the operation corresponding to the target function control. Thus, the device input function and device control function are displayed in separate areas on the device management platform interface, enabling remote control of the device corresponding to at least one device identifier input by the user, thereby improving the convenience of device management.

[0119] refer to Figure 5 , Figure 5 This is a flowchart illustrating a device management method provided in another embodiment of this application.

[0120] like Figure 5 As shown, the equipment management methods include:

[0121] S501, Display device management platform interface, the device management platform interface includes a first area for identifying the target device and a second area containing functional controls.

[0122] S502, in response to a first operation toward a first region, at least one target device is identified.

[0123] The implementation principles and technical effects of S501 and S502 can be referred to in the aforementioned embodiments, and will not be repeated here.

[0124] S503, Receive a second operation targeting the function control in the second area.

[0125] S504. In response to the second operation, an operation page is displayed. The operation page includes multiple second controls, including a power-on control and a power-off control.

[0126] The second area includes a first control that indicates the completion of device selection, and the target function control is this first control.

[0127] The operation page is used by users to remotely control the target device. The power-on control instructs the user to power on the device, and the power-off control instructs the user to power off the device.

[0128] In this embodiment, after identifying at least one target device, the user can perform a second operation on the first control in the second area to confirm that the device selection is complete. Upon receiving the user's second operation, an operation page is displayed in response to the second operation, allowing the user to remotely control the target device on the operation page. The second operation on the first control is, for example, a click operation on the first control.

[0129] In one possible implementation, the first operation is a device selection operation. In response to the device selection operation targeting the first area, the device corresponding to at least one device identifier selected by the device selection operation is determined to be the target device. A second operation targeting the first control in the second area is then received, and in response to the second operation, an operation page is displayed. For example, from the user's perspective, the user can select the device identifier of the target device in the first area, and then click the virtual button to complete the device selection in the second area to enter the operation page for remotely operating the target device.

[0130] S505. In response to a click operation on a target second control among multiple second controls, remotely control the target device to perform the operation corresponding to the target second control.

[0131] The target second control is one or more controls among a plurality of second controls.

[0132] In this embodiment, after displaying the operation page, multiple second controls are shown on the operation page, and the user can click on one or more of these second controls. If a user click on a target second control is received, in response to the click, the target device is remotely controlled to perform the operation corresponding to the target second control based on the device identifier of the target device.

[0133] Since the second control includes a power-on control and a power-off control, the S505 can include the following various situations:

[0134] In one possible implementation, the target device is remotely powered on in response to a click operation on the power-on control among multiple second controls. This achieves remote control of the target device's power-on.

[0135] In this system, when the target device is powered off but connected to a power source, its power-on module can receive a power-on command from the current device (the user's device). After the user selects the target device and enters the remote control interface, if the system detects a click on the power-on control, it sends a power-on command to the target device based on its device identifier (such as its IP address). Upon receiving this command, the target device performs the power-on operation, thus enabling remote power-on of the target device.

[0136] In another possible implementation, considering that the target device may be online or offline, upon receiving a click operation on the power-on control, the system can determine the target device's status in response to the click operation. If the target device is online, it can be remotely restarted; if it is offline, it can be remotely powered on. Thus, not only can the target device be remotely powered on, but it can also be remotely restarted.

[0137] In another possible implementation, the target device is remotely powered off in response to a click operation on the power-off control among multiple second controls. This achieves remote control of the target device's power-off.

[0138] In this system, after the user selects the target device and enters the operation interface for remote control, if the system detects that the user clicks on the power-on control on the interface, it sends a shutdown command to the target device based on the device identifier (such as the target device's IP address). Upon receiving the shutdown command, the target device executes the shutdown operation. This achieves remote shutdown of the target device.

[0139] In some embodiments, the plurality of second controls further include a status viewing control, which is used to indicate the status of the target device. The status of the target device includes online status and / or offline status. In one possible implementation, S505 includes: displaying the status of the target device in response to a click operation on the status viewing control among the plurality of second controls.

[0140] In this embodiment, upon receiving a click operation on the status viewing control, a status viewing request can be sent to the target device in response to the click operation. If a response message is received from the target device, the target device is displayed as online; otherwise, the target device is displayed as offline. Alternatively, a communication connection establishment request can be sent to the target device in response to the click operation on the status viewing control. If a response message is received from the target device, the target device is displayed as online; otherwise, the target device is displayed as offline.

[0141] In this embodiment, in response to confirming the completion of device selection on the device management platform interface, an operation page is displayed. The second controls on the operation page include a power-on control and a power-off control. In response to a click operation on a target second control, the target device is remotely controlled to perform the operation corresponding to the target second control. Thus, remote control of device power-on and power-off operations is achieved, effectively improving the convenience of device management.

[0142] refer to Figure 6 , Figure 6 This is a flowchart illustrating a device management method provided in another embodiment of this application.

[0143] like Figure 6 As shown, the equipment management methods include:

[0144] S601, Display device management platform interface, the device management platform interface includes a first area for identifying the target device and a second area containing functional controls.

[0145] S602, in response to a first operation toward a first region, identify at least one target device.

[0146] The implementation principles and technical effects of S601 and S602 can be referred to in the aforementioned embodiments, and will not be repeated here.

[0147] S603, Receive a second operation targeting a function control in the second area.

[0148] S604. In response to the second operation, a remote connection page is displayed, which is used to enter user account information and user password.

[0149] The second area includes a third control for submitting the target device, and the target functional control is this third control.

[0150] The remote connection page is the operation page after the current device and the target device have successfully established a remote control connection. In fact, it is the login page of the target device after the current device and the target device are connected.

[0151] In this embodiment, after identifying at least one target device, the user can perform a second operation on the third control in the second area to submit the device identifier of the target device and trigger a request to establish a remote control connection with the target device. The current device responds to the second operation, establishes a remote control connection with the target device, and displays the remote control connection page after the connection is successfully established.

[0152] In one possible implementation, the first operation is a device input operation. In response to the device input operation targeting the first area, the device corresponding to at least one device identifier entered in the device input operation is determined to be the target device. A second operation targeting a third control in the second area is then received. In response to the second operation, a remote connection page is displayed. For example, a user can enter the device identifier of the target device in the first area, and then click the virtual button to submit device information in the second area, triggering a request to remotely control the target device and entering the target device's login page, i.e., the remote connection page.

[0153] S605: In response to the user's input of user account information and user password, remotely log in to the target device.

[0154] In this embodiment, the user's account information and password entered by the user on the remote connection page are obtained. The target device is then remotely controlled to verify the user's authorization based on this information. If the verification is successful, the user logs into the target device, allowing them to further remotely operate it. Thus, remote login to the target device is achieved through interaction between the user and the device management platform interface.

[0155] In some embodiments, in a device commissioning scenario, the device management method further includes:

[0156] S606. After remotely logging into the target device, debug the target device.

[0157] In this embodiment, a debugger is configured on the target device, and the specific configuration process can be referred to the aforementioned embodiment. After remotely logging into the target device, the debugger on the target device can be remotely controlled to debug the target device. Thus, by submitting the device identifier of the target device, the user can establish a remote control connection between the current device and the target device, remotely log into the target device, and debug the target device without requiring the user to perform on-site debugging. This improves the convenience of debugging the target device, especially when there are a large number of devices requiring debugging, enabling remote debugging of batch devices, effectively saving user time and improving the convenience and efficiency of debugging.

[0158] In one possible implementation, an application for debugging the target device is deployed on the debugger. Therefore, after remotely logging into the target device, the user can remotely select the corresponding application on the debugger configured on the target device. In response to the selection of the application, debugging of the target device is initiated through the selected application. For example, after a successful remote control connection between the current device and the target device, the user can operate the target device from the current device, open the file directory corresponding to the debugger on the target device, locate the application for debugging the target device in that directory, select the application, and click "run" to initiate debugging of the target device through that application.

[0159] Optionally, debugging the target device includes JTAG debugging or EJTAG debugging. This enables remote JTAG or EJTAG debugging of the target device, improving the convenience of such debugging.

[0160] In this embodiment, in response to submitting an operation for the target device on the device management platform interface, a remote communication connection is established with the target device, and a remote connection page is accessed. On the remote connection page, the target device can be controlled to perform login and debugging operations. This enables remote control of device login and debugging operations, especially when there are a large number of devices, allowing for the login and debugging of batches of devices, effectively improving the convenience of device management.

[0161] The following are embodiments of the apparatus described in this application, which can be used to execute the corresponding method embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the corresponding method embodiments of this application.

[0162] refer to Figure 7 , Figure 7 This is a schematic diagram of the structure of a device management apparatus provided in an embodiment of this application.

[0163] like Figure 7 As shown, the device management device 700 provided in this embodiment includes:

[0164] Display module 701 is used to display the device management platform interface, which includes a first area for identifying the target device and a second area containing functional controls.

[0165] The determination module 702 is configured to determine at least one target device in response to a first operation toward a first region;

[0166] The receiving module 703 is used to receive a second operation targeting a function control in the second area;

[0167] The control module 704 is used to remotely control the target device to perform the operation corresponding to the target function control in response to the second operation.

[0168] In one feasible implementation, the first area is used to display device identifiers, and the determining module 702 is specifically used to: in response to a device selection operation targeting the first area, determine that the device corresponding to at least one device identifier selected by the device selection operation is the target device.

[0169] In one feasible implementation, the first area is used to input device identifiers, and the determining module 702 is specifically used to: in response to a device input operation targeting the first area, determine that the device corresponding to at least one device identifier input in the device input operation is the target device.

[0170] In one feasible implementation, the functional control includes a first control for indicating the completion of device selection, the target functional control being the first control, and the control module 704 is specifically used for: responding to a second operation, displaying an operation page, the operation page including multiple second controls, the second controls including a power-on control and a power-off control; and responding to a click operation on a target second control among the multiple second controls, remotely controlling the target device to perform the operation corresponding to the target second control.

[0171] In one feasible implementation, the target second control is a power-on control, and the control module 704 is specifically used to: determine the status of the target device in response to a click operation on the power-on control; if the target device is online, remotely control the target device to restart.

[0172] In one feasible implementation, the second control also includes a status viewing control, and the control module 704 is further configured to: display the status of the target device in response to a click operation on the status viewing control, the status including online status and / or offline status.

[0173] In one feasible implementation, the functional control includes a third control for submitting to the target device, the target functional control being the third control, and the control module 704 is specifically used to: in response to the second operation, display a remote connection page, the remote connection page being used to input user account information and user password; and in response to the user's input of user account information and user password, remotely log in to the target device.

[0174] In one feasible implementation, the control module 704 is also used to: debug the target device after remotely logging into the target device.

[0175] In one feasible implementation, the control module 704 is further configured to: in response to the selection operation of the corresponding application, enable JTAG debugging or EJTAG debugging of the target device through the application corresponding to the selection operation.

[0176] It is worth noting that the device management apparatus provided in the above embodiments can be used to execute each step in the device management method provided in any of the above embodiments. The specific implementation methods and technical effects are similar, and will not be repeated here.

[0177] The device embodiments provided in this application are merely illustrative, and the module division is only a logical functional division. In actual implementation, there may be other division methods. For example, multiple modules may be combined or integrated into another system. The coupling between the modules can be achieved through some interfaces, which are usually electrical communication interfaces, but mechanical interfaces or other forms of interfaces are also possible. Therefore, the modules described as separate components may or may not be physically separated; they may be located in one place or distributed in different locations on the same or different devices.

[0178] refer to Figure 8 , Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 8 As shown, the electronic device 800 may include at least one processor 801 and a memory 802. Figure 8 The example shown is an electronic device using a processor.

[0179] The memory 802 is used to store the program of the processor 801. Specifically, the program may include program code, which includes computer operation instructions.

[0180] The memory 802 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0181] The processor 801 is configured to execute computer programs stored in the memory 802 to implement the steps of the device management methods in the above method embodiments.

[0182] The processor 801 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of this application.

[0183] Optionally, the memory 802 can be either independent or integrated with the processor 801. When the memory 802 is a device independent of the processor 801, the electronic device 800 may further include a bus 803 for connecting the processor 801 and the memory 802. The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, or an extended industry standard architecture (EISA) bus, etc. Buses can be classified as address buses, data buses, control buses, etc., but this does not mean that there is only one bus or one type of bus.

[0184] Optionally, in a specific implementation, if the memory 802 and the processor 801 are integrated on a single chip, the memory 802 and the processor 801 can communicate through an internal interface.

[0185] This application also provides a computer-readable storage medium, which may include various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. Specifically, the computer-readable storage medium stores a computer program. When at least one processor of the electronic device executes the computer program, the electronic device performs each step of the device management method provided in the above-described embodiments.

[0186] This application also provides a computer program product comprising a computer program stored in a readable storage medium. At least one processor of an electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to cause the electronic device to perform the various steps of the device management methods provided in the various embodiments described above.

[0187] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0188] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for managing equipment, characterized in that, The device management method, applicable to devices equipped with a device management platform, includes: during initialization of the debugging environment, recording the device identifier of the target device and the debugger identifier of the corresponding debugger in a database as an identifier group according to a pairwise rule, wherein the device identifier is the Internet Protocol (IP) address of the device, the debugger identifier is the debugger IP address, and the target device and the debugger are configured to be on the same local area network; displaying a device management platform interface, the device management platform interface including a first area for identifying target devices and a second area containing functional controls; the first area is further used to display at least one of the identifier groups; in response to a first operation targeting the first area, identifying at least two target devices; and receiving a second operation targeting target functional controls in the second area. In response to the second operation, the at least two target devices are remotely controlled to perform the operation corresponding to the target function control; The functional control includes a third control for submitting the target device, and the target functional control is the third control. The step of remotely controlling the at least two target devices to perform the operation corresponding to the target functional control in response to the second operation includes: displaying a remote connection page in response to the second operation, the remote connection page being used to input user account information and user password; remotely logging into the target device in response to the user's input user account information and user password; and after remotely logging into the target device, remotely controlling the debugger on the target device to debug the target device.

2. The equipment management method according to claim 1, characterized in that, The response to the first operation toward the first region, identifying at least two target devices, includes: In response to a device selection operation targeting the first region, the device corresponding to at least two device identifiers selected by the device selection operation is determined to be the target device.

3. The equipment management method according to claim 1, characterized in that, The first area is used to input device identification, and the first operation in response to the first area, determining at least two target devices, includes: In response to a device input operation targeting the first region, the device corresponding to at least two device identifiers input in the device input operation is determined to be the target device.

4. The equipment management method according to any one of claims 1 to 3, characterized in that, The functional control includes a first control for indicating completion of device selection, the target functional control being the first control, and the step of remotely controlling the target device to perform the operation corresponding to the target functional control in response to the second operation includes: In response to the second operation, an operation page is displayed, the operation page including a plurality of second controls, including a power-on control and a power-off control; In response to a click operation on a target second control among the plurality of second controls, the target device is remotely controlled to perform the operation corresponding to the target second control.

5. The equipment management method according to claim 4, characterized in that, The target second control is a power-on control. The step of remotely controlling at least two target devices to perform the operation corresponding to the target second control in response to a click operation on the target second control among the plurality of second controls includes: In response to a click operation on the power-on control, the status of the at least two target devices is determined; If at least two target devices are in an online state, then remotely control at least two target devices to restart.

6. The equipment management method according to claim 4, characterized in that, The second control also includes a status viewing control, and further includes: In response to a click operation on the status viewing control, the status of the target device is displayed, including online status and / or offline status.

7. The equipment management method according to claim 1, characterized in that, The debugging of the target device includes: In response to the selection of a corresponding application, JTAG debugging or EJTAG debugging of the target device is initiated through the application corresponding to the selection operation.

8. An equipment management device, characterized in that, The device management device is applied to equipment equipped with a device management platform, and includes: The display module is used to display the device management platform interface, which includes a first area for identifying the target device and a second area containing functional controls. During the initialization of the debugging environment, the device identifier of the target device and the debugger identifier of the corresponding debugger are recorded as identifier groups in the database according to a pairwise rule. The device identifier is the device's Internet Protocol (IP) address, and the debugger identifier is the debugger's IP address. The target device and the debugger are configured to be on the same local area network. The first area is also used to display at least one of the identifier groups. The determination module is configured to determine at least two target devices in response to a first operation directed toward the first region; A receiving module is configured to receive a second operation directed to a target functional control in the second region, wherein the functional control includes a third control for submitting the target device, and the target functional control is the third control; The control module is configured to, in response to the second operation, display a remote connection page for inputting user account information and user password; in response to the user's input of user account information and user password, remotely log in to the target device; and after remotely logging in to the target device, remotely control the debugger on the target device to debug the target device.

9. An electronic device, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the device management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the device management method as described in any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the device management method as described in any one of claims 1 to 7.

Images