Electronic device, system, and method for controlling electronic device

Abstract

This electronic device comprises: a communication device capable of communicating with a server device that provides data; a storage device; and a control device. The control device: uses the communication device to periodically access the server device to check if new data is being provided; determines, if new data is being provided, whether the new data should be downloaded from the server device or the download should be postponed, on the basis of a predetermined probability; and stores the new data downloaded from the server device in the storage device.

Description

[Technical Field]

[0001] The present disclosure relates to an electronic device, a system, and a method for controlling an electronic device. [Background technology]

[0002] In a system including a server device and multiple client devices connected to each other via a communication line, data may be periodically downloaded and / or uploaded. When the size of the files to be downloaded or uploaded is very large, or when there are many client devices, the server device and the communication line may be heavily loaded. Generally, the server device controls each client device so as to distribute the downloads or uploads of each client device over time, thereby alleviating the concentration of load on the server device and the communication line.

[0003] For example, Patent Document 1 discloses an automatic data file collection system that controls the transmission of data files stored in a client device to a file collection server based on a file collection schedule created by the file collection server. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-275846 Summary of the Invention

[0005] In cases where there are a large number of client devices, such as when the server device cannot control each client device or when the client devices cannot cooperate with each other, it is necessary to alleviate the load concentration on the server device and communication lines by having the client devices operate alone.

[0006] For example, if a server device periodically provides data for each client device, it is possible to configure each client device to access the server device on a predetermined day of the week in order to distribute access from the client devices over time. However, if the client device is a personal computer used in a company office, for example, the client device is activated only on business days and not on holidays. Therefore, the client device accesses the server device only on business days to check for new data to download, and not on holidays. In this case, if the client device is not activated on the day of the week on which it is configured to access the server device due to a long weekend or other reason, each client device will access the server device on the first business day after the long weekend, which could result in a concentration of data downloads. Therefore, when each client device downloads data from the server device, it is necessary to alleviate the concentration of load on the server device and communication lines caused by public holidays and other reasons.

[0007] The present disclosure provides an electronic device that is a client device capable of communicating with a server device, and that can download data from the server device while mitigating the load on the server device and communication lines caused by holidays, weekends, etc. The present disclosure also provides a system including at least one such electronic device and the server device. The present disclosure also provides a method for controlling such an electronic device.

[0008] According to one aspect of the present disclosure, an electronic device includes a communication device, a storage device, and a control device. The communication device is communicatively connected to a server device that provides data. The control device periodically accesses the server device using the communication device to check whether new data is available. If new data is available, the control device determines, based on a predetermined probability, whether to download the new data from the server device or postpone the download. The control device stores the new data downloaded from the server device in the storage device.

[0009] According to an electronic device according to an aspect of the present disclosure, it is possible to download data from a server device while mitigating the concentration of load on the server device and communication lines caused by public holidays and other days off. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a schematic diagram showing the configuration of a system including a server device 1 and an electronic device 2 according to an embodiment. [Figure 2] 2 is a block diagram showing the configuration of a server device 1 in FIG. 1. FIG. [Figure 3] 2 is a block diagram showing the configuration of the electronic device 2 of FIG. 1. FIG. [Figure 4] 4 is a first part of a flowchart showing an update management process executed by the control device 21 of the electronic device 2 of FIG. 3. [Figure 5] 4 is a second part of a flowchart showing the update management process executed by the control device 21 of the electronic device 2 of FIG. 3. [Figure 6] FIG. 2 is a diagram showing an example of access from each electronic device 2 to a server device 1 in a system according to a first comparative example. [Figure 7] FIG. 10 is a diagram showing an example of access from each electronic device 2 to a server device 1 in a system according to a second comparative example. [Figure 8] 1 is a diagram showing an example of access from each electronic device 2 to a server device 1 and download of data in the system according to the embodiment. FIG. [Figure 9] 10 is a graph showing an example of a change in the number of downloads over time in the system according to the embodiment. [Figure 10] 10 is a graph showing another example of the change over time in the number of downloads in the system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, more detailed description than necessary may be omitted. For example, detailed description of well-known matters or redundant description of substantially identical configurations may be omitted. This is to avoid unnecessary redundancy in the following description and to facilitate understanding by those skilled in the art.

[0012] The inventors provide the accompanying drawings and the following description to enable those skilled in the art to fully understand the present disclosure, and do not intend for them to limit the subject matter described in the claims.

[0013] [Embodiment] [Configuration of the embodiment] 1 is a schematic diagram showing the configuration of a system including a server device 1 and an electronic device 2 according to an embodiment. The system in FIG. 1 includes the server device 1 and electronic devices 2-1 to 2-5 connected to each other via a communication line 3.

[0014] In this specification, the electronic devices 2-1 to 2-5 are also collectively referred to as "electronic device 2."

[0015] The server device 1 periodically provides data for each electronic device 2. The data for each electronic device 2 includes, for example, an update program for an application program installed in the electronic device 2. The data for each electronic device 2 may also include, for example, video data, audio data, text data, etc. The server device 1 includes, for example, a general-purpose computer. In this specification, as an example, a case will be described in which the server device 1 periodically provides new data, i.e., update data, for each electronic device 2.

[0016] Each electronic device 2 accesses the server device 1 via the communication line 3 and downloads update data from the server device 1. Each electronic device 2 includes, for example, a personal computer or a mobile phone.

[0017] The communication line 3 includes a wired or wireless network, for example, the Internet or a mobile phone network.

[0018] FIG. 2 is a block diagram showing the configuration of the server device 1 of FIG. 1. The server device 1 includes a bus 10, a control device 11, a memory 12, a storage device 13, and a communication device 14. The control device 11 controls the overall operation of the server device 1 and, in response to a request from each electronic device 2, provides update data 13a (described later) stored in the storage device 13 to the electronic device 2. The control device 11 includes, for example, a CPU. The memory 12 temporarily stores programs and data necessary for the operation of the server device 1. The data necessary for the operation of the server device 1 includes, for example, an update management file 12a indicating the file name, timestamp, file size, etc. of the update data 13a stored in the storage device 13. The storage device 13 is a non-volatile storage medium that stores programs necessary for the operation of the server device 1 and also stores the update data 13a for each electronic device 2. The communication device 14 is communicably connected to each electronic device 2 via a communication line 3. The control device 11, the memory 12, the storage device 13, and the communication device 14 are connected to each other via a bus 10.

[0019] FIG. 3 is a block diagram showing the configuration of the electronic device 2 in FIG. 1. The electronic device 2 includes a bus 20, a control device 21, a memory 22, a storage device 23, a communication device 24, a display device 25, and an input device 26. The control device 21 controls the overall operation of the electronic device 2. The memory 22 temporarily stores programs and data necessary for the operation of the server device 1. The storage device 23 is a non-volatile storage medium that stores programs necessary for the operation of the electronic device 2 and also stores update data 13a downloaded from the server device 1. The communication device 24 is communicatively connected to the server device 1 via a communication line 3. The display device 25 displays the status of the electronic device 2. The input device 26 receives user input to control the operation of the electronic device 2. The input device 26 includes, for example, a keyboard and a pointing device. The control device 21, the memory 22, the storage device 23, the communication device 24, the display device 25, and the input device 26 are connected to each other via a bus 20.

[0020] The control device 21 periodically accesses the server device 1 using the communication device 24 to check whether new update data 13a has been provided. If new update data 13a has been provided, the control device 21 determines whether to download the new update data 13a from the server device 1 or postpone the download based on a predetermined probability Pr. The control device 21 stores the new update data 13a downloaded from the server device 1 in the storage device 23.

[0021] Furthermore, the control device 21 may access the server device 1 using the communication device 24, for example, every seven days, to check whether new update data 13a has been provided.

[0022] Furthermore, when new update data 13a is provided and the control device 21 has determined to postpone the download of the new update data 13a based on the probability Pr, the control device 21 may increase the probability Pr. After a predetermined period of time has elapsed, the control device 21 re-determines whether to download the new update data 13a from the server device 1 or postpone the download based on the increased probability Pr.

[0023] In addition, when new update data 13a is provided and the control device 21 decides to postpone the download of the new update data 13a based on the probability Pr, after a predetermined random time period has elapsed, the control device 21 may re-decide, based on the probability Pr, whether to download the new update data 13a from the server device 1 or postpone the download.

[0024] In addition, the control device 21 may periodically access the server device 1 using the communication device 24 after a predetermined random time has elapsed since the electronic device 2 was started to check whether new update data 13a has been provided.

[0025] [Operation of the embodiment] Fig. 4 is a first portion of a flowchart showing an update management process executed by the control device 21 of the electronic device 2 of Fig. 3. Fig. 5 is a second portion of a flowchart showing an update management process executed by the control device 21 of the electronic device 2 of Fig. 3.

[0026] After the electronic device 2 is started up, in step S1 of FIG. 4, the control device 21 automatically starts the update management service.

[0027] In step S2, the control device 21 reads the update check date and time Tu and the probability Pr from the storage device 23 (or another non-volatile storage medium). The update check date and time Tu indicates the date and time set to access the server device 1 to check whether new update data 13a to be downloaded is available. The probability Pr indicates the probability of determining to download the update data 13a in step S11 of FIG. 5, which will be described later. When performing the update management process for the first time after setting up the electronic device 2, the control device 21 may randomly set the initial value of the update check date and time Tu to, for example, any time between 0 and 6 days after the current time, or may set the initial value of the probability Pr to, for example, 1 / 8. On the other hand, when performing the update management process for the second or subsequent time, the control device 21 reads the update check date and time Tu and the probability Pr that were set the previous time the update management process was performed from the storage device 23 (or another non-volatile storage medium).

[0028] In step S3, the control device 21 waits for a random length of time, for example, any length of time between 0 and 300 minutes.

[0029] In step S4, the control device 21 determines whether the current time has passed the update confirmation date and time Tu, and if YES, the process proceeds to step S5, and if NO, the process proceeds to step S7.

[0030] In step S5, the control device 21 checks the update management file 12a of the server device 1 to see if new update data 13a has been provided. In step S6, the control device 21 determines whether the check of the update management file 12a was successful. If the result is YES, the control device 21 proceeds to step S10 in Fig. 5, and if the result is NO, the control device 21 proceeds to step S7 in Fig. 4.

[0031] In step S7, the control device 21 determines whether the determination in step S4 was NO three times in a row, and if YES, proceeds to step S8, and if NO, proceeds to step S9. In step S8, the control device 21 waits for 21 hours and then returns to step S4. In step S9, the control device 21 waits for 60 minutes and then returns to step S4.

[0032] In step S10 of FIG. 5, the control device 21 determines whether new update data 13a exists in the server device 1 based on the update management file 12a, and if YES, proceeds to step S11, and if NO, proceeds to step S18.

[0033] In step S11, the control device 21 determines whether to download the update data 13a from the server device 1 based on the probability Pr. If the determination is YES, the process proceeds to step S12, and if the determination is NO, the process proceeds to step S13. In other words, in step S11, the control device 21 determines, based on the probability Pr, whether to immediately download the update data 13a from the server device 1 or to postpone the download. Here, "immediately download" means to start downloading the update data 13a without any waiting time, or to start downloading the update data 13a within a predetermined time period, for example, within 24 hours.

[0034] In step S12, the control device 21 starts downloading the update data 13a.

[0035] In step S13, the control device 21 changes the probability Pr. For example, if the initial value of the probability Pr is 1 / 8, the control device 21 may change the probability Pr in the following order each time step S11 is determined to be NO: 1 / 8 → 1 / 7 → 1 / 6 → 1 / 5 → 1 / 4 → 1 / 3 → 1 / 2 → 1 / 1. In step S14, the control device 21 sets the next update check date and time Tu to a random time later, for example, one to seven days after the current time. After steps S13 and S14 are executed, the process returns to step S7 in FIG. 4.

[0036] In step S15, the control device 21 determines whether or not the download of the update data 13a has been successful, and if YES, the process proceeds to step S16, and if NO, the process proceeds to step S19.

[0037] In step S16, the control device 21 processes the downloaded update data 13a. If the update data 13a is an update program for an application program, the control device 21 applies the update program. If the update data 13a is video data, the control device 21 may display the video data on the display device 25 or store the video data in the storage device 23 for later display.

[0038] In step S17, the control device 21 sets the probability Pr to an initial value, for example, 1 / 8. In step S18, the control device 21 sets the next update check date and time Tu to 7 days later. After executing step S18, the process returns to step S7 in FIG. 4.

[0039] In step S19, the control device 21 sets the probability Pr to 1. As a result, it is determined that the next time step S11 is executed, the update data 13a will be downloaded from the server device 1. After step S19 is executed, the process returns to step S7 in FIG.

[0040] The control device 21 stores the probability Pr in the storage device 23 (or another non-volatile storage medium) each time it sets the probability Pr in steps S13, S17, and S19. Furthermore, the control device 21 stores the update check date and time Tu in the storage device 23 (or another non-volatile storage medium) each time it sets the update check date and time Tu in steps S14 and S18. As a result, if the update management process is interrupted due to, for example, shutting down the electronic device 2, the next time the electronic device 2 is started, the control device 21 can read the update check date and time Tu and the probability Pr that were set before the interruption from the storage device 23 (or another non-volatile storage medium) and resume the process.

[0041] 4 and 5 , each electronic device 2 periodically accesses the server device 1 to check whether new update data 13a is available. If new update data is available, each electronic device 2 determines, based on the probability Pr, whether to immediately download the new update data 13a from the server device 1 or postpone the download. When each electronic device 2 determines, based on the probability Pr, to postpone the download of the new update data 13a, the probability Pr is increased. After a predetermined random time period has elapsed, each electronic device 2 re-determines, based on the increased probability Pr, whether to immediately download the new update data 13a from the server device 1 or postpone the download. This allows each electronic device 2 to download the update data 13a from the server device 1 while mitigating the load on the server device 1 and the communication line 3 caused by holidays and other occasions, even when a large number of electronic devices 2 are present.

[0042] Next, an example of the operation of the system according to the embodiment will be described with reference to FIGS.

[0043] FIG. 6 is a diagram showing an example of access from each electronic device 2 to the server device 1 in a system according to a first comparative example. FIG. 6 shows a case where each electronic device 2 in FIG. 1 does not execute the update management process of FIGS. 4 and 5, and each electronic device 2 is set to access the server device 1 every five days in the initial state to check whether new update data is available to download. In FIG. 6 (and FIGS. 7 and 8), a black circle indicates that each electronic device 2 accesses the server device 1 to check whether new update data is available to download. Also, in FIG. 6 (and FIGS. 7 and 8), "S" indicates that access from the electronic device 2 to the server device 1 is skipped despite the update check date and time Tu being set for each electronic device 2. If the update check date and time Tu is set to Saturday or Sunday, the electronic device 2 is not started on a holiday and therefore does not access the server device 1, but accesses the server device 1 on the first business day following that, i.e., Monday. According to FIG. 6, in the initial state, access from the electronic device 2 to the server device 1 is set on Monday through Friday However, because Saturday and Sunday are holidays, as time passes, accesses from the electronic devices 2 to the server device 1 tend to be concentrated on Mondays.

[0044] FIG. 7 illustrates an example of access from each electronic device 2 to the server device 1 in a system according to a second comparative example. FIG. 7 illustrates a case in which each electronic device 2 in FIG. 1 does not execute the update management process of FIGS. 4 and 5 and is initially configured to access the server device 1 every seven days to check for new update data to download. When each electronic device 2 accesses the server device 1 every seven days, the update check date and time Tu is generally not set to a Saturday or Sunday. However, if there is a bias in the accesses from the electronic devices 2 to the server device 1 in the initial state, this bias will be maintained permanently. Furthermore, there is a possibility that the update check date and time Tu may be shifted due to public holidays or other holidays, resulting in a loss of uniformity in access from the electronic devices 2 to the server device 1.

[0045] FIG. 8 is a diagram showing an example of access from each electronic device 2 to the server device 1 and data download in the system according to the embodiment. FIG. 8 shows a case where each electronic device 2 in FIG. 1 executes the update management process of FIGS. 4 and 5, and is initially set to access the server device 1 every seven days to check whether new update data is available for download. FIG. 8 also shows a case where the server device 1 provides new update data 13a on Monday of the second week. In FIG. 8, "D" indicates that each electronic device 2 downloads update data 13a from the server device 1.

[0046] As shown in the first and second weeks of FIG. 8, each electronic device 2 periodically accesses the server device 1 to check whether new update data 13a has been provided.

[0047] 8, each electronic device 2 probabilistically determines whether to immediately download new update data 13a from the server device 1 or postpone the download. In the example of FIG. 8, the electronic device 2-1 immediately downloads new update data 13a from the server device 1 at the first update check date and time Tu after the update data 13a is provided. Meanwhile, the other electronic devices 2-2 to 2-5 download new update data 13a from the server device 1 at the second to fourth update check dates and times Tu after the update data 13a is provided.

[0048] 8, when the electronic devices 2-2 to 2-5 decide to postpone the download of new update data 13a, they re-decide, after a random time has elapsed, whether to immediately download the new update data 13a from the server device 1 or to postpone the download. In the example of FIG. 8, when the electronic devices 2-2 to 2-5 decide to postpone the download of new update data 13a, they set the next update check date and time Tu to be 1 to 5 days later.

[0049] Also, as shown in the third and fourth weeks of Figure 8, after downloading the update data 13a, each electronic device 2 periodically accesses the server device 1 to check whether new update data 13a has been provided.

[0050] If the cycle for each electronic device 2 to access the server device 1 is set to six days or less, there will be holidays within a week, so there is a risk that accesses from the electronic devices 2 to the server device 1 will be concentrated on Mondays, as in the case of Fig. 6. On the other hand, if the cycle for each electronic device 2 to access the server device 1 is set to eight days or more, the degree of distribution of access will be the same as when the access cycle is set to seven days.

[0051] If the server device 1 is simply accessed periodically to download the update data 13a, and if there is an initial bias in access from the electronic devices 2 to the server device 1, this bias will be maintained permanently. Furthermore, if the server device 1 is simply accessed periodically to download the update data 13a, the update confirmation date and time Tu may be shifted due to holidays or other holidays, which may disrupt the uniformity of access from the electronic devices 2 to the server device 1. In response to this, by probabilistically determining whether to immediately download new update data 13a or postpone the download, it is possible to constantly alleviate bias in access and reduce the likelihood of concentrating loads on the server device 1 and the communication line 3.

[0052] Next, the effects of the system according to the embodiment will be described with reference to Figures 9 and 10. Figures 9 and 10 show a case where one million electronic devices 2 download update data 13a from the server device 1. Figures 9 and 10 also show a case where the initial value of the probability Pr is set to 1 / 8, and the probability Pr is changed in the order 1 / 8 → 1 / 7 → ... → 1 / 2 → 1 / 1 each time it is decided to postpone the download of new update data 13a.

[0053] 9 is a graph showing an example of the change in the number of downloads over time in the system according to the embodiment. This graph shows a case in which the electronic devices 2 are activated only on weekdays, and not on Saturdays and Sundays. As can be seen from FIG. 9, update data 13a is not downloaded on Saturdays and Sundays, and as a result, the number of downloads increases on Mondays compared to Tuesdays through Fridays. However, the peak number of downloads is at most approximately 85,000 times per day, which is sufficiently low compared to the number of electronic devices 2, and it can be said that the concentration of load on the server device 1 and the communication line 3 is alleviated.

[0054] Fig. 10 is a graph showing another example of the change over time in the number of downloads in the system according to the embodiment. Fig. 10 shows a case where each electronic device 2 is started up on Saturday and Sunday. According to Fig. 10, the peak number of downloads is at most about 40,000 times per day, which means that the load concentration on the server device 1 and the communication line 3 is alleviated.

[0055] The length of time Td required for all electronic devices 2 to complete downloading of the update data 13a after the server device 1 starts providing the update data 13a is determined based on factors such as the performance of the server device 1, the capacity of the communication line 3, and the size of the update data. The initial value of the probability Pr is 1 / x (x is an integer). Each time a decision is made to postpone the download of new update data 13a, the probability Pr is changed in the following order: 1 / x → 1 / (x-1) → ... → 1 / 2 → 1 / 1. Each electronic device 2 accesses the server device 1 every y days to check whether new update data 13a is available. In this case, the length of time Td is given by Td = (x × y) + 1. By appropriately setting the parameters x and y, an appropriate length of time Td can be set based on the performance of the server device 1, the capacity of the communication line 3, the size of the update data, and the like.

[0056] According to the electronic device 2 of the embodiment, when it is determined to postpone the download of new update data 13a, after a predetermined random time has elapsed, it is determined again whether to immediately download the new update data 13a from the server device 1 or to postpone the download. Therefore, it is possible to alleviate the concentration of load on the server device 1 and the communication line 3, for example, on the first business day after a long holiday.

[0057] Furthermore, according to the electronic device 2 of the embodiment, by adjusting the initial value 1 / x of the probability Pr, it is possible to dynamically adjust the degree of distribution of access from the electronic devices 2 to the server device 1. The degree of distribution of access has a trade-off relationship with the length of time Td required for all the electronic devices 2 to complete downloading the update data 13a.

[0058] Furthermore, according to the electronic device 2 of the embodiment, the concentration of load on the server device 1 and the communication line 3 can be alleviated by operating only the electronic device 2, for example, by simply executing the update management processing program of Figures 4 and 5 in the electronic device 2.

[0059] Furthermore, the electronic device 2 according to the embodiment does not require information such as days of the week and holidays, and therefore does not require calendar data for each country or localization for each country.

[0060] [Effects of the embodiment] An electronic device 2 according to one embodiment of the present disclosure includes a communication device 24, a storage device 23, and a control device 21. The communication device 24 is communicatively connected to a server device 1 that provides data. The control device 21 periodically accesses the server device 1 using the communication device 24 to check whether new data has been provided. If new data has been provided, the control device 21 determines whether to download the new data from the server device 1 or postpone the download based on a predetermined probability Pr. The control device 21 stores the new data downloaded from the server device 1 in the storage device 23.

[0061] This allows each electronic device 2 to download update data 13a from the server device 1, even if there are a large number of electronic devices 2, by alleviating the concentration of load on the server device 1 and communication line 3 caused by public holidays and other days off.

[0062] In an electronic device 2 according to one embodiment of the present disclosure, the control device 21 may access the server device 1 using the communication device 24 every seven days to check whether new data has been provided.

[0063] This reduces the possibility that the update check date and time Tu will be set on a Saturday or Sunday, compared to when the server device 1 is accessed every six days or less.

[0064] In the electronic device 2 according to one embodiment of the present disclosure, when new data is provided and the control device 21 has determined to postpone the download of the new data based on the probability Pr, the control device 21 may increase the probability Pr. In this case, after a predetermined period of time has elapsed, the control device 21 re-determines whether to download the new data from the server device 1 or postpone the download based on the increased probability Pr.

[0065] As a result, the probability Pr finally becomes 1, and the electronic device 2 can download the update data.

[0066] In an electronic device 2 according to one embodiment of the present disclosure, when new data is provided and the control device 21 has decided to postpone the download of the new data based on the probability Pr, the control device 21 may, after a first random time period has elapsed, re-decide based on the probability Pr whether to download the new data from the server device 1 or postpone the download.

[0067] This makes it possible to reduce the concentration of load on the server device 1 and the communication line 3.

[0068] In an electronic device 2 according to one embodiment of the present disclosure, the control device 21 may periodically access the server device 1 using the communication device 24 after a second random time period has elapsed since the electronic device 2 was started to check whether new data has been provided.

[0069] This makes it possible to avoid a concentration of accesses to the server device 1 and downloads of update data 13a at, for example, 9:00 AM when startups of the electronic devices 2 are concentrated in a certain time zone.

[0070] A system according to one embodiment of the present disclosure includes at least one electronic device 2 and a server device 1 communicatively connected to each electronic device 2 and providing data.

[0071] This allows each electronic device 2 to download update data 13a from the server device 1, even if there are a large number of electronic devices 2, by alleviating the concentration of load on the server device 1 and communication line 3 caused by public holidays and other days off.

[0072] A control method for an electronic device 2 according to one embodiment of the present disclosure is a control method for an electronic device 2 capable of communicating with a server device 1 that provides data, and includes the following steps. The control method includes a step of periodically accessing the server device 1 to check whether new data has been provided. If new data has been provided, the control method includes a step of determining, based on a predetermined probability Pr, whether to download the new data from the server device 1 or postpone the download. The control method includes a step of storing the new data downloaded from the server device 1 in a storage device 23.

[0073] This allows each electronic device 2 to download update data 13a from the server device 1, even if there are a large number of electronic devices 2, by alleviating the concentration of load on the server device 1 and communication line 3 caused by public holidays and other days off.

[0074] [Other embodiments] As described above, the embodiments have been described as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these, and can be applied to embodiments in which appropriate modifications, substitutions, additions, omissions, etc. are made. Furthermore, it is also possible to combine the components described in the above embodiments to create new embodiments.

[0075] Therefore, other embodiments will be exemplified below.

[0076] The value of the probability Pr is not limited to being changed in the order of 1 / 8 → 1 / 7 → ... → 1 / 2 → 1 / 1, but may start from another initial value or may be changed to another value.

[0077] The server device 1 may dynamically obtain the number of electronic devices 2 and adjust the value of the probability Pr so that the number of downloads is equal to or less than a certain threshold. In this case, each electronic device 2 obtains the value of the probability Pr set by the server device 1 from the server device 1.

[0078] As described above, the embodiments have been described as examples of the technology in the present disclosure, and for that purpose, the accompanying drawings and detailed description have been provided.

[0079] Therefore, the components shown in the accompanying drawings and detailed description may include not only essential components for solving the problem, but also components that are not essential for solving the problem in order to illustrate the above technology. Therefore, the fact that these non-essential components are shown in the accompanying drawings or detailed description should not be interpreted as immediately indicating that these non-essential components are essential.

[0080] Furthermore, since the above-described embodiments are intended to illustrate the technology of the present disclosure, various modifications, substitutions, additions, omissions, etc. may be made within the scope of the claims or their equivalents. [Industrial Applicability]

[0081] The electronic device, system, and method for controlling an electronic device according to an aspect of the present disclosure are applicable to cases where a large number of client devices exist, for example, when a server device cannot control each client device to distribute traffic on a communication line, or when the client devices cannot cooperate with each other. The electronic device, which is a client device, can distribute traffic on a communication line. [Explanation of symbols]

[0082] 1. Server device 2,2-1~2-5 Electronic equipment 3. Communication lines 10 Bus 11 Control device 12 Memory 12a update management file 13 Storage device 13a update data 14. Communications equipment 20 Bus 21 Control device 22 Memory 23 Storage device 24 Communication equipment 25 Display device 26 Input Devices

Claims

1. a communication device capable of communicating with a server device that provides data; A storage device; a control device that periodically accesses the server device using the communication device to check whether new data is provided, and if the new data is provided, determines whether to download the new data from the server device or postpone the download based on a predetermined probability, and stores the new data downloaded from the server device in the storage device; The predetermined probability is set according to the size of the new data. electronic equipment.

2. the control device accesses the server device using the communication device every seven days to check whether new data has been provided; The electronic device of claim 1 .

3. When the new data is provided and the control device has determined to postpone the download of the new data based on the probability, the control device increases the probability, and after a predetermined time period has elapsed, the control device re-determines whether to download the new data from the server device or postpone the download based on the increased probability. The electronic device of claim 1 .

4. When the new data is provided and the control device has determined to postpone the download of the new data based on the probability, the control device re-determines, after a first random time period has elapsed, whether to download the new data from the server device or postpone the download based on the probability. An electronic device according to one of claims 1 to 3.

5. the control device periodically accesses the server device using the communication device to check whether new data has been provided after a second random time period has elapsed since the electronic device was started; An electronic device according to one of claims 1 to 3.

6. An electronic device according to any one of claims 1 to 3; a server device communicatively connected to the electronic device and providing data; system.

7. A method for controlling an electronic device capable of communicating with a server device that provides data, comprising: periodically accessing the server device to check whether new data is available; If the new data is provided, determining whether to download the new data from the server device or postpone the download based on a predetermined probability; storing the new data downloaded from the server device in a storage device; The predetermined probability is set according to the size of the new data. A method for controlling an electronic device.

Images