TWI884898B - Operating method for electronic apparatus for performing cashe update and electronic apparatus supporting thereof - Google Patents

Abstract

According to the present invention, a method for implementing cache update in an electronic device is disclosed, which includes: a step of obtaining information of an update end setting time point set by a user in order to update the above-mentioned cache; a step of confirming the time required for updating the above-mentioned cache; a step of determining a start setting time point for updating the above-mentioned cache based on the above-mentioned update end setting time point and the above-mentioned update required time; and a step of implementing the first update on the above-mentioned cache based on the above-mentioned update start setting time point.

Description

Operation method of electronic device for implementing cache update and electronic device supporting the same

The present invention relates to a method and device for implementing cache update, and more specifically, to a method and electronic device for flexibly implementing cache update according to a time point set by a user.

With the development of electronic technology, e-commerce has become a field of shopping. Customers can buy items online even if they do not go directly to the mall or market, and the items purchased online will be delivered to the delivery location requested by the customer.

In the case of e-commerce, providing detailed and accurate information about products has a significant impact on service satisfaction, so various solutions for providing more detailed and accurate information are being discussed. Here, at the level of managing information, discussions on data structures including caches may also be included.

In this regard, please refer to previous literature such as KR101756594B1 or KR101500849B1.

[Problem to be solved by the invention] According to the method of the present invention, the cache can be updated flexibly according to the time point set by the user.

The technical problems that the present invention intends to solve are not limited to the technical problems mentioned above. Those with common sense in the technical field to which the present invention belongs can clearly understand other technical problems not mentioned based on the following description. [Technical means for solving the problem]

Various embodiments may provide an operation method of an electronic device for implementing cache update and an electronic device supporting the same.

The method of implementing cache update in an electronic device of various embodiments may include: a step of obtaining information of an update end setting time point set by a user in order to update the above-mentioned cache; a step of confirming the time required for updating the above-mentioned cache; a step of determining a start setting time point for updating the above-mentioned cache based on the above-mentioned update end setting time point and the above-mentioned update required time; and a step of implementing the first update of the above-mentioned cache based on the above-mentioned update start setting time point.

In an exemplary embodiment, the update required time may correspond to an average required time of a plurality of updates corresponding to an update history that has been performed on the cache.

In an exemplary embodiment, the first update may be triggered based on a data confirmation request received from the cache after the update start setting time point, and the first update is set in the following manner: it ends within a fixed time period including the update end setting time point.

In an exemplary embodiment, the cache update implementation method may further include a step configured as follows: triggering the first update based on a first data confirmation request received for the cache for the first time after the update start setting time point.

In an exemplary embodiment, the cache update implementation method may further include: a step of setting flag information for confirming whether to update the cache; and a step of setting the value of the flag information based on receiving the first data confirmation request.

In an exemplary embodiment, based on the value set in the flag information, it may be set in the following manner: updating of the cache is not triggered by other data confirmation requests received for the cache after the first data confirmation request.

In an exemplary embodiment, if no request for confirming the cached data is received after the update start setting time, the first update may not be triggered.

In an exemplary embodiment, the cache update implementation method may further include: after the update end setting time point, setting the cache expiration preset time point corresponding to the first update; and setting the step in the following manner, that is, implementing a new update to the cache after the cache expiration preset time point.

In an exemplary embodiment, the cache expiration default time can be set as follows: the fixed time interval set by the user is set from the update end setting time.

In an exemplary embodiment, the cache expiration preset time point can be set in the following manner: the update end setting time point has an arbitrary time interval determined based on a random function.

In an exemplary embodiment, the cache update implementation method may further include: based on a second data confirmation request initially received for the cache after the preset cache expiration time, performing a second update step on the cache.

In an exemplary embodiment, the cache update implementation method may further include a step configured as follows: based on receiving the second data confirmation request, interrupting the data confirmation corresponding to the data confirmation request received for the cache until the second update is completed.

In an exemplary embodiment, the cache update implementation method may further include steps configured as follows: when the second data confirmation request is received and the number of other data confirmation requests received for the cache within a fixed time after the second data confirmation request is greater than a critical number, data confirmation corresponding to the data confirmation request received for the cache is interrupted until the second update is completed.

In an exemplary embodiment, the cache update implementation method may further include: a step of receiving a third data confirmation request for the cache; a step of confirming the time point of receiving the third data confirmation request; and a step of setting in the following manner, that is, comparing the received time point with the update end setting time point and confirming the data corresponding to the third data confirmation request in the cache.

In an exemplary embodiment, it can be set as follows: when the received time point is before the update end setting time point, the previous data stored in the cache before the first update is performed is confirmed in response to the third data confirmation request.

In an exemplary embodiment, it can be set as follows: when the received time point is after the update end setting time point, the updated data stored in the cache after the first update is performed is confirmed in response to the third data confirmation request.

The electronic device for updating the cache in various embodiments may include: a processor; and one or more memories storing one or more instructions; when executing the one or more instructions, controlling the processor to perform: a step of obtaining information of an update end setting time point set by a user in order to update the cache; a step of confirming the time required for updating the cache; a step of determining a start setting time point for updating the cache based on the update end setting time point and the update required time; and a step of performing a first update on the cache based on the update start setting time point.

The above-mentioned various embodiments of the present invention are only a part of the preferred embodiments of the present invention. Those with common sense in the technical field can derive and understand multiple embodiments reflecting the technical features of the various embodiments of the present invention based on the following detailed description. [Effects of the invention]

The present invention proposes a method for flexibly implementing cache updates according to a time point set by a user, thereby having a technical effect in terms of being able to conveniently manage cache updates.

The effects that can be obtained in the present invention are not limited to the effects mentioned above. Those with common sense in the technical field to which the present invention belongs can clearly understand other effects not mentioned according to the following description.

The following embodiments are those that combine the constituent elements and features of various embodiments in a specific form. If not explicitly mentioned otherwise, each constituent element or feature can be considered optional. Each constituent element or feature can be implemented in a form that is not combined with other constituent elements or features. In addition, some constituent elements and features can be combined to form various embodiments. The flow of actions described in various embodiments can be changed. A part of the constituent elements or features of a certain embodiment can be included in other embodiments, or can be exchanged with corresponding constituent elements or features of other embodiments.

In the description of the drawings, processes or steps that may confuse the gist of various embodiments are not described, nor are processes or steps that are understandable to a person having ordinary knowledge in the technical field.

Throughout the specification, when a certain part is described as "comprising or including" a certain constituent element, unless otherwise specifically stated, it means that other constituent elements may be further included, and other constituent elements are not excluded. In addition, the terms "...part", "...device", "module" and the like stated in the specification refer to a unit that processes at least one function or action, which may be implemented by hardware, software, or a combination of hardware and software. In addition, in the text describing various embodiments (especially, in the scope of the invention application below), unless otherwise indicated in this specification or explicitly contradicted in the text, "a (a or an)", "one (one)", "the (the)" and similar related words can be used in a meaning including both the singular and the plural.

Hereinafter, with reference to the accompanying drawings, preferred implementations of various embodiments are described in detail. The detailed description disclosed below together with the accompanying drawings is for illustrating exemplary implementations of various embodiments, and is not intended to represent the only implementation.

Furthermore, specific terms used in various embodiments are provided to help understand the various embodiments, and the use of such specific terms may be changed into other forms without departing from the technical ideas of the various embodiments.

FIG. 1 is a diagram of a cache update implementation system for illustrating an operation method of an electronic device for implementing cache update in various embodiments.

Referring to FIG. 1 , the cache update implementation system of various embodiments can be implemented in various electronic devices. For example, the cache update implementation system can be implemented in a server device 100 and a manager device 200. In other words, the server device 100 and the manager device 200 can implement the actions of various embodiments of the present invention based on the cache update implementation system implemented in each device. On the other hand, the cache update implementation system of various embodiments can also be implemented in more electronic devices and servers, and is not limited to the above-mentioned FIG. 1 .

The server device 100 of various embodiments may be a device that performs wireless and wired communication with a plurality of manager devices 200 and includes a storage device with a large unit of storage capacity. For example, the server device 100 may be a cloud device that is connected to a plurality of manager devices 200.

The manager device 200 of various embodiments may be a desktop computer, a tablet computer, a mobile terminal, etc. that can be used by a personal user. In addition, other electronic devices that perform similar functions may also be used as the manager device 200. In the present invention, in particular, the terminal used by the manager or user to manage the data structure and system that provides or processes data may correspond to the above-mentioned manager device 200.

The cache update implementation system of various embodiments may include various modules for performing its actions. The modules included in the cache update implementation system may be computer codes and one or more instructions implemented in the following manner: the physical device (e.g., the server device 100 and the manager device 200) that implements the cache update implementation system (or included in the physical device) may perform a specified action. In other words, the physical device that implements the cache update implementation system may store a plurality of modules in a computer code form in a memory, and when executing the plurality of modules stored in the memory, the plurality of modules cause the physical device to perform the specified actions corresponding to the plurality of modules.

FIG. 2 is a diagram showing the configuration of a server device and a manager device according to various embodiments.

2 , the server device 100 and the manager device 200 may include an input/output unit 210 , a communication unit 220 , a memory 230 , and a processor 240 .

The input/output unit 210 may be various interfaces or ports for receiving user input or outputting information to the user. The input/output unit 210 may include an input module and an output module, and the input module receives user input from the user. User input can be implemented in various forms including key input, touch input, and audio input. As examples of input modules that can receive such user input, in addition to traditional keypads or keyboards, and mice, of course, they also include touch sensors that sense user touch, microphones that receive audio signals, cameras that recognize gestures by image recognition, proximity sensors that include at least one of an illumination sensor or an infrared sensor that senses the approach of a user, motion sensors that recognize user movements by means of an accelerometer or a gyroscope sensor, and various other forms of input mechanisms that sense or receive user input. The input module of the embodiments of the present invention may include at least one of the devices listed above. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that senses touch by attaching a touch panel or touch film on a display panel, an optical touch sensor that senses touch by optical means, etc. In addition, the input module can also be implemented in the form of an input interface (Universal Serial Bus (USB) port, second generation personal system (Personal System 2, PS/2) port, etc.) that connects to an external input device that receives user input instead of the device that senses user input itself. In addition, the output module can output various information. The output module may include a display for outputting images, a speaker for outputting sounds, a tactile device for generating vibrations, and at least one of various output mechanisms in addition thereto. In addition, the output module may also be implemented in the form of an output interface of a port type connected to the above-mentioned single output mechanism.

For example, the output module in the form of a display can display text, still images, and videos. Displays include liquid crystal displays (LCD), light emitting diode (LED), organic light emitting diode (OLED), flat panel displays (FPD), transparent displays, curved displays, flexible displays, three-dimensional displays (3D), holographic displays, projectors, and at least one of various devices that can implement image output functions. Such a display can also be in the form of a touch display that is integrally formed with a touch sensor of the input module.

The communication unit 220 can communicate with other devices. Therefore, the server device 100 and the manager device 200 can send and receive information with other devices through the communication unit. For example, the server device 100 and the manager device 200 can use the communication unit to communicate between signals or communicate with other devices.

Here, communication, i.e., the sending and receiving of data, can be realized by wired or wireless. For this purpose, the communication unit may include a wired communication module connected to the Internet via a LAN (Local Area Network), a mobile communication module connected to a mobile communication network via a mobile communication base station to send and receive data, a short-range communication module using a communication method such as WLAN (Wireless Local Area Network) series of wireless fidelity (Wi-Fi) or a communication method such as WPAN (Wireless Personal Area Network) series of Bluetooth and Zigbee, a satellite communication module using GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), or a combination thereof.

The memory 230 can store various information. The memory 230 can store data temporarily or semi-permanently. For example, the memory 230 of the server device 100 can store an operating system (OS) for driving the server device 100, data for hosting a website, or a program for generating braille and data related to an application (e.g., a website application). In addition, the memory can store the module in a computer-coded form as described above.

Examples of the memory 230 include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), etc. Such a memory can be provided in a built-in type or a removable type.

The processor 240 controls the overall operation of the server device 100 and the manager device 200. To this end, the processor 240 can perform calculations and processing of various information and control the operation of the components of the server device 100. For example, the processor 240 can execute programs and applications for implementing cache updates. The processor 240 can be implemented as a computer or a similar device based on hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented in the form of a circuit that processes electrical signals to implement control functions, and in terms of software, it can be implemented in the form of a program that drives the hardware processor 240. On the other hand, in the case where no particular mention is made in the following description, the actions of the server device 100 and the manager device 200 can be interpreted as being performed under the control of the processor 240. That is, in the case of executing the module implemented in the above-mentioned cache update implementation system, the module can be interpreted as controlling the processor 240 in such a manner that the server device 100 and the manager device 200 perform the following actions.

In short, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software or a combination thereof.

When implemented by hardware, the methods of various embodiments can be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

When implemented by firmware or software, the methods of various embodiments can be implemented in the form of modules, processes or functions that implement the functions or actions described below. For example, the software code can be stored in a memory and driven by a processor. The memory can be located inside or outside the processor and can send and receive data with the processor through various well-known mechanisms.

The following describes various embodiments in more detail based on the above-mentioned technical ideas. For the various embodiments described below, the contents described previously can be applied. For example, actions, functions, terms, etc. that are not defined in the various embodiments described below can be implemented and described based on the contents described previously.

In the following description, various embodiments are described based on the premise that the server device 100 processes the cache update execution action. According to various embodiments, the manager device 200 can send and receive various information related to the cache update execution action of the server device 100 with the server device 100.

FIG. 3 is a diagram showing the operation method of the server device 100 for performing cache update according to various embodiments.

According to FIG. 3 , the server device 100 performs an update on the cache. As an action for implementing the cache update, the following can be implemented: obtaining information of the update end setting time point set by the user in order to update the cache (301); confirming the time required for the cache update (303); determining the update start setting time point for the cache based on the update end setting time point and the update required time (305); and performing the first update on the cache based on the update start setting time point (307).

According to FIG. 3 , the action of updating the cache by the server device 100 may be to update the cache bound to the storage storing various data to be processed in the service provided by the server device 100. In this case, the above service may be a service in which a plurality of users utilizing the service can order and purchase a plurality of items sold in the service. The plurality of items sold in the service are not limited to the types or categories of items, etc., and may include various types or categories of items registered by the seller for the purpose of selling the items.

The cache receives data from the storage and stores it. If the server device 100 or other devices confirms the call data, the stored data is transmitted to the above-mentioned device. The cache can be set as follows: every time the time point corresponding to the fixed update cycle, the data can be received from the storage and updated. Different from the time point corresponding to the preset update cycle, the data is re-received from the storage and updated at the time point corresponding to the setting of the administrator or user as in the present invention.

According to various embodiments, in action 301, the server device 100 may obtain information of an update end setting time point set by the user in order to update the cache.

For example, in action 301, the user who sets the update end setting time point may be the administrator or user corresponding to the administrator device 200, and the above-mentioned update end setting time point may be a user setting update end default time point for a user setting update that is set by the user or separately, and the user setting update is different from the update that has been set to the cache or the update managed in the data processing system including the cache. Therefore, the action 301 of the server device 100 may be the following action: the server device 100 obtains the information of the update end default time point set by the user from the administrator device 200. In addition, according to action 307, the first update of the cache implemented by the server device 100 may be the update set by the user.

For example, the update end setting time point in action 301 is the time point when the user wants to end the cache update. When the server device 100 obtains the normal required time required for updating the cache, the server device 100 can manage the update end setting time point in the following manner: start updating the cache at a time point before the normal required time required for the above-mentioned update, and end the update at the update end setting time point.

For example, in the case where the update of the cache is terminated at the update end setting time in action 301, the data stored in the cache may be different before/after the update end setting time, and the data confirmed in the cache may be different depending on whether the data confirmation request for the cache is received before the update end setting time or after the update end setting time. In this regard, the server device 100 may perform an action of confirming the data by comparing the time point of receiving the data confirmation request with the update end setting time as shown in FIG. 4.

FIG. 4 is a diagram showing an operation method of confirming data by comparing the time when the server device 100 receives a data confirmation request with the update completion setting time according to various embodiments.

In FIG4 , the server device 100 may receive a specific data confirmation request for the cache (401). At this time, the specific data confirmation request as described above may be a request obtained by a user, administrator, and/or other data to confirm the existence of data stored in the storage. When the data stored in the storage is also stored in the cache, it may also be a request to confirm the above data in the cache.

When receiving a specific data confirmation request for the cache, the server device 100 can confirm the time point when the above-mentioned specific data confirmation request is received (403), and can compare the time point when the above-mentioned specific data confirmation request is received with the above-mentioned update end setting time point set by the user to confirm the data corresponding to the above-mentioned specific data confirmation request (405).

In summary, when the server device 100 receives a specific data confirmation request for the cache, the server device 100 can be configured as follows: it can confirm the time when the above-mentioned specific data confirmation request is received, and compare the time when the above-mentioned specific data confirmation request is received with the above-mentioned update end setting time to confirm the data corresponding to the above-mentioned specific data confirmation request.

When the time point of receiving the above-mentioned specific data confirmation request is before the above-mentioned update end setting time point, the server device 100 can be configured as follows: it can be determined that a data confirmation request is received for the cache before the update, and the previous data stored in the cache before the update that ends at the above-mentioned update end setting time point is confirmed in response to the above-mentioned specific data confirmation request.

On the contrary, when the time point of receiving the above-mentioned specific data confirmation request is after the above-mentioned update end setting time point, the server device 100 can be configured as follows: it is determined that a data confirmation request is received for the updated cache, and corresponding to the above-mentioned specific data confirmation request, the updated data stored in the cache after the update is completed at the above-mentioned update end setting time point is confirmed.

According to various embodiments, in action 303, the server device 100 may determine the time required to update the cache.

For example, according to action 303, the time required for updating the cache confirmed by the server device 100 can be obtained based on the time generally required for updating the cache. As one example, the time required for updating can be obtained as a value corresponding to the time required for updating the cache last time. As another example, the time required for updating can be obtained as a value corresponding to the average time required for multiple updates, and the average time required corresponds to the update history that has been performed on the cache.

According to various embodiments, in action 305, the server device 100 may determine an update start setting time for caching based on the update end setting time and the time required for the update.

For example, in action 305, the update start setting time point determined by the server device 100 for caching may be a time point before the update end setting time point obtained by the server device 100 according to action 301 and before the update required time confirmed by the server device 100 according to action 303. That is, when the server device 100 starts the first update according to the update start setting time point determined by action 305, the first update requires a time of the update required time, and thus the first update may be terminated at the update end setting time point.

For example, the first update managed in such a manner as to end at the update end setting time point can be triggered by a data confirmation request received for the cache after the update start setting time point determined by the server device 100 according to action 305. That is, if there is a data confirmation request received for the cache, it can be triggered in such a manner as to start the first update set by the user for the cache. In addition, considering that it takes time to receive the data confirmation request for triggering the first update, it is also possible to manage and set in such a manner that the first update ends within a fixed time period including the update end setting time point.

For example, the first update of the cache setting by the user can be triggered by the first data confirmation request received for the cache after the update start setting time. That is, for the cache, multiple data confirmation requests can be received, but the update of the cache can be set as follows: it starts with the first data confirmation request received for the cache after the update start setting time. In order to perform the above setting, the server device 100 can also use flag information.

For example, the server device 100 sets a flag information for confirming whether to update the cache. If the cache receives a data confirmation request for the first time after the update start setting time, the flag information value can be set to ''1'' to indicate that the cache is currently updating. On the contrary, if the cache is not updated because the data confirmation request is not received, the server device 100 can set the flag information value to ''0'' to indicate that the cache is not currently updating. When the value of the flag information is set to ''1'' according to the method described above, the server device 100 can be set in the following manner: after the initial data confirmation request for the cache after the update start setting time point, the cache update is not triggered by further confirming other data received by the cache.

For example, if no data confirmation request is received for the cache after the update start setting time determined by the server device 100 according to action 305, the first update corresponding to the user setting update may not be triggered. In this case, the cache will not be updated by the first update corresponding to the user setting update, but may be updated by the cache default update or the update managed in the data processing system.

According to various embodiments, in action 307, the server device 100 may perform a first update on the cache based on the update start setting time.

For example, when the server device 100 performs the first update on the cache according to action 307, the various embodiments described in actions 301 to 305 can be applied.

On the other hand, when the server device 100 performs the first update according to action 307, the server device 100 can also perform the following actions as shown in Figure 5: the first update expires and the subsequent cache can be updated by re-updating, setting the cache expiration default time corresponding to the first update and re-managing the cache update.

FIG. 5 is a diagram showing an operation method of managing cache by setting a preset cache expiration time in the server device 100 according to various embodiments.

In FIG. 5 , the server device 100 can confirm the aspect set in the following manner: at the update end setting time point corresponding to the action 301, the first update corresponding to the action 307 is executed (501). The server device 100 that confirms the aspect set in the manner of executing the first update needs to manage in a manner of setting the effective period of the first update and executing a new update to the subsequent cache, so the cache expiration preset time point (503) corresponding to the first update can be set after the update end setting time point. After setting the cache expiration preset time point, the effective period of the first update can be confirmed to the cache expiration preset time point, and the server device 100 can manage in the following manner: setting in a manner of executing a new update to the cache after the cache expiration preset time point (505) and executing the first update, and re-updating the cache after a period of time.

For example, the cache expiration preset time point set by the server device 100 in accordance with the action 503 in response to the first update can be set as follows: a fixed time interval is provided from the update end setting time point managed in a manner of ending the first update; in this case, the fixed time interval can be a time interval set by the administrator or user corresponding to the administrator device 200. That is, the administrator or user who sets the update end setting time point managed in a manner of ending the first update can set the cache expiration preset time point as follows: a new update can be implemented after a fixed time interval has passed since the end of the first update. As an example, the cache expiration preset time point can be set as follows: a time interval of 1 minute, 2 minutes, 3 minutes, ..., etc. is provided from the update end setting time point. As another example, the cache expiration preset time point can also be set in the following manner: the self-update end setting time point has a time interval corresponding to the current time point to the update end setting time point.

For example, according to action 503, the cache expiration preset time point set by the server device 100 in response to the first update can be set as follows: there is an arbitrary time interval from the update end setting time point managed in a manner of terminating the first update; in this case, the arbitrary time interval can be a time interval randomly determined based on a random function. That is, the administrator or user who sets the update end setting time point managed in a manner of terminating the first update can use the cache expiration preset time point as follows: after the first update is completed, a new update is performed after the arbitrarily set time interval. When the cache expiration preset time point is set in a manner that has an arbitrary time interval from the update end setting time point, the following problems may occur: the time interval set between the update end setting time point and the cache expiration preset time point is set too short and the cache is repeatedly updated unnecessarily; or the time interval set between the update end setting time point and the cache expiration preset time point is set too long and the update is not performed in time. To this end, the server device 100 can also be set in the following manner: the minimum time interval value and the maximum time interval value that can set the time interval between the update end setting time point and the cache expiration preset time point are set, thereby determining an arbitrary time interval corresponding to the random function between the minimum time interval value and the maximum time interval value.

For example, the time interval between the update end setting time point and the cache expiration preset time point can also be set based on the number of data requests confirmed for the cache. That is, if the number of data requests confirmed for the cache is large during the time interval between the update end setting time point and the cache expiration preset time point, it will be more appropriate to update the cache after the data confirmation corresponding to the data request is completed. Therefore, the time interval between the update end setting time point and the cache expiration preset time point can also be set according to the number of data requests confirmed for the cache. As an example, it can be set as follows: whenever the number of data requests increases at a fixed interval, the above time interval also increases at a fixed interval. For example, if the number of data requests confirmed by the cache is N, the above time interval is set to 1 minute. If the number of data requests confirmed by the cache is 2N, the above time interval is set to 2 minutes, and so on.

For example, the time interval between the update end setting time point and the cache expiration preset time point may be set in consideration of the characteristics of the data stored in the cache. When the data stored in the storage device associated with the cache is determined to be data that needs to be updated in real time and the cache is managed in a manner to store the data as described above, the time interval between the update end setting time point and the cache expiration preset time point may be set shorter to update the cache more frequently to store more real-time data. On the contrary, when the data stored in the storage associated with the cache is data that does not need to be updated in real time and the cache is managed in a manner to store the data as described above, the time interval between the update end setting time point and the cache expiration preset time point can be set longer to reduce the load caused by the cache update.

For example, in the case of managing a second update different from the previous first update after the cache expiration preset time, the second update described above can be triggered by a data confirmation request received from the cache after the cache expiration preset time. If there is a data confirmation request received from the cache after the cache expiration preset time, the server device 100 can execute the second update. At this time, similar to the first update described above, the second update can be triggered by a data confirmation request received from the cache for the first time after the cache expiration preset time. That is, a plurality of data confirmation requests may be received for the cache, but the second update of the cache is configured to start with the data confirmation request first received for the cache after the preset cache expiration time, so that the server device 100 may perform the second update based on the data confirmation request first received for the cache after the preset cache expiration time.

For example, the server device 100 may consider that the cache expiration preset time point is the time point at which the first update corresponding to the user setting update set by the user is effective, and may be set in the following manner: for the second update executed after the cache expiration preset time point as described above, even if there is a data confirmation request for the cache, data confirmation is interrupted until the second update is completed. That is, in the case where the second update is performed after the cache expiration preset time point when the data confirmation request is received for the first time, the server device 100 can be set in the following manner: data confirmation corresponding to other data confirmation requests received for the cache is interrupted until the second update is completed.

Alternatively, the server device 100 can also be configured to conditionally implement the interruption of the data confirmation as described above. That is, the server device 100 can be configured in the following manner: when there are many data confirmation requests or when it is predicted that the data confirmation processing will be delayed (latency), the data confirmation is interrupted. For example, if all situations in which the second update is implemented are set to interrupt data confirmation, data confirmation will be unnecessary. Therefore, the server device 100 can be set as follows: when the second update is performed by receiving the first data confirmation request after the preset cache expiration time, if the number of other data confirmation requests received for the cache within a fixed time after the above-mentioned first data confirmation request is greater than a critical number, the data confirmation corresponding to the other data confirmation requests received for the cache is interrupted until the second update is completed.

The action of the server device 100 updating the cache according to FIGS. 3 to 5 can be represented as shown in FIG. 6 .

FIG. 6 is a diagram showing the implementation of cache update according to the present invention.

In 601, the server device 100 may determine an update start setting time (start refresh) of the update required time required for the last update of the cache or the normal update required time (last execution time) confirmed as required for updating the cache based on the last update history of the cache, in order to manage in a manner that the update is terminated within a time period (refreshed range) including the update end setting time (user setting) of the user setting. That is, if a data confirmation request for the cache is received after the update start setting time (start refresh), the update of the user setting may be started for the cache, and the update of the user setting may be terminated within a time period (refreshed range) including the update end setting time (user setting) of the user setting.

Furthermore, in order to set the effective period of the update of the user setting as described above and manage the cache in a manner that allows new updates to be implemented, the server device 100 can also set a cache expiration preset time (redis cache expire) as shown in 603. If a data confirmation request for the cache is received after the cache expiration preset time, the cache can be updated again. In 603, it can be confirmed that the cache expiration preset time (redis cache expire) is set 3 minutes after the update end setting time (user setting).

It should be understood that in the process of implementing the operation method of FIG. 3 to FIG. 6 , the information provided by the server device 100 can be provided in combination in various forms.

The embodiments of the present invention disclosed in this specification and drawings are only provided to easily explain the technical content of the present invention and to help understand the present invention, and are not intended to limit the scope of the present invention. That is, those with common sense in the technical field to which the present invention belongs should understand that other variations based on the technical ideas of the present invention can be implemented. In addition, the above-mentioned embodiments can be combined with each other as needed for application. For example, all embodiments of the present invention can be combined with a part of each other and implemented by a system.

Furthermore, the methods corresponding to the system of the present invention can be implemented in the form of program commands that can be executed by various computer mechanisms and recorded in a computer-readable medium.

As described above, in certain aspects, various embodiments of the present invention may be implemented in a computer readable recording medium by computer readable code. A computer readable recording medium is any data storage device that can store data that can be read by a computer system. Examples of computer readable recording media may include read only memory (ROM), random access memory (RAM), compact disk-read only memory (CD-ROM), magnetic tape, floppy disk, optical data storage device, and carrier wave (data transmission via the Internet, etc.). The computer-readable recording medium can also be distributed through a computer system connected by a network, so that the computer-readable code is stored and executed in a distributed manner. In addition, the functional programs, codes and code segments used to implement various embodiments of the present invention can be easily explained by a skilled programmer in the field of application of the present invention.

Furthermore, it is known that the devices and methods of various embodiments of the present invention can be implemented as hardware, software, or a combination of hardware and software. Such software can be stored in a volatile or non-volatile storage device such as a ROM, or a memory such as a RAM, a memory chip, a device or an integrated circuit, or a storage medium such as a compact disk (CD), a DVD (Digital Versatile Disc), a disk or a tape that can be recorded optically or magnetically and can be read by a machine (e.g., a computer), regardless of whether it is erasable or re-recordable. It can be known that the methods of various embodiments of the present invention can be implemented by a computer including a control unit and a memory or a vehicle including the memory or computer as described above. Such a memory is an example of a storage medium that includes a program that includes commands for implementing the embodiments of the present invention or can be read by a machine suitable for storing programs.

Therefore, the present invention includes a coded program for realizing the device or method described in the invention application scope of this specification, and a storage medium readable by a machine (computer, etc.) storing such a program. In addition, such a program can be electronically transferred through any medium such as a communication signal transmitted by wired or wireless connection, and the present invention appropriately includes its equivalent content.

The above description is made with reference to the embodiments of the present invention, but the embodiments of the present invention disclosed in this specification and drawings are only specific examples provided to easily explain the technical content of the present invention and to help understand the present invention, and are not intended to limit the scope of the present invention. In addition, it can be understood that the embodiments of the present invention described above are only examples, and those with common sense in the field can realize various variations and equivalent embodiments based on them. Therefore, the true technical protection scope of the present invention should be defined according to the following invention patent application scope.

100: Server device 200: Manager device 210: Input/output unit 220: Communication unit 230: Memory 240: Processor 301: Action 303: Action 305: Action 307: Action 401: Action 403: Action 405: Action 501: Action 503: Action 505: Action

FIG. 1 is a diagram of a cache update implementation system for illustrating an operation method of an electronic device for implementing cache update in various embodiments. FIG. 2 is a diagram showing the configuration of a server device and a manager device in various embodiments. FIG. 3 is a diagram showing an operation method of a server device 100 for implementing cache update in various embodiments. FIG. 4 is a diagram showing an operation method of the server device 100 in various embodiments for confirming data by comparing the time point of receiving a data confirmation request with the update end setting time point. FIG. 5 is a diagram showing an operation method of the server device 100 in various embodiments for managing the cache by setting a cache expiration preset time point. FIG. 6 is a diagram showing a situation of implementing cache update of the present invention.

301:Action

303:Action

305:Action

307:Action

Claims (11)

A cache update implementation method, which is an electronic device implementing cache updates, comprising: Based on the update start setting time for the cache confirmed by the update end setting time and the update required time, implement the first update of the cache; and Based on the cache expiration preset time set according to a specific time interval after the update end setting time, implement a new update to the cache after the cache expiration preset time, Wherein, the specific time interval is set to one of the values of the time interval confirmed based on a random function, the time interval confirmed based on the number of data requests identified for the cache, and the time interval confirmed based on the data stored in the cache that needs to be updated in real time. A cache update implementation method as claimed in claim 1, wherein the time required for the update corresponds to an average time required for multiple updates, and the average time required corresponds to an update history that has been performed on the cache. A cache update implementation method as in claim 1, wherein the first update is triggered based on a data confirmation request received from the cache after the update start setting time point, and the first update is set to end within a fixed time period including the update end setting time point. The cache update implementation method of claim 3 further includes steps set in the following manner: Based on the first data confirmation request for the cache that is first received after the update start setting time point, the first update is triggered. The cache update implementation method of claim 4 further includes: Setting flag information for confirming whether to update the cache; and Based on the aspect of receiving the first data confirmation request, setting the value of the flag information. The cache update implementation method of request item 5 is set in the following manner: based on the above value set in the above flag information, the update of the above cache is not triggered by other data confirmation requests received by the above cache after the above first data confirmation request. In the cache update implementation method of request item 3, if no data confirmation request for the cache is received after the update start setting time, the first update is not triggered. The cache update implementation method of request item 1 further includes: Based on the second data confirmation request first received for the cache after the preset expiration time of the cache, the step of implementing the second update of the cache. The cache update implementation method of claim 8 further includes steps configured as follows: Based on the reception of the second data confirmation request, the data confirmation corresponding to the data confirmation request received for the cache is interrupted until the second update is completed. The cache update implementation method of claim 9 further includes steps set as follows: When the second data confirmation request is received and the number of other data confirmation requests received for the cache within a fixed time after the second data confirmation request is greater than a critical number, the data confirmation corresponding to the data confirmation request received for the cache is interrupted until the second update is completed. An electronic device that performs updates on a cache, comprising: a processor; and one or more memories storing one or more instructions; when executing the one or more instructions, controlling the processor to execute: based on the update start setting time for the cache confirmed by the update end setting time and the update required time, performing the first update on the cache; and based on the cache expiration preset time set according to a specific time interval after the update end setting time, performing a new update on the cache after the cache expiration preset time, The specific time interval is set to be one of a time interval value confirmed based on a random function, a time interval value confirmed based on the number of data requests identified for the cache, and a time interval value confirmed based on data stored in the cache that needs to be updated in real time.