Method for accessing embedded device and device management network
Through virtual terminal and pre-configured interface information, the user terminal automatically jumps and connects to embedded devices and displays the access page of the embedded devices, solving the problems of low access efficiency and resource preemption of embedded devices, and improving access efficiency and management simplicity.
Patent Information
- Application Number
- CN202310575760.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-22
- Publication Date
- 2024-11-22
AI Technical Summary
In the prior art, user terminals have low efficiency in accessing embedded devices, and it is easy to cause problems such as user overriding the use of the user and resource preemption when connecting through the server.
Accessing the target embedded device through a virtual terminal, automatically jumping and connecting using pre-configured interface information, displaying the access page to the user terminal, avoiding users directly logging into the server, and achieving efficient access and permission management of the embedded device by the user terminal.
It effectively shortens the process of users accessing embedded devices, improves access efficiency, avoids resource preemption and override of rights between user terminals, and simplifies device management.
Smart Images

Figure CN119011643A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of embedded devices, and in particular to a method for accessing embedded devices and device management networking. Background Art
[0002] Embedded devices are special computer systems with strict requirements on functions, reliability, cost, size and power consumption, and are widely used in production and life. With the continuous development of hardware technology, embedded devices are becoming more and more diversified.
[0003] The connection of embedded devices is often very complicated and requires professionals with professional skills and knowledge. For embedded devices that only support serial port connection, the traditional device management method is to place all devices in the laboratory and debug them in the laboratory through computers to control the connection of embedded devices. Another device management method is to connect the embedded device to the server through the serial port, and the user end can access the required embedded device by accessing the server. It can be seen that using a serial port to connect embedded devices is inconvenient. If connected through a server, a serial port connection tool needs to be deployed on the server to configure each embedded device. Moreover, the server is limited by the number of serial ports and cannot connect a large number of embedded devices.
[0004] How to improve the efficiency of user terminals accessing embedded devices is a technical problem to be solved by this application. Summary of the invention
[0005] The purpose of the embodiments of the present application is to provide a method for accessing an embedded device and a device management network to solve the problem of low efficiency of user terminals accessing embedded devices.
[0006] In a first aspect, a method for accessing an embedded device is provided, which is applied to a device management system, comprising:
[0007] Receiving a target connection request from a user terminal, wherein the target connection request carries information of a target embedded device to be accessed;
[0008] According to the pre-configured interface information of the target embedded device, accessing the target server to which the target embedded device is connected in communication through a virtual terminal;
[0009] Calling a connection tool instruction of the target server to connect the virtual terminal to the target embedded device;
[0010] The access page of the target embedded device is obtained through the virtual terminal, and the access page is displayed to the user terminal.
[0011] In a second aspect, a device for accessing an embedded device is provided, which is applied to a device management system, and includes:
[0012] A receiving module receives a target connection request from a user terminal, wherein the target connection request carries information of a target embedded device to be accessed;
[0013] An access module, which accesses a target server to which the target embedded device is connected in communication through a virtual terminal according to pre-configured interface information of the target embedded device;
[0014] A connection module, calling a connection tool instruction of the target server to connect the virtual terminal with the target embedded device;
[0015] A display module obtains the access page of the target embedded device through the virtual terminal and displays the access page to the user terminal.
[0016] In a third aspect, a device management network is provided, including:
[0017] A device management system, configured to execute the steps of the method according to the first aspect;
[0018] At least one user terminal in communication with the device management system;
[0019] at least one server in communication with the device management system;
[0020] A plurality of embedded devices are connected to the device management system through a server for communication.
[0021] In a fourth aspect, an electronic device is provided, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method of the first aspect when executed by the processor.
[0022] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method of the first aspect are implemented.
[0023] The scheme provided by the embodiment of the present application is applied to the device management system. First, a target connection request of a user terminal is received, and the target connection request carries the information of the target embedded device to be accessed. Then, according to the pre-configured interface information of the target embedded device, the target server to which the target embedded device is connected is accessed through a virtual terminal. Subsequently, the connection tool instruction of the target server is called to connect the virtual terminal to the target embedded device. Finally, the access page of the target embedded device is obtained through the virtual terminal, and the access page is displayed to the user terminal. In this scheme, based on the target embedded device specified by the target connection request of the user terminal, the access is performed with the virtual terminal according to the pre-configured interface information, and the access page is displayed to the user terminal, which can realize automatic jump connection based on the virtual terminal, effectively shorten the process of user access to the target embedded device, and improve the efficiency of user terminal access to the embedded device. In addition, this scheme realizes the access of the user terminal to the embedded device by displaying the access page to the user terminal, avoiding the user terminal directly logging into the server, which may cause the user to use multiple embedded devices under the server beyond his authority, thereby avoiding the problem of multiple user terminals logging into the same server grabbing embedded device resources, and effectively improving the efficiency of user terminal access to embedded devices. BRIEF DESCRIPTION OF THE DRAWINGS
[0024] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0025] Figure 1 It is a connection diagram of an embedded device management system.
[0026] Figure 2a It is a structural diagram of a device management system provided by an embodiment of the present application.
[0027] Figure 2b This is one of the flowcharts of a method for accessing an embedded device according to an embodiment of the present application.
[0028] Figure 3a This is the second flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0029] Figure 3b It is a flowchart of a user terminal accessing a target embedded device through a device management system according to an embodiment of the present application.
[0030] Figure 4a This is the third flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0031] Figure 4b It is a flowchart of a manager accessing a device management system according to an embodiment of the present application.
[0032] Figure 5 This is the fourth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0033] Figure 6a This is the fifth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0034] Figure 6b It is a flowchart of a user terminal accessing a device management system to perform power control in one embodiment of the present application.
[0035] Figure 7 This is the sixth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0036] Figure 8 This is the seventh flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0037] Fig. 9 This is the eighth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0038] Fig.10 It is a structural diagram of an apparatus for accessing an embedded device according to an embodiment of the present application.
[0039] Fig.11 This is one of the structural diagrams of a device management network in an embodiment of the present application.
[0040] Fig.12 This is the second structural diagram of a device management network in an embodiment of the present application. DETAILED DESCRIPTION
[0041] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application. The numbering of the drawings in this application is only used to distinguish the various steps in the scheme, and is not used to limit the execution order of the various steps. The specific execution order is subject to the description in the specification.
[0042] In the field of embedded devices, for embedded devices that only support serial port connection, an optional device management method is to place all devices in the laboratory and debug them in the laboratory through a PC (Personal Computer). Alternatively, the embedded device is connected to the server through the serial port, and the user terminal logs in to the server to access the embedded device connected to the server.
[0043] In actual application scenarios, different user terminals can access different embedded devices through the server. For multiple embedded devices, you can use a serial port tool to connect the embedded device to the server, and the user terminal can access the embedded device connected to the server by logging in to the server. Due to the limitation of the serial port connection method, the number of embedded devices connected to a server is limited. Users need to log in to the server connected to the embedded device to access the required embedded device.
[0044] by Figure 1 Taking the connection mode of the embedded device management system shown as an example, user A can access embedded device A and embedded device B connected to server A through a serial port tool by logging in to server A. Correspondingly, user B can access embedded device C and embedded device D by logging in to server B, and user C can access embedded device E and embedded device F by logging in to server C.
[0045] exist Figure 1 In the scenario shown, if user A needs to access embedded device C or embedded device D, user A needs to log in to server B again and then access the connected embedded device. However, embedded device C or embedded device D may be accessed by user B. The embedded device accessed by user B cannot be accessed by user A at the same time, and serial port printing anomalies may occur. It is also difficult for user A to know in advance which embedded device user B is occupying, resulting in low connection and access efficiency.
[0046] Since users cannot know which embedded devices are occupied, Figure 1 In the scenario shown, it is also possible that user A, user B, and user C all want to connect to and access embedded device C. In this case, only one user can successfully connect to and access embedded device C, which may cause multiple users to compete for embedded device resources.
[0047] Moreover, if user B connects to access embedded device C, other users cannot connect to access embedded device C until user B actively disconnects. In actual applications, if user B does not disconnect in time after using embedded device C, the resources of embedded device C will be wasted.
[0048] In addition, the operation of using multiple serial ports to connect embedded devices is cumbersome and the connection control is complicated. When different users need to use different embedded devices, the embedded devices need to be reconfigured, and connection and access cannot be achieved conveniently and quickly.
[0049] In one application scenario, assume that user B has the right to access embedded device C but not embedded device D. Both embedded device C and embedded device D are connected to server B. As long as user B logs in to server B, he has the right to access all embedded devices connected to the server. This may result in user B unauthorized access to embedded device D. This shows that there is a problem in this device management system that it is difficult to manage the connection access rights of embedded devices.
[0050] In order to solve the problems existing in the prior art, the present application embodiment provides a method for accessing an embedded device, which is applied to a device management system. As an example, the structure of the device management system can be as follows: Figure 2a As shown. During the application process, multiple user devices can connect to the device management system to access the embedded device. Figure 2a The illustrated scenario shows three user devices, namely user A, user B and user C. In actual applications, a greater or lesser number of user terminals may be communicatively connected to the device management system.
[0051] The device management system can be connected to multiple embedded devices through a server. In practical applications, the server can be a serial port server, a jump server or other types of servers.
[0052] like Figure 2a As shown, the device management system can be connected to one or more embedded devices through a serial port server via a serial port connection. Figure 2a The serial device server A in the example connects embedded device A and embedded device B through the serial port. The serial device server B connects embedded device C through the serial port.
[0053] Alternatively, the device management system can be connected to one or more embedded devices through a network connection via a jump server. Figure 2a The jump board A in the example connects embedded device D and embedded device E through the network. The jump board B connects embedded device F through the network.
[0054] In addition, Figure 2aIn the system shown, the device management system can also control the power supply of each embedded device through the PDU (Power Distribution Unit) power socket. Among them, PDU is a socket device, and other types of power supplies can also be used to power each embedded device in actual applications. Alternatively, multiple power supplies can be used to power multiple embedded devices respectively.
[0055] The method provided in the embodiment of the present application is as follows Figure 2b As shown, it is applied to the equipment management system and includes the following steps:
[0056] S21: Receive a target connection request from a user terminal, where the target connection request carries information about a target embedded device to be accessed.
[0057] When a user terminal needs to access an embedded device, it can send a target connection request containing information about the target embedded device to the device management system. The device management system can parse the target connection request to determine which embedded device the user terminal wants to access. The target connection request can also include information about the user terminal itself so that the device management system can provide feedback to the user terminal.
[0058] S22: Accessing a target server to which the target embedded device is communicatively connected through a virtual terminal according to the pre-configured interface information of the target embedded device.
[0059] The device management system is pre-configured with interface information of each embedded device, and the interface information represents the connection relationship of the corresponding embedded device in the device management system. In this step, the target server connected to the target embedded device is determined based on the pre-configured interface information of the target embedded device, and the target server is accessed through a virtual terminal to access the target embedded device. Specifically, if the information of the target embedded device carries information of the connected server, the target embedded device can be directly accessed through the server based on the information.
[0060] Among them, the device management system can pre-store the pre-configured interface information of the embedded device through a database or other forms, so that after determining the target embedded device that the user terminal wants to connect to, it can efficiently obtain the pre-configured interface information of the target embedded device by querying the database, and then connect to the target server through the virtual terminal.
[0061] S23: calling the connection tool instruction of the target server to connect the virtual terminal with the target embedded device.
[0062] After accessing the target server through the virtual terminal, the connection tool command of the target server is called to further connect the virtual terminal to the target embedded device. Since the embedded device is connected to the server through the virtual terminal, the access interface is then displayed to the user terminal to achieve access, so the user terminal itself does not need to log in to the serial port service, and there is no need to frequently change the configuration of the embedded device. In the scenario where different users access the embedded device, since there is no need to change the configuration of the embedded device, the efficiency of the user terminal accessing the embedded device can be improved.
[0063] S24: Acquire an access page of the target embedded device through the virtual terminal, and display the access page to the user terminal.
[0064] After the device management system successfully accesses the target embedded device through the server, the device management system can obtain the access page of the target embedded device from the server. The device management system displays the access page to the user terminal, so that the user can see the access page of the target embedded device through the user terminal and perform the required operation.
[0065] This solution uses a virtual terminal to connect to an embedded device through a server, and enables the user terminal to access the embedded device by displaying an access page to the user terminal, avoiding the problem of the user directly logging into the server and causing the user to use multiple embedded devices under the server without authorization. It also avoids the problem of multiple user terminals logging into the same server competing for embedded device resources, effectively improving the efficiency of user terminals accessing embedded devices.
[0066] Based on the solution provided in the above embodiment, optionally, Figure 3a As shown, before the above step S21, it also includes:
[0067] S31: Acquire information of the user terminal and access status information corresponding to a plurality of embedded devices, wherein the plurality of embedded devices are communicatively connected to a device management system via a server, and the access status information indicates whether the corresponding embedded device is in an accessed state.
[0068] In this step, information of the user terminal and access status information corresponding to a plurality of embedded devices are obtained, wherein the plurality of embedded devices are communicatively connected to a device management system via a server, and the access status information indicates whether the corresponding embedded device is in an accessed state.
[0069] The information of the user terminal may specifically include hardware information of the user terminal, information of a user using the user terminal, etc. The user information may be information pre-registered by a user, or may be information pre-set by a manager in a device management system.
[0070] In this step, the information of the user terminal and the access status information corresponding to multiple embedded devices can be obtained at the same time, so that the obtained access status information can represent the access status of each embedded device at the moment when the user terminal information is obtained, which is conducive to improving the accuracy of the accessible devices determined in subsequent steps.
[0071] In this step, an embedded device corresponds to an access status information, and the access status information indicates whether the corresponding embedded device is in a state of being accessed by a user terminal. In this solution, the embedded device can be in two states during normal operation. One is the accessed state, that is, a user terminal is accessing the embedded device, and the embedded device can no longer be connected and accessed by other user terminals. The other is the unaccessed state, that is, no user terminal is accessing the embedded device, and the embedded device is in a state where it can be connected and accessed by a user terminal.
[0072] In actual applications, the access status information corresponding to the multiple embedded devices can be displayed in the form of a list, recorded and stored as an access status list for easy query. Optionally, when the user terminal information is obtained, the access status information corresponding to each embedded device is obtained accordingly, and the access status list is updated and maintained.
[0073] Alternatively, the access status information of each embedded device can be queried through each server based on a preset time period, and the access status list can be updated and maintained in real time. When the information of the user terminal is obtained, the access status list updated and maintained in advance can be directly called to obtain the access status information corresponding to multiple embedded devices.
[0074] S32: Determine an accessible device list according to the information of the user terminal and the access status information corresponding to the plurality of embedded devices, wherein the accessible device list includes information of embedded devices that are accessible to the user terminal and are in an unaccessed state.
[0075] In this step, embedded devices accessible to the user terminal are screened from multiple embedded devices based on the information of the user terminal obtained in the above step, and embedded devices in a non-accessed state are screened from multiple embedded devices based on the access status information obtained in the above step.
[0076] In the actual execution steps, embedded devices that are not accessed can be screened out, and then embedded devices accessible to the user terminal can be selected from these unaccessed embedded devices to generate an accessible device list. Alternatively, embedded devices accessible to the user terminal can be screened out first, and then unaccessed embedded devices can be selected from accessible embedded devices to generate an accessible device list. Unaccessed embedded devices and embedded devices accessible to the user terminal can also be screened separately, and then the accessible device list can be determined by calculating the intersection.
[0077] The embedded devices accessible to the user terminal may specifically indicate the access conditions of which embedded devices are satisfied by the hardware functions of the user terminal, or may also indicate the embedded devices that the user corresponding to the user terminal has the authority to access.
[0078] The information of the embedded devices included in the accessible device list may specifically be the identification of the embedded devices, which indicates which embedded devices are in a state accessible to the user terminal. The information of the embedded devices may also include information of the server to which the embedded devices are connected, relevant configuration information of the embedded devices, and the like.
[0079] After the accessible device list is generated, the accessible device list may be sent to a user terminal so that the user can view each accessible embedded device through the user terminal.
[0080] S33: Send the accessible device list to the user terminal, so that the user terminal can select the target embedded device to be accessed from the accessible device list.
[0081] By sending the accessible device list to the user terminal, it is convenient for the user terminal to select the target embedded device that needs to be connected and accessed according to the above-mentioned access device list, and then the user terminal sends a target connection request carrying the information of the target embedded device. Optionally, the information of the target embedded device carried in the target connection request can be the information related to the target embedded device in the above-mentioned access device list, so that the device management system can parse the target embedded device requested by the user terminal according to the target connection request.
[0082] The solution provided by the embodiment of the present application can effectively improve the efficiency of user terminals accessing embedded devices. By obtaining the access status information of each embedded device, the list of devices accessible to the user terminal can be determined, so that the user can quickly determine the target embedded device that can be used currently, avoiding multiple users from occupying the same embedded device, thereby improving the efficiency of user terminals accessing embedded devices.
[0083] Subsequently, after determining the target embedded device selected by the user terminal, it is possible to determine which target server the target embedded device that the user needs to access is connected to based on the information of the target embedded device, so that in subsequent steps, the target embedded device can be connected to the above target embedded device through the target server to achieve access to the target embedded device.
[0084] Specifically, see Figure 3b First, the user terminal accesses the front end of the device management system, and then determines the accessible device list of the user terminal through the device management server and the database. Then, the user terminal selects the target embedded device to be accessed from the accessible device list. The device management system can determine the target server connected to the target embedded device based on the information of the target embedded device, or the device management system can query the pre-stored information based on the information of the target embedded device to determine the target server connected to the target embedded device.
[0085] Furthermore, the target server is accessed through the virtual terminal and the connection tool instruction of the target server is called, so that the virtual terminal is connected to the target embedded device to obtain the access page of the target embedded device.
[0086] The virtual terminal can be, for example, a Web Terminal. In actual applications, other virtual terminals can also be used to perform access. After obtaining the information of the target embedded device that the user terminal needs to access, the target server connected to the target embedded device is accessed through the human-computer interaction terminal (i.e., the virtual terminal). Figure 3b The server A shown in FIG. Then, the target embedded device is accessed through the server A, that is, Figure 3b Device A shown in FIG.
[0087] Specifically, the front end of the device management system can send an HTTP request to the back end of the device management system, and the back end queries the permission list in the database, returns the embedded devices that are accessible to the user terminal and are not accessed to the front end, and displays them to the user terminal in a table. The user terminal clicks on the target embedded device to be connected in the table. Based on the user's click operation, it automatically jumps to the web-simulated human-computer interaction terminal, which automatically accesses the server where the device is located according to the device information configured in the database, and then automatically connects to the target embedded device on the server through the command of the serial port tool. The process is fully automated, and the user only needs to click to connect the device to access the embedded device, which can easily and quickly achieve access to the target embedded device.
[0088] Subsequently, the access page of the target embedded device is displayed to the user terminal, so that the user terminal can access the target embedded device through the access page without connecting to the target embedded device. Furthermore, the user terminal can perform operations on the access page, and then the device management system performs corresponding operations on the target embedded device according to the user operation.
[0089] Through the solution provided by the embodiment of the present application, when any user terminal requests to access the target embedded device, the target embedded device selected by the user terminal is accessed as a virtual terminal, and the user terminal itself does not need to log in and connect to the server. On the one hand, the configuration of the embedded device is simpler, and there is no need to re-execute the configuration every time a connection is made. On the other hand, it avoids the problem that the user terminal may unauthorizedly use other embedded devices of the server after connecting to the server, and can effectively realize the management of the user terminal's access rights to the embedded device.
[0090] After the target embedded device is implemented, the serial port usage on the server can be queried regularly, and the device occupancy information can be sent to the device management system. After the device management system obtains that the target embedded device is accessed by the user terminal, it automatically changes the access status of the device to "accessed status". As a result, other users can no longer access the embedded device during the process of the embedded device being occupied, avoiding the snatch of embedded device resources. Until the user terminal closes the access interface of the target embedded device, the target embedded device resources are released, and the device management system records the status of the target embedded device as "not accessed status". After that, other users can request to access the embedded device.
[0091] Optional, see Figure 3b In this example, the human-computer interaction terminal can also write or read terminal log files to the device management server. The terminal log files may include, for example, the access records of the human-computer interaction terminal to the server and embedded devices, the records of the access interface displayed to the user terminal, the records of the user terminal performing operations on the access interface, the records of the human-computer interaction terminal performing operations on the embedded device according to the user operation, etc. The user terminal can retrieve the terminal log file from the device management server through the human-computer interaction terminal to query the historical operation records.
[0092] In addition, each server can periodically report the occupancy status of each embedded device connected to it to the database of the device management system, so that the database records the real-time access status information of each embedded device, so that when a new user terminal accesses the device management system, it can query the database to find out which embedded devices are in an unaccessed state, which is conducive to quickly generating a list of accessible devices for the user terminal.
[0093] Based on the solution provided in the above embodiment, optionally, Figure 4a As shown, before the above step S32, it also includes:
[0094] S41: configuring permission information corresponding to the user terminal, wherein the permission information represents access rights of the user terminal to the multiple embedded devices.
[0095] In actual applications, the administrator can pre-configure the access rights of the user terminal to the embedded device in the device management system. If there are multiple embedded devices, each embedded device can be configured separately, or the multiple embedded devices can be classified into different levels, and then the configuration can be performed on the embedded devices of each level in batches.
[0096] For example, in one application scenario, an embedded device and a server can be connected via a serial port. The administrator can add device information and server information connected to the device through the background interface, which may include the device name, device type, address of the server where the device is located, serial port number of the device, etc. The administrator can then add a list of users who can access the device, and the added users will have the right to access the embedded device with one click.
[0097] Optional, such as Figure 4b As shown, first, the administrator accesses the background management interface of the device management system. Then, the device information is added, and the added device information is the information of the embedded device for which the user terminal access rights need to be set. Next, the user rights of the device are added for the device information. Specifically, the added user rights may include which users can access the device, or the added user rights may include which users are prohibited from accessing the device. Finally, the added device information and the corresponding user rights can be stored and displayed through the device list. The administrator can modify the device information or the corresponding user rights through the device list.
[0098] Among them, access permissions can be quickly set in batches by setting the device level and the user terminal level. For example, first, corresponding level identifiers are set for multiple embedded devices, such as level one, level two, level three, etc. Then corresponding permission identifiers are set for multiple user terminals, so that the permission identifier matches the level identifier of the above embedded device. For example, the permission identifier of the user terminal can be level one, level two, level three, etc. Among them, a user terminal with a level three permission identifier can access an embedded device with a level three level identifier, a user terminal with a level two permission identifier can access embedded devices with level two and level three level identifiers, and correspondingly, a user terminal with a level one permission identifier can access embedded devices with level one, level two, and level three level identifiers, thereby realizing batch setting of access permissions. In actual use, the user terminal's access permissions to embedded devices can be flexibly adjusted by adjusting the level identifier or the permission identifier, and the access permissions can be easily maintained or changed.
[0099] Wherein, the above step S32 includes:
[0100] S42: Determine authority information corresponding to the user terminal according to the information of the user terminal.
[0101] In this step, the information of the user terminal may be queried, for example, the information of the user terminal may be queried in a device list of pre-stored access permissions to determine which embedded devices the user terminal can access.
[0102] If the permission identifier corresponding to the user terminal information is recorded in the device list pre-stored with the access rights, the permission information corresponding to the queried user terminal may include the permission identifier. Further, a comparison may be performed based on the permission identifier corresponding to the queried user terminal and the level identifier corresponding to each embedded device to determine which embedded devices the user terminal has the right to access, and generate permission information containing the information of the embedded devices that the user terminal has the right to access.
[0103] S43: Determine an accessible device list according to the permission information and the access status information corresponding to the plurality of embedded devices, wherein the accessible device list includes information of embedded devices that the user terminal has the right to access and are in an unaccessed state.
[0104] In this step, the embedded devices that the user terminal is authorized to access are determined based on the corresponding permission information of the user terminal, so that the access permission management of the user terminal to the embedded devices can be realized. The administrator can flexibly configure the access permission of the user terminal to the embedded devices, and can realize the permission management of the user terminal to access each embedded device.
[0105] Based on the solution provided in the above embodiment, optionally, Figure 5As shown, in the above step S41, configuring the permission information corresponding to the user terminal includes:
[0106] S51: receiving authority configuration information, wherein the authority configuration information includes information of a terminal to be configured and authority information to be configured.
[0107] In this example, the administrator can configure the terminal permissions in advance. The terminal to be configured can be a terminal that the administrator needs to use for daily inspection and management, or a registered user terminal. The information of the terminal to be configured includes, for example, the device name, device type, address of the server where the device is located, and the serial port number of the device.
[0108] The permission information to be configured corresponding to the information of the terminal to be configured may be, for example, a preset permission level. The permission information may be used to indicate the embedded devices that the terminal to be configured has the right to access, or may also be used to indicate the embedded devices that the terminal to be configured has no right to access.
[0109] S52: associating the information of the terminal to be configured with the permission information to be configured and storing them in a permission database through a preset permission interface.
[0110] For the permission configuration information, the permission configuration is performed through the pre-set permission interface. Specifically, the information of the terminal to be configured is associated with the permission information to be configured, and the terminal information and its corresponding permission information are stored in the permission database, so that when the terminal requests to access the embedded device, the access permission of the terminal can be queried.
[0111] Wherein, in the above step S42, determining the authority information corresponding to the user terminal according to the information of the user terminal includes:
[0112] S53: querying the authority database according to the information of the user terminal to obtain the authority information corresponding to the user terminal.
[0113] In this example, the user terminal information is queried in the authority database to obtain the authority information corresponding to the user terminal, which is used to indicate which embedded devices the user terminal has the right to access. Then, in subsequent steps, the accessible device list of the user terminal can be determined according to the authority information.
[0114] Combine the following Figure 2aThe scenario shown illustrates this example. For example, through the solution provided in the embodiment of the present application, it can be set that user A has the right to access embedded device A but has no right to access embedded device B. Based on the access rights, when user A requests access to embedded device A, the device management system accesses embedded device A through serial port server A, and displays the access interface to user A, so that user A can access embedded device A. Since user A itself has not logged in to serial port server A during the access process, it will not be connected to embedded device B, effectively preventing user A from accessing embedded device B. This avoids the situation where the user terminal can use all embedded devices connected to the server after logging in to the server, thereby solving the problem of difficulty in managing access rights for multiple embedded devices in the same server.
[0115] Based on the solution provided in the above embodiment, optionally, the device management system is also used to supply power to the multiple embedded devices.
[0116] In this example, see Figure 2a , the device management system can supply power to each embedded device through the PDU. In actual applications, managers can control the PDU through the device management system to control the power on or off of each embedded device.
[0117] Among them, Figure 6a As shown, after step S32, the following further includes:
[0118] S61: Receive a power control instruction from the user terminal, where the power control instruction carries information of an embedded device selected by the user terminal in the accessible device list and to be powered on.
[0119] See also Figure 6b In this example, the user terminal can access the front end of the device management system, and then query the database through the device management server to determine the list of devices that the user terminal can access. Then receive the power control instruction sent by the user terminal. In other words, the user terminal can perform power control on the user terminal that is accessible to itself and is not accessed. In actual applications, if an abnormality occurs in an embedded device, the power control instruction can be used to power off and power on the abnormal embedded device, so as to restart the embedded device and repair the abnormality.
[0120] Optionally, based on the list of accessible devices of the user terminal, the front end of the device management system can display virtual buttons for powering on, powering off or restarting each embedded device in the list to the user terminal. The user terminal can send a power control instruction by clicking the virtual button, thereby realizing power control of the embedded device.
[0121] S62: Execute a power control operation matching the power control instruction on the embedded device to be powered on.
[0122] After receiving the power control instruction from the user terminal, the device management system can execute the power control operation that matches the power control instruction by sending instructions. For example, power control is performed on a remote power module that matches the power control instruction, and the remote power module may include a PDU, for example. The remote power module performs power-on or power-off switch control on the embedded device that matches the power control instruction, thereby realizing power control.
[0123] Through this solution, the user terminal can remotely control the power on and off of the embedded device. When the embedded device is stuck or has other abnormal failures, it can try to recover by controlling the power on and off, without the need for the management personnel to perform the restart operation on site. It can improve the overall operation stability of the system and improve the convenience of system control.
[0124] Optionally, in order to facilitate power control, the administrator can configure the power control related parameters in advance. For example, when adding a device, the administrator adds the relevant configuration of the device power. The configuration may include parameter configurations such as the address of the PDU, the login method of the PDU, and the socket number on the PDU where the device is located. After the configuration is completed, the device management system can find and control the corresponding PDU power supply according to the configured information. The user only needs to click the power off and power on buttons in the visual interface to realize remote power control of the embedded device and restart the device.
[0125] Based on the solution provided by the above embodiment, optionally, the target connection request includes a hypertext transfer protocol request. The target connection request carries access time information corresponding to the information of the target embedded device, and the access time information includes the access start time.
[0126] Among them, HyperText Transfer Protocol (HTTP) is a network transmission protocol widely used on the Internet. In this example, the user terminal can realize remote access and control of the embedded device through HTTP protocol request.
[0127] In this example, after selecting the target embedded device to be accessed, the user terminal can also set the access time information of the target embedded device, wherein the access time information at least includes the access start time, which indicates when the user terminal starts to access the target embedded device.
[0128] Optionally, the access time information may also include the length of time of the access, such as ten minutes. Alternatively, the access time information may also include the access end time, that is, when to stop accessing the target embedded device.
[0129] Among them, Figure 7 As shown, the above step S23 includes:
[0130] S71: At the access start time specified by the access time information, calling the connection tool instruction of the target server to connect the virtual terminal with the target embedded device.
[0131] In actual applications, user terminals can make reservations for access to target embedded devices. For example, suppose user A, user B, and user C all need to access embedded device A. If there is no negotiation between the three users, they will not know when they can access embedded device A, which may lead to embedded device resource preemption or idle embedded device resources.
[0132] Through the solution provided by the embodiment of the present application, user A, user B and user C can reserve the access time period to embedded device A through access time information. For example, the access time information carried in the target connection request sent by user A includes 10:00-10:30, the access time information carried in the target connection request sent by user B includes 10:40-11:10, and the access time information carried in the target connection request sent by user C includes 12:00-12:10. Based on the access time information of user A, user B and user C, the corresponding user terminal can be allowed to access embedded device A during the corresponding period to avoid the preemption or idleness of embedded device resources.
[0133] Optionally, after the user terminal selects the target embedded device through the front end of the device management system, the device management system can query whether other users have reserved access time periods for the target embedded device. If so, the access time information reserved by other users can be displayed to the user terminal so that the user can select other time periods for access according to the existing reservation time periods. This is conducive to multiple users to orderly access the same embedded device, thereby making full and reasonable use of embedded device resources.
[0134] In practical applications, for multiple embedded devices distributed on different servers, the solution provided by the embodiment of the present application can effectively realize the management of multiple embedded devices. It is conducive to the rational allocation and use of embedded device resources to avoid resource preemption or idleness. The user terminal can efficiently access the target embedded device through this solution, and can also realize the scheduled access to the target embedded device. It can facilitate the collaborative execution of work by multiple user terminals, facilitate the reasonable arrangement of the access of each user terminal to the same embedded device, and help improve the efficiency of collaborative work between multiple user terminals.
[0135] Based on the solution provided in the above embodiment, optionally, Figure 8 As shown, the above step S31 includes:
[0136] S81: When the device management system is accessed by the user terminal, the information of the user terminal is obtained and the access status information corresponding to the multiple embedded devices respectively stored in the database is queried.
[0137] In the solution provided in the embodiment of the present application, the access status information of each embedded device is stored in a database. Figure 3b First, the user terminal accesses the front end of the device management system, and then the front end of the device management system sends a request to the back end to query the access status information corresponding to each embedded device stored in the database through the device management server. Then, the embedded devices in the unaccessed state are determined, and the embedded devices that are accessible to the user terminal and in the unaccessed state are determined according to the information of the user terminal to generate an accessible device list.
[0138] After the above step S21, the method further includes:
[0139] S82: storing access status information of the target embedded device being in an accessed state into a database according to the target connection request.
[0140] After the user terminal selects the target embedded device to be connected, the access state of the target embedded device is changed based on the target connection request, so that the database records that the target embedded device is in the accessed state. Subsequently, if other user terminals access the front end of the device management system again, since the target embedded device is recorded in the database as being in the accessed state, the target embedded device will no longer be selected for access by other user terminals, thereby avoiding the preemption of embedded device resources.
[0141] Optionally, after the user terminal ends accessing the target embedded device, the access status of the target embedded device in the database is modified to an unaccessed status, so that the target embedded device can be selected for access by other user terminals after it becomes idle.
[0142] Optionally, in addition to modifying the access status of each embedded device in the database according to the target connection request, the access status of each embedded device can also be monitored by other means such as periodic querying to improve the accuracy of the access status of the embedded devices recorded in the database.
[0143] Based on the solution provided in the above embodiment, optionally, Fig. 9 As shown, the method also includes:
[0144] S91: Monitor the operating status information corresponding to the plurality of embedded devices respectively, wherein the operating status information indicates whether the operating status of the corresponding embedded device is abnormal.
[0145] In this step, detection instructions can be periodically sent to each embedded device to determine whether each embedded device is operating normally. Optionally, there is no need to perform detection on the embedded device being accessed, and the embedded device that is not being accessed can be mainly monitored. In practical applications, if an embedded device fails in an unaccessed state, it will not actively report, which makes it difficult for the fault of the embedded device to be discovered in time. Through the solution provided by the embodiment of the present application, the operating status information of each embedded device can be monitored in real time according to actual needs to ensure that each embedded device is in a normal and accessible operating state.
[0146] S92: If there is an embedded device with an abnormal operating status, generate fault information according to the embedded device with the abnormal operating status.
[0147] If there is an embedded device with abnormal operation status, fault information is generated according to the actual situation monitored. The fault information may include information about the abnormal embedded device, server information and port information to which the abnormal embedded device is connected, and historical operation information performed on the abnormal embedded device.
[0148] Optionally, after the fault information is generated, backup storage can be performed on important information data. Then, the abnormal embedded device is restarted by remotely controlling the power on and off, and the operating status of the embedded device is detected again after the restart is completed to try to repair the abnormality. If the embedded device is still in an abnormal state, an alarm message can be generated to prompt the management personnel to handle the abnormality in time. Through the solution provided by the embodiment of the present application, the abnormality of the embedded device can be detected in time, and the overall stability of the system can be improved. Furthermore, the embedded device can also be automatically repaired to reduce the situation where the user terminal side cannot access the embedded device.
[0149] In order to solve the problems existing in the prior art, the embodiment of the present application also provides a device 100 for accessing an embedded device, such as Fig.10As shown, it is applied to the equipment management system, including:
[0150] The receiving module 101 receives a target connection request from a user terminal, wherein the target connection request carries information of a target embedded device to be accessed.
[0151] The access module 102 accesses the target server to which the target embedded device is communicatively connected through a virtual terminal according to the pre-configured interface information of the target embedded device.
[0152] The connection module 103 calls the connection tool instruction of the target server to connect the virtual terminal with the target embedded device.
[0153] The display module 104 obtains the access page of the target embedded device through the virtual terminal, and displays the access page to the user terminal.
[0154] Through the device provided by the embodiment of the present application, first, a target connection request of a user terminal is received, and the target connection request carries the information of the target embedded device to be accessed. Then, according to the pre-configured interface information of the target embedded device, the target server to which the target embedded device is connected is accessed through a virtual terminal. Subsequently, the connection tool instruction of the target server is called to connect the virtual terminal to the target embedded device. Finally, the access page of the target embedded device is obtained through the virtual terminal, and the access page is displayed to the user terminal. In this scheme, based on the target embedded device specified by the target connection request of the user terminal, the virtual terminal is used to perform access according to the pre-configured interface information, and the access page is displayed to the user terminal, which can realize automatic jump connection based on the virtual terminal, effectively shorten the process of user access to the target embedded device, and improve the efficiency of user terminal access to the embedded device. In addition, this scheme realizes the access of the user terminal to the embedded device by displaying the access page to the user terminal, avoiding the user terminal directly logging into the server, which may cause the user to use multiple embedded devices under the server beyond his authority, thereby avoiding the problem of multiple user terminals logging into the same server grabbing embedded device resources, and effectively improving the efficiency of user terminal access to embedded devices.
[0155] Among them, the above modules in the device provided by the embodiment of the present application can also implement the method steps provided by the above method embodiment. Alternatively, the device provided by the embodiment of the present application can also include other modules in addition to the above modules to implement the method steps provided by the above method embodiment. And the device provided by the embodiment of the present application can achieve the technical effects that can be achieved by the above method embodiment.
[0156] In order to solve the problems existing in the prior art, the embodiment of the present application also provides a device management network, such as Fig.11 As shown, including:
[0157] The device management system 111 is used to execute the steps of the method described in any of the above embodiments;
[0158] At least one user terminal 112 communicatively connected to the device management system 111;
[0159] At least one server 113 in communication with the device management system 111;
[0160] A plurality of embedded devices 114 are communicatively connected to the device management system 111 via a server 113 .
[0161] The system provided by the embodiment of the present application first receives a target connection request from a user terminal, the target connection request carrying information of a target embedded device to be accessed. Then, according to the pre-configured interface information of the target embedded device, the target server to which the target embedded device is connected for communication is accessed through a virtual terminal. Subsequently, a connection tool instruction of the target server is called to connect the virtual terminal to the target embedded device. Finally, an access page of the target embedded device is obtained through the virtual terminal, and the access page is displayed to the user terminal.
[0162] In this solution, the target embedded device specified by the target connection request of the user terminal is accessed with a virtual terminal according to the pre-configured interface information, and the access page is displayed to the user terminal. Automatic jump connection can be achieved based on the virtual terminal, effectively shortening the process of user access to the target embedded device and improving the efficiency of user terminal access to embedded devices. In addition, this solution enables user terminals to access embedded devices by displaying access pages to user terminals, avoiding the possibility that users may unauthorizedly use multiple embedded devices under the server due to direct login of the user terminal to the server, thereby avoiding the problem of multiple user terminals logging into the same server grabbing embedded device resources, and effectively improving the efficiency of user terminals accessing embedded devices.
[0163] Optionally, the device management system in the network provided in the embodiment of the present application may also include multiple sub-function modules. Fig.12 As shown, the equipment management system may also include an equipment reservation module, an equipment terminal module, a power control module, a permission management module, an equipment monitoring module, a health check module, a log management module, an operation and maintenance statistics module, and the like.
[0164] In actual applications, different functional modules can be accessed through different interfaces according to the permissions of the user device. For example, ordinary users access the user operation interface through the user terminal, and then access the device reservation module, device terminal module, and power control module. Managers access the background management interface through the management terminal, and then access the permission management module, device monitoring module, health check module, log management module, and operation and maintenance statistics module.
[0165] Optionally, the user's authority can be determined based on the device accessing the device management system. For example, when accessing the device management system through a preset management device, access is achieved through the background management interface. When accessing the device management system through a device other than the preset management device, access is achieved through the user operation interface.
[0166] Alternatively, the user can access the device management system through a pre-registered account and password, and the device management system determines whether the user is a common user or a manager based on the permissions corresponding to the user's login account, and then displays the user operation interface to common users and the background management interface to managers.
[0167] Next, one by one Fig.12 The various sub-function modules in the equipment management system are described as follows:
[0168] 1. Device reservation module. It provides users with the function of making reservations for using embedded devices. Users can specify a time period for using a device, during which other users cannot use the device.
[0169] 2. Device terminal module. By storing the embedded device configuration information, users can access the embedded device with one click. Users can select the target embedded device to be accessed through the interface.
[0170] 3. Power control module. The embedded device power is remotely controlled through the PDU and the power status is displayed in the system. The power control module provides device power information query and allows users to remotely control the device power with one click to realize the power on and off function. The device management system and PDU are deployed in the same LAN, and the embedded device power is connected to the PDU to realize this function.
[0171] 4. Permission management module. Manage user permissions and only display the list of devices that the user has permission to access. Allow administrator users to set user permissions, and ordinary users can only use devices with permissions.
[0172] 5. Equipment monitoring module. The equipment management system monitors the equipment in real time, including the equipment usage and power status. The equipment monitoring module can monitor the equipment status in real time and display it to the user, including the current user of the equipment, the equipment power status, and whether the equipment is faulty. The equipment monitoring module contains a scheduler, which queries the equipment usage and power status from the server and PDU via SSH or HTTP every 20 seconds, sends the status to the front end and updates it to the database.
[0173] 6. Health check module. The device management system regularly checks whether the device has any faults. If a fault occurs, it will be displayed on the interface and the administrator will be notified. It can be used to determine whether the device is faulty. The system automatically accesses the embedded device regularly, returns the serial port or network port information to the system and performs fault analysis, sends the faulty device to the device monitoring module, and finally displays it to the user and sends the faulty device information to the administrator user.
[0174] 7. Log management module. It is used to provide users with query operation logs. The system automatically stores the serial port or network port information of the device, and provides a download interface to allow users to download and view at any time.
[0175] 8. Operation and maintenance statistics module. Used to record the usage of the system, including the number of users, user visits, device visits, daily average visits, annual average visits, and user growth.
[0176] In addition, the device management system realizes user interaction through the user operation interface and the background management interface. Among them, the user operation interface is used to display the list of devices that the user has permission to use, and provides buttons for accessing connected devices, reserving devices, and powering on and off devices for user convenience. Users can perform operations through this interface. The background management interface is provided for administrators to add and delete devices, view and modify device information. Managers can quickly configure devices and assign permissions. An interface for adding devices and assigning permissions is provided. The interface sends device information to the backend through http requests, and the backend stores the information in the database.
[0177] Through the system provided by the embodiment of the present application, users can quickly and conveniently access embedded devices with one click, simplify the configuration content of the device administrator, and do not need to repeatedly modify the configuration after changing the access user, thereby reducing the complexity of the configuration. After accessing the device management system, users can directly view which boards are idle and available and which are used by other users on the interface without logging into the server. In addition, users can remotely control the power supply of the device, and can flexibly record the device startup log, which is convenient for device debugging, without having to reach the actual geographical location of the embedded device to manually reset the power supply.
[0178] In terms of embedded device resource utilization, users can make reservations to use boards without waiting for other users to release devices, thus improving board usage efficiency. In addition, this system can control user permissions and only open authorized devices to users, without logging into the serial port server, to prevent users from using multiple embedded devices under the server beyond their authority, which can effectively improve security. In addition, this system can also perform health checks on devices, detect faulty devices in a timely manner and handle them, reducing the number of situations where user terminals cannot access embedded devices.
[0179] Preferably, an embodiment of the present application also provides an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the various processes of the above-mentioned method embodiment for accessing an embedded device are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.
[0180] The embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, each process of the above-mentioned method embodiment for accessing an embedded device is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0181] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0182] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0183] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0184] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0185] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0186] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0187] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0188] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0189] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0190] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims
1. A method for accessing an embedded device, It is characterized in that Applied to equipment management systems, including: Receiving a target connection request from a user terminal, wherein the target connection request carries information of a target embedded device to be accessed; According to the pre-configured interface information of the target embedded device, accessing the target server to which the target embedded device is connected in communication through a virtual terminal; Calling a connection tool instruction of the target server to connect the virtual terminal to the target embedded device; The access page of the target embedded device is obtained through the virtual terminal, and the access page is displayed to the user terminal.
2. The method according to claim 1, It is characterized in that Before receiving the target connection request of the user terminal, the method further includes: Acquire information of the user terminal and access status information corresponding to a plurality of embedded devices, wherein the plurality of embedded devices are connected to a device management system through a server for communication, and the access status information indicates whether the corresponding embedded device is in an accessed state; Determine an accessible device list according to the information of the user terminal and the access status information respectively corresponding to the plurality of embedded devices, wherein the accessible device list includes information of embedded devices that are accessible to the user terminal and are in an unaccessed state; The accessible device list is sent to the user terminal, so that the user terminal can select the target embedded device to be accessed from the accessible device list.
3. The method according to claim 2, It is characterized in that Before determining the accessible device list according to the information of the user terminal and the access status information respectively corresponding to the plurality of embedded devices, the method further includes: Configuring permission information corresponding to the user terminal, wherein the permission information represents access rights of the user terminal to the multiple embedded devices; Wherein, determining the accessible device list according to the information of the user terminal and the access status information respectively corresponding to the plurality of embedded devices includes: Determining authority information corresponding to the user terminal according to the information of the user terminal; An accessible device list is determined according to the permission information and the access status information respectively corresponding to the plurality of embedded devices, wherein the accessible device list includes information of embedded devices that the user terminal has the right to access and are in a non-accessed state.
4. The method according to claim 3, It is characterized in that Configuring the authority information corresponding to the user terminal includes: Receiving permission configuration information, wherein the permission configuration information includes information of the terminal to be configured and permission information to be configured; By means of a preset permission interface, the information of the terminal to be configured is associated with the permission information to be configured and stored in a permission database; Wherein, determining the authority information corresponding to the user terminal according to the information of the user terminal includes: The authority database is queried according to the information of the user terminal to obtain the authority information corresponding to the user terminal.
5. The method according to claim 3, It is characterized in that After determining the accessible device list according to the information of the user terminal and the access status information respectively corresponding to the plurality of embedded devices, the method further includes: Receiving a power control instruction from the user terminal, the power control instruction carrying information of an embedded device to be power-controlled selected by the user terminal in the accessible device list; A power control operation matching the power control instruction is executed on the embedded device to be powered on.
6. The method according to claim 1, It is characterized in that The target connection request includes a hypertext transfer protocol request, the target connection request carries access time information corresponding to the information of the target embedded device, and the access time information includes the access start time; The step of calling the connection tool instruction of the target server to connect the virtual terminal to the target embedded device includes: At the access start time specified by the access time information, the connection tool instruction of the target server is called to connect the virtual terminal with the target embedded device.
7. The method according to any one of claims 2 to 6, It is characterized in that Acquiring information of the user terminal and access status information corresponding to a plurality of embedded devices, including: When the device management system is accessed by the user terminal, the information of the user terminal is obtained and the access status information corresponding to the plurality of embedded devices respectively stored in the database is queried; After receiving the target connection request from the user terminal, the method further includes: According to the target connection request, access status information of the target embedded device being in an accessed state is stored in a database.
8. The method according to any one of claims 1 to 6, It is characterized in that Also includes: Monitoring the operation status information corresponding to the plurality of embedded devices respectively, wherein the operation status information indicates whether the operation status of the corresponding embedded devices is abnormal; If there is an embedded device with an abnormal operating status, fault information is generated according to the embedded device with the abnormal operating status.
9. A device management network, It is characterized in that include: A device management system, configured to execute the steps of the method according to any one of claims 1 to 8; At least one user terminal in communication with the device management system; at least one server in communication with the device management system; A plurality of embedded devices are connected to the device management system through a server for communication.
10. An electronic device, It is characterized in that include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method according to any one of claims 1 to 8 when executed by the processor.
11. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.
