Networking operation and maintenance method of embedded device, electronic device and storage medium

Abstract

The invention relates to the technical field of computers, in particular to a networking operation and maintenance method of embedded equipment, electronic equipment and a computer readable storage medium, and the method comprises the following steps: in response to a received startup instruction, establishing temporary connection with a server based on a short connection mode of an HTTP protocol, and sending a registration request to the server; receiving a security token which is sent by the server and comprises a reporting period, and sending a heartbeat packet to the server based on the temporary connection every other reporting period; and if an updated reporting period sent by the server is received, sending a heartbeat packet to the server based on the temporary connection every other updated reporting period. Heartbeat packet reporting of the embedded device is achieved through an HTTPS short connection mode, and the concurrent processing capacity of the system is greatly improved. And the reporting frequency of the heartbeat packet is dynamically adjusted according to a period specified by the server, so that the problems of resource waste and information lag are avoided.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a networking operation and maintenance method for an embedded device, an electronic device, and a computer-readable storage medium. Background Art

[0002] Embedded devices are computer hardware and software components built into other devices or systems to perform specific functions. After leaving the factory, embedded devices are usually connected to the local network or the Internet by end users or system integrators, and the corresponding network configuration and authorization operations are performed. After that, the embedded device can be managed by a remote management platform, which can be remotely monitored, maintained and upgraded to ensure the normal operation and performance optimization of the embedded device. However, in actual application, we found that some manufacturers' embedded devices do not support online operation and maintenance, and problems require on-site support from technicians, which has high labor costs; or the operation and maintenance of embedded devices only supports reporting simple data such as device status, and cannot conduct in-depth analysis of the performance and faults of embedded devices; even some manufacturers directly open the remote ports of embedded devices for the convenience of operation and maintenance, which poses certain security risks. With the rapid development of communication technology, the application scope of embedded devices continues to expand, and the operation and maintenance level of existing embedded devices obviously cannot meet people's increasingly high requirements. Specifically, the problems faced by the operation and maintenance management of current embedded devices after leaving the factory mainly include:

[0003] 1. Device status is not visible: Traditional embedded devices lack effective remote monitoring methods, making it difficult to understand the operating status of the device in a timely manner.

[0004] 2. Difficulty in fault diagnosis: When an embedded device malfunctions, technicians often need to conduct on-site inspections, which is time-consuming and labor-intensive.

[0005] 3. Impact of network instability: In an unstable network environment, the status information of embedded devices may be lost, affecting operation and maintenance efficiency.

[0006] 4. Limited remote operation: The lack of a safe and reliable remote operation mechanism makes it difficult to achieve remote task execution and debugging.

[0007] 5. Difficulty in performance evaluation: The lack of systematic performance data collection and analysis methods makes it difficult to evaluate the stability of the firmware.

[0008] 6. Security risks: Existing remote access solutions may have security vulnerabilities, increasing the risk of illegal access to embedded devices.

[0009] 7. Heavy server load pressure: The long connection mode causes excessive consumption of server resources, making it difficult to support the access of large-scale embedded devices.

[0010] 8. Lack of overall analysis capabilities: It is impossible to conduct overall analysis on the same type of embedded devices, making it difficult to discover batch problems.

[0011] 9. Fixed reporting strategy: The reporting frequency of embedded devices is fixed and cannot be dynamically adjusted according to actual needs, resulting in resource waste or information delay.

[0012] In view of the existence of the above problems, there is an urgent need for a networked operation and maintenance method for new embedded devices that can efficiently manage embedded devices and adapt to different application scenarios. Summary of the invention

[0013] In view of this, the present invention proposes a networking operation and maintenance method for an embedded device, an electronic device and a computer-readable storage medium, aiming to solve the problem of resource waste or information delay caused by the fixed reporting frequency of existing embedded devices.

[0014] In order to solve the above problems, the present invention adopts the following technical solutions:

[0015] In a first aspect, the present invention provides a network operation and maintenance method for an embedded device, comprising:

[0016] In response to receiving the power-on instruction, a temporary connection is established with the server based on a short connection mode of the HTTP protocol, and a registration request is sent to the server through the temporary connection; wherein the registration request includes the identity information of the embedded device;

[0017] Receive a security token including a reporting period sent by the server, establish a temporary connection with the server based on a short connection method of the HTTP protocol at each interval of the reporting period, and send a heartbeat packet to the server through the temporary connection; wherein the security token is generated after the identity information is verified, and the heartbeat packet includes the operating status of the embedded device;

[0018] If an updated reporting cycle sent by the server is received, a temporary connection is established with the server based on a short connection mode of the HTTP protocol at intervals of the updated reporting cycle, and a heartbeat packet is sent to the server through the temporary connection.

[0019] Further, after receiving the security token including the reporting period sent by the server, the method further includes:

[0020] If an abnormal event is detected and it is confirmed that the network connection with the server is stable, a temporary connection is established with the server based on a short connection method of the HTTP protocol, and an abnormality report related to the abnormal event is sent to the server through the temporary connection;

[0021] If an abnormal event is detected and it is confirmed that the network connection with the server is interrupted, an abnormal report related to the abnormal event is stored in the embedded device; when it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and the abnormal report stored in the embedded device is sent to the server in chronological order through the temporary connection;

[0022] The abnormal report includes the abnormal event type, occurrence time and event parameters.

[0023] Further, after receiving the security token including the reporting period sent by the server, the method further includes:

[0024] If it is detected that the network connection with the server is interrupted, the heartbeat packets of the embedded device collected at each interval of the reporting period are stored in the embedded device;

[0025] When it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and the heartbeat packets stored in the embedded device are sent to the server in chronological order through the temporary connection.

[0026] Further, after receiving the security token including the reporting period sent by the server, the method further includes:

[0027] If a task instruction issued by the server is received through a temporary connection established with the server in a short connection mode based on the HTTP protocol, a request authorization notification is issued;

[0028] When receiving the authorization execution instruction, executing the task included in the task instruction; wherein the authorization execution instruction is generated according to the authorization request notification, and the task includes software update and configuration modification;

[0029] If it is confirmed that a temporary connection is established with the server in a short connection mode based on the HTTP protocol, the execution progress and execution result of the task are sent to the server.

[0030] Further, after receiving the security token including the reporting period sent by the server, the method further includes:

[0031] If a temporary connection is established with the server through a short connection method based on the HTTP protocol, and a debugging request instruction issued by the server is received, a debugging request notification is issued;

[0032] When receiving the authorization debugging instruction, the remote debugging channel is started for remote debugging; wherein the authorization debugging instruction is generated according to the debugging request notification, the authorization debugging instruction includes a key, and the key generated each time the remote debugging channel is started is different.

[0033] Further, after receiving the security token including the reporting period sent by the server, the method further includes:

[0034] Collecting the performance parameters of the embedded device at preset intervals;

[0035] At each reporting period interval, a temporary connection is established with the server based on a short connection method of the HTTP protocol, and a heartbeat packet is sent to the server through the temporary connection while the performance parameters are sent out, so that the server can perform batch problem analysis based on the performance parameters and the operating status, and issue an alarm when confirming the existence of batch problems; wherein the batch problems are problems existing in the embedded devices of the same type or version.

[0036] Furthermore, the performance parameter includes at least one of CPU usage, memory occupancy, network traffic, and disk usage.

[0037] Furthermore, the short connection method based on the HTTP protocol and the communication data transmitted by the server through the temporary connection are encrypted using the TLS1.3 protocol.

[0038] In a second aspect, the present invention further provides an electronic device, wherein the electronic device is an embedded device, comprising:

[0039] a memory for storing program instructions; and

[0040] The processor is used to execute the program instructions to implement the steps of the network operation and maintenance method of the embedded device as described above.

[0041] In a third aspect, the present invention further proposes a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the networked operation and maintenance method of the embedded device as described above are implemented.

[0042] Compared with the prior art, the beneficial effects of the present invention are: a network operation and maintenance method of an embedded device, an electronic device and a computer-readable storage medium, comprising: in response to receiving a power-on instruction, establishing a temporary connection with a server based on a short connection method of the HTTP protocol, and sending a registration request to the server through the temporary connection; wherein the registration request includes the identity information of the embedded device; receiving a security token including a reporting cycle sent by the server, establishing a temporary connection with the server based on a short connection method of the HTTP protocol at each interval of the reporting cycle, and sending a heartbeat packet to the server through the temporary connection; wherein the security token is generated after the identity information is verified, and the heartbeat packet includes the running status of the embedded device; if an updated reporting cycle sent by the server is received, a temporary connection is established with the server based on a short connection method of the HTTP protocol at each interval of the updated reporting cycle, and a heartbeat packet is sent to the server through the temporary connection. It can be seen that the network operation and maintenance method, electronic device and computer-readable storage medium of the embedded device realize the heartbeat packet reporting of the embedded device through the HTTPS short connection mode, thereby greatly improving the concurrent processing capability of the system. The reporting frequency of the heartbeat packet is dynamically adjusted according to the cycle specified by the server, which realizes the efficient use of server resources, avoids the problems of resource waste and information lag, improves the flexibility and efficiency of network operation and maintenance of embedded devices, and optimizes the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0044] Figure 1 A schematic diagram of a flow chart of a first embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0045] Figure 2 A schematic diagram of a flow chart of a second embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0046] Figure 3 A schematic diagram of a flow chart of a third embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0047] Figure 4 A schematic diagram of a flow chart of a fourth embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0048] Figure 5 A schematic diagram of a flow chart of a fifth embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0049] Figure 6 A schematic diagram of a sixth embodiment of a networked operation and maintenance method for an embedded device of the present invention;

[0050] Figure 7 It is a schematic diagram of the structure of an electronic device in a hardware operating environment involved in an embodiment of the present invention. DETAILED DESCRIPTION

[0051] The scheme in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is only a part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0052] It should be noted that if the embodiments of the present invention involve directional indications (such as up, down, left, right, front, back, etc.), the directional indications are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0053] In addition, if there are descriptions involving "first", "second", etc. in the embodiments of the present invention, the descriptions of "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or suggesting their relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but they must be based on the ability of ordinary technicians in the field to implement them. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0054] See also Figure 1 As shown, it is a flow chart of the first embodiment of the network operation and maintenance method of the embedded device of the present invention. This embodiment describes in detail the steps of device registration and status declaration of the embedded device.

[0055] In this embodiment, the network operation and maintenance method of the embedded device includes:

[0056] Step S100: in response to receiving a power-on instruction, a temporary connection is established with a server based on a short connection mode of the HTTP protocol, and a registration request is sent to the server through the temporary connection.

[0057] Wherein, the registration request includes the identity information of the embedded device.

[0058] Specifically, the HTTP (Hypertext Transfer Protocol) protocol is an application layer protocol for transmitting hypermedia documents (such as HTML). It is the basis of Web data communication and is usually used to transmit hypertext from a Web server to a browser. The HTTP protocol is built on top of the TCP / IP protocol. The short connection mode of the HTTP protocol refers to the way in which the client's embedded device and the server immediately disconnect after completing a request-response during the communication process. In other words, a new connection needs to be established for each request, and the connection is closed immediately after the request is completed, without maintaining a long connection state. Compared with long connections, this method can reduce the resource usage of the server.

[0059] Specifically, one of the main reasons for establishing a temporary connection is to improve the efficiency and resource utilization of the system. In some cases, a persistent connection may take up more resources, especially when a large number of devices need to communicate with the server at the same time. By using a temporary connection, you can temporarily establish a connection for data transmission when needed, and close the connection immediately after the data transmission is completed to release resources, thereby reducing the occupation of system resources. In addition, using a temporary connection can also improve the security of the system. Persistent connections will remain connected for a long time, which may increase security risks, while temporary connections will be closed after each communication, reducing the security risks brought by persistent connections. Choosing to establish a temporary connection can manage resources more flexibly, improve system security, and adapt to the needs of short-term data transmission.

[0060] Specifically, after receiving the power-on command, the embedded device sends a registration request to the server through a temporary connection so that the server can identify and manage the device. The registration request includes the identity information of the device to ensure that the device can be accurately identified and connected to the system. The identity information of the embedded device includes information such as the device unique identifier, device model, and firmware version. Among them, the device unique identifier is used to uniquely identify and identify each device to ensure that each device can be accurately located and managed in the network. The device model is used to reflect the type and specifications of the device, which is helpful for device classification and management. The firmware version information is used to reflect the current software version of the device, including updates and improvements in functions, performance, and security, which is helpful for firmware management and upgrades. These identity information can help the server accurately identify, classify, and manage embedded devices as well as manage and maintain firmware versions.

[0061] Step S200: receiving a security token including a reporting period sent by the server, establishing a temporary connection with the server based on a short connection method of the HTTP protocol at intervals of the reporting period, and sending a heartbeat packet to the server through the temporary connection.

[0062] The security token is generated after the identity information is verified, and the heartbeat packet includes the operating status of the embedded device.

[0063] Specifically, the verification of identity information usually involves using an encryption algorithm to encrypt information such as the device's unique identifier, device model, and firmware version, and then sending the encrypted identity information to the server. The server uses the same encryption algorithm and key to decrypt the received identity information to verify whether the identity information of the embedded device is valid. If valid, it means that the identity information has passed the verification and a security token can be generated. A security token is a token generated by the server based on the identity information of the embedded device, which is used to identify the legitimacy of the device. The security token includes information about the reporting period, which can be a specific field or tag, used to tell the embedded device how often it should report a heartbeat packet.

[0064] Specifically, the heartbeat packet includes the operating status of the embedded device, which usually includes the device's on, off, sleep, etc.; the connection status of the device to the network or other devices, including successful connection, disconnection, reconnection, etc.; if the device is equipped with a sensor, the operating status may also include the sensor's working status, data collection, etc.; and the device's power supply, such as battery power, charging status, etc. These operating status can help monitor the device's operation, identify problems in a timely manner, and handle them accordingly. By sending heartbeat packets through a temporary connection, the embedded device can regularly report the operating status to the server to ensure that the device remains connected to the server and help the server keep track of the device's operation.

[0065] Step S300: if an updated reporting cycle sent by the server is received, a temporary connection is established with the server based on the short connection mode of the HTTP protocol at each interval of the updated reporting cycle, and a heartbeat packet is sent to the server through the temporary connection.

[0066] Specifically, if the server sends an updated reporting cycle, it means that the previously used reporting cycle has been changed, and the embedded device needs to report subsequent heartbeat packets according to the new reporting cycle, so as to dynamically adjust the reporting frequency of the heartbeat packets to avoid resource waste or information lag. Among them, the new reporting cycle is automatically adjusted according to the load of the server to achieve load balancing.

[0067] Specifically, the server connected to the embedded device is a distributed server. The distributed server architecture can improve the reliability and scalability of the system, share the request load, and provide better performance and fault tolerance. At the same time, the distributed server can also better cope with concurrent requests when large-scale devices are connected, ensuring the stability and reliability of the system. The distributed server architecture and the short connection mode based on the HTTPS protocol can greatly improve the concurrent processing capability of the system and support the access of massive embedded devices.

[0068] Compared with the prior art, the network operation and maintenance method of the embedded device in the embodiment of the present invention is a network operation and maintenance method with dynamic registration, secure communication and dynamic reporting. The heartbeat packet reporting of the embedded device is realized through the HTTPS short connection mode, thereby greatly improving the concurrent processing capability of the system. The reporting frequency of the heartbeat packet is dynamically adjusted according to the cycle specified by the server, realizing the efficient use of server resources, avoiding the problems of resource waste and information lag, improving the flexibility and efficiency of the network operation and maintenance of the embedded device, and optimizing the user experience.

[0069] See also Figure 2 As shown, it is a flow chart of the second embodiment of the networking operation and maintenance method of the embedded device of the present invention.

[0070] Compared with other embodiments of the networked operation and maintenance method for embedded devices, this embodiment adds a step of reporting abnormal events.

[0071] In this embodiment, in step 200, after receiving the security token including the reporting period sent by the server, the method further includes:

[0072] Step S401: If an abnormal event is detected and it is confirmed that the network connection with the server is stable, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and an abnormal report related to the abnormal event is sent to the server through the temporary connection.

[0073] Specifically, by sending an exception report, the embedded device can promptly notify the server of the occurrence of an abnormal event, so that the server can respond in time and take appropriate measures. The exception report includes detailed information related to the abnormal event, such as the type of abnormal event, the time of occurrence, and the event parameters, which helps the server to troubleshoot and solve problems. The server can perform remote fault handling based on the information in the exception report, such as sending instructions to the device to restart, adjust the configuration, etc., thereby improving the efficiency and accuracy of fault handling. Among them, the abnormal events include CPU too high, memory is about to run out, and disk failure.

[0074] Step S402: If an abnormal event is detected and it is confirmed that the network connection with the server is interrupted, an abnormal report related to the abnormal event is stored in the embedded device; when it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection method of the HTTP protocol, and the abnormal report stored in the embedded device is sent to the server in chronological order through the temporary connection.

[0075] The abnormal report includes the abnormal event type, occurrence time and event parameters.

[0076] Specifically, in order to transmit data in a network environment, a connection needs to be established. Without a connection, data cannot be effectively transmitted between the sender and the receiver. In network communication, establishing a connection is a basic operation of a communication protocol. By establishing a connection, reliable data transmission can be ensured, and necessary communication control and management can be performed. When establishing communication between a device and a server, network coverage is required to establish any type of connection, including temporary or persistent connections. Network coverage is the basis of communication, and communication is impossible without network coverage. Network interruption refers to the lack of network coverage between the device and the server, and the interruption of the network connection between the device and the server, resulting in the device being unable to communicate directly with the server. Network interruption may be caused by network failure, signal interference, server failure, etc.

[0077] Specifically, when the embedded device detects an abnormal event and confirms that the network connection with the server is interrupted, the abnormal report is stored in the local device to ensure that the device can record the occurrence of the abnormal event even when the network connection is interrupted, and ensure that the abnormal report will not be lost. Once it is confirmed that the network connection with the server is restored, the device will send the stored abnormal report to the server in chronological order through a temporary connection, so that the server can promptly understand the abnormal events that occurred during the network interruption. By storing the abnormal report and sending it after the network is restored, the system's ability to handle abnormal events can be improved, ensuring the integrity and timeliness of the abnormal report, which helps to discover and solve problems in a timely manner. In addition, the abnormal reports stored in the embedded device are sent in chronological order so that after the server receives the offline data, it can perform timestamp analysis to ensure the timing and integrity of the data.

[0078] Specifically, the abnormal event type is used to describe the specific type or category of the abnormal event, such as hardware failure, software error, network interruption, etc. It helps the server quickly understand the nature of the abnormal event and take corresponding processing measures. The occurrence time is used to record the specific occurrence time of the abnormal event so that the server can accurately track and analyze the time point when the abnormal event occurred. This is very important for troubleshooting, log analysis, and event tracing. The event parameter is the specific information or data of the abnormal event, including device status, error code, sensor data, etc. It provides a detailed context of the abnormal event, which helps the server to diagnose and solve problems. The specific event parameters depend on the specific application scenario and device function. It can be seen that the abnormal event type, occurrence time, and event parameters in the abnormal report provide key information about the abnormal event, which helps the server to diagnose and solve problems. The integrity and accuracy of these parameters are crucial for the server to perform effective troubleshooting and problem solving.

[0079] It should be noted that step S401 and step S402 are two different exception report uploading methods. Step S401 corresponds to the exception report uploading under the premise that the network connection between the embedded device and the server is stable; step S402 corresponds to the exception report uploading under the premise that the network connection between the embedded device and the server is interrupted. There is no order between step S401 and step S402, and either one can be implemented.

[0080] The networked operation and maintenance method for embedded devices according to the embodiment of the present invention can ensure that abnormal events are reported to the server in a timely and accurate manner regardless of whether the network connection is stable, thereby improving the system's ability to handle abnormal events.

[0081] See also Figure 3 As shown, it is a flow chart of the third embodiment of the networking operation and maintenance method of the embedded device of the present invention.

[0082] Compared with other embodiments of the network operation and maintenance method for embedded devices, this embodiment adds a step of ensuring the integrity of the uploaded heartbeat packet.

[0083] In this embodiment, in step S200, after receiving the security token including the reporting period sent by the server, the step further includes:

[0084] Step S501: if it is detected that the network connection with the server is interrupted, the heartbeat packets of the embedded device collected at intervals of the reporting period are stored in the embedded device.

[0085] Specifically, when the network connection is interrupted, the device stores the collected heartbeat packet data locally so that the heartbeat packet data can be sent to the server after the network is restored.

[0086] Step S502: When it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and the heartbeat packets stored in the embedded device are sent to the server in chronological order through the temporary connection.

[0087] Specifically, after the network connection is restored, the device can send the previously collected heartbeat packet data to the server in a timely manner so that the server can obtain the complete heartbeat packet data for status monitoring and analysis.

[0088] Specifically, sending the heartbeat packets stored locally in chronological order can ensure that the heartbeat packets received by the server are processed in the order sent by the device. The server analyzes the received heartbeat packets in sequence to better understand the operating status and performance change trends of the device, which helps to discover potential problems and anomalies in a timely manner.

[0089] The networking operation and maintenance method of the embedded device of the embodiment of the present invention can ensure that the heartbeat packet data collected by the embedded device will not be lost even when the network connection is interrupted, and can send these data to the server in time after the network is restored, thereby ensuring the integrity of the heartbeat packet data and the accuracy and predictability of system status monitoring.

[0090] See also Figure 4 As shown, it is a flow chart of the fourth embodiment of the networking operation and maintenance method of the embedded device of the present invention.

[0091] Compared with other embodiments of the networked operation and maintenance method for embedded devices, this embodiment adds the steps of remote task issuance and execution.

[0092] In this embodiment, in step S200, after receiving the security token including the reporting period sent by the server, the step further includes:

[0093] Step S601: If a temporary connection is established with the server through a short connection method based on the HTTP protocol and a task instruction issued by the server is received, a request authorization notification is issued.

[0094] Specifically, the authorization request notification is sent to the end user (such as notifying the user via SMS or mobile App) in order to request authorization from the user. Only after the user's authorization can the next task be executed. This user authorization mechanism can perform more sophisticated and detailed permission management for users, allowing administrators or system designers to set personalized permissions for users based on their specific needs and roles, so as to achieve fine control over system resources and functions. This user authorization mechanism fully respects the rights and interests of users and enhances the user's trust in remote equipment maintenance.

[0095] Step S602: When the authorization execution instruction is received, the task included in the task instruction is executed.

[0096] The authorization execution instruction is generated according to the authorization request notification, and the task includes software update and configuration modification.

[0097] Specifically, the authorization execution instruction is issued by the user through the terminal. With the authorization of the user, the embedded device can perform software updates and configuration modifications in a timely manner to ensure that the device is always in the latest working state.

[0098] Step S603: If it is confirmed that a temporary connection is established with the server in a short connection mode based on the HTTP protocol, the execution progress and execution result of the task are sent to the server.

[0099] Specifically, reporting the execution progress and results of the task to the server enables the server to understand the status of task execution in a timely manner, thereby realizing the management and monitoring of remote task execution.

[0100] The networked operation and maintenance method of the embedded device of the embodiment of the present invention realizes the management and monitoring of remote task issuance and task execution, and adopts a fine-grained user authorization mechanism to ensure that sensitive operations are permitted by users, thereby improving user trust and favorability.

[0101] See also Figure 5 As shown, it is a flow chart of the fifth embodiment of the networking operation and maintenance method of the embedded device of the present invention.

[0102] Compared with other embodiments of the networked operation and maintenance method for embedded devices, this embodiment adds a remote debugging step.

[0103] In this embodiment, in step S200, after receiving the security token including the reporting period sent by the server, the step further includes:

[0104] Step S701: If a temporary connection is established with a server through a short connection method based on the HTTP protocol, and a debugging request instruction is received from the server, a debugging request notification is issued.

[0105] Specifically, the main reasons for requesting debugging include troubleshooting, performance optimization, function verification, and remote support. For example, when a device fails or behaves abnormally, requesting debugging can help developers remotely connect to the device and collect relevant debugging information to quickly locate and solve the problem, greatly saving labor costs. In addition, by requesting debugging, you can monitor the performance indicators of the device, such as response time, resource utilization, etc., in order to optimize and adjust performance. It can be seen that requesting debugging is an important operation to ensure the normal operation of the device and improve development efficiency.

[0106] Step S702: When the authorization debugging instruction is received, the remote debugging channel is started to perform remote debugging.

[0107] The authorization debugging instruction is generated according to the debugging request notification, and the authorization debugging instruction includes a key, and the key generated each time the remote debugging channel is started is different.

[0108] Specifically, after the device starts a secure remote debugging channel, the operation and maintenance personnel are allowed to access logs, remote debugging ports, etc. A key is generated synchronously during remote debugging to effectively prevent unauthorized access and potential security threats. This security mechanism ensures that each remote debugging channel startup requires authorization, and only authorized users with the corresponding key can perform remote debugging operations, thereby protecting the security of the device and system. In addition, generating different keys each time also increases security, because even if a key is leaked or cracked, it will only affect the current remote debugging channel and will not affect the security of other channels. This dynamic key generation method provides an additional layer of security and helps prevent potential security threats.

[0109] The networked operation and maintenance method of the embedded device of the embodiment of the present invention ensures that the embedded device can safely and reliably start the remote debugging channel and perform remote debugging. The purpose of remote debugging is to solve problems or abnormal situations that occur during the operation of the embedded device. Through remote debugging, the operating status of the device can be monitored in real time, debugging information can be collected, and troubleshooting and problem analysis can be performed.

[0110] See also Figure 6 As shown, it is a flow chart of the sixth embodiment of the networking operation and maintenance method of the embedded device of the present invention.

[0111] Compared with other embodiments of the networked operation and maintenance method for embedded devices, this embodiment adds the steps of device performance monitoring and analysis, and batch problem detection.

[0112] In this embodiment, in step S200, after receiving the security token including the reporting period sent by the server, the step further includes:

[0113] Step S801: collecting performance parameters of the embedded device at preset intervals.

[0114] Specifically, performance parameters are indicators used to measure the efficiency and ability of a device when performing a specific task or operation. Regularly collecting performance parameters of embedded devices helps monitor the health of the device, perform fault diagnosis and analysis, optimize performance, and implement predictive maintenance, thereby improving the stability and reliability of the device.

[0115] Step S802: Establishing a temporary connection with the server based on the short connection method of the HTTP protocol at each interval of the reporting cycle, and sending a heartbeat packet to the server through the temporary connection while sending the performance parameters together, so that the server can perform batch problem analysis based on the performance parameters and the operating status, and issue an alarm when confirming that there is a batch problem.

[0116] The batch problems are problems existing in the embedded devices of the same type or version.

[0117] Specifically, batch problem analysis can identify common problems of embedded devices of the same type or version, which helps to find and solve these problems in a timely manner and improve the overall stability and reliability of the equipment. Batch problem analysis can also help the server to centrally monitor and process the performance parameters and operating status of a large number of devices, improve the efficiency of problem discovery and resolution, and reduce the need for manual intervention. Batch problem analysis can also predict the problems that may occur in embedded devices of the same type or version, which helps to implement preventive maintenance measures, reduce equipment failure rates, and extend equipment life.

[0118] Specifically, when the preset cycle and the reporting cycle are the same, at the beginning of each cycle, the embedded device will collect the current performance parameters and send the performance parameters and the heartbeat packet to the server through a temporary connection. In this way, the server can receive and analyze the performance data and operating status of the device in real time to achieve timely monitoring and analysis. When the preset cycle and the reporting cycle are different, the performance parameters of the embedded device are collected regularly according to the preset cycle and stored in the device. When the reporting cycle is reached, the device will establish a temporary connection with the server based on the short connection method of the HTTP protocol, and send the stored performance parameters and the collected heartbeat packet to the server. In this way, the server can perform batch problem analysis based on the received performance parameters and operating status to achieve regular performance monitoring and analysis.

[0119] In some embodiments of the present application, the performance parameter includes at least one of CPU usage, memory occupancy, network traffic, and disk usage.

[0120] Specifically, CPU usage indicates the workload of the CPU during a specific period of time. High CPU usage indicates that the system is overloaded and may cause performance degradation or delayed response time. Memory usage refers to the amount of memory currently used by the system or application. High memory usage may cause system slowdowns, application crashes, or excessive swap space usage. Network traffic refers to the amount of data transmitted over the network. Monitoring network traffic can help evaluate the usage of network bandwidth and detect network congestion or anomalies. Disk usage indicates the usage of disk storage space. High disk usage may lead to insufficient disk space, affect the normal operation of the system, or cause data loss. Monitoring and analysis of these performance parameters can help evaluate the health of the system, discover performance bottlenecks, optimize resource allocation, and predict the capacity requirements of the system. By monitoring and analyzing these performance parameters in real time, timely measures can be taken to optimize system performance, improve resource utilization efficiency, and ensure system stability and reliability.

[0121] In some embodiments of the present application, the short connection method based on the HTTP protocol and the communication data transmitted by the server through a temporary connection are encrypted using the TLS1.3 protocol.

[0122] Specifically, using the TLS1.3 protocol to encrypt communication data is a very safe and reliable practice. The TLS (Transport Layer Security) protocol is an encrypted communication protocol used to ensure the security of communications on the network. The TLS1.3 protocol is the latest version of the TLS protocol, which provides more powerful encryption algorithms and more advanced security features, including a faster handshake process, more secure key exchange, and more powerful encryption algorithms. By using the TLS1.3 protocol to encrypt communication data, the confidentiality and integrity of the data can be effectively protected, and the data can be prevented from being stolen or tampered with during transmission. This encryption mechanism can ensure that the communication data is fully protected during transmission, thereby improving the security of the system, protecting the user's privacy information, and preventing possible network attacks and data leaks.

[0123] The networked operation and maintenance method of the embedded device of the embodiment of the present invention can monitor the performance indicators and operation status of the device in real time by regularly reporting the performance parameters and operation status of the embedded device, which helps to promptly discover problems such as device performance degradation and abnormal resource utilization. The server performs batch problem analysis based on these performance parameters and operation status, and can identify common problems of devices of the same type or version, and issue an alarm when a problem is confirmed. This helps to quickly diagnose and solve device failures, reducing downtime and maintenance costs.

[0124] The networked operation and maintenance method of the embedded device in the embodiment of the present invention is applied to the networked operation and maintenance system of the embedded device, and mainly includes the following components: embedded device end software module, distributed server, data analysis module and operation and maintenance management platform. Through the collaborative cooperation of these four components, the following goals can be achieved:

[0125] 1. Provide real-time and reliable equipment status monitoring mechanism.

[0126] 2. It has the functions of remote fault diagnosis and abnormality reporting.

[0127] 3. Ensure data integrity in the event of network instability.

[0128] 4. Secure remote task execution and debugging mechanism.

[0129] 5. Collect comprehensive device performance data to facilitate firmware stability analysis.

[0130] 7. Optimize server resource utilization and support large-scale device access.

[0131] 8. Analyze the equipment operation status by model and version to detect batch problems in time.

[0132] 9. Dynamically adjust device reporting strategies to balance information real-time and system load.

[0133] The following specifically describes the process of using the networked operation and maintenance method of the embedded device according to the embodiment of the present invention to achieve the above-mentioned goal:

[0134] (1) Equipment registration and status reporting

[0135] -When the device is started for the first time, a registration request is sent to the distributed server via an HTTPS short connection, which contains information such as the device's unique identifier, device model, and firmware version.

[0136] -The server verifies the device's identity information and generates a security token and returns it to the device.

[0137] -The device periodically sends heartbeat packets to the server through HTTPS short connection according to the reporting cycle returned by the server, including basic operating status.

[0138] -The server returns the latest reporting cycle setting in the response, and the device adjusts the next reporting time accordingly.

[0139] (2) Abnormal event reporting

[0140] -When the device detects an abnormal event (such as high CPU, memory exhaustion, disk failure, etc.), it immediately sends an abnormal report to the server via HTTPS short connection.

[0141] -Exception reports contain detailed information such as event type, occurrence time, and related event parameters.

[0142] -After the server receives the abnormal report from the device, the data analysis module analyzes it and sends an alert to the administrator if necessary.

[0143] (3) Network exception handling

[0144] -When the device detects a network interruption, it caches the operating status information and abnormal events in local storage.

[0145] -After the network is restored, the device automatically reports the cached information to the server via HTTPS short connection in chronological order.

[0146] -After receiving offline data, the server performs timestamp analysis to ensure the timing and integrity of the data.

[0147] (4) Remote task execution

[0148] -Operation and maintenance personnel issue task instructions (such as software updates, configuration modifications, etc.) to the equipment through the management platform.

[0149] -The device receives the task instruction the next time it establishes a short HTTPS connection with the server.

[0150] -After receiving the task, the device first requests authorization from the user (such as through SMS or mobile App notification).

[0151] -After user authorization, the device executes the task and provides feedback on the execution progress and results the next time it connects.

[0152] (5) Remote debugging

[0153] -Operation and maintenance personnel can request to enable remote debugging mode of the device.

[0154] -The device receives a debug request the next time it connects to the server, notifies the user and waits for authorization.

[0155] -After user authorization, the device starts a secure remote debugging channel, allowing operation and maintenance personnel to access logs, remote debugging ports, etc.

[0156] - The debugging session uses a temporarily generated key to ensure security.

[0157] (6) Equipment performance monitoring and analysis

[0158] -The device regularly collects performance indicators such as CPU usage, memory usage, network traffic, and disk usage.

[0159] -The collected performance parameters and heartbeat packets are reported to the server through HTTPS short connection.

[0160] -The server transmits the data to the data analysis module for the following analysis:

[0161] 1. Single device performance trend analysis;

[0162] 2. Performance comparison of equipment of the same model;

[0163] 3. Analysis of performance differences between different firmware versions;

[0164] 4. Identification of abnormal behavior patterns.

[0165] -Analysis results are used to generate performance reports, stability assessments, and early warnings of potential problems.

[0166] (7) Dynamic reporting strategy

[0167] -Administrators can set the reporting cycle for different device types, models or versions through the operation and maintenance (Web) management platform.

[0168] -When responding to the device heartbeat, the server returns the latest reporting period setting to the device.

[0169] -The device adjusts its reporting frequency according to the new reporting period received.

[0170] -The system automatically adjusts the recommended reporting cycle based on the server load to achieve load balancing.

[0171] (8) Batch Problem Detection

[0172] -The data analysis engine aggregates and analyzes the operating data of devices of the same type and version.

[0173] -Identify unusual patterns and potential problems through machine learning algorithms.

[0174] -When a common problem is found in a certain model or version of equipment, the system automatically generates an alert.

[0175] - Provide visual problem tracking and version comparison tools to assist operation and maintenance personnel in quickly locating and resolving batch problems.

[0176] (9) Security Mechanism

[0177] -Use TLS1.3 protocol to encrypt all HTTPS communication data.

[0178] - Encryption of sensitive operations using temporary session keys.

[0179] -Implement a fine-grained user authorization mechanism to ensure that sensitive operations are authorized by the user.

[0180] The improved embedded device networking operation and maintenance system using the embedded device networking operation and maintenance method according to the embodiment of the present invention has the following advantages:

[0181] 1. Real-time monitoring: Through regular status reporting, the operating status of the equipment can be mastered in real time, which improves the transparency of equipment management.

[0182] 2. Quick response: The real-time reporting mechanism for abnormal events enables operation and maintenance personnel to discover and handle problems in the first place, greatly shortening the fault response time.

[0183] 3. Data integrity: The network exception handling mechanism ensures the integrity of device status and event data even when the network is unstable.

[0184] 4. Remote maintenance: Remote task execution and debugging functions greatly reduce the need for on-site maintenance, improve operation and maintenance efficiency, and reduce maintenance costs.

[0185] 5. Performance optimization: Through comprehensive performance data collection and analysis, it provides strong support for firmware optimization and stability improvement.

[0186] 6. Safe and reliable: The implementation of multiple security mechanisms ensures the security of remote operation and effectively prevents illegal access and data leakage.

[0187] 7. User-friendly: The user authorization mechanism fully respects the rights and interests of users and enhances users' trust in remote maintenance of equipment.

[0188] 8. Scalability: The distributed server architecture and HTTPS short connection mode greatly improve the system's concurrent processing capabilities and support the access of massive devices.

[0189] 9. Resource optimization: The dynamic reporting strategy realizes the efficient use of server resources, reducing the system load while ensuring the real-time nature of the data.

[0190] 10. Batch problem detection: Through the aggregate analysis of data from similar devices, batch problems can be quickly discovered and resolved, improving product quality and user satisfaction.

[0191] 11. Predictive maintenance: By analyzing the data reported by the equipment, the system has predictive maintenance capabilities and can take preventive measures before the problem is perceived by the user.

[0192] 12. Version management optimization: Through performance comparison and analysis of different versions, data support is provided for product iteration and version management, accelerating the product optimization cycle.

[0193] It can be seen that the networked operation and maintenance method and system of embedded devices provided by the embodiments of the present invention effectively solve the various challenges faced in the operation and maintenance of traditional embedded devices, and provide strong technical support for improving equipment reliability, extending equipment life, and optimizing user experience. The networked operation and maintenance system of embedded devices of the present invention can be widely used in remote monitoring, fault diagnosis and security event analysis of smart network camera door locks, alarms and other devices in security systems; it can also be used for remote monitoring, equipment maintenance and environmental trend analysis of smart home devices, industrial Internet of Things, medical equipment, automotive electronics, smart cities, agricultural Internet of Things, renewable energy equipment such as solar panels and wind turbines, retail vending machines, air quality monitoring stations and water quality monitoring equipment.

[0194] The following is an embodiment of the electronic device provided by the present invention. The embodiment of the electronic device and the embodiment of the network operation and maintenance method of the above-mentioned embedded device belong to the same concept, and the details not described in detail in the embodiment of the electronic device can refer to the embodiment of the network operation and maintenance method of the above-mentioned embedded device.

[0195] See also Figure 7 As shown, it is a schematic diagram of the structure of an electronic device in a hardware operating environment involved in an embodiment of the present invention.

[0196] In this embodiment, an electronic device is an embedded device, including:

[0197] Memory 1005, used to store program instructions; and

[0198] Processor 1001 is used to execute the program instructions to implement the steps of the network operation and maintenance method of the embedded device as described above.

[0199] The electronic device of the embodiment of the present invention can be a computing device such as a desktop computer, a notebook, a palm computer, and a server. Figure 7 As shown, the electronic device may include: a processor 1001 (e.g., a CPU), a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit, such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. The network interface 1004 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a disk memory. The memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0200] Those skilled in the art will understand that Figure 7 The electronic device structure shown in the figure does not constitute a limitation of the electronic device, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.

[0201] like Figure 7 As shown, the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module and a computer program.

[0202] exist Figure 7 In the electronic device shown, the network interface 1004 is mainly used to connect to the background server and communicate data with the background server; the user interface 1003 is mainly used to connect to the client (user end) and communicate data with the client; and the processor 1001 can be used to call the computer program stored in the memory 1005. When the computer program is called and executed by the processor 1001, the steps of the above-mentioned network operation and maintenance method of the embedded device are implemented.

[0203] The following is an embodiment of the computer-readable storage medium provided by the present invention. The embodiment of the computer-readable storage medium and the above-mentioned network operation and maintenance method of the embedded device and the embodiment of the electronic device belong to the same concept, and the details not described in detail in the embodiment of the computer-readable storage medium can refer to the above-mentioned network operation and maintenance method of the embedded device and the embodiment of the electronic device.

[0204] In this embodiment, a computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the steps of the networked operation and maintenance method for an embedded device as described above.

[0205] Since the electronic device and computer-readable storage medium of the present invention can both implement the steps of the above-mentioned network operation and maintenance method of the embedded device, they at least have all the beneficial effects brought by the technical solutions of the above-mentioned network operation and maintenance method of the embedded device, which will not be described one by one here.

[0206] The above description is only a partial or preferred embodiment of the present invention. Neither the text nor the drawings can limit the scope of protection of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the overall concept of the present invention, or direct / indirect application in other related technical fields are included in the scope of protection of the present invention.

[0207] 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, CDROM, optical storage, etc.) containing computer-usable program codes.

[0208] The present application is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to 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 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.

[0209] 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.

[0210] 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.

[0211] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. A network operation and maintenance method for an embedded device, characterized in that: include: In response to receiving the power-on instruction, a temporary connection is established with the server based on a short connection mode of the HTTP protocol, and a registration request is sent to the server through the temporary connection; wherein the registration request includes the identity information of the embedded device; Receive a security token including a reporting period sent by the server, establish a temporary connection with the server based on a short connection method of the HTTP protocol at each interval of the reporting period, and send a heartbeat packet to the server through the temporary connection; wherein the security token is generated after the identity information is verified, and the heartbeat packet includes the operating status of the embedded device; If an updated reporting cycle sent by the server is received, a temporary connection is established with the server based on a short connection mode of the HTTP protocol at intervals of the updated reporting cycle, and a heartbeat packet is sent to the server through the temporary connection.

2. The network operation and maintenance method of an embedded device according to claim 1, characterized in that: After receiving the security token including the reporting period sent by the server, the method further includes: If an abnormal event is detected and it is confirmed that the network connection with the server is stable, a temporary connection is established with the server based on a short connection method of the HTTP protocol, and an abnormality report related to the abnormal event is sent to the server through the temporary connection; If an abnormal event is detected and it is confirmed that the network connection with the server is interrupted, an abnormal report related to the abnormal event is stored in the embedded device; when it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and the abnormal report stored in the embedded device is sent to the server in chronological order through the temporary connection; The abnormal report includes the abnormal event type, occurrence time and event parameters.

3. The network operation and maintenance method of an embedded device according to claim 1, characterized in that: After receiving the security token including the reporting period sent by the server, the method further includes: If it is detected that the network connection with the server is interrupted, the heartbeat packets of the embedded device collected at each interval of the reporting period are stored in the embedded device; When it is confirmed that the network connection with the server is restored, a temporary connection is established with the server based on the short connection mode of the HTTP protocol, and the heartbeat packets stored in the embedded device are sent to the server in chronological order through the temporary connection.

4. The network operation and maintenance method of an embedded device according to claim 1, characterized in that: After receiving the security token including the reporting period sent by the server, the method further includes: If a task instruction issued by the server is received through a temporary connection established with the server in a short connection mode based on the HTTP protocol, a request authorization notification is issued; When receiving the authorization execution instruction, executing the task included in the task instruction; wherein the authorization execution instruction is generated according to the authorization request notification, and the task includes software update and configuration modification; If it is confirmed that a temporary connection is established with the server in a short connection mode based on the HTTP protocol, the execution progress and execution result of the task are sent to the server.

5. The network operation and maintenance method of an embedded device according to claim 1, characterized in that: After receiving the security token including the reporting period sent by the server, the method further includes: If a debugging request instruction is received from the server through a temporary connection established with the server in a short connection mode based on the HTTP protocol, a debugging request notification is issued; When receiving the authorization debugging instruction, the remote debugging channel is started for remote debugging; wherein the authorization debugging instruction is generated according to the debugging request notification, the authorization debugging instruction includes a key, and the key generated each time the remote debugging channel is started is different.

6. The network operation and maintenance method of embedded devices according to claim 1, characterized in that: After receiving the security token including the reporting period sent by the server, the method further includes: Collecting the performance parameters of the embedded device at preset intervals; At each interval of the reporting cycle, a temporary connection is established with the server based on the short connection method of the HTTP protocol, and a heartbeat packet is sent to the server through the temporary connection while the performance parameters are sent out, so that the server can perform batch problem analysis based on the performance parameters and the operating status, and issue an alarm when confirming the existence of batch problems; wherein the batch problems are problems existing in the embedded devices of the same type or version.

7. The network operation and maintenance method of an embedded device according to claim 6, characterized in that: The performance parameter includes at least one of CPU usage, memory occupancy, network traffic, and disk usage.

8. The network operation and maintenance method of an embedded device according to any one of claims 1 to 6, characterized in that: The short connection method based on the HTTP protocol and the communication data transmitted by the server through a temporary connection are both encrypted using the TLS1.3 protocol.

9. An electronic device, the electronic device being an embedded device, characterized in that: include: A memory for storing program instructions; as well as A processor is used to execute the program instructions to implement the steps of the network operation and maintenance method of an embedded device as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, the steps of the networked operation and maintenance method for an embedded device as described in any one of claims 1 to 8 are implemented.

Images