JP2013029874A - Electronic apparatus, control method of electronic apparatus, control program of electronic apparatus - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce server's load or reduce communication traffic volume between a plurality of clients (electronic apparatuses) and a server in, for example, a client and server type system.SOLUTION: An electronic apparatus according to an embodiment includes a first update reference unit for referring to a server for a first update of software used by the own apparatus. The electronic apparatus also includes a second update schedule reception unit for receiving a second update schedule of the software that is output from the server according to the reference of the first update of the software. The electronic apparatus further includes a second update reference unit for referring to the server for a second update of the software according to the received second update schedule of the software.

Description

  Embodiments described herein relate generally to an electronic device, an electronic device control method, and an electronic device control program.

In recent years, electronic devices (clients, terminals) and servers such as personal computers (PCs) have become widespread, and client-server systems are widely used.
In this client-server system, for example, updated software or the like is distributed from a server to a plurality of clients (electronic devices) connected to the server.

However, for example, when the number of clients (electronic devices) is too large, there is a possibility that a load may be generated on the server, which is a problem.
In addition, for example, due to the update of the software or the like, the amount of communication between the plurality of clients (electronic devices) and the server has increased, which has been a problem.
For this reason, for example, in a client-server system, reducing the burden on the server and reducing the amount of communication between a plurality of clients (electronic devices) and the server have been problems.

JP 2009-110138 A

  For example, in a client / server system, reducing the burden on the server and reducing the amount of communication between a plurality of clients (electronic devices) and the server have been problems.

The electronic device according to the embodiment includes a first update inquiry unit that inquires of the server about a first update of software used in the device.
A second update schedule receiving unit configured to receive a second update schedule of the software output from the server in response to the first update inquiry of the software;

  In addition, a second update inquiry unit that inquires the server for a second update of the software according to the received second update schedule of the software.

1 is a system configuration diagram showing an example of a configuration of a client / server system using an electronic apparatus (client) according to an embodiment. FIG. 3 is a diagram showing an example of the appearance of an electronic apparatus (client) according to the embodiment. FIG. 2 is an exemplary block diagram showing an example of the configuration of an electronic apparatus (client) according to the embodiment. FIG. 5 is a sequence diagram showing how the server and the electronic device (client) communicate according to the embodiment. The flowchart explaining operation | movement of the client server system concerning embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
FIG. 1 is a system configuration diagram illustrating an example of a configuration of a client / server system using an electronic apparatus (client) according to the embodiment.
In this embodiment, for example, as shown in FIG. 1, a plurality of electronic devices (clients) such as an electronic device (client) 31, an electronic device (client) 32, and an electronic device (client) 33 are connected to the server 20. And configure a client / server system.

Here, the client / server system will be described.
A client-server system is a computer network system that separates a client and a server.
The client / server system is a system in which roles are divided into a computer (server) that is in charge of a specific role and a computer (client) that is operated by a user, and these are connected to each other via a network. Generally, in this system, processing is performed in such a manner that a client sends a “request” to a server and the server returns a “response” thereto.

For example, the role of the server is a mail server, a Web server, an application server, a file server, a print server, or the like.
The plurality of electronic devices (clients) and the server 20 can perform communication such as polling, for example.
Polling is, for example, a method in which each communication partner or software asks each other party whether there is a transmission (or processing) request when a plurality of communication devices or software operate in cooperation.
In the case of software, for example, the main routine in the program calls each procedure in turn to check for a response, and if there is a response, performs some processing.
In the case of communication control, for example, one computer is the master (host) and the rest are slaves (terminals), and the master computer asks each slave computer whether there is a transmission request according to the specified order. To go.

  In this embodiment, for example, in the client / server system, the electronic device (client) 31 inquires of the server 20 about the first update of the software used in the own device (first update inquiry). ).

  Further, the second update schedule of the software output from the server 20 is received in response to the inquiry about the first update of the software (second update schedule reception).

  Further, the second update of the software is referred to the server 20 in accordance with the received second update schedule of the software (second update inquiry).

FIG. 2 is a diagram illustrating an example of an appearance of the electronic apparatus (client) according to the embodiment.
Here, the electronic device (client) 31 is realized as a notebook type personal computer (notebook PC or PC) 31, for example.
Note that this embodiment is not limited to a personal computer, and can also be applied to a TV, a mobile phone, a portable electronic device, and the like.
As shown in FIG. 1, the electronic device (client) 31 includes a computer (notebook PC) main body 11 and a video display unit 12. For example, an LCD (liquid crystal display) 17 is incorporated in the video display unit 12.

  The video display unit 12 is rotatable between a computer (notebook PC) main body 11 so as to be rotatable between an open position where the upper surface of the computer (notebook PC) main body 11 is exposed and a closed position covering the upper surface of the computer (notebook PC) main body 11. Is attached.

  The computer (notebook PC) main body 11 has a thin box-shaped housing, and on its upper surface, a keyboard 13, a power button 14 for powering on / off the electronic device (client) 31, and a touch pad. 16, speakers 18A, 18B and the like are arranged.

  In addition, a USB connector 19 for connecting a USB cable or USB device of USB (universal serial bus) 2.0 standard is provided on the right side of the computer (notebook PC) main body 11, for example.

  Furthermore, an external display connection terminal corresponding to, for example, a high-definition multimedia interface (HDMI) standard is provided on the back surface of the computer (notebook PC) main body 11 (not shown). This external display connection terminal is used to output a digital video signal to an external display.

FIG. 3 is a block diagram illustrating an example of the configuration of the electronic device (client) according to the embodiment.
As shown in FIG. 3, the electronic device (client) 31 includes a CPU (central processing unit) 101, a system memory 103, a south bridge 104, a GPU (Graphics Processing Unit) 105, a VRAM (video RAM: random access memory) 105A, Sound controller 106, BIOS-ROM (basic input / output system-read only memory) 107, LAN (local area network) controller 108, hard disk drive (HDD (storage device)) 109, optical disk drive (ODD) 110, USB controller 111A A card controller 111B, a card slot 111C, a wireless LAN controller 112, an embedded controller / keyboard controller (EC / KBC) 113, an EEPROM (electrically erasable programmable ROM) 114, and the like.

The CPU 101 is a processor that controls the operation of each unit in the electronic device (client) 31.
The CPU 101 executes the BIOS stored in the BIOS-ROM 107. The BIOS is a program for hardware control. The CPU 101 also includes a memory controller that controls access to the system memory 103. Also, for example, it has a function of executing communication with the GPU 105 via a PCI EXPRESS serial bus or the like.

The GPU 105 is a display controller that controls the LCD 17 used as a display monitor of the electronic apparatus (client) 31.
A display signal generated by the GPU 105 is sent to the LCD 17. The GPU 105 can also send a digital video signal to the external display 1 via the HDMI control circuit 3 and the HDMI terminal 2.

  The HDMI terminal 2 is the aforementioned external display connection terminal. The HDMI terminal 2 can send an uncompressed digital video signal and a digital audio signal to the external display 1 such as a television with a single cable. The HDMI control circuit 3 is an interface for sending a digital video signal to an external display 1 called an HDMI monitor via the HDMI terminal 2.

  The south bridge 104 controls each device on a peripheral component interconnect (PCI) bus and each device on a low pin count (LPC) bus. Further, the south bridge 104 includes an IDE (Integrated Drive Electronics) controller for controlling the HDD 109 and the ODD 110.

Further, the south bridge 104 has a function of executing communication with the sound controller 106.
The sound controller 106 is a sound source device, and outputs audio data to be reproduced to the speakers 18A and 18B or the HDMI control circuit 3. The LAN controller 108 is a wired communication device that executes IEEE 802.3 standard wired communication, for example, while the wireless LAN controller 112 is a wireless communication device that executes IEEE 802.11g standard wireless communication, for example. For example, the USB controller 111A performs communication with an external device that supports the USB 2.0 standard.

  For example, the USB controller 111A is used for receiving an image data file stored in a digital camera. The card controller 111 </ b> B executes data writing and reading with respect to a memory card such as an SD card inserted into a card slot provided in the computer (notebook PC) main body 11.

  The EC / KBC 113 is a one-chip microcomputer in which an embedded controller for power management and a keyboard controller for controlling the keyboard 13 and the touch pad 16 are integrated. The EC / KBC 113 has a function of turning on / off the electronic device (client) 31 in accordance with the operation of the power button 14 by the user.

The display control in this embodiment is performed, for example, by causing the CPU 101 to execute a program recorded in the system memory 103, the HDD 109, or the like.
FIG. 4 is a sequence diagram illustrating communication between the server and the electronic device (client) according to the embodiment.
Here, the communication between the server 20 and the electronic device (client) 31 will be described as an example.
In this embodiment, for example, the operator operates the server 20 to set the software update check interval and the time difference range as appropriate.
In addition, the electronic device (client) 31 includes an activation unit that activates the device itself, and makes an inquiry about the first update of the software at a random date and time within one month after the device itself is activated for the first time.

Here, an update confirmation check 41 is performed from the electronic device (client) 31 to the server 20.
The server 20 transmits to the electronic device (client) 31 update information 42 indicating that the first update of the software has been performed or that the update has not been performed.

  Further, the server 20 transmits the next update schedule information (second update information of the software) 43 after the first update of the software to the electronic device (client) 31.

  The server 20 receives the next update schedule information (second update information of the software), and the number of days / time specified by the next update schedule information (second update information of the software) elapses. The update confirmation check 44 is transmitted to the server 20 after the designated number of days / time has elapsed.

FIG. 5 is a flowchart for explaining the operation of the client / server system according to the embodiment.
Step S100 is a start step here. Then, it progresses to step S101.
Step S101 is a step in which, for example, an operator instructs to set a software update check interval and a time difference range in the server 20. Then, it progresses to step S102.

  Step S102 is a step of inquiring whether the software has been updated from the client (electronic device) 31 to the server 20 at a random date and time within one month after the electronic device (client) 31 is started for the first time (step S102). Update confirmation check, first software update inquiry). Then, it progresses to step S103.

  Step S <b> 103 is a step of transmitting software update information (first software update inquiry result) from the server 20 to the client (electronic device) 31. Then, it progresses to step S104.

  In step S104, for example, the server 20 sets the next software update date and time of the client (electronic device) 31 based on the setting of the server 20 by the operator in step S101 and the reception timing of the update confirmation check (step S102). It is. Then, it progresses to step S105.

  Step S105 is a step of transmitting information designating the next software update date / time from the server 20 to the client (electronic device) 31 (next update schedule information transmission). Then, it progresses to step S106.

  Step S106 is a step in which the CPU 101 of the client (electronic device) 31 determines whether or not the specified date and time (number of days / time) has elapsed. Information specifying the next software update date and time transmitted from the server 20 to the client (electronic device) 31 is stored in, for example, the storage device (HDD) 109 or the EC / KBC 113 shown in FIG. Be controlled. If it is determined that the specified date and time (number of days / time) has elapsed, the process proceeds to step S107 (Yes). If it is not determined that the specified date and time (number of days / time) has elapsed, the processing here is repeated (No).

  Step S107 is a step of confirming the presence or absence of the software update from the client (electronic device) 31 to the server 20 (update confirmation check, second software update inquiry). Then, it progresses to step S108.

Step S108 is an end step, and the process here ends.
That is, in this embodiment, in a client-server system that distributes software updates, for example, when the capability on the server 20 side is low, it is possible to cope with this environment.

  In this embodiment, for example, when the client (electronic device) 31 confirms the presence or absence of update software with respect to the server 20, information specifying the next update date is also sent from the server 20 to the client (electronic device). It returns to 31.

Further, the client (electronic device) 31 automatically accesses the server 20 at the next update date and confirms the presence or absence of update software.
In addition, the client (electronic device) 31 first confirms with the server 20 at random one time within one month.
Further, when access is made from the client (electronic device) 31 side, the server 20 side sets the next update interval set in advance by maintenance personnel and transmits it to the client (electronic device) 31. At this time, for example, the time and date are automatically shifted within a preset range so that accesses from each machine are not concentrated.

  It is also possible to manually perform an update check by operating the client (electronic device) 31 side. However, for example, the server 20 is accessed only once within 24 hours. After that, unless an update check is performed manually, the update interval returned from the server 20 is followed.

In other words, in this embodiment, the second update schedule of the software includes information designating the next update date and time after the first update of the software.
The inquiry for the first update of the software includes confirming whether the software has been updated.
Further, the client (electronic device) 31 according to this embodiment is not particularly illustrated, but for example, a time based on the second update schedule of the software by an application such as software stored in the storage unit (HDD). It has a detection part for detecting whether or not. Then, for example, when the time has elapsed, the second update of the software is inquired.

The received second update schedule of the software is stored in a storage unit such as the storage unit (HDD) 109 or the EC / KBC 113, for example.
In addition, the client (electronic device) 31 according to this embodiment includes, for example, an activation unit that activates its own device in the system memory 103 or the like. Then, for example, the first update of the software is inquired within one month after the device starts up for the first time.

In addition, the second update schedule of the software received by the client (electronic device) 31 according to this embodiment is set by the server 20, for example.
By configuring as described above, in this embodiment, in response to the inquiry of the first update of the software, the second update schedule of the software output from the server 20 is received. The server 20 is configured to inquire the second update of the software according to the received second update schedule of the software.

  For this reason, for example, it becomes possible to reduce unnecessary polling, so that it is possible to reduce the burden on the server 20 in the client-server type system. Moreover, it becomes possible to reduce the communication amount between a some client (electronic device) and a server. Further, as described above, by using a client / server system, for example, it is possible to reduce the mixing of computer viruses and the like.

  In addition to the above, as another embodiment, for example, a person in charge of this system that manages the server 20 has an update interval and a machine (client (electronic device)) in the server 20 based on the next system update plan. It is possible to configure so as to set a time range for performing the update check for each time.

Then, in the same manner as described above, the system of the software update check program corresponding to this system is started.
Then, for example, a random date and time within one month is generated at startup, and a timer is set. When this timer is woken up, the server 20 set in advance is accessed.
If the software update information is registered as described above, the server 20 returns the information to the client side (for example, the client (electronic device) 31).

  In addition, the server 20 generates a random date and time within a range that falls within a predetermined update check time range in the order of a preset update interval and a machine (client (electronic device)) that has been checked for update. The generated date and time information is transmitted to the client side.

  Then, the client (electronic device) 31 sets a timer based on the received “next update check date”. When this timer is woken up, the server 20 set in advance is accessed and the above process is repeated.

  In this embodiment, the user (user) operates the client (electronic device) 31 so that the update check can be manually operated as appropriate. Note that the server is accessed once a day, and if there is no manual operation thereafter, the update check may not be performed until the next update check interval returned from the server.

  Note that all the control processing procedures of the above-described embodiment can be executed by software. For this reason, it is possible to easily realize the same effect as that of the above-described embodiment only by installing and executing this program on a normal computer through a computer-readable storage medium storing the program for executing the control processing procedure. it can.

  Note that the above embodiment is not limited to the description itself, and in the implementation stage, the constituent elements can be variously modified and embodied without departing from the spirit of the invention.

Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment.
For example, some components may be deleted from all the components shown in the embodiment. Furthermore, you may combine suitably the component covering different embodiment.

  20 ... server, 31 ... client (electronic device), 32 ... client (electronic device), 33 ... client (electronic device).

Claims (9)

A first update inquiry unit for inquiring of the server about a first update of software used in the device;
A second update schedule receiving unit that receives a second update schedule of the software output from the server in response to a query of the first update of the software;
An electronic apparatus comprising: a second update inquiry unit that inquires of the server for a second update of the software according to the received second update schedule of the software.   The electronic device according to claim 1, wherein the second update schedule of the software includes information designating an update date and time next to the first update of the software.   The electronic device according to claim 1, wherein the inquiry for the first update of the software includes checking whether the software has been updated.   The electronic device according to claim 1, further comprising: a detection unit configured to detect whether a time based on a schedule of the second update of the software has elapsed, and inquiring a second update of the software when the time has elapsed. .   The electronic device of Claim 1 provided with the memory | storage part which memorize | stores the schedule of the said 2nd update of the said received said software.   The electronic device according to claim 1, further comprising an activation unit that activates the device itself, wherein the first update of the software is inquired within one month after the device is activated for the first time.   The electronic device according to claim 1, wherein the second update schedule of the received software is set by the server. Querying the server for a first update of the software used on the device;
Receiving a second update schedule of the software output from the server in response to a query of the first update of the software;
A method for controlling an electronic device, comprising: inquiring the server for a second update of the software according to the received schedule of the second update of the software. Querying the server for a first update of the software used on the device;
Receiving a second update schedule of the software output from the server in response to a query of the first update of the software;
A control program for an electronic device, comprising: inquiring the server for a second update of the software according to the received schedule of the second update of the software.

Images