JP7108059B2 - Network system and method - Google Patents

Description

The present invention relates to a network system and network method for connecting a management server and network devices and upgrading firmware.

Conventionally, various researches and developments have been conducted on updating the firmware of network devices.

For example, Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2005-228201) discloses a network device capable of accurately updating firmware.

The network device described in Patent Document 1 is a network device having an automatic firmware update function that is connected to a firmware management server device via a network. It has transmission means for transmitting a notification as to whether or not to update the firmware to the user.

In Patent Document 2 (Japanese Patent Application Laid-Open No. 2012-98906), in a wireless LAN environment in which a plurality of wireless LAN devices are connected, convenience is provided when updating firmware installed in a wireless LAN device and restarting the device. An improved wireless LAN device is disclosed.

The wireless LAN device described in Patent Document 2 is a wireless LAN device that is connected to a wireless LAN, and includes a firmware storage unit that stores firmware, model identification information for specifying the model of the wireless LAN device, and a wireless LAN device. Identification information assigned to each device individually, version information indicating the firmware version, and another wireless LAN device of the same model as the wireless LAN device to which the wireless LAN device is directly connected in the wireless LAN. and a device information storage unit for storing device information including connection destination information indicating, and device information about another wireless LAN device directly or indirectly connected to the wireless LAN device from another wireless LAN device. The version information included in the device information stored in the device information storage unit and the version information included in the device information about other wireless LAN devices are compared with the version information stored in the firmware storage unit. A version determination unit for determining whether or not the version of firmware is newer than the version of firmware held by another wireless LAN device; a distribution unit that distributes firmware stored in a firmware storage unit to other wireless LAN devices when the firmware is newer than the version; and device information stored in the device information storage unit and device information about the other wireless LAN devices. determining the timing of instructing the other wireless LAN device to restart based on the connection configuration of the wireless LAN device and the other wireless LAN device in the wireless LAN, and instructing the restart at the instruction timing to another wireless LAN device.

Japanese Patent Application Laid-Open No. 2005-228201 JP 2012-98906 A

As described above, Patent Document 1 or Patent Document 2 discloses a network update device and a wireless LAN device for firmware update.
In the network device described in Patent Document 1, it is possible to confirm whether or not the firmware is new.
Further, in the wireless LAN device described in Patent Document 2, the firmware can be updated all at once.

However, there are cases in which the individual wants to change to new firmware, and there are cases in which the individual wants to wait for the surrounding reaction to the update because there is a possibility that a problem may occur.
Furthermore, updating the firmware all at once is likely to cause problems because the restart process or the like is entered regardless of the individual's intention.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a network system and a network method that can be upgraded while recognizing the importance of the upgrade.

(1)
A network system according to one aspect includes a management server, a network device, and a mobile communication terminal, and includes an adjustment unit that adjusts at least one of the notification content and the notification method according to the importance level of version upgrade of the network device. It is a thing.

In this case, the adjustment unit adjusts either the notification content or the notification method according to the degree of importance (level) of the version upgrade. As a result, the user can recognize the level of importance of version upgrade by the adjustment unit.
As a result, the user can appropriately upgrade the version.

(2)
A network system according to a second aspect of the invention is a network system according to one aspect, wherein at least one of the communication device and the external storage device has a connection port, and at least one of the communication device and the external storage device has a connection port, and a device that is further connected to the connection port.

In this case, the network device includes either a communication device or an external storage device, and a device connected to a connection port of either the communication device or the external storage device. As a result, the device connected to the connection port can be easily upgraded.

(3)
A network system according to a third aspect of the invention is the network system according to one aspect or the second aspect of the invention, wherein the content of notification may differ depending on the number of times of notification.

When the number of times of notification increases, the degree of urgency is indicated in the content of the notification, thereby easily encouraging the user to upgrade.

(4)
A network system according to a fourth aspect of the invention is the network system according to the first aspect to the third aspect of the invention, wherein the content of notification may present a percentage of network devices for which version upgrade has been completed.

In this case, by presenting the percentage of network devices for which upgrades have been completed in the notification content, the user can recognize the percentage of upgrades completed in the vicinity.
As a result, the user can recognize the ratio, and if the ratio is high, it can be confirmed that other troubles (bugs) will not occur, and the version can be upgraded with confidence.

(5)
A network system according to a fifth aspect of the present invention is the network system according to the first aspect to the fourth aspect of the present invention, wherein the notification content may provide profit points when the version upgrade is performed within a predetermined period.

In this case, the user can immediately respond to the version upgrade in order to obtain profit points for the content of the notification.

(6)
A network system according to a sixth aspect of the invention is the network system according to any one of the first to fifth aspects of the invention, wherein the notification method changes the notification interval according to at least one of the importance level and the number of times of notification.

In this case, the notification interval can be changed according to at least one of the importance level and the number of notifications. As a result, the notification interval is changed according to one or both of the importance level and the number of notifications, so that the user can recognize the importance level and/or the number of notifications according to the notification interval.

(7)
A network system according to a seventh aspect of the invention is the network system according to any one of the first to fifth aspects of the invention, wherein the notification method changes at least one of the number of notifications and the notification interval according to the importance level.

In this case, at least one of the notification interval and the number of times of notification can be changed according to the importance level. As a result, one or both of the number of notifications and/or the number of notifications is changed according to the importance level, so that the user can recognize the importance level according to the notification interval and/or the number of notifications.

(8)
A network system according to still another aspect includes a management server, a network device, and a mobile communication terminal. and a communication establishing unit that enables transmission and reception in which the management server associates the network device with the mobile communication terminal.

In this case, the unique information of the network device can be acquired by the acquisition device of the mobile communication terminal. Also, the unique information is transmitted to the management server by the transmission unit of the mobile communication terminal. Then, the communication establishing unit enables the management server to perform transmission/reception in which the network device and the mobile communication terminal are associated with each other.
As a result, it is possible to easily communicate between the management server and the network device.

(9)
A network system according to a ninth aspect of the present invention is a network system according to another aspect, wherein at least one of the communication device and the external storage device has a connection port, and at least one of the communication device and the external storage device has a connection port. and a device further connected to the connection port.

In this case, the network device includes either a communication device or an external storage device, and a device connected to a connection port of either the communication device or the external storage device. As a result, the device connected to the connection port can be easily upgraded. Communication between the management server and the communication device, the external storage device, and the device can be easily made possible.

(10)
A network system according to a tenth invention is the network system according to another aspect or the ninth invention, wherein the unique information is recorded in a bar code or QR code (registered trademark) attached to the network device, and the acquisition device may consist of an imaging unit.

In this case, the unique information can be obtained by capturing an image of the bar code or QR code (registered trademark) using the imaging unit.

(11)
According to another aspect of the network system according to the eleventh invention, in the network system according to the tenth invention, the mobile communication terminal may acquire the unique information of the network device using short-range wireless communication.

In this case, the mobile communication terminal can easily acquire the unique information using short-range wireless communication.

(12)
A network method according to another aspect is a network method including a management server, a network device, and a mobile communication terminal, and includes an adjustment step of adjusting at least one of the notification content and the notification method according to the importance level of the version upgrade of the network device. includes.

In this case, either the notification content or the notification method is adjusted according to the level of importance of the version upgrade by the adjustment process. As a result, the user can recognize the importance level of version upgrade through the adjustment process.
As a result, the user can appropriately upgrade the version.

(13)
In a network method according to still another aspect, in a network method including a management server, a network device, and a mobile communication terminal, an acquisition step capable of acquiring unique information of the network device by the mobile communication terminal, and managing the unique information by the mobile communication terminal. It includes a transmission step of transmitting to the server, and a communication establishment step of enabling transmission and reception in which the management server associates the network device and the mobile communication terminal.

In this case, the unique information of the network device can be acquired by the acquiring step of the mobile communication terminal. Also, the unique information is transmitted to the management server by the transmission process of the portable communication terminal. Then, the communication establishment step enables transmission and reception in which the management server associates the network device with the mobile communication terminal.
As a result, it is possible to easily communicate between the management server and the network device.

1 is a schematic diagram showing an example of a network system according to a first embodiment; FIG. 1 is a schematic diagram showing an example of the structure of an external storage device; FIG. It is a schematic diagram which shows an example of the structure of a mobile communication terminal. It is a schematic diagram which shows an example of the structure of a management server. 5 is a flow chart showing an example of network connection and FW update; 4 is a schematic diagram showing an example of device information of a management server; FIG. FIG. 10 is a flow chart showing an example of network connection and FW update according to the second embodiment; FIG. FIG. 11 is a flow chart showing an example of network connection and FW update according to the third embodiment; FIG. 4 is a schematic diagram showing an example of information recorded in a FW (firmware) management section of a management server; FIG. FIG. 5 is a schematic diagram showing another example of information recorded in the firmware management unit; 4 is a schematic diagram showing an example of the importance of update data transmitted from a firmware management unit; FIG. It is a schematic diagram which shows an example of the display part of a mobile communication terminal. FIG. 10 is a schematic diagram showing another example of the display unit of the mobile communication terminal; FIG. 10 is a schematic diagram showing another example of the display unit of the mobile communication terminal; FIG. 13 is a schematic diagram showing an example of a network system according to a fourth embodiment; FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same parts are given the same reference numerals. Their names and functions are also the same. Therefore, detailed description thereof will not be repeated.

<First Embodiment>
FIG. 1 is a schematic diagram showing an example of a network system 100 according to the first embodiment.
2 is a schematic diagram showing an example of the structure of the external storage device 220, FIG. 3 is a schematic diagram showing an example of the structure of the mobile communication terminal 300, and FIG. 4 is a schematic diagram showing an example of the structure of the management server 400. is.

As shown in FIG. 1, network system 100 includes network device 200 , mobile communication terminal 300 , and management server 400 .
In network system 100 , network device 200 , mobile communication terminal 300 and management server 400 are each connected via Internet 500 .

A network device 200 shown in FIG. 1 mainly includes a wireless router 210 and an external storage device (hereinafter abbreviated as NAS) 220 .
2, the NAS 220 includes a network connection unit 221, a firmware (hereinafter abbreviated as FW) update unit 222, a recording unit 223, and a notification light emitting diode (hereinafter abbreviated as notification LED) 224. including.

Next, as shown in FIG. 3, the mobile communication terminal 300 includes a network connection section 301, an imaging section 302, an email transmission/reception section 303, and a display section 304. FIG.

Next, as shown in FIG. 4, the management server 400 includes a network connection unit 401 , a mail transmission/reception unit 402 , device information 403 , user information 404 , and a firmware (hereinafter abbreviated as FW) management unit 405 .
Note that device information and FW Ver information at the time of shipment of the network device 200 may be registered in advance in the device information 403 and the FW management unit 405 .

As shown in FIG. 1, the wireless router 210 has a QR code (registered trademark) 291 attached to the housing of the wireless router 210. there is
Also, as shown in FIG. 1, the NAS 220 has a QR code (registered trademark) 292 attached to the housing of the NAS 220, which includes at least device information about the unique device and address information of the management server 400 and the like.
Note that the device information may include information about the network device 200 such as the manufacturer name, product name, serial number, and MAC address of the network device 200 .

<Flow chart of network method>
Next, using the network system 100, network connection and FW update will be described. FIG. 5 is a flow chart showing an example of network connection and FW update.

First, the NAS 220 displays its own device information and the address information of the management server 400 as registration information. (Step S1).
The address information of the management server 400 includes the domain name used for sending mail to the management server 400. FIG. However, as will be described later, the address information may be a URL indicating a link address to the user registration screen of the management server 400. FIG.
In this embodiment, a QR code (registered trademark) 291 is attached to the wireless router 210 and a QR code (registered trademark) 292 is attached to the NAS 220 .

In the present embodiment, QR codes (registered trademark) 291 and 292 are provided, but the present invention is not limited to this, and near field communication (hereinafter referred to as NFC) or URL is attached to the housing. It may be written on a sticker or the like worn, QR codes (registered trademark) 291 and 292 may be separately provided on the card, or each network device 200 may be provided with a display section to display.

The user captures an image of the QR code (registered trademark) 291 attached to the wireless router 210 using the imaging unit 302 of the mobile communication terminal 300 . Similarly, the imaging unit 302 of the mobile communication terminal 300 is used to image the QR code (registered trademark) 292 attached to the NAS 220 .

As a result, the mobile communication terminal 300 acquires the unique information of the wireless router 210, the unique information of the NAS 220, and the address information of the management server 400 (step S2).
In this case, the QR code (registered trademark) 291 records the domain name used in the mail of the management server 400 as the address information at the time of product shipment.
Specifically, the device information of each network device 200 (device-specific information such as a serial number) is used as an email address account, and an email address of “device-specific information@domain name (example: 123456789@example.com)” is set. Recorded.

In the present embodiment, when an image of an e-mail address is imaged using imaging unit 302 of mobile communication terminal 300 and sent to that e-mail address, the image is sent to management server 400 indicated by the domain name.
As a normal mail reception operation, the contents of the mail are saved in the mailbox for each account on the management server 400 side.

In this embodiment, as shown in FIG. 6, which will be described later, when the management server 400 receives an email of "123456789@example.com", the source email address (user's E-mail address) is In response, the account information of the received mail (equipment specific information "123456789") is associated. The details will be described later.

Subsequently, the mobile communication terminal 300 sends the acquired information, the specific information of the wireless router 210 and the NAS 220, the user registration information to the management server 400 via the network connection unit 301, and the acquired e-mail address information to the management server 400. (step S3).
Management server 400 receives transmission from mobile communication terminal 300 via network connection unit 401 .

Here, in the process of step S3, for example, the mobile communication terminal 300 writes unique information of the wireless router 210 and NAS 220 before the at mark of the mail address.

Specifically, mobile communication terminal 300 transmits the following blank mail to management server 400 . As described above, for example, the unique information of the wireless router 210 is "123456789" and the domain name of the management server 400 is example. com, the mobile communication terminal 300 sends a blank email to the management server 400 using the email address "123456789@example.com".
That is, a combination of e-mail account (equipment information of the wireless router 200 such as serial number) @ domain name (management server) or combination of "[service number] [product name] [serial number]@example.com" Communication terminal 300 transmits to management server 400 .
Note that the device information of the wireless router 200 may include a service number and the like.
The service number in this case is a number that means "user registration related to FW update notification", and is configured such that the management server 400 can distinguish it from other services, such as user registration without FW update notification. may be

Further, the management server 400, as a reply mail to the mail from the mobile communication terminal 300, makes the mobile communication terminal 300 perform detailed user registration to the mail address of the mobile communication terminal 300. An e-mail prompting the user to enter a questionnaire (for example, a URL link to the registration screen of the management server 400 for registering user information or inputting a questionnaire in the text of the e-mail) may be sent. In the above case, the user can make various settings by accessing the link on the registration screen.

Furthermore, the management server 400 connects with the network connection unit 221 of the NAS 220 via the wireless router 210 (not shown).

In addition, the management server 400 receives a blank email from the mobile communication terminal 300, records the received email account (equipment information of each network device 200 such as the serial number) in association with the email address of the sender, User registration is performed (step S4).

Next, FIG. 6 is a schematic diagram showing an example of the device information 403 of the management server 400. As shown in FIG.

As shown in FIG. 6, in the process of step S4, the management server 400 collects device information for each user's E-mail address.
For example, the E-mail address of user 1 is associated with "equipment information A: individual identification information A1", "equipment information B: individual identification information B1", and "equipment information C: individual identification information C1". The e-mail address is associated with "equipment information A: individual identification information A2", and the e-mail address of user 3 is associated with "equipment information B: individual identification information B2" and "equipment information C: individual identification information C2". Associated.

Further, device information may be added to each user's E-mail address each time a product is registered by the user.
For example, when the mobile communication terminal 300 images the QR codes (registered trademark) 291 and 292 of each of a plurality of different network devices 200 with the E-mail address of the user 1 as the transmission source and performs user registration in the management server 400, Device information of a plurality of different networks 200 is associated with the E-mail address of user 1 .
In the present embodiment, the information is grouped for each E-mail address, but is not limited to this, and may be grouped for each device information.
For example, they may be associated in a form such as "user 1's e-mail address to device information A", "user 1's e-mail address to device information B", and "user 2's e-mail address to device information C". .

The management server 400 also records the result of the processing in step S4 in the firmware management unit 405, records the obtained device information in the device information 403, and records the obtained user information in the user information 404. FIG.

Further, the management server 400 may be set so that each user can add or change a spare E-mail address later through the setting screen of the management server 400 .
For example, the user accesses the link address to the setting screen of the management server 400 indicated in the reply mail from the management server 400 in response to the registration mail sent from the mobile communication terminal 300 to the management server 400, thereby sending the user's E-mail address. The configuration may be such that a spare E-mail address can be added in association with the address.
In this case, the management server 400 can perform notification using a backup E-mail address when notification using the user's E-mail address is impossible.

Next, the management server 400 checks whether there is FW update data registered in the management server 400 by an administrator such as the manufacturer of the network device 200 . For example, the management server 400 determines whether or not there is FW update data based on the device information 403 . A notification mail is sent using the e-mail address of the corresponding user that the update has occurred (step S5).

The mobile communication terminal 300 receives the FW update notification mail via the network connection unit 301, and notifies the display unit 304 of the FW update data (step S6). The user selects the FW update data displayed on the display unit 304 .
For example, the user writes in the text of the notification mail from the management server 400 to indicate “approval” of the FW update data and returns it to the management server 400 .
Further, for example, the user selects a link for instructing the management server 400 to approve the FW update of the device information indicated in the text of the notification mail from the management server 400 .

When this FW update data is selected, the mobile communication terminal 300 transmits FW update approval information to the management server 400 (step S7).
Here, if the management server 400 cannot obtain the FW update approval information for a predetermined period of time, the management server 400 repeats the process of step S5 based on the device information 403 again. This process is repeated until the FW update approval information is received (step S8).

The management server 400 receives the FW update approval information (step S9), sets the FW update flag when it determines that the FW update has been approved (step S10), and wirelessly responds to a request from each network device 200. It transmits that there is FW update data for NAS 220 via router 210 .

On the other hand, the NAS 220 accesses the management server 400 at a predetermined timing via the wireless router 210, and confirms the FW update corresponding to its own device information (step S11).
Address information for accessing the management server 400 is recorded in advance in each network device 200 such as the wireless router 210 or the NAS 220 .
After the process of step S11, the NAS 220 confirms the presence or absence of the FW update flag of the management server 400 via the wireless router 210 (step S12).

When the FW update flag is present, the NAS 220 lights the notification LED 224 (step S13).
Subsequently, the NAS 220 downloads FW update data from the management server 400 and instructs execution of FW update (step S14).
At the same time, the management server 400 gives FW update data to the NAS 220 via the wireless router 210 (step S15).
The NAS 220 executes FW update (step S16).

Next, when the FW update is completed, the NAS 220 notifies the management server 400 of the completion (step S17).
The management server 400 receives the notification of completion, lowers the FW update flag, and raises the firmware completion flag (step S18). The management server 400 confirms the firmware completion flag and notifies the portable communication terminal 300 of completion (step S19).
The user confirms the completion sent to the mobile communication terminal 300 and displayed on the display unit 304 (step S20).
In the above embodiment, the operations of the NAS 220 have been mainly described, but the wireless router 210 or other network devices 200 may perform similar operations.

<Second Embodiment>
FIG. 7 is a flowchart illustrating an example of network connection and FW update according to the second embodiment.
In the second embodiment, only points different from the first embodiment will be described, and descriptions of the same portions will not be repeated.

In the second embodiment, the initial password is attached to the NAS 220 with a sticker or the like. Here, the initial password consists of, for example, a three-digit number or figure, and is set at random for each network device 200. The initial password is stored in the management server 400 in advance as shipping information for each network device 200. registered in association with The initial password can be used to log in to the user registration screen of the management server 400 .
As with the QR codes (registered trademark) 291 and 292, the initial password may be configured to be provided to the mobile communication terminal 300 using NFC, or the initial password may be separately provided on the card, and the initial password may be provided to each network. A display unit may be provided in the device 200 for display.

As shown in FIG. 7, the mobile communication terminal 300 transmits the initial password, the acquired information, and the unique information of the wireless router 210 and NAS 220 to the management server (step S3a).
When sending the user registration information from the portable terminal 300 to the management server 400 by e-mail, the user enters the initial password in the body of the e-mail or in the destination part and sends the e-mail.
That is, by transmitting the input initial password to the management server 400, the management server 400 determines that the initial passwords match,
The management server 400 becomes ready to receive information.
If the initial password consists of a figure, the figure may be selected.

This can prevent a malicious user from connecting to the management server 400 .

In addition, the user accesses the link address (URL) to the web page for changing the registration of the user information of the management server 400, uses his/her e-mail address as the login name, and enters the initial password. It may be designed so that it can be connected to the 400 user registration screen.
Also, the user may be configured to be able to change and add his/her own email address or change the initial password.

It is assumed that the device information and the initial password are recorded in advance in the management server 400 in association with each other. However, if the manufacturer registers the device information together with the initial password at the time of product shipment, it becomes possible to deal with the above problem.

Also, in the above embodiment, the initial password is attached to the e-mail.
That is, the mobile terminal 300 sends a blank mail to the management server 400, and the management server 400 shows a link to the URL for entering the initial password to the mobile terminal 300 in a reply mail to the blank mail. Alternatively, an initial password may be entered.

Further, in the process of step S3a in FIG. 7, the user may use the dedicated barcode reader application of the mobile communication terminal 300 to image the QR code (registered trademark).
As a result, the mobile communication terminal 300 may acquire an e-mail address with the setting information and send an e-mail to the management server 400 together with the acquired setting information to the e-mail address.
For example, the content described in the QR code (registered trademark) is "a href="mailto:123456789@example.com. com? Subject = product name, etc. & body = device information", etc.", and the barcode reader application that reads the contents extracts the email address with the setting information, and uses that email address. The mail may be sent to the management server 400 by the user.

Alternatively, each setting information may be passed to a mail application downloaded to the mobile communication terminal 300 to be transmitted. In addition, convenience can be enhanced by using a dedicated barcode reader application to automatically attach a password to an email and send it by email together with the reading of the QR code (registered trademark).
Further, the password may be used to display the user registration screen of the management server 400 on the display unit 304 of the mobile communication terminal 300 at a later date, so that it is possible to change and add one's own e-mail address or change the password. .

Further, in the above embodiment, the case where the portable communication terminal 300 is used to capture an image of the QR code (registered trademark) 292 is displayed on the display unit 304 as to whether or not to send an email to the management server 400. However, it is not limited to this, and a URL address can be obtained by capturing an image, and the management server 400 can be accessed by tapping the URL. You may set so that the user registration screen where it became was displayed.
Then, the user may be able to enter his/her own e-mail address on the user registration screen, or the user may be able to enter any e-mail address for contact.

Furthermore, the management server 400 may receive a URL address, analyze the content of options in the received URL address, and record the e-mail address associated with each piece of device information such as the serial number.
For example, a user may enter aaa. jp may be accessed with the parameters of service name aaa, product name bbb, and serial number ccc. Specifically, the URL address with parameters is http://aaa. jp/? Access servicename=aaa&productname=bbb&sn=ccc.

User registration may also be performed from the setting screen of the NAS 220 . Note that a personal computer, a smart phone, a tablet terminal, or the like may be used instead of the mobile communication terminal 300 .

Specifically, the user enters the address of the NAS 220 to open the setting screen (user registration screen) of the NAS 220, the user enters his/her e-mail address on the setting screen, presses the registration button, and the NAS 220 may cause the management server 400 to transmit its own device information and the user's e-mail address.

In this case, the management server 400 can receive the information and store the device information in association with the user's e-mail address.
It should be noted that an address for opening the setting screen of the NAS 220 for the mobile communication terminal (smartphone) 300 may be provided by a QR code (registered trademark) or near field communication (NFC).

For example, when the mobile communication terminal 300 uses a dedicated barcode reader application to capture an image of this QR code (registered trademark), the dedicated barcode reader application extracts the address information of the NAS 220 from the imaged QR code (registered trademark). In addition, using WiFi communication, the extracted address information is used to search for the NAS 220 on the network, and automatically opens the setting screen when the NAS 220 is found on the network.
If the user's e-mail address is registered in the mobile communication terminal, it is automatically registered with the NAS 220 when the NAS 220 is found on the network, and the NAS 220 automatically manages the registered e-mail address. It may be configured to transmit to the server 400 .

Alternatively, the user may directly register with the management server 400 . For example, the user enters the URL address of the management server 400 to open the user registration screen of the management server 400, the user enters his/her own e-mail address on the user registration screen of the management server 400, and the user enters the device of the NAS 220. After inputting the information, the user presses the registration button, and the management server 400 can associate and store the device information and the user's e-mail address.

Note that an address for opening the user registration screen of the management server 400 for the mobile communication terminal (smartphone) 300 may be provided by a QR code (registered trademark) or near field communication (NFC).
Although the NAS 220 is described in this example, the same applies to the wireless router 210 and other network devices 200 .

<Third Embodiment>
FIG. 8 is a flowchart illustrating an example of network connection and FW update according to the third embodiment. In the third embodiment, only points different from the first embodiment will be described.

As shown in FIG. 8, in the flowchart according to the third embodiment, instead of step S12 according to the first embodiment, the NAS 220 updates the FW update flag of the management server 400 via the wireless router 210. FW version information of the NAS 220 is also notified (step S12b).

In this case, for example, the management server 400 can recognize the FW Ver of the network device 200 even if the FW Ver of the network device 200 when shipped from the factory is not registered in the management server 400 in advance. Further, even if the network device 200 performs the FW update without going through the management server 400, the management server 400 recognizes the FW Ver applied to the network device 200, and thereby requests unnecessary FW update. It is possible to prevent execution on the mobile communication terminal 300 .
Also, between the version of the FW of the network device 200 before the FW update and the version of the current latest FW update data on the management server 400, the version of the FW update to which the network device 200 has not performed the FW update. exists, the management server 400 can request the mobile communication terminal 300 to update the FW so that the network device 200 has the latest FW version.

Further, as shown in FIG. 8, in the flowchart according to the third embodiment, instead of step S14 according to the first embodiment, the NAS 220 performs FW update even if the FW update flag is not set. Data is downloaded from the management server 400 and FW is received (step S14b).
In other words, FW update data is acquired in advance without waiting for the user's approval of the FW update. Therefore, when the user approves the FW update, the update process is quickly performed using the acquired FW update data.

Note that the FW update data acquired in this case is the FW update data of the FW Ver for which the completion flag is not set, among the FW update data corresponding to the device information of the device itself. FW update data of FW Ver.

FIG. 9 is a schematic diagram showing an example of information recorded in the FW management unit 405 of the management server 400. As shown in FIG.
As shown in FIG. 9, the FW management unit 405 of the management server 400 records an update flag, an execution completion flag, and FW version information.

Specifically, as shown in FIG. 9, "user 1's E-mail address, device information A, FW Ver information A1, update flag (1), completion flag (0),""user1's E-mail mail address, device information B, FW Ver information B5, update flag (1), completion flag (0), ”, “e-mail address of user 1, device information C, FW Ver information C3, update flag (1), Completion flag (0)," is recorded.
In this case, the FW management unit 405 of the management server 400 indicates versions (Ver) of versions A1, B5, and C3.

When the update flag is not set, it is indicated by update flag (0), and when the update flag is set, it is indicated by update flag (1).
The management server 400 determines whether or not the update flag is set. Here, if the update flag is set, it means that the user has approved the update of the FW related to the device information.

Also, for example, "E-mail address of user 2, device information A, FW Ver information A2, update flag (0), completion flag (1)" is recorded.
Here, when the completion flag is not set, it is indicated by the completion flag (0), and when the completion flag is set, it is indicated by the completion flag (1).
In this case, if the completion flag is set, it means that the FW update is completed.
Also, in accordance with the change of the completion flag from (0) to (1), the management server 400 notifies the portable communication terminal 300 of completion.

Further, for example, "user 3's E-mail address, device information B, FW Ver information B2, update flag (0), completion flag (0), user 3's E-mail address, device information C, FW Ver information C2 , update flag (0), completion flag (0)”.
In this case, the update flag and the completion flag are not set, and FW update data exists in the management server 400, but the user has not approved the FW update, and the FW update has not been approved by the user. data has been applied to the network device 200 .

Next, FIG. 10 is a schematic diagram showing another example of information recorded in the FW management unit 405. As shown in FIG. In FIG. 10, an example of the email address of user 1 will be described.

As shown in FIG. 10, the FW management unit 405 stores "user 1's E-mail address, device information A, FW Ver information A1, update flag (1), completion flag (0), user 1's E-mail address, device information A, FW Ver information A0, update flag (0), completion flag (1), E-mail address of user 1, device information B, FW Ver information B5, update flag (1), completion flag (0) ), E-mail address of user 1, device information B, FW version information B4, update flag (0), completion flag (1), E-mail address of user 1, device information C, FW version information C3, update flag (1), completion flag (0), E-mail address of user 1, device information C, FW Ver information C2, update flag (0), completion flag (1)” are recorded.

In this case, the FW version (Ver) may be A1 or A0. That is, A1 is FW update data of a new version, and A0 is FW update data of one version earlier.
Also, the FW version (Ver) may be B5 or B4. In other words, B5 is the new version of FW update data, and B4 is the previous FW update data.
Similarly, the FW version (Ver) may be C3 or C2. That is, C3 is FW update data of a new version, and C2 is FW update data of one version earlier.

In this way, by recording and holding the previous version in the FW management unit 405, the user can easily change to the previous version using the mobile communication terminal 300 when a problem occurs. can be returned.

For example, the management server 400 is configured so that the user 1 can confirm part or all of the contents of FIG. Then, for example, an old version FW update flag is set. In such a case, the network device 200 can acquire and update the FW update data of the FW Ver for which the FW update flag is set. Then, after updating, the completion flag is raised and the update flag is lowered.
Note that FIG. 10 shows an example of FW update information one year before, but multiple versions of FW update information may be recorded and held.
Further, when the user 1 sets the FW update flag of the old FW version, the management server 400 sets the completion flag of the FW of the version for which the FW update flag is set if the completion flag is already set. It may be configured to be lowered.

Next, FIG. 11 is a schematic diagram showing an example of the importance of update data transmitted from the FW management unit 405, and FIG. 12 is a schematic diagram showing an example of the display unit 304 of the mobile communication terminal 300. As shown in FIG. FIG. 12 shows an example of the display section 304 in step S6 of FIGS. 5, 7 and 8. FIG.

First, as shown in FIG. 11, "FW Ver information A1" has a rank of "importance A", recommends updating "within 3 hours", and gives a privilege of "10% discount". and the notification interval is "every hour".
Similarly, "FW Ver information A0" has a rank of "importance B", recommends updating "within 2 days", is given a "5% discount" benefit, and has a notification interval of ""Every 1 day", "FW Ver information B5" has a rank of "importance C", recommends updating "within 3 days", gives a privilege of "3% discount", and notifies The interval is "every 30 hours".

In addition, "FW Ver information B4" has a rank of "importance D", recommends updating "within 1 week", does not give benefits with "discount 0%", and has a notification interval of " "FW Ver information C3" is ranked "importance F", recommends updating "within 1 month", "discount 0%" and benefits are not given, The notification interval is "every week", the "FW Ver information C2" has a rank of "importance C", it is recommended to update "within 3 days", and the privilege is "0% discount" is not given, and the notification interval is "every 30 hours".

In this way, the FW update unit 405 ranks the FW update data according to the importance thereof, and the notification changes according to the importance thereof.

Specifically, as shown in FIG. 12, the display unit 304 of the mobile communication terminal 300 displays the message "New update software is available" when the importance level is A. Please update within 3 hours. If the version is upgraded in time, we will give you a discount ticket. ', and unless the version is upgraded and the completion flag is set, re-notification is performed every hour.
At the time of this re-notification, the message "New update software is available. Please update within 3 hours. If the version is upgraded in time, we will give you a discount ticket. ' is not notified, but 'There is new update software. If you upgrade within 1 hour, we will give you a discount ticket. ', and the second notification says, 'New update software is available. Please update as soon as possible. etc. is notified. Note that the content of the notification and the re-notification may be the same, and only the content of the re-re-notification may be changed.

For example, the management server 400 counts the number of re-notifications and changes the content of notification according to the number of re-notifications. For example, in the first three notifications, "There is new update software. Please upgrade. ” is displayed, and from the fourth notification onwards, “Important content is included. Please update as soon as possible. etc. is notified.
Also, the notification interval may be changed according to the number of re-notifications. For example, up to the third notification, the notification is performed every week, and after the fourth notification, the notification is performed every three days. Of course, these notification changes may be configured to be implemented in combination with each other.

13 and 14 are schematic diagrams showing other examples of the display unit 304 of the mobile communication terminal 300. FIG.

As shown in FIG. 13, the display unit 304 of the mobile communication terminal 300 displays "There is new updated software. There are XX million people who have already upgraded." As a result, the user can be motivated to upgrade the updated software.
Specifically, the management server 400 confirms the device information 403, the user information 404, and the FW management unit 405 to check the number of user-registered network devices 200 and the presence or absence of update completion for each FW based on the completion flag. Because it is possible to know, that information is used to implement notifications to users.

Further, as shown in FIG. 14, the display unit 304 of the mobile communication terminal 300 displays "There is new updated software. More than 80% of users have already upgraded." As a result, the user can be motivated to upgrade the updated software.

In the present embodiment, the case where everything is upgraded manually has been described, but the present invention is not limited to this, and "automatic" or "manual" may be switched according to the importance of the FW update. , the user may set the above in advance on the setting screen of the management server 400 .
For example, in the case of an important FW update related to product reliability, the management server 400 automatically sets an update flag for the update software in the management server 400 even if there is no notification of approval from the user.
By doing so, the network device 200 can automatically update the FW without obtaining user approval.
For example, an automatic update flag is provided in the FW management unit 405 of the management server 400, and the user accesses the setting screen using the address to the setting screen of the management server 400 to set the automatic update flag. may be When the automatic update flag is set, the network device 200 updates the FW regardless of the update flag.

<Fourth Embodiment>
Next, FIG. 15 is a schematic diagram showing an example of a network system according to a fourth embodiment. In the fourth embodiment, only points different from the first embodiment will be described, and descriptions of the same portions will not be repeated.

As shown in FIG. 15, in the fourth embodiment, network system 100 further includes another external device 230 in addition to network system 100 shown in FIG. The external storage device (NAS) 220 has a USB port 293 , and the external device 230 is a USB device, for example, and is connected to the USB port 293 of the external storage device (NAS) 220 .
A QR code (registered trademark) 294 is attached to the external device 230 in the same manner as the QR codes 291 and 292 .

In the fourth embodiment, a case will be described where the external device 230 connected to the USB port 293 of the NAS 220 is targeted for FW update.
Note that the USB port 293 is not limited to USB. For example, if the external device 230 is a device having an interface such as IEEE 1394, Serial ATA, HDMI (registered trademark) (High-Definition Mulimedia Interface), each network device 200 A configuration including a port 293 corresponding to those interfaces may be used.

<Regarding registration of the external device 230 in the management server 400>
First, when transmitting the device information of the external device 230 to the management server 400 via each network device 200 , the user connects the external device 230 to the USB port 293 of the NAS 220 . The NAS 220 reads the device information of the external device 230 from the connected external device 230 and transmits it to the management server 400 together with the device information of the NAS 220 . The management server 400 associates the device information of the external device 230 with "the user's E-mail address information registered in association with the device information of the NAS 220 that is the transmission source".

When transmitting the device information of the external device 230 to the management server 400 via the mobile communication terminal 300 , the user sends the QR code (registered trademark) 294 attached to the external device 230 to the mobile communication terminal 300 . is imaged by the image capturing unit 302 and registered as a user in the management server 400 . That is, the same processing as that of step S2 in FIG. 5 is performed.
Next, the management server 400 transmits a FW update notification to the external device 230 to the user. If the user approves, the update flag of the management server 400 will be set.

<Regarding FW Update Notification and Approval from Management Server 400 to User>
When a new FW for the external device 230 is uploaded to the management server 400, the management server 400 sends information about the FW update to the user's E-mail address (the user's address information associated with the device information of the external device 230). to send.
Then, the management server 400 can raise the update flag in response to a reply from the user to the effect that the FW update is approved.

<Regarding FW update of external device>
When the external device 230 is connected to the USB port 293 of the NAS 220, the NAS 220 transmits the device information of the external device 230 to the management server 400, and the update flag is set in the FW update data associated with the device information of the external device 230. Check if you are standing.
When the NAS 220 determines that the update flag of the FW update data of the external device 230 is set, it uses the FW update data to update the FW of the external device 230 .

Note that the NAS 220 may be configured to retain device information of the connected external device 230 . In that case, the notification LED 224 of the NAS 220 can be used to notify the user of the presence or absence of FW update data of the external device 230 .

Further, regardless of the state of the FW update flag on the management server 400, when new FW update data of the external device 230 is uploaded, the FW update data can be obtained. After that, when the user actually connects the external device 230 and the update flag is set, the FW update of the external device 230 may be performed using the acquired FW update data.

In the first to third embodiments described above, the registration information is transmitted from the mobile communication terminal 300 to the management server 400 (processing from step S1 to step S4). However, the wireless router 210 may be configured to transmit from the mobile communication terminal 300 to the management server 400 via the wireless router 210 .
For example, when the mobile communication terminal 300 is connectable to the wireless router 210 via WiFi communication, a QR code (registered trademark) is captured, the registration information is transmitted to the wireless router 210 via the dedicated barcode reader application, and the wireless router 210 transmits the received registration information to the management server 400 for registration.
Further, when checking update information from the management server 400 (process of step S11) and when issuing a FW execution instruction (process of step S14), the wireless router 210 may be used.
It should be noted that mobile communication terminal 300 must be within the WiFi connection area of wireless router 210, but no problem will occur if the setting is made indoors.
Also, for example, the mobile communication terminal 300 supports an interface with the wireless router 210, that is, WiFi communication, but does not support 3G (third generation communication) or LTE (long term evolution) that can directly access the Internet. It is suitable when it does not correspond.

Therefore, in the first to fourth embodiments, it is possible to update the FW even from outside.

When the wireless router 210 and the NAS 220 are reset, that is, when the wireless router 210 and the NAS 220 are connected to the management server 400, the network device 200 resets the management server 400. It is preferable that the management server 400 that receives the signal rewrites the content of the network device 200 in the firmware management unit 405 of the management server 400 to the initial state.

Furthermore, if the mobile communication terminal 300 is a mobile phone or the like, the model may change over time, so the user's E-mail address registered in the management server 400 may also change. In that case, it is assumed that the notification mail from the management server 400 may not reach the user. , NAS 220 may be configured.

For example, in the case of SNS such as Facebook, the management server 400 searches for users participating in the SNS using the user's E-mail address registered in the management server 400 . For example, it is a friend search etc. Then, it is confirmed whether or not it is permissible for the retrieved user to be notified using this SNS. Specifically, a friend request is made. Then, when the friend application is approved, the management server 400 notifies using the SNS (friend registration).

For example, in the case of an instant messenger such as LINE, the management server 400 uses the user's e-mail address registered in the management server 400 to notify the user using this instant messenger. Send messenger registration address information (URL) (friend request). When the user accesses the address, this instant messenger is used to notify the user (friend registration).

In the case of other e-mail addresses such as Google-mail, the user accesses the setting screen of the management server 400 and adds the e-mail address. As a result, the management server 400 can also send notifications using this E-mail address.

Further, in the first to fourth embodiments, the FW is manually updated, but the automatic update is performed only when the importance rank (level) is low or high. You may do so.
In addition, the schedule of the update FW to be updated and the influential software may also be displayed on the display unit 304 of the mobile communication terminal 300 . As a result, the user can update the FW according to the timing of other software or update FW.

As described above, the firmware management unit 405 adjusts either the notification content or the notification method according to the level of importance of the upgrade. As a result, the user can recognize the level of importance of the version upgrade, and can perform the version upgrade appropriately.

In addition, the imaging unit 302 of the mobile communication terminal 300 can acquire the device information of the NAS 220 , and the mail transmitting/receiving unit 302 and the mail transmitting/receiving unit 402 can transmit unique information to the management server 400 .
The network connection unit 401 and the network connection unit 221 enable the management server 400 to transmit and receive data to and from the NAS 220 . As a result, communication between the management server 400 and the NAS 220 can be facilitated.

In the present invention, the management server 400 corresponds to the "management server", the wireless router 210, the NAS 220 and the external device 230 correspond to the "network devices", the USB port 293 corresponds to the "connection port", and the mobile communication terminal 300 corresponds to "portable communication terminal", importance levels A, . . . The privilege corresponds to the "profit point", the imaging unit 302 corresponds to the "acquisition device and acquisition process", the mail transmission/reception unit 303 and the mail transmission/reception unit 402 correspond to the "transmission unit and The network connection unit 301, the network connection unit 221, the wireless router 210, the network connection unit 401, the device information 403, and the user information 404 correspond to the "communication establishment unit and communication establishment process".

Although one preferred embodiment of the invention is described above, the invention is not so limited. It is understood that various other embodiments can be made without departing from the spirit and scope of the invention. Furthermore, in this embodiment, the actions and effects of the configuration of the present invention are described, but these actions and effects are examples and do not limit the present invention.
In this embodiment, the operations of NAS 220 of network device 200 have been mainly described, but similar operations may be used in wireless router 210, external device 230, or other network devices 200 as well.

100 network system 210 wireless router 220 NAS
221 network connection unit 230 external device 300 mobile communication terminal 301 network connection unit 302 imaging unit 303 mail transmission/reception unit 400 management server 401 network connection unit 402 mail transmission/reception unit 403 device information 404 user information 405 firmware management unit

Claims (12)

a management server;
a network device capable of updating its own firmware via the management server;
a communication terminal that communicates with the management server without going through the network device and causes the network device to update firmware;
The management server includes an adjustment unit that adjusts at least one of the notification content and the notification method according to the importance level of the firmware update of the network device. associating the user information with the unique information of the network device input to the management server;
The user information includes e-mail address information of the user on a computer network from which the communication terminal can receive notifications according to the importance level of the firmware update,
The network device transmits version information of its own program to the management server;
The management server confirms the version of the program of the network device sent from the network device, and if there is data for firmware update that allows firmware update of the network device, the E included in the user information - Notify according to the importance level of the firmware update based on the mail address information;
enabling firmware update for the network device based on a response from the communication terminal that received the notification;
The network system according to claim 1, wherein the network device confirms the management server and, if the firmware update is possible, performs firmware update processing using the firmware update data acquired from the management server. 2. The network system according to claim 1, wherein said user information and said unique information are input to said management server via said network device or said communication terminal. 3. The network system according to claim 1, wherein the content of said notification differs depending on the number of times of notification. 3. The network system according to claim 1, wherein said notification content presents a percentage of said network devices for which firmware update has been completed. 5. The network system according to any one of claims 1 to 4, wherein said notification content provides profit points when firmware update is performed within a predetermined period. 6. The network system according to any one of claims 1 to 5, wherein said notification method changes the notification interval according to at least one of the importance level and the number of times of notification. 6. The network system according to any one of claims 1 to 5, wherein said notification method changes at least one of the number of times of notification and the notification interval according to the importance level. The unique information is recorded in a barcode or QR code (registered trademark),
8. The network system according to any one of claims 1 to 7, wherein said communication terminal acquires said unique information using an imaging unit. 9. The network system according to any one of claims 1 to 8, wherein said communication terminal acquires said unique information of said network device using short-range wireless communication. 10. The network according to any one of claims 1 to 9, wherein notification of said firmware update from said management server to said communication terminal is performed via SNS or instant messenger in addition to said E-mail address information . system. 11. The network system according to any one of claims 1 to 10, wherein said firmware update process by said network device is performed manually or automatically according to the importance level of said firmware update. a management server; a network device capable of updating its own firmware via the management server;
a communication terminal that communicates with the management server without going through the network device and causes the network device to perform firmware update,
an adjusting step of adjusting at least one of the notification content and the notification method according to the importance level of the firmware update of the network device;
an association step in which the management server associates user information of a user using the communication terminal input to the management server with unique information of the network device input to the management server, wherein the user information includes e-mail address information of the user on a computer network from which the communication terminal can receive notifications according to the importance level of the firmware update; and
The network device transmits version information of its own program to the management server, and the management server confirms the version of the program of the network device sent from the network device, and can update the firmware of the network device. a notification step of notifying in accordance with the level of importance of said firmware update based on said e-mail address information included in said user information;
a firmware update preparation step of enabling firmware update for the network device based on a response from the communication terminal that has received the notification in the notification step;
Firmware that checks the management server and, if there is firmware update data that allows the firmware update, performs firmware update processing using the firmware update data acquired from the management server by the network device. a network method, comprising: an update process;

Images