WO2021208564A1 - 设备故障修复方法、装置、电子设备及存储介质 - Google Patents

设备故障修复方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2021208564A1
WO2021208564A1 PCT/CN2021/074410 CN2021074410W WO2021208564A1 WO 2021208564 A1 WO2021208564 A1 WO 2021208564A1 CN 2021074410 W CN2021074410 W CN 2021074410W WO 2021208564 A1 WO2021208564 A1 WO 2021208564A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
uboot
network configuration
abnormal state
configuration information
Prior art date
Application number
PCT/CN2021/074410
Other languages
English (en)
French (fr)
Inventor
张凯军
Original Assignee
杭州海康威视数字技术股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 杭州海康威视数字技术股份有限公司 filed Critical 杭州海康威视数字技术股份有限公司
Publication of WO2021208564A1 publication Critical patent/WO2021208564A1/zh
Priority to US18/046,676 priority Critical patent/US20230061066A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0793—Remedial or corrective actions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N17/00—Diagnosis, testing or measuring for television systems or their details
    • H04N17/002—Diagnosis, testing or measuring for television systems or their details for television cameras
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/085—Retrieval of network configuration; Tracking network configuration history
    • H04L41/0853—Retrieval of network configuration; Tracking network configuration history by actively collecting configuration information or by backing up configuration information

Definitions

  • This application relates to the technical field of equipment maintenance, in particular to equipment failure repair methods, devices, electronic equipment, and storage media.
  • the video surveillance system is composed of camera, transmission, control, display and recording processes.
  • the front-end equipment such as cameras, as the main body of the camera, is the core part of the video surveillance system.
  • the stability and reliability of the front-end equipment largely determines the overall performance of the video surveillance system.
  • the embodiments of the present application propose equipment failure repair methods, devices, electronic equipment, and storage media to realize remote repair of equipment failures.
  • the technical solutions of the embodiments of the present application are implemented as follows:
  • an embodiment of the present application provides a method for repairing a device failure.
  • the method includes: after the device is restarted, detecting whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart; when the device is detected When the abnormal state file, read the Uboot network configuration information saved corresponding to the abnormal state file; according to the read Uboot network configuration information, initiate a communication connection with the file transfer protocol FTP server; when the communication connection with the FTP server is successfully established, Send an upgrade request to the FTP server; repair and upgrade the device in response to the software package returned by the FTP server.
  • the initiating communication connection with the FTP server according to the read Uboot network configuration information includes: according to the device IP address, device gateway, subnet mask, and FTP server in the Uboot network configuration information Address the Uboot network configuration and initiate a communication connection with the FTP server.
  • the sending an upgrade request to the FTP server includes: sending an upgrade request carrying device identification information to the FTP server, so that the FTP server queries the SVN server address that publishes the software package according to the device identification information .
  • the detecting whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart includes: detecting whether there is a flash memory that is saved by the CPU due to a device failure detected before the restart Abnormal state file; said reading the Uboot network configuration information stored corresponding to the abnormal state file includes: reading the Uboot network configuration information stored corresponding to the abnormal state file from the flash memory.
  • the device restart is: the front-end device restarts.
  • the abnormal state file and the Uboot network configuration information are: when a device failure is detected, the saved abnormal state file and Uboot network configuration information of the device when the failure occurs.
  • the detecting that the device is malfunctioning includes: detecting that the business process of the device is exited, restarting the business process, and determining that the device is malfunctioning if it is detected that the business process fails to restart for a preset number of consecutive times.
  • the detecting that the business process exits includes: periodically sending a keep-alive packet to the business process, and if the keep-alive packet returned by the business process is not received within the preset keep-alive waiting time, then Determine the business process to exit.
  • the detection of the failure of restarting the business process for a predetermined number of consecutive times includes: sending a startup completion query packet to the business process every preset startup query duration, if a preset number of startup completion query packets are continuously sent , But does not receive any startup completion package from the business process, it is determined that the business process restart has failed.
  • the Uboot network configuration information includes: device IP address, device gateway, subnet mask, and FTP server address.
  • an embodiment of the present application provides a method for repairing a device failure.
  • the method includes: after the device is powered on, detecting whether there is an abnormal state file saved by the processor due to the device failure in the device; When the abnormal state file of the device is detected, obtain the universal boot loader module Uboot network configuration information of the device, wherein the Uboot network configuration information includes the address of the server; according to the address of the server in the Uboot network configuration information , Initiate a communication connection with the server; after successfully establishing a communication connection with the server, send an upgrade request to the server; repair and upgrade the device in response to the software package returned by the server.
  • an embodiment of the present application provides a device for repairing equipment failures.
  • the device includes: an abnormal state file detection module for detecting whether the equipment is processed due to the equipment failure after the equipment is powered on.
  • Uboot network configuration information acquisition module which is used to obtain the universal boot loader module Uboot network configuration information of the device when the device abnormal state file is detected, wherein the Uboot network configuration information includes The address of the server; a communication connection initiation module for initiating a communication connection with the server according to the address of the server in the Uboot network configuration information; an upgrade request sending module for when a communication connection with the server is successfully established After that, an upgrade request is sent to the server; a repair and upgrade execution module is used to repair and upgrade the device in response to the software package returned by the server.
  • an embodiment of the present application provides an electronic device including a processor and a memory; the memory is used to store a computer program; when the processor is configured to execute the program stored in the memory, Realize any device fault repair method described in this application.
  • an embodiment of the present application provides a computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any of the The equipment failure repair method described.
  • FIG. 1 is a flowchart of a method for repairing a device fault according to an embodiment of the application
  • FIG. 2 is a flowchart of a method for repairing a device fault according to another embodiment of the application
  • FIG. 3 is a flowchart of a method for repairing a device fault according to another embodiment of this application.
  • FIG. 4 is a schematic structural diagram of a device fault repairing device provided by an embodiment of the application.
  • FIG. 5 is a schematic structural diagram of a device fault repair system provided by an embodiment of the application.
  • FIG. 6 is a flowchart of a method for repairing a device failure provided by another embodiment of the application.
  • Uboot Universal Boot Loader, universal boot loader module
  • Uboot is a boot loader module mainly used in embedded terminals.
  • FTP File Transfer Protocol
  • TCP Transmission Control Protocol
  • IP Internet Protocol, Internet Protocol
  • Front-end equipment refers to all types of equipment distributed at the detection site. In this application, it refers to cameras and related equipment.
  • Daemon A process running in the device that provides system services.
  • Business process the process of realizing specific software functions of the device, such as preview, storage, communication and other business functions.
  • SVN is a software version control system.
  • an embodiment of the present application provides a method for repairing equipment failures.
  • the flowchart is shown in Fig. 1, and the specific steps are as follows:
  • Step 101 After the device is restarted, detect whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart.
  • the method for repairing device failures in the embodiments of the present application may be implemented by a front-end device.
  • the front-end device may be a camera or a device related to a camera.
  • Step 102 When the abnormal state file of the device is detected, read the Uboot network configuration information saved corresponding to the abnormal state file.
  • Uboot network configuration information includes: device IP address, device gateway, subnet mask, and FTP server address.
  • one device corresponds to one Uboot network configuration information.
  • Step 103 According to the read Uboot network configuration information, initiate a communication connection with the FTP server.
  • Step 104 After successfully establishing a communication connection with the FTP server, send an upgrade request to the FTP server.
  • Step 105 Repair and upgrade the device in response to the software package returned by the FTP server.
  • FIG. 2 is a flowchart of a method for repairing a device fault according to another embodiment of the application, and the specific steps are as follows:
  • Step 201 When a failure of the device is detected, save the abnormal state file and Uboot network configuration information of the device when the failure occurs.
  • detecting that the device has failed includes: detecting that the service process of the device has exited, restarting the service process, and if it is detected that the service process fails to restart for a preset number of consecutive times, it is determined that the device has failed.
  • detecting the exit of the business process includes: periodically sending a keep-alive packet to the business process, and if the keep-alive packet returned by the business process is not received within the preset keep-alive waiting time, it is determined that the business process exits .
  • detecting the failure of restarting the business process for a preset number of consecutive times includes: sending a startup completion query packet to the business process every preset startup query duration, if a preset number of startup completion query packets are continuously sent but not received If any start-up completion packet replies to the business process, it is determined that the business process has failed to restart.
  • Step 202 After the device is restarted, detect whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart.
  • Step 203 When the abnormal state file of the device is detected, read the Uboot network configuration information saved corresponding to the abnormal state file.
  • Step 204 Initiate a communication connection with the FTP server according to the read Uboot network configuration information.
  • Step 205 Send an upgrade request carrying device identification information to the FTP server, so that the FTP server queries the SVN (Subversion) server address that publishes the software package according to the device identification information, and downloads the latest software package of the device from the corresponding SVN server.
  • SVN Subversion
  • Step 206 Repair and upgrade the device in response to the software package returned by the FTP server.
  • the device is determined to be abnormal by detecting that the business process exits, and then, if the failure of the business process restart is detected consecutively for a preset number of times, it is determined that the device is faulty, thereby realizing an accurate determination of the device failure; and, according to The device identification information is queried to the address of the SVN server that releases the software package, so that the latest software package of the device can be accurately downloaded.
  • FIG. 3 is a flowchart of a method for repairing a device failure provided by another embodiment of the application, and the specific steps are as follows:
  • Step 301 The device is started, and a Socket connection is established between the daemon process of the device and the business process.
  • Step 302 The daemon periodically sends a keeplive (keep-alive) packet to the business process through the Socket connection, and waits for the business process to reply.
  • keeplive keep-alive
  • the daemon process sends a keeplive packet to the business process every 1s (second).
  • Step 303 If the daemon process does not receive the keeplive packet from the business process within the preset keep-alive waiting time, it is determined that the business process has exited, restarts the business process, and sends a start-up completion to the business process every preset start-up query duration Ask about the package.
  • the start query duration is, for example, 5s.
  • Step 304 The service process receives the startup completion inquiry packet, and checks whether the startup completion flag is 1, if it is 1, then the daemon process returns the startup completion packet, and if it is 0, the startup completion packet is returned.
  • Step 305 If the daemon process receives the incomplete startup packet from the business process for a preset number of times, it is determined that the device is faulty, and the daemon process saves the abnormal state file of the device and the device Uboot network configuration information to the Flash (flash memory) of the device, and at the same time Reboot the device.
  • the preset number 6.
  • Uboot network configuration information includes: device IP address, device gateway, subnet mask and FTP server address, etc.
  • Step 306 After the device restarts, the Uboot module is started.
  • the Uboot module reads the abnormal state file of the device from the Flash and enters the abnormal repair mode, reads the Uboot network configuration information of the device from the Flash, and performs the Uboot network configuration according to the Uboot network configuration information.
  • the Uboot module has two working modes, namely the normal mode and the abnormal repair mode.
  • the Linux kernel is directly loaded after the boot is completed in the normal mode.
  • Step 307 The Uboot of the device establishes an FTP connection with the FTP server according to the FTP server address in the Uboot network configuration information, and sends an upgrade request carrying the device identification information to the FTP server.
  • the device identification information carried in the upgrade request includes: device IP address, device MAC address, and device model.
  • Step 308 The FTP server receives the upgrade request, adds the device identification information in the request to the faulty device table, and finds the SVN server in the correspondence relationship between the device model saved by itself and the SVN server address of the software package according to the device model Address, download the latest software package of the device from the corresponding SVN server.
  • the FTP server sends a software package download request carrying the device model of the device to the SVN server.
  • the SVN server queries the latest software package according to the device model, and returns the latest software package to the FTP server.
  • Step 309 The FTP server sends the latest software package of the device to the device.
  • Step 310 The device receives the latest software package, decompresses it into the Flash, reads the latest software package from the Flash, and uses the software package to repair and upgrade the device.
  • the device After the upgrade is completed, the device sends a repair complete message carrying the device identification information to the FTP server, and the FTP server deletes the device identification information from the faulty device table.
  • the SVN server If the software package corresponding to the device model does not exist in the SVN server, the SVN server prompts the maintenance staff to generate a software package for the device model, waiting for the maintenance staff to manually repair the device, and the maintenance staff compiles and generates the software package for the device model. , And upload it to the FTP server. When the FTP server receives the software package of the device model uploaded by the maintenance personnel, it sends the software package to the device.
  • Fig. 4 is a schematic structural diagram of a device fault repairing device provided by an embodiment of the application.
  • the device mainly includes: an abnormal query module 41 and a repair module 42, wherein:
  • the abnormal query module 41 is used to detect after the device restarts whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart; when an abnormal state file of the device is detected, read the file corresponding to the abnormal state file saved Uboot network configuration information.
  • Repair module 42 According to the Uboot network configuration information read by the abnormal query module 41, initiate a communication connection with the FTP server; after successfully establishing a communication connection with the FTP server, send an upgrade request to the FTP server; respond to the software returned by the FTP server Package, repair and upgrade the equipment.
  • the repair module 42 initiates a communication connection with the FTP server according to the Uboot network configuration information read by the abnormal query module 41, including: according to the device IP address, device gateway, and subnet mask in the Uboot network configuration information Perform Uboot network configuration with the FTP server address, and initiate a communication connection with the FTP server.
  • the repair module 42 sending the upgrade request to the FTP server includes: sending the upgrade request carrying the device identification information to the FTP server, so that the FTP server queries the SVN server address that publishes the software package according to the device identification information.
  • the abnormality query module 41 detecting whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart includes: detecting whether there is a flash memory that is stored by the CPU due to a device failure detected before the restart Abnormal state file;
  • the abnormal query module 41 reading the Uboot network configuration information saved corresponding to the abnormal state file includes: reading the Uboot network configuration information stored corresponding to the abnormal state file from the flash memory.
  • the abnormal state file and Uboot network configuration information read by the abnormal query module 41 are: when a device failure is detected, the saved abnormal state file and Uboot network configuration information of the device when the failure occurs.
  • the above-mentioned device is located on the front-end equipment.
  • Fig. 5 is a schematic structural diagram of a device fault repair system provided by an embodiment of the application.
  • the system mainly includes: a device 51, an FTP server 52, and an SVN server 53, in which:
  • the device 51 is used to detect after restarting whether there is an abnormal state file saved by the CPU due to the device failure detected before the restart; when the device abnormal state file is detected, read the Uboot network saved corresponding to the abnormal state file Configuration information; according to the read Uboot network configuration information, initiate a communication connection with the FTP server 52; after successfully establishing a communication connection with the FTP server 52, send an upgrade request to the FTP server 52; respond to the software package returned by the FTP server 52 , Repair and upgrade the device 51.
  • the device 51 initiating a communication connection with the FTP server 52 according to the read Uboot network configuration information includes: according to the device IP address, device gateway, subnet mask, and FTP server address in the Uboot network configuration information Perform Uboot network configuration and initiate a communication connection with the FTP server 52.
  • the device 51 sending the upgrade request to the FTP server 52 includes: sending the upgrade request carrying device identification information to the FTP server 52, so that the FTP server 52 queries the SVN server that publishes the software package according to the device identification information 53 addresses.
  • the device 51 detecting whether there is an abnormal state file saved by the CPU due to a device failure detected before the restart includes: detecting whether there is an abnormality stored by the CPU due to the device failure detected before the restart in the flash memory.
  • the device 51 reading the Uboot network configuration information stored corresponding to the abnormal state file includes: reading the Uboot network configuration information stored corresponding to the abnormal state file from the flash memory.
  • the abnormal state file and Uboot network configuration information read by the device 51 are: when a device failure is detected, the saved abnormal state file and Uboot network configuration information of the device when the failure occurs.
  • detecting that the device 51 has failed includes: detecting that the service process of the device has exited, restarting the service process, and if it is detected that the service process fails to restart for a preset number of consecutive times, it is determined that the device has failed.
  • detecting that the service process exits by the device 51 includes: periodically sending a keep-alive packet to the service process, and if the keep-alive packet returned by the service process is not received within the preset keep-alive waiting time, determining the service The process exits.
  • the device 51 continuously detecting the service process restart failure for a preset number of times includes: sending a startup completion query packet to the business process every preset startup query duration, if a preset number of startup completion query packets are continuously sent, but If no start-up completion package is received from the business process, it is determined that the business process has failed to restart.
  • the device 51 is a front-end device.
  • the FTP server 52 is configured to receive the upgrade request from the device 51, obtain the latest software package of the device from the SVN server 53, and send the latest software package to the device 51.
  • the FTP server 52 queries the address of the SVN server that publishes the software package according to the device identification information carried in the upgrade request, and downloads the latest software package of the device from the corresponding SVN server.
  • the SVN server 53 is configured to provide the latest software package of the device 51 to the FTP server 52.
  • the device in the embodiment of the present application may be a front-end device.
  • the embodiment of the present application provides a method for repairing a device failure.
  • the method includes:
  • S601 After the device is powered on, detect whether there is an abnormal state file saved by the processor due to the device failure in the device.
  • the method for repairing device failures in the embodiments of the present application may be implemented by a front-end device.
  • the front-end device may be a camera or a device related to a camera.
  • Device power-on means that the device is powered on and started.
  • the processor in the device can be used, for example, FPGA (Field Programmable Gate Array), ASIC (Application Specific Integrated Circuit), dedicated integration Circuit), SoC (System on Chip, system-on-chip), etc., before loading the system program of the device, execute the device fault repair method in this application; it can also execute the method in this application after the processor in the device loads the system program All methods for repairing equipment failures are within the scope of protection of this application.
  • One device corresponds to one Uboot network configuration information.
  • the Uboot network configuration information includes the address of the server.
  • the device can download the software package used for repair and upgrade from the server according to the address of the server, thereby completing the repair and upgrade of its own program.
  • S603 Initiate a communication connection with the server according to the address of the server in the Uboot network configuration information.
  • S605 Repair and upgrade the device in response to the software package returned by the server.
  • the Uboot network configuration information further includes the IP address of the device, the device gateway, and the subnet mask; according to the address of the server in the Uboot network configuration information, the initiating and The communication connection of the server includes: performing Uboot network configuration according to the IP address of the device, the device gateway, the subnet mask, and the address of the server in the Uboot network configuration information, and initiating a communication connection with the server.
  • the address of the server is the address of the communication server;
  • the sending the upgrade request to the server includes: sending the upgrade request carrying the identifier of the device to the communication server, to The communication server can query the address of the SVN server that publishes the software package according to the identification information of the device, and download the software package of the device from the corresponding SVN server.
  • the detecting whether there is an abnormal state file saved by the processor due to the device failure in the device includes: detecting whether there is a flash memory of the device that has been processed due to the device failure
  • the abnormal state file saved by the device includes: reading the Uboot network configuration information of the device from the flash memory of the device.
  • the device restart is: the front-end device restarts.
  • the method further includes: when a failure of the device is detected, generating and saving an abnormal state file of the failure of the device.
  • the generating and saving an abnormal state file of the device failure when a device failure is detected includes: for each business program of the device, when the business process is detected In the case of exiting, restart the business process; for each business program of the device, if the number of restart failures of the business process reaches the preset number of times, it is determined that the device is faulty, and the device is generated and saved The abnormal status file.
  • restarting the business process includes: for each business program of the device, cycle Send a keep-alive packet to the business process. If the keep-alive packet returned by the business process is not received within the preset keep-alive waiting time, it is determined that the business process exits, and the business process is restarted.
  • the abnormal state file of the device includes: for each restarted business program of the device, a startup completion query packet is sent to the business process every preset startup query duration, if a preset number of startup completion query packets are continuously sent and In the case of not receiving the startup completion packet returned by the business process, it is determined that the device is malfunctioning, and the abnormal state file of the device is generated and saved.
  • the embodiment of the present application provides a device fault repairing device, which includes:
  • the abnormal state file detection module is used to detect whether there is an abnormal state file saved by the processor due to the device failure in the device after the device is powered on.
  • the Uboot network configuration information obtaining module is used to obtain the Uboot network configuration information of the universal boot loading module of the device when the abnormal state file of the device is detected, wherein the Uboot network configuration information includes the address of the server.
  • the communication connection initiation module is used to initiate a communication connection with the server according to the address of the server in the Uboot network configuration information.
  • the upgrade request sending module is configured to send an upgrade request to the server after successfully establishing a communication connection with the server.
  • the repair and upgrade execution module is used to repair and upgrade the device in response to the software package returned by the server.
  • the Uboot network configuration information further includes the IP address of the device, the device gateway, and the subnet mask;
  • the communication connection initiation module is specifically used to: According to the Uboot network configuration information Uboot network configuration is performed on the IP address of the device, the device gateway, the subnet mask, and the address of the server, and a communication connection with the server is initiated.
  • the address of the server is the address of the communication server;
  • the upgrade request sending module is specifically configured to: after successfully establishing a communication connection with the server, send the communication server with The upgrade request for the identification of the device enables the communication server to query the address of the SVN server that publishes the software package according to the identification information of the device, and download the software package of the device from the corresponding SVN server.
  • the abnormal state file detection module is specifically configured to: after the device is powered on, detect whether there is an abnormal state file saved by the processor due to a device failure in the flash memory of the device;
  • the Uboot network configuration information acquisition module is specifically configured to read the Uboot network configuration information of the device from the flash memory of the device when the abnormal state file of the device is detected.
  • the device is a front-end device.
  • the device further includes: an abnormal state file saving module, configured to generate and save an abnormal state file of the equipment failure when a failure of the equipment is detected.
  • the abnormal state file saving module includes: a business process restart submodule, which is used to restart each business program of the device when the business process exits are detected Business process; equipment failure determination sub-module, for each business program of the device, if the number of restart failures of the business process reaches a preset time, it is determined that the device is faulty, and the device is generated and saved The abnormal status file of the device.
  • the service process restart submodule is specifically configured to: for each service process of the device, periodically send a keep-alive packet to the service process, if the preset keep-alive wait If the keep-alive packet returned by the business process is not received within the time period, it is determined that the business process exits, and the business process is restarted.
  • the device failure determination submodule is specifically configured to: for each restarted business program of the device, send a startup completion query packet to the business process every preset startup query duration, If a preset number of startup completion inquiry packets are continuously sent and the startup completion packet returned by the service process is not received, it is determined that the device is malfunctioning, and an abnormal state file of the device is generated and saved.
  • An embodiment of the present application provides an electronic device, including a processor and a memory; the memory is used to store a computer program; the processor is configured to execute the program stored in the memory to implement the Any of the described equipment failure repair methods.
  • the electronic device of the embodiment of the present application further includes a communication interface and a communication bus, where the processor, the communication interface, and the memory complete mutual communication through the communication bus.
  • the communication bus mentioned in the above electronic device may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus or the like.
  • the communication bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.
  • the communication interface is used for communication between the above-mentioned electronic device and other devices.
  • the memory may include RAM (Random Access Memory, random access memory), and may also include NVM (Non-Volatile Memory, non-volatile memory), such as at least one disk storage.
  • NVM Non-Volatile Memory, non-volatile memory
  • the memory may also be at least one storage device located far away from the foregoing processor.
  • the above-mentioned processor may be a general-purpose processor, including CPU (Central Processing Unit), NP (Network Processor, network processor), etc.; it may also be DSP (Digital Signal Processing, digital signal processor), ASIC ( Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array, Field Programmable Gate Array) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor, network processor
  • DSP Digital Signal Processing, digital signal processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array, Field Programmable Gate Array
  • other programmable logic devices discrete gates or transistor logic devices, discrete hardware components.
  • An embodiment of the present application further provides a computer-readable storage medium, and the computer-readable storage medium stores a computer program, and the computer program is executed by a processor to implement any device fault repair method described in the present application.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • General Health & Medical Sciences (AREA)
  • Multimedia (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)
  • Hardware Redundancy (AREA)

Abstract

本申请实施例提出设备故障修复方法、装置、电子设备及存储介质。方法包括：在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息；根据读取到的Uboot网络配置信息，发起与FTP服务器的通信连接；当与FTP服务器成功建立通信连接后，向FTP服务器发送升级请求；响应于FTP服务器返回的软件包，对设备进行修复升级。本申请实施例实现了对设备故障的远程修复。

Description

设备故障修复方法、装置、电子设备及存储介质
本申请要求于2020年04月15日提交中国专利局、申请号为202010293809.3发明名称为“设备故障修复方法”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及设备维护技术领域，尤其涉及设备故障修复方法、装置、电子设备及存储介质。
背景技术
随着对公共安全需求的提升，以摄像机为核心的视频监控技术在道路、商场、机场、火车站等大型公共场所被广泛的应用。视频监控系统由摄像、传输、控制、显示及记录等过程组成。其中摄像机等前端设备作为摄像的主体，是视频监控系统的核心部分，前端设备的稳定性与可靠性很大程度上决定了视频监控系统整体的性能。
在实际应用场景中，前端设备种类和数量繁多，各前端设备均需要加载相应的软件才能运行，而由软件问题导致的设备问题成了制约设备可靠性的瓶颈。对于简单软件问题，一般可以通过简单恢复或重启设备进行解决。但是当设备出现严重软件问题时，如用户修改了某项参数导致业务进程启动未完成而退出或者由于技术人员的疏忽升级了异常程序导致设备挂死，重启之后现象仍然存在，对于该种情况，目前没有合适的手段来进行故障设备的远程修复，只能依靠维护人员去现场拆卸设备，并使用串口进行修复升级，增加了人力和时间成本，并且由于此种修复方式时间周期较长，损害了用户的产品体验。
针对目前视频监控前端设备出现严重软件问题时远程修复困难问题，目前尚未出现解决方案。
发明内容
本申请实施例提出设备故障修复方法、装置、电子设备及存储介质，以实现对设备故障的远程修复。本申请实施例的技术方案是这样实现的：
第一方面，本申请实施例提供了一种设备故障修复方法，该方法包括：在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息；根据读取到的Uboot网络配置信息，发起与文件传输协议FTP服务器的通信连接；当与FTP服务器成功建立通信连接后，向FTP服务器发送升级请求；响应于FTP服务器返回的软件包，对设备进行修复升级。
在一种可能的实施方式中，所述根据读取到的Uboot网络配置信息发起与FTP服务器的通信连接包括：根据Uboot网络配置信息中的设备IP地址、设备网关、子网掩码和FTP服务器地址进行Uboot网络配置，并发起与FTP服务器的通信连接。
在一种可能的实施方式中，所述向FTP服务器发送升级请求包括：向FTP服务器发送携带设备标识信息的升级请求，以使得：FTP服务器根据该设备标识信息查询到发布软件包的SVN服务器地址。
在一种可能的实施方式中，所述检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件包括：检测闪存中是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；所述读取与异常状态文件对应保存的Uboot网络配置信息包括：从闪存中读取与异常状态文件对应保存的Uboot网络配置信息。
在一种可能的实施方式中，所述设备重启为：前端设备重启。
在一种可能的实施方式中，所述异常状态文件和所述Uboot网络配置信息为：当检测到设备发生故障时，保存的设备在发生该故障时的异常状态文件和Uboot网络配置信息。
在一种可能的实施方式中，所述检测到设备发生故障包括：检测到设备的业务进程退出，则重启业务进程，若连续预设次检测到业务进程重启失败，则确定设备发生故障。
在一种可能的实施方式中，所述检测到业务进程退出包括：周期性地向业务进程发送保活包，若在预设保活等待时长内未收到业务进程回复的保活包，则判定业务进程退出。
在一种可能的实施方式中，所述连续预设次检测到业务进程重启失败包括：每隔预设启动询问时长向业务进程发送启动完成询问包，若连续发出预设数目个启动完成询问包，但未收到业务进程回复的任何启动完成包，则判定业务进程重启失败。
在一种可能的实施方式中，所述Uboot网络配置信息包括：设备IP地址、设备网关、子网掩码和FTP服务器地址。
第二方面，本申请实施例提供了一种设备故障修复方法，该方法包括：在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件；当检测到所述设备异常状态文件时，获取所述设备的通用引导加载模块Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址；根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接；当与所述服务器成功建立通信连接后，向所述服务器发送升级请求；响应于所述服务器返回的软件包，对设备进行修复升级。
第三方面，本申请实施例提供了一种设备故障修复装置，该装置包括：异常状态文件检测模块，用于在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件；Uboot网络配置信息获取模块，用于当检测到所述设备异常状态文件时，获取所述设备的通用引导加载模块Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址；通信连接发起模块，用于根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接；升级请求发送模块，用于当与所述服务器成功建立通信连接后，向所述服务器发送升级请求；修复升级执行模块，用于响应于所述服务器返回的软件包，对设备进行修复升级。
第四方面，本申请实施例提供了一种电子设备，包括处理器及存储器；所述存储器，用于存放计算机程序；所述处理器，被配置为执行所述存储器上所存放的程序时，实现本申请中任一所述的设备故障修复方法。
第五方面，本申请实施例提供了一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现申请中任一所述的设备故障修复方法。
本申请实施例中，当设备发生故障后，通过与FTP服务器进行远程交互， 获取最新软件包完成修复升级，实现了对设备故障的自动远程修复，无需人工参与，减少了设备维护成本。
附图说明
为了更清楚地说明本申请实施例和现有技术的技术方案，下面对实施例和现有技术中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请一实施例提供的设备故障修复方法流程图；
图2为本申请另一实施例提供的设备故障修复方法流程图；
图3为本申请又一实施例提供的设备故障修复方法流程图；
图4为本申请实施例提供的设备故障修复装置的结构示意图；
图5为本申请实施例提供的设备故障修复系统的结构示意图；
图6为本申请又一实施例提供的设备故障修复方法流程图。
具体实施方式
为使本申请的目的、技术方案、及优点更加清楚明白，以下参照附图并举实施例，对本申请进一步详细说明。显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
为方便理解，首先给出如下解释：
Uboot(Universal Boot Loader，通用引导加载模块)：是一种主要应用于嵌入式终端的引导加载模块。
FTP(File Transfer Protocol，文件传输协议)：是TCP(Transfer Control Protocol，传输控制协议)/IP(Internet Protocol，因特网协议)组中的协议之一。
前端设备：指分布于探测现场的各类设备，本申请中指摄像机及相关设备。
守护进程：设备中运行的提供系统类服务的进程。
业务进程：实现设备具体软件功能的进程，如预览、存储、通信等业务 功能。
SVN(Subversion)：是一个软件版本的控制系统。
为了实现了对设备故障的自动远程修复，本申请一实施例提供了一种设备故障修复方法，其流程图如图1所示，具体步骤如下：
步骤101：在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件。
本申请实施例的设备故障修复方法，可以通过前端设备实现，具体的，前端设备可以为摄像机或与摄像机相关的设备。
步骤102：当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息。
一可选实施例中，Uboot网络配置信息包括：设备IP地址、设备网关、子网掩码和FTP服务器地址。一个例子中，一个设备对应一个Uboot网络配置信息。
步骤103：根据读取到的Uboot网络配置信息，发起与FTP服务器的通信连接。
步骤104：当与FTP服务器成功建立通信连接后，向FTP服务器发送升级请求。
步骤105：响应于FTP服务器返回的软件包，对设备进行修复升级。
上述实施例中，当设备发生故障后，通过与FTP服务器进行远程交互，获取最新软件包完成修复升级，实现了对设备故障的自动远程修复，无需人工参与，减少了设备维护成本。
图2为本申请另一实施例提供的设备故障修复方法流程图，其具体步骤如下：
步骤201：当检测到设备发生故障时，保存设备在发生该故障时的异常状态文件和Uboot网络配置信息。
一可选实施例中，检测到设备发生故障包括：检测到设备的业务进程退出，则重启业务进程，若连续预设次检测到业务进程重启失败，则确定设备发生故障。
一可选实施例中，检测到业务进程退出包括：周期性地向业务进程发送保活包，若在预设保活等待时长内未收到业务进程回复的保活包，则判定业务进程退出。
一可选实施例中，连续预设次检测到业务进程重启失败包括：每隔预设启动询问时长向业务进程发送启动完成询问包，若连续发出预设数目个启动完成询问包，但未收到业务进程回复的任何启动完成包，则判定业务进程重启失败。
步骤202：在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件。
步骤203：当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息。
步骤204：根据读取到的Uboot网络配置信息，发起与FTP服务器的通信连接。
步骤205：向FTP服务器发送携带设备标识信息的升级请求，以使得：FTP服务器根据该设备标识信息查询到发布软件包的SVN(Subversion)服务器地址，并从对应SVN服务器下载设备的最新软件包。
步骤206：响应于FTP服务器返回的软件包，对设备进行修复升级。
上述实施例中，通过检测到业务进程退出，则确定设备异常，之后，若连续预设次检测到业务进程重启失败，则确定设备发生故障，从而实现了对设备故障的准确判定；且，根据设备标识信息查询到发布软件包的SVN服务器地址，从而准确下载到设备的最新软件包。
图3为本申请又一实施例提供的设备故障修复方法流程图，其具体步骤如下：
步骤301：设备启动，设备的守护进程和业务进程之间建立Socket连接。
步骤302：守护进程通过Socket连接周期性地向业务进程发送keeplive(保活)包，并等待业务进程回复。
例如：守护进程每隔1s(秒)向业务进程发送一次keeplive包。
步骤303：若守护进程在预设保活等待时长内未收到业务进程回复的 keeplive包，则判定业务进程已退出，重启业务进程，并每隔预设启动询问时长向业务进程发送一次启动完成询问包。
一个例子中，启动询问时长例如为：5s。
步骤304：业务进程接收到启动完成询问包，查看启动完成标志是否为1，若为1，则向守护进程回复启动完成包，若为0，则回复启动未完成包。
步骤305：若守护进程连续预设数目次收到业务进程回复的启动未完成包，则判定设备故障，守护进程保存设备异常状态文件和设备Uboot网络配置信息到设备的Flash(闪存)中，同时重启设备。
例如：预设数目＝6。
Uboot网络配置信息包括：设备IP地址、设备网关、子网掩码及FTP服务器地址等。
步骤306：设备重启之后启动Uboot模块，Uboot模块从Flash中读取到设备异常状态文件则进入异常修复模式，从Flash读取设备Uboot网络配置信息，根据Uboot网络配置信息进行Uboot网络配置。
Uboot模块有两种工作模式，分别为正常模式和异常修复模式，正常模式下启动完成之后直接加载Linux内核。
步骤307：设备的Uboot根据Uboot网络配置信息中的FTP服务器地址，与FTP服务器建立FTP连接，向FTP服务器发送携带设备标识信息的升级请求。
升级请求携带的设备标识信息包括：设备IP地址、设备MAC地址和设备型号等。
步骤308：FTP服务器接收升级请求，将请求中的设备标识信息加入到故障设备表中，并根据设备型号在自身保存的设备型号与发布软件包的SVN服务器地址的对应关系中，查找到SVN服务器地址，从对应SVN服务器下载设备的最新软件包。
具体地，FTP服务器向SVN服务器发送携带该设备的设备型号的软件包下载请求，SVN服务器收到该请求后，根据该设备型号查询到最新软件包，将该最新软件包返回给FTP服务器。
步骤309：FTP服务器将设备的最新软件包发送给设备。
步骤310：设备接收最新软件包，并解压到Flash中，从Flash中读取最新软件包，采用该软件包对设备进行修复升级。
升级完成之后，设备向FTP服务器发送携带设备标识信息的修复完成消息，FTP服务器将该设备标识信息从故障设备表中删除。
若SVN服务器中不存在该设备型号对应的软件包，则SVN服务器提示维护人员需要生成该设备型号的软件包，等待维护人员对设备进行人工修复，由维护人员自行编译生成该设备型号的软件包，并上传到FTP服务器上，当FTP服务器接收到维护人员上传的该设备型号的软件包时，将该软件包发送给该设备。
图4为本申请实施例提供的设备故障修复装置的结构示意图，该装置主要包括：异常查询模块41和修复模块42，其中：
异常查询模块41，用于在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息。
修复模块42：根据异常查询模块41读取到的Uboot网络配置信息，发起与FTP服务器的通信连接；当与FTP服务器成功建立通信连接后，向FTP服务器发送升级请求；响应于FTP服务器返回的软件包，对设备进行修复升级。
一可选实施例中，修复模块42根据异常查询模块41读取到的Uboot网络配置信息发起与FTP服务器的通信连接包括：根据Uboot网络配置信息中的设备IP地址、设备网关、子网掩码和FTP服务器地址进行Uboot网络配置，并发起与FTP服务器的通信连接。
一可选实施例中，修复模块42向FTP服务器发送升级请求包括：向FTP服务器发送携带设备标识信息的升级请求，以使得：FTP服务器根据该设备标识信息查询到发布软件包的SVN服务器地址。
一可选实施例中，异常查询模块41检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件包括：检测闪存中是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；
异常查询模块41读取与异常状态文件对应保存的Uboot网络配置信息包 括：从闪存中读取与异常状态文件对应保存的Uboot网络配置信息。
一可选实施例中，异常查询模块41读取的异常状态文件和Uboot网络配置信息为：当检测到设备发生故障时，保存的设备在发生该故障时的异常状态文件和Uboot网络配置信息。
一可选实施例中，上述装置位于前端设备上。
图5为本申请实施例提供的设备故障修复系统的结构示意图，该系统主要包括：设备51、FTP服务器52和SVN服务器53，其中：
设备51，用于在重启后，检测是否存在由于重启前检测到的本设备故障而被CPU保存的异常状态文件；当检测到设备异常状态文件时，读取与异常状态文件对应保存的Uboot网络配置信息；根据读取到的Uboot网络配置信息，发起与FTP服务器52的通信连接；当与FTP服务器52成功建立通信连接后，向FTP服务器52发送升级请求；响应于FTP服务器52返回的软件包，对本设备51进行修复升级。
一可选实施例中，设备51根据读取到的Uboot网络配置信息发起与FTP服务器52的通信连接包括：根据Uboot网络配置信息中的设备IP地址、设备网关、子网掩码和FTP服务器地址进行Uboot网络配置，并发起与FTP服务器52的通信连接。
一可选实施例中，设备51向FTP服务器52发送升级请求包括：向FTP服务器52发送携带设备标识信息的升级请求，以使得：FTP服务器52根据该设备标识信息查询到发布软件包的SVN服务器53地址。
一可选实施例中，设备51检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件包括：检测闪存中是否存在由于重启前检测到的本设备故障而被CPU保存的异常状态文件；
设备51读取与异常状态文件对应保存的Uboot网络配置信息包括：从闪存中读取与异常状态文件对应保存的Uboot网络配置信息。
一可选实施例中，设备51读取的异常状态文件和Uboot网络配置信息为：当检测到设备发生故障时，保存的设备在发生该故障时的异常状态文件和Uboot网络配置信息。
一可选实施例中，设备51检测到设备发生故障包括：检测到本设备的业 务进程退出，则重启业务进程，若连续预设次检测到业务进程重启失败，则确定本设备发生故障。
一可选实施例中，设备51检测到业务进程退出包括：周期性地向业务进程发送保活包，若在预设保活等待时长内未收到业务进程回复的保活包，则判定业务进程退出。
一可选实施例中，设备51连续预设次检测到业务进程重启失败包括：每隔预设启动询问时长向业务进程发送启动完成询问包，若连续发出预设数目个启动完成询问包，但未收到业务进程回复的任何启动完成包，则判定业务进程重启失败。
一可选实施例中，设备51为前端设备。
FTP服务器52，用于接收到设备51发来的升级请求，从SVN服务器53获取到设备的最新软件包，将最新软件包发送给设备51。
一可选实施例中，FTP服务器52根据升级请求携带的设备标识信息，查询到发布软件包的SVN服务器地址，从对应的SVN服务器下载该设备的最新软件包。
SVN服务器53，用于将设备51的最新软件包提供给FTP服务器52。
本申请实施例中的设备可为前端设备。
本申请实施例提供了一种设备故障修复方法，参见图6，该方法包括：
S601，在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件。
本申请实施例的设备故障修复方法，可以通过前端设备实现，具体的，前端设备可以为摄像机或与摄像机相关的设备。设备上电是指设备接通电源并启动，设备上电后，可以通过设备中的处理器，例如，FPGA(Field Programmable Gate Array，现场可编程门阵列)、ASIC(Application Specific Integrated Circuit，专用集成电路)、SoC(System on Chip，系统级芯片)等，在加载设备的系统程序前，先执行本申请中的设备故障修复方法；也可以在设备中的处理器加载系统程序后执行本申请中的设备故障修复方法，均在本申请的保护范围内。
S602，当检测到所述设备异常状态文件时，获取所述设备的Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址。
一个设备对应一个Uboot网络配置信息，该Uboot网络配置信息包括服务器的地址，设备可以根据服务器的地址从服务器中下载修复升级所使用的软件包，从而完成对自身程序的修复升级。
S603，根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接。
S604，当与所述服务器成功建立通信连接后，向所述服务器发送升级请求。
S605，响应于所述服务器返回的软件包，对设备进行修复升级。
在一种可能的实施方式中，所述Uboot网络配置信息还包括所述设备的IP地址、设备网关、子网掩码；所述根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接，包括：根据Uboot网络配置信息中所述设备的IP地址、设备网关、子网掩码和所述服务器的地址进行Uboot网络配置，并发起与所述服务器的通信连接。
在一种可能的实施方式中，所述服务器的地址为通信服务器的地址；所述向所述服务器发送升级请求，包括：向所述通信服务器发送携带有所述设备的标识的升级请求，以使得所述通信服务器根据所述设备的标识信息查询到发布软件包的SVN服务器地址，并从对应SVN服务器下载所述设备的软件包。
在一种可能的实施方式中，所述检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件，包括：检测所述设备的闪存中是否存在由于设备故障而被处理器保存的异常状态文件；所述获取所述设备的Uboot网络配置信息，包括：从所述设备的闪存中读取所述设备的Uboot网络配置信息。
在一种可能的实施方式中，所述设备重启为：前端设备重启。
在一种可能的实施方式中，所述方法还包括：当检测到设备发生故障时，生成并保存所述设备发生故障的异常状态文件。
在一种可能的实施方式中，所述当检测到设备发生故障时，生成并保存 所述设备发生故障的异常状态文件，包括：针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程；针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
在一种可能的实施方式中，所述针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程，包括：针对所述设备的每一业务程序，周期性地向该业务进程发送保活包，若在预设保活等待时长内未收到该业务进程回复的保活包，则判定该业务进程退出，重启该业务进程。
在一种可能的实施方式中，所述针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件，包括：针对所述设备的每一重启的业务程序，每隔预设启动询问时长向该业务进程发送启动完成询问包，若在连续发出预设数目个启动完成询问包且未收到该业务进程回复的启动完成包的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
本申请实施例提供了一种设备故障修复装置，该装置包括：
异常状态文件检测模块，用于在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件。
Uboot网络配置信息获取模块，用于当检测到所述设备异常状态文件时，获取所述设备的通用引导加载模块Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址。
通信连接发起模块，用于根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接。
升级请求发送模块，用于当与所述服务器成功建立通信连接后，向所述服务器发送升级请求。
修复升级执行模块，用于响应于所述服务器返回的软件包，对设备进行修复升级。
在一种可能的实施方式中，所述Uboot网络配置信息还包括所述设备的IP地址、设备网关、子网掩码；所述通信连接发起模块，具体用于：根据Uboot网络配置信息中所述设备的IP地址、设备网关、子网掩码和所述服务 器的地址进行Uboot网络配置，并发起与所述服务器的通信连接。
在一种可能的实施方式中，所述服务器的地址为通信服务器的地址；所述升级请求发送模块，具体用于：当与所述服务器成功建立通信连接后，向所述通信服务器发送携带有所述设备的标识的升级请求，以使得所述通信服务器根据所述设备的标识信息查询到发布软件包的SVN服务器地址，并从对应SVN服务器下载所述设备的软件包。
在一种可能的实施方式中，所述异常状态文件检测模块，具体用于：在设备上电后，检测所述设备的闪存中是否存在由于设备故障而被处理器保存的异常状态文件；所述Uboot网络配置信息获取模块，具体用于：当检测到所述设备异常状态文件时，从所述设备的闪存中读取所述设备的Uboot网络配置信息。
在一种可能的实施方式中，所述设备为前端设备。
在一种可能的实施方式中，所述装置还包括：异常状态文件保存模块，用于当检测到设备发生故障时，生成并保存所述设备发生故障的异常状态文件。
在一种可能的实施方式中，所述异常状态文件保存模块，包括：业务进程重启子模块，用于针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程；设备故障判定子模块，用于针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
在一种可能的实施方式中，所述业务进程重启子模块，具体用于：针对所述设备的每一业务程序，周期性地向该业务进程发送保活包，若在预设保活等待时长内未收到该业务进程回复的保活包，则判定该业务进程退出，重启该业务进程。
在一种可能的实施方式中，所述设备故障判定子模块，具体用于：针对所述设备的每一重启的业务程序，每隔预设启动询问时长向该业务进程发送启动完成询问包，若在连续发出预设数目个启动完成询问包且未收到该业务进程回复的启动完成包的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
本申请实施例提供了一种电子设备，包括处理器及存储器；所述存储器，用于存放计算机程序；所述处理器，被配置为执行所述存储器上所存放的程序时，实现本申请中任一所述的设备故障修复方法。
在一种可能的实施方式中，本申请实施例的电子设备还包括通信接口和通信总线，其中，处理器，通信接口，存储器通过通信总线完成相互间的通信。
上述电子设备提到的通信总线可以是PCI(Peripheral Component Interconnect，外设部件互连标准)总线或EISA(Extended Industry Standard Architecture，扩展工业标准结构)总线等。该通信总线可以分为地址总线、数据总线、控制总线等。为便于表示，图中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
通信接口用于上述电子设备与其他设备之间的通信。
存储器可以包括RAM(Random Access Memory，随机存取存储器)，也可以包括NVM(Non-Volatile Memory，非易失性存储器)，例如至少一个磁盘存储器。可选的，存储器还可以是至少一个位于远离前述处理器的存储装置。
上述的处理器可以是通用处理器，包括CPU(Central Processing Unit，中央处理器)、NP(Network Processor，网络处理器)等；还可以是DSP(Digital Signal Processing，数字信号处理器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field-Programmable Gate Array，现场可编程门阵列)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。
本申请实施例还提供了一种计算机可读存储介质，上述计算机可读存储介质内存储有计算机程序，上述计算机程序被处理器执行时实现本申请中任一所述的设备故障修复方法。
在本申请提供的又一实施例中，还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行本申请中任一所述的设备故障修复方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的 流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
需要说明的是，在本文中，各个可选方案中的技术特征只要不矛盾均可组合来形成方案，这些方案均在本申请公开的范围内。诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
本说明书中的各个实施例均采用相关的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
以上所述仅为本申请的较佳实施例而已，并不用以限制本申请，凡在本申请的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本申请保护的范围之内。

Claims (30)

  1. 一种设备故障修复方法，该方法包括：
    在设备重启后，检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；
    当检测到设备异常状态文件时，读取与异常状态文件对应保存的通用引导加载模块Uboot网络配置信息；
    根据读取到的Uboot网络配置信息，发起与文件传输协议FTP服务器的通信连接；
    当与FTP服务器成功建立通信连接后，向FTP服务器发送升级请求；
    响应于FTP服务器返回的软件包，对设备进行修复升级。
  2. 根据权利要求1所述的方法，其中，所述根据读取到的Uboot网络配置信息发起与FTP服务器的通信连接包括：
    根据Uboot网络配置信息中的设备IP地址、设备网关、子网掩码和FTP服务器地址进行Uboot网络配置，并发起与FTP服务器的通信连接。
  3. 根据权利要求1所述的方法，其中，所述向FTP服务器发送升级请求包括：
    向FTP服务器发送携带设备标识信息的升级请求，以使得：FTP服务器根据该设备标识信息查询到发布软件包的SVN服务器地址。
  4. 根据权利要求1所述的方法，其中，所述检测是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件包括：
    检测闪存中是否存在由于重启前检测到的设备故障而被CPU保存的异常状态文件；
    所述读取与异常状态文件对应保存的Uboot网络配置信息包括：
    从闪存中读取与异常状态文件对应保存的Uboot网络配置信息。
  5. 根据权利要求1所述的方法，其中，所述设备重启为：前端设备重启。
  6. 根据权利要求1所述的方法，其中，所述异常状态文件和所述Uboot网络配置信息为：
    当检测到设备发生故障时，保存的设备在发生该故障时的异常状态文件和Uboot网络配置信息。
  7. 根据权利要求6所述的方法，其中，所述检测到设备发生故障包括：
    检测到设备的业务进程退出，则重启业务进程，若连续预设次检测到业务进程重启失败，则确定设备发生故障。
  8. 根据权利要求7所述的方法，其中，所述检测到业务进程退出包括：
    周期性地向业务进程发送保活包，若在预设保活等待时长内未收到业务进程回复的保活包，则判定业务进程退出。
  9. 根据权利要求7或8所述的方法，其中，所述连续预设次检测到业务进程重启失败包括：
    每隔预设启动询问时长向业务进程发送启动完成询问包，若连续发出预设数目个启动完成询问包，但未收到业务进程回复的任何启动完成包，则判定业务进程重启失败。
  10. 根据权利要求1所述的方法，其中，所述Uboot网络配置信息包括：设备IP地址、设备网关、子网掩码和FTP服务器地址。
  11. 一种设备故障修复方法，该方法包括：
    在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件；
    当检测到所述设备异常状态文件时，获取所述设备的Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址；
    根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接；
    当与所述服务器成功建立通信连接后，向所述服务器发送升级请求；
    响应于所述服务器返回的软件包，对设备进行修复升级。
  12. 根据权利要求11所述的方法，其中，所述Uboot网络配置信息还包括所述设备的IP地址、设备网关、子网掩码；
    所述根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接，包括：
    根据Uboot网络配置信息中所述设备的IP地址、设备网关、子网掩码和所述服务器的地址进行Uboot网络配置，并发起与所述服务器的通信连接。
  13. 根据权利要求11或12所述的方法，其中，所述服务器的地址为通 信服务器的地址；所述向所述服务器发送升级请求，包括：
    向所述通信服务器发送携带有所述设备的标识的升级请求，以使得所述通信服务器根据所述设备的标识信息查询到发布软件包的SVN服务器地址，并从对应SVN服务器下载所述设备的软件包。
  14. 根据权利要求11所述的方法，其中，所述检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件，包括：检测所述设备的闪存中是否存在由于设备故障而被处理器保存的异常状态文件；
    所述获取所述设备的Uboot网络配置信息，包括：从所述设备的闪存中读取所述设备的Uboot网络配置信息。
  15. 根据权利要求11所述的方法，其中，所述设备重启为：前端设备重启。
  16. 根据权利要求11所述的方法，其中，所述方法还包括：当检测到设备发生故障时，生成并保存所述设备发生故障的异常状态文件。
  17. 根据权利要求16所述的方法，其中，所述当检测到设备发生故障时，生成并保存所述设备发生故障的异常状态文件，包括：
    针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程；
    针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
  18. 根据权利要求17所述的方法，其中，所述针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程，包括：
    针对所述设备的每一业务程序，周期性地向该业务进程发送保活包，若在预设保活等待时长内未收到该业务进程回复的保活包，则判定该业务进程退出，重启该业务进程。
  19. 根据权利要求17或18所述的方法，其中，所述针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件，包括：
    针对所述设备的每一重启的业务程序，每隔预设启动询问时长向该业务 进程发送启动完成询问包，若在连续发出预设数目个启动完成询问包且未收到该业务进程回复的启动完成包的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
  20. 一种设备故障修复装置，该装置包括：
    异常状态文件检测模块，用于在设备上电后，检测所述设备中是否存在由于所述设备故障而被处理器保存的异常状态文件；
    Uboot网络配置信息获取模块，用于当检测到所述设备异常状态文件时，获取所述设备的Uboot网络配置信息，其中，所述Uboot网络配置信息包括服务器的地址；
    通信连接发起模块，用于根据所述Uboot网络配置信息中所述服务器的地址，发起与所述服务器的通信连接；
    升级请求发送模块，用于当与所述服务器成功建立通信连接后，向所述服务器发送升级请求；
    修复升级执行模块，用于响应于所述服务器返回的软件包，对设备进行修复升级。
  21. 根据权利要求20所述的装置，其中，所述Uboot网络配置信息还包括所述设备的IP地址、设备网关、子网掩码；所述通信连接发起模块，具体用于：根据Uboot网络配置信息中所述设备的IP地址、设备网关、子网掩码和所述服务器的地址进行Uboot网络配置，并发起与所述服务器的通信连接。
  22. 根据权利要求20或21所述的装置，其中，所述服务器的地址为通信服务器的地址；所述升级请求发送模块，具体用于：当与所述服务器成功建立通信连接后，向所述通信服务器发送携带有所述设备的标识的升级请求，以使得所述通信服务器根据所述设备的标识信息查询到发布软件包的SVN服务器地址，并从对应SVN服务器下载所述设备的软件包。
  23. 根据权利要求20所述的装置，其中，所述异常状态文件检测模块，具体用于：在设备上电后，检测所述设备的闪存中是否存在由于设备故障而被处理器保存的异常状态文件；所述Uboot网络配置信息获取模块，具体用于：当检测到所述设备异常状态文件时，从所述设备的闪存中读取所述设备的Uboot网络配置信息。
  24. 根据权利要求20所述的装置，其中，所述设备为前端设备。
  25. 根据权利要求20所述的装置，其中，所述装置还包括：异常状态文件保存模块，用于当检测到设备发生故障时，生成并保存所述设备发生故障的异常状态文件。
  26. 根据权利要求25所述的装置，其中，所述异常状态文件保存模块，包括：
    业务进程重启子模块，用于针对所述设备的每一业务程序，在检测到该业务进程退出的情况下，重启该业务进程；
    设备故障判定子模块，用于针对所述设备的每一业务程序，若该业务进程重启失败的次数达到预设次的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
  27. 根据权利要求26所述的装置，其中，所述业务进程重启子模块，具体用于：针对所述设备的每一业务程序，周期性地向该业务进程发送保活包，若在预设保活等待时长内未收到该业务进程回复的保活包，则判定该业务进程退出，重启该业务进程。
  28. 根据权利要求26或27所述的装置，其中，所述设备故障判定子模块，具体用于：针对所述设备的每一重启的业务程序，每隔预设启动询问时长向该业务进程发送启动完成询问包，若在连续发出预设数目个启动完成询问包且未收到该业务进程回复的启动完成包的情况下，则判定所述设备发生故障，生成并保存所述设备的异常状态文件。
  29. 一种电子设备，包括处理器及存储器；所述存储器，用于存放计算机程序；所述处理器，被配置为执行所述存储器上所存放的程序时，实现权利要求1-19任一所述的设备故障修复方法。
  30. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质内存储有计算机程序，所述计算机程序被处理器执行时实现权利要求1-19任一所述的方法步骤。
PCT/CN2021/074410 2020-04-15 2021-01-29 设备故障修复方法、装置、电子设备及存储介质 WO2021208564A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/046,676 US20230061066A1 (en) 2020-04-15 2022-10-14 Device failure repair method and apparatus, electronic device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010293809.3 2020-04-15
CN202010293809.3A CN113542318B (zh) 2020-04-15 2020-04-15 设备故障修复方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/046,676 Continuation US20230061066A1 (en) 2020-04-15 2022-10-14 Device failure repair method and apparatus, electronic device, and storage medium

Publications (1)

Publication Number Publication Date
WO2021208564A1 true WO2021208564A1 (zh) 2021-10-21

Family

ID=78084008

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/074410 WO2021208564A1 (zh) 2020-04-15 2021-01-29 设备故障修复方法、装置、电子设备及存储介质

Country Status (3)

Country Link
US (1) US20230061066A1 (zh)
CN (1) CN113542318B (zh)
WO (1) WO2021208564A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499295A (zh) * 2022-07-29 2022-12-20 浪潮通信技术有限公司 服务器故障上报方法、装置、电子设备及存储介质
CN116546551A (zh) * 2023-07-06 2023-08-04 深圳市华曦达科技股份有限公司 无线网络设备检测方法、装置和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103970564A (zh) * 2014-04-23 2014-08-06 京信通信系统（中国）有限公司 嵌入式操作系统自动修复升级功能的方法及其系统
US20160224428A1 (en) * 2015-02-03 2016-08-04 Insyde Software Corp. Automatic scanning and recovering method for electronic device
WO2018076169A1 (zh) * 2016-10-25 2018-05-03 华为技术有限公司 终端设备开机失败的恢复方法和终端设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7308487B1 (en) * 2000-12-12 2007-12-11 Igate Corp. System and method for providing fault-tolerant remote controlled computing devices
US7055062B2 (en) * 2002-10-31 2006-05-30 General Electric Company Method, system and program product for establishing a self-diagnosing and self-repairing automated system
CN100525206C (zh) * 2005-06-15 2009-08-05 华为技术有限公司 自动恢复设备故障的实现方法及系统
CN100545809C (zh) * 2006-03-22 2009-09-30 华为技术有限公司 一种软件升级方法及其系统
CN101296135A (zh) * 2008-06-27 2008-10-29 中兴通讯股份有限公司 故障信息的处理方法和装置
CN108694093A (zh) * 2017-04-06 2018-10-23 迈普通信技术股份有限公司 进程异常监控方法及装置
CN109982065B (zh) * 2017-12-27 2020-10-20 浙江宇视科技有限公司 视频监控网络中设备故障恢复的方法、装置及存储介质
US10831605B2 (en) * 2018-04-27 2020-11-10 Rovi Guides, Inc. System and method for detection of, prevention of, and recovery from software execution failure

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103970564A (zh) * 2014-04-23 2014-08-06 京信通信系统（中国）有限公司 嵌入式操作系统自动修复升级功能的方法及其系统
US20160224428A1 (en) * 2015-02-03 2016-08-04 Insyde Software Corp. Automatic scanning and recovering method for electronic device
WO2018076169A1 (zh) * 2016-10-25 2018-05-03 华为技术有限公司 终端设备开机失败的恢复方法和终端设备

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499295A (zh) * 2022-07-29 2022-12-20 浪潮通信技术有限公司 服务器故障上报方法、装置、电子设备及存储介质
CN116546551A (zh) * 2023-07-06 2023-08-04 深圳市华曦达科技股份有限公司 无线网络设备检测方法、装置和系统
CN116546551B (zh) * 2023-07-06 2023-10-27 深圳市华曦达科技股份有限公司 无线网络设备检测方法、装置和系统

Also Published As

Publication number Publication date
CN113542318B (zh) 2023-04-14
US20230061066A1 (en) 2023-03-02
CN113542318A (zh) 2021-10-22

Similar Documents

Publication Publication Date Title
US11490323B2 (en) Method and device for accessing a network hotspot device by an unconfigured device
US20230061066A1 (en) Device failure repair method and apparatus, electronic device, and storage medium
JP6359652B2 (ja) 情報の伝送方法、装置および機器
US20150026322A1 (en) Configuring a network device
CN106549789B (zh) 一种实现服务器安装的方法及系统
CN109039518B (zh) Android电视系统的NTP服务器地址智能管理方法
WO2018010425A1 (zh) Wifi热点信息推送方法、接收方法、装置及存储介质
US20230319157A1 (en) Device cross-area access method, electronic device, and non-transitory computer-readable storage medium
CN112272246A (zh) 带外网络ip自动配置方法、装置、电子设备及存储介质
WO2023124328A1 (zh) 无线通信模组及其功能恢复方法、电子设备和存储介质
WO2023143275A1 (zh) 数据处理方法和系统
US7039682B2 (en) Extension of the BOOTP protocol towards automatic reconfiguration
US20210274020A1 (en) Communication method, client device, and server device
US8854962B2 (en) Methods for coupling information handling systems through a communications stack
CN113766041B (zh) 获取第一服务器媒体访问控制mac地址的方法、装置、设备及存储介质
WO2024051739A1 (zh) 通信方法、设备和存储介质
CN111817878A (zh) 一种智能设备的联网方法、装置及云端服务器
US9658927B1 (en) Assisted device recovery
TW201523277A (zh) 伺服器系統與節點偵測方法
EP3649762B1 (en) Method and apparatus for rapidly configuring network element device for plug and play
CN115757505A (zh) 一种信息查询方法和机柜管理节点
CN107959595B (zh) 一种异常检测的方法、装置及系统
KR20210113595A (ko) 이상 처리 방법, 단말 기기 및 저장 매체
CN110943975A (zh) 服务注册的方法、装置、计算机设备和存储介质
CN106878379B (zh) 一种启动控制方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21789016

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21789016

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 19/05/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21789016

Country of ref document: EP

Kind code of ref document: A1