WO2015080556A1 - Method for booting an embedded device from an external usb device - Google Patents

Method for booting an embedded device from an external usb device Download PDF

Info

Publication number
WO2015080556A1
WO2015080556A1 PCT/MY2014/000136 MY2014000136W WO2015080556A1 WO 2015080556 A1 WO2015080556 A1 WO 2015080556A1 MY 2014000136 W MY2014000136 W MY 2014000136W WO 2015080556 A1 WO2015080556 A1 WO 2015080556A1
Authority
WO
WIPO (PCT)
Prior art keywords
embedded device
external usb
hardware
configuration file
existing
Prior art date
Application number
PCT/MY2014/000136
Other languages
French (fr)
Inventor
Rosli UZAIRI
Nazarudin MASHUDI
Mohd Hafiz BAHARUDIN
Badrul Zaman ADNAN
Original Assignee
Mimos Berhad
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 Mimos Berhad filed Critical Mimos Berhad
Publication of WO2015080556A1 publication Critical patent/WO2015080556A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/65Updates
    • G06F8/654Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories

Definitions

  • the present invention relates generally to a method for booting an embedded device, and more particularly to a method for booting an embedded device by using an external USB device.
  • an embedded device boot up by loading existing kernel, file system, and configuration file, which are stored within an internal storage of the embedded device.
  • the embedded device is required to be updated with new firmware, new configuration file, or both from time to time for the purposes of debugging, maintenance, and management of the embedded device, such as updating the firmware to enhance the capability of the device or just to fix some bug issues.
  • such actions are carried out by a certain user who knows the existing configurations of the embedded device, such as the IP address, service set identifier (SSID), username, and password of the embedded device.
  • the embedded device cannot be accessed by people who does not know the existing configurations, or when the username and password are forgotten.
  • SSID service set identifier
  • a user is forced to reset the embedded device to factory default settings so that he or she is able to access and boot the embedded device. This solution is not the best because all the existing configurations will be erased and further settings have to be done to the embedded device.
  • the user is able to access the embedded device by performing serial cable connection.
  • the core technical aspect of the present invention is directed to a method for booting an embedded device, such as a wireless access router, by using an external USB device, such as an external USB flash drive, in a circumstance where the IP address, service set identifier (SSID), username, password, or a combination thereof of the embedded device is unknown to a user.
  • an external USB device such as an external USB flash drive
  • the said method comprises a first step of having the embedded device to detect the presence of the external USB device, i.e. whether the external USB device is connected to the hardware of the embedded device, which preferably may be performed by a universal boot loader (U-boot) of the embedded device; a second step of having the embedded device to verify the external USB device, i.e.
  • U-boot universal boot loader
  • the verification process preferably may be a key exchange mechanism; a third step of booting the embedded device via the external USB device by having the embedded device to detect and load the second kernel, second file system, and second configuration file of the external USB device; a fourth step of having the external USB device to set the IP address, SSID, username, password, or a combination thereof of the embedded device to default; a fifth step of having the external USB device to scan the hardware of the embedded device; a sixth step of having the external USB device to list out, according to the scanning results of the fifth step, at least one new firmware that is related to the hardware of the embedded device, at least one new configuration file that is related to the hardware of the embedded device, or a combination thereof; and a seventh step of viewing the existing configuration of the hardware of the embedded device, updating the existing firmware of the hardware of the embedded device with the listed out new firmware, updating the existing first configuration file of the hardware of the embedded device with the listed out new configuration file, or a combination thereof.
  • the existing firmware or the existing first configuration file of the hardware of the embedded device will be automatically updated with the listed out new firmware or the listed out new configuration file, respectively, upon booting.
  • the existing firmware of the hardware of the embedded device will be updated with the listed out new firmware prior to updating the existing first configuration file of the hardware of the embedded device with the listed out new configuration file.
  • the user will be able to choose which listed out new firmwares to be used to update the existing firmware of the hardware of the embedded device, which listed out new configuration file to be used to update the existing first configuration file of the hardware of the embedded device, or a combination thereof via a remote debugging screen.
  • FIG 1 illustrates the elements that are involved in the method of the present invention for booting an embedded device by using an external USB device
  • FIG. 2 is a flow chart depicting the method of the present invention. DETAILED DESCRIPTION OF THE INVENTION
  • the main aspect of the present invention relates to a method for booting an embedded device (100) by using an external USB device (200).
  • the unique feature about this particular method is that a user is able to boot the embedded device (100) for the purposes of debugging, management, and maintenance of the embedded device (100) without the need to know the IP address, service set identifier (SSID), username, password, or a combination thereof the embedded device (100).
  • SSID service set identifier
  • the user is only able to access and boot the embedded device (100) by resetting the embedded device (100) to factory default settings.
  • Two core devices are involved, namely the embedded device (100) such as a wireless access router, and the external USB device (200) such as an external USB flash drive.
  • the embedded device (100) such as a wireless access router
  • the external USB device (200) such as an external USB flash drive.
  • the embedded device Within the embedded device (100), it comprises several other elements, namely a universal boot loader (U-boot) (101), a first kernel (102), a first file system (103), and a first configuration file (104), whereas within the external USB device (200), it comprises several other elements, namely a second kernel (202), a second file system (203), a second configuration file (204), at least one new firmware (300) that is related to the hardware of the embedded device (100), and at least one new configuration file (400) that is related to the hardware of the embedded device (100).
  • U-boot universal boot loader
  • 102 first kernel
  • 103 first file system
  • 104 a first configuration file
  • the external USB device 200
  • it comprises several other elements, namely a second kernel (202), a second file system (203), a second configuration file (204), at least one new firmware (300) that is related to the hardware of the embedded device (100), and at least one new configuration file (400) that is related to the hardware of the embedded device (
  • the method comprises the initial step of having the embedded device (100) to detect for the presence of the external USB device (200) (701), i.e. whether the external USB device (200) is connected to the hardware of the embedded device (100).
  • the embedded device (100) Upon detecting that the external USB device (200) is present, the embedded device (100) will verify the external USB device (200) in order to confirm the authenticity of the external USB device (200) (702).
  • the verification process can be of any known verification process. In one embodiment of the present invention, the verification process is a key exchange mechanism.
  • the embedded device (100) proceeds to detect and load the second kernel (202), the second file system (203), and the second configuration file (204) in order to boot the embedded device (100) via the external USB device (200) (703).
  • the aforesaid detection and loading action are performed by the U-boot (101) of the embedded device (100). Referring to Figure 1 , it can be seen that the embedded device (100) and the external USB device (200) are connected to each, and the connection is represented by the bi-directional arrow.
  • the external USB device (200) set the IP address, SSID, username, password, or a combination thereof of the embedded device (100) to default (704). In other words, at this point, it is not necessary for the user to know the IP address, SSID, username, password, or a combination thereof of the embedded device (100).
  • the external USB device (200) scans the hardware of the embedded device (100) (705) in order to determine and list out at least one new firmware (300) that is related to the hardware of the embedded device (100), at least one new configuration file (400) that is related to the hardware of the embedded device (100), or a combination thereof (706).
  • the user will then has the options of viewing the existing configuration of the hardware of the embedded device (100) (707), update the existing firmware of the hardware of the embedded device (100) with the listed out new firmware (300) (708), updating the existing first configuration file (104) of the hardware of the embedded device (100) with the listed out new configuration file (400) (709), or a combination thereof.
  • the existing firmware or the existing first configuration file (104) of the hardware of the embedded device (100) will be automatically updated with the listed out new firmware (300) or the listed out new configuration file (400), respectively (708) (709), upon booting.
  • the existing firmware of the hardware of the embedded device (100) is prioritized to be updated first with the listed out new firmware (300) (708) before the existing first configuration file (104) of the hardware of the embedded device (100) is updated with the listed out new configuration file (400) (709).
  • the user is able to choose, via a remote debugging screen, from the listed out new firmwares (300) which version of new firmware (300) is to be used to update the existing firmware of the hardware of the embedded device (100) (708), from the listed out new configuration files (400) which version of new configuration file (400) is to be used to update the existing first configuration file (104) of the hardware of the embedded device (100) (709), or a combination thereof.

Abstract

Disclosed herein is a method for booting an embedded device (100) by using an external USB device (200) without the need to know the IP address, service set identifier (SSID), username, password, or a combination thereof of the embedded device (100). In general, the method works by detecting the presence of the external USB device (200) (701). Once detected, a verification process is performed to confirm the authenticity of the external USB device (200) (702) before the embedded device (100) is booted via the external USB device (200). Subsequently, the external USB device (200) sets the IP address, SSID, username, password, or a combination thereof of the embedded device (100) to default (704), and then proceeds to scan the hardware of the embedded device (705) (100) in order to determine the relevant new firmware (300), new configuration file (400), or a combination thereof. A user will then be able to view the existing configuration of the embedded device (100) (707), and choose to update the existing firmware (708), the existing first configuration file (104) (709), or both by using the determined new firmware (300) and determined new configuration file (400).

Description

METHOD FOR BOOTING AN EMBEDDED DEVICE
FROM AN EXTERNAL USB DEVICE
TECHNICAL FIELD OF THE INVENTION
The present invention relates generally to a method for booting an embedded device, and more particularly to a method for booting an embedded device by using an external USB device.
BACKGROUND OF THE INVENTION
In a normal situation, an embedded device boot up by loading existing kernel, file system, and configuration file, which are stored within an internal storage of the embedded device. The embedded device is required to be updated with new firmware, new configuration file, or both from time to time for the purposes of debugging, maintenance, and management of the embedded device, such as updating the firmware to enhance the capability of the device or just to fix some bug issues.
Typically, such actions are carried out by a certain user who knows the existing configurations of the embedded device, such as the IP address, service set identifier (SSID), username, and password of the embedded device. This is where problems occur. For example, the embedded device cannot be accessed by people who does not know the existing configurations, or when the username and password are forgotten. At time like this, a user is forced to reset the embedded device to factory default settings so that he or she is able to access and boot the embedded device. This solution is not the best because all the existing configurations will be erased and further settings have to be done to the embedded device. Alternatively, the user is able to access the embedded device by performing serial cable connection. While this alternate solution preserves the existing configurations, it requires the user to physically handle the embedded device, and involves messy cables, all of which are tedious, time consuming, and require great effort. Therefore, it has become an aim of the present invention to introduce a method for booting an embedded device by using an external USB device without knowing the IP address, SSID, username, password, or a combination thereof of the embedded device.
SUMMARY OF THE INVENTION
The core technical aspect of the present invention is directed to a method for booting an embedded device, such as a wireless access router, by using an external USB device, such as an external USB flash drive, in a circumstance where the IP address, service set identifier (SSID), username, password, or a combination thereof of the embedded device is unknown to a user.
The said method comprises a first step of having the embedded device to detect the presence of the external USB device, i.e. whether the external USB device is connected to the hardware of the embedded device, which preferably may be performed by a universal boot loader (U-boot) of the embedded device; a second step of having the embedded device to verify the external USB device, i.e. to confirm the authenticity of the external USB device, wherein the verification process preferably may be a key exchange mechanism; a third step of booting the embedded device via the external USB device by having the embedded device to detect and load the second kernel, second file system, and second configuration file of the external USB device; a fourth step of having the external USB device to set the IP address, SSID, username, password, or a combination thereof of the embedded device to default; a fifth step of having the external USB device to scan the hardware of the embedded device; a sixth step of having the external USB device to list out, according to the scanning results of the fifth step, at least one new firmware that is related to the hardware of the embedded device, at least one new configuration file that is related to the hardware of the embedded device, or a combination thereof; and a seventh step of viewing the existing configuration of the hardware of the embedded device, updating the existing firmware of the hardware of the embedded device with the listed out new firmware, updating the existing first configuration file of the hardware of the embedded device with the listed out new configuration file, or a combination thereof.
In the event where the external USB device manages to list out one new firmware or one new configuration file that is related to the hardware of the embedded device, the existing firmware or the existing first configuration file of the hardware of the embedded device will be automatically updated with the listed out new firmware or the listed out new configuration file, respectively, upon booting.
In the event where the external USB device manages to list out one new firmware and one new configuration file that are related to the hardware of the embedded device, the existing firmware of the hardware of the embedded device will be updated with the listed out new firmware prior to updating the existing first configuration file of the hardware of the embedded device with the listed out new configuration file.
In the event where the external USB device manages to list out more than new firmwares, more than one new configuration files, or a combination thereof that are related to the hardware of the embedded device, the user will be able to choose which listed out new firmwares to be used to update the existing firmware of the hardware of the embedded device, which listed out new configuration file to be used to update the existing first configuration file of the hardware of the embedded device, or a combination thereof via a remote debugging screen.
BRIEF DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates the elements that are involved in the method of the present invention for booting an embedded device by using an external USB device; and
Figure 2 is a flow chart depicting the method of the present invention. DETAILED DESCRIPTION OF THE INVENTION
The above mentioned and other features and objects of this invention will become more apparent and better understood by reference to the following detailed description. It should be understood that the detailed description made known below is not intended to be exhaustive or limit the invention to the precise disclosed form as the invention may assume various alternative forms. On the contrary, the detailed description covers all the relevant modifications and alterations made to the present invention, unless the claims expressly state otherwise.
The main aspect of the present invention relates to a method for booting an embedded device (100) by using an external USB device (200). The unique feature about this particular method is that a user is able to boot the embedded device (100) for the purposes of debugging, management, and maintenance of the embedded device (100) without the need to know the IP address, service set identifier (SSID), username, password, or a combination thereof the embedded device (100). Conventionally, in the condition where the IP address, SSID, username, password, or a combination thereof of the embedded device (100) is unknown to the user, the user is only able to access and boot the embedded device (100) by resetting the embedded device (100) to factory default settings. This is an undesirable action as the existing configurations of the embedded device (100) will all be wiped out, and additional setting action will have to be taken after accessing the embedded device (100). The other way to access and boot the embedded device (100) while preserving the existing configurations is to perform serial cable connection. While this is more advantageously than the previously discussed technique, it is still unfavourable as it requires the user to physically handle the embedded device (100) such as dismantling the embedded device (100) in order to access the hardware part, and involved messy cables, all of which are tedious, time consuming, and require great effort. All of the aforementioned disadvantages are not present in the method as described herein.
The details of the present method will now be thoroughly discussed with the aid of Figure 1 and Figure 2. Two core devices are involved, namely the embedded device (100) such as a wireless access router, and the external USB device (200) such as an external USB flash drive.
Within the embedded device (100), it comprises several other elements, namely a universal boot loader (U-boot) (101), a first kernel (102), a first file system (103), and a first configuration file (104), whereas within the external USB device (200), it comprises several other elements, namely a second kernel (202), a second file system (203), a second configuration file (204), at least one new firmware (300) that is related to the hardware of the embedded device (100), and at least one new configuration file (400) that is related to the hardware of the embedded device (100).
The method comprises the initial step of having the embedded device (100) to detect for the presence of the external USB device (200) (701), i.e. whether the external USB device (200) is connected to the hardware of the embedded device (100).
Upon detecting that the external USB device (200) is present, the embedded device (100) will verify the external USB device (200) in order to confirm the authenticity of the external USB device (200) (702). The verification process can be of any known verification process. In one embodiment of the present invention, the verification process is a key exchange mechanism. Soon after the verification process, the embedded device (100) proceeds to detect and load the second kernel (202), the second file system (203), and the second configuration file (204) in order to boot the embedded device (100) via the external USB device (200) (703). The aforesaid detection and loading action are performed by the U-boot (101) of the embedded device (100). Referring to Figure 1 , it can be seen that the embedded device (100) and the external USB device (200) are connected to each, and the connection is represented by the bi-directional arrow.
Subsequently, the external USB device (200) set the IP address, SSID, username, password, or a combination thereof of the embedded device (100) to default (704). In other words, at this point, it is not necessary for the user to know the IP address, SSID, username, password, or a combination thereof of the embedded device (100). At this point, the external USB device (200) scans the hardware of the embedded device (100) (705) in order to determine and list out at least one new firmware (300) that is related to the hardware of the embedded device (100), at least one new configuration file (400) that is related to the hardware of the embedded device (100), or a combination thereof (706). The user will then has the options of viewing the existing configuration of the hardware of the embedded device (100) (707), update the existing firmware of the hardware of the embedded device (100) with the listed out new firmware (300) (708), updating the existing first configuration file (104) of the hardware of the embedded device (100) with the listed out new configuration file (400) (709), or a combination thereof.
In the circumstance where the external USB device (200) only manages to list out one new firmware (300) or only one new configuration file (400) that is related to the hardware of the embedded device (100) (706), the existing firmware or the existing first configuration file (104) of the hardware of the embedded device (100) will be automatically updated with the listed out new firmware (300) or the listed out new configuration file (400), respectively (708) (709), upon booting. In the circumstance where the external USB device (200) manages to list out one new firmware (300), and one new configuration file (400) that are related to the hardware of the embedded device (100) (706), the existing firmware of the hardware of the embedded device (100) is prioritized to be updated first with the listed out new firmware (300) (708) before the existing first configuration file (104) of the hardware of the embedded device (100) is updated with the listed out new configuration file (400) (709). In the circumstance where the external USB device (200) manages to list out more than one new firmwares (300), more than one new configuration files (400), or a combination thereof that are related to the hardware of the embedded device (100) (706), the user is able to choose, via a remote debugging screen, from the listed out new firmwares (300) which version of new firmware (300) is to be used to update the existing firmware of the hardware of the embedded device (100) (708), from the listed out new configuration files (400) which version of new configuration file (400) is to be used to update the existing first configuration file (104) of the hardware of the embedded device (100) (709), or a combination thereof.

Claims

A method to boot an embedded device (100) by using an external USB device (200), characterized in that the method comprises the steps of: a) detecting, by the embedded device (100), for the external USB device (200) that is connected to the hardware of the embedded device (100) (701);
b) verifying, by the embedded device (100), the external USB device (200) (702);
c) detecting and loading, by the embedded device (100), a second kernel (202), a second file system (203), and a second configuration file (204) of the external USB device (200) (703); d) setting, by the external USB device (200), the IP address, SSID, username, password, or a combination thereof of the embedded device (100) to default (704);
e) scanning, by the external USB device (200), the hardware of the embedded device (100) (705);
f) listing out according to the scanning results of step (e), by the external USB device (200), at least one new firmware (300) that relates to the hardware of the embedded device (100), at least one new configuration file (400) that relates to the hardware of the embedded device (100), or a combination thereof (706); and g) viewing the existing configuration of the hardware of the embedded device (100) (707), updating the existing firmware of the hardware of the embedded device (100) with the listed out new firmware (300) (708), updating the existing first configuration file (104) of the hardware of the embedded device (100) with the listed out new configuration file (400) (709), or a combination thereof.
Figure imgf000010_0001
A method in accordance with claim 1 , wherein the step of detecting, by the embedded device (100), for the external USB device (200) that is connected to the hardware of the embedded device (100) (701) is performed by a universal boot loader (U-boot) of the embedded device (100).
A method in accordance with claim 1 , wherein the step of verifying, by the embedded device (100), the external USB device (200) (702) is performed by using a key exchange mechanism.
A method in accordance with claim 1 , wherein in the event that there is one new firmware (300) or one new configuration file (400) listed out by the external USB device (200) (706), the existing firmware or the existing first configuration file (104) of the hardware of the embedded device (100) is updated with the listed out new firmware (300) or the listed out new configuration file (400), respectively (708) (709), in an automatic manner upon booting.
A method in accordance with claim 1 , wherein in the event that there are one new firmware (300) and one new configuration file (400) listed out by the external USB device (200) (706), the existing firmware of the hardware of the embedded device (100) is updated first with the listed out new firmware (300) (708) before the existing first configuration file (104) of the hardware of the embedded device (100) is updated with the listed out new configuration file (400) (709).
A method in accordance with claim 1 , wherein in the event there are more than one new firmwares (300), more than one new configuration files (400), or a combination thereof listed out by the external USB device (200) (706), a user is able to choose, via a remote debugging screen, from the listed out new firmwares (300) which version of new firmware (300) is to be used to update the existing firmware of the hardware of the embedded device (100) (708), from the listed out new configuration files (400) which version of new configuration file (400) is to be used to update the existing first configuration file (104) of the hardware of the embedded device ( 00) (709), or a combination thereof.
PCT/MY2014/000136 2013-11-27 2014-05-29 Method for booting an embedded device from an external usb device WO2015080556A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
MYPI2013702282 2013-11-27
MYPI2013702282A MY183609A (en) 2013-11-27 2013-11-27 Method for booting an embedded device from an external usb device

Publications (1)

Publication Number Publication Date
WO2015080556A1 true WO2015080556A1 (en) 2015-06-04

Family

ID=51570822

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/MY2014/000136 WO2015080556A1 (en) 2013-11-27 2014-05-29 Method for booting an embedded device from an external usb device

Country Status (2)

Country Link
MY (1) MY183609A (en)
WO (1) WO2015080556A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106843842A (en) * 2016-12-23 2017-06-13 光锐恒宇(北京)科技有限公司 The update method and device of a kind of application profiles
CN109417471A (en) * 2016-06-23 2019-03-01 马恩德优尔帕斯控股有限公司 Password generating device and password authentification equipment
CN110647433A (en) * 2019-09-26 2020-01-03 深圳创维-Rgb电子有限公司 Function self-checking method and device and computer readable storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060085631A1 (en) * 2004-10-20 2006-04-20 Young Joel K System and method for booting embedded systems using removable storage
EP1768022A2 (en) * 2005-09-09 2007-03-28 Samsung Electronics Co., Ltd. Electronic apparatus and control method thereof

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060085631A1 (en) * 2004-10-20 2006-04-20 Young Joel K System and method for booting embedded systems using removable storage
EP1768022A2 (en) * 2005-09-09 2007-03-28 Samsung Electronics Co., Ltd. Electronic apparatus and control method thereof

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417471A (en) * 2016-06-23 2019-03-01 马恩德优尔帕斯控股有限公司 Password generating device and password authentification equipment
CN109417471B (en) * 2016-06-23 2022-05-27 马恩德优尔帕斯控股有限公司 Password generation device and password verification device
CN106843842A (en) * 2016-12-23 2017-06-13 光锐恒宇(北京)科技有限公司 The update method and device of a kind of application profiles
CN106843842B (en) * 2016-12-23 2020-06-12 光锐恒宇(北京)科技有限公司 Method and device for updating application program configuration file
CN110647433A (en) * 2019-09-26 2020-01-03 深圳创维-Rgb电子有限公司 Function self-checking method and device and computer readable storage medium

Also Published As

Publication number Publication date
MY183609A (en) 2021-03-02

Similar Documents

Publication Publication Date Title
US9547765B2 (en) Validating a type of a peripheral device
JP5582909B2 (en) Platform integrity verification system
US8505069B1 (en) System and method for updating authorized software
US7865952B1 (en) Pre-emptive application blocking for updates
US7424706B2 (en) Automatic detection and patching of vulnerable files
US20150242627A1 (en) Apparatus and method for blocking actvity of malware
CN102262574B (en) Boot protecting method and device of operating system
KR20150048136A (en) Secure firmware updates
CN106341732B (en) Management method of desktop starter and intelligent television
US9244758B2 (en) Systems and methods for repairing system files with remotely determined repair strategy
US9659172B2 (en) System and method of preventing execution of undesirable programs
CN108351923B (en) Thresholds associated with scripts executable by a unified extensible firmware interface system
US20090234942A1 (en) Apparatus, system, and method for testing embedded device
CN103944757A (en) Network anomaly detecting method and device
US20160350166A1 (en) Systems and methods for smart diagnosis using hosted resources with intelligent altering of boot order
CN105809055A (en) Access control method and device, and related equipment
WO2015080556A1 (en) Method for booting an embedded device from an external usb device
US20160014123A1 (en) Apparatus and method for verifying integrity of applications
US9959127B2 (en) Systems and methods for exporting diagnostic data and securing privileges in a service operating system
CN104298924A (en) Method and device for ensuring system safety and terminal
CN111046383B (en) Terminal attack defense method and device, terminal and cloud server
CN112685071A (en) Application program repairing method, device, equipment and storage medium
CN106355079B (en) Method and device for optimizing installation of application program and terminal
US11714744B2 (en) System and method for diagnosing a computing device in safe mode
CN105808253B (en) The method and device of Android system starting up

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: 14767164

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: 14767164

Country of ref document: EP

Kind code of ref document: A1