Electronic equipment and control methods

Abstract

Regardless of how often it's used, you'll have the opportunity to perform processing on a specific option. [Solution] The system comprises a device that operates based on firmware and an interface that provides communication functionality. The firmware-based operation has an option that can be selected whether or not to perform. The device intermittently enables the communication function, and when the communication function is enabled, it executes optional processing according to commands obtained from an external device. This embodiment can be implemented as both an electronic device and a control method.

Description

[Technical Field]

[0001] The present application relates to electronic devices and control methods, for example, to firmware maintenance. [Background Art]

[0002] Electronic devices including personal computers (PCs) are configured to include various devices including a host system. In maintenance of electronic devices, operations such as firmware updating and operation parameter setting may be performed.

[0003] For example, the electronic device described in Patent Document 1 enables acquisition and updating of software via a network, causes at least the software to be activated among the acquired software to be displayed on a display unit, downloads the software, updates the installed software, activates the function of the updated software, and activates the function of the software displayed as an object to be activated after updating the software. The software that can be acquired and updated via a network is firmware. [Related Art] [Patent Documents]

[0004] [Patent Document 1] Japanese Laid-Open Patent Publication No. 2024-138038 [Summary of the Invention] [Problem to be Solved by the Invention]

[0005] Maintenance of electronic devices may be performed by executing specified software tools in response to requests from a dedicated cloud server connected to a network. During maintenance, administrator-specified boot options may be executed remotely. To this end, WOL (Wake-on-LAN: Local Area Network) or remote reset may be applied to specify the target boot option to be executed. On the other hand, the target boot option may be selected by the user at the site where the electronic device is being used.

[0006] However, remote maintenance relies on administrator-initiated operations, which may not take into account user behavior. Furthermore, PCs equipped with Ethernet ports are relatively rare these days, and WOL (Wake-on-LAN) may not be supported in WLAN (Wireless LAN) environments. On the other hand, user operations in the field may not always execute administrator-required processes in a timely manner. In this regard, it might be considered to prioritize the target boot option in the optional function settings. However, in that case, the target boot option would be executed preferentially regardless of necessity, increasing the time it takes for the boot option the user actually wants to use to start. Therefore, configuring optional functions is unsuitable for promptly starting specific boot options that are used relatively infrequently. [Means for solving the problem]

[0007] This invention was made to solve the above-mentioned problems, and an electronic device according to one aspect of this invention comprises a device that operates based on firmware and an interface that provides a communication function, wherein the operation has an option that can be selected to be performed or not, the device intermittently enables the communication function, and when the communication function is enabled, it performs processing of the option in accordance with a command obtained from an external device.

[0008] The above-mentioned electronic device may be equipped with a timer for measuring the current time, and the communication function may be activated when the current time has elapsed to a predetermined date and time.

[0009] In the electronic device described above, the device is a host device that constitutes a host system, and the host system may verify the effectiveness of the communication function during the initialization process.

[0010] In the above-described electronic device, the host system may start the initialization process when the current time has elapsed to a predetermined date and time while the power is off, and after the completion of the optional processing, change back to the power-off state.

[0011] In the above-described electronic device, the host system may operate in a low-power mode, which is a power mode that consumes less power than the standard power mode, and when the current time has elapsed to a predetermined date and time, it may pause its operation before starting the initialization process, and after the completion of the optional process, it may perform a restart process and change the power mode to the low-power mode.

[0012] In the above-described electronic device, the host system may, when it detects a startup instruction while the power is off, start the initialization process, activate the communication function when the current time has elapsed to a predetermined date and time, and execute the startup process after the completion of the optional processing.

[0013] In the electronic device described above, the device may repeat the process based on one of the unexecuted commands and the restart process after the completion of the process until there are no more unexecuted commands.

[0014] A control method according to one aspect of the present invention is a control method for electronic equipment comprising a host system that operates according to firmware and an interface that provides a communication function, wherein the operation has an option that can be selected whether or not to be performed, and the host system intermittently enables the communication function, and when the communication function is enabled, the control method executes the processing of the option according to a command obtained from an external device. [Effects of the Invention]

[0015] According to the embodiments of the present invention, an opportunity is obtained to perform processing on a specific option regardless of its frequency of use. [Brief explanation of the drawing]

[0016] [Figure 1] This is a schematic block diagram showing an example configuration of the maintenance system according to this embodiment. [Figure 2] This is a schematic block diagram showing an example of the hardware configuration of the electronic device according to this embodiment. [Figure 3] This is a schematic block diagram showing an example of the functional configuration of the electronic device according to this embodiment. [Figure 4] This flowchart illustrates a first example of the maintenance process according to this embodiment. [Figure 5] This flowchart illustrates a second example of the maintenance process according to this embodiment. [Figure 6] This flowchart illustrates a third example of the maintenance process according to this embodiment. [Figure 7] This figure illustrates a network connection warning screen according to this embodiment. [Modes for carrying out the invention]

[0017] Hereinafter, embodiments of the present application will be described with reference to the drawings. An example of the configuration of the maintenance system S1 according to this embodiment will be described. Figure 1 is a schematic block diagram showing an example of the configuration of the maintenance system S1 according to this embodiment. A maintenance system S1 includes an electronic device 1 and a server device 2. The electronic device 1 and the server device 2 are connected by wire or wirelessly via a network NW so as to be capable of transmitting and receiving various types of data. Part or all of the network NW is configured to include a wide-area communication network such as the Internet. Part of the network NW may include a narrow-area communication network such as a local area network (LAN).

[0018] The electronic device 1 includes a host system 10 (FIG. 2) that operates in accordance with system firmware, and a communication interface for implementing a communication function with other devices. An operation based on the system firmware has an option, which is a function for which executability can be selected. The host system 10 intermittently enables the communication function. When the communication function is enabled, the host system 10 waits for a command transmitted from the server device 2. When the host system 10 receives a command from the server device 2, the host system 10 executes optional processing in accordance with the received command.

[0019] The server device 2 provides various services related to maintenance and management of the electronic device 1. The server device 2 mainly performs maintenance on system firmware executed in the electronic device 1. System firmware refers to firmware for controlling basic operations of a host system. In the present application, the system firmware refers to a system Basic Input / Output System (BIOS) that employs Unified Extensible Firmware Interface (UEFI), and is sometimes simply referred to as BIOS.

[0020] The server device 2 mainly includes a maintenance processing unit that remotely performs system firmware maintenance. For example, the maintenance processing unit enables the server device 2 to provide services such as BIOS factory default initialization (BIOS Initialize Factory Default), Secure Wipe, BIOS update (Update BIOS), CSME update (Update CSME: Converged Security and Management Engine), and Diagnostics to the electronic device 1. CSME is firmware for managing the security of a host device. For example, CSME enables encryption or decryption of various types of firmware and other software.

[0021] The maintenance processing unit transmits commands to the electronic device 1 in accordance with a predetermined communication protocol, and causes a software tool (for example, an EFI Tool) instructed in accordance with the command to be executed. Each command is obtained, for example, in response to an operation by an administrator. Each command may also be selected in accordance with a predetermined rule or model based on the operating state reported from the electronic device 1. The mechanism for providing this maintenance-related service is also called LCM (Life Cycle Management). In the present application, a maintenance-related command may be referred to as a "maintenance action" or simply an "action".

[0022] As a protocol for transmitting maintenance actions, for example, LCM HTTPS (Hypertext Transfer Protocol Secure) Boot is used. LCM HTTPS corresponds to a procedure that applies UEFI BIOS HTTPS Boot (sometimes simply referred to as "HTTPS Boot") to maintenance actions. Maintenance actions are mainly executed during periods when the electronic device 1 is not in use.

[0023] Server device 2 manages maintenance execution information, which indicates the maintenance actions taken and their execution status, for the electronic device 1 that is to be maintained and managed. For example, when server device 2 receives a maintenance action request from electronic device 1, it refers to the maintenance execution information to identify any unexecuted maintenance actions. Server device 2 notifies electronic device 1 of the presence or absence of unexecuted actions. If server device 2 has unexecuted maintenance actions, it notifies electronic device 1 of those maintenance actions. When server device 2 receives notification from electronic device 1 that the unexecuted maintenance actions notified by server device 2 have been completed, it changes the execution status of those maintenance actions to "executed".

[0024] Electronic device 1 is a user device primarily used at the user's location. Typically, electronic device 1 is used at a different location than server device 2. Electronic device 1 may be any form of information terminal device, such as a PC (Personal Computer), a tablet device, or a multifunction mobile phone. Server device 2 is used at locations such as the manufacturer and maintenance company of electronic device 1. Server device 2 is configured as a cloud server connected to the internet.

[0025] Next, an example of the configuration of the electronic device 1 according to this embodiment will be described. Figure 2 is a schematic block diagram showing an example of the hardware configuration of the electronic device 1 according to this embodiment. In the example of Figure 2, the electronic device 1 is configured as a notebook PC (sometimes referred to as a "notebook PC" in this application).

[0026] The electronic device 1 comprises a host system 10, a video subsystem 13, a display 14, a ROM (Read Only Memory) 22, storage 23, a WLAN (Wireless Local Area Network) module 25, an input / output interface 26, an EC 31, an input device 32, a power supply circuit 34, and a power button 38.

[0027] The host system 10 is the core computer system of the electronic device 1. The host system 10 includes a CPU (Central Processing Unit) 11, main memory 12, and a chipset 21. In this application, the devices that make up the host system 10 may be referred to as "host devices".

[0028] The CPU 11 is a processor that executes various programs. For example, it executes programs such as firmware, OS (Operating System), utility software, and application programs. In this invention, "executing a program" or "executing a program" refers to executing the processing instructed by the commands written in the program. By executing various programs, the CPU 11 works in cooperation with the main memory 12 and other hardware to realize the functions of the host system 10.

[0029] Main memory 12 is writable memory used as a reading area for the CPU 11's executable program, or as a work area for writing processing data for the executable program. Main memory 12 is composed of, for example, multiple DRAM (Dynamic Random Access Memory) chips. The CPU 11 and main memory 12 constitute the minimum hardware that makes up the host system 10.

[0030] The video subsystem 13 is a subsystem for implementing functions related to image display. The video subsystem 13 includes a video controller and video memory (not shown). The video controller generates drawing information according to drawing instructions input from the CPU 11 and writes the generated drawing information to the video memory. The video memory temporarily stores the drawing information generated by the video controller. The video controller reads the stored drawing information from the video memory at predetermined intervals and outputs display data showing the display screen composed of the read drawing information to the display 14.

[0031] The display 14 displays a screen based on display data input from the video subsystem 13. The display 14 may be, for example, a liquid crystal display (LCD) or an organic light-emitting diode (OLED) display.

[0032] The chipset 21 includes multiple controllers, enabling connection to multiple devices and various data input / output. The controllers on the chipset 21 may be, for example, USB (Universal Serial Bus), SPI (Serial Peripheral Interface) bus, PCI-Express bus, etc. In the example in Figure 1, the chipset 21 is connected to ROM 22, storage 23, WLAN module 25, input / output I / F 26, and EC31.

[0033] ROM22 primarily stores firmware. Firmware stored in ROM22 includes system firmware such as BIOS, and firmware for controlling individual devices. Furthermore, firmware typically consists of multiple driver software (sometimes simply referred to as "drivers" in this application). In this application, BIOS refers to system firmware that instructs the operation of host devices and starts the OS, and primarily means a system BIOS employing UEFI (Unified Extensible Firmware Interface) (i.e., UEFI BIOS), which may include UEFI drivers. ROM22 may be either EEPROM (Electrically Erasable Programmable Read Only Memory) or flash ROM.

[0034] Storage 23 is an auxiliary storage device that non-temporarily stores various data used in the processing of the host system 10, various data acquired through such processing, or various programs in a read-write manner. Storage 23 may be, for example, an SSD (Solid State Drive) or an HDD (Hard-disk Drive).

[0035] The WLAN module 25 connects to a WLAN, enabling it to send and receive various types of data. The WLAN module 25 enables it to send and receive various types of data with other devices connected to other networks via the WLAN or through the WLAN. These other networks may be, for example, the Internet, a public wireless network, or a virtual private network.

[0036] The I / F26 input / output interface connects to various devices for data input and output via wired or wireless connections. The I / F26 includes, for example, a USB connector. The USB connector is a connector for wired data input and output in accordance with USB specifications.

[0037] The Embedded Controller (EC) 31 is a controller that monitors and controls the operation of various devices connected to it, regardless of the operating state of the host system 10. The EC 31 is separate from the host system 10 and includes a CPU, ROM, RAM, timers (e.g., an RTC (Real Time Clock) timer), and input / output interfaces. Devices with a lower data transfer speed than the chipset 21 can be connected to the EC 31. In the example in Figure 1, an input device 32, a power supply circuit 34, and a power button 38 are connected to the EC 31.

[0038] The input device 32 detects user operations, generates an operation signal according to the detected operation, and outputs the generated operation signal to EC31. The input device 32 may be, for example, a keyboard, a touch sensor, a trackpoint, or any combination thereof.

[0039] The power supply circuit 34 supplies power to each device according to the control of EC31. The power supply circuit 34 includes a charger and a transformer (DC / DC, Direct Current / Direct Current). The charger charges the battery with surplus power from the external power source that is not consumed by each device. If power is not supplied from the external power source, or if the power supplied from the power source does not meet the needs of each device, the charger supplies power discharged from the battery to each device via a transformer. A transformer converts the voltage of DC power supplied from an external power source or battery via a charger into the voltage required for the operation of each device. The transformer then supplies the DC power with the converted voltage to the target device.

[0040] Each time the power button 38 is pressed, it notifies EC31 of an instruction to the electronic device 1 to either power on or power off. When the power button 38 is pressed, it outputs a press signal to EC31. When the electronic device 1 is powered off and a press signal is input from the power button 38, EC31 instructs the power supply circuit 34 to start supplying power to each device of the electronic device 1 (power on).

[0041] On the other hand, when power is supplied to the electronic device 1 and a press signal is input from the power button 38, EC31 causes the CPU 11 to perform a shutdown process. During the shutdown process, the CPU 11 saves the data currently present in the work area to the storage 23. After the data saving is complete, the CPU 11 stops processing based on the applications, device drivers, and other programs currently running. Subsequently, the CPU 11 notifies EC31 that the shutdown process is complete. EC31 then causes the power supply circuit 34 to stop supplying power to each device of the electronic device 1.

[0042] Next, an example of the functional configuration of the electronic device 1 according to this embodiment will be described. Figure 3 is a schematic block diagram showing an example of the functional configuration of the electronic device 1 according to this embodiment. The host system 10 includes a BIOS processing unit 110 and an OS processing unit 120. The functions of the BIOS processing unit 110 are realized by the CPU 11 executing the BIOS. When the CPU 11 detects power-on, it reads various drivers that constitute the BIOS, which are stored in the ROM 22 beforehand, and starts the functions of the BIOS processing unit 110. At this time, the BIOS processing unit 110 executes a preboot process. The preboot process is part of the startup process. The preboot process includes detecting the devices that make up the electronic device 1, initializing the detected devices (POST process), and loading the OS. In this application, the startup process refers to a series of processes until the entire electronic device 1 becomes usable so that it can perform the expected functions from power-on. Boot mainly refers to the process related to starting the OS (OS boot). Reboot mainly refers to the process related to restarting. The BIOS processing unit 110 manages the detected devices and supports device control and input / output by the OS even after the OS has started.

[0043] The BIOS processing unit 110 is pre-configured with maintenance boot enabled, LCM HTTPS Boot as a maintenance boot option, and the maintenance cycle (e.g., weekly or daily) and maintenance time within that cycle (e.g., a set of day and time or specific time). These settings can be specified as BIOS setup settings. For example, RTC (Real-time Clock) Wake settings are applied to the maintenance cycle and maintenance time settings. RTC Wake settings are setting information for the RTC timer. The RTC timer is a timer that measures the time at that moment (current time). The RTC timer operates regardless of whether power is supplied to the host system 10.

[0044] The BIOS processing unit 110 activates the communication function with the server device 2 at the set startup time at set intervals and retrieves any unexecuted actions issued by the server device 2. To retrieve actions, the BIOS processing unit 110 attempts LCM HTTPS boot to activate the communication function. LCM HTTPS boot corresponds to one of the boot options related to BIOS maintenance. In attempting LCM HTTPS Boot, the BIOS processing unit 110 installs the driver related to LCM HTTPS Boot. That is, the BIOS processing unit 110 reads the driver from ROM 22, loads the read driver into main memory 12, and makes it executable. The BIOS processing unit 110 accesses the server device 2 using the WLAN module 25 and retrieves any unexecuted actions at that time. The BIOS processing unit 110 executes the processing instructed by the retrieved action. After that, if the OS is not started, the BIOS processing unit 110 starts (boots) the OS, or if the OS is running, it restarts (reboots) the OS.

[0045] The OS processing unit 120 executes the OS and related software and provides basic functions. Related software refers to software that works in cooperation with the OS. Related software includes, for example, device drivers and utilities. Basic functions include memory management, task management, file management, input / output management, and execution management of application software (sometimes referred to as "apps" or "applications" in this application). The functions of the OS processing unit 120 are provided after the OS has finished booting or rebooting. The OS processing unit 120 may also notify the EC31 of the power mode of the host system 10 when it changes. The EC31 sends power corresponding to the notified power mode to the host device and other devices.

[0046] In this embodiment, the trigger for attempting HTTPS Boot and attempting to obtain maintenance actions may be any of the following: (1) when the electronic device 1 is powered off, (2) when the power mode is in sleep mode (e.g., modern standby) while the OS is running, or (3) during startup processing in response to user operation (e.g., pressing the power button 38). The BIOS processing unit 110 receives notification of the current time from the RTC timer, and when the current time reaches the maintenance time for each maintenance cycle, the BIOS processing unit 110 attempts HTTPS Boot.

[0047] If electronic device 1 is powered off during the maintenance time, EC31 instructs the power supply circuit 34 to power on the host device. The BIOS processing unit 110 starts its function and attempts HTTPS Boot. However, after the maintenance action and the OS boot or reboot are completed, the CPU 11 performs a shutdown process. As a result, electronic device 1 returns to a powered-off state.

[0048] If the OS is running and the power mode is sleep mode during maintenance, the OS processing unit 120 stops the processing on the OS at that time and puts it into hibernation. More specifically, the OS processing unit 120 saves image data, including the program being processed, data, and parameters used in the processing, which indicate the processing status at that time, to the storage 23. After that, the CPU 11 stops its processing, and the EC31 temporarily stops the power supply to the host device from the power circuit 34. After that, the EC31 restarts the power supply to the host device from the power circuit 34. The BIOS processing unit 110 resumes its function and attempts HTTPS Boot. However, after the execution of the action and the completion of the OS boot or reboot, the OS processing unit 120 transitions the power mode from normal mode to sleep mode.

[0049] If a startup process is performed in response to user input during maintenance time, the BIOS processing unit 110 starts its function and attempts HTTPS Boot. However, after the execution of the action and the completion of OS booting or rebooting, the OS processing unit 120 maintains the power mode in normal mode.

[0050] Next, a first example of the maintenance process according to this embodiment will be described. Figure 4 is a flowchart illustrating a first example of the maintenance process according to this embodiment. The process in Figure 4 is an example of a case where the electronic device 1 is started when the power is off.

[0051] (Step S102) The RTC timer determines whether the current time has exceeded the maintenance time set in the RTC Wake settings. If it is determined that it has exceeded the maintenance time (Step S102 YES), the process proceeds to Step S104. If it is determined that it has not exceeded the maintenance time (Step S102 NO), the process of Step S102 is repeated. (Step S104) EC31 instructs the power supply circuit 34 to power on the host device. At this time, the BIOS processing unit 110 starts functioning. (Step S106) The BIOS processing unit 110 sets the initial value of the MBM flag to 1. The MBM (Maintenance Boot Mode) flag is a 1-bit piece of information that indicates whether or not the system operates in maintenance boot mode, depending on whether its value is 1 or 0.

[0052] (Step S108) If the value of the MBM flag is 1 (Step S108 YES), proceed to step S110. If the value of the MBM flag is zero (Step S108 NO), proceed to step S130. (Step S110) The BIOS processing unit 110 attempts LCM HTTPS Boot.

[0053] (Step S112) The BIOS processing unit 110 determines whether the BIOS Network is enabled or not. The BIOS Network being enabled indicates that the communication function is active. That is, the communication interface (WLAN module 25 in the example in Figure 1) is detected, and the driver required to implement the communication function is executable. If it is enabled (Step S112 YES), the process proceeds to step S114. If it is not enabled (Step S112 NO), the process proceeds to step S116. (Step S114) The BIOS processing unit 110 executes LCM HTTPS Boot, accesses the server device 2, and sends a maintenance action request to the electronic device 1. (Step S116) The BIOS processing unit 110 sets the value of the MBM flag to zero. Then, it proceeds to the process in step S130.

[0054] (Step S118) The BIOS processing unit 110 is notified by the server device 2 whether or not there are any unexecuted maintenance actions in response to the maintenance action request. If there are any unexecuted maintenance actions (Step S118 YES), the process proceeds to step S120. In this case, the BIOS processing unit 110 is notified of the unexecuted maintenance action. If there are no unexecuted maintenance actions (Step S118 NO), the process proceeds to step S122.

[0055] (Step S120) The BIOS processing unit 110 executes any unexecuted maintenance actions. However, if multiple unexecuted maintenance actions are notified, the BIOS processing unit 110 executes the first maintenance action in order and does not execute any other unexecuted maintenance actions. When the BIOS processing unit 110 has completed the execution of a maintenance action, it notifies the server device 2 of the completion of that maintenance action. (Step S122) The BIOS processing unit 110 sets the value of the MBM flag to zero. Then, it proceeds to the process in step S130.

[0056] (Step S124) The BIOS processing unit 110 determines whether the completed maintenance action is the last maintenance action among the notified unexecuted maintenance actions. If it is determined to be the last maintenance action (Step S124 YES), the process proceeds to step S126. If it is not determined to be the last maintenance action (Step S124 NO), the process proceeds to step S128. (Step S126) The BIOS processing unit 110 sets the value of the MBM flag to zero. (Step S128) The BIOS processing unit 110 executes the POST process and then starts the OS reboot process. However, if there is only one unexecuted maintenance action that has been notified, or if the first of several unexecuted maintenance actions has already been executed, the BIOS processing unit 110 starts the normal boot process instead of the reboot process. Then, the process proceeds to step S108. (Step S130) The CPU 11 performs a shutdown process. Then, the EC 31 stops supplying power to each device of the electronic equipment 1 via the power supply circuit 34 (power OFF). After that, the process shown in Figure 4 is terminated.

[0057] Next, a second example of the maintenance process according to this embodiment will be described. Figure 5 is a flowchart illustrating a second example of the maintenance process according to this embodiment. The process in Figure 5 is an example of a case where the OS of the electronic device 1 has been started and is in operation.

[0058] (Step S202) When the power mode of the host system 10 is in normal mode, the OS processing unit 120 detects the usage status of the electronic device 1 and transitions the power mode from normal mode to modern standby (ModS) when predetermined transition conditions are met. The transition conditions include events that suggest non-use or indifference by the user. Transition conditions include, for example, when no user operation is detected for a predetermined period of time or when sleep is instructed in response to user operation according to the settings screen. In the case of a notebook PC, the transition conditions include when two connected casings are closed. A notebook PC, for example, has a sensor in one casing that can detect the open / closed state of the other casing based on a physical quantity (e.g., magnetic field, capacitance, etc.) detected by the sensor. Normal mode is the operating mode in which the electronic device 1 performs the functions expected of it. Normal mode corresponds to the S0 state among the power states defined by ACPI (Advanced Configuration and Power Interface). Modern standby is an operating mode that consumes less power than normal mode and involves a state in which the display of information to the user, such as screen display, is stopped (screen off). However, in modern standby, connections to other devices and acceptance of operation input are maintained. Modern standby is a type of sleep state, but corresponds to an extended state of the S0 state.

[0059] (Step S204) The OS processing unit 120 checks the current time notified by the RTC timer. (Step S206) The OS processing unit 120 determines whether the current time has exceeded the MBM time. The maintenance time mentioned above is set as the initial value of the MBM time. If it is determined that the MBM time has exceeded (Step S206 YES), the process proceeds to step S208. If it is determined that the MBM time has not exceeded (Step S206 NO), the process returns to step S204.

[0060] (Step S208) The OS processing unit 120 notifies the BIOS processing unit 110 and EC31 of a power-on request to the host device immediately after the host system 10 transitions to the S4 power mode. The S4 state corresponds to the hibernation state, which is defined by ACPI as a power state in which the host device is not operating. Immediately before changing the power mode to the S4 state, the CPU 11 saves the operating state of the electronic device 1 up to that point. At this time, the CPU 11 saves image data showing various information expanded in the main memory 12 to the storage 23, and then uses EC31 to stop the power supply to itself and the main memory 12 to the power circuit 34. The BIOS processing unit 110 sets up S4 startup by EC31 based on the power-on request notified by the OS processing unit 120. S4 startup means restarting the functions of the host system 10 and transitioning the power mode from the S4 state to the normal mode.

[0061] (Step S210) EC31 restarts the power supply circuit 34 to the host device in response to the notified power supply request. (Step S212) Power is supplied to the host device, the BIOS processing unit 110 resumes functioning, and POST processing begins. (Step S214) The BIOS processing unit 110 determines whether S4 Wake is set by EC31. If S4 Wake is set (Step S214 YES), the process proceeds to step S216. If S4 Wake is not set (Step S214 NO), the process proceeds to step S218. If S4 Wake is not set, the electronic device 1 may be started by pressing the power button 38, for example.

[0062] (Step S216) The BIOS processing unit 110 sets the MBM flag value to 1 and sets the MBM time to the next time. The next time corresponds to the time after a predetermined processing cycle has elapsed from the current time. As the processing cycle, the upper limit of the time required for one processing cycle, from the transition of the power mode from modern standby to S4 state, S4 startup, execution of an action, reboot, to the transition of the power mode from S0 state to modern standby, can be set in advance in the BIOS processing unit 110. (Step S218) The BIOS processing unit 110 determines the value of the MBM flag. If the value of the MBM flag is 1 (Step S218 YES), the process proceeds to step S220. If the value of the MBM flag is not 1 (Step S218 NO), the process proceeds to step S242. (Step S220) The BIOS processing unit 110 attempts LCM HTTPS Boot.

[0063] (Step S222) The BIOS processing unit 110 determines whether the BIOS Network is enabled or not. If it is enabled (Step S222 YES), the process proceeds to step S224. If it is not enabled (Step S222 NO), the process proceeds to step S226. (Step S224) The BIOS processing unit 110 executes LCM HTTPS Boot, accesses the server device 2, and sends a maintenance action request to the electronic device 1. (Step S226) The BIOS processing unit 110 sets the value of the MBM flag to zero. Then, it proceeds to step S242.

[0064] (Step S228) The BIOS processing unit 110 is notified by the server device 2 whether or not there are any unexecuted maintenance actions in response to the maintenance action request. If there are any unexecuted maintenance actions (Step S228 YES), the process proceeds to step S230. If there are no unexecuted maintenance actions (Step S228 NO), the process proceeds to step S232.

[0065] (Step S230) The BIOS processing unit 110 executes any unexecuted maintenance actions. However, if multiple unexecuted maintenance actions are notified, the BIOS processing unit 110 executes the first maintenance action in order and does not execute any other unexecuted maintenance actions. When the BIOS processing unit 110 has completed the execution of a maintenance action, it notifies the server device 2 of the completion of that maintenance action. (Step S232) The BIOS processing unit 110 sets the value of the MBM flag to zero. Then, the process proceeds to step S242.

[0066] (Step S234) The BIOS processing unit 110 determines whether the completed maintenance action is the last maintenance action among the notified unexecuted maintenance actions. If it is determined to be the last maintenance action (Step S234 YES), the process proceeds to step S240. If it is not determined to be the last maintenance action (Step S234 NO), the process proceeds to step S236. (Step S236) The BIOS processing unit 110 initiates the OS reboot process. After that, the OS processing unit 120 starts its functions. (Step S238) The OS processing unit 120 transitions the power mode from normal mode to modern standby (ModS). Then, it returns to the process in step S204.

[0067] (Step S240) The BIOS processing unit 110 sets the value of the MBM flag to zero. (Step S242) The BIOS processing unit 110 initiates the OS reboot process. After that, the OS processing unit 120 starts functioning. (Step S244) The OS processing unit 120 transitions the power mode from normal mode to modern standby. After that, it terminates the process shown in Figure 5.

[0068] Next, a third example of the maintenance process according to this embodiment will be described. Figure 6 is a flowchart illustrating a sixth example of the maintenance process according to this embodiment. The process in Figure 6 is an example in which power supply is started when the power button 38 is pressed when the state of the electronic device 1 is powered off.

[0069] (Step S302) When EC31 detects that the power button 38 has been pressed, it instructs the power supply circuit 34 to power on the host device. At this time, the BIOS processing unit 110 starts functioning and POST processing begins. (Step S304) The BIOS processing unit 120 checks the current time notified by the RTC timer. (Step S306) The BIOS processing unit 120 determines whether the current time has exceeded the MBM time. The maintenance time described above is set as the initial value of the MBM time. If it is determined that the MBM time has exceeded the MBM time (Step 306 YES), the process proceeds to step S308. If it is determined that the MBM time has not exceeded the MBM time (Step 306 NO), the process proceeds to step S310.

[0070] (Step S308) The BIOS processing unit 110 sets the value of the MBM flag to 1 and sets the MBM time to the next time. The next time corresponds to the time after a predetermined processing cycle has elapsed from the current time. (Step S310) The BIOS processing unit 110 determines the value of the MBM flag. If the value of the MBM flag is 1 (Step S310 YES), the process proceeds to step S312. If the value of the MBM flag is not 1 (Step S310 NO), the process proceeds to step S336. (Step S312) The BIOS processing unit 110 attempts LCM HTTPS Boot.

[0071] (Step S314) The BIOS processing unit 110 determines whether the BIOS Network is enabled or not. If it is enabled (Step S314 YES), the process proceeds to step S316. If it is not enabled (Step S314 NO), the process proceeds to step S318. (Step S316) The BIOS processing unit 110 executes LCM HTTPS Boot, accesses the server device 2, and sends a maintenance action request to the electronic device 1. (Step S318) The BIOS processing unit 110 displays a network connection warning screen on the display 14. The network connection warning screen includes either or both notification information indicating that a network connection cannot be established, and guidance information showing how to configure the network connection (see Figure 7). The process then proceeds to step S334.

[0072] (Step S320) The BIOS processing unit 110 is notified by the server device 2 whether or not there are any unexecuted maintenance actions in response to the maintenance action request. If there are any unexecuted maintenance actions (Step S320 YES), the process proceeds to step S322. If there are no unexecuted maintenance actions (Step S320 NO), the process proceeds to step S334.

[0073] (Step S322) The BIOS processing unit 110 executes any unexecuted maintenance actions. However, if multiple unexecuted maintenance actions are notified, the BIOS processing unit 110 executes the first maintenance action in order and does not execute any other unexecuted maintenance actions. When the BIOS processing unit 110 has completed the execution of a maintenance action, it notifies the server device 2 of the completion of that maintenance action. (Step S324) The BIOS processing unit 110 determines whether the completed maintenance action is the last maintenance action among the notified unexecuted maintenance actions. If it is determined to be the last maintenance action (Step S324 YES), the process proceeds to step S326. If it is not determined to be the last maintenance action (Step S324 NO), the process proceeds to step S330. (Step S326) The BIOS processing unit 110 sets the value of the MBM flag to zero. Then, the process proceeds to step S328.

[0074] (Step S328) The BIOS processing unit 110 initiates the OS reboot process. After that, the OS processing unit 120 starts functioning, and the process shown in Figure 6 is completed. (Step S330) The BIOS processing unit 110 initiates the OS reboot process. After that, the OS processing unit 120 starts functioning. (Step S332) The OS processing unit 120 instructs EC31 to power on after shutdown. The CPU 11 then performs a shutdown process. After that, the process returns to step S302. In step S302, EC31 instructs the power supply circuit 34 to start supplying power to the host device, and the POST process begins.

[0075] (Step S334) The BIOS processing unit 110 sets the value of the MBM flag to zero and exits maintenance boot mode. (Step S336) The BIOS processing unit 110 returns to the normal boot menu. (Step S338) The BIOS processing unit 110 executes the normal boot process of the OS. After that, the functions of the OS processing unit 120 are started, and the process shown in Figure 6 is completed.

[0076] The above explanation primarily assumes that the firmware is system firmware related to the host system, but it is not limited to this. The firmware may also be a device driver for other types of devices. Other types of devices may include, for example, the video subsystem 13, the display 14, the WLAN module 25, the input / output interface 26, etc.

[0077] Electronic device 1 is not necessarily limited to a notebook PC, but may be an electronic device implemented in other forms, such as a desktop PC or a tablet terminal. Furthermore, server device 2 is not necessarily limited to a server device dedicated to maintenance, but may be any external device capable of providing various maintenance actions to electronic device 1 via a communication network. Such external device may be, for example, a general-purpose server device such as a web server, or a communication device installed at the user's facility, or another device installed alongside such communication device. Also, the interface providing communication functionality is not limited to the WLAN module 25, but may be a communication interface compatible with communication methods other than WLAN, such as a mobile communication card or an Ethernet card.

[0078] Furthermore, the above explanation uses the example of electronic device 1 enabling its communication function at predetermined maintenance intervals, each time the maintenance time has elapsed, to receive commands from external devices. However, the maintenance interval does not necessarily have to be constant as long as the communication function can be enabled intermittently. For example, if the OS processing unit 120 is running when the maintenance time has elapsed, after the shutdown process executed immediately afterward is completed, electronic device 1 may execute the processes from step S104 onward in Figure 4. In addition, the BIOS processing unit 110 may be configured to allow setting maintenance times for each day of the week, or for weekdays or holidays. The BIOS processing unit 110 may record the power-on and power-off times for each day and set the maintenance time within the unused period from the power-off time to the next power-on time.

[0079] As described above, the electronic device 1 according to this embodiment comprises a device that operates based on firmware and an interface that provides communication functionality (e.g., a WLAN module 25). The firmware-based operation has selectable options for execution, and the device intermittently enables communication functionality (e.g., attempts LCM HTTP Boot), and when communication functionality (e.g., BIOS Network) is enabled, it executes optional processing according to commands obtained from an external device (e.g., a server device 2). This configuration intermittently enables communication to receive commands issued by external devices, and processes firmware options according to the received commands. Therefore, even if relatively infrequently used options are notified by commands received from external devices, there is an opportunity for those options to be processed. In turn, firmware maintenance through option processing is promoted.

[0080] Furthermore, the electronic device 1 may be equipped with a timer for timing the current time (e.g., an RTC timer), and the communication function may be activated when the current time has elapsed to a predetermined date and time (e.g., MBM time). In this configuration, the communication function is activated at a predetermined date and time, and optional processing is executed according to commands received from external devices. Furthermore, by periodically activating the communication function, opportunities to execute notified optional processing are periodically obtained.

[0081] Furthermore, the above-mentioned device may be a host device that constitutes the host system 10. The host system 10 may verify the effectiveness of the communication function during the initialization process. This configuration allows for the acquisition of commands from external devices during the initialization process. Therefore, optional processing is more reliably implemented.

[0082] Furthermore, the host system 10 may, while in a power-off state, start an initialization process when the current time has elapsed to a predetermined date and time, and after the completion of optional processing, change back to a power-off state. With this configuration, after the optional process is completed, the system returns to the same power-off state as before the process was executed. Therefore, the process is executed when the system is not in use, without the user being aware of it.

[0083] Furthermore, the host system 10 may operate in a low-power mode, which consumes less power than the standard power mode, and when the current time has elapsed to a predetermined date and time, it may pause its operation before starting the initialization process (for example, by transitioning to the S4 state), and after the completion of optional processing, it may perform a restart process (for example, a reboot) and change the power mode to low-power mode. With this configuration, the system pauses before starting the initialization process when operating in low-power mode, preserving the execution state before the initialization process began. Furthermore, after the optional process is completed, the system returns to the same low-power mode state as before the optional process was executed. Therefore, the process is executed without the user's awareness when it is not in use, and the system resumes operation from the execution state before the optional process was executed.

[0084] When the host system 10 detects a startup instruction while powered off, it may start an initialization process, enable the communication function when the current time has elapsed to a predetermined date and time, and execute the startup process after the completion of optional processing. In this configuration, when a startup command is issued, the startup process is executed after the current time reaches a predetermined date and time, and after optional processing has been performed. The purpose of putting the system into a startup state is achieved by the startup command, and optional processing is performed intermittently before the system enters a startup state.

[0085] The above device may repeat the process based on one of the unexecuted instructions, followed by a restart process after the completion of the process, until there are no more unexecuted instructions. In this configuration, when multiple commands are notified from an external device, a restart process is executed after each command is completed. Therefore, even if the firmware configuration changes due to the execution of each command, the changed state is reflected in the functions of the host system 10 through the OS restart process.

[0086] Although embodiments of the present invention have been described in detail above with reference to the drawings, the specific configurations are not limited to the embodiments described above, and include designs and the like that do not depart from the spirit of this invention. The configurations described in the embodiments described above can be combined in any way. [Explanation of Symbols]

[0087] S1...Maintenance System, 1...Electronic Devices, 2...Server Device, 10...Host System, 11...CPU, 12...Main Memory, 13...Video Subsystem, 14...Display, 21...Chipset, 22...ROM, 23...Storage, 25...WLAN Module, 26...Input / Output Interface, 31...EC, 32...Input Device, 34...Power Circuit, 38...Power Button, 110...BIOS Processing Unit, 120...OS Processing Unit

Claims

1. Devices that operate based on firmware, It includes an interface that provides communication functionality, The aforementioned operation has an option to choose whether or not to perform it. The device described above, The communication function is enabled intermittently, When the aforementioned communication function is enabled, the processing of the option is executed according to the command received from the external device. electronic equipment.

2. Equipped with a timer to measure the current time, The communication function is activated when the current time has elapsed to a predetermined date and time. The electronic device according to claim 1.

3. The aforementioned device is a host device that constitutes a host system, The host system, in the initialization process, Confirm the effectiveness of the aforementioned communication function. The electronic device according to claim 2.

4. The host system, in a power-off state, When the current time has elapsed to a predetermined date and time, the initialization process is started. After the completion of the processing of the aforementioned option, Change to the aforementioned power-off state. The electronic device according to claim 3.

5. The host system operates in a low-power mode, which is a power mode that consumes less power than the standard power mode. When the current time has elapsed to a predetermined date and time, the operation is paused before starting the initialization process. After the completion of the processing of the aforementioned option, The restart process is executed, and the power mode is changed to the low power mode. The electronic device according to claim 3.

6. The host system, in a power-off state, When a startup instruction is detected, the initialization process is started. When the current time has elapsed to a predetermined date and time, the aforementioned communication function will be activated. After the processing of the aforementioned options is complete, the startup process is executed. The electronic device according to claim 3.

7. The device described above, Processing based on one of the aforementioned unexecuted instructions, The restart process after the completion of the aforementioned process is Repeat until there are no more unexecuted commands. The electronic device according to claim 1.

8. Devices that operate according to their firmware, A control method for an electronic device comprising an interface that provides communication functions, The aforementioned operation has an option to choose whether or not to perform it. The device described above, The communication function is enabled intermittently, When the aforementioned communication function is enabled, the processing of the option is executed according to the command received from the external device. Control method.

Images