Patent ID: 12229427

The same reference numerals are used to represent the same elements throughout the drawings.

MODE FOR INVENTION

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the claims and their equivalents. It includes various specific details to assist in that understanding but these are to be regarded as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to the bibliographical meanings, but, are merely used by the inventor to enable a clear and consistent understanding of the disclosure. Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the disclosure is provided for illustration purpose only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to “a component surface” includes reference to one or more of such surfaces.

FIG.1is a block diagram illustrating an electronic device101in a network environment100according to an embodiment of the disclosure.

Referring toFIG.1, the electronic device101in the network environment100may communicate with an electronic device102via a first network198(e.g., a short-range wireless communication network), or at least one of an electronic device104or a server108via a second network199(e.g., a long-range wireless communication network). According to an embodiment, the electronic device101may communicate with the electronic device104via the server108. According to an embodiment, the electronic device101may include a processor120, memory130, an input module150, a sound output module155, a display module160, an audio module170, a sensor module176, an interface177, a connecting terminal178, a haptic module179, a camera module180, a power management module188, a battery189, a communication module190, a subscriber identification module (SIM)196, or an antenna module197. In some embodiments, at least one of the components (e.g., the connecting terminal178) may be omitted from the electronic device101, or one or more other components may be added in the electronic device101. In some embodiments, some of the components (e.g., the sensor module176, the camera module180, or the antenna module197) may be implemented as a single component (e.g., the display module160).

The processor120may execute, for example, software (e.g., a program140) to control at least one other component (e.g., a hardware or software component) of the electronic device101coupled with the processor120, and may perform various data processing or computation. According to one embodiment, as at least part of the data processing or computation, the processor120may store a command or data received from another component (e.g., the sensor module176or the communication module190) in volatile memory132, process the command or the data stored in the volatile memory132, and store resulting data in non-volatile memory134. According to an embodiment, the processor120may include a main processor121(e.g., a central processing unit (CPU) or an application processor (AP)), or an auxiliary processor123(e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operable independently from, or in conjunction with, the main processor121. For example, when the electronic device101includes the main processor121and the auxiliary processor123, the auxiliary processor123may be adapted to consume less power than the main processor121, or to be specific to a specified function. The auxiliary processor123may be implemented as separate from, or as part of the main processor121.

The auxiliary processor123may control at least some of functions or states related to at least one component (e.g., the display module160, the sensor module176, or the communication module190) among the components of the electronic device101, instead of the main processor121while the main processor121is in an inactive (e.g., sleep) state, or together with the main processor121while the main processor121is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor123(e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module180or the communication module190) functionally related to the auxiliary processor123. According to an embodiment, the auxiliary processor123(e.g., the neural processing unit) may include a hardware structure specified for artificial intelligence model processing. An artificial intelligence model may be generated by machine learning. Such learning may be performed, e.g., by the electronic device101where the artificial intelligence is performed or via a separate server (e.g., the server108). Learning algorithms may include, but are not limited to, e.g., supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. 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-network or a combination of two or more thereof but is not limited thereto. The artificial intelligence model may, additionally or alternatively, include a software structure other than the hardware structure.

The memory130may store various data used by at least one component (e.g., the processor120or the sensor module176) of the electronic device101. The various data may include, for example, software (e.g., the program140) and input data or output data for a command related thereto. The memory130may include the volatile memory132or the non-volatile memory134.

The program140may be stored in the memory130as software, and may include, for example, an operating system (OS)142, middleware144, or an application146.

The input module150may receive a command or data to be used by another component (e.g., the processor120) of the electronic device101, from the outside (e.g., a user) of the electronic device101. The input module150may 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 module155may output sound signals to the outside of the electronic device101. The sound output module155may include, for example, a speaker or a receiver. The speaker may be used for general purposes, such as playing multimedia or playing record. The receiver may be used for receiving incoming calls. According to an embodiment, the receiver may be implemented as separate from, or as part of the speaker.

The display module160may visually provide information to the outside (e.g., a user) of the electronic device101. The display module160may include, for example, a display, a hologram device, or a projector and control circuitry to control a corresponding one of the display, hologram device, and projector. According to an embodiment, the display module160may include a touch sensor adapted to detect a touch, or a pressure sensor adapted to measure the intensity of force incurred by the touch.

The audio module170may convert a sound into an electrical signal and vice versa. According to an embodiment, the audio module170may obtain the sound via the input module150, or output the sound via the sound output module155or a headphone of an external electronic device (e.g., an electronic device102) directly (e.g., wiredly) or wirelessly coupled with the electronic device101.

The sensor module176may detect an operational state (e.g., power or temperature) of the electronic device101or an environmental state (e.g., a state of a user) external to the electronic device101, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module176may include, for example, a gesture sensor, a gyro sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface177may support one or more specified protocols to be used for the electronic device101to be coupled with the external electronic device (e.g., the electronic device102) directly (e.g., wiredly) or wirelessly. According to an embodiment, the interface177may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

A connecting terminal178may include a connector via which the electronic device101may be physically connected with the external electronic device (e.g., the electronic device102). According to an embodiment, the connecting terminal178may include, for example, a HDMI connector, a USB connector, a SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module179may convert an electrical signal into a mechanical stimulus (e.g., a vibration or a movement) or electrical stimulus which may be recognized by a user via his tactile sensation or kinesthetic sensation. According to an embodiment, the haptic module179may include, for example, a motor, a piezoelectric element, or an electric stimulator.

The camera module180may capture a still image or moving images. According to an embodiment, the camera module180may include one or more lenses, image sensors, image signal processors, or flashes.

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

The battery189may supply power to at least one component of the electronic device101. According to an embodiment, the battery189may include, for example, a primary cell which is not rechargeable, a secondary cell which is rechargeable, or a fuel cell.

The communication module190may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device101and the external electronic device (e.g., the electronic device102, the electronic device104, or the server108) and performing communication via the established communication channel. The communication module190may include one or more communication processors that are operable independently from the processor120(e.g., the application processor (AP)) and supports a direct (e.g., wired) communication or a wireless communication. According to an embodiment, the communication module190may include a wireless communication module192(e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module194(e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules may communicate with the external electronic device via the first network198(e.g., a short-range communication network, such as Bluetooth™, wireless-fidelity (Wi-Fi) direct, or infrared data association (IrDA)) or the second network199(e.g., a long-range communication network, such as a legacy cellular network, a fifth generation (5G) network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or wide area network (WAN)). These various types of communication modules may be implemented as a single component (e.g., a single chip), or may be implemented as multi components (e.g., multi chips) separate from each other. The wireless communication module192may identify and authenticate the electronic device101in a communication network, such as the first network198or the second network199, using subscriber information (e.g., international mobile subscriber identity (IMSI)) stored in the subscriber identification module196.

The wireless communication module192may support a 5G network, after a fourth generation (4G) network, and next-generation communication technology, e.g., new radio (NR) access technology. The NR access technology may support enhanced mobile broadband (eMBB), massive machine type communications (mMTC), or ultra-reliable and low-latency communications (URLLC). The wireless communication module192may support a high-frequency band (e.g., the millimeter wave (mmWave) band) to achieve, e.g., a high data transmission rate. The wireless communication module192may support various technologies for securing performance on a high-frequency band, such as, e.g., beamforming, massive multiple-input and multiple-output (massive MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module192may support various requirements specified in the electronic device101, an external electronic device (e.g., the electronic device104), or a network system (e.g., the second network199). According to an embodiment, the wireless communication module192may support a peak data rate (e.g., 20 Gbps or more) for implementing eMBB, loss coverage (e.g., 164 dB or less) for implementing mMTC, or U-plane latency (e.g., 0.5 ms or less for each of downlink (DL) and uplink (UL), or a round trip of 1 ms or less) for implementing URLLC.

The antenna module197may transmit or receive a signal or power to or from the outside (e.g., the external electronic device) of the electronic device101. According to an embodiment, the antenna module197may include an antenna including a radiating element composed of a conductive material or a conductive pattern formed in or on a substrate (e.g., a printed circuit board (PCB)). According to an embodiment, the antenna module197may include a plurality of antennas (e.g., array antennas). In such a case, at least one antenna appropriate for a communication scheme used in the communication network, such as the first network198or the second network199, may be selected, for example, by the communication module190(e.g., the wireless communication module192) from the plurality of antennas. The signal or the power may then be transmitted or received between the communication module190and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as part of the antenna module197.

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

At least some of the above-described components may be coupled mutually and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)).

According to an embodiment, commands or data may be transmitted or received between the electronic device101and the external electronic device104via the server108coupled with the second network199. Each of the electronic devices102or104may be a device of a same type as, or a different type, from the electronic device101. According to an embodiment, all or some of operations to be executed at the electronic device101may be executed at one or more of the external electronic devices102,104, or108. For example, if the electronic device101should perform a function or a service automatically, or in response to a request from a user or another device, the electronic device101, instead of, or in addition to, executing the function or the service, may request the one or more external electronic devices to perform at least part of the function or the service. The one or more external electronic devices receiving the request may perform the at least part of the function or the service requested, or an additional function or an additional service related to the request, and transfer an outcome of the performing to the electronic device101. The electronic device101may provide the outcome, with or without further processing of the outcome, as at least part of a reply to the request. To that end, a cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device101may provide ultra low-latency services using, e.g., distributed computing or mobile edge computing. In another embodiment, the external electronic device104may include an internet-of-things (IoT) device. The server108may be an intelligent server using machine learning and/or a neural network. According to an embodiment, the external electronic device104or the server108may be included in the second network199. The electronic device101may be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology or IoT-related technology.

FIG.2is a block diagram from a physical point of view and a logical point of view of a storage space according to an embodiment of the disclosure.

Referring toFIG.2, a storage device according to various embodiments may include a non-volatile memory (e.g., the non-volatile memory134ofFIG.1). For example, the storage device (e.g., the memory130ofFIG.1) may be a not-and (NAND) flash memory or a storage device (e.g., SSD, universal flash storage (UFS), or embedded multimedia card (eMMC)) based on a NAND flash memory.

According to various embodiments, the storage device may include a device partition210corresponding to a physical partition. The device partition210may include a first partition211, a second partition212, and/or a free space segment213which are divided based on a physical address corresponding to a physical location of the memory130.

According to an embodiment, the first partition211may be a system partition in which an executable file for driving an electronic device (e.g., the electronic device101ofFIG.1) is stored. For example, the first partition211may store system data (e.g., operating system (OS) data).

According to an embodiment, the free space segment213may be a temporary space (free-space reserve) for storing a file having an increased capacity in response to an executable file being updated according to a software update (e.g., firmware over-the-air (FOTA)) of the electronic device. For example, the free space segment213may be a temporary space for supplementing the storage space of system data such as the executable file.

According to an embodiment, the second partition212may be a user data partition in which user data is stored. For example, the second partition212may store user data (e.g., contacts, photos, music, or applications).

According to various embodiments, the storage device may include at least one file system. The file system may manage the spaces of the first partition211, the second partition212, and/or the free space segment213of the storage device. For example, the electronic device may load a first file system (e.g., a first file system410ofFIG.4A) into the first partition211of the storage device and a second file system (e.g., a second file system420ofFIG.4A) into the second partition212of the storage device. The file system may perform management of or access to files or data of the partitions, allocation of the storage space, and/or data integrity verification.

According to various embodiments, a volume manager250may configure a volume220based on a virtual address mapped to a physical address corresponding to a physical location of the memory130. For example, the volume manager250may configure the volume220corresponding to the first partition211, the second partition212, and/or the free space segment213of the device partition210, and may dynamically manage the volume220.

According to an embodiment, the volume220may include a first extent221and/or a second extent222. For example, the first extent221may correspond to the second partition212, and the second extent222may correspond to the free space segment213. For example, the volume manager250may configure the second partition212as the first extent221and the free space segment213as the second extent222. According to various embodiments, the volume manager250may be included in a file system. According to an embodiment, the volume manager250may be a component included in the second file system420.

According to various embodiments, unlike shown inFIG.2, the volume manager250may be constituted of a plurality of modules.

According to various embodiments, unlike shown inFIG.2, the volume manager250may generate a plurality of volumes220. Each of the plurality of volumes220may mount a file system (e.g., the file system420ofFIG.4A). The volume manager250according to various embodiments is a software module, and the operation of the volume manager (e.g., the volume manager250ofFIG.2) described throughout the disclosure may be performed by a processor (e.g., the processor120ofFIG.1).

FIG.3is a flowchart illustrating a method for managing a volume according to an embodiment of the disclosure.

Although the operation of the volume manager (e.g., the volume manager250ofFIG.2) is described inFIG.3, the volume manager250is a software module, and each operation of the volume manager250may be performed by a processor (e.g., the processor ofFIG.1).

Referring toFIG.3, the volume manager (e.g., the volume manager250ofFIG.2) according to an embodiment may configure a second partition (e.g., the second partition212ofFIG.2) as a first extent (e.g., the first extent221ofFIG.2) and configure a free space segment (e.g., the free space segment213ofFIG.2) as a second extent (e.g., the second extent222ofFIG.2) to load a second file system (e.g., the second file system420ofFIG.4A).

According to various embodiments, in operation310, the volume manager250may confirm a system software update request.

According to an embodiment, the volume manager250may confirm the system software update request. According to the system software update, the file capacity related to the system software stored in a first partition (e.g., the first partition211inFIG.2) may increase, and the first partition211may require an additional storage space.

According to various embodiments, in operation320, the volume manager250may move at least some of data blocks of the second extent222to the first extent221.

According to an embodiment, the volume manager250may move at least some of file data blocks stored in the second extent222to the first extent221before performing the system software update. According to an embodiment, the volume manager250may guide a user to backup and delete at least a portion of user data in order to secure a free space in the second partition212corresponding to the first extent221.

According to various embodiments, the volume manager250may detach the second extent222to which the at least some of the file data blocks are moved, from the second file system420. For example, the volume manager250may remove the second extent222corresponding to the free space segment213from a management area of the second file system420, and may perform a file system resizing operation (fs-resize) for reducing the size of the second file system420as the data block and/or capacity managed by the second file system420decreases. The second file system420may not access the second extent222. For example, the volume manager250may store information of the second file system420resized in metadata214corresponding to the second file system420.

According to various embodiments, in operation330, the volume manager250may update the system software and the first partition211.

According to various embodiments, in response to at least a portion of the data volume allocated to the second extent222being moved to the first extent221, the volume manager250may cause an electronic device (e.g., the electronic device101ofFIG.1or the processor120ofFIG.1) to perform a system software update operation. For example, the electronic device may acquire a new version of the system software file from a server and/or an external electronic device, and may store the acquired new version of the system software file in the first partition211.

According to various embodiments, the volume manager250may update the first partition211as the electronic device performs a system software update operation. For example, the volume manager250may perform a file system resizing operation (fs-resize) for increasing the size of the first file system410managing the first partition211in response to an increase in the capacity of the system software file stored in the first partition211. For example, the volume manager250may perform file system resizing so that the first file system410manages free blocks of the free space segment213corresponding to the increased capacity of the system software file. For example, the volume manager250may store the resized information of the first file system410in the metadata214corresponding to the first file system410.

According to various embodiments, the volume manager250may reduce the area of the free space segment213. For example, the volume manager250may reconfigure the area of the free space segment213to correspond to free blocks of the free space segment213remaining after being used for system software update in the first partition211. For example, the volume manager250may store information related to the start and end positions of the reduced area of the free space segment213in a designated position.

According to various embodiments, in operation340, the volume manager250may re-generate the second extent222.

According to various embodiments, the volume manager250may attach the area of the free space segment213remaining after the system software update to the second file system420. For example, the volume manager250may attach the free blocks of the free space segment213remaining after the system software update to the second file system420so that the second file system420manages the free blocks.

According to an embodiment, the volume manager250may generate the second extent222based on the information related to the start and end points of the area of the free space segment213corresponding to the free blocks of the free space segment213remaining after being used for system software update in the first partition211. For example, the volume manager250may load the generated second extent222into the second file system420and may resize (fs-resize) the second file system420. For example, the volume manager250may perform file system resizing so that the second file system420manages the remaining free blocks of the free space segment213.

FIGS.4A,4B, and4Care diagrams illustrating various embodiments corresponding to a method in which the volume manager250included in a file system manages a volume in response to a system software update according to various embodiments of the disclosure.

FIG.4Aillustrates an embodiment of an operation in which the volume manager250moves at least some of data blocks of the second extent222to the first extent221in response to a system software update according to an embodiment of the disclosure.

According to an embodiment,FIG.4Amay be the embodiment of operation320ofFIG.3.

According to various embodiments, the storage space shown inFIG.4Amay be in a state in which the free space segment213is maximally secured within a designated range.

According to various embodiments, the second file system420may include the volume manager250that manages the first extent221and/or the second extent222. The volume manager250may configure the second partition212as the first extent221and the free space segment213as the second extent222to load the second file system420.

According to various embodiments, in response to all data blocks of the first extent221being allocated when a file is stored, the electronic device may be allocated to data blocks of the second extent222and store the file.

According to various embodiments of the disclosure, in response to all data blocks of the first extent221being allocated when storing a file, the electronic device may store the file by being allocated to the data block of the second extent222.

According to various embodiments, the volume manager250may confirm a system software update request. According to the system software update, the file capacity related to the system software stored in the first partition211may increase, and the first partition211may require an additional storage space.

According to various embodiments, before performing the system software update, the volume manager250may move at least some of the file data blocks stored in the second extent222to the first extent221. According to an embodiment, the volume manager250may guide the user to backup and delete user data in order to secure a free space in the second partition212corresponding to the first extent221.

According to various embodiments, the volume manager250may detach the second extent222to which the at least some of the file data blocks are moved from the second file system420. For example, the volume manager250may remove the second extent222corresponding to the free space segment213from the management area of the second file system420, and may perform a file system resizing (fs-resize) operation on the second file system420along with a reduction in the data block and/or capacity managed by the second file system420. The second file system420may not access the second extent222. For example, the volume manager250may store the resized information of the second file system420in the metadata214corresponding to the second file system420.

FIG.4Bis a diagram illustrating an embodiment of an operation of the volume manager250updating system software and updating the first partition211according to an embodiment of the disclosure.

According to an embodiment,FIG.4Bmay be the embodiment of operation330ofFIG.3.

According to various embodiments, the volume manager250may cause the electronic device to perform a system software update operation in response to at least a portion of the data volume allocated to the second extent222being moved to the first extent221. For example, the electronic device may acquire a new version of the system software file from a server and/or an external electronic device, and may store the acquired new version of the system software file in the first partition211.

According to various embodiments, the volume manager250may update the first partition211as the electronic device performs the system software update operation. For example, the volume manager250may perform a file system resizing (fs-resize) operation for increasing the size of the first file system410managing the first partition211in response to an increase in the capacity of the system software file stored in the first partition211. For example, the volume manager250may perform file system resizing so that the first file system410manages free blocks (e.g., S4) of the free space segment213corresponding to the increased capacity of the system software file. For example, the volume manager250may store the resized information of the first file system410in the metadata214corresponding to the first file system410.

According to various embodiments, the volume manager250may reduce the area of the free space segment213. For example, the volume manager250may reconfigure the area of the free space segment213to correspond to free blocks S1, S2, and S3of the free space segment213remaining after being used for the system software update. For example, the volume manager250may store information related to the start and end positions of the reduced area of the free space segment213in a designated position.

FIG.4Cis a diagram illustrating an embodiment of an operation in which the volume manager250regenerates the second extent222according to an embodiment of the disclosure.

According to an embodiment,FIG.4Cmay be the embodiment of operation340ofFIG.3.

According to various embodiments, the volume manager250may attach the areas S1, S2, and S3of the free space segment213remaining after the system software update to the second file system420. For example, the volume manager250may attach the free blocks S1, S2, and S3of the free space segment213remaining after the system software update, to the second file system420so that the second file system420manages the free blocks S1, S2, and S3.

According to an embodiment, the volume manager250may generate the second extent222based on information related to the start and end positions of the area of the free space segment213corresponding to the free blocks S1, S2, and S3of the free space segment213remaining after being used for the system software update in the first partition211. For example, the volume manager250may load the generated second extent222into the second file system420and may resize (fs-resize) the second file system420. For example, the volume manager250may perform file system resizing so that the second file system420manages the remaining free blocks S1, S2, and S3of the free space segment213.

FIGS.5A,5B, and5Care diagrams illustrating various embodiments corresponding to a method in which a volume manager (e.g., the volume manager250ofFIG.2) separated from a file system manages a volume in response to a system software update according to various embodiments of the disclosure.

FIG.5Ais a diagram illustrating an embodiment of an operation in which the volume manager250moves at least some of data blocks of the second extent222to the first extent221to correspond to system software update according to an embodiment of the disclosure.

According to an embodiment,FIG.5Amay be the embodiment of operation320ofFIG.3.

According to various embodiments, a first logical partition510may be mapped to the first partition211of the device partition210, and a second logical partition520may be mapped to the first partition211of the device partition210. The first file system410may be loaded into the first logical partition510, and the second file system420may be loaded into the second logical partition520.

According to various embodiments, the volume manager250may be separated from the file system and may manage the first logical partition510and the second logical partition520based on logical partition information M.

According to various embodiments, the storage space shown inFIG.5Amay be in a state in which the free space segment213is maximally secured within a designated range. For example, the storage space shown inFIG.5Amay be in a state in which the volume manager250is using the free space segment213by attaching the free space segment213to the second logical partition520.

According to various embodiments, the volume manager250may confirm a system software update request. According to the system software update, the file capacity related to the system software stored in the first partition211may increase, and the first partition211may require an additional storage space.

According to various embodiments, before performing the system software update, the volume manager250may reduce the size of the second file system420loaded into the second logical partition520and may resize the second logical partition520by the reduced size of the second file system420. For example, before performing the system software update, the volume manager250may move at least some of file data blocks stored in the area of the second logical partition520corresponding to the free space segment213to the area of the second logical partition520corresponding to the second partition212. According to various embodiments, the volume manager250may remove an area corresponding to the free space segment213from a management area of the second file system420with respect to the second logical partition520to which the at least some of the file data blocks are moved, and may perform a file system resizing (fs-resize) operation for reducing the size of the second file system420along with a reduction in the data block and/or capacity managed by the second file system420. For example, the volume manager250may store information of the resized second file system420in the metadata214corresponding to the second file system420.

FIG.5Bis a diagram illustrating an embodiment of an operation in which the volume manager250updates system software and updates the first logical partition510according to an embodiment of the disclosure.

According to an embodiment,FIG.5Bmay be the embodiment of operation330ofFIG.3.

According to various embodiments, the volume manager250may reconfigure the first logical partition510in response to the size of the second logical partition520being adjusted. For example, the volume manager250may attach at least one S4of unused free blocks S1, S2, S3, and S4of the free space segment213to the area of the first logical partition510. For example, the volume manager250may perform a file system resizing (fs-resize) operation for increasing the size of the first file system410managing the first partition211in response to an increase in the capacity of the system software file stored in the first partition211. For example, the volume manager250may perform the file system resizing operation so that the first file system410manages the free block (e.g., S4) of the free space segment213corresponding to the increased system software file capacity. For example, the volume manager250may store information of the resized first file system410in the metadata214corresponding to the first file system410.

According to various embodiments, the volume manager250may perform system software update in the reconfigured first logical partition510. For example, the volume manager250may cause the electronic device to perform a system software update operation in response to the first logical partition510being resized. For example, the electronic device may acquire a new version of the system software file from a server and/or an external electronic device, and may store the acquired new version of the system software file in the first partition211and/or the free block S4corresponding to the first logical partition510.

FIG.5Cis a diagram illustrating an embodiment of an operation in which the volume manager250reconfigures the second logical partition520according to an embodiment of the disclosure.

According to an embodiment,FIG.5Cmay be the embodiment of operation340ofFIG.3.

According to various embodiments, the volume manager250may attach areas S1, S2and S3of the free space segment213remaining after a system software update to the second logical partition520. For example, the volume manager250may attach the free blocks S1, S2, and S3of the free space segment213remaining after the system software update to the second file system420so that the second file system420manages the free bocks S1, S2, and S3.

According to an embodiment, the volume manager250may increase the size of the second logical partition520and may also extend and use the size of the second file system420driven in the second logical partition520to correspond to the size of the second logical partition520. For example, the volume manager250may resize (fs-resize) the second file system420to correspond to the size of the second logical partition520. For example, the volume manager250may perform file system resizing so that the second file system420manages the remaining free blocks S1, S2, and S3of the free space segment213.

FIG.6is a diagram illustrating a method in which a volume manager manages a volume in response to a system software update according to an embodiment of the disclosure.

Although the operation of a volume manager (e.g., the volume manager250ofFIG.2) is described inFIG.6, the volume manager250is a software module, and each operation of the volume manager250may be performed by a processor (e.g., the processor120ofFIG.1).

According to various embodiments, in operation611, the volume manager250may begin loading of a second file system (e.g., the second file system420ofFIG.4A).

According to various embodiments, in operation612, the volume manager250may configure the second partition212as a first extent (e.g., the first extent221ofFIG.2) and may load the first extent into the second file system420.

According to various embodiments, in operation613, the volume manager250may load a free space segment (e.g., the free space segment213ofFIG.2) into the second file system420as a second extent (e.g., the second extent222ofFIG.2), and may resize the second file system420.

According to various embodiments, in operation614, the volume manager250may complete loading of the second file system420.

According to various embodiments, in operation615, the volume manager250may determine whether there is a system software update request.

According to an embodiment, the volume manager250may confirm the system software update request. According to the system software update, the file capacity related to system software stored in a first partition (e.g., the first partition211ofFIG.1) may increase, and the first partition211may require an additional storage space.

According to various embodiments, in operation621, the volume manager250may determine whether there is data allocated to the second extent222in response to the fact that there is the system software update request (e.g., operation615—YES).

According to various embodiments, in operation631, the volume manager250may determine whether the data of the second extent222is movable to the first extent221in response to the fact that there is the data allocated to the second extent (e.g., operation621—YES).

According to various embodiments, in operation633, the volume manager250may secure the space of the first extent221in response to the fact that the data of the second extent222is not movable to the first extent221(e.g., operation631—NO).

According to an embodiment, the volume manager250may guide the user to backup and delete user data in order to secure a free space of a second partition (e.g., the second partition212ofFIG.2) corresponding to the first extent221.

According to various embodiments, in operation632, the volume manager250may move the data of the second extent222to the first extent221in response to the fact that the data of the second extent222is movable to the first extent221(e.g., operation63—YES).

According to an embodiment, before performing a system software update, the volume manager250may move at least some of file data blocks stored in the second extent222to the first extent221.

According to various embodiments, in operation622, the volume manager250may detach the second extent222from the second file system420and may resize the second file system420in response to the fact that there is no data allocated to the second extent222(e.g., operation621—NO).

According to an embodiment, the volume manager250may detach the second extent222to which the at least some of the file data blocks are moved from the second file system420. For example, the volume manager250may remove the second extent222corresponding to the free space segment213from a management area of the second file system420, and may perform a file system resizing (fs-resize) operation for reducing the size of the second file system420along with a reduction in the data block and/or capacity managed by the second file system420. The second file system420may not access the second extent222. For example, the volume manager250may store information of the resized second file system420in the metadata214corresponding to the second file system420.

According to various embodiments, in operation623, the volume manager250may cause the electronic device to perform a system software update.

According to an embodiment, the electronic device may acquire a new version of the system software file from a server and/or an external electronic device, and may store the acquired new version of the system software file in the first partition211.

According to an embodiment, the volume manager250may update the first partition211as the electronic device performs a system software update operation. For example, the volume manager250may perform a file system resizing (fs-resize) operation for increasing the size of the first file system410managing the first partition211along with an increase in the capacity of the system software file stored in the first partition211. For example, the volume manager250may perform file system resizing so that the first file system410manages free blocks of the free space segment213corresponding to the increased capacity of the system software file. For example, the volume manager250may store information of the resized first file system410in the metadata214corresponding to the first file system410.

According to various embodiments, in operation624, the volume manager250may store information related to the start and end positions of the reduced area of the free space segment213in a designated position.

According to an embodiment, the volume manager250may reduce the area of the free space segment213. For example, the volume manager250may reconfigure the area of the free space segment213to correspond to the free blocks of the free space segment213remaining after being used for the system software update. For example, the volume manager250may store the information related to the start and end positions of the reduced area of the free space segment213in a designated position.

According to various embodiments, after operation624, the volume manager250may reperform operation612.

According to an embodiment, the volume manager250may attach the area of the free space segment213remaining after the system software update, to the second file system420. For example, the volume manager250may attach the free blocks of the free space segment213remaining after the system software update, to the second file system420so that the second file system420manages the free blocks.

According to an embodiment, the volume manager250may generate the second extent222based on the information related to the start and end positions of the area of the free space segment213corresponding to the free blocks of the free space segment213remaining after being used for the system software update in the first partition211. For example, the volume manager250may load the generated second extent222into the second file system420, and may resize (fs-resize) the second file system420. For example, the volume manager250may perform file system resizing so that the remaining free blocks of the free space segment213are managed by the second file system420.

An electronic device according to various embodiments may include a storage device configured to include a first partition, a second partition, and a third partition, and a processor configured to configure the second partition as a first volume and the third partition as a second volume, and may attach or detach the second volume to or from a file system to manage a storage space of the storage device.

In the electronic device according to various embodiments, the first partition may be a system partition in which an executable file for driving the electronic device is stored, the second partition may be a user data partition in which user data is stored, and the third partition may be a temporary space for supporting a storage space of the executable file for the system partition.

In the electronic device according to various embodiments, the processor may confirm a request for a system software update of the electronic device, may move data stored in the second volume to the first volume, may detach the second volume from the file system, and may store a file for the system software update in the third partition to perform the system software update.

In the electronic device according to various embodiments, the processor may resize the file system from which the second volume is detached, and may store information related to the resized file system in a metadata area of the file system.

In the electronic device according to various embodiments, before moving the data stored in the second volume to the first volume, the processor may guide a user to backup and delete the user data in order to secure a free space of the second partition corresponding to the first volume in response to a lack of a space to store the data stored in the second volume, in the first volume.

In the electronic device according to various embodiments, the processor may store information related to start and end positions of an area for a space remaining after the file for the system software update is stored in the third partition, may reconfigure the space remaining after the file for the system software update is stored in the third partition as the second volume based on the stored information, and may attach the reconfigured second volume to the file system.

In the electronic device according to various embodiments, when storing a file, the processor may store the file in data blocks of the second volume in response to all data blocks of the first volume being allocated.

An electronic device according to various embodiments may include a storage device configured to include a first partition, a second partition, and a third partition, and a processor configured to configure a first file system for managing the first partition, may configure a second file system by using the second partition as a first volume and the third partition as a second volume, and may manage a storage space of the storage device by attaching or detaching the second volume to or from the second file system.

In the electronic device according to various embodiments, the first partition may be a system partition in which a system file for driving the electronic device is stored, the second partition may be a user data partition in which user data is stored, and the third partition may be a temporary space for supporting a storage space of an executable file for the system partition.

In the electronic device according to various embodiments, the processor may confirm a request for a system software update of the electronic device, may move data stored in the second volume to the first volume, may detach the second volume from the second file system, and may store a file for the system software update in the third partition to perform the system software update.

In the electronic device according to various embodiments, the processor may resize the second file system from which the second volume is detached, and may store information related to the resized second file system in a metadata area of the second file system.

In the electronic device according to various embodiments, before moving the data stored in the second volume to the first volume, the processor may guide a user to backup and delete the user data to secure a free space of the second partition corresponding to the first volume in response to a lack of a space to store the data stored in the second volume, in the first volume.

In the electronic device according to various embodiments, the processor may extend the first file system by a space for storing the file for the system software update in the third partition.

In the electronic device according to various embodiments, the processor may store information related to start and end positions of an area for a space remaining after the file for the system software update is stored in the third partition, in a designated position, and may reconfigure the space remaining after the file for the system software update is stored in the third partition as the second volume and attach the reconfigured second volume to the second file system.

In the electronic device according to various embodiments, when storing a file, the processor may store the file in data blocks of the second volume in response to all data blocks of the first volume being allocated.

A method performed by an electronic device for managing a storage device including a first partition, a second partition, and a third partition, may include configuring a first file system for managing the first partition, configuring a second file system by using the second partition as a first volume and the third partition as a second volume, and attaching or detaching the second volume to or from the second file system.

In the method of operating the electronic device according to various embodiments, the first partition may be a system partition in which a system file for driving the electronic device is stored, the second partition may be a user data partition in which user data is stored, and the third partition may be a temporary space for supporting a storage space of an executable file for the system partition.

The method of operating the electronic device according to various embodiments may further include confirming a request for a system software update of the electronic device, moving data stored in the second volume to the first volume, detaching the second volume from the second file system, and storing a file for the system software update in the third partition to perform the system software update.

The method of operating the electronic device according to various embodiments may further include resizing the second file system from which the second volume is detached, and storing information related to the resized second file system in a metadata area of the second file system.

The method of operating the electronic device according to various embodiments may further include, before moving the data stored in the second volume to the first volume, guiding a user to backup and delete the user data to secure a free space of the second partition corresponding to the first volume in response to a lack of a space to store the data stored in the second volume, in the first volume.

The method of operating the electronic device according to various embodiments may further include extending the first file system by a space for storing the file for the system software update in the third partition.

The method of operating the electronic device according to various embodiments may further include storing information related to start and end positions of an area for a space remaining after the file for the system software update is stored in the third partition, in a designated position, and reconfiguring the space remaining after the file for the system software update is stored in the third partition as the second volume and attaching the reconfigured second volume to the second file system.

The method of operating the electronic device according to various embodiments may further include, when storing a file, storing the file in data blocks of the second volume in response to all data blocks of the first volume being allocated.

The electronic device according to various embodiments may be one of various types of electronic devices. The electronic devices 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 home appliance. According to an embodiment of the disclosure, the electronic devices are not limited to those described above.

It should be appreciated that various embodiments of the disclosure and the terms used therein are not intended to limit the technological features set forth herein to particular embodiments and include various changes, equivalents, or replacements for a corresponding embodiment. With regard to the description of the drawings, similar reference numerals may be used to refer to similar or related elements. As used herein, each of such phrases 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 include any one of, or all possible combinations of the items enumerated together in a corresponding one of the phrases. As used herein, such terms as “1st” and “2nd,” or “first” and “second” may be used to simply distinguish a corresponding component from another, and does not limit the components in other aspect (e.g., importance or order). It is to be understood that if an element (e.g., a first element) is referred to, with or without the term “operatively” or “communicatively”, as “coupled with,” “coupled to,” “connected with,” or “connected to” another element (e.g., a second element), it means that the element may be coupled with the other element directly (e.g., wiredly), wirelessly, or via a third element.

As used in connection with various embodiments of the disclosure, the term “module” may include a unit implemented in hardware, software, or firmware, and may interchangeably be used with other terms, for example, “logic,” “logic block,” “part,” or “circuitry”. A module may be a single integral component, or a minimum unit or part thereof, adapted to perform one or more functions. For example, according to an embodiment, the module may be implemented in a form of an application-specific integrated circuit (ASIC).

Various embodiments as set forth herein may be implemented as software (e.g., the program140) including one or more instructions that are stored in a storage medium (e.g., internal memory136or external memory138) that is readable by a machine (e.g., the electronic device101). For example, a processor (e.g., the processor120) of the machine (e.g., the electronic device101) may invoke at least one of the one or more instructions stored in the storage medium, and execute it, with or without using one or more other components under the control of the processor. This allows the machine to be operated to perform at least one function according to the at least one instruction invoked. The one or more instructions may include a code generated by a complier or a code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein, the term “non-transitory” simply means that the storage medium is a tangible device, and does not include a signal (e.g., an electromagnetic wave), but this term does not differentiate between where data is semi-permanently stored in the storage medium and where the data is temporarily stored in the storage medium.

According to an embodiment, a method according to various embodiments of the disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read only memory (CD-ROM)), or be distributed (e.g., downloaded or uploaded) online via an application store (e.g., PlayStore™), or between two user devices (e.g., smart phones) directly. If distributed online, at least part of the computer program product may be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory of the manufacturer's server, a server of the application store, or a relay server.

According to various embodiments, each component (e.g., a module or a program) of the above-described components may include a single entity or multiple entities, and some of the multiple entities may be separately disposed in different components. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) may be integrated into a single component. In such a case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as they are performed by a corresponding one of the plurality of components before the integration. According to various embodiments, operations performed by the module, the program, or another component may be carried out sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be executed in a different order or omitted, or one or more other operations may be added.

While the disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the disclosure as defined by the appended claims and their equivalents.