Refrigerator

Abstract

To provide a refrigerator that can improve convenience in management.SOLUTION: A refrigerator of an embodiment includes: a storage unit; a control unit capable of controlling functions of the refrigerator; and a communication unit capable of acquiring information from the outside. The storage unit includes: a first storage unit that stores first information that is common to multiple models and can be used for control by the control unit; and a second storage unit that stores second information that varies depending on the model, function, season, or external environment of a location where the refrigerator is installed and can be combined with the first information and used for control by the control unit. At least one of the first information and the second information can be updated with update information newly acquired from the outside by the communication unit. The update information includes both first information and the second information.SELECTED DRAWING: Figure 16

Description

[Technical Field]

[0001] An embodiment of the present invention relates to a refrigerator. [Background technology]

[0002] There are technologies that allow software updates for home appliances, and such technologies are expected to improve management convenience, for example. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-346190 Summary of the Invention [Problem to be solved by the invention]

[0004] An object of the present invention is to provide a refrigerator that can improve convenience in terms of management. [Means for solving the problem]

[0005] A refrigerator according to an embodiment includes a storage unit, a control unit capable of controlling functions of the refrigerator, and a communication unit capable of acquiring information from an external device. The storage unit includes a first storage unit that stores first information that is common to multiple models and can be used for control by the control unit, and a second storage unit that stores second information that is information that varies depending on the model, function, season, or external environment of the location where the refrigerator is installed and can be combined with the first information and used for control by the control unit. At least one of the first information and the second information can be updated with update information newly acquired from an external device by the communication unit. The update information includes both the first information and the second information. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram showing a home appliance management system according to a first embodiment. [Figure 2] FIG. 2 is a diagram showing an example of a model of a refrigerator according to the first embodiment. [Figure 3] 1 is a diagram showing a schematic configuration of a refrigerator according to a first embodiment. [Figure 4] FIG. 2 is a block diagram showing the configuration of a control device according to the first embodiment. [Figure 5] FIG. 2 is a block diagram showing the functional configuration of a server according to the first embodiment. [Figure 6] FIG. 4 is a diagram showing an example of discrimination voltages for each model according to the first embodiment. [Figure 7] FIG. 3 is a diagram for explaining software processing according to the first embodiment. [Figure 8] FIG. 3 is a diagram for explaining software processing according to the first embodiment. [Figure 9] FIG. 2 is a diagram for explaining control software and parameter information according to the first embodiment. [Figure 10] FIG. 2 is a diagram for explaining control software and parameter information according to the first embodiment. [Figure 11] FIG. 10 is a sequence diagram showing a process for updating software. [Figure 12] FIG. 10 is a diagram showing an example of a management table. [Figure 13] FIG. 4 is a diagram for explaining difference data according to the first embodiment. [Figure 14] FIG. 4 is a diagram for explaining difference data according to the first embodiment. [Figure 15] FIG. 2 is a diagram for explaining a software update according to the first embodiment. [Figure 16] FIG. 2 is a diagram for explaining a software update according to the first embodiment. [Figure 17] FIG. 2 is a diagram for explaining a dual-bank ROM according to the first embodiment. [Figure 18] FIG. 2 is a diagram for explaining a ROM divided into multiple parts according to the first embodiment. [Figure 19] FIG. 10 is a diagram for explaining a software update according to the second embodiment. [Figure 20] FIG. 10 is a diagram for explaining a software update according to the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, refrigerators according to embodiments will be described with reference to the drawings. In the following description, components having the same or similar functions will be assigned the same reference numerals. Duplicate descriptions of those components may be omitted. In this application, "based on XX" means "based on at least XX" and may include a case where the component is based on another element in addition to XX. Furthermore, "based on XX" is not limited to a case where the component is based directly on XX, but may also include a case where the component is based on XX after calculation or processing. In this application, "XX or YY" is not limited to either XX or YY, but may include both XX and YY. This also applies when there are three or more optional elements. XX and YY are any elements (e.g., any information).

[0008] In this application, "acquire" is not limited to actively acquiring by sending a transmission request, but may also include passively receiving information transmitted from another device. Furthermore, "acquire" is not limited to directly acquiring target information (information to be acquired) from the outside, but may also include generating and acquiring target information by performing calculations or processing on information acquired from the outside.

[0009] (First embodiment) <1. Overall structure> 1 is a diagram showing a home appliance management system 1 according to a first embodiment. The home appliance management system 1 includes, for example, a refrigerator 100, a server 200, and a terminal device 300. The network NW described below may be, for example, the Internet, a cellular network, a Wi-Fi network, a low power wide area network (LPWA), a wide area network (WAN), a local area network (LAN), or other public or dedicated lines.

[0010] The refrigerator 100 is an example of an electrical appliance (home appliance) that is primarily used at home. The refrigerator 100 is connected to a network NW via a wireless router WR and a modem M in the residence of a user U. The refrigerator 100 can communicate with a server 200 or a terminal device 300 via the network NW. The refrigerator 100 may also be able to communicate directly with the terminal device 300 using short-range wireless communication such as Bluetooth (registered trademark). The following description is not limited to the refrigerator 100 and can also be applied to other home appliances (such as a clothes disposal machine, an air conditioner, a cooking appliance, a rice cooker, a coffee maker, a water disposal device, a garbage disposal machine, an electric vacuum cleaner, or an iron).

[0011] Server 200 is a management server that manages refrigerator 100. Server 200 is configured with one or more server devices (for example, cloud servers). Server 200 can communicate with refrigerator 100 or terminal device 300 via network NW. Server 200 may include an information processing unit that performs edge computing or fog computing, such as an information processing unit included in a router in network NW.

[0012] The terminal device 300 is an electronic device used by the user U. The terminal device 300 can be used, for example, independently of the refrigerator 100. The terminal device 300 is, for example, a mobile terminal device such as a smartphone or a tablet terminal device. However, the terminal device 300 is not limited to a mobile terminal device, and may be a personal computer or a voice interactive device (for example, a smart speaker).

[0013] <2. Refrigerator> Next, the refrigerator 100 will be described. There are multiple models of the refrigerator 100. In this application, the term "model" refers to a model that differs in one or more of the structure, performance, or functions of the refrigerator 100. For example, there are multiple models of the refrigerator 100 that differ in one or more of the structure (capacity, single door / French door, etc.), performance (insulation performance, cooling performance, etc.), or functions (special cooling control, special chill mode, energy saving function, door opening function, presence or absence of voice interaction function, etc.).

[0014] FIG. 2 is a diagram showing an example of a model of refrigerator 100. The configuration shown in FIG. 2 is an example for explaining the present application and is unrelated to the actual lineup of refrigerators. The configuration of refrigerator 100 varies depending on the model, but the basic configuration is the same. Here, a typical configuration of refrigerator 100 will be described.

[0015] <2-1. Overall configuration of the refrigerator> 3 is a diagram showing a schematic configuration of a refrigerator 100. The refrigerator 100 includes, for example, a housing 10 and a plurality of doors 20.

[0016] The housing 10 is thermally insulated and formed in the shape of a rectangular box. A plurality of storage compartments 30 are provided inside the housing 10. The plurality of storage compartments 30 include, for example, a refrigerator compartment 31, a vegetable compartment 32, an ice making compartment 33, a small freezer compartment 34, and a main freezer compartment 35. The refrigerator compartment 31 and the vegetable compartment 32 are storage compartments in the refrigerator temperature range (for example, a positive temperature range of 1 to 4°C). The ice making compartment 33, the small freezer compartment 34, and the main freezer compartment 35 are storage compartments in the freezer temperature range (for example, a negative temperature range of -10 to -20°C).

[0017] The openings of the multiple storage compartments 30 are openably and closably closed by multiple doors 20. The multiple doors 20 include left and right refrigerator compartment doors 21A, 21B that close the opening of refrigerator compartment 31, vegetable compartment door 22 that closes the opening of vegetable compartment 32, ice compartment door 23 that closes the opening of ice compartment 33, small freezer compartment door 24 that closes the opening of small freezer compartment 34, and main freezer compartment door 25 that closes the opening of main freezer compartment 35.

[0018] <2-2. Refrigerator control device> FIG. 4 is a block diagram showing the configuration of the control device 101 of the refrigerator 100. The refrigerator 100 has the control device 101. The control device 101 controls each functional unit of the refrigerator 100, such as cooling control or power saving control for each storage compartment 30. The control device 101 has, for example, a main microcomputer 110, an EEPROM (Electrically Erasable Programmable Read-Only Memory) 102, a communication unit 103, an operation unit 104, a display unit 105, a control circuit unit 106, and an interface 108. For convenience of explanation, the main microcomputer 110 may be referred to as the "main microcomputer 110" below.

[0019] The main microcomputer 110 is a functional unit capable of controlling the functions of the refrigerator 100. The main microcomputer 110 performs overall control of the refrigerator 100. For example, the main microcomputer 110 executes cooling control of the refrigerator 100 by driving electrical components such as the compressor 51 and the blower 52. The main microcomputer 110 includes, for example, a control unit 111, a ROM (Read Only Memory) 112, and a RAM (Random Access Memory) 113. In this embodiment, the ROM 112, the RAM 113, and the EEPROM 102 constitute a memory unit MR.

[0020] Control unit 111 is a functional unit that can control functions of refrigerator 100. Control unit 111 performs overall control of refrigerator 100. Control unit 111 executes cooling control of refrigerator 100, for example, by driving compressor 51 and blower 52. Control unit 111 is realized, for example, by a processor such as CPU (Central Processing Unit) 111 executing software. At least a part of control unit 111 is realized, for example, by CPU (Central Processing Unit) 111 executing refrigerator control software SF1, which will be described later.

[0021] ROM 112 is a non-volatile storage unit provided in main microcomputer 110. Information stored in ROM 112 is retained even when refrigerator 100 is turned off. ROM 112 can be electrically rewritten multiple times. Instead of being provided in main microcomputer 110, ROM 112 may be mounted on a board as a component separate from main microcomputer 110. ROM 112 is an example of a "first storage unit."

[0022] ROM 112 stores refrigerator control software SF1. For ease of explanation, the refrigerator control software SF1 may be referred to as "control software SF1" below. The control software SF1 is software that is common to multiple models of refrigerator 100. In other words, the same control software SF1 is stored in multiple models of refrigerator 100 that differ in one or more of the structure, performance, or function.

[0023] The control software SF1 is information that can be used for control by the control unit 111. For example, the control software SF1 is software for realizing main control (e.g., cooling control) of the refrigerator 100 by the control unit 111. When the control software SF1 is executed by the control unit 111, the control of the refrigerator 100 (e.g., cooling control) is executed and various functions of the refrigerator 100 become available.

[0024] The control software SF1 is, for example, information that defines a control algorithm. The content of the control realized by the control software SF1 (for example, the drive amount, drive time, drive timing of electrical components such as the compressor 51 and the blower 52, whether or not electronic components corresponding to predetermined functions are operating, etc.) is defined by parameter information PR, which will be described later. The control software SF1 is an example of "first information."

[0025] RAM 113 is a volatile storage unit provided in main microcomputer 110. Information stored in RAM 113 is erased when refrigerator 100 is turned off. Instead of being provided in main microcomputer 110, RAM 113 may be mounted on a board as a component separate from main microcomputer 110.

[0026] Parameter information PR is read from EEPROM 102 and stored in RAM 113. Parameter information PR is information that varies depending on the model, function, and season of refrigerator 100, or the external environment of the place where refrigerator 100 is installed. The "external environment of the place where refrigerator 100 is installed" refers to, for example, the external environment corresponding to the region where refrigerator 100 is installed (e.g., Hokkaido, Okinawa, the Sea of ​​Japan side, the Pacific Ocean side, the Ogasawara Islands, etc.). The "external environment of the place where refrigerator 100 is installed" refers to the external environment corresponding to the topography of the place where refrigerator 100 is installed (plains, highlands, bay areas, etc.). Parameter information PR is information that can be combined with the first information (control software SF1) and used for control by control unit 111. Parameter information PR is an example of "second information."

[0027] It should be noted that the "parameter information PR" referred to in the present application may be information including the parameter value itself, or may be difference information indicating a portion that differs from the parameter value (e.g., the initial value of the parameter) previously stored in the EEPROM 102. The parameter information PR that is difference information will be described in detail later.

[0028] In this embodiment, the parameter information PR is information that differs depending on the model of the refrigerator 100, and is information that can be used for control by the control unit 111 in combination with the first information (control software SF1).

[0029] The parameter information PR, for example, when combined with the control software SF1, defines the content of the control realized by the control software SF1. For example, even when the control software SF1 is executed (when the same algorithm is realized), the content of the control realized by the control software SF1 (for example, the drive amount, drive time, drive timing of electrical components such as the compressor 51 and the blower 52, whether or not electronic components corresponding to predetermined functions are operating, etc.) will differ depending on the parameter information PR.

[0030] To the main microcomputer 110 described above, for example, an EEPROM 102, a communication unit 103, an operation unit 104, a display unit 105, and a control circuit unit 106 are connected.

[0031] The EEPROM 102 is a rewritable nonvolatile memory. The EEPROM 102 stores parameter information PR. In this embodiment, when the software of the refrigerator 100 is updated, the control software SF1 in the ROM 112 and the parameter information PR in the EEPROM 102 are updated. The EEPROM 102 is an example of a "second storage unit."

[0032] The communication unit 103 communicates with the outside of the refrigerator 100 and can acquire information from the outside of the refrigerator 100. For example, the communication unit 103 communicates with the server 200 and the terminal device 300 via the network NW. The communication unit 103 is, for example, an IEEE802.11 wireless LAN (Local Area Network) module, but is not limited to this example. When updating the software of the refrigerator 100, the communication unit 103 receives update information SA from the server 200 and sends the received update information SA to the main microcomputer 110. The "update information SA" will be described later.

[0033] The operation unit 104 inputs various operations to the refrigerator 100. The display unit 105 displays various setting states and the like.

[0034] Control circuit unit 106 includes electronic components 107 for controlling each part in refrigerator 100. Control circuit unit 106 controls each part in refrigerator 100 based on commands from main microcomputer 110. Control circuit unit 106 is connected to sensors and actuators (e.g., electrical components such as compressor 51 and blower 52) of each part in refrigerator 100 via interface 108.

[0035] In this embodiment, the control circuit 106 has resistors R1 and R2 connected in series and resistors R3 and R4 connected in series between the power supply line P1 and the ground G. A voltage V1 at the connection point between the resistors R1 and R2 and a voltage V2 at the connection point between the resistors R3 and R4 are input to an analog port of the main microcomputer 110 as information for identifying (determining) the model of the refrigerator 100. The voltages V1 and V2 are examples of the "unique characteristics" of the refrigerator 100.

[0036] <3. Server> Next, the server 200 will be described. 5 is a block diagram showing the functional configuration of the server 200. The server 200 provides update software for controlling the refrigerator 100. The server 200 includes, for example, an update management unit 210, a communication processing unit 220, and an information storage unit 230.

[0037] The update management unit 210 manages the update information SA provided to the refrigerator 100. The communication processing unit 220 communicates with the refrigerator 100 or the terminal device 300 via the network NW. The information storage unit 230 stores the update information SA used to update the software of the refrigerator 100. In this embodiment, the information storage unit 230 provides the update information SA including control software SF1 that is common to multiple models and parameter information PR provided for each model.

[0038] <4. Basic design of refrigerator> Next, the basic design of refrigerator 100 will be described. As shown in FIG. 2, there are multiple models of refrigerator 100 that combine different structures, performance, or functions. However, the resources (people, time, funds, etc.) spent on developing refrigerator 100 are limited, and it is necessary to avoid placing an excessive development burden on the refrigerator. In this context, a common approach is used for both the hardware and software that control refrigerator 100 in order to reduce development costs.

[0039] For example, if three models of refrigerators 100 are offered, namely, a high-end model, a main model, and a popular model, those that can be made common among the three models are made common. For example, the printed wiring board and circuit design of the control device 101 are made common, while the types or numbers of electronic components installed are made different. For example, all functions are made available in the high-end model. The main model has some functions removed from the high-end model, reducing performance. The popular model has even more functions removed from the main model, reducing performance, and narrowing down to the bare minimum of functions and performance. In this way, those that can be made common among multiple models are made common, and a lineup is created by combining commonality and differentiation.

[0040] <4-1. Standardization of hardware> First, the standardization of hardware will be described. As shown in Fig. 4, refrigerator 100 is provided with control circuit unit 106 on which electronic components 107 are mounted. In this embodiment, the printed wiring board of control circuit unit 106 is standardized among high-end models, mainstream models, and popular models. The printed circuit board of control circuit unit 106 (printed wiring board on which electronic components are mounted) is one type of standardized printed wiring board, but the electronic components mounted thereon vary so that the structure, performance, or function of each model can be realized.

[0041] Furthermore, in order to identify the control circuit unit 106 for each model of refrigerator 100, resistors R1 and R2, and resistors R3 and R4 are connected in series between the power supply line P1 (e.g., 5 V) and ground G. Voltages V1 and V2, which are obtained by dividing the power supply voltage, are obtained from the connection points of resistors R1 and R2 and resistors R3 and R4. These voltages V1 and V2 vary depending on the resistance values ​​of resistors R1 and R2 and resistors R3 and R4. The control unit 111 can identify (determine) the model of refrigerator 100 based on the values ​​of voltages V1 and V2 input from an analog port of the main microcomputer 110.

[0042] 6 shows an example of discrimination voltages of control circuit unit 106 installed in each model. For example, if discrimination voltage V1 is 0 [V] and discrimination voltage V2 is 0 [V], the model of refrigerator 100 installed in control circuit unit 106 can be determined to be "A600F." Also, for example, if discrimination voltage V1 is 0 [V] and discrimination voltage V2 is 1 [V], the model of refrigerator 100 installed in control circuit unit 106 can be determined to be "A550F."

[0043] Here, discrimination voltage V1 and discrimination voltage V2 are generated by dividing the power supply voltage using resistors R1, R2, R3, and R4 provided between power line P1 and ground G and are read at the analog port, but model discrimination may also be performed by connecting pull-up or pull-down resistors to multiple GPIO (General-purpose input / output) output ports and combining voltage levels [High / Low] (bootstrap) read as digital ports in a high-impedance state at boot time. Instead of using the discrimination voltages, control unit 111 may transmit identification information (e.g., a serial number) of refrigerator 100 to external server 200 via communication unit 103 and obtain information indicating the model of refrigerator 100 from external server 200 in response.

[0044] <4-2. Standardization of software> Next, software standardization will be described. In this embodiment, in order to develop control software SF1 common to a plurality of models, development is performed by dividing the software into two types: control software SF1 and parameter information PR. Here, control software SF1 describes a series of commands and procedures. Parameter information PR is information that specifies the set temperature (target temperature) of storage compartment 30 and the drive amount, drive time, and drive timing of electrical components such as compressor 51 or blower 52. In this way, by developing control software SF1 common to a plurality of models and combining parameter information PR for each model, refrigerators 100 can be developed with various functions added / deleted for each model.

[0045] 7 and 8 are diagrams for explaining software processing in this embodiment. In FIG. 7, refrigerator control software SF1 and EEPROM rewrite control software SF2 are stored in ROM 112 of main microcomputer 110. Parameter information PR is also stored in EEPROM 102. For convenience of explanation, EEPROM rewrite control software SF2 may be referred to as "rewrite control software SF2" below.

[0046] The rewrite control software SF2 is software for executing a process for writing parameter information PR included in update information SA, which will be described later, to EEPROM 102. The rewrite control software SF2 is executed by the control unit 111, which is a processor such as a CPU, to write the parameter information PR included in the update information SA to EEPROM 102. The rewrite control software SF2 is an example of "processing information."

[0047] The rewrite control software SF2 is software common to multiple models of refrigerator 100. Even when the refrigerator control software SF1 is updated, the rewrite control software SF2 stored at the time of shipment may be used. Alternatively, the rewrite control software SF2 may be updated according to the version of the refrigerator control software SF1. In this case, the rewrite control software SF2 may be included in the update information SA together with the corresponding refrigerator control software SF1 and parameter information PR. In this case, the rewrite control software SF2 is updated using the same procedure as for the refrigerator control software SF1. Therefore, for details of updating the rewrite control software SF2, in the following description of updating the refrigerator control software SF1, simply replace "refrigerator control software SF1" with "rewrite control software SF2."

[0048] When the refrigerator 100 is powered on, an initialization process starts, and initial values ​​INIT of variables used in controlling the refrigerator 100 are prepared in the RAM 113 as shown in FIG. 8. The initial values ​​INIT are prepared, for example, under the control of the control unit 111. A fixed value such as "0" may be used as the initial value INIT, or a preset value may be read out from the ROM 112 and prepared.

[0049] Next, the parameter information PR stored in EEPROM 102 is read by control unit 111 and stored in RAM 113. Control unit 111 generates a refrigerator control variable VAR for each model by combining (for example, adding) the initial value INIT and the parameter information PR stored in RAM 113. Refrigerator 100 is a home appliance that operates continuously for a long period of time. Therefore, to ensure that refrigerator 100 can continue to be controlled even if the parameter information PR or the variable VAR in RAM 113 is unintentionally damaged, the parameter information PR is periodically read from EEPROM 102 to RAM 113 and reflected in the variable VAR. Note that although the initial value INIT is shown as being stored in RAM 113 in the figure, the initial value INIT may also be embedded in ROM 112.

[0050] <4-3. Software Update> In this embodiment, update information SA is developed that includes control software SF1 common to multiple models and parameter information PR specific to each model. Then, the control software SF1 and the parameter information PR are updated using the update information SA.

[0051] 9 and 10 are diagrams for explaining control software SF1 and parameter information PR. As shown in Fig. 2, there are nine models (A600F, A550F, B600F, B550F, B500F, B450F, B550G, B500G, and B450G) in the lineup of refrigerator 100. These models operate using common control software SF1 and parameter information PR that differs depending on the model.

[0052] In the example shown in FIG. 9, there are four versions of control software SF1 common to multiple models, from sv0 to sv3. In contrast, as shown in FIG. 10, there are seven versions of parameter information PR, from pv0 to pv6 (#01_pv0 to #01_pv6, #02_pv0 to #02_pv6, ..., #09_pv0 to #09_pv6), for each model. Here, the combination of control software SF1 and parameter information PR is important. As shown in FIG. 10, for example, parameter information #01_pv0 to #01_pv2 corresponding to versions 0 to 2 of model A600F run on control software sv0. Furthermore, parameter information #01_pv3 corresponding to version 3 of model A600F runs on control software sv1.

[0053] <4-4. Software update management> As described above, in this embodiment, software development is carried out by dividing it into control software SF1 and parameter information PR. This makes management of updated software complicated. This will be explained below.

[0054] FIG. 11 is a sequence diagram showing, as a comparative example, processing for updating the software of the refrigerator 100 by separately downloading the control software SR1 and the parameter information PR.

[0055] First, when update data for the control software SF1 is registered on the server 200, the server 200 notifies the terminal device 300 of the user U of the update (step S101). Upon receiving the update notification, the user U operates the terminal device 300 to transmit permission to start the update to the server 200 (step S102).

[0056] When server 200 receives the permission to start the update, it transmits a notification to refrigerator 100 that it is preparing to update control software SF1 (step S103). Refrigerator 100 prepares a temporary storage area in RAM 113 according to the size of the update data. Then, when server 200 completes the preparation, it transmits a notification to server 200 that it is ready to download (step S104).

[0057] When server 200 receives the notification from refrigerator 100 that the download preparation is complete, it transmits update control software SF1 to refrigerator 100, and refrigerator 100 downloads the update control software SF1 (step S105). Note that the update control software SF1 downloaded from server 200 may include hash data for signature verification. Refrigerator 100 checks the hash data, for example, using a public key, to verify the authenticity of the software.

[0058] As described above, the download and signature authentication of control software SF1 are performed, and after further updating (S107 to S109), the update process of parameter information PR is performed. Here, as described above, there are predetermined combinations of control software SF1 and parameter information PR. Therefore, when updating parameter information PR, it is necessary to manage the relationship between control software SF1 and parameter information PR. For this reason, server 200 needs a management table that manages the relationship between the model of refrigerator 100, the version of control software SF1, and the version of parameter information PR, as shown in FIG. 12.

[0059] Server 200 transmits a notification to refrigerator 100 to start updating parameter information PR at a timing when updating is possible (step S110). Refrigerator 100 prepares a temporary storage area in RAM 113 according to the size of the update data. Then, when preparation is complete, server 200 transmits a notification to server 200 that preparation for downloading parameter information PR is complete (step S111).

[0060] When server 200 receives notification from refrigerator 100 that preparation for downloading parameter information PR is complete, server 200 transmits parameter information PR to be used for updating to refrigerator 100, and refrigerator 100 downloads the parameter information PR for updating (step S112). Note that the parameter information PR downloaded from server 200 includes hash data for signature verification. Refrigerator 100 checks the hash data, for example, using a public key, to confirm the validity of the parameters.

[0061] When refrigerator 100 completes updating parameter information PR, refrigerator 100 transmits an update completion notice to server 200 (step S113). When server 200 completes the update process of parameter information PR, it transmits an update completion notice of parameter information PR to user U (step S114).

[0062] In this way, when updating software separately into control software SF1 and parameter information PR, a management table is required to manage the relationship between the model of refrigerator 100, the version of control software SF1, and the version of parameter information PR, as shown in Fig. 12, which increases the load on server 200. Also, server 200 needs to store the software of control software SF1 for each version and parameter information PR for each version for each model, as shown in Figs. 9 and 10. Also, when updating software separately into control software SF1 and parameter information PR, two update processes are required for the control software SF1 and the parameter information PR for one software update.

[0063] <4-5. Differential Data> There are two methods for downloading update data for parameter information PR: downloading update data that includes the parameter values ​​themselves, and downloading update data that indicates the difference from the previously stored parameter values. Using the difference in update data makes it easier to reduce the amount of data.

[0064] 13 shows a case where the parameter information PR is updated in order from version 0 to version 4. The data of the parameter information PR is pointed to by data from address "0" to address "7".

[0065] As shown in FIG. 13, in version 0, the data of the parameter information PR is "0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07" in the order from address "0" to address "7".

[0066] In version 1, the data at address "1" is updated to "0xF0", in version 2 the data at address "3" is updated to "0xE3", in version 3 the data at address "6" is updated to "0xC1", and in version 4 the data at address "1" is updated to "0x01" and the data at address "6" is updated to "0xC0". In version 4, the parameter data is "0x00, 0x01, 0x02, 0xE3, 0x04, 0x05, 0xC0, 0x07" from address "0" to address "7". In this example, the data size is 8 bytes, but if the parameter is 256 bytes, all parameters will be 256 bytes in size.

[0067] A simple difference downloads and updates only the data that has changed from the previous data. In other words, when updating from version 0 to version 1, only the data at address "1" is downloaded, and address "1" is updated to "0xF0." Using simple difference data, the minimum data required for version 1 is the address information, data size (1 byte in this example), and data (0xF0 in this example), so the data size can be kept to a minimum. When updating from version 1 to version 2, only the data at address "3" is downloaded, and address "3" is updated to "0xE3." When updating from version 2 to version 3, only the data at address "6" is downloaded, and address "6" is updated to "0xC1." When updating from version 3 to version 4, the data at address "1" and the data at address "6" are downloaded, and address "1" is updated to "0x01," and address "6" is updated to "0xC0."

[0068] However, in the case of simple differences, if for some reason the version upgrades are not performed in order, an incorrect parameter combination may result, leading to malfunctions. Figure 14 shows a case where the version 2 update has not been performed. As shown in Figure 14, if the version 2 update has not been performed, the process of updating address "3" to "0xE3" will not be performed. In both version 3 and version 4, the data at address "3" will remain at "0x03" without being updated. To prevent this from happening, it becomes necessary to establish a mechanism to ensure that no updates are missed.

[0069] Next, a difference resulting from merging histories will be described. The difference resulting from merging histories means a difference including history with respect to data of a base version. Here, the base version data is data of version 0. The data of parameter information PR of base version 0 is written in EEPROM 102, for example, when refrigerator 100 is shipped.

[0070] That is, when comparing version 0 and version 1, the data at address "1" has been updated to "0xF0." Therefore, when updating to version 1, the data "0xF0" at address "1" is downloaded, and the data at address "1" is updated to "0xF0."

[0071] Comparing version 0 and version 2, the data at address "1" has been updated to "0xF0" and the data at address "3" has been updated to "0xE3". Therefore, when updating to version 2, the data "0xF0" at address "1" and the data "0xE3" at address "3" are downloaded, and the data at address "1" is updated to "0xF0" and the data at address "3" is updated to "0xE3".

[0072] Similarly, when updating to version 3, the data "0xF0" at address "1", the data "0xE3" at address "3", and the data "0xC1" at address "6" are downloaded, and the data at address "1" is updated to "0xF0", the data at address "3" is updated to "0xE3", and the data at address "6" is updated to "0xC1".

[0073] When updating to version 4, the data "0x01" from address "1", the data "0xE3" from address "3", and the data "0xC0" from address "6" are downloaded, and the data from address "1" is updated to "0x01", the data from address "3" is updated to "0xE3", and the data from address "6" is updated to "0xC0".

[0074] One thing to be careful of here is when updating to version 4. When comparing the base version 0 and version 4, the data at address "1" is the same, "0x01." However, in versions 1 to 3, the data at address "1" is "0x0F," which is different from the data in base version 0. For this reason, if the difference from base version 0 is simply used, when updating to version 4, the data at address "3," "0xE3," and the data at address "6," "0xC1," will be downloaded, and the data at address "1" will not be updated to "0x01."

[0075] Therefore, the history is merged and the differences from the base version are used. In other words, the differences from the base version are downloaded, including data that has been changed even once in the past. This makes it possible to update to the latest parameters. Although the update data size of such differences resulting from merging the history is larger than that of simple differences, the data size is smaller than when all data is downloaded.

[0076] 5. Software Update in the First Embodiment Next, the software update process in this embodiment will be described. In this embodiment, parameter information PR is embedded in the control software SF1 to be updated, thereby allowing the combination of the control software SF1 and the parameter information PR to be appropriately managed, thereby enabling the software to be updated.

[0077] 15 and 16 are diagrams for explaining software updates in this embodiment. In this embodiment, at least one (for example, both) of the control software SF1 and the parameter information PR can be updated by update information SA (update software) newly acquired from the outside by the communication unit 103. In this embodiment, the update information SA is information that integrally includes the control software SF1 and the parameter information PR (information that includes a set of corresponding control software SF1 and parameter information PR) so that the combination of the control software SF1 and the parameter information PR is maintained. For example, the update information SA is information that integrates the control software SF1 and the parameter information PR by embedding the parameter information PR in the control software SF1. Note that, unless otherwise specified, control related to updates in this embodiment is executed by the control unit 111.

[0078] When new update information SA is acquired from the outside via the communication unit 103, the control unit 111 updates the control software SF1 stored in the ROM 112 with the control software SF1 included in the update information SA. When new update information SA is acquired from the outside via the communication unit 103, the control unit 111 compares the control software SF1 included in the update information SA with the control software SF1 stored in the ROM 112, and updates the control software SF1 if the control software SF1 included in the update information SA is newer than the control software SF1 stored in the ROM 112, but does not need to update if the control software SF1 included in the update information SA is not newer.

[0079] The updated control software SF1 (or the control software SF1 stored in the ROM 112 that was not updated) is executed by the control unit 111 to control the rewrite control software SF2 and update the parameter information PR stored in the EEPROM 102 with the parameter information PR included in the update information SA. Note that the parameter information PR may be updated directly by the control unit 111 instead of by the control software SF1.

[0080] A specific example will be described below. However, the example described below does not limit the contents of this embodiment. As shown in FIG. 10, for example, in model A600F, parameters (parameter information PR) from parameter #01_pv0 of version 0 to parameter #01_pv2 of version 2 are used in combination with control software sv0 of version 0 (control software SF1). Parameter #01_pv3 of version 3 (parameter information PR) is used in combination with control software sv1 (control software SF1). Parameters (parameter information PR) from parameter #01_pv4 of version 4 to parameter #01_pv5 of version 5 are used in combination with control software sv2 (control software SF1). Parameter #01_pv6 of version 6 (parameter information PR) is used in combination with control software sv3 of version 3 (control software SF1).

[0081] In this case, as shown in FIG. 15, in the update software (update information SA) for model A600F, in update software SFT#01_v0 for version 0, parameter #01_pv0 of version 0 is embedded in control software sv0 of version 0. In update software SFT#01_v1 for version 1, parameter #01_pv1 of version 1 is embedded in control software sv0 of version 0. Similarly, in update software SFT#01_v2 for version 2, parameter #01_pv2 of version 2 is embedded in control software sv0 of version 0. In update software SFT#01_v3 for version 3, parameter #01_pv3 of version 3 is embedded in control software sv1 of version 1. In update software SFT#01_v4 for version 4, parameter #01_pv4 of version 4 is embedded in control software sv2 of version 2. In the version 5 update software SFT#01_v5, the version 5 parameter #01_pv5 is embedded in the version 2 control software sv2. In the version 6 update software SFT#01_v6, the version 6 parameter #01_pv6 is embedded in the version 3 control software sv3.

[0082] Similarly, in the update software for model A550F, the version 0 update software SFT#02_v0 has the version 0 parameter #02_pv0 embedded in the version 0 control software sv0. The version 1 update software SFT#02_v1 has the version 1 parameter #02_pv1 embedded in the version 0 control software sv0. Similarly, in each version of update software (update information SA), the parameter information PR for each version is embedded in the control software SF1 for each version in a predetermined combination. The same is true for update software for other models.

[0083] The update management unit 210 of the server 200 acquires such update software SFT#01_v0 to SFT#09_v6 and stores it in the information storage unit 230. When updating software, the update software SFT#01_v0 to SFT#09_v6 is provided to the refrigerator 100.

[0084] 16 shows the process of updating the software of model A600F to version 6. When updating the software of model A600F to version 6, it is necessary to update the control software SF1 to control software sv3 of version 3 and then update the parameter information PR to parameter #01_pv6.

[0085] In this embodiment, as shown in Fig. 15, update software SFT#01_v6 (update information SA) that updates the software of model A600F to version 6 includes control software sv3 (control software SF1) of version 3 and parameter #01_pv6 (parameter information PR) of version 6. Therefore, as shown in Fig. 16, refrigerator 100 downloads update software SFT#01_v6 of version 6 for model A600F from server 200, thereby completing the update of control software SF1 and the update of parameter information PR.

[0086] For example, when updating software version 6, the control software SF1 stored in the ROM 112 is updated by the control software SF1 included in the update software (update information SA). This update is performed, for example, under the control of the main microcomputer 110 (for example, under the control of the control unit 111).

[0087] Furthermore, when the version 6 software is updated, the parameter information PR included in the update software (update information SA) is stored in ROM 112 together with the control software SF1 included in the update software (update information SA). Then, the parameter information PR stored in EEPROM 102 is updated by the parameter information PR included in the update software (update information SA) stored in ROM 11.

[0088] This update is performed, for example, under the control of control unit 111 using rewrite control software SF2. For example, rewrite control software SF2 is executed by control unit 111 to write parameter information PR included in the update software and stored in ROM 112 to EEPROM 102. As a result, the parameter information PR stored in EEPROM 102 is updated. In addition, for example, updated control software SF1 loads parameter information PR included in the update software and stored in ROM 112 into RAM 113. As a result, control unit 111 can control refrigerator 100 using updated control software SF1 and updated parameter information PR.

[0089] In this embodiment, the user U downloads update software from the server 200, in which parameter information PR corresponding to the relevant model is embedded, and after updating the update software through signature verification and the like, the embedded parameter information PR is written to the EEPROM 102. Therefore, what was required to be downloaded twice (including signature verification) in the above comparative example can be done only once. Also, processes provided for parameter processing, such as allocating temporary space using RAM 113, are no longer necessary, and the method can be unified to just the update software update method.

[0090] Note that the parameter information PR for updating may be information containing the parameter data as is, or may use the difference obtained by merging the histories described above. Using the difference obtained by merging the histories can reduce the amount of data if the difference is small. When using the difference obtained by merging the histories, control unit 111 obtains information to be used for controlling refrigerator 100 by control unit 111 based on the value of parameter information PR previously stored in EEPROM 102 (for example, the initial value of parameter information PR) and parameter information PR, which is difference information.

[0091] Furthermore, because the update software (update information SA) includes control software SF1 and parameter information PR, it is not necessary to rewrite parameter information PR stored in EEPROM 102 with parameter information PR included in the update software. Parameter information PR included in the update software is stored in ROM 112 together with control software SF1 included in the update software, and is not written to EEPROM 102. In this case, control unit 111 may load parameter information PR (e.g., parameter information PR at the time of shipment) stored in EEPROM 102 into RAM 113, and then replace or change the parameter information PR (e.g., parameter information PR at the time of shipment) loaded into RAM 113 with parameter information stored in ROM 112 (parameter information PR included in the update software), thereby reflecting parameter information PR included in the update software and controlling the refrigerator. In this case, the parameter information PR stored in EEPROM 102 can maintain its state at the time of shipment.

[0092] When it is desired to maintain the parameters in EEPROM 102 at the time of shipment, or when it is desired to embed a plurality of pieces of parameter information PR in update software and change the parameter information PR using the refrigerator function, it may be better to rewrite the parameter information PR in RAM 113 using the function rather than rewriting the parameter information PR in EEPROM 102.

[0093] FIG. 17 is a diagram illustrating a dual-bank ROM 112. A dual-bank ROM may be used as the ROM 112. The dual-bank ROM 112 may have two areas 112a and 112b, which are, for example, bank 0 (first storage area) and bank 1 (second storage area), that can be used independently. When the control unit 111 has a dual-bank ROM configuration as the ROM 112, old software (e.g., control software SF1 and parameter information PR at the time of shipment) may be stored in the area 112a of bank 0, and updated software (control software SF1 and parameter information PR included in update information SA) may be stored in the area 112b of bank 1. By selectively loading the parameter information PR stored in the area 112a and the parameter information PR stored in the area 112b in the RAM 113, the old software and the updated software can be selectively used.

[0094] 18 is a diagram illustrating a ROM 112 divided into multiple parts. When the ROM 112 is a single bank, the same processing as in the case of a dual bank can be performed by dividing the ROM area. For example, by using the ROM interrupt area, the ROM area can be divided and the old software and the updated software can be stored.

[0095] The dual-bank ROM 112 has a configuration in which two ROMs (bank 0 and bank 1) exist at the same address, and it is possible to return to the control before the update by selecting which bank to use. On the other hand, even when one ROM 112 is divided into three areas (three storage areas) 112a, 112b, and 112c for operation as shown in Fig. 18, if area 112a is used as a download area for updated software (control software SF1 and parameter information PR included in update information SA), area 112b is used as a backup area for old software (control software SF1 and parameter information PR at the time of shipment), and area 112c is used as a software execution area, it is possible to selectively execute the control before the update and the control after the update by selectively writing the updated software stored in area 112a and the old software stored in area 112b to area 112c.

[0096] As described above, in this embodiment, development costs can be reduced by developing control software SF1 and parameter information PR separately. Also, in this embodiment, update software is generated by including a predetermined combination of control software SF1 and parameter information PR. As a result, when updating at least one of control software SF1 and parameter information PR, the combination of control software SF1 and parameter information PR can be maintained while performing the update. This makes it possible to provide refrigerator 100 with improved management convenience. Furthermore, according to this embodiment, software can be updated with a single download without placing a burden on server 200. From this perspective as well, it is possible to provide refrigerator 100 with improved management convenience.

[0097] (Second embodiment) Next, a second embodiment will be described. In the first embodiment described above, control software SF1 including parameter information PR that differs depending on the model is stored in server 200 as update software. In this case, there is a possibility of human error occurring, such as the creator of the update software mistaking the correspondence between the model of refrigerator 100 and parameter information PR and creating incorrect update software.

[0098] For example, there is a possibility that a developer of update software may make a mistake by creating update software that embeds parameter information PR for model B450G into control software SF1 for model B600F. In this case, because control software SF1 is common to multiple models, it is unlikely that refrigerator 100 will not operate at all. However, if the parameter information PR is different, refrigerator 100 may not operate optimally. To prevent such a mistake from occurring, it is necessary to verify whether update software exists that has an inappropriate correspondence between the model of refrigerator 100 and the parameter information PR, which increases the workload. In contrast, this embodiment uses update software (update information SA) in which parameter information PR for multiple models (e.g., all models) is embedded in control software SF that is common to multiple models.

[0099] 10, parameters #01_pv0 to #09_pv0 of version 0 of all models A600F to B450G are used in combination with common control software sv0. Also, parameters #01_pv1 to #09_pv1 of version 1 of models A600F to B450G are used in combination with common control software sv0. Similarly, parameters #01_pv2 to #09_pv2 of version 2 of models A600F to B450G are used in combination with common control software sv0, and parameters #01_pv3 to #09_pv3 of version 3 of models A600F to B450G are used in combination with common control software sv1. Parameters #01_pv4 to #09_pv4 of version 4 of models A600F to B450G are used in combination with common control software sv2, parameters #01_pv5 to #09_pv5 of version 5 of models A600F to B450G are used in combination with common control software sv2, and parameters #01_pv6 to #09_pv6 of version 6 of models A600F to B450G are used in combination with common control software sv3.

[0100] 19 is a diagram for explaining software updates in the second embodiment. For example, version 0 update software SFT_v0 (update information SA) is generated from control software sv0 (control software SF1 common to multiple models) and parameters #01_pv0 to #09_pv0 (multiple pieces of parameter information PR corresponding to multiple models). Similarly, version 1 update software SFT_v1 (update information SA) is generated from control software sv0 (control software SF1 common to multiple models) and parameters #01_pv1 to #09_pv1 (multiple pieces of parameter information PR corresponding to multiple models). Version 2 update software SFT_v2 (update information SA) is generated from control software sv0 (control software SF1 common to multiple models) and parameters #01_pv2 to #09_pv2 (multiple pieces of parameter information PR corresponding to multiple models). Similarly, update software SFT_v3 for version 3, update software SFT_v4 for version 4, update software SFT_v5 for version 5, and update software SFT_v6 for version 6 are generated.

[0101] The parameter information PR for updating may use the parameter data as is, or may use the difference obtained by merging the history as described above.

[0102] FIG. 20 shows the process of updating the software of model A600F to version 6. When updating the software of model A600F to version 6, user U downloads update software SFT_v6 (update information SA) for version 6. As shown in FIG. 19, update software SFT_v6 includes control software sv3 (control software SF1) common to each model and model-specific parameters #01_pv6 to #09_pv6 (plurality of parameter information PR). Of the model-specific parameters #01_pv6 to #09_pv6, parameter #01_pv6 corresponding to model A600F is an example of "second information." Of the model-specific parameters #01_pv6 to #09_pv6, parameters #02_pv6 to #09_pv6 corresponding to models other than model A600F are each an example of "third information."

[0103] When update software SFT_v6 is downloaded, control unit 111 determines the model of refrigerator 100 in which control unit 111 is installed based on a discrimination voltage obtained from the series connection of resistors R1 and R2 and resistors R3 and R4, selects parameter information PR corresponding to the determined model from parameters #01_pv6 to #09_pv6 for each model, and updates parameter information PR used for control based on the selected parameter information PR. For example, if the discrimination voltages are V1=0 [V] and V2=0 [V], control unit 111 determines that the model is A600F from FIG. 6.

[0104] In this example, the update software contains parameters for all models. Therefore, the update software to be downloaded is compatible with all models. This eliminates registration errors in server 200 and makes verification work relatively simple. Furthermore, standardizing the update software for updates reduces the human workload and human error, contributing to the prevention of an increase in development resources.

[0105] Note that parameter information PR may be different depending on the functions of refrigerator 100. When a function on refrigerator control software SF1 is enabled, function information (functions assigned to refrigerator 100 at that time (functions whose use is not restricted)) is written using an area other than the parameters in EEPROM 102. Server 200 provides update software (update information SA) that includes rewrite control software SF2 and parameter information PR for realizing all functions that can be assigned to refrigerator 100. When control is switched to rewrite control software SF2 by rollback, control unit 111 reads the function information stored in EEPROM 102. Then, control unit 111 sets parameter information PR for realizing a corresponding function from multiple pieces of parameter information PR for realizing all functions that can be assigned to refrigerator 100 in EEPROM 102. This allows parameter information PR corresponding to each function to be reflected in EEPROM 102, and refrigerator control can be returned to by rollback.

[0106] Furthermore, for example, by preparing update software (update information SA) including rewrite control software SF2 and a plurality of pieces of parameter information PR corresponding to the external environment of the place where refrigerator 100 is installed, such as season (summer (compatible with high temperature and high humidity), rainy season (compatible with high humidity), winter (compatible with low temperature and low humidity)), region (Hokkaido, Okinawa, Sea of ​​Japan side, Pacific Ocean side, Ogasawara Islands), and topography (plain, highland, bay area), and by writing information about the season and region using an area other than the parameters in EEPROM 102 when a function on the refrigerator control software SF1 side is enabled, it is possible to set parameter information PR corresponding to the combination of season, region, and topography and control refrigerator 100.

[0107] The preparation of different parameter information PR depending on the function of the refrigerator 100 or the external environment may be realized in the first embodiment and / or the second embodiment.

[0108] (advantage) The first and second embodiments relate to refrigerator 100, which includes a storage unit (ROM 112, RAM 113, EEPROM 102), a control unit 111 that can control functions of the refrigerator, and a communication unit 103 that can acquire information from an external device. The storage unit includes a first storage unit (ROM 112) that stores first information (control software SF1) that is common to a plurality of models and can be used for control by control unit 111, and a second storage unit (EEPROM 102) that stores second information (parameter information PR) that is different depending on the model and can be used for control by control unit 111 in combination with the first information. At least one of the first information (control software SF1) and the second information (parameter information PR) can be updated by update information SA (update software) newly acquired from an external device by communication unit 103. The first storage unit (ROM 112) stores processing information (rewrite control software SF2) for executing a process for writing the second information (parameter information PR) included in the update information SA (update software) to the second storage unit (EEPROM 102). According to this embodiment, the first information (control software) is shared among a plurality of models, thereby improving the convenience of management.

[0109] In the first embodiment, the control unit 111 acquires information (update software SFT#01_v0 to SFT#09_v06) including first information (control software SF1) and second information (parameter information PR) as update information SA, and updates the information. According to this embodiment, the first information (control software SF1) and the second information (parameter information PR) can be acquired in a predetermined combination, and the first information (control software SF1) and the second information (parameter information PR) can be updated by a single download.

[0110] In the second embodiment, the control unit 111 acquires, as the update information SA, information (update software SFT_v1 to SFT_v6) including first information (control software SF1), second information (parameter information PR), and third information (parameter information PR corresponding to another model) that can be used to control a model different from that of the refrigerator 100, and updates the information. According to the present embodiment, it is possible to prevent human error in registering update information SA with an incorrect combination of the first information and the second information in the server 200.

[0111] In the first and second embodiments, the second information (parameter information PR) included in the update information SA (update software) newly acquired from the outside by the communication unit 103 includes difference information, which is a portion that differs from at least a portion of the second information stored in the second storage unit (EEPROM 102). The control unit 111 updates the second information (parameter information PR) using the difference information. According to the present embodiment, the amount of data can be reduced by using the difference information to update the second information (parameter information PR).

[0112] In the second embodiment, when executing a process for writing second information (parameter information PR) included in update information SA (update software) to the second storage unit (EEPROM 102), control unit 111 identifies the second information (parameter information PR) based on a characteristic (e.g., a discrimination voltage) unique to refrigerator 100. According to this embodiment, the model of refrigerator 100 can be identified based on the characteristic of refrigerator 100, and the second information (parameter information PR) corresponding to the model can be identified.

[0113] In the first and second embodiments, the first storage unit (ROM 112) has a first storage area (area 112a) and a second storage area (area 112b). When updating information, the control unit 111 writes the updated information to one of the first or second storage area (area 112a or 112b) and stores the information before the update in the other of the first or second storage area. According to this embodiment, by storing the information before the update in one of the first or second storage area (area 112a or 112b), it is possible to restore the information before the update in the event of a malfunction or the like.

[0114] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents. [Explanation of symbols]

[0115] 100...refrigerator, 101...control device, 102...EEPROM, 103...communication unit, 106...control circuit unit, 107...electronic components, 110...main microcomputer, 111...control unit, 112...ROM, 113...RAM.

Claims

1. A refrigerator, A memory unit; a control unit capable of controlling functions of the refrigerator; a communication unit capable of acquiring information from an external device; Equipped with The storage unit a first storage unit that stores first information that is common to a plurality of models and can be used for control by the control unit; a second storage unit that stores second information that varies depending on a model, a function, a season, or an external environment of a place where the refrigerator is installed, and that can be used for control by the control unit in combination with the first information; Including, at least one of the first information and the second information can be updated by update information newly acquired from an external source by the communication unit; the update information includes both the first information and the second information, refrigerator.

2. The second information is information that differs depending on the model and can be combined with the first information to be used for control by the control unit. The refrigerator according to claim 1.

3. the update information includes both the first information and the second information even when only one of the first information and the second information is updated; The refrigerator according to claim 1 or 2.

4. When the update information is newly acquired from an external device by the communication unit, the first information stored in the first storage unit is updated with the first information included in the update information. The refrigerator according to claim 1 or 2.

5. the update information includes the first information, the second information, and third information, the second information is information that differs depending on the model and can be used to control the refrigerator in combination with the first information, the third information is information that varies depending on the model and can be combined with the first information to be used to control a model different from the refrigerator, the control unit identifies the second information included in the update information based on a characteristic unique to the refrigerator or information externally obtained by the communication unit. The refrigerator according to claim 1 or 2.

6. the second information included in the update information is difference information indicating a portion different from the second information previously stored in the second storage unit, the control unit obtains information to be used for control by the control unit based on the second information previously stored in the second storage unit and the difference information. The refrigerator according to claim 1 or 2.

7. the second information is information that varies depending on the function and that can be combined with the first information to be used for control by the control unit; The refrigerator according to claim 1.

Images