JP6851708B2 - Network system and network method - Google Patents

Description

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

Conventionally, various development studies have been conducted on updating the firmware of network devices.

For example, Patent Document 1 (Japanese Unexamined Patent 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 connected to a firmware management server device via a network and having an automatic firmware update function, and is managed when a new version of the firmware provided therein is released. It has a transmission means for sending a notification to a person as to whether or not to update the firmware.

Patent Document 2 (Japanese Unexamined Patent Publication No. 2012-98906) provides convenience when updating and restarting the firmware installed in a wireless LAN device in a wireless LAN environment in which a plurality of wireless LAN devices are connected. The wireless LAN device to be improved is disclosed.

The wireless LAN device described in Patent Document 2 is a wireless LAN device connected to a wireless LAN, and includes a firmware storage unit for storing firmware, model identification information for specifying a model of the wireless LAN device, and a wireless LAN. Identification information individually assigned to the device, version information indicating the firmware version, and other wireless LAN devices of the same model as the wireless LAN device to which the wireless LAN device is directly connected in the wireless LAN. The device information storage unit that stores the device information including the connection destination information shown, and the device information about the other wireless LAN device directly or indirectly connected to the wireless LAN device from the other wireless LAN device. The version information included in the device information stored in the collection unit to be collected and the device information storage unit is compared with the version information included in the device information for other wireless LAN devices and stored in the firmware storage unit. The version determination unit that determines whether the firmware version is newer than the firmware version held by other wireless LAN devices, and the firmware version stored in the firmware storage unit is the firmware held by other wireless LAN devices. When the version is newer than the version, the distribution unit that distributes the firmware stored in the firmware storage unit to other wireless LAN devices, the device information stored in the device information storage unit, and the device information about other wireless LAN devices Based on the connection form of the wireless LAN device and the other wireless LAN device in the wireless LAN specified based on the above, the restart instruction timing to the other wireless LAN device is determined, and the restart instruction is given at the instruction timing. Is provided with a restart instruction transmission control unit that transmits the above to another wireless LAN device.

Japanese Unexamined Patent Publication No. 2005-228201 Japanese Unexamined Patent Publication No. 2012-98906

As described above, Patent Document 1 or Patent Document 2 discloses a network update device and a wireless LAN device for updating by firmware.
In the network device described in Patent Document 1, it can be confirmed 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 times when you want to change to new firmware, and on the contrary, there is a possibility that problems will occur, so individuals may wait for a reaction to surrounding updates.
Furthermore, updating the firmware all at once is prone to problems because a restart process or the like is involved regardless of the individual's intention.

An object of the present invention is to provide a network system and a network method capable of upgrading while recognizing the importance of version upgrade.

(1)
A network system that follows one aspect includes a management server, a network device, a mobile communication terminal, and a coordinator that adjusts at least one of the notification contents and the notification method according to the important level of the version upgrade of the network device. It's a network.

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

(2)
The network system according to the second invention is a network system according to one aspect, wherein the network device has at least one of a communication device and an external storage device, and at least one of the communication device and the external storage device has a connection port. It may also include equipment 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, it is possible to easily upgrade the version of the device connected to the connection port.

(3)
The network system according to the third invention may differ in the content of notification depending on the number of notifications in one aspect or the network system according to the second invention.

When the number of notifications increases, the user can easily promote the version upgrade by indicating the degree of urgency in the notification content.

(4)
In the network system according to the fourth invention, in the network system according to the third aspect to the third invention, the notification content may indicate the ratio of the network devices whose version upgrade has been completed.

In this case, by presenting the ratio of the network device whose version upgrade has been completed in the notification content, the user can recognize the ratio of the surrounding version upgrade completed.
As a result, the user can recognize the ratio, and if the ratio is high, it can be confirmed that other defects (bugs) do not occur, and the version can be upgraded with confidence.

(5)
The network system according to the fifth invention may provide profit points when the version of the notification content is upgraded within a predetermined period in the network system according to the first aspect to the fourth invention.

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

(6)
In the network system according to the sixth invention, in the network system according to the fifth aspect to the fifth invention, the notification method may change the notification interval according to at least one of the important level and the number of notifications.

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)
In the network system according to the seventh invention, in the network system according to the fifth aspect to the fifth invention, the notification method may change at least one of the number of notifications and the notification interval according to the important level.

In this case, at least one of the notification interval and the number of notifications can be changed according to the importance level. As a result, one or both of the number of notifications and 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)
The network system according to still another aspect includes a management server, a network device, and a mobile communication terminal, an acquisition device capable of acquiring the unique information of the network device by the mobile communication terminal, and a management server that acquires the unique information by the mobile communication terminal. It includes a transmission unit that transmits to, and a communication establishment unit that enables the management server to transmit and receive in association with the network device and 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. In addition, the transmission unit of the mobile communication terminal transmits unique information to the management server. Then, the communication establishment unit enables the management server to transmit and receive in association with the network device and the mobile communication terminal.
As a result, the management server and the network device can be easily communicated with each other.

(9)
The network system according to the ninth aspect of the present invention is a network system according to another aspect, wherein the network device has at least one of a communication device and an external storage device, and at least one of the communication device and the external storage device has a connection port. However, it may include 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, it is possible to easily upgrade the version of the device connected to the connection port. It is possible to easily communicate between the management server and the communication device, the external storage device and the device.

(10)
In the network system according to the tenth invention, in another aspect or in the network system according to the ninth invention, unique information is recorded in a barcode 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 acquired by imaging the barcode or QR code using the imaging unit.

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

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

(12)
The network method related to the other aspect is an adjustment step of adjusting at least one of the notification content and the notification method according to the important level of the version upgrade of the network device in the network method including the management server, the network device and the mobile communication terminal. Is included.

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

(13)
In the network method related to still other aspects, in the network method including the management server, the network device and the mobile communication terminal, the acquisition process in which the unique information of the network device can be acquired by the mobile communication terminal and the unique information are managed by the mobile communication terminal. It includes a transmission step of transmitting to the server and a communication establishment step of enabling the management server to transmit and receive in association with the network device and the mobile communication terminal.

In this case, the unique information of the network device can be acquired by the acquisition process of the mobile communication terminal. In addition, unique information is transmitted to the management server by the transmission process of the mobile communication terminal. Then, the communication establishment process 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, the management server and the network device can be easily communicated with each other.

It is a schematic diagram which shows an example of the network system which concerns on 1st Embodiment. It is a schematic diagram which shows an example of the structure of an external storage device. 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 the management server. It is a flowchart which shows an example of network connection and FW update. It is a schematic diagram which shows an example of the device information of a management server. It is a flowchart which shows an example of network connection and FW update which concerns on 2nd Embodiment. It is a flowchart which shows an example of network connection and FW update which concerns on 3rd Embodiment. It is a schematic diagram which shows an example of the information recorded in the FW (firmware) management part of the management server. It is a schematic diagram which shows other example of the information recorded in the firmware management part. It is a schematic diagram which shows an example of the importance of the update data transmitted from the firmware management part. It is a schematic diagram which shows an example of the display part of a mobile communication terminal. It is a schematic diagram which shows another example of the display part of a mobile communication terminal. It is a schematic diagram which shows another example of the display part of a mobile communication terminal. It is a schematic diagram which shows an example of the network system which concerns on 4th Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same parts are designated by the same reference numerals. Their names and functions are the same. Therefore, the detailed description of them will not be repeated.

<First Embodiment>
FIG. 1 is a schematic diagram showing an example of the network system 100 according to the first embodiment.
FIG. 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, the network system 100 includes a network device 200, a mobile communication terminal 300, and a management server 400.
In the network system 100, the network device 200, the mobile communication terminal 300, and the management server 400 are each connected by the Internet 500.

The network device 200 shown in FIG. 1 mainly includes a wireless router 210 and an external storage device (hereinafter, abbreviated as NAS) 220.
Further, as shown in FIG. 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 a notification LED) 224. including.

Next, as shown in FIG. 3, the mobile communication terminal 300 includes a network connection unit 301, an image pickup unit 302, a mail transmission / reception unit 303, and a display unit 304.

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.
The device information 403 and the FW management unit 405 may be registered in advance with the device information and the FW Ver information at the time of shipment of the network device 200.

As shown in FIG. 1, a QR code 291 including at least device information related to a unique device, address information of the management server 400, and the like is attached to the housing of the wireless router 210.
Further, as shown in FIG. 1, a QR code 292 including at least device information related to a unique device and address information of the management server 400 is attached to the NAS 220 housing.
The device information may include information about the network device 200, such as a manufacturer name, a product name, a serial number, and a MAC address of the network device 200.

<Flowchart of network method>
Subsequently, the network connection and the FW update will be described using the network system 100. FIG. 5 is a flowchart 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 a domain name used for sending an e-mail to the management server 400. 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.
In the present embodiment, the QR code 291 is attached to the wireless router 210, and the QR code 292 is attached to the NAS 220.

In the present embodiment, the QR code 291,292 is provided, but the present invention is not limited to this, and a sticker having short-range wireless communication (hereinafter referred to as NFC) or a URL attached to the housing. Etc., QR codes 291,292 may be separately provided on the card, or a display unit may be provided on each network device 200 for display.

The user uses the imaging unit 302 of the mobile communication terminal 300 to image the QR code 291 attached to the wireless router 210. Similarly, the image pickup unit 302 of the mobile communication terminal 300 is used to image the QR code 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 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 (device-specific information such as serial number) of each network device 200 is used as an account for the mail address, and the mail address "device-specific information @ domain name (example: 123456789@sample.com)" is used. Recorded.

In the present embodiment, when an e-mail address is imaged by using the image pickup unit 302 of the mobile communication terminal 300 and transmitted to the e-mail address, the e-mail address is transmitted to the management server 400 indicated by the domain name.
As a normal operation when receiving an e-mail, the content of the e-mail is saved in the mailbox of each account on the management server 400 side.

Then, in the present embodiment, as shown in FIG. 6 to be described later, when the management server 400 receives the mail of "123456789@sample.com", it is sent to the sender's mail address (user's E-mail address). On the other hand, the account information of the received e-mail (device-specific information "123456789") is associated with it. The details will be described later.

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

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

Specifically, the mobile communication terminal 300 transmits the following blank mail to the 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 analyze. In the case of com, the mobile communication terminal 300 sends a blank e-mail to the management server 400 using the e-mail address of "123456789@sample.com".
That is, a combination of a mail account (device information of the wireless router 200 such as a serial number) @ domain name (management server), or a combination of "[service number] [product name] [serial number] @ simple.com" is carried. The communication terminal 300 transmits to the management server 400.
The service number and the like may be included in the device information of the wireless router 200.
The service number in this case is a number meaning "user registration related to FW update notification", and the management server 400 can distinguish it from other services such as user registration without FW update notification. It may be.

Further, the management server 400 registers detailed user information or registers detailed user information to the e-mail address of the mobile communication terminal 300 so that the mobile communication terminal 300 can perform detailed user registration as a reply mail of the mail from the mobile communication terminal 300. An e-mail prompting the input of 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 body of the e-mail) may be sent. In the above case, the user can make various settings by accessing the link to the registration screen.

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

Further, the management server 400 receives a blank mail from the mobile communication terminal 300, records the received mail account (device information such as each network device 200 such as a serial number) in association with the sender's mail address, and records the received mail account. User registration is performed (step S4).

Next, FIG. 6 is a schematic view showing an example of the device information 403 of the management server 400.

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 "device information A: individual identification information A1", "device information B: individual identification information B1", and "device information C: individual identification information C1", and is associated with user 2. The E-mail address is associated with "device information A: individual identification information A2", and the E-mail address of user 3 is "device information B: individual identification information B2", "device information C: individual identification information C2". Be associated.

Further, the device information may be added to the E-mail address of each user each time the product is registered by the user.
For example, when the mobile communication terminal 300 captures the QR codes 291 and 292 of each of a plurality of different network devices 200 using the E-mail address of the user 1 as the transmission source and registers the user in the management server 400, the E of the user 1 is used. -Device information of a plurality of different networks 200 is associated with the mail address.
In the present embodiment, the information is grouped by E-mail address, but the present invention is not limited to this, and the information may be grouped by device information.
For example, the device information A may be associated with the user 1's E-mail address, the device information B may be associated with the user 1's E-mail address, and the device information C may be associated with the user 2's E-mail address. ..

Further, the management server 400 records the result of the process 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.

Further, the management server 400 may be set so that each user can additionally change the 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 shown in the reply mail from the management server 400 to the registration mail from the mobile communication terminal 300 to the management server 400, thereby allowing the user to E-mail. It may be configured so that a spare E-mail address can be added in association with the address.
In this case, the management server 400 can perform the notification using the spare E-mail address when the notification using the user's E-mail address is not possible.

Next, the management server 400 confirms the presence or absence of FW update data registered in the management server 400 by an administrator such as a manufacturer of the network device 200. For example, the management server 400 determines the presence / absence of FW update data based on the device information 403, and when it is determined that there is FW update data, the management server 400 transmits the FW to the mobile communication terminal 300 via the network connection unit 401. A notification email is sent using the E-mail address of the corresponding user when the update occurs (step S5).

The mobile communication terminal 300 receives the notification mail of the occurrence of the FW update 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 body of the notification mail from the management server 400 indicating "approval" of the FW update data, and returns 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 shown in the body of the notification mail from the management server 400.

When the FW update data is selected, the mobile communication terminal 300 transmits the FW update approval information to the management server 400 (step S7).
Here, when the management server 400 cannot obtain the FW update approval information for a predetermined period, the management server 400 repeats the process of step S5 again based on the device information 403. The 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 is determined that the FW update is approved (step S10), and wirelessly responds to the request from each network device 200. It transmits that there is FW update data for NAS 220 via the 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).
The 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, NAS 220 confirms the presence / absence of the FW update flag of the management server 400 via the wireless router 210 (step S12).

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

Next, when the FW update is completed, the NAS 220 transmits the completion to the management server 400 (step S17).
Upon receiving the completion, the management server 400 lowers the FW update flag and sets the farm completion flag (step S18). The management server 400 confirms the farm completion flag and transmits the completion to the mobile communication terminal 300 (step S19).
The user confirms that the completion has been transmitted to the mobile communication terminal 300 and displayed on the display unit 304 (step S20).
In the above embodiment, the operation of the NAS 220 has been mainly described, but the same operation may be performed in the wireless router 210 or each of the other network devices 200.

<Second embodiment>
FIG. 7 is a flowchart showing an example of network connection and FW update according to the second embodiment.
In the second embodiment, only the differences from the first embodiment will be described, and the same part 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 is composed of, for example, a number or a figure of about 3 digits, and is randomly set for each network device 200, for example, and is also set in the management server 400 in advance as shipping information for each network device 200. It is 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 code 291,292, the initial password may be configured to be provided to the mobile communication terminal 300 using NFC, or an initial password may be separately provided on the card and displayed on each network device 200. A part may be provided and displayed.

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 the NAS 220 to the management server (step S3a).
When the user registers the user registration information from the mobile terminal 300 to the management server 400 by e-mail, the user inputs the initial password in the body or the destination part of the e-mail and sends the information.
That is, by sending the input of the initial password to the management server 400, it is determined on the management server 400 side that the initial passwords match.
The management server 400 is ready to receive information.
If the initial password consists of a figure, the figure may be selected.

Thereby, it is possible to 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 to enter the management server. It may be designed so that it can be connected to 400 user registration screens.
In addition, the user may be configured to be able to change and add his / her own e-mail address, change the initial password, and the like.

It is premised that the device information and the initial password are recorded in advance on the management server 400 side in association with each other. However, the above measures can be taken by the manufacturer registering the device information according to the initial password at the time of product shipment.

Further, in the above embodiment, the initial password is attached to the e-mail, but the present invention is not limited to this, and a simple blank e-mail may be sent to the management server 400.
That is, the mobile terminal 300 sends a blank mail to the management server 400, the management server 400 shows a link to the URL for inputting the initial password to the mobile terminal 300 in the reply mail to the blank mail, and the user sends the link to the link destination. On the other hand, the initial password may be input.

Further, in the process of step S3a of FIG. 7, the user may image the QR code by using the dedicated barcode reader application of the mobile communication terminal 300.
As a result, the mobile communication terminal 300 may acquire an e-mail address with 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 is "a ref =" mailto: 123456789 @ sample. com? It may be described in HTML format such as "server = product name, etc. &amp; body = device information", and the barcode reader application that reads the contents extracts the e-mail address with the setting information and uses that e-mail address. It may be configured to send an e-mail to the management server 400.

Alternatively, each setting information may be passed to the mail application downloaded to the mobile communication terminal 300 and transmitted. In addition, if the dedicated barcode reader application is configured to automatically attach a password to an e-mail together with reading the QR code and send the e-mail, the convenience can be enhanced.
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 the user's e-mail address can be changed or the password can be changed. ..

Further, in the above embodiment, the case where the display unit 304 displays whether or not to send an e-mail to the management server 400 by imaging the QR code 292 using the mobile communication terminal 300 has been described. The URL address can be obtained by taking an image, and the management server 400 can be accessed by tapping the URL. The management server 400 is a user who has already input device information or the like according to the URL information. You may set to display the registration screen.
Then, the user may be able to enter his / her own e-mail address on the user registration screen, and the user may be able to enter an arbitrary e-mail address for contact.

Further, the management server 400 may receive the URL address, analyze the optional contents of the received URL address, and record the e-mail address in association with each device information such as the serial number.
For example, the user can use aaa. The management server 400 called jp may be accessed with parameters such as service name aaa, product name bbb, and serial number ccc. Specifically, as a URL address with parameters, http: // aaa. jp /? Access service = aaa & productname = bbb & sn = ccc.

Further, the user may be registered from the setting screen of NAS 220. A personal computer, a smartphone, a tablet terminal, or the like may be used instead of the mobile communication terminal 300.

Specifically, the user inputs the address of NAS220 to open the setting screen (user registration screen) of NAS220, the user inputs his / her e-mail address on the setting screen, the user presses the registration button, and NAS220. May send its own device information and the user's e-mail address to the management server 400.

In this case, the management server 400 can receive the information and store the device information and the user's e-mail address in association with each other.
The mobile communication terminal (smartphone) 300 may be configured to provide an address for opening the setting screen of the NAS 220 by a QR code or a short-range wireless communication (NFC).

For example, when the mobile communication terminal 300 uses the dedicated barcode reader application to image this QR code, the dedicated barcode reader application extracts the address information of NAS220 from the captured QR code and also uses WiFi communication. Then, the extracted address information is used to search for the NAS 220 on the network, and when the NAS 220 is found on the network, the setting screen is automatically opened.
If the user's e-mail address is registered in the mobile communication terminal, when NAS220 is found on the network, it is automatically registered with NAS220, and NAS220 automatically manages the registered e-mail address. It may be configured to send to the server 400.

Further, the user may directly register with the management server 400. For example, the user inputs the URL address of the management server 400 to open the user registration screen of the management server 400, the user inputs his / her e-mail address on the user registration screen of the management server 400, and the user is the device of the NAS 220. After inputting the information, the user presses the registration button, and the management server 400 can store the device information and the user's e-mail address in association with each other.

The mobile communication terminal (smartphone) 300 may be configured to provide an address for opening the user registration screen of the management server 400 by a QR code or short-range wireless communication (NFC).
Although NAS 220 is described in this example, the same applies to the wireless router 210 or each of the other network devices 200.

<Third embodiment>
FIG. 8 is a flowchart showing an example of network connection and FW update according to the third embodiment. In the third embodiment, only the differences 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 sets the FW update flag of the management server 400 via the wireless router 210. In addition to confirming the presence or absence of the above, the version information of the FW of NAS220 is also notified (step S12b).

In that case, for example, the management server 400 can recognize the FW Ver of the network device 200 even if the factory-shipped FW Ver of the network device 200 is not registered in advance with the management server 400. Further, even when 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 makes an unnecessary FW update request. It is possible to prevent the mobile communication terminal 300 from being implemented.
Further, between the FW version of the network device 200 before the FW update and the current latest FW update data version on the management server 400, the FW update of the version in which the network device 200 has not performed the FW update. When a plurality of the above data exist, the management server 400 can execute the FW update request to the mobile communication terminal 300 so that the network device 200 has the latest FW version.

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

The FW update data acquired in this case is the FW update data of the FW Ver in which the completion flag is not set among the FW update data corresponding to the own device information. For example, the latest version thereof. FW Ver FW update data.

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

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),", "User 1's E- 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 is indicated with versions (Ver) of versions A1, B5, and C3.

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

Further, for example, "user 2's E-mail address, device information A, FW Ver information A2, update flag (0), completion flag (1)" are 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, when the completion flag is set, it means that the FW update is completed.
Further, when the completion flag is changed from (0) to (1), the management server 400 transmits the completion to the mobile communication terminal 300.

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) "is recorded.
In this case, the update flag and the completion flag are not set, and the FW update data exists in the management server 400, but the FW update has not been approved by the user, and the FW update has not been made. This means that there is no history of the data being applied to the network device 200.

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

As shown in FIG. 10, the FW management unit 405 is informed that "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), user 1 E-mail address, device information B, FW Ver information B5, update flag (1), completion flag (0) ), User 1 E-mail address, device information B, FW Ver information B4, update flag (0), completion flag (1), user 1 E-mail address, device information C, FW Ver 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, if the FW version (Ver) is A1, it may be A0. That is, A1 is the data of the FW update of the new version, and A0 is the data of the FW update of the previous version.
Further, when the FW version (Ver) is B5, it may be B4. That is, B5 is the data of the FW update of the new version, and B4 is the data of the FW update of the previous version.
Similarly, when the FW version (Ver) is C3, it may be C2. That is, C3 is the data of the FW update of the new version, and C2 is the data of the FW update of the previous version.

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

For example, the management server 400 is configured so that the user 1 can confirm a part or all of the contents of FIG. 10, and the user 1 accesses the setting screen of the management server 400. Then, for example, the update flag of the FW of the old version is set. In such a case, the network device 200 can acquire and update the FW update data of the FW Ver in which the FW update flag is set. Then, after updating, the completion flag is set and the update flag is lowered.
Although FIG. 10 shows an example of FW update information one year ago, a plurality of versions of FW update information may be recorded and retained.
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 completion flag of the version in which the FW update flag is set. It may be a structure to be lowered.

Next, FIG. 11 is a schematic diagram showing an example of the importance of the 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. FIG. 12 shows an example of the display unit 304 in step S6 of FIGS. 5, 7, and 8.

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

In addition, "FW Ver information B4" is ranked as "importance D" and is recommended to be updated within "1 week". The benefit is not given at "discount 0%", and the notification interval is ". "Every 2 days", "FW Ver information C3" is the rank of "Importance F", and it is recommended to update within "1 month". The notification interval is "every week", "FW Ver information C2" is the rank of "importance C", and it is recommended to update within "3 days", and the benefit is "0% discount". Is not given, and the notification interval is "every 30 hours".

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

Specifically, as shown in FIG. 12, the display unit 304 of the mobile communication terminal 300 has "new update software" in the case of importance A rank. Please upgrade 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 will be performed every hour.
At the time of this re-notification, "There is new update software. Please upgrade within 3 hours. If the version is upgraded in time, we will give you a discount ticket. Is not notified, but "There is a new update software. If you upgrade within 1 hour, we will give you a discount ticket. ", And the re-notification says," There is new update software. Please update as soon as possible. ] Etc. will be notified. The content of the notification and the re-notification are the same, and the content of the re-notification may be changed.

For example, the management server 400 counts the number of re-notifications and changes the notification content according to the number of re-notifications. For example, in the third notification, "There is new update software. Please upgrade. Is displayed, and in the fourth and subsequent notifications, "Important content is included. Please update as soon as possible. ] Etc. will be notified.
Further, the notification interval may be changed according to the number of re-notifications. For example, the notification is carried out every week for the third notification, and the notification is carried out every three days after the fourth notification. Of course, the changes in these notifications may be configured to be implemented in combination with each other.

Subsequently, FIGS. 13 and 14 are schematic views showing another example of the display unit 304 of the mobile communication terminal 300.

As shown in FIG. 13, the display unit 304 of the mobile communication terminal 300 displays "There is new update software. Those who have already upgraded are XX million people." As a result, the user can be conscious of upgrading the version of the update software.
Specifically, the management server 400 confirms the device information 403, the user information 404, and the FW management unit 405 to determine the number of network devices 200 registered as users and whether or not the update is completed for each FW by the completion flag. Since it is possible to grasp it, the information is used to notify the user.

Further, as shown in FIG. 14, the display unit 304 of the mobile communication terminal 300 displays "There is new update software. More than 80% of those who have already upgraded." As a result, the user can be conscious of upgrading the version of the update software.

In the present embodiment, the case where all the versions are manually upgraded has been described, but the present invention is not limited to this, and "automatic" or "manual" may be switched depending on the importance of 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 approval notification from the user.
By doing so, the network device 200 can automatically perform the FW update without obtaining the user approval.
For example, an automatic update flag is provided in the FW management unit 405 of the management server 400, and the user can access the setting screen using the address to the setting screen of the management server 400 and set this 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 the network system according to the fourth embodiment. In the fourth embodiment, only the points different from the first embodiment will be described, and the same part will not be repeated.

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

In the fourth embodiment, a case where the external device 230 connected to the USB port 293 of the NAS 220 is targeted for FW update will be described.
The USB port 293 is not limited to USB. For example, when the external device 230 is a device having an interface such as IEEE1394, SerialATA, or HDMI (registered trademark) (High-Definition Peripheral Interface), each network device 200 may be used. The configuration may include a port 293 corresponding to those interfaces.

<Registration of external device 230 in 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 the device information of the external device 230 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 source NAS 220".

Further, when the device information of the external device 230 is transmitted to the management server 400 via the mobile communication terminal 300, the user uses the QR code 294 attached to the external device 230 to the imaging unit 302 of the mobile communication terminal 300. The image is taken by the user and registered as a user in the management server 400. That is, the same process 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.

<About FW update notification and approval from the management server 400 to the 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 (user's address information associated with the device information of the external device 230). To send.
Then, the management server 400 can set the update flag by the reply from the user to approve the FW update.

<About updating the FW of external devices>
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 added to 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, the NAS 220 updates the FW of the external device 230 using the FW update data.

The NAS 220 may be configured to hold 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 regarding 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 the new FW update data of the external device 230 is uploaded, the FW update data can be acquired. Then, after that, when the user actually connects the external device 230 and the update flag is set, the external device 230 may be FW updated using the acquired FW update data.

In the first to third embodiments described above, registration information is transmitted from the mobile communication terminal 300 to the management server 400 (processing of steps S1 to S4). The wireless router 210 may be configured so that the mobile communication terminal 300 transmits the transmission to the management server 400 via the wireless router 210.
For example, when the mobile communication terminal 300 can be connected to the wireless router 210 by WiFi communication, the QR code of each network device 200 is captured by using the dedicated barcode reader application installed in the mobile communication terminal 300. At that time, 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 confirming the update information from the management server 400 (process in step S11) or when issuing a FW execution instruction (process in step S14), the wireless router 210 may be used.
It is a condition that the mobile communication terminal 300 exists in the WiFi connection area of the wireless router 210, but no problem occurs when the mobile communication terminal 300 is set indoors.
Also, for example, the mobile communication terminal 300 supports the interface with the wireless router 210, that is, WiFi communication, but for 3G (3rd 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, the FW can be updated even when the user is away from home.

Further, when the wireless router 210 and NAS 220 are reset, that is, returned to the factory default state, when the wireless router 210 and NAS 220 are connected to the management server 400, the network device 200 resets the management server 400. It is desirable that the management server 400 that transmits the signal to that effect and receives the signal rewrites the contents of the network device 200 of the firmware management unit 405 of the management server 400 to the initial state.

Further, when the mobile communication terminal 300 is a mobile phone or the like, the model may be changed with time, so that the E-mail address of the user registered in the management server 400 may also be changed. In that case, since it is assumed that the notification mail from the management server 400 does not reach the user, the management server 400 or the wireless router 210 is used by using an SNS such as Facebook or a communication terminal equipped with LINE, googl-mail, etc. , The configuration may be such that it can be connected to the NAS 220.

For example, in the case of an SNS such as Facebook, the management server 400 searches for a user participating in the SNS using the E-mail address of the user registered in the management server 400. For example, friend search. Then, it is confirmed whether or not the notification using this SNS may be executed for the searched user. Specifically, apply for a friend. Then, when the friend application is approved, the management server 400 notifies using this SNS (friend registration).

Further, 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 the messenger registration address information (URL) (friend application). Use this instant messenger to notify you when a user accesses that address (friend registration).

Further, in the case of another E-mail address 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 perform notification using this E-mail address.

Further, in the first to fourth embodiments, the FW is manually updated, but the FW is automatically updated only when the rank (level) of importance is low or high. You may do so.
In addition, the update FW schedule to be updated and the affected software may 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 the update FW.

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

Further, the device information of the NAS 220 can be acquired by the image pickup unit 302 of the mobile communication terminal 300, and the unique information can be transmitted to the management server 400 by the mail transmission / reception unit 302 and the mail transmission / reception unit 402.
Then, the network connection unit 401 and the network connection unit 221 enable the management server 400 to send and receive to and from the NAS 220. As a result, the management server 400 and the NAS 220 can be easily communicated with each other.

In the present invention, the management server 400 corresponds to the "management server", the wireless router 210, NAS 220 and the external device 230 correspond to the "network device", the USB port 293 corresponds to the "connection port", and the mobile communication terminal. 300 corresponds to "portable communication terminal", importance levels A, ~, and F correspond to "important level of version upgrade", firmware management unit 405 corresponds to "adjustment unit and adjustment process", and network system 100 corresponds to "adjustment unit and adjustment process". Corresponds to "network system and network method", benefits correspond to "profit points", imaging unit 302 corresponds to "acquisition device and acquisition process", mail transmission / reception unit 303, mail transmission / reception unit 402 "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".

A preferred embodiment of the present invention is as described above, but the present invention is not limited thereto. It will be appreciated that various embodiments are made that do not deviate from the spirit and scope of the present invention. Further, in the present embodiment, the actions and effects according to the constitution of the present invention are described, but these actions and effects are examples and do not limit the present invention.
In this embodiment, the operation of the NAS 220 of the network device 200 has been mainly described, but the same operation may be used in the wireless router 210, the external device 230, or each of the other network devices 200.

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 (10)

With the management server
With network equipment
Communication terminal and
Including an external device that can be connected to the network device,
The management server
It includes an adjustment unit that adjusts at least one of the notification content and notification method according to the important level of version upgrade of the external device.
The user information of the user who uses the communication terminal input to the management server is associated with the unique information of the external device input to the management server.
The user information includes E-mail address information of the user on a computer network on which the communication terminal can receive notifications according to the critical level of the version upgrade.
When there is version upgrade data that allows the version upgrade of the external device, a notification is given according to the important level of the version upgrade based on the E-mail address information included in the user information.
Based on the response from the communication terminal that received the notification, the version upgrade for the external device is enabled.
The network device confirms the management server, and when it is possible to upgrade to the external device, the external device connected to the network device using the upgrade data acquired from the management server. A network system that performs version upgrade processing for. The user information and the unique information, the network device or input to the management server via the communication terminal, the network system of claim 1, wherein. The network system according to claim 1 or 2, wherein the content of the notification differs depending on the number of notifications. The network system according to claim 1 or 2 , wherein the notification content presents the ratio of the network device whose version upgrade has been completed. The network system according to any one of claims 1 to 4 , wherein the content of the notification provides profit points when the version is upgraded within a predetermined period. The network system according to any one of claims 1 to 5 , wherein the notification method changes the notification interval according to at least one of the importance level and the number of notifications. The network system according to any one of claims 1 to 5 , wherein the notification method changes at least one of the number of notifications and the notification interval according to the importance level. The unique information is recorded in a barcode or QR code (registered trademark).
The network system according to any one of claims 1 to 7 , wherein the communication terminal acquires the unique information by using an imaging unit. The network system according to any one of claims 1 to 8 , wherein the communication terminal acquires the unique information of the network device by using short-range wireless communication. In a network method including a management server, a network device, a communication terminal, and an external device that can be connected to the network device.
An adjustment step that adjusts at least one of the notification contents and the notification method according to the importance level of the version upgrade of the external device that can be connected to the network device.
This is an association step in which the management server associates the user information of the user who uses the communication terminal input to the management server with the unique information of the external device input to the management server, and is the user information. includes: the communication terminal the upgrade of the user on the importance level can receive the computer network notification in accordance with the E-mail address information including, association step,
When the version of the external device can be upgraded, a notification step of notifying according to the important level of the version upgrade based on the E-mail address information included in the user information, and a notification process.
Based on the response from the communication terminal that received the notification by the notification process, the version upgrade preparation step that enables the version upgrade for the external device, and the version upgrade preparation step.
When the management server is checked and there is version upgrade data that can be upgraded, the network device is connected to the network device using the version upgrade data acquired from the management server by the network device. A network method including a version upgrade process step of performing a version upgrade process on the external device.

Images