KR20240020131A - Apparatus and method for managing processes - Google Patents

Abstract

The present disclosure relates to a process management device and method. When a process starts, information about the started process is updated in the process list, and the number preset in the process list in order of priority to be protected is checked as a kill protection list, When a process kill event occurs, processes that are not included in the kill protection list can be selected and deleted from memory, depending on the type of process kill event.

Description

Process management apparatus and method {APPARATUS AND METHOD FOR MANAGING PROCESSES}

The following embodiments are intended to control the phenomenon of processes being frequently uploaded to memory.

The more memory a process uses, the more data stored in memory is forced out of memory due to physical limitations.

In operating systems that support multi-tasking, such as the Android operating system, multiple processes can be uploaded to memory at the same time. This operating system cannot keep all processes in memory due to physical memory limitations, and when memory is insufficient or the number of processes in memory exceeds a certain number, processes are killed.

When a process is started and killed, the system performs various tasks such as making system calls, setting permissions, granting permissions, checking permissions, and loading resources that must actually be used. This is sometimes a burden on the system.

In particular, when multiple processes are started at the same time, the system may stutter. This is why the terminal may stutter immediately after booting.

When a process is killed, the system also runs a signal handler, cleans up memory, and cleans up the created process records. This causes as much load as when the process starts. .

Therefore, frequent process startup and kill situations are one of the main causes of terminal stuttering and deterioration of the user's perceived performance.

A process management method according to an embodiment includes: when a process starts (210), updating information about the started process in a process list (220); An operation (230) of checking a preset number of processes in the process list in order of high priority to be protected as a kill protection list; And when a process kill event occurs (240), an operation (250) of selecting a process that is not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110.

A process management device according to an embodiment includes a memory 110 to which a process is uploaded; And when a process starts, the information about the started process is updated in the process list, the number preset in the process list in order of priority protected is checked with the kill protection list, and when a process kill event occurs, the process Depending on the type of kill event, it may include a processor 120 that selects a process not included in the kill protection list and deletes it from the memory 110.

FIG. 1 is a diagram illustrating a schematic configuration of a process management device according to an embodiment.
Figure 2 is a flowchart illustrating a process for managing a process in a process management device according to an embodiment.
Figure 3 is a flowchart illustrating a process of updating a process list in a process management device according to an embodiment.
Figure 4 is a flowchart illustrating a process of initializing a process list and a kill protection list at preset time intervals in a process management device according to an embodiment.
Figure 5 is a flowchart illustrating a processing process when a process kill event due to a user request occurs in a process management device according to an embodiment.
FIG. 6 is a flowchart illustrating a processing process when a process kill event occurs because the number of processes uploaded to memory exceeds a preset number in a process management device according to an embodiment.
FIG. 7 is a flowchart illustrating a process when a process kill event occurs due to insufficient memory in a process management device according to an embodiment.
Figure 8 is a block diagram of an electronic device in a network environment according to an embodiment.

Hereinafter, embodiments will be described in detail with reference to the attached drawings. However, various changes can be made to the embodiments, so the scope of the patent application is not limited or limited by these embodiments. It should be understood that all changes, equivalents, or substitutes for the embodiments are included in the scope of rights.

The terms used in the examples are for descriptive purposes only and should not be construed as limiting. Singular expressions include plural expressions unless the context clearly dictates otherwise. In this specification, terms such as “comprise” or “have” are intended to designate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, but are not intended to indicate the presence of one or more other features. It should be understood that this does not exclude in advance the possibility of the existence or addition of elements, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by a person of ordinary skill in the technical field to which the embodiments belong. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the related technology, and unless explicitly defined in the present application, should not be interpreted in an ideal or excessively formal sense. No.

In addition, when describing with reference to the accompanying drawings, identical components will be assigned the same reference numerals regardless of the reference numerals, and overlapping descriptions thereof will be omitted. In describing the embodiments, if it is determined that detailed descriptions of related known technologies may unnecessarily obscure the gist of the embodiments, the detailed descriptions are omitted.

Additionally, in describing the components of the embodiment, terms such as first, second, A, B, (a), and (b) may be used. These terms are only used to distinguish the component from other components, and the nature, sequence, or order of the component is not limited by the term. When a component is described as being "connected," "coupled," or "connected" to another component, that component may be directly connected or connected to that other component, but there is no need for another component between each component. It should be understood that may be “connected,” “combined,” or “connected.”

Components included in one embodiment and components including common functions will be described using the same names in other embodiments. Unless stated to the contrary, the description given in one embodiment may be applied to other embodiments, and detailed description will be omitted to the extent of overlap.

Below, according to an embodiment of the present invention The process management device and method will be described in detail with reference to the attached FIGS. 1 to 8.

FIG. 1 is a diagram illustrating a schematic configuration of a process management device according to an embodiment.

Referring to FIG. 1, the process management device 100 may include a memory 110 and a processor 120.

The memory 110 may be volatile memory such as RAM.

Processes controlled by the processor 120 may be uploaded to the memory 110 .

When a process starts, the processor 120 can update information about the started process in the process list.

In addition, the processor 120 can confirm the kill protection list as a preset number in order of priority to be protected in the process list.

Also, when a process kill event occurs, the processor 120 may select a process that is not included in the kill protection list according to the type of the process kill event and delete it from the memory 110.

When updating the process list, the processor 120 may search for information about the started process in the process list and check whether information about the started process exists in the process list.

If, as a result of the confirmation, there is no information about the started process in the process list, the processor 120 initializes the information about the number of starts, start intervals, and start time, and updates the process list with the process identification information of the started process. You can. At this time, the number of starts is the number of times the started process started, the start interval is the time interval between the previous start time of the started process and the current start time, and the start time is the number of days it takes for the started process to start after receiving the start request. there is.

As a result of the check, if information about the started process exists in the process list, the processor 120 increases the start count of the started process by 1, compares the start interval of the started process stored in the process list with the current start interval of the started process, and sets a smaller You can update the value and update it to a larger value by comparing the startup time of the started process stored in the process list with the current startup time of the started process.

When updating the process list, the processor 120 may delete from the process list the process with the oldest update among the processes present in the process list if the number of processes included in the process list exceeds a preset number. That is, the processor 120 can manage the number of processes included in the process list to a preset number.

When the processor 120 checks the kill protection list for a preset number of protected processes in the process list in order of high priority, the processor 120 may assign priorities to the processes included in the process list in the order of the highest number of starts.

When assigning priorities, the processor 120 may assign a higher priority to a process that takes longer to start among processes that have the same number of starts.

Additionally, in the case of processes with the same number of starts and similar start times (within a preset offset range), the processor 120 may assign a higher priority to a process with a shorter start interval.

If the process kill event is a result of a user's request, the processor 120 checks whether the process requested to be killed by the user is included in the kill protection list, and if the process requested to be killed by the user is included in the kill protection list, the processor 120 deletes it from the memory 110. You can skip it without doing it. The processor 120 may delete the process that the user has requested to kill from the memory 110 if it is not included in the kill protection list.

If a process kill event occurs when the number of processes uploaded to the memory 110 exceeds a preset number, the processor 120 may check which processes are inactive among the processes uploaded to the memory 110. Additionally, the processor 120 may select processes in the order in which they were started most recently among inactive processes. Also, if the selected process does not exist in the kill protection list, the processor 120 may skip the selected process to be deleted from the memory 110 and select the next process in the kill protection list. Additionally, the processor 120 may delete the selected process from the memory 110 if it does not exist in the kill protection list.

When uploading a started process to the memory 110, the processor 120 may initialize the skip flag of the started process to false and upload it. If the process kill event occurs when the memory 110 is insufficient, the processor 120 may select the lowest priority group among groups divided according to priority in the memory 110. Additionally, the processor 120 may select the process with the largest usage of the memory 110 among processes included in the selected group and whose skip flag is false. If the selected process is included in the kill protection list, the skip flag of the selected process is converted to true, and the processor to be deleted from memory can be selected again as described above. At this time, the above-described method may be to select the process with the largest usage of the memory 110 among the processes included in the selected group and whose skip flag is false. Additionally, the processor 120 may delete the selected process from the memory 110 if the selected process is not included in the kill protection list.

At this time, groups classified by priority may be classified into a high priority group, a medium priority group, and a low priority group. The high priority group may be a group of processes that are uploaded to the memory 110 and are operating in the foreground. The medium priority group may be a group of processes that are uploaded to the memory 110 and are being serviced. The lower priority group may be a group of processes that are uploaded to the memory 110 and operating in the background.

The processor 120 may initialize the process list and kill protection list at preset time intervals 410. At this time, initialization may be converting the process list and kill protection list into a preset process list and a preset kill protection list.

When process management software is installed in the process management device 100, a process list may be created as a preset process list including preset processes. In other words, when the process list is initially created, it may be created as a preset process list including preset processes. At this time, the preset processes included in the preset process list may be arbitrary processes that the developer determines will be started frequently.

Meanwhile, when the process management software in the process management device 100 is updated, the process list may be updated to a preset process list including preset processes.

Hereinafter, the method according to the present disclosure configured as above will be described with reference to the drawings.

Figure 2 is a flowchart illustrating a process for managing a process in a process management device according to an embodiment.

Referring to FIG. 2, when a process starts (210), the process management device 100 may update information about the started process in the process list (220). At this time, the information about the started process to be updated may be information about process identification information, start count, start interval, and start time. At this time, the number of starts is the number of times the started process started, the start interval is the time interval between the previous start time of the started process and the current start time, and the start time is the time it takes for the started process to start after receiving the start request. there is. A more detailed description of operation 220 will be described later with reference to FIG. 3.

Additionally, the process management device 100 may check the kill protection list as a preset number in order of priority to be protected in the process list (230). At this time, in operation 230, the process management device 100 may assign priorities to processes included in the process list in the order of the highest number of starts. In operation 230, for processes with the same number of starts, the process management device 100 may assign a higher priority to a process with a longer start time. In operation 230, the process management device 100 may assign a higher priority to a process with a shorter start interval for processes that have the same number of starts and whose start time is within a preset offset range.

Then, the process management device 100 checks whether a process kill event occurs (240).

If a process kill event occurs as a result of confirmation of operation 240 (240), processes not included in the kill protection list can be selected and deleted from the memory 110 according to the type of the process kill event (250). A more detailed description of operation 250 according to the type of process kill event will be described later with reference to FIGS. 5, 6, and 7.

The process management device 100 of the present disclosure manages frequently started processes to reside in the memory 110 for a long time through the process of FIG. 2, thereby improving stuttering due to frequent starting and killing of processes.

Figure 3 is a flowchart illustrating a process of updating a process list in a process management device according to an embodiment.

Referring to FIG. 3, the process management device 100 may search for information about the started process in the process list and check whether information about the started process exists in the process list (310).

As a result of checking operation 310, if there is no information about the started process in the process list, the process management device 100 may check whether the number of processes included in the process list exceeds the preset number (312).

As a result of checking operation 312, if the number of processes included in the process list exceeds the preset number, the process management device 100 may delete the process with the oldest update among the processes existing in the process list from the process list (314). .

In FIG. 3, if the number of processes included in the process list is not managed to a preset number, operations 312 and 314 may be omitted.

As a result of operation 310, if there is no information about the process started in the process list, as a result of operation 312, if the number of processes included in the process list does not exceed the preset number, or after performing operation 314 The process management device 100 may initialize information regarding the number of starts, start intervals, and start time (316).

As a result of checking operation 310, if information about the started process exists in the process list, the process management device 100 increases the start count of the started process by 1, and increases the start interval of the started process stored in the process list and the current start interval of the started process. You can set it to a smaller value by comparing , and set it to a larger value by comparing the startup time of the started process stored in the process list with the current startup time of the started process (318).

After operation 316 or 318, the process management device 100 may update the process list with information about the process identification information, start number, start interval, and start time of the started process (320).

Figure 4 is a flowchart illustrating a process of initializing a process list and a kill protection list at preset time intervals in a process management device according to an embodiment.

Referring to FIG. 4, the process management device 100 may check whether a preset time interval has elapsed (410).

As a result of checking operation 410, if the preset time interval has elapsed, the process management device 100 may initialize the process list and kill protection list (420).

At this time, initialization of the process list and kill protection list may be to convert the process list and kill protection list into a preset process list and a preset kill protection list.

Figure 5 is a flowchart illustrating a processing process when a process kill event due to a user request occurs in a process management device according to an embodiment.

Referring to FIG. 5, if the process kill event is a result of a user's request (510), the process management device 100 may check whether the process requested to be killed by the user is included in the kill protection list (512).

As a result of checking operation 521, if the process requested to be killed by the user is included in the kill protection list, the process management device 100 may skip the process requested to be killed by the user without deleting it from the memory 110 (514). .

As a result of checking operation 521, if the process requested to be killed by the user is not included in the kill protection list, the process management device 100 may delete the process requested to be killed by the user from the memory 110 (516).

FIG. 6 is a flowchart illustrating a processing process when a process kill event occurs because the number of processes uploaded to memory exceeds a preset number in a process management device according to an embodiment.

Referring to FIG. 6, the process management device 100 may check whether a process kill event occurred because the number of processes uploaded to the memory 110 exceeds a preset number (610).

As a result of checking operation 610, if the number of processes uploaded to the memory 110 exceeds the preset number and a process kill event occurs, the process management device 100 selects an inactive process among the processes uploaded to the memory 110. You can check (612).

Additionally, the process management device 100 may select processes in the order in which they were started most recently among inactive processes (614).

Additionally, the process management device 100 may check whether the selected process exists in the kill protection list (616).

As a result of checking operation 616, if the selected process exists in the kill protection list, the process management device 100 can skip deletion of the selected process and select the next process (618). After operation 618, the process management device 100 may return to operation 616.

If the selected process exists in the kill protection list as a result of checking operation 616, the process management device 100 may delete the selected process from the memory 110 (620).

FIG. 7 is a flowchart illustrating a process when a process kill event occurs due to insufficient memory in a process management device according to an embodiment.

Referring to FIG. 7 , the process management device 100 may check whether a process kill event occurred due to a shortage of memory 110 (710).

If, as a result of the confirmation in step 710, it is a process kill event due to insufficient memory 110, the process management device 100 may select the lowest priority group among the groups divided according to priority in the memory 110 (712) ). At this time, groups classified by priority may be classified into a high priority group, a medium priority group, and a low priority group. The high priority group may be a group of processes that are uploaded to the memory 110 and are operating in the foreground. The medium priority group may be a group of processes that are uploaded to the memory 110 and are being serviced. The lower priority group may be a group of processes that are uploaded to the memory 110 and operating in the background.

Additionally, the process management device 100 may select the process with the largest usage of the memory 110 among the processes included in the selected group and whose skip flag is false (714). At this time, the skip flag of the started process may be initialized to false and uploaded when the started process is uploaded to the memory 110.

Additionally, the process management device 100 may check whether the selected process is included in the kill protection list (716).

As a result of checking operation 716, if the selected process is included in the kill protection list,

The process management device 100 may convert the skip flag of the selected process to true (718). After operation 718, the process management device 100 may return to operation 714.

As a result of checking operation 716, if the selected process is not included in the kill protection list, the process management device 100 may delete the selected process from the memory 110 (720).

Figure 8 is a block diagram of an electronic device in a network environment according to one embodiment.

Referring to FIG. 8, in the network environment 800, the electronic device 801 communicates with the electronic device 802 through a first network 898 (e.g., a short-range wireless communication network) or a second network 899. It is possible to communicate with at least one of the electronic device 804 or the server 808 through (e.g., a long-distance wireless communication network). According to one embodiment, the electronic device 801 may communicate with the electronic device 804 through the server 808. According to one embodiment, the electronic device 801 includes a processor 820, a memory 830, an input module 850, an audio output module 855, a display module 860, an audio module 870, and a sensor module ( 876), interface 877, connection terminal 878, haptic module 879, camera module 880, power management module 888, battery 889, communication module 890, subscriber identification module 896 , or may include an antenna module 897. In some embodiments, at least one of these components (eg, the connection terminal 878) may be omitted, or one or more other components may be added to the electronic device 801. In some embodiments, some of these components (e.g., sensor module 876, camera module 880, or antenna module 897) are integrated into one component (e.g., display module 860). It can be.

The processor 820, for example, executes software (e.g., program 840) to operate at least one other component (e.g., hardware or software component) of the electronic device 801 connected to the processor 820. It can be controlled and various data processing or calculations can be performed. According to one embodiment, as at least part of data processing or computation, the processor 820 stores commands or data received from another component (e.g., sensor module 876 or communication module 890) in volatile memory 832. The commands or data stored in the volatile memory 832 can be processed, and the resulting data can be stored in the non-volatile memory 834. According to one embodiment, the processor 820 includes a main processor 821 (e.g., a central processing unit or an application processor) or an auxiliary processor 823 that can operate independently or together (e.g., a graphics processing unit, a neural network processing unit ( It may include a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, if the electronic device 801 includes a main processor 821 and a auxiliary processor 823, the auxiliary processor 823 may be set to use lower power than the main processor 821 or be specialized for a designated function. You can. The auxiliary processor 823 may be implemented separately from the main processor 821 or as part of it.

The auxiliary processor 823 may, for example, act on behalf of the main processor 821 while the main processor 821 is in an inactive (e.g., sleep) state, or while the main processor 821 is in an active (e.g., application execution) state. ), together with the main processor 821, at least one of the components of the electronic device 801 (e.g., the display module 860, the sensor module 876, or the communication module 890) At least some of the functions or states related to can be controlled. According to one embodiment, co-processor 823 (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module 880 or communication module 890). there is. According to one embodiment, the auxiliary processor 823 (eg, neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. Artificial intelligence models can be created through machine learning. For example, such learning may be performed in the electronic device 801 itself on which the artificial intelligence model is performed, or may be performed through a separate server (e.g., server 808). Learning algorithms may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but It is not limited. An artificial intelligence model may include multiple artificial neural network layers. Artificial neural networks include deep neural network (DNN), convolutional neural network (CNN), recurrent neural network (RNN), restricted boltzmann machine (RBM), belief deep network (DBN), bidirectional recurrent deep neural network (BRDNN), It may be one of 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 hardware structures, artificial intelligence models may additionally or alternatively include software structures.

At least one or a combination of the processor 820, the main processor 821, and the auxiliary processor 823 may perform the operations of the processor 120 of FIG. 1.

The memory 830 may store various data used by at least one component (eg, the processor 820 or the sensor module 876) of the electronic device 801. Data may include, for example, input data or output data for software (e.g., program 840) and instructions related thereto. Memory 830 may include volatile memory 832 or non-volatile memory 834. Volatile memory 832 can perform the operation of memory 110 of FIG. 1.

The program 840 may be stored as software in the memory 830 and may include, for example, an operating system 842, middleware 844, or application 846.

The input module 850 may receive commands or data to be used in a component of the electronic device 801 (e.g., the processor 820) from outside the electronic device 801 (e.g., a user). The input module 850 may include, for example, a microphone, mouse, keyboard, keys (eg, buttons), or digital pen (eg, stylus pen).

The sound output module 855 may output sound signals to the outside of the electronic device 801. The sound output module 855 may include, for example, a speaker or receiver. Speakers can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to one embodiment, the receiver may be implemented separately from the speaker or as part of it.

The display module 860 can visually provide information to the outside of the electronic device 801 (eg, a user). The display module 860 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling the device. According to one embodiment, the display module 860 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by the touch.

The audio module 870 can convert sound into an electrical signal or, conversely, convert an electrical signal into sound. According to one embodiment, the audio module 870 acquires sound through the input module 850, the sound output module 855, or an external electronic device (e.g., directly or wirelessly connected to the electronic device 801). Sound may be output through an electronic device 802 (e.g., speaker or headphone).

The sensor module 876 detects the operating state (e.g., power or temperature) of the electronic device 801 or the external environmental state (e.g., user state) and generates an electrical signal or data value corresponding to the detected state. can do. According to one embodiment, the sensor module 876 includes, for example, a gesture sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, humidity sensor, or light sensor.

The interface 877 may support one or more designated protocols that can be used to connect the electronic device 801 directly or wirelessly with an external electronic device (eg, the electronic device 802). According to one embodiment, the interface 877 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 878 may include a connector through which the electronic device 801 can be physically connected to an external electronic device (eg, the electronic device 802). According to one embodiment, the connection terminal 878 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

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

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

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

Battery 889 may supply power to at least one component of electronic device 801. According to one embodiment, the battery 889 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

Communication module 890 is configured to provide a direct (e.g., wired) communication channel or wireless communication channel between electronic device 801 and an external electronic device (e.g., electronic device 802, electronic device 804, or server 808). It can support establishment and communication through established communication channels. Communication module 890 operates independently of processor 820 (e.g., an application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module 890 is a wireless communication module 892 (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 module 894 (e.g., : LAN (local area network) communication module, or power line communication module) may be included. Among these communication modules, the corresponding communication module is a first network 898 (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 899 (e.g., legacy It may communicate with an external electronic device 804 through a telecommunication network such as a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., LAN or WAN). These various types of communication modules may be integrated into one component (e.g., a single chip) or may be implemented as a plurality of separate components (e.g., multiple chips). The wireless communication module 892 uses subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 896 to communicate within a communication network such as the first network 898 or the second network 899. The electronic device 801 can be confirmed or authenticated.

The wireless communication module 892 may support 5G networks after 4G networks and next-generation communication technologies, for example, NR access technology (new radio access technology). NR access technology provides high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low latency). -latency communications)) can be supported. The wireless communication module 892 may support high frequency bands (e.g., mmWave bands), for example, to achieve high data rates. The wireless communication module 892 uses various technologies to secure performance in high frequency bands, such as beamforming, massive MIMO (multiple-input and multiple-output), and full-dimensional multiplexing. It can support technologies such as input/output (FD-MIMO: full dimensional MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module 892 may support various requirements specified in the electronic device 801, an external electronic device (e.g., electronic device 804), or a network system (e.g., second network 899). According to one embodiment, the wireless communication module 892 supports 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., 164 dB or less) for realizing URLLC. Example: Downlink (DL) and uplink (UL) each of 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 897 may transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to one embodiment, the antenna module 897 may include an antenna including a radiator made of a conductor or a conductive pattern formed on a substrate (eg, PCB). According to one embodiment, the antenna module 897 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for the communication method used in the communication network, such as the first network 898 or the second network 899, is connected to the plurality of antennas by, for example, the communication module 890. can be selected. Signals or power may be transmitted or received between the communication module 890 and an external electronic device through the selected at least one antenna. According to some embodiments, in addition to the radiator, other components (eg, radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module 897.

According to various embodiments, antenna module 897 may form a mmWave antenna module. According to one embodiment, a mmWave antenna module includes a printed circuit board, an RFIC disposed on or adjacent to a first side (e.g., bottom side) of the printed circuit board and capable of supporting a designated high frequency band (e.g., mmWave band); And a plurality of antennas (e.g., array antennas) disposed on or adjacent to the second side (e.g., top or side) of the printed circuit board and capable of transmitting or receiving signals in the designated high frequency band. can do.

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

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

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may store program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the medium may be specially designed and configured for the embodiment or may be known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. -Includes optical media (magneto-optical media) and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include machine language code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing unit to operate as desired, or may be processed independently or collectively. You can command the device. Software and/or data may be used on any type of machine, component, physical device, virtual equipment, computer storage medium or device to be interpreted by or to provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

Although the embodiments have been described with limited drawings as described above, those skilled in the art can apply various technical modifications and variations based on the above. For example, the described techniques are performed in a different order than the described method, and/or components of the described system, structure, device, circuit, etc. are combined or combined in a different form than the described method, or other components are used. Alternatively, appropriate results may be achieved even if substituted or substituted by an equivalent.

Therefore, other implementations, other embodiments, and equivalents of the claims also fall within the scope of the following claims.

A process management method according to an embodiment includes: when a process starts (210), updating information about the started process in a process list (220); An operation (230) of checking a preset number of processes in the process list in order of high priority to be protected as a kill protection list; And when a process kill event occurs (240), an operation (250) of selecting a process that is not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110.

In the process management method according to an embodiment, the operation 220 of updating the process list includes searching 310 for information about the started process in the process list, and determining that information about the started process exists in the process list. If not, an operation 320 of initializing information on the number of starts, start intervals, and start time required, and updating the process list along with process identification information of the started process (320).

At this time, the start count is the number of times the started process started, the start interval is the time interval between the previous start time of the started process and the current start time, and the start time is the start time when the started process starts after receiving a start request. It may be the time it takes for it to happen.

In the process management method according to an embodiment, the operation 220 of updating the process list includes searching 310 for information about the started process in the process list, and determining that information about the started process exists in the process list. If so, the start count of the started process is increased by 1, the start interval of the started process stored in the process list is compared with the current start interval of the started process, updated to a smaller value, and the started process stored in the process list is updated to a smaller value. It may include operations 318 and 320 of comparing the start time required for and the current start time required for the started process and updating it to a larger value.

In the process management method according to one embodiment, the operation of updating the process list (220) includes, when the number of processes included in the process list exceeds a preset number (312), the update is performed among the processes existing in the process list. An operation 314 of deleting the oldest process from the process list may be included.

In the process management method according to one embodiment, the operation 230 of checking the number of preset numbers in the process list in the order of high priority protected as the kill protection list is determined by the order in which the processes included in the process list have a high number of start times. For processes with the same number of starts, a higher priority is assigned to a process with a longer start time, and processes with the same number of starts and whose start time are within a preset offset range In these cases, a higher priority can be assigned to processes with shorter startup intervals.

In the process management method according to one embodiment, the operation 250 of selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110 is performed when the process kill event is requested by the user. If so (510), it is checked (512) whether the process that the user requested to kill is included in the kill protection list, and if the process that the user requested to kill is included in the kill protection list, it is deleted from the memory (110). Otherwise, if the process requested to be killed by the user is not included in the kill protection list, it can be deleted from the memory 110 (516).

In the process management method according to an embodiment, the operation 250 of selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110 is performed when the process kill event is selected from the memory ( If the number of processes uploaded to 110) exceeds the preset number (610), the inactive process among the processes uploaded to the memory 110 is checked (612), and the most inactive process is checked (612). Select a process in the order started a long time ago (614), and if the selected process exists in the kill protection list (616), skip it and select a process in the next order (618), and if the selected process exists in the kill protection list, If not (616), it can be deleted (620) from the memory 110.

In the process management method according to one embodiment, the operation 220 of updating information about the started process to the process list includes, when uploading the started process to the memory 110, the skip flag of the started process is set to false ( In the operation 250 of initializing and uploading to false) and selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110, the process kill event is deleted from the memory 110. ), if a shortage situation occurs (710), the lowest priority group is selected (712) among the groups divided according to priority in the memory 110, and the group included in the selected group and the skip flag is false is selected (712). Among the processes, the process with the largest usage of the memory 110 is selected (714), and if the selected process is not included in the kill protection list (716), the selected process is deleted from the memory 110 (720). , if the selected process is included in the kill protection list (716), the skip flag of the selected process can be converted to true (718).

At this time, in the group, processes uploaded to the memory 110 and operating in the foreground are classified as a high priority group, and processes uploaded to the memory 110 and in service are classified as a medium priority group. Processes uploaded to the memory 110 and operating in the background may be classified into a lower priority group.

The process management method according to an embodiment may further include an operation 420 of initializing the process list and the kill protection list at a preset time interval 410.

In the process management method according to one embodiment, the initializing operation 420 may be performed by converting the process list and the kill protection list into a preset process list and a preset kill protection list.

In the process management method according to one embodiment, when the process list is initially created, it may be created as a preset process list including preset processes.

A process management device according to an embodiment includes a memory 110 to which a process is uploaded; And when a process starts, the information about the started process is updated in the process list, the number preset in the process list in order of priority protected is checked with the kill protection list, and when a process kill event occurs, the process Depending on the type of kill event, it may include a processor 120 that selects a process not included in the kill protection list and deletes it from the memory 110.

When updating the process list, the processor 120 of the process management device according to one embodiment searches for information about the started process in the process list, and determines that information about the started process exists in the process list. If not, information on the number of starts, start intervals, and start time required can be initialized and updated in the process list along with the process identification information of the started process.

At this time, the start count is the number of times the started process started, the start interval is the time interval between the previous start time of the started process and the current start time, and the start time is the start time when the started process starts after receiving a start request. It may be the time it takes for it to happen.

When updating the process list, the processor 120 of the process management device according to one embodiment searches for information about the started process in the process list, and determines that information about the started process exists in the process list. If so, the start count of the started process is increased by 1, the start interval of the started process stored in the process list is compared with the current start interval of the started process, updated to a smaller value, and the started process stored in the process list is updated to a smaller value. It can be updated to a larger value by comparing the start time required for and the current start time required for the process started above.

When updating the process list, the processor 120 of the process management device according to one embodiment updates the process among the processes present in the process list if the number of processes included in the process list exceeds a preset number. The oldest process can be deleted from the process list.

When the processor 120 of the process management device according to an embodiment checks the number preset in the process list in order of high priority as a kill protection list, the number of starts of the process included in the process list is Priorities are assigned in higher order, and for processes with the same number of starts, a higher priority is assigned to a process with a longer start time, and the number of starts is the same, and the start time is within a preset offset range. For processes that exist, higher priorities can be assigned to processes with shorter startup intervals.

If the process kill event is a result of a user's request, the processor 120 of the process management device according to one embodiment checks whether the process requested to be killed by the user is included in the kill protection list, and determines whether the process requested to be killed by the user is included in the kill protection list. If a process is included in the kill protection list, it may not be deleted from the memory 110. If the process requested to be killed by the user is not included in the kill protection list, it may be deleted from the memory 110.

The processor 120 of the process management device according to an embodiment may, if the process kill event occurs when the number of processes uploaded to the memory 110 exceeds a preset number, Among the processes, an inactive process is checked, a process is selected from among the inactive processes in the order in which it was started most recently, and if the selected process exists in the kill protection list, it is skipped and the next process is selected, and the selected process is selected. If a process does not exist in the kill protection list, it can be deleted from the memory 110.

When uploading the started process to the memory 110, the processor 120 of the process management device according to one embodiment initializes the skip flag of the started process to false, uploads it, and kills the process. If the event occurs due to a shortage of the memory 110, a process that selects the lowest priority group among the groups divided according to priority in the memory 110 and is included in the selected group and the skip flag is false Among them, the process with the largest usage of the memory 110 is selected, and if the selected process is not included in the kill protection list, the selected process is deleted from the memory 110, and the selected process is included in the kill protection list. If included, the skip flag of the selected process can be converted to true.

[One]

Claims (20)

When a process starts (210), an operation of updating information about the started process in the process list (220);
An operation (230) of checking a preset number of processes in the process list in order of high priority to be protected as a kill protection list; and
When a process kill event occurs (240), an operation (250) of selecting processes that are not included in the kill protection list according to the type of the process kill event and deleting them from the memory (110).
Process management method including.
According to paragraph 1,
The operation 220 of updating the process list is,
Information about the started process is searched in the process list (310), and if information about the started process does not exist in the process list, information about the number of starts, start intervals, and start time is initialized (316). , An operation of updating the process list with the process identification information of the started process (320)
Including,
The number of starts is,
The number of times the started process was started,
The starting interval is,
The time interval between the previous start time and the current start time of the started process,
The starting time is,
The time taken for the started process to receive the start request and start
How to manage the process.
According to any one of claims 1 and 2,
The operation 220 of updating the process list is,
Information about the started process is searched in the process list (310), and if information about the started process exists in the process list, the start count of the started process is increased by 1, and the started process stored in the process list is increased by 1. Compare the start interval of the started process with the current start interval of the started process and update it to a smaller value, and compare the start time of the started process stored in the process list with the current start time of the started process and update it to a larger value. Action (318, 320)
Including,
The number of starts is,
The number of times the started process was started,
The starting interval is,
The time interval between the previous start time and the current start time of the started process,
The starting time is,
The time taken for the started process to receive the start request and start
How to manage the process.
According to any one of claims 1 to 3,
The operation 220 of updating the process list is,
If the number of processes included in the process list exceeds a preset number (312), the operation of deleting the process with the oldest update among the processes existing in the process list from the process list (314)
Process management method including.
According to any one of claims 1 to 4,
The operation 230 of checking the kill protection list for a preset number of protected processes in the process list in order of high priority,
Assign priorities to the processes included in the process list in order of the highest number of starts,
For processes with the same number of startups, a higher priority is assigned to the process with a longer startup time,
For processes where the number of starts is the same and the start time is within a preset offset range, a higher priority is assigned to the process with a shorter start interval.
How to manage the process.
According to any one of claims 1 to 5,
Operation 250 of selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110,
If the process kill event is due to a user's request (510), check whether the process requested to be killed by the user is included in the kill protection list (512),
If the process requested to be killed by the user is included in the kill protection list, it is not deleted from the memory 110 (514),
If the process requested to be killed by the user is not included in the kill protection list, it is deleted (516) from the memory 110.
How to manage the process.
According to any one of claims 1 to 6,
Operation 250 of selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110,
If the process kill event occurs when the number of processes uploaded to the memory 110 exceeds the preset number (610), inactive processes among the processes uploaded to the memory 110 are checked (612) ,
Among the inactive processes, the process is selected in the order in which it was started most recently (614),
If the selected process exists in the kill protection list (616), skip it and select the next process (618),
If the selected process does not exist in the kill protection list (616), it is deleted (620) from the memory 110.
How to manage the process.
According to any one of claims 1 to 7,
Operation 220 of updating information about the started process to the process list,
When uploading the started process to the memory 110, the skip flag of the started process is initialized to false and uploaded,
Operation 250 of selecting a process not included in the kill protection list according to the type of the process kill event and deleting it from the memory 110,
If the process kill event occurs in a situation where the memory 110 is insufficient (710), the group with the lowest priority is selected from among the groups divided according to priority in the memory 110 (712),
Selecting the process with the largest usage of the memory 110 among the processes included in the selected group and having a false skip flag (714),
If the selected process is not included in the kill protection list (716), the selected process is deleted (720) from the memory 110,
If the selected process is included in the kill protection list (716), the skip flag of the selected process is converted to true (718).
How to manage the process.
According to any one of claims 1 to 8,
The group is:
Processes uploaded to the memory 110 and operating in the foreground are classified into a high priority group,
Processes uploaded to the memory 110 and in service are classified into a medium priority group,
Processes uploaded to the memory 110 and operating in the background are classified into a lower priority group.
How to manage the process.
According to any one of claims 1 to 9,
An operation (420) to initialize the process list and the kill protection list at a preset time interval (410).
A process management method further comprising:
According to any one of claims 1 to 10,
The initializing operation 420 is,
Initializing the process list and the kill protection list by converting them into a preset process list and a preset kill protection list.
How to manage the process.
According to any one of claims 1 to 11,
The process list is,
When initially created, it is created as a preset process list containing preset processes.
How to manage the process.
Memory 110 to which the process is uploaded; and
When a process starts, the information about the started process is updated in the process list, the number preset in the process list in order of priority protected is checked with the kill protection list, and when a process kill event occurs, the process kill A processor 120 that selects processes not included in the kill protection list according to the type of event and deletes them from the memory 110.
A process management device including a.
According to clause 13,
The processor 120,
When updating the process list,
Search for information about the started process in the process list, and if there is no information about the started process in the process list, initialize information about the number of starts, start intervals, and start time, and start the process of the started process. Update the process list with identification information,
The number of starts is,
The number of times the started process was started,
The starting interval is,
The time interval between the previous start time and the current start time of the started process,
The starting time is,
The time taken for the started process to receive the start request and start
Process management device.
According to any one of claims 13 to 14,
The processor 120,
When updating the process list,
Search for information about the started process in the process list, and if information about the started process exists in the process list, increase the start count of the started process by 1, and increase the start interval of the started process stored in the process list. Compare the current start interval of the started process and update it to a smaller value, compare the start time of the started process stored in the process list with the current start time of the started process, and update it to a larger value,
The number of starts is,
The number of times the started process was started,
The starting interval is,
The time interval between the previous start time and the current start time of the started process,
The starting time is,
The time taken for the started process to receive the start request and start
Process management device.
According to any one of claims 13 to 15,
The processor 120,
When updating the process list,
If the number of processes included in the process list exceeds a preset number, the process with the oldest update among the processes existing in the process list is deleted from the process list.
process management device
According to any one of claims 13 to 16,
The processor 120,
When checking the kill protection list for the number of processes set in order of priority protected in the above process list,
Assign priorities to the processes included in the process list in order of the highest number of starts,
For processes with the same number of startups, a higher priority is assigned to the process with a longer startup time,
For processes where the number of starts is the same and the start time is within a preset offset range, a higher priority is assigned to the process with a shorter start interval.
Process management device.
According to any one of claims 13 to 17,
The processor 120,
If the process kill event is due to a user's request, check whether the process requested to be killed by the user is included in the kill protection list,
If the process requested to be killed by the user is included in the kill protection list, it is not deleted from the memory 110,
If the process requested to be killed by the user is not included in the kill protection list, it is deleted from the memory 110.
Process management device.
According to any one of claims 13 to 18,
The processor 120,
If the process kill event occurs when the number of processes uploaded to the memory 110 exceeds the preset number, check which process is inactive among the processes uploaded to the memory 110,
Among the processes with no activity, select the process in the order in which it was started most recently,
If the selected process exists in the kill protection list, skip it and select the next process,
If the selected process does not exist in the kill protection list, it is deleted from the memory 110.
How to manage the process.
According to any one of claims 13 to 19,
The processor 120,
When uploading the started process to the memory 110, the skip flag of the started process is initialized to false and uploaded,
If the process kill event occurs in a situation where the memory 110 is insufficient, select the lowest priority group among the groups divided according to priority in the memory 110,
Selecting the process with the largest usage of the memory 110 from among the processes included in the selected group and whose skip flag is false,
If the selected process is not included in the kill protection list, delete the selected process from the memory 110,
If the selected process is included in the kill protection list, converting the skip flag of the selected process to true.
Process management device.

Images