Method for accessing embedded device and device management networking
Through the virtual terminal technology of the device management system, the problems of low efficiency and complex permission management of user terminal access to embedded devices are solved, efficient access and security management are achieved, and the connection and use process of embedded devices are simplified.
Patent Information
- Application Number
- PCT/CN2024/090767
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-22
- Filing Date
- 2024-04-30
- Publication Date
- 2024-11-28
AI Technical Summary
In the prior art, user terminals have low efficiency in accessing embedded devices, and the device management is complex, so it is impossible to connect a large number of embedded devices at the same time, which has difficulties in permission management and waste of resources.
Through the device management system, the target connection request of the user terminal is received, the virtual terminal accesses the server of the preconfigured target embedded device, calls the connection tool instructions to connect, and obtains the access page to the user terminal through the virtual terminal to realize the user terminal's matching Efficient access and permission management for embedded devices.
It improves the efficiency of user terminal accessing embedded devices, avoids the problems of overprivileged use and resource preemption caused by user terminals directly logging into the server, simplifies the device connection process, and improves the convenience and security of device management.
Smart Images

Figure CN2024090767_28112024_PF_FP_ABST
Abstract
Description
Method for accessing embedded devices and device management networking
[0001] Cross-references
[0002] This application claims priority to a Chinese patent application filed with the Patent Office of China on May 22, 2023, with application number 202310575760.4 and invention name “Method for accessing embedded devices and device management networking”. The entire contents of the application are incorporated by reference into this application. Technical Field
[0003] 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
[0004] Embedded devices are specialized computer systems with strict requirements for functionality, reliability, cost, size, and power consumption. They are widely used in production and daily life. With the continuous development of hardware technology, embedded devices are becoming more and more diverse.
[0005] Connecting embedded devices is often complex and requires specialized expertise. For embedded devices that only support serial port connections, the traditional device management approach involves placing all devices in a lab and debugging them using a computer in the lab to control the embedded device connections. Another device management approach involves connecting embedded devices to a server via serial ports, allowing clients to access the required embedded devices by accessing the server. Consequently, connecting embedded devices using serial ports presents numerous inconveniences. Connecting via a server requires deploying serial port connection tools on the server to configure each embedded device. Furthermore, servers are limited in the number of serial ports available, making it difficult to connect to a large number of embedded devices.
[0006] How to improve the efficiency of user terminals accessing embedded devices is a technical problem to be solved by this application.
[0007] Summary of the Invention
[0008] The purpose of the embodiments of the present application is to provide a method for accessing an embedded device and device management networking.
[0009] In a first aspect, a method for accessing an embedded device is provided, which is applied to a device management system, comprising: receiving a target connection request from a user terminal, the target connection request carrying information of a target embedded device to be accessed; accessing a target server to which the target embedded device is connected for communication through a virtual terminal according to pre-configured interface information of the target embedded device; calling a connection tool instruction of the target server to connect the virtual terminal to the target embedded device; obtaining an access page of the target embedded device through the virtual terminal, and displaying the access page to the user terminal.
[0010] In the second aspect, a device for accessing an embedded device is provided, which is applied to a device management system, including: a receiving module, which receives a target connection request from a user terminal, and the target connection request carries information of a target embedded device to be accessed; an access module, which accesses a target server to which the target embedded device is connected through a virtual terminal according to pre-configured interface information of the target embedded device; a connection module, which calls a connection tool instruction of the target server to connect the virtual terminal to the target embedded device; and a display module, which obtains an access page of the target embedded device through the virtual terminal and displays the access page to the user terminal.
[0011] In a third aspect, a device management network is provided, including: a device management system for executing the steps of the method described in the first aspect; at least one user terminal connected to the device management system for communication; at least one server connected to the device management system for communication; and multiple embedded devices connected to the device management system for communication via the server.
[0012] 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.
[0013] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method of the first aspect are implemented. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] 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:
[0015] FIG1 is a schematic diagram of a connection mode of an embedded device management system.
[0016] FIG2 a is a schematic diagram of the structure of a device management system provided by an embodiment of the present application.
[0017] FIG2 b is a flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0018] FIG3 a is a second flow chart of a method for accessing an embedded device according to an embodiment of the present application.
[0019] FIG3 b is a schematic diagram of a process in which a user terminal accesses a target embedded device through a device management system according to an embodiment of the present application.
[0020] FIG4 a is a third flow chart of a method for accessing an embedded device according to an embodiment of the present application.
[0021] FIG4 b is a schematic diagram of a flow chart of a manager accessing a device management system according to an embodiment of the present application.
[0022] FIG5 is a fourth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0023] FIG6 a is a fifth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0024] FIG6 b is a schematic diagram of a flow chart of a user terminal accessing a device management system to execute power control according to an embodiment of the present application.
[0025] FIG7 is a sixth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0026] FIG8 is a seventh flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0027] FIG9 is an eighth flowchart of a method for accessing an embedded device according to an embodiment of the present application.
[0028] FIG10 is a schematic structural diagram of an apparatus for accessing an embedded device according to an embodiment of the present application.
[0029] FIG11 is a structural diagram of a device management network according to an embodiment of the present application.
[0030] FIG12 is a second structural diagram of a device management network according to an embodiment of the present application. DETAILED DESCRIPTION
[0031] 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, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. The figure numbers in this application are only used to distinguish the various steps in the scheme and are not used to limit the execution order of the various steps. The specific execution order is subject to the description in the specification.
[0032] In the embedded device field, for embedded devices that only support serial port connections, one possible device management method is to place all devices in a laboratory and debug them using a PC (personal computer). Alternatively, the embedded devices can be connected to a server via a serial port, and user terminals can log in to the server to access the connected embedded devices.
[0033] In actual application scenarios, different user terminals can access different embedded devices through a server. For multiple embedded devices, a serial port tool can be used to connect the embedded device to the server. The user terminal then logs in to the server to access the embedded devices connected to that server. Due to serial port connection limitations, the number of embedded devices that can be connected to a server is limited. To access the desired embedded device, the user must log in to the server connected to the desired device.
[0034] Taking the connection method of the embedded device management system shown in Figure 1 as an example, user A can access embedded devices A and B, which are connected to server A through a serial port tool by logging in to server A. Correspondingly, user B can access embedded devices C and D by logging in to server B, and user C can access embedded devices E and F by logging in to server C.
[0035] In the scenario shown in Figure 1, if user A needs to access embedded device C or embedded device D, user A must log in to server B again and then access the connected embedded device. However, embedded device C or embedded device D may be currently being accessed by user B. The embedded device being accessed by user B cannot be accessed by user A at the same time, potentially causing serial port printing anomalies. It is also difficult for user A to know in advance which embedded device user B is occupying, resulting in inefficient connection and access.
[0036] Because users cannot know which embedded devices are occupied, in the scenario shown in Figure 1, it is 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.
[0037] Moreover, if user B connects to and accesses embedded device C, no other user can connect to and 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.
[0038] In addition, using multiple serial ports to connect embedded devices is cumbersome and complex to control. When different users need to use different embedded devices, the embedded devices need to be reconfigured, which makes it difficult to quickly and easily connect and access them.
[0039] In one application scenario, assume that user B has permission to access embedded device C but not embedded device D. Both embedded devices C and D are connected to server B. Once user B logs in to server B, he or she has access to all embedded devices connected to that server. This could potentially allow user B to unauthorizedly access embedded device D, highlighting the difficulty of managing embedded device connection access permissions in this device management system.
[0040] In order to solve the problems existing in the prior art, an embodiment of the present application 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 shown in Figure 2a. During the application process, multiple user devices can be connected to the device management system to access the embedded device. The scenario shown in Figure 2a shows three user devices: user A, user B, and user C. In actual applications, there can also be a greater or lesser number of user terminals communicating with the device management system.
[0041] 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.
[0042] As shown in Figure 2a, a device management system can connect to one or more embedded devices through a serial port connection using a serial device server. For example, in Figure 2a, serial device server A is connected to embedded device A and embedded device B through a serial port. Serial device server B is also connected to embedded device C through a serial port.
[0043] Alternatively, the device management system can be connected to one or more embedded devices via a network connection through a jump server. For example, in Figure 2a, jump server A is connected to embedded devices D and E via the network. Jump server B is connected to embedded device F via the network.
[0044] Furthermore, in the system shown in Figure 2a, the device management system can also control the power supply of each embedded device through the PDU (Power Distribution Unit) power outlet. A PDU is a type of outlet device, and in actual applications, other types of power supplies can also be used to power each embedded device. Alternatively, multiple power supplies can be used to power multiple embedded devices separately.
[0045] The method provided in an embodiment of the present application is shown in FIG2b , and is applied to a device management system and includes the following steps.
[0046] 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.
[0047] 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 wishes to access. The target connection request can also include information about the user terminal itself, allowing the device management system to provide feedback to the user terminal.
[0048] 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.
[0049] The device management system is preconfigured with interface information for each embedded device. This interface information represents the connection relationship between the corresponding embedded device in the device management system. In this step, the target server to which the target embedded device is connected is determined based on the preconfigured interface information of the target embedded device. The target server is then accessed through a virtual terminal to access the target embedded device. Specifically, if the target embedded device's information contains information about the connected server, the target embedded device can be directly accessed through the server based on this information.
[0050] 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.
[0051] S23: calling the connection tool instruction of the target server to connect the virtual terminal with the target embedded device.
[0052] After accessing the target server through a virtual terminal, the target server's connection tool command is invoked to further connect the virtual terminal to the target embedded device. Since the embedded device is connected to the server through a virtual terminal, access is achieved by simply displaying an access interface to the user terminal. This eliminates the need for the user terminal to log in to the serial port service, and eliminates the need to frequently change the embedded device configuration. This improves the efficiency of user terminal access to the embedded device, as there is no need to change the embedded device configuration in scenarios where different users access the embedded device.
[0053] S24: Obtaining an access page of the target embedded device through the virtual terminal, and displaying the access page to the user terminal.
[0054] After the device management system successfully accesses the target embedded device through the server, it 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, allowing the user to view the access page of the target embedded device through the user terminal and perform the required operations.
[0055] This solution uses a virtual terminal to connect to an embedded device through a server. This solution enables user terminals to access the embedded device by displaying an access page to the user terminal. This avoids the problem of users logging directly into the server, which could lead to unauthorized access to multiple embedded devices on the server. It also prevents multiple user terminals logging into the same server from competing for embedded device resources, effectively improving the efficiency of user terminal access to embedded devices.
[0056] Based on the solution provided in the above embodiment, optionally, as shown in FIG3 a , before the above step S21 , the following steps are further included.
[0057] 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.
[0058] In this step, information of the user terminal and access status information corresponding to multiple embedded devices are obtained, wherein the multiple embedded devices are communicated with the device management system through the server, and the access status information indicates whether the corresponding embedded device is in an accessed state.
[0059] The information of the user terminal may specifically include hardware information of the user terminal, information of the user using the user terminal, etc. The user information may be information pre-registered by the user, or may be information pre-set by the administrator in the device management system.
[0060] 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.
[0061] In this step, each embedded device is associated with a piece of access status information, which indicates whether the corresponding embedded device is currently being accessed by a user terminal. In this solution, an embedded device can be in two states during normal operation. One is the accessed state, meaning that a user terminal is currently accessing the embedded device, and the embedded device cannot be connected to or accessed by other user terminals. The other is the unaccessed state, meaning that no user terminal is currently accessing the embedded device, and the embedded device is accessible to a user terminal.
[0062] In actual applications, the access status information corresponding to 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.
[0063] 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 user terminal information is obtained, the pre-updated access status list can be directly called to obtain the access status information corresponding to multiple embedded devices.
[0064] 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.
[0065] 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 an unaccessed state are screened from multiple embedded devices based on the access status information obtained in the above step.
[0066] 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 not accessed embedded devices to generate a list of accessible devices. Alternatively, embedded devices accessible to the user terminal can be screened out first, and then not accessed embedded devices can be selected from the accessible embedded devices to generate a list of accessible devices. Alternatively, not accessed embedded devices and embedded devices accessible to the user terminal can be screened separately, and then the list of accessible devices can be determined by calculating the intersection.
[0067] The embedded devices accessible to the user terminal may specifically indicate which embedded devices' access conditions are satisfied by the hardware functions of the user terminal, or may also indicate which embedded devices the user corresponding to the user terminal has the authority to access.
[0068] The information of the embedded devices included in the accessible device list may specifically be an identifier of the embedded device, indicating which embedded devices are in a state accessible to the user terminal. The information of the embedded device may also include information of the server to which the embedded device is connected, relevant configuration information of the embedded device, etc.
[0069] After the accessible device list is generated, the accessible device list may be sent to the user terminal so that the user can view each accessible embedded device through the user terminal.
[0070] 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.
[0071] By sending a list of accessible devices to a user terminal, the user terminal can select a target embedded device to connect to based on the list of accessible devices, and then send a target connection request containing information about the target embedded device. Optionally, the target embedded device information included in the target connection request can be information related to the target embedded device in the list of accessible devices, so that the device management system can parse the target connection request to obtain the target embedded device requested by the user terminal.
[0072] The solution provided by the embodiments of this application can effectively improve the efficiency of user terminals accessing embedded devices. By obtaining the access status information of each embedded device, a list of devices accessible to the user terminal can be determined, allowing the user to quickly determine the target embedded device currently available, preventing multiple users from competing for the same embedded device, thereby improving the efficiency of user terminals accessing embedded devices.
[0073] 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.
[0074] Specifically, referring to FIG3b , a user terminal first accesses the front end of the device management system, which then determines a list of accessible devices for the user terminal through the device management server and the database. The user terminal then selects the target embedded device to be accessed from the list of accessible devices. The device management system can determine the target server to which the target embedded device is connected based on the information about the target embedded device, or it can query pre-stored information based on the information about the target embedded device to determine the target server to which the target embedded device is connected.
[0075] Then, the target server is accessed through the virtual terminal and a connection tool instruction of the target server is called to connect the virtual terminal to the target embedded device to obtain an access page of the target embedded device.
[0076] The virtual terminal can be, for example, a Web Terminal. In actual applications, other virtual terminals can also be used for access. After obtaining information about the target embedded device that the user terminal needs to access, the user terminal uses the human-computer interaction terminal (i.e., the virtual terminal) to access the target server connected to the target embedded device, i.e., Server A shown in Figure 3b. Furthermore, the user terminal accesses the target embedded device, i.e., Device A shown in Figure 3b, through Server A.
[0077] 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 in an unaccessed state 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. The human-computer interaction terminal 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. The user only needs to click to connect the device to access the embedded device, which can quickly and easily achieve access to the target embedded device.
[0078] 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 having to connect 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 based on the user operations.
[0079] Through the solution provided by the embodiments of the present application, when any user terminal requests access to a target embedded device, the target embedded device selected by the user terminal is accessed via a virtual terminal, without the user terminal having to log in and connect to the server. This simplifies configuration of the embedded device by eliminating the need to reconfigure each time a connection is made. Furthermore, it avoids the possibility of a user terminal unauthorizedly accessing other embedded devices on the server after connecting to the server, effectively enabling user terminals to manage access rights to embedded devices.
[0080] After the target embedded device is implemented, you can also regularly query the server's serial port usage and send device occupancy information to the device management system. Once the device management system detects that the target embedded device is being accessed by a user terminal, it automatically changes the device's access status to "accessed." This prevents other users from accessing the embedded device while it is occupied, preventing resource grabbing. Once the user terminal closes the target embedded device's access interface, the target embedded device's resources are released, and the device management system records the target embedded device's status as "unaccessed." After that, other users can request access to the embedded device.
[0081] Optionally, as shown in FIG3b , the human-computer interaction terminal in this example can also write or read terminal log files to the device management server. The terminal log files may include, for example, records of the human-computer interaction terminal's access to the server and embedded devices, records of the access interface displayed to the user terminal, records of operations performed by the user terminal on the access interface, and records of operations performed by the human-computer interaction terminal on the embedded device based on user operations. The user terminal can retrieve the terminal log files from the device management server through the human-computer interaction terminal to query historical operation records.
[0082] 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 through the database which embedded devices are in an unaccessed state, which is conducive to quickly generating a list of accessible devices for the user terminal.
[0083] Based on the solution provided by the above embodiment, optionally, as shown in FIG4a , before the above step S32 , the method further includes: S41 : configuring permission information corresponding to the user terminal, wherein the permission information represents the access rights of the user terminal to the multiple embedded devices.
[0084] In practice, administrators can pre-configure user terminal access permissions for embedded devices in the device management system. If there are multiple embedded devices, each can be configured individually. Alternatively, multiple embedded devices can be categorized and then configured in batches.
[0085] For example, in one application scenario, an embedded device and a server can be connected via a serial port. An administrator can add device information and the server it's connected to through the backend interface. This information can include the device name, type, server address, and serial port number. The administrator can then add users who can access the device. These users then have one-click access to the embedded device.
[0086] Optionally, as shown in Figure 4b, the administrator first accesses the backend management interface of the device management system. Device information is then added. This information refers to the embedded device for which user terminal access permissions need to be set. Next, user permissions for the device are added based on the device information. Specifically, the added user permissions may include which users can access the device, or which users are prohibited from accessing the device. Finally, the added device information and corresponding user permissions are stored and displayed in a device list. The administrator can modify the device information or corresponding user permissions through the device list.
[0087] Among them, access rights 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 identifiers match the level identifiers of the above-mentioned embedded devices. For example, the permission identifiers of the user terminals 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 rights. In actual use, the user terminal's access rights to embedded devices can be flexibly adjusted by adjusting the level identifier or the permission identifier, and access rights can be easily maintained or changed.
[0088] The above step S32 includes the following steps.
[0089] S42: Determine authority information corresponding to the user terminal according to the information of the user terminal.
[0090] In this step, the information of the user terminal may be queried, for example, by querying the information of the user terminal in a device list of pre-stored access permissions to determine which embedded devices the user terminal can access.
[0091] If the list of devices pre-stored with access rights records the permission identifier corresponding to the user terminal's information, the queried permission information corresponding to the user terminal may include the permission identifier. Furthermore, a comparison may be performed based on the queried permission identifier corresponding to the user terminal and the level identifiers corresponding to each embedded device to determine which embedded devices the user terminal is authorized to access, and permission information may be generated containing information about the embedded devices that the user terminal is authorized to access.
[0092] 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.
[0093] 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, which can realize the access permission management of the user terminal to the embedded devices. 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.
[0094] Based on the solution provided in the above embodiment, optionally, as shown in FIG5 , in the above step S41 , configuring the permission information corresponding to the user terminal includes the following steps.
[0095] S51: Receive authority configuration information, where the authority configuration information includes information of a terminal to be configured and authority information to be configured.
[0096] In this example, administrators can pre-configure terminal permissions. The terminal to be configured can be a terminal used by administrators for routine inspections and management, or a registered user terminal. Information about the terminal to be configured includes, for example, the device name, device type, the server address where the device resides, and the device's serial port number.
[0097] The permission information to be configured corresponding to the information of the terminal to be configured may be, for example, a pre-set permission level. The permission information may be used to indicate the embedded devices that the terminal to be configured has access to, or may be used to indicate the embedded devices that the terminal to be configured does not have access to.
[0098] 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.
[0099] For permission configuration information, permission configuration is performed through a 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. When the terminal requests access to the embedded device, the terminal can query the access permission for the terminal.
[0100] Wherein, in the above step S42, determining the authority information corresponding to the user terminal according to the information of the user terminal includes: S53: performing a query on the authority database according to the information of the user terminal to obtain the authority information corresponding to the user terminal.
[0101] In this example, the user terminal information is queried in the authority database to obtain the authority information corresponding to the user terminal, which indicates which embedded devices the user terminal is authorized to access. In the subsequent steps, the user terminal's accessible device list can be determined based on the authority information.
[0102] This example is explained below with reference to the scenario shown in Figure 2a. 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 into 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 into the server, thereby solving the problem of difficulty in managing access rights for multiple embedded devices in the same server.
[0103] Based on the solution provided in the above embodiment, optionally, the device management system is further configured to supply power to the multiple embedded devices.
[0104] In this example, as shown in Figure 2a, the device management system can supply power to each embedded device through the PDU. In actual applications, the administrator can control the PDU through the device management system to control the power on or off of each embedded device.
[0105] As shown in FIG6a , after step S32 , the following steps are further included.
[0106] 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.
[0107] Referring to Figure 6b, in this example, a 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 accessible to the user terminal. The user terminal then receives power control instructions sent by the user terminal. In other words, the user terminal can perform power control on user terminals that are accessible to the user terminal and are not accessed. In actual applications, if an abnormality occurs in an embedded device, the power control instruction can be used to power off and on the abnormal embedded device, restarting the embedded device and repairing the abnormality.
[0108] Optionally, based on the user terminal's list of accessible devices, the device management system's front-end can display virtual buttons for powering on, powering off, or restarting each embedded device in the list. The user terminal can click the virtual buttons to send power control commands, thereby achieving power control of the embedded device.
[0109] S62: Execute a power control operation matching the power control instruction on the embedded device to be powered on.
[0110] After receiving a power control instruction from a user terminal, the device management system can execute the power control operation that matches the power control instruction by sending an instruction. For example, power control can be performed on a remote power module that matches the power control instruction. This remote power module can, for example, include a PDU. This remote power module can then power on or off the embedded device that matches the power control instruction, thereby achieving power control.
[0111] This solution allows user terminals to remotely power on and off embedded devices. When an embedded device freezes or experiences other abnormal failures, recovery can be attempted by controlling power on and off, eliminating the need for administrators to physically reboot the device. This improves overall system stability and facilitates control.
[0112] Optionally, to facilitate power control, administrators can pre-configure power control parameters. For example, when adding a device, administrators can add power configuration for the device. This configuration can include parameters such as the PDU address, PDU login method, and the socket number on the PDU where the device is located. After configuration is complete, the device management system can locate and control the corresponding PDU power supply based on the configured information. Users can remotely control the power supply of embedded devices and restart the device by simply clicking the power off and power on buttons in the visual interface.
[0113] 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 an access start time.
[0114] Among them, Hyper Text Transfer Protocol (HTTP) is a network transmission protocol widely used on the Internet. In this example, the user terminal can implement remote access and control of the embedded device through HTTP protocol request.
[0115] In this example, after selecting the target embedded device to be accessed, the user terminal can also set access time information for the target embedded device, wherein the access time information at least includes the access start time, which indicates when the user terminal starts accessing the target embedded device.
[0116] Optionally, the access time information may further include the duration of the access, such as ten minutes. Alternatively, the access time information may further include the end time of the access, that is, when the access to the target embedded device is stopped.
[0117] As shown in FIG. 7 , the above step S23 includes: 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.
[0118] In practice, user terminals can reserve access to target embedded devices. For example, suppose user A, user B, and user C all need to access embedded device A. If these three users don't negotiate, they won't know when they can access embedded device A, potentially leading to resource preemption or idleness.
[0119] Through the solution provided by the embodiments of the present application, users A, B, and C can reserve access time periods for embedded device A using access time information. For example, the target connection request sent by user A carries access time information from 10:00 to 10:30, the target connection request sent by user B carries access time information from 10:40 to 11:10, and the target connection request sent by user C carries access time information from 12:00 to 12:10. Based on the access time information of users A, B, and C, the corresponding user terminals can be allowed to access embedded device A during the corresponding time periods, preventing embedded device resources from being preempted or left idle.
[0120] Optionally, after a user terminal selects a target embedded device through the device management system's front-end, the device management system can query whether other users have reserved access times for the target embedded device. If so, the user terminal can display the reserved access time information to allow the user to select a different time slot based on the existing reservations. This facilitates orderly access to the same embedded device by multiple users, thereby fully and rationally utilizing embedded device resources.
[0121] In practical applications, the solution provided by the embodiments of the present application can effectively manage multiple embedded devices distributed across different servers. This facilitates the rational allocation and use of embedded device resources, preventing resource preemption or idleness. User terminals can efficiently access target embedded devices through this solution, as well as schedule access to target embedded devices. This facilitates the collaborative execution of tasks by multiple user terminals, facilitates the rational arrangement of access by each user terminal to the same embedded device, and helps improve the efficiency of collaborative work between multiple user terminals.
[0122] Based on the solution provided in the above embodiment, optionally, as shown in Figure 8, the above step S31 includes: S81: when the device management system is accessed by the user terminal, obtain the information of the user terminal and query the access status information corresponding to the multiple embedded devices stored in the database.
[0123] In the solution provided by the embodiments of the present application, the access status information of each embedded device is stored in a database. Referring to Figure 3b, a user terminal first accesses the front-end of the device management system. Subsequently, the front-end of the device management system sends a request to the back-end to query the database of the device management server for the access status information corresponding to each embedded device. Furthermore, embedded devices that are not accessed are identified, and based on the information of the user terminal, embedded devices that are accessible to the user terminal and are not accessed are identified to generate a list of accessible devices.
[0124] Wherein, after the above step S21, the method further includes: S82: storing access status information of the target embedded device in an accessed state into a database according to the target connection request.
[0125] After a user terminal selects a target embedded device to connect to, the access status of the target embedded device is modified based on the target connection request, so that the database records the target embedded device as being in the accessed state. Subsequently, if another user terminal accesses the front end of the device management system, the target embedded device will no longer be selected for access by other user terminals because the database records the target embedded device as being in the accessed state, thereby avoiding embedded device resource preemption.
[0126] 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.
[0127] 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 through other methods such as periodic querying to improve the accuracy of the access status of the embedded devices recorded in the database.
[0128] Based on the solution provided in the above embodiment, optionally, as shown in FIG9 , the method further includes the following steps.
[0129] S91: Monitoring the operating status information corresponding to each of the plurality of embedded devices, wherein the operating status information indicates whether the operating status of the corresponding embedded device is abnormal.
[0130] In this step, a detection instruction 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 monitoring can be performed mainly on the embedded devices that are not being accessed. In actual applications, if an embedded device is not being accessed, it will not actively report a fault, which makes it difficult to detect the fault of the embedded device in a timely manner. 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, ensuring that each embedded device is in a normal and accessible operating state.
[0131] 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.
[0132] If there is an embedded device with an abnormal operating status, fault information is generated based on the actual monitored situation. The fault information may include information about the abnormal embedded device, information about the server and port to which the abnormal embedded device is connected, and historical information about operations performed on the abnormal embedded device.
[0133] 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 deal with the abnormality in a timely manner. Through the solution provided by the embodiment of the present application, abnormalities occurring in the embedded device can be detected in a timely manner, thereby improving the overall stability of the system. Furthermore, the embedded device can also be automatically repaired to reduce the situation where the user terminal side cannot access the embedded device.
[0134] In order to solve the problems existing in the prior art, an embodiment of the present application also provides a device 100 for accessing an embedded device, as shown in Figure 10, which is applied to a device management system and includes: a receiving module 101, which receives a target connection request from a user terminal, and the target connection request carries information of a target embedded device to be accessed. An access module 102, which accesses a target server to which the target embedded device is connected through a virtual terminal according to the pre-configured interface information of the target embedded device. A connection module 103, which calls the connection tool instruction of the target server to connect the virtual terminal to the target embedded device. A display module 104, which obtains an access page of the target embedded device through the virtual terminal and displays the access page to the user terminal.
[0135] The device provided by the embodiment of the present application first receives a target connection request from a user terminal, the target connection request carrying information about 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, 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. In this solution, 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. 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 terminal access to embedded devices by displaying the access page to the user terminal, avoiding the problem of user terminal directly logging into the server causing the user to unauthorizedly use multiple embedded devices under the server, thereby avoiding the problem of multiple user terminals logging into the same server grabbing embedded device resources, effectively improving the efficiency of user terminal access to embedded devices.
[0136] The aforementioned modules in the apparatus provided in the embodiments of the present application may also implement the method steps provided in the aforementioned method embodiments. Alternatively, the apparatus provided in the embodiments of the present application may further include other modules in addition to the aforementioned modules to implement the method steps provided in the aforementioned method embodiments. Furthermore, the apparatus provided in the embodiments of the present application can achieve the technical effects achievable by the aforementioned method embodiments.
[0137] In order to solve the problems existing in the prior art, an embodiment of the present application also provides a device management network, as shown in Figure 11, including: a device management system 111, used to execute the steps of the method described in any of the above embodiments; at least one user terminal 112 communicatively connected to the device management system 111; at least one server 113 communicatively connected to the device management system 111; and multiple embedded devices 114 communicatively connected to the device management system 111 through the server 113.
[0138] 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 about the target embedded device to be accessed. Then, based on 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, a connection tool instruction of the target server is called to connect the virtual terminal to the target embedded device. Finally, an access page for the target embedded device is obtained through the virtual terminal and displayed to the user terminal.
[0139] In this solution, the target embedded device specified by the target connection request of the user terminal is accessed using a virtual terminal according to the pre-configured interface information, and the access page is displayed to the user terminal. This can automatically jump the connection based on the virtual terminal, effectively shortening the process of users accessing the target embedded device and improving the efficiency of the user terminal accessing the embedded device. In addition, this solution enables the user terminal to access the embedded device by displaying the access page to the user terminal, avoiding the possibility that the user may exceed the authority to use multiple embedded devices under the server due to the user terminal directly logging into the server, thereby avoiding the problem of multiple user terminals logging into the same server competing for embedded device resources, effectively improving the efficiency of the user terminal accessing the embedded device.
[0140] Optionally, the device management system in the network provided in the embodiment of the present application may further include multiple sub-functional modules. As shown in Figure 12, the device management system may further include a device reservation module, a device terminal module, a power control module, a permission management module, a device monitoring module, a health check module, a log management module, an operation and maintenance statistics module, etc.
[0141] In practice, different functional modules can be accessed through different interfaces based on user device permissions. For example, ordinary users can access the user operation interface through a user terminal, and then access the device reservation module, device terminal module, and power control module. Managers can access the backend management interface through a management terminal, and then access the permission management module, device monitoring module, health check module, log management module, and operation and maintenance statistics module.
[0142] Optionally, user permissions 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 backend 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.
[0143] Alternatively, users can access the device management system using a pre-registered account and password. The device management system will determine whether the user is a regular user or an administrator based on the permissions corresponding to the user's login account. It will then display the user interface to regular users and the backend management interface to administrators.
[0144] Next, each sub-functional module in the device management system in FIG12 is described one by one.
[0145] 1. Device reservation module. This module allows users to schedule the use of embedded devices. Users can specify a time period for the use of a device, during which other users cannot use the device.
[0146] 2. Device terminal module. This module stores embedded device configuration information and enables one-click access to embedded devices. Users can select the target embedded device to access through the interface.
[0147] 3. Power Control Module. This module remotely controls the power supply of embedded devices through the PDU and displays power status in the system. The module provides device power information query and allows users to remotely power on and off devices with a single click. This functionality is achieved when the device management system and PDU are deployed on the same local area network, and the embedded device power supply is connected to the PDU.
[0148] 4. Permission Management Module. Manage user permissions and only display a list of devices that the user has permission to access. Allow administrators to set user permissions, and ordinary users can only use devices for which they have permission.
[0149] 5. Device Monitoring Module. The device management system monitors devices in real time, including device usage and power status. The device monitoring module monitors device status in real time and displays it to the user, including the current user, power status, and whether the device is faulty. The device monitoring module includes a scheduler that queries device 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 the database.
[0150] 6. Health Check Module. The device management system regularly checks devices for faults. Faults are displayed on the interface and the administrator is notified. This module can be used to determine if a device is faulty. The system automatically and regularly accesses embedded devices, returning serial or network port information to the system for fault analysis. Faulty devices are then sent to the device monitoring module, which displays the information to the user and sends it to the administrator.
[0151] 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 it at any time.
[0152] 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.
[0153] The device management system facilitates user interaction through a user interface and a backend management interface. The user interface displays a list of devices for which the user has permissions and provides convenient buttons for accessing connected devices, reserving devices, and powering devices on and off. Users can perform operations through this interface. The backend management interface is for administrators, allowing them to add and remove devices, view and modify device information. Administrators can quickly configure devices and assign permissions. An interface for adding devices and assigning permissions is provided. This interface sends device information to the backend via HTTP requests, which then stores the information in a database.
[0154] Through the system provided by the embodiments of the present application, users can quickly and conveniently access embedded devices with one click, simplifying the configuration content of the device administrator. After changing the access user, there is no need to repeatedly modify the configuration, thereby reducing the configuration complexity. After accessing the device management system, users can directly view which boards are available and which are in use by other users on the interface without logging into the server. In addition, users can remotely control the power supply of the device and flexibly record the device startup log, facilitating device debugging without having to manually reset the power supply by going to the actual location of the embedded device.
[0155] In terms of embedded device resource utilization, users can reserve boards for use without having to wait for other users to release them, improving board usage efficiency. Furthermore, the system controls user permissions, making only authorized devices available to users without logging into a serial port server. This prevents users from unauthorized access to multiple embedded devices on the server, effectively improving security. Furthermore, the system performs device health checks, promptly identifying and addressing faulty devices and reducing the number of instances where user terminals are unable to access embedded devices.
[0156] 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 runnable 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.
[0157] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the computer program implements the various processes of the above-mentioned method embodiment for accessing an embedded device and can achieve the same technical effect. To avoid repetition, the details are not described 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.
[0158] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can 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 can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.
[0159] The present application is described with reference to the flow chart and / or block diagram of the method, device (system), and computer program product according to the embodiment of the present application. It should be understood that each flow process and / or box in the flow chart and / or block diagram and the combination of the flow process and / or box in the flow chart and / or block diagram can be realized 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 processing machine or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for realizing the function specified in one flow chart flow or multiple flows and / or one box or multiple boxes of the block diagram.
[0160] These computer program instructions may also be stored in a computer-readable memory that can direct 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 a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0161] 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, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.
[0162] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0163] 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. Memory is an example of a computer-readable medium.
[0164] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The 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 disc read-only memory (CD-ROM), digital versatile disc (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 transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.
[0165] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.
[0166] 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 take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0167] The foregoing is merely 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 modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.
Claims
1. A method for accessing an embedded device, applied to a device management system, include: 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, in, 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, in, 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 an unaccessed state.
4. The method according to claim 3, in, 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; The information of the terminal to be configured is associated with the permission information to be configured through a preset permission interface. Linked storage to the authority 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, in, 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 selected by the user terminal in the accessible device list and to be powered on; 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, in, 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, in, 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, in, 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, 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, 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 having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.
Citation Information
Patent Citations
Remote assistance service method aiming at embedded operation system
CN102377814A
Method for managing and monitoring embedded equipment cluster
CN102664952A
Method and apparatus for managing field device based on cloud server
US20190116095A1
Method and apparatus for providing multiple management interfaces to a network device
US7254781B1
