KR102968552B1 - Method for rebooting and electronic device supporting same - Google Patents

Abstract

An electronic device is disclosed that includes a memory and a processor, wherein the processor checks the status of the memory and, based on the check result, registers a reboot alarm when it detects a low state of the memory, and when the time corresponding to the reboot alarm arrives, checks whether the electronic device is in use and, if the electronic device is not in use, reboots the device. In addition to this, various embodiments identified through this document are possible.

Description

Method for rebooting and electronic device supporting the same

Various embodiments of this document relate to a method for rebooting and an electronic device that supports the same.

Electronic devices (e.g., smartphones) can provide users with various functions. As electronic devices perform various operations corresponding to these functions, situations may arise where memory capacity is insufficient, which can degrade the usability of the device. For instance, if the memory capacity of an electronic device is insufficient, the processing speed may slow down.
The technology forming the background of the present disclosure is disclosed in the following literature.
1) U.S. Patent Application Publication US 2008/0294936 (Nov. 27, 2008)
2) Published Patent Application No. 10-2013-0004174 (January 9, 2013)

Previously, electronic devices received user input to reboot. The electronic device initiated a reboot in response to receiving user input; consequently, users using the electronic device may experience inconvenience as they are unable to use the device when needed due to the reboot.

Various embodiments disclosed in this document can resolve inconvenience that may occur to the user by determining whether the electronic device is currently being used by the user when the electronic device detects a state of insufficient available memory, and automatically rebooting the device if it is not being used by the user.

An electronic device according to various embodiments of the present invention includes a memory and a processor, and the processor checks the state of the memory and, based on the check result, registers a reboot alarm when it detects a state of insufficient memory, and when the time corresponding to the reboot alarm arrives, checks whether the electronic device is in use and, if the electronic device is not in use, can reboot it.

An electronic device according to various embodiments of the present invention includes a display, a memory, and a processor, and the processor checks the state of the memory and, if it detects a low state of the memory based on the check result, outputs a message requesting the selection of a reboot time of the electronic device through the display.

A method of operating an electronic device according to various embodiments of the present invention may include an operation of checking the state of a memory, an operation of registering a reboot alarm when a state of insufficient memory is detected based on the result of the check, an operation of checking whether the electronic device is in use when a time corresponding to the reboot alarm arrives, and an operation of rebooting the electronic device when it is not in use.

According to various embodiments disclosed in this document, a method for rebooting and an electronic device supporting the same can resolve inconvenience that may occur to the user by determining whether the electronic device is currently being used by the user when a state of insufficient available memory is detected, and by automatically executing a reboot if it is not in use. According to various embodiments, the electronic device switches to a silent mode before rebooting, and since it reboots in silent mode upon rebooting, it can resolve inconvenience that may occur to the user due to notification sounds and vibrations. According to various embodiments, the electronic device saves setting information before rebooting, and after a certain period of time has elapsed after the reboot is completed, the settings of the electronic device can be restored to the settings prior to the reboot based on the saved setting information. Therefore, the user can resolve the inconvenience of having to reset the settings of the electronic device.

In addition to this, various effects that can be identified directly or indirectly through this document may be provided.

FIG. 1 is a block diagram of an electronic device in a network environment according to various embodiments of the present invention.
FIG. 2 is a block diagram of an electronic device according to one embodiment of the present invention.
FIG. 3 is a block diagram of configurations for rebooting according to an embodiment of the present invention.
FIG. 4 is a flowchart illustrating a method for rebooting according to an embodiment of the present invention.
FIG. 5 is a flowchart illustrating operations performed to reboot according to an embodiment of the present invention.
FIG. 6 is a flowchart illustrating other operations performed to reboot according to one embodiment of the present invention.
FIG. 7 is a flowchart illustrating another method of rebooting according to one embodiment of the present invention.

In relation to the description of the drawings above, the same reference number may be assigned to identical or corresponding components.

Hereinafter, various embodiments of the present invention are described with reference to the attached drawings. For convenience of explanation, the size of the components illustrated in the drawings may be exaggerated or reduced, and are not limited to what is illustrated.

FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to various embodiments. Referring to FIG. 1, in the network environment (100), the electronic device (101) may communicate with an electronic device (102) through a first network (198) (e.g., a short-range wireless communication network) or with an electronic device (104) or a server (108) through a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) through a server (108). According to one embodiment, the electronic device (101) may include a processor (120), memory (130), input module (150), sound output module (155), display module (160), audio module (170), sensor module (176), interface (177), connection terminal (178), haptic module (179), camera module (180), power management module (188), battery (189), communication module (190), subscriber identification module (196), or antenna module (197). In some embodiments, at least one of these components (e.g., connection terminal (178)) may be omitted from the electronic device (101), or one or more other components may be added. In some embodiments, some of these components (e.g., sensor module (176), camera module (180), or antenna module (197)) may be integrated into a single component (e.g., display module (160)).

The processor (120) can control at least one other component (e.g., hardware or software component) of the electronic device (101) connected to the processor (120) by executing software (e.g., program (140)), for example, and can perform various data processing or operations. According to one embodiment, as at least part of the data processing or operations, the processor (120) can store commands or data received from other components (e.g., sensor module (176) or communication module (190)) in volatile memory (132), process the commands or data stored in volatile memory (132), and store the resulting data in non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., central processing unit or application processor) or an auxiliary processor (123) that can operate independently or together with it (e.g., graphics processing unit, neural processing unit (NPU), image signal processor, sensor hub processor, or communication processor). For example, if the electronic device (101) includes a main processor (121) and an auxiliary processor (123), the auxiliary processor (123) may be configured to use lower power than the main processor (121) or to be specialized for a designated function. The auxiliary processor (123) may be implemented separately from the main processor (121) or as part thereof.

The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence is performed, or through a separate server (e.g., server (108)). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), deep Q-networks, or a combination of two or more of the above, but is not limited to the examples described above. In addition to the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

The memory (130) can store various data used by at least one component of the electronic device (101) (e.g., processor (120) or sensor module (176)). The data may include, for example, input data or output data for software (e.g., program (140)) and related commands. The memory (130) may include volatile memory (132) or non-volatile memory (134).

The program (140) may be stored as software in memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

The input module (150) can receive commands or data to be used for a component of the electronic device (101) (e.g., processor (120)) from outside the electronic device (101) (e.g., user). The input module (150) may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

The sound output module (155) can output a sound signal to the outside of the electronic device (101). The sound output module (155) may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as multimedia playback or recording playback. The receiver may be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part thereof.

The display module (160) can visually provide information to an external (e.g., user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling said device. According to one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of the force generated by said touch.

The audio module (170) can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150) or output sound through the sound output module (155) or an external device (e.g., electronic device (102)) (e.g., speaker or headphones) that is directly or wirelessly connected to the electronic device (101).

The sensor module (176) can detect the operating state of the electronic device (101) (e.g., power or temperature) or the external environmental state (e.g., user state) and generate an electrical signal or data value corresponding to the detected state. According to one embodiment, the sensor module (176) may include, for example, a gesture sensor, a gyroscope sensor, a barometric pressure sensor, a magnetic sensor, an accelerometer sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biosensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface (177) may support one or more specified protocols that can be used for the electronic device (101) to be connected directly or wirelessly to an external device (e.g., electronic device (102)). According to one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal (178) may include a connector through which the electronic device (101) can be physically connected to an external device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

The camera module (180) can capture still images and video. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module (188) can manage the power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least part of a power management integrated circuit (PMIC).

The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

The communication module (190) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an electronic device (101) and an external device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (104) through a first network (198) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules may be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (196).

The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), full-dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large-scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), external device (e.g., electronic device (104)), or network system (e.g., second network (199)). According to one embodiment, the wireless communication module (192) can support a Peak data rate (e.g., 20 Gbps or more) for realizing eMBB, loss coverage (e.g., 164 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) for realizing URLLC.

An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (197).

According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

At least some of the above components can be connected to each other via a communication method between peripheral devices (e.g., bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)) and exchange signals (e.g., commands or data) with each other.

According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) through a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or different type of device as the electronic device (101). According to one embodiment, all or part of the operations performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and/or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within a second network (199). The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

FIG. 2 is a block diagram of an electronic device according to one embodiment of the present invention.

Referring to FIG. 2, an electronic device (200) (e.g., the electronic device (101) of FIG. 1) can detect a state in which available memory is insufficient due to the accumulation of processes in memory (203) (e.g., the memory (130) of FIG. 1). Upon detecting the insufficient available memory state, the electronic device (200) can determine whether it is currently being used by a user. If the electronic device (200) is not currently being used by a user, it can automatically reboot to resolve the insufficient available memory state. For example, if the electronic device (200) detects the insufficient available memory state, the processing speed may be slowed down.

According to one embodiment, the electronic device (200) may include a display (201) (e.g., the display module (160) of FIG. 1), a memory (203) (e.g., the memory (130) of FIG. 1), and a processor (205) (e.g., the processor (120) of FIG. 1). However, the configuration of the electronic device (200) is not limited thereto.

According to various embodiments, the electronic device (200) may omit at least one of the components described above and may include at least one other component. For example, the electronic device (200) may include a communication module (e.g., the communication module (190) of FIG. 1). The electronic device (200) may transmit and receive data with another electronic device (e.g., the electronic device (102 or 104) of FIG. 1) through the communication module.

According to one embodiment, the processor (205) can detect a state in which available memory in the memory (203) is insufficient. The processor (205) can detect a state in which available memory is insufficient and determine whether the electronic device (200) is currently being used by a user. For example, the processor (205) can determine that the electronic device (200) is currently being used by a user if at least one of the display (201), speaker (not shown) (e.g., sound output module (155) of FIG. 1), microphone (not shown) (e.g., input module (150) of FIG. 1), sensor (not shown) (e.g., sensor module (176) of FIG. 1), camera (not shown) (e.g., camera module (180) of FIG. 1) and communication module (not shown) (e.g., communication module (190) of FIG. 1) of the electronic device (200) is operating.

According to one embodiment, the processor (205) may store setting information when it is determined by a user that the electronic device (200) is not in use. The setting information may include volume levels (e.g., ringtone volume, media volume, call volume, and/or alarm volume) and information related to data connection status (e.g., whether mobile data is in use) set on the electronic device before rebooting.

Previously, when a full reset that completely reboots the electronic device (200) is completed, the processor (205) included in the electronic device (200) can receive a signal that the reboot is complete (e.g., boot-complete). However, when the processor (205) receives a signal that the reboot is complete (e.g., boot-complete), it initiates a file-based encryption (FBE) operation that sets the memory (203) to lock mode. Accordingly, if the downloaded content (e.g., audio source) is set as an alarm sound, the processor (205) cannot access the memory after the reboot, so the alarm sound may not be output, or the default alarm sound may be output. Therefore, after rebooting the electronic device (200), the processor (205) can store the setting information to provide the user with the electronic device (200) configured the same as before the reboot.

According to one embodiment, the processor (205) can store the setting information and switch or set the vibration function, audio function, and data connection function of the electronic device (200) to an off state. The processor (205) can switch or set to an off state not only of the above functions but also of functions that may cause inconvenience to the user as the electronic device (200) is rebooted, before rebooting.

According to one embodiment, the processor (205) may set a reboot value (e.g., reset reason) to a specified value. The reboot value may be a code value for determining how to reboot the electronic device (200). Additionally, the processor (205) may create a specified file in a protected area (e.g., an EFS area (encrypting file system zone)). The protected area may be an area that encrypts and protects files from an attacker hacking the electronic device (200). A detailed description regarding the specified file created in the protected area will be provided below.

According to one embodiment, the processor (205) can identify the reboot value. If the reboot value is the specified value, the processor (205) can platform reset the electronic device (200). The platform reset may be a method of rebooting the remaining configurations (e.g., applications and application frameworks) of the electronic device (200), excluding the kernel configuration.

According to one embodiment, the processor (205) can detect whether the specified file exists in the protection area when the platform reset is completed. If the specified file exists in the protection area, the processor (205) can skip the FBE operation of setting the memory (203) to lock mode before receiving a signal that the reboot (platform reset) is completed (e.g., boot-complete). Accordingly, the processor (205) can access the memory (203) and restore the settings of the electronic device (200) after the reboot based on the settings information saved before the reboot.

According to one embodiment, the processor (205) can restore the settings of the electronic device (200) based on the setting information after a specified time has elapsed. The specified time may be determined as the time after the electronic device (200) is rebooted and all possible vibrations, system sounds, and notification sounds are output.

According to another embodiment, the processor (205) can check that the available memory has become insufficient as processes accumulate in the memory (203). Based on the result of the check, if the processor (205) detects that the available memory (203) has become insufficient, it can output a message requesting the selection of a reboot time for the electronic device (200) through the display (201).

According to one embodiment, the processor (205) can control the timing of the reboot based on user input to the message. For example, if the processor (205) receives “Start now” as user input to the message, it can immediately start rebooting the electronic device (200). As another example, if the processor (205) receives “Start later” as user input to the message, it can output a timer in a part of the message to schedule the time to start the reboot. The processor (205) can receive reboot start time information (e.g., 04:25 tomorrow) from the user through the timer. When the time corresponding to the reboot start time arrives, the processor (205) can automatically start rebooting the electronic device (200).

According to one embodiment, when the time corresponding to the reboot start time arrives, the processor (205) can reboot the electronic device (200) by saving setting information and switching or setting functions that may cause inconvenience to the user to an off state. When the reboot is completed, the processor (205) can restore the settings of the electronic device (200) to the settings prior to the reboot based on the setting information.

According to various embodiments, an electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) includes a memory (e.g., the memory (130) of FIG. 1 or the memory (205) of FIG. 2)) and a processor (e.g., the processor (120) of FIG. 1 or the processor (203) of FIG. 2), and the processor checks the state of the memory and, based on the result of the check, if it detects a state of insufficient memory, registers a reboot alarm, and when the time corresponding to the reboot alarm arrives, checks whether the electronic device is in use and, if the electronic device is not in use, can reboot it.

According to various embodiments, the processor may store configuration information of the electronic device before rebooting the electronic device.

According to various embodiments, the processor can restore the settings of the electronic device based on the stored setting information after a specified time has elapsed following the completion of the reboot.

According to various embodiments, the setting information may include volume information and data connection status information prior to the electronic device automatically rebooting.

According to various embodiments, the processor may switch the output of the data connection pop-up of the electronic device to an off state before rebooting the electronic device, and switch the output of the data connection pop-up to a state prior to rebooting after the specified time has elapsed.

According to various embodiments, the specified time may be set as the time after all notification sounds generated when the electronic device is rebooted have occurred.

According to various embodiments, the processor may switch to silent mode before rebooting the electronic device.

According to various embodiments, the electronic device further includes a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2), and the processor can automatically reboot by setting the display to an off state.

According to various embodiments, the processor may execute the reboot by skipping the file-based encryption (FBE) operation.

According to various embodiments, an electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) includes a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2), a memory (e.g., the memory (130) of FIG. 1 or the memory (205) of FIG. 2), and a processor (e.g., the processor (120) of FIG. 1 or the processor (203) of FIG. 2), and the processor checks the state of the memory, and if it detects a low state of the memory based on the check result, it may output a message requesting the electronic device to select a reboot time through the display.

According to various embodiments, the processor may initiate the reboot if there is no response to the message output through the display for a certain period of time.

FIG. 3 is a block diagram of configurations for rebooting according to an embodiment of the present invention.

Referring to FIG. 3, the memory (e.g., memory (130) of FIG. 1 or memory (203) of FIG. 2) may include configurations for rebooting.

According to one embodiment, the memory may include an application (310), an application framework (330), and a kernel (350).

According to one embodiment, the application (310) may include device care (311) and alarm manager (313).

According to one embodiment, the application framework (330) may include a power manager (331), a storage manager (333), an audio manager (335), a logo animation manager (337), and a telephony manager (339).

According to one embodiment, the kernel (350) may include an audio driver (351).

According to one embodiment, the device care (311) can detect a state in which the available amount of memory becomes insufficient as processes accumulate in the memory. When the device care (311) detects a state insufficient for available memory, it can check setting information (e.g., information related to volume levels and information related to data connection status) set in the audio manager (335) and telephony manager (339), and store the checked setting information. For example, the information related to volume levels may include at least one of ringtone volume, media volume, call volume, and alarm volume. In addition, it may include information related to sound modes of the electronic device (e.g., sound, vibration, silence) as well as volume.

According to one embodiment, the device care (311) may request the logo animation manager (337) not to output a start sound indicating a reboot of the electronic device (e.g., the electronic device (200) of FIG. 2). Additionally, the device care (311) may request the audio manager (335) not to output system sounds, vibrations, and notification sounds of the electronic device. Additionally, the device care (311) may request the telephony manager (339) not to output a data connection pop-up of the electronic device.

According to one embodiment, the setting information may include volume information and data connection status information. The volume information may be information related to the volume level set on the electronic device before rebooting the electronic device. The data connection status information may be information related to whether the electronic device is connected to the wireless internet before rebooting the electronic device.

According to one embodiment, if the device care (311) detects the available memory shortage, it may set a reboot value (e.g., reset reason) to a specified value and create a specified file in a protected area (e.g., EFS (encrypting file system zone)). The reboot value may be a code value for determining how to initiate a reboot of the electronic device. The reboot method of the electronic device may be classified into a full reset, which completely reboots the electronic device, or a platform reset, which reboots the rest (e.g., applications (310) and application frameworks (330)) excluding the kernel (350).

According to one embodiment, the power manager (331) may perform a platform reset if it is identified that the reboot value is a specified value. The specified value may be a data value for resetting the electronic device platform. On the other hand, the power manager (331) may perform a full reset if the reboot value is not a specified value.

In the past, when an electronic device was fully reset, an FBE operation was initiated to set the memory to lock mode, making it impossible to access the configuration information stored in the memory set to lock mode. Consequently, the configuration of the electronic device after rebooting may not be restored. Therefore, the power manager (331) of the present invention can perform a platform reset of the electronic device instead of a full reset when the reboot value is identified as a specified value.

According to one embodiment, when the power manager (331) completes the platform reset, the storage manager (333) can check whether the specified file exists in the protection area. The specified file may be a file required to skip the FBE operation. If the storage manager (333) finds that the specified file exists, it can skip the FBE operation that sets the memory to lock mode.

According to one embodiment, the device care (311) can access the memory when the platform reset is completed, because the memory is not set to lock mode. The device care (311) can transmit the setting information stored in the memory to the audio manager (335) and the telephony manager (339).

According to one embodiment, the audio manager (335) can restore the electronic device to a volume level prior to the platform reset based on the received setting information. The setting information received by the audio manager (335) may be volume information.

According to one embodiment, the audio manager (335) restores the volume level, and

According to one embodiment, the telephony manager (339) can restore the electronic device to the data connection state prior to the platform reset based on the received configuration information. The configuration information received by the telephony manager (339) may be data connection status information (e.g., information regarding whether mobile data is used) and/or output configuration information for a data allowance popup. The data connection status information may include configuration information regarding whether the data connection popup is displayed.

For example, the telephony manager (339) can switch the data connection popup to an on state if it is set to an on state before rebooting. The telephony manager (339) can restore the display state of the data connection popup to an on state when the reboot of the electronic device is completed. As another example, the telephony manager (339) can restore the display state of the data connection popup to an off state after rebooting if it is set to an off state before rebooting.

For example, if the data connection state of the electronic device before the platform reset is off, the telephony manager (339) can restore the data connection state of the electronic device to off after the platform reset. As another example, if the data connection state set before the platform reset is on, the telephony manager (339) can restore the data connection state of the electronic device to on after the platform reset.

According to one embodiment, when the reboot of the electronic device is completed, the telephony manager (339) can restore the display status of the data connection pop-up to the setting prior to the reboot, based on the data connection status information. For example, the telephony manager (339) can restore the display status of the data connection pop-up to the setting prior to the reboot of the electronic device, based on the data connection status information received from the device care (311). That is, the data connection status information may include not only information regarding the presence or absence of a data connection of the electronic device, but also information regarding the display status of the data connection pop-up.

According to another embodiment, the device care (311) can detect a state in which the available memory capacity becomes insufficient as processes accumulate in the memory. When the device care (311) detects the insufficient available memory capacity, it may output a message requesting the user to select a reboot time via a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2). For example, the message may be a user interface including “Start Now” to start the reboot now and “Start Later” to start the reboot at a time set by the user.

According to one embodiment, when the device care (311) receives user input of “Start now,” it may start rebooting the electronic device.

According to one embodiment, when the device care (311) receives user input for “start later,” it may output a timer in a portion of the message. The device care (311) may receive time information (time to start rebooting) from the user through the timer. The device care (311) may transmit the received time information to the alarm manager (313).

According to one embodiment, the alarm manager (313) may store the received time information. When the time corresponding to the stored time information arrives, the alarm manager (313) may transmit a signal to the device care (311) requesting the start of the reboot.

According to one embodiment, when the device care (311) receives a signal requesting the start of the reboot, it can determine whether the electronic device is currently being used by a user. For example, the device care (311) can determine whether the electronic device is currently being used by a user by checking whether at least one of the display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2) included in the electronic device, the speaker (e.g., the sound output module (155) of FIG. 1), the microphone (e.g., the input module (150) of FIG. 1), and the sensor (e.g., the sensor module (176) of FIG. 1) is operating.

In another example, the device care (311) can determine whether the electronic device is being used when the electronic device is connected to an external electronic device (e.g., a wearable electronic device) through a communication module and is being controlled by the external electronic device.

According to one embodiment, the device care (311) may request the power manager (331) to reboot the electronic device when the electronic device is not being used by the user.

According to one embodiment, when the power manager (331) receives a reboot request signal from the device care (311), it can check the reboot value stored in the device care (311). If the checked reboot value is a specified value, the power manager (331) can perform a platform reset on the electronic device. That is, the electronic device can automatically perform a platform reset when the time corresponding to the stored time information arrives.

FIG. 4 is a flowchart illustrating a method for rebooting according to an embodiment of the present invention.

Looking at operation 401 of FIG. 4, the processor of the electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) (e.g., the processor (120) of FIG. 1 or the processor (205) of FIG. 2) can check the status of the memory (e.g., the memory (130) of FIG. 1 or the memory (203) of FIG. 2) (e.g., the device care (311) of FIG. 3 checks).

According to one embodiment, the processor can check the available capacity of the memory.

Looking at operation 403, the processor can detect a shortage of memory based on the availability of the confirmed memory (e.g., the device care (311) of FIG. 3 detects it).

For example, the processor may detect that the usage of the memory is greater than or equal to a specified setting value. The specified setting value may be a threshold value for rebooting. As another example, the processor may check for a memory shortage by checking the number of memory leaks (FDs) or file descriptors (FDRs) due to the memory shortage, the number of process kills due to the memory shortage, and/or the number of application refreshes due to the memory shortage. As a specific example, the processor may check the number of process forced terminations due to the memory shortage. The processor may check the number of process terminations due to the memory shortage at specified intervals (e.g., 60 process executions or specified time intervals), and if the number checked is greater than or equal to the specified setting value (e.g., a number corresponding to a 30% ratio), it may determine this as a memory shortage.

According to one embodiment, if the processor does not detect the available memory shortage state, it can check the state of the memory. If the processor does not detect the memory shortage state, it can check the state of the memory periodically or at specified intervals.

Looking at operation 405, the processor can register a reboot alarm (e.g., through the alarm manager (313) of FIG. 3).

According to one embodiment, when the processor (e.g., Device Care (311)) detects the available memory shortage, it can generate reboot time information and register a reboot alarm. For example, the Device Care (311) can generate reboot time information by using a pre-specified time information (e.g., 3:00 AM) or by generating a random time (e.g., 3:17:23) within a set time interval (e.g., between 1:00 AM and 4:00 AM). The processor (e.g., Device Care (311)) can register a reboot alarm using the reboot time information. For example, the Device Care (311) can register an alarm by transmitting the reboot time information to the Alarm Manager (313). When the reboot time arrives, the Alarm Manager (313) can notify the Device Care (311) that the reboot time has arrived.

According to various other embodiments, when the processor detects the available memory shortage, it may output a message requesting the selection of a reboot start time. When the processor receives user input in response to the message, it may generate time information based on the received user input. The processor may store the generated time information (e.g., through the alarm manager (313) of FIG. 3) to register a reboot alarm, which is the scheduled time to reboot the electronic device (200).

The above reboot alarm may be time information generated by the processor based on user input received from a user to register the reboot alarm. For example, the processor may generate time information such as 04:20 to reboot the electronic device based on the user input. For example, the device care (311) may transmit the generated reboot time information to the alarm manager (313) to register the alarm. When the reboot time arrives, the alarm manager (313) may notify the device care (311) that the reboot time has arrived.

The above processor stores the generated time information and can reboot the electronic device when the time corresponding to the time information arrives.

Looking at operation 407, the processor can determine whether the electronic device is in use.

According to one embodiment, when the time of the registered reboot alarm arrives (e.g., the time is checked via the alarm manager (313) of FIG. 3), the processor can determine whether the electronic device is currently being used by a user (e.g., determined via the device k (311) of FIG. 3).

For example, when the processor reaches a time corresponding to the reboot alarm time (time information) (e.g., recognized through the alarm manager (3131) of FIG. 3), it can determine whether at least one of the display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2)), the speaker (e.g., the sound output module (155) of FIG. 1), the microphone (e.g., the input module (150) of FIG. 1), and the sensor (e.g., the sensor module (176) of FIG. 1) included in the electronic device is operating, and determine whether the electronic device is currently being used by a user (e.g., determined through the device care (311) of FIG. 3).

As another example, the processor can determine whether the electronic device is being used when the electronic device is connected to an external electronic device (e.g., a wearable electronic device) through a communication module and is being controlled by the external electronic device.

According to one embodiment, the processor can periodically determine whether the electronic device is being used by a user when the electronic device is not being used by a user.

Looking at operation 409, the processor can automatically reboot (e.g., reboot via the power manager (331) of FIG. 3).

According to one embodiment, the processor can check the reboot value stored in the electronic device when the current start is the registered reboot alarm time and the electronic device is not currently being used by a user. If the reboot value is a specified value, the processor can automatically reboot the electronic device (e.g., reboot via the Power Manager (331) of FIG. 3) without receiving separate user input. For example, Device Care (311) can request a platform reset (cf. silent reboot) to the Power Manager (331). A platform reset may be an operation that reboots only the framework operating system while maintaining the kernel operating system among the entire operating system (including the kernel and framework).

According to one embodiment, the processor may store volume information and data connection status information of the electronic device (e.g., stored by Device Care (311) of FIG. 3) before automatically rebooting (platform reset). The volume information and data connection status information may be included in the setting information. Additionally, before automatically rebooting the electronic device, the processor may switch system sounds, vibrations, and notification sounds to silent mode (e.g., switched via Audio Manager (335) of FIG. 3) and switch the output of the data allow popup to off (e.g., switched via Telephony Manager (339) of FIG. 3). The processor may switch the start sound output when the electronic device starts to off (e.g., switched via Logo Animation Manager (337) of FIG. 3).

According to one embodiment, the processor (e.g., Device Care (311) of FIG. 3) may create a specified file in a protected area (e.g., an EFS area (encrypting file system zone)) and set a reboot value to a specified value before automatically rebooting the electronic device. A detailed description regarding the specified file and the reboot value is disclosed in FIG. 3.

According to one embodiment, the processor can platform reset the electronic device when the reboot value is a specified value.

According to one embodiment, when the platform reset is completed, the processor can check whether a file designated in the protection area exists. If the designated file exists, the processor can skip the file-based encryption (FBE) operation of setting the memory to lock mode.

According to one embodiment, the processor can access configuration information stored in the memory by skipping the FBE operation. Based on the configuration information, the processor can restore the configuration of the electronic device (e.g., volume settings, data connection settings) to the settings prior to rebooting. For example, if the volume level of the volume information included in the configuration information is "5", the processor can restore the volume level of the electronic device to "5" after rebooting. Additionally, if the connection level of the data connection status information included in the configuration information is "on", the processor can restore the connection level of the electronic device to "on" after rebooting.

According to various embodiments, a method of operating an electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) may include an operation of checking the state of a memory (e.g., the memory (130) of FIG. 1 or the memory (205) of FIG. 2), an operation of registering a reboot alarm when the memory is insufficient based on the result of the check, an operation of checking whether the electronic device is in use when the time corresponding to the reboot alarm arrives, and an operation of rebooting the electronic device when it is not in use.

According to various embodiments, the operation of rebooting may further include the operation of saving the configuration information of the electronic device before rebooting.

According to various embodiments, the setting information may include volume information and data connection status information prior to the electronic device being rebooted.

According to various embodiments, the operation of rebooting may further include the operation of restoring the settings of the electronic device based on the stored setting information after a specified time has elapsed following the completion of the reboot.

According to various embodiments, the operation of rebooting may further include switching the output of the data connection pop-up of the electronic device to an off state before the electronic device is rebooted, and switching the output of the data connection pop-up to a state prior to rebooting when the specified time has elapsed.

According to various embodiments, the specified time may be set as the time after the electronic device is rebooted and all notification sounds have occurred.

According to various embodiments, the operation of rebooting may further include the operation of switching the electronic device to silent mode before the electronic device is rebooted.

According to various embodiments, the electronic device includes a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2), and the rebooting operation may further include the operation of automatically rebooting by setting the display to an off state.

According to various embodiments, the rebooting operation may include skipping the file-based encryption (FBE) operation and executing the reboot.

FIG. 5 is a flowchart illustrating operations performed to reboot according to an embodiment of the present invention.

According to one embodiment, device care (501) (e.g., device care (311) of FIG. 3) can detect (501a) a state in which the available capacity of memory becomes insufficient (insufficient available memory state) as a process accumulates in memory (e.g., memory (130) of FIG. 1). For example, the insufficient available memory state can be detected when the usage of the memory exceeds a specified set value. The operation of detecting the insufficient available memory state is disclosed in detail in the 401 operation of FIG. 4.

According to one embodiment, when the device care (501) detects the available memory shortage state (501a), it can check (501b) volume information stored in the audio manager (503) (e.g., audio manager (335) of FIG. 3). Additionally, the device care (501) can check (501c) data connection status information stored in the telephony manager (505) (e.g., telephony manager (339) of FIG. 3).

According to one embodiment, the device care (501) can store the verified volume information and data connection status information as setting information (501d). For example, the device care (501) can verify that the volume level of the verified volume information is set to “5” and store the verified volume level as volume information. Additionally, the device care (501) can verify that the connection level of the verified data connection status information is set to “off” and store the verified connection level as data connection status information.

According to one embodiment, the device care (501) may store volume information and data connection status information (501d) and then request the audio manager (503) to switch system sounds, vibrations, and notification sounds to silent mode (501e). Additionally, the device care (501) may request the telephony manager (505) to switch the output of the data allow popup to off (e.g., popup disabled) (501f). For example, the electronic device may output (display) the 'data allow popup' (e.g., “Would you like to connect mobile data?”) on the display upon booting. For example, the user may turn off (disable) the output of the data allow popup by selecting the 'Don't ask again' option within the popup, but otherwise, the popup will be displayed every time the device boots.

Additionally, the device care (501) may request (501g) the logo animation manager (507) (e.g., the logo animation manager (337) of FIG. 3) to switch the start sound output upon reboot to an off state.

According to one embodiment, when the audio manager (503) receives the request (501e) from the device care (501), it can switch the system sound, vibration and notification sound to silent mode (503a).

According to one embodiment, when the telephony manager (505) receives the request (501f) from the device care (501), it may switch the data allow pop-up to an off state (505a).

According to one embodiment, when the logo animation manager (507) receives the request (501g) from the device care (501), it may switch (507a) so that the start sound output at boot time is not output through the speaker.

According to one embodiment, the device care (501) may create a specified file in a protected area (e.g., an EFS area (encrypting file system zone)) when the switching operations (503a, 505a, 507a) are completed. Additionally, the device care (501) may set a reboot value to a specified value. The reboot value may be a code value for determining whether to perform a full reset or a platform reset of the electronic device. The specified file may be a file required to skip the file-based encryption (FBE) operation that sets the memory to a lock mode after the electronic device is platform reset.

According to one embodiment, a power manager (509) (e.g., a power manager (331) of FIG. 3) can check (509a) a reboot value stored in the device care (501). If the reboot value is a specified value, the power manager (509) can perform a platform reset (509b).

According to another embodiment, the memory may further include an alarm manager (not shown) (e.g., the alarm manager (313) of FIG. 3). When the device care (501) detects the available memory shortage state (501a), it may output a message requesting the selection of a reboot start time through a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2). The device care (501) may receive user input regarding the message and, based on the received user input, determine the reboot start time.

According to another embodiment, the device care (501) may transmit (not shown) time information related to the confirmed reboot start time to the alarm manager (313). When the time corresponding to the time information arrives, the alarm manager (313) may transmit a reboot start signal to the device care (501). When the device care (501) receives the reboot start signal, it may start rebooting the electronic device.

According to another embodiment, the device care (501) can determine whether the electronic device is being used by a user when it receives the reboot start signal from the alarm manager (313). If the electronic device is being used by a user, the device care (501) can obtain reboot start time information from the user by outputting a message requesting the user to select a reboot start time through the display.

FIG. 6 is a flowchart illustrating other operations performed to reboot according to one embodiment of the present invention.

According to one embodiment, when a reboot of an electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) is completed, the device care (501) (e.g., the device care (311) of FIG. 3) and the storage manager (607) (e.g., the storage manager (333) of FIG. 3) may detect (601a) that the reboot of the electronic device is completed. The reboot may be a platform reset that reboots the remaining components (e.g., applications and application frameworks) excluding the kernel of the electronic device.

According to one embodiment, when the storage manager (607) detects (601b) that the reboot is complete, it can check whether a specified file exists in a protected area (e.g., an EFS area (encrypting file system zone)). If the storage manager (607) finds that the specified file exists in the protected area, it can skip (607a) the file-based encryption (FBE) operation. The specified file may be a file required to skip the FBE operation that sets the memory (e.g., memory (130) in FIG. 1 or memory (203) in FIG. 2) to lock mode.

According to one embodiment, the device care (601) may transmit (601c) stored volume information to the audio manager (603) (e.g., the audio manager (335) of FIG. 3) when the FBE operation is skipped by the storage manager (607). The volume information may be information related to the volume level set in the electronic device before the platform reset.

According to one embodiment, the audio manager (603) can restore the volume level (603a) based on volume information received from the device care (601). For example, if the volume level of the received volume information is “10,” the audio manager (603) can restore the volume level of the electronic device to “10.” The volume information and the data connection status information may be included in the setting information.

According to one embodiment, the device care (601) may transmit (601d) stored data connection status information to the telephony manager (605) (e.g., the telephony manager (339) of FIG. 3) when the FBE operation is skipped by the storage manager (607). The data connection status information may be information related to whether a data connection is set on the electronic device before the platform reset.

According to one embodiment, the telephony manager (605) can restore a data connection (605a) based on data connection status information received from the device care (601). For example, the telephony manager (605) can establish data communication between the electronic device and the wireless network if the connection level of the received data connection status information is in an “on” state. As another example, if the connection level of the data connection status information received by the telephony manager (605) is in an “off” state, data communication between the electronic device and the wireless network may not be established.

FIG. 7 is a flowchart illustrating another method of rebooting according to one embodiment of the present invention.

Looking at operation 701 of FIG. 7, the processor of the electronic device (e.g., the electronic device (101) of FIG. 1 or the electronic device (200) of FIG. 2) (e.g., the processor (120) of FIG. 1 or the processor (205) of FIG. 2) can check the status of the memory (e.g., the memory (130) of FIG. 1 or the memory (203) of FIG. 2) (e.g., the device care (311) of FIG. 3 checks).

According to one embodiment, the processor can check the available capacity of the memory.

Looking at operation 703, the processor can detect a state of insufficient available memory (insufficient available memory state) based on the available memory capacity identified above.

For example, the processor may detect that the usage of the memory exceeds a specified setting value. The specified setting value may be a threshold value at which a process accumulates in the memory and a message related to a reboot (e.g., a message requesting the selection of a reboot time) may be generated. For example, the processor may detect that the usage of the memory exceeds a specified setting value. The specified setting value may be a threshold value at which a reboot can be performed. As another example, the processor may check for a memory shortage by verifying the number of memory leaks (FDs) or file descriptors (FDRs) due to the memory shortage, the number of process kills due to the memory shortage, and/or the number of application refreshes due to the memory shortage. As a specific example, the processor may check the number of process forced terminations due to the memory shortage. The processor may check the number of times a process is terminated due to insufficient memory capacity at a specified period (e.g., 50 process executions or a specified time interval), and if the number of times checked is greater than or equal to a specified setting value (e.g., a number corresponding to a ratio of 25%), it may determine that there is insufficient available memory.

Looking at operation 705, the processor may output a message requesting a reboot point to be selected.

According to one embodiment, when the processor detects the available memory shortage, it may output a message requesting the user to select a reboot time through a display (e.g., the display module (160) of FIG. 1 or the display (201) of FIG. 2).

Looking at operation 707, the processor can receive user input for the message.

According to one embodiment, the processor may receive user input selecting the reboot time. For example, the processor may receive user input to start the reboot immediately. As another example, the processor may receive user input setting the reboot start time.

Looking at operation 709, the processor may initiate a reboot (e.g., via the power manager (331) of FIG. 3). According to one embodiment, if the received user input is an input that initiates a reboot immediately, the processor may store volume information and data connection status information of the electronic device before initiating the reboot. Additionally, before initiating the reboot, the processor may switch the electronic device to silent mode (e.g., via the audio manager (335) of FIG. 3) and switch the output of the data allow popup to off (e.g., via the telephony manager (339) of FIG. 3). The processor may switch the start sound output when the electronic device starts to off (e.g., via the logo animation manager (337) of FIG. 3).

According to another embodiment, if the processor does not receive user input for the message for a certain period of time, it may immediately start the reboot.

According to one embodiment, the processor may create a file specified in the protection area and set the reboot value to a specified value before initiating a reboot.

According to one embodiment, if the processor identifies that the reboot value is a specified value, it can platform reset the electronic device. When the processor completes the platform reset, it can check whether a file specified in the protection area exists. If the processor finds that the file specified exists, it can skip the file-based encryption (FBE) operation that sets the memory to lock mode.

According to one embodiment, the processor can access configuration information stored in the memory by skipping the FBE operation. Based on the configuration information, the processor can restore the configuration of the electronic device (e.g., volume configuration, data connection configuration) to the configuration prior to the reboot.

Looking at operation 711, the processor can set a reboot alarm time. When the processor receives user input to schedule a reboot start time associated with operation 707, it can register information related to the set reboot schedule time (reboot start time information) (e.g., registered via the alarm manager (313) of FIG. 3).

Looking at operation 713, the processor can automatically start rebooting at the set time.

According to one embodiment, the processor can reboot the electronic device when the time corresponding to the stored reboot start time information arrives.

According to another embodiment, the processor may determine whether the electronic device is being used by a user when the time corresponding to the reboot start time information arrives. If the electronic device is not currently being used by a user, the processor may reboot the electronic device. On the other hand, if the electronic device is currently being used by a user, the processor may output a message requesting the user to select a reboot start time through the display.

According to one embodiment, the processor may store volume information and data connection status information of the electronic device when the time corresponding to the reboot start time information arrives. Additionally, before initiating a reboot (platform reset), the processor may switch the electronic device to silent mode and switch the output of the data allow popup to an off state.

According to one embodiment, the processor may create a file specified in a protected area and set a reboot value to a specified value before automatically rebooting. If the reboot value is the specified value, the processor may reboot the electronic device (platform reset).

According to one embodiment, when the processor completes the platform reset, it can check whether a file designated in the protection area exists. If the processor finds that the designated file exists, it can skip the file-based encryption (FBE) operation of setting the memory to lock mode.

According to one embodiment, the processor can skip the FBE operation and restore the settings of the electronic device (e.g., volume settings, data connection settings) to the settings prior to rebooting based on the setting information stored in the memory.

The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

The term “module” as used in the various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, ‘non-temporary’ simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

According to one embodiment, the method according to the various embodiments disclosed herein may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims (20)

In electronic devices,
Memory; and
Includes a processor,
The above processor is,
Check the status of the above memory, and
When detecting a memory shortage based on the above verification result,
Register a reboot alarm,
A reboot value is set to a specified value, wherein the specified value is a value representing the second reset method among a first reset method that executes a reboot of the first components including a lock setting for the memory and a kernel configuration, and a second reset method that executes a reboot of the second components excluding the kernel configuration among the first components without a lock on the memory.
When the time corresponding to the above reboot alarm arrives, check whether the above electronic device is in use, and
When the above electronic device is not in use,
Before rebooting the electronic device, at least one of the vibration function, audio function, and data connection function of the electronic device is set to an off state, and
An electronic device that performs a reboot of the second components without locking the memory based on the above-specified value. In paragraph 1,
The above processor is,
An electronic device that stores setting information of the electronic device before rebooting the electronic device. In paragraph 2,
The above processor is,
An electronic device that restores the settings of the electronic device based on the stored setting information when a specified time has elapsed after the reboot of the electronic device is completed. In paragraph 2,
The above setting information is,
An electronic device comprising volume information and data connection status information prior to the electronic device being rebooted. In paragraph 3,
The above processor is,
Before rebooting the electronic device, the data connection function is switched to an off state so that the output of the data connection popup of the electronic device is turned off, and
An electronic device that restores the output of the data connection popup to the state prior to reboot when the above-mentioned specified time has elapsed. In paragraph 3,
The above-mentioned time is,
An electronic device designated as a time after all at least one notification sound occurring as a result of the reboot of the electronic device is executed. In paragraph 1,
The above processor is,
Before rebooting the electronic device, the vibration function and the audio function are switched to an off state so that silent mode is set, and
An electronic device that disables the silent mode when the above-specified time has elapsed. In paragraph 1,
The above electronic device further includes a display,
The above processor is,
An electronic device that automatically reboots by setting the above display to the off state. In electronic devices,
display;
Memory; and
Includes a processor,
The above processor is,
Check the status of the above memory, and
When detecting a memory shortage based on the above verification result,
Output a message requesting the selection of a reboot point of the electronic device through the above display, and
Based on user input regarding the above message, register a reboot alarm, and
A reboot value is set to a specified value, wherein the specified value is a value representing the second reset method among a first reset method that executes a reboot of the first components including a lock setting for the memory and a kernel configuration, and a second reset method that executes a reboot of the second components excluding the kernel configuration among the first components without a lock on the memory.
When the time corresponding to the above reboot alarm arrives, check whether the above electronic device is in use, and
When the above electronic device is not in use,
Before rebooting the electronic device, at least one of the vibration function, audio function, and data connection function of the electronic device is set to an off state, and
An electronic device that performs a reboot of the second components without locking the memory based on the above-specified value. In the method of operating an electronic device,
Operation to check the state of memory;
When detecting a memory shortage based on the above verification result:
Action to register a reboot alarm;
An operation in which a reboot value is set to a specified value, wherein the specified value is a value representing the second reset method among a first reset method that executes a reboot of the first components including a lock setting for the memory and a kernel configuration, and a second reset method that executes a reboot of the second components excluding the kernel configuration among the first components without a lock on the memory;
An operation to check whether the electronic device is in use when the time corresponding to the above reboot alarm arrives;
When the above electronic device is not in use,
Before rebooting the electronic device, the operation of setting at least one of the vibration function, audio function, and data connection function of the electronic device to an off state; and
A method comprising the operation of rebooting the second components without locking the memory based on the specified value. delete delete delete delete delete delete delete delete delete delete