Home appliance system, server device, terminal device, and computer program

Abstract

To provide a home appliance system, a server device, a terminal device, and a computer program, capable of improving convenience of applications that provide remote control functions for home appliances.SOLUTION: A home appliance system according to an embodiment includes a server device and a terminal device. The server device stores a plug-in that provides a predetermined function or information for an application that remotely controls or monitors a home appliance. The terminal device executes the application, and downloads the plug-in from the server device when the plug-in that provides the function or information required by the running application is not stored in the own device. When a plug-in before updating is in use by the application, the terminal device downloads a plug-in after updating from the server apparatus, and replaces the plug-in before updating with the plug-in after updating after the use of the plug-in before updating is completed.SELECTED DRAWING: Figure 2

Description

[Technical field]

[0001] The present invention relates to a home appliance system, a server device, a terminal device, and a computer program. [Background technology]

[0002] Traditionally, home appliances have been remotely controlled using applications on smartphones, and the remote control function was generally provided by a different application for each home appliance (type and model number). However, in recent years, there has been a shift to a system where remote control functions for home appliances of different types and model numbers are provided by a single application. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6465198 [Patent Document 2] Special Publication No. 2017-534094 [Patent Document 3] JP 2014-59717 A [Patent Document 4] Special Publication No. 2017-530496 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when one application enables remote control of multiple home appliances, a user who has only a few home appliances to operate may end up installing an application that includes a lot of data on home appliances that the user does not operate, which may consume more storage space than necessary. In addition, an application that enables remote control of multiple home appliances may need to be updated every time a new home appliance is released, which may result in frequent downloading and installation of the application. Thus, conventional applications that provide a function for remote control of home appliances have not always been very convenient for users.

[0005] The problem to be solved by the present invention is to provide a home appliance system, a server device, a terminal device, and a computer program that can improve the convenience of an application that provides a remote control function for a home appliance. [Means for solving the problem]

[0006] The home appliance system of the embodiment has a server device and a terminal device. The server device stores a plug-in that provides a predetermined function or information to an application that remotely controls or monitors a home appliance. The terminal device is a terminal device that executes the application, and when a plug-in that provides a function or information required by the application being executed is not stored in the terminal device, the terminal device downloads the plug-in from the server device. When an unupdated plug-in is being used by the application, the terminal device downloads an updated plug-in from the server device, and replaces the unupdated plug-in with the updated plug-in after use of the unupdated plug-in has ended. The home appliance system of the embodiment has a server device and a terminal device. The server device stores a plug-in that provides a predetermined function or information to an application that remotely controls or monitors a home appliance. The terminal device executes the application, and when a plug-in that provides a function or information required by the application being executed is not stored in the terminal device, the terminal device downloads the plug-in from the server device. The terminal device executes a process of inquiring about whether a plug-in has been updated and a process of downloading the plug-in in response to the result of the inquiry, when the application is not being used by a user. The home appliance system of the embodiment has a server device and a terminal device. The server device stores a plug-in that provides a predetermined function or information to an application that remotely controls or monitors a home appliance. The terminal device executes the application, and when a plug-in that provides a function or information required by the application being executed is not stored in the terminal device, the terminal device downloads the plug-in from the server device. When a plug-in is no longer used for remote control of any home appliance due to the registration of any home appliance being deleted from the application, the terminal device deletes the plug-in stored in the terminal device. [Brief description of the drawings]

[0007] [Figure 1] FIG. 2 is a system configuration diagram showing a specific example of the system configuration of the home appliance system according to the first embodiment. [Diagram 2] FIG. 2 is a functional block diagram showing a specific example of a functional configuration of a remote control terminal according to the first embodiment. [Diagram 3] FIG. 2 is a functional block diagram showing a specific example of the functional configuration of a remote control server according to the first embodiment. [Figure 4] 5 is a diagram showing a specific example of management information of a plug-in according to the first embodiment. [Diagram 5]4 is a sequence diagram showing a specific example of a process flow in which the remote control terminal of the first embodiment remotely controls a target device. [Figure 6] 4 is a sequence diagram showing a specific example of a process flow in which the remote control terminal of the first embodiment remotely controls a target device. [Figure 7] 4 is a sequence diagram showing a specific example of a process flow in which the remote control terminal of the first embodiment remotely controls a target device. [Figure 8] 3A to 3C are diagrams showing specific examples of operation screens and their screen transitions displayed on the remote control terminal of the first embodiment. [Figure 9] 5A to 5C are diagrams showing specific examples of operation screens and their screen transitions used when deleting a registered home electric device from a remote control application in the remote control terminal of the first embodiment. [Figure 10] 4A to 4C are diagrams showing specific examples of operation screens and their screen transitions used when adding a service related to a registered home appliance to a remote control application in the remote control terminal of the first embodiment. [Figure 11] 4A to 4C are diagrams showing specific examples of operation screens and their screen transitions used when executing a demo mode in the remote control terminal of the first embodiment. [Figure 12] 5A to 5C are diagrams showing a specific example of an operation screen and its screen transition used when selecting a plug-in download method on the remote control terminal of the first embodiment. [Figure 13] FIG. 11 is a system configuration diagram showing a specific example of the system configuration of a home electric appliance system according to a second embodiment. [Figure 14] FIG. 11 is a functional block diagram showing a specific example of the functional configuration of a remote control terminal according to the second embodiment. [Figure 15] FIG. 11 is a functional block diagram showing a specific example of the functional configuration of a remote control server according to the second embodiment. [Figure 16] FIG. 11 is a sequence diagram showing a specific example of a process flow in which a remote control unit updates a downloaded plug-in in the home electric appliance system of the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] (First embodiment) FIG. 1 is a system configuration diagram showing a specific example of the system configuration of a home appliance system in the first embodiment. A home appliance system 100 shown in FIG. 1 is a specific example of the home appliance system in the first embodiment, and is a system that enables a home appliance 1 in a user's home to be remotely controlled from a remote control terminal 2. The home appliance system 100 includes one or more home appliances 1, a remote control terminal 2, an application server 3, and a remote control server 4. The home appliance 1 is a home appliance that is to be remotely controlled (hereinafter referred to as a "target appliance"). FIG. 1 shows home appliances 1-1 to 1-5 as specific examples of the one or more home appliances 1.

[0009] For example, the home appliance 1-1 is a refrigerator, and the home appliance 1-2 is a lighting device. The home appliance 1-3 is an air conditioner, and the home appliance 1-4 is a television. The home appliance 1-5 is a washing machine. These are examples of home appliances that are target devices, and the target device is not limited to the home appliance 1 shown in FIG. 1. The home appliance 1 may be any home appliance other than those illustrated in FIG. 1 as long as it can operate in cooperation with a remote control application executed on the remote control terminal 2. The home appliance 1 has a wireless communication function such as a wireless LAN (Local Area Network) and is connected to a router 51 so as to be able to wirelessly communicate with the router 51. The router 51 is connected to a WAN (Wide Area Network) 52, and the home appliance 1 can communicate with the application server 3 and the remote control server 4 via the router 51 and the WAN 52. The home appliance 1 may be configured to communicate with the application server 3 and the remote control server 4 via a wire (for example, a power line) provided in the user's home and the WAN 52.

[0010] The remote control terminal 2 is a terminal device used to remotely control the home appliance 1. For example, the remote control terminal 2 is configured using an information processing device such as a smartphone, a tablet terminal, a mobile phone terminal, or a notebook computer. Specifically, an application (hereinafter referred to as a "remote control app") that provides a remote control function (including a remote monitoring function) of the home appliance 1 is installed in the remote control terminal 2. By executing the remote control app, the remote control terminal 2 can instruct a specified operation to a specified home appliance 1. The remote control app is a dedicated program that realizes remote control of the home appliance 1, and is an executable program stored in the remote control terminal 2. For example, by executing the remote control app, a user can configure the operation settings of the home appliance 1 from outside the home, and receive the operating state of the home appliance 1 from the remote control server 4 or the like by push notification.

[0011] The application server 3 is a distribution server of a remote control application. The application server 3 distributes the remote control application in response to a request from the remote control terminal 2. If the remote control application is not installed in the remote control terminal 2 used by the user, the user downloads the remote control application from the application server 3 and installs it in the remote control terminal 2.

[0012] The remote control server 4 is a server device that stores plug-ins that provide a predetermined function or information to the remote control application. In response to a request from the remote control terminal 2, the remote control server 4 distributes the requested plug-in to the remote control terminal 2. The plug-ins used by the remote control application are roughly divided into a device registration plug-in used when the remote control application registers (or deletes) a target device, and a device operation plug-in used when remotely controlling the target device. The remote control application can operate without necessarily requiring all plug-ins by loading a plug-in when the above function or information becomes necessary. The plug-in referred to here is a part of a program that realizes the remote control function of the home appliance 1, and a part or all of the plug-in is downloaded at a timing different from the timing when the remote control application is downloaded.

[0013] FIG. 2 is a functional block diagram showing a specific example of the functional configuration of the remote control terminal 2 in the first embodiment. The remote control terminal 2 includes a CPU (Central Processing Unit), a memory, an auxiliary storage device, and the like, which are connected by a bus, and executes a program. The remote control terminal 2 functions as a device including a communication unit 21, an application storage unit 22, a plug-in storage unit 23, an input unit 24, a display unit 25, a control unit 26, and a remote control unit 27 by executing the program. All or part of the functions of the remote control terminal 2 may be realized using hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array). The program may be recorded in a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built into a computer system. The program may be transmitted via an electric communication line.

[0014] The communication unit 21 includes a wireless communication interface that wirelessly connects the remote control terminal 2 to the router 51. The remote control terminal 2 is communicably connected to the application server 3 and the remote control server 4 via the router 51. Note that the communication unit 21 may be configured to communicate with the application server 3 and the remote control server 4 directly via the WAN 52 without via the router 51.

[0015] The application storage unit 22 and the plug-in storage unit 23 are functional units that store various information necessary for the operation of the remote control terminal 2. The application storage unit 22 and the plug-in storage unit 23 are configured using storage devices such as a magnetic hard disk device or a semiconductor storage device. Specifically, the application storage unit 22 stores a remote control application acquired from the application server 3. The plug-in storage unit 23 stores a plug-in of the remote control application acquired from the remote control server 4.

[0016] The input unit 24 has a function of inputting information to the remote control terminal 2 in response to a user's operation. For example, the input unit 24 is configured using input devices such as a touch panel, a mouse, and a keyboard. Specifically, the input unit 24 outputs input information for an operation to start a remote control app to the control unit 26, and outputs input information for an operation on the started remote control app to the remote control unit 27.

[0017] The display unit 25 has a function of displaying various information stored in the remote control terminal 2. For example, the display unit 25 is configured using a display device such as a CRT (Cathode Ray Tube), a liquid crystal display, an organic EL (Electro-Luminescence) display, etc. For example, the display unit 25 displays various operation screens for remotely controlling the home appliance 1 using a remote control application.

[0018] The control unit 26 has a function of controlling the operation of the remote control terminal 2. For example, the control unit 26 generates an execution environment for the remote control application on the memory by reading and executing an execution file for the remote control application from the application storage unit 22. Hereinafter, the execution environment for the remote control application generated on the memory is referred to as a remote control unit 27. In addition, the control unit 26 deletes the remote control unit 27 from the memory when the remote control application is terminated.

[0019] The remote control unit 27 has a function of remotely controlling the home appliance 1 in response to an input operation by the user. Specifically, the remote control unit 27 is an execution environment of a remote control app generated in a memory by the execution of the remote control app by the control unit 26. The remote control unit 27 displays various operation screens on the display unit 25 and accepts input operations by the user on the operation screens. The remote control unit 27 has a function of registering a target device in the remote control app in response to an input operation by the user on the operation screen, and of instructing the registered home appliance 1 to execute various operations desired by the user.

[0020] FIG. 3 is a functional block diagram showing a specific example of the functional configuration of the remote control server 4 in the first embodiment. The remote control server 4 includes a CPU, a memory, an auxiliary storage device, and the like, which are connected by a bus, and executes a program. The remote control server 4 functions as a device including a communication unit 41, a plug-in information storage unit 42, and a plug-in providing unit 43 by executing the program. All or part of the functions of the remote control server 4 may be realized using hardware such as an ASIC, a PLD, or an FPGA. The program may be recorded in a computer-readable recording medium. The computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built into a computer system. The program may be transmitted via an electric communication line.

[0021] The communication unit 41 includes a communication interface that connects the remote control server 4 to the WAN 52. The remote control server 4 communicates with the remote control terminal 2 via the WAN 52 and the router 51.

[0022] The plug-in information storage unit 42 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The plug-in information storage unit 42 stores plug-in information. The plug-in information includes data of a plug-in that provides a remote control application with a function or information related to the remote control of the home appliance 1, and management information of the plug-in.

[0023] In response to a request from the remote control terminal 2, the plug-in providing unit 43 acquires the requested plug-in from the plug-in information storage unit 42, and distributes the acquired plug-in to the remote control terminal 2 that originated the request.

[0024] FIG. 4 is a diagram showing a specific example of management information of a plug-in in the first embodiment. FIG. 4 is a diagram showing an example of a table showing management information (hereinafter referred to as a "management information table"). The management information table has one record (hereinafter referred to as a "management information record") for each combination of a plug-in ID, a device ID, and a device ID. The management information record has values ​​of a plug-in ID, a function ID, a device ID, and version information. The plug-in ID is identification information of a plug-in. The function ID is identification information of a function provided by a plug-in identified by the plug-in ID. The device ID is identification information of a type of home appliance 1. For example, a product model number can be used as a device ID because it includes information indicating the type of home appliance. The version information is information indicating the version of a function identified by the plug-in ID and the function ID.

[0025] 4, management information records R1 and R2 indicate that the function identified by "F001" is a function related to remote control of home appliance 1 identified by "DEV001" and "DEV002", that the function is provided by a plug-in identified by "P001", and that the version of the plug-in is "1.01". Based on such management information, plug-in providing unit 43 can identify the plug-in requested by remote control terminal 2.

[0026] Figures 5 to 7 are sequence diagrams showing a specific example of the process flow when the remote control terminal 2 of the first embodiment remotely controls a target device. Also, Figure 8 is a diagram showing how the operation screen displayed on the remote control terminal 2 transitions in accordance with the series of processes shown in Figures 5 to 7. The process flow shown in Figures 5 to 7 will be described below with reference to the screen transitions in Figure 8 as appropriate.

[0027] [Terms of Use screen~Top screen] First, in the remote control terminal 2, the remote control unit 27 displays a terms of use screen (step S101). Here, the terms of use screen is a screen that requests the user of the remote control application to agree to the terms of use of the remote control application. Fig. 8(A) shows an example of the terms of use screen in which a text box T01 showing the contents of the terms of use and an agreement button B01 for receiving an input of an operation indicating agreement are arranged.

[0028] In this case, the remote control unit 27 accepts an input of pressing the Agree button B01 as an example of a condition for transitioning the terms of use screen to the next operation screen (step S102). At this time, the remote control unit 27 judges whether or not a plug-in that provides a display function of a top screen to be displayed after the terms of use screen is stored in the device (step S103). If it is judged that the plug-in is not stored in the device (step S103-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S104). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that originated the request (step S105).

[0029] Specifically, in step S104, the remote control unit 27 notifies the remote control server 4 of the device ID of its own device and the function ID of the function for displaying the top screen. That is, the function ID notified here is the function ID of the function required for the next operation, and is the function that has become necessary in response to the user's operation (step S102). The plug-in providing unit 43 refers to the plug-in management information table and selects a management information record having the device ID and function ID values ​​notified from the remote control terminal 2. The plug-in providing unit 43 obtains from the plug-in information storage unit 42 the plug-in identified by the plug-in ID value of the selected management information record, and transmits it to the remote control terminal 2 that made the request.

[0030] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying the top screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the top screen using the plug-in acquired from the remote control server 4 (step S106), and accepts input of operations for the top screen. Note that, if it is determined in step S103 that the plug-in is stored in the remote control terminal 2 (step S103-YES), the remote control unit 27 displays the top screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0031] [Top page - User registration screen] Here, the top screen is a screen that accepts input of an operation to instruct the remote control application to execute one of the processes of new user registration process, registered user login process, and demo mode. Fig. 8(B) shows an example of the top screen on which a new registration button B02 that accepts input of an instruction to execute a new user registration process, a login button B03 that accepts input of an instruction to execute a registered user login process, and a demo mode button B04 that accepts input of an instruction to execute the demo mode are arranged.

[0032] In this case, the remote control unit 27 accepts an input of pressing the New Registration button B02 as an example of a condition for transitioning the top screen to the next operation screen (step S107). At this time, the remote control unit 27 judges whether or not a plug-in providing a display function of a user registration screen to be displayed after the top screen is stored in the device itself (step S108). When it is judged that the plug-in is not stored in the device itself (step S108-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S109). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that made the request (step S110). Note that the method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S110 is the same as that in step S105.

[0033] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying a user registration screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the user registration screen using the plug-in acquired from the remote control server 4 (step S111), and accepts input of operations for the user registration screen. Note that, if it is determined in step S108 that the plug-in is stored in the remote control terminal 2 (step S108-YES), the remote control unit 27 displays the user registration screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0034] [User registration screen ~ Top page] Here, the user registration screen is a screen that accepts input of information required for user registration for the remote control application. Fig. 8(C) shows an example of the user registration screen that has a text box T02 that accepts input of information required for user registration and a registration button B05 that accepts input of an instruction to execute a registration process for the entered information.

[0035] In this case, the remote control unit 27 accepts an input of pressing the registration button B05 as an example of a condition for transitioning the user registration screen to the next operation screen (step S112). At this time, the remote control unit 27 judges whether or not a plug-in providing a display function of a top screen to be displayed after the user registration screen is stored in the device (step S113). In the operation example of Figs. 5 to 7, since the plug-in providing the display function of the top screen has already been acquired in step S104, in this case, the remote control unit 27 judges that the plug-in is stored in the device (step S113-YES). Then, the remote control unit 27 displays the top screen using the acquired plug-in (step S114) and accepts an input of an operation for the top screen.

[0036] If the plug-in is not stored in the remote control device when step S113 is executed for some reason (NO in step S113), the remote control unit 27 may request the remote control server 4 to provide the plug-in (step S115). In this case, the plug-in providing unit 43 in the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that made the request (step S116). The method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S116 is the same as that in step S105.

[0037] [Top screen - Function screen] In this case, the remote control unit 27 accepts an input of pressing the login button B03 as an example of a condition for transitioning the top screen to the next operation screen (step S117). At this time, the remote control unit 27 judges whether or not a plug-in providing a display function of a functional screen to be displayed after the top screen is stored in the device itself (step S118). When it is judged that the plug-in is not stored in the device itself (step S118-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S119). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that is the request source (step S120). Note that the method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S120 is the same as that in step S105.

[0038] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying the functional screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the functional screen using the plug-in acquired from the remote control server 4 (step S121), and accepts an input of an operation for the functional screen. Note that, if it is determined in step S118 that the plug-in is stored in the remote control terminal 2 (step S118-YES), the remote control unit 27 displays the functional screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0039] [Function screen ~ Home appliance addition screen] Here, the function screen is a screen that accepts input of the selection of various functions related to the remote control of the home appliance 1 to the remote control application. Fig. 8(E) shows an example of a function screen on which an add home appliance button B06 that accepts an input of an operation to instruct the remote control application to execute a registration process of a target appliance, a service menu button B07 that accepts an input of an operation to display a menu screen (service screen) related to a function (hereinafter referred to as a "service") that causes the registered home appliance 1 to perform a predetermined operation, and a menu button B08 that accepts an input of an operation to instruct the display of the menu screen are arranged.

[0040] In this case, the remote control unit 27 accepts an input of pressing the home appliance addition button B06 as an example of a condition for transitioning the function screen to the next operation screen (step S122). At this time, the remote control unit 27 judges whether or not a plug-in providing a display function of a home appliance addition screen to be displayed next to the function screen is stored in the own device (step S123). When it is judged that the plug-in is not stored in the own device (step S123-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S124). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that originated the request (step S125). Note that the method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S125 is the same as that in step S105.

[0041] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying the home appliance addition screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the home appliance addition screen using the plug-in acquired from the remote control server 4 (step S126), and accepts an input of an operation on the home appliance addition screen. Note that, if it is determined in step S123 that the plug-in is stored in the remote control terminal 2 (step S123-YES), the remote control unit 27 displays the home appliance addition screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0042] [Add Home Appliances screen - Air Conditioner Function Registration Screen] Here, the home appliance addition screen is a screen for receiving input for an operation of selecting the type of home appliance 1 to be added to the remote control app. Fig. 8(F) shows an example of the home appliance addition screen on which a refrigerator button B09 for adding a refrigerator as a target appliance, a washing machine button B10 for adding a washing machine as a target appliance, an air conditioner button B11 for adding an air conditioner as a target appliance, and a microwave button B12 for adding a microwave oven as a target appliance are arranged.

[0043] In this case, the remote control unit 27 accepts an input of pressing the air conditioner button B11 as an example of a condition for transitioning the home appliance addition screen to the next operation screen (step S127). At this time, the remote control unit 27 determines whether or not a plug-in that provides a display function of a device connection screen to be displayed next to the home appliance addition screen is stored in the device itself (step S128). Note that the device connection screen differs depending on the type of home appliance 1, and the display function is to display a device connection screen corresponding to the selected home appliance 1. If it is determined that the plug-in is not stored in the device itself (step S128-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S129). At this time, the remote control unit 27 notifies the remote control server 4 of the device ID indicating the type of the selected home appliance 1 and the function ID of the function of displaying the device connection screen together with the request for the plug-in. In response to this request, the plug-in providing unit 43 in the remote control server 4 obtains a plug-in corresponding to the notified device ID and function ID from the plug-in information storage unit 42, and transmits the obtained plug-in to the remote control terminal 2 that originated the request (step S130).

[0044] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying the device connection screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the device connection screen using the plug-in acquired from the remote control server 4 (step S131), and accepts input of operations for the device connection screen. Note that, if it is determined in step S128 that the plug-in is stored in the remote control terminal 2 (step S128-YES), the remote control unit 27 displays the device connection screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0045] [Device connection screen - Add home appliance screen] Here, the device connection screen is a screen that accepts input of an operation to wirelessly connect the remote control terminal 2 that executes the remote control app to the air conditioner of the target device. Fig. 8(G) shows an example of the device connection screen that has a text box T03 that accepts input of information (hereinafter referred to as "device information") required to wirelessly connect the air conditioner of the target device to the router 51, and a connection button B13 that accepts input of an operation to instruct to wirelessly connect to the air conditioner of the target device using the input device information. For example, a device ID for identifying the type of home electric appliance 1 is input into the text box T03.

[0046] In this case, the remote control unit 27 accepts an input of pressing the connection button B13 as an example of a condition for transitioning the device connection screen to the next operation screen (step S132), and accordingly displays a connection method selection screen (step S133). Here, the connection method selection screen is a screen for accepting an input of an operation for selecting a connection method for connecting the remote control terminal 2 to the added air conditioner. Fig. 8(H) shows an example of a home appliance connection screen on which an easy connection button B14 for selecting a simple connection method such as the AOSS (registered trademark) method or the WPS (Wi-Fi (registered trademark) Protected Setup) method as one of the connection method options, and a manual connection button B15 for selecting a manual connection method are arranged.

[0047] In this case, the remote control unit 27 accepts an input of pressing the simple connection button B14 as an example of a condition for transitioning the home appliance connection screen to the next operation screen (step S134). At this time, the remote control unit 27 judges whether or not a plug-in providing a display function of a simple connection screen to be displayed next to the home appliance connection screen is stored in the own device (step S135). The simple connection screen here also differs depending on the type of home appliance 1, and its display function is to display a simple connection screen corresponding to the selected home appliance 1. If it is judged that the plug-in is not stored in the own device (step S135-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S136). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that originated the request (step S137). Note that the method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S137 is the same as that in step S130.

[0048] Next, in the remote control terminal 2, the remote control unit 27 receives a plug-in that provides a function for displaying the simple connection screen from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the simple connection screen using the plug-in acquired from the remote control server 4 (step S138), and accepts input of operations for the simple connection screen. Note that, if it is determined in step S135 that the plug-in is stored in the remote control terminal 2 (step S135-YES), the remote control unit 27 displays the simple connection screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0049] [Easy connection screen ~ Function screen] Here, the simple connection screen is a screen that accepts input of an instruction to execute a connection using a simple connection method. Fig. 8(I) shows an example of the simple connection screen on which a text box T04 (which may display an image) that displays the execution procedure for a connection using the simple connection method and a Next button B16 for inputting an instruction to execute a connection are arranged.

[0050] In this case, the remote control unit 27 receives input of pressing the Next button B16 as an example of a condition for transitioning the simple connection screen to the next operation screen (step S139), and in response to this, executes connection between the air conditioner and the router 51 and displays a connection completion screen (step S140). Here, the connection completion screen is a screen that displays that the connection between the air conditioner added on the home appliance addition screen and the router 51 has been completed, and that the air conditioner can now be controlled from the remote control server 4. Fig. 8(J) shows an example of the connection completion screen on which a text box T05 that displays that the connection with the air conditioner has been completed and a Next button B17 that receives input of an operation for transitioning the connection completion screen to the next screen are arranged.

[0051] In this case, the remote control unit 27 accepts an input of pressing the Next button B17 as an example of a condition for transitioning the connection completion screen to the next operation screen (step S141). At this time, the remote control unit 27 judges whether or not a plug-in (air conditioner operation plug-in) that provides a function for displaying the added air conditioner operation screen is stored in the remote control unit 27 (step S142). If it is judged that the plug-in is not stored in the remote control unit 27 (step S142-NO), the remote control unit 27 requests the remote control server 4 to provide the plug-in (step S143). In response to this request, the plug-in providing unit 43 in the remote control server 4 acquires a plug-in corresponding to the request from the plug-in information storage unit 42, and transmits the acquired plug-in to the remote control terminal 2 that originated the request (step S144). Note that the method in which the remote control server 4 acquires the plug-in corresponding to the request from the plug-in information storage unit 42 in step S144 is the same as that in step S105.

[0052] Next, in the remote control terminal 2, the remote control unit 27 receives the air conditioner operation plug-in from the remote control server 4, and records the received plug-in in the plug-in storage unit 23. The remote control unit 27 displays the function screen again (step S145), and accepts input of operations for the function screen. Note that, if it is determined in step S142 that the plug-in is stored in the remote control terminal 2 (step S142-YES), the remote control unit 27 displays the function screen using the plug-in stored in the remote control terminal 2, without requesting the remote control server 4 to provide the plug-in.

[0053] [Function screen - Air conditioner operation screen] As shown in Fig. 8(K), in addition to the add home appliance button B06 and the service menu button B07 arranged on the function screen of Fig. 8(E), an air conditioner button B18 for receiving an input for an operation to select the newly added air conditioner as a target device is arranged on the function screen here. This air conditioner button B18 is displayed by generating a function screen using an air conditioner operation plug-in acquired by the remote control unit 27 from the remote control server 4 and a plug-in for displaying an already acquired function screen.

[0054] In this case, the remote control unit 27 accepts an input of pressing the air conditioner button B18 as an example of a condition for transitioning the function screen to the next operation screen (step S146). In response to this, the remote control unit 27 displays an operation screen for the air conditioner (step S147). Note that the air conditioner operation screen also differs depending on the type of home appliance 1, and the display function displays the air conditioner operation screen corresponding to the selected home appliance 1. Fig. 8(L) shows an example of an air conditioner operation screen on which a power on button B19 that accepts an input for an operation to turn on the air conditioner, a power off button B20 that accepts an input for an operation to turn off the air conditioner, a set temperature change button B21 that accepts an input for an operation to change the set temperature of the air conditioner, and a timer setting button B22 that accepts an input for an operation to set the air conditioner's timer are arranged.

[0055] In this way, when an operation for transitioning the current operation screen to the next operation screen is input to the operation screen, the remote control unit 27 judges whether or not a plug-in required for executing the process instructed by the operation is stored in the device itself. If the plug-in is not stored in the device itself, the remote control unit 27 downloads the plug-in from the remote control server 4, and if the plug-in has already been downloaded, the remote control unit 2 executes the instructed process using the plug-in stored in the device itself. The remote control terminal 2 of the first embodiment thus configured only needs to store plug-ins that provide functions required for remote control of the target device (including registration of the target device), so that it is possible to reduce the capacity of the storage area required for the operation of the remote control app. Therefore, the remote control terminal 2 of the first embodiment can improve the convenience of the remote control app.

[0056] 8, each plug-in that displays each of the operation screens related to the registration of the home appliance 1 is an example of a device registration plug-in, and each plug-in that displays each of the operation screens related to the operation of the home appliance 1 is an example of a device operation plug-in. As shown in FIG. 4, one plug-in that becomes necessary in response to a user's operation may include only a program that realizes the required function (operation screen), or may include a program that realizes a function other than the required function.

[0057] Furthermore, the registration of the home appliance 1 for the remote control application may be storing information on the target appliance in the remote control terminal 2 that executes the remote control application, or may be storing information on the target appliance in the remote control server 4 that executes control instructions for the target appliance, or may be both. For example, the registration of the air conditioner in the example of FIG. 8 may be the remote control terminal 2 storing the appliance information input to the appliance connection screen of FIG. 8(G), or the remote control server 4 storing the appliance information acquired from the air conditioner that has become communicable through a network connection without going through the remote control terminal 2, or the appliance information of the air conditioner acquired from the remote control terminal 2. The registration of the air conditioner may be the storage of the appliance information when the appliance information acquired directly from the air conditioner by the remote control server 4 matches the appliance information of the air conditioner acquired from the remote control terminal 2. When such a registration of the home appliance 1 is performed, individual identification information (such as a serial number) of the home appliance 1 may be input to the appliance connection screen in the example of FIG. 8.

[0058] 5 to 8, the process flow in which the remote control unit 27 registers a new home appliance 1 as a target device in the remote control app has been mainly described, but the configuration in which a necessary plug-in is acquired from the remote control server 4 as needed when using a plug-in is similar for other plug-ins used by the remote control unit 27. Specific examples of the process flow for deleting a registered home appliance 1 and the process flow for adding a service to a registered home appliance 1 will be described below, but since the basic process flow is similar to the process flow for registering a home appliance 1 in the remote control app, only screen transitions are illustrated in Figs. 9 to 12, and detailed description will be omitted here.

[0059] 9 to 12, the shaded buttons represent the buttons to be pressed on each operation screen, and the arrows represent the flow of screen transitions caused by pressing the buttons. Similarly to Fig. 8, the shaded arrows represent that a plug-in required for providing a function or displaying information on a transition destination screen is downloaded from the remote control server 4 as appropriate when the plug-in is not stored in the remote control terminal 2 at the time the button is pressed.

[0060] FIG. 9 is a diagram showing a specific example of an operation screen and its screen transition used when a registered home appliance 1 is deleted from a remote control application in the remote control terminal 2 of the first embodiment. Specifically, FIG. 9 shows screen transitions from a function screen as a starting point until the registration of the home appliance 1 is deleted from the remote control application. When such an operation is performed, the remote control unit 27 deletes the registration of the selected home appliance 1 from the registration information of the remote control application, and deletes the plug-in downloaded for remote control of the home appliance 1 from the plug-in storage unit 23. Specifically, the remote control unit 27 does not delete a plug-in that is common regardless of the type of home appliance 1, such as a plug-in that displays a terms of use screen, but deletes a plug-in that displays a different operation screen depending on the type of home appliance 1. Here, it is assumed that the home appliance 1 to be deleted has been selected in advance by another operation.

[0061] In this manner, the related plug-in is deleted from the remote control terminal 2 in response to the deletion of the registration of the home appliance 1, thereby making it possible to prevent unnecessary data from accumulating in the remote control terminal 2. The remote control unit 27 may be configured not to delete a plug-in that may be used to remotely control another registered home appliance 1 among the plug-ins downloaded for the remote control of the home appliance 1. In this case, the remote control terminal 2 may determine whether or not the plug-in may be used to remotely control another home appliance 1 by storing management information similar to that shown in FIG. 4 in advance. The remote control unit 27 may also be configured to delete the plug-in after a predetermined time has elapsed since the registration of the home appliance 1 was deleted.

[0062] The service realized by the plug-in is not limited to a specific one. For example, the service may be a service that supports monitoring of a user of the home appliance 1. For example, if one home appliance 1 is registered, the service may be a service that supports monitoring of the user by the one home appliance 1, or if multiple home appliances 1 are registered, the service may be a service that supports monitoring of the user by the multiple home appliances 1.

[0063] FIG. 10 is a diagram showing a specific example of an operation screen and its screen transition used when adding a service related to a registered home appliance 1 to a remote control app in the remote control terminal 2 of the first embodiment. Specifically, FIG. 10 shows screen transitions from a service screen as a starting point to adding a new service to a registered home appliance 1 and displaying an execution screen for the added service. When such an operation is performed, the remote control unit 27 displays the specified service on the service screen so that the user can select the service. This allows the user to cause the home appliance 1 registered in the remote control app to perform a desired operation. Note that even in this case, the necessary plug-in is downloaded from the remote control server 4 as needed at the timing when it becomes necessary, so that it is possible to prevent the remote control terminal 2 from consuming more storage space than necessary.

[0064] FIG. 11 is a diagram showing a specific example of an operation screen and its screen transition used when executing the demo mode in the remote control terminal 2 of the first embodiment. The demo mode is a function that presents an example of the operation of an application to a user of a remote control application. The demo mode function may be provided to a user who has registered the user, the target device, and the service, or to a user who has not registered these. Specifically, FIG. 11 shows screen transitions starting from the top screen until the operation screen of an air conditioner in the demo mode is displayed. When such an operation is performed, the remote control unit 27 executes a demo of the application using a plug-in for the demo mode (demo mode plug-in). This allows the user to check the usability of the remote control application before starting to use the remote control application in earnest. Also, in this case, the necessary plug-in is downloaded from the remote control server 4 as needed at the timing when it becomes necessary, so that it is possible to prevent the remote control terminal 2 from consuming more storage space than necessary.

[0065] FIG. 12 is a diagram showing a specific example of an operation screen and its screen transition used when selecting a plug-in download method in the remote control terminal 2 of the first embodiment. Specifically, FIG. 12 shows a screen transition from a terms of use screen to a plug-in download method selection screen to a top screen. In this case, the remote control unit 27 downloads the plug-in from the remote control server 4 by the download method selected on the download setting screen, and then displays the top screen. By performing such processing, the user can select whether to download the plug-ins required when using the remote control app all at once (batch download) or to download the plug-ins in parts when they become necessary (partial download). By allowing the user to select the plug-in download method in this way, it is possible to prevent a loss of convenience for users who are not limited by the communication environment or memory capacity. Note that here, an example of transition from the terms of use screen to the download setting screen is shown, but the remote control app may be configured to transition from another screen to the download setting screen.

[0066] The remote control terminal 2 of the first embodiment configured as above downloads a plug-in from the remote control server 4 when the remote control app requires a function or information provided by a plug-in that is not stored in the remote control terminal 2. In addition, the remote control terminal 2 deletes the plug-in downloaded for remote control of the home appliance 1 in response to the home appliance 1 being deleted from the registration of the remote control app. Furthermore, since the remote control app of the first embodiment can download and use a required plug-in when it becomes necessary, there is no need to update the remote control app when incorporating a plug-in into the remote control app. With this configuration, it is possible to prevent the remote control terminal 2 from consuming more storage space than necessary, and to reduce the frequency of updating the remote control app, thereby improving the convenience of the remote control app.

[0067] Furthermore, the remote control terminal 2 of the first embodiment allows the user to select whether to download plug-ins in bulk or in parts. This makes it possible to improve the convenience for users who require divided downloads without impairing the convenience for users who do not require divided downloads.

[0068] <Modification> In FIG. 8, a plugin that provides a function of displaying an easy connection screen that explains how to establish a communication connection (hereinafter referred to as an "explanation plugin") has been described as an example of a plugin. However, the explanation plugin may be configured as a plugin for each type or model of home appliance 1 that explains different connection methods for each type or model of home appliance 1.

[0069] For example, the remote control app may be configured to be able to execute a first explanation plug-in that provides a function of explaining a communication connection method according to the type of the home appliance 1 to be registered, and may be configured to execute the function of the first explanation plug-in on the condition that information indicating the type of the home appliance 1 to be registered is acquired. In this case, the appliance registration plug-in may provide the remote control app with a function of receiving an input of an operation for selecting the type of the home appliance 1 to be registered.

[0070] Also, for example, the remote control app may be configured to be able to execute a second explanation plug-in that provides a function of explaining a communication connection method according to the model of the home appliance 1 to be registered, and configured to execute the function of the second explanation plug-in on the condition that information indicating the model of the home appliance to be registered is acquired. In this case, the device registration plug-in may provide the remote control app with a function of receiving an input of an operation for selecting the model of the home appliance 1 to be registered.

[0071] Second embodiment Fig. 13 is a system configuration diagram showing a specific example of the system configuration of the home appliance system 100a in the second embodiment. The home appliance system 100a differs from the home appliance system 100 in the first embodiment in that it includes a remote control terminal 2a instead of the remote control terminal 2, and further includes a remote control server 4a instead of the remote control server 4. The other configurations of the home appliance system 100a are the same as those of the home appliance system 100 in the first embodiment. Therefore, in Fig. 13, the same components as those in the home appliance system 100 are denoted by the same reference numerals as those in Fig. 1, and description thereof will be omitted.

[0072] Fig. 14 is a functional block diagram showing a specific example of the functional configuration of a remote control terminal 2a in the second embodiment. The remote control terminal 2a differs from the remote control terminal 2 in the first embodiment in that it includes a remote control unit 27a instead of the remote control unit 27. Other configurations of the remote control terminal 2a are similar to those of the remote control terminal 2 in the first embodiment. Therefore, in Fig. 14, the same components as those of the remote control terminal 2 are denoted by the same reference numerals as those in Fig. 2, and description thereof will be omitted.

[0073] The remote control unit 27a differs from the remote control unit 27 in the first embodiment in that, in addition to having the same functions as the remote control unit 27 in the first embodiment, the remote control unit 27a further has a function of updating plug-ins that have already been downloaded. Specifically, the remote control unit 27a has a function of acquiring information indicating whether or not a downloaded plug-in has been updated (hereinafter referred to as "update information") from the remote control server 4a, and downloading the latest plug-in from the remote control server 4a if an update has been made. The update information may be acquired by inquiring of the remote control server 4a, or may be acquired by notification from the remote control server 4a.

[0074] Fig. 15 is a functional block diagram showing a specific example of the functional configuration of the remote control server 4a in the second embodiment. The remote control server 4a differs from the remote control server 4a in the first embodiment in that it includes a plug-in providing unit 43a instead of the plug-in providing unit 43. Other configurations of the remote control server 4a are similar to those of the remote control server 4 in the first embodiment. Therefore, in Fig. 15, the same components as those of the remote control server 4 are denoted by the same reference numerals as those in Fig. 3, and description thereof will be omitted.

[0075] The plug-in providing unit 43a has a function of providing update information of the plug-in stored in the plug-in providing unit 43a to the remote control terminal 2a in addition to the same function as the plug-in providing unit 43 in the first embodiment. For example, the plug-in providing unit 43a detects whether the plug-in has been updated by determining whether the management information has been changed. For example, when the plug-in itself includes version information, the plug-in providing unit 43a may detect whether the plug-in has been updated by comparing the version information included in the plug-in stored in the plug-in information storage unit 42 with the version information included in the management information. The management information may be changed by the administrator of the remote control server 4a or by the plug-in providing unit 43a.

[0076] Fig. 16 is a sequence diagram showing a specific example of the flow of a process in which the remote control unit 27a in the home appliance system 100a of the second embodiment updates a downloaded plug-in. Note that the same processes as those in the first embodiment are denoted by the same reference numerals as those in Fig. 5, and the description thereof will be omitted. Also, as an example, a case in which a plug-in is updated from the terms of use screen to the top screen is described here, but other plug-ins can also be updated in a similar manner.

[0077] First, when it is determined in step S103 that a plug-in for displaying a top screen (hereinafter referred to as a "top screen plug-in") is stored in the remote control terminal 2a (step S103-YES), the remote control unit 27a requests update information for the top screen plug-in from the remote control server 4a (step S201). In response to this request, the remote control server 4a transmits update information for the top screen plug-in to the remote control terminal 2a (step S202). The remote control unit 27a determines whether the top screen plug-in has been updated based on the received update information (step S203). When it is determined that the top screen plug-in has not been updated (step S203-NO), the remote control unit 27a displays the top screen using the top screen plug-in stored in the remote control terminal 2a (step S106). On the other hand, when it is determined that the top screen plug-in has been updated (step S203-YES), the remote control unit 27a requests the remote control server 4a to provide the latest version of the top screen plug-in (step S204). In response to this request, the remote control server 4a transmits the latest version of the top screen plug-in to the remote control terminal 2a (step S205).Then, the remote control unit 27a displays the top screen using the received latest version of the top screen plug-in (step S106).

[0078] The remote control terminal 2a of the second embodiment thus configured determines whether the plug-in stored in the terminal itself has been updated, and if an update has been made, acquires the latest version of the plug-in from the remote control server 4a. With this configuration, the remote control terminal 2a can always provide the remote control function of the target device using the latest version of the plug-in, thereby further improving the convenience of the remote control app.

[0079] Furthermore, with this configuration, the remote control app can be updated by updating the plug-in, which reduces the frequency of updating the remote control app itself and reduces the frequency with which the user downloads the remote control app from the application server 3. This reduces the burden on the user for updating the remote control app and further improves the convenience of the remote control app.

[0080] In the above embodiment, the remote control terminal 2a determines whether the plug-in is updated when the plug-in is used. However, the remote control unit 27a may periodically obtain update information from the remote control server 4a and periodically determine whether the plug-in is updated. The remote control unit 27a may be configured to execute the process of detecting whether the plug-in is updated and the process of downloading the plug-in according to the detection result at a timing when the remote control app is not being used by the user. The timing when the remote control app is not being used by the user may be, for example, a timing when the remote control app is being executed as a background process, or a timing when the user is not operating the remote control app. In addition, when the process of checking whether the plug-in is updated is executed by a program other than the remote control app, the check of whether the plug-in is updated may be executed at a timing when the remote control app is not running.

[0081] In addition, the remote control unit 27a may be configured to download the updated plug-in from the remote control server 4a when the pre-update plug-in is being used by a remote control app, and replace the pre-update plug-in with the updated plug-in after use of the pre-update plug-in has ended.

[0082] The remote control unit 27a may also have a function of notifying the user of a plug-in update when the remote control unit 27a detects the plug-in update. The remote control unit 27a may notify the user of the plug-in update by any method, such as displaying information, outputting audio, or transmitting information.

[0083] In addition, the functions of downloading, deleting, updating, and inquiring about whether or not a plug-in has been updated may be realized by the remote control app itself, or may be realized as a separate application that operates in conjunction with the remote control app.

[0084] According to at least one of the embodiments described above, the convenience of an application that provides a remote control function for a home appliance can be improved by providing a remote control server that stores a plug-in that provides a predetermined function or information to a remote control app that remotely controls or monitors a home appliance, and a remote control terminal that is a terminal device that executes the remote control app and that downloads the plug-in that provides the function or information required by the running remote control app from the remote control server when the plug-in does not exist in the terminal device.

[0085] Although some 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 in the scope of the invention and its equivalents described in the claims, as well as in the scope and spirit of the invention. [Explanation of symbols]

[0086] 100, 100a... Home appliance system, 1, 1-1 to 1-5... Home appliances, 2, 2a... Remote control terminal, 3... Application server, 4, 4a... Remote control server, 21... Communication unit, 22... Application storage unit, 23... Plug-in storage unit, 24... Input unit, 25... Display unit, 26... Control unit, 27, 27a... Remote control unit, 41... Communication unit, 42... Plug-in information storage unit, 43, 43a... Plug-in providing unit, 51... Router, 52... WAN (Wide Area Network)

Claims

1. a server device that stores plug-ins used when displaying various screens that are displayed by an application for remotely controlling or remotely monitoring a home appliance in order to provide a predetermined function or information; a terminal device which executes the application, the terminal device determining whether or not a plug-in for displaying a screen related to an operation is stored in the terminal device each time an operation for displaying each screen is input to the application being executed, and downloading the plug-in from the server device when a part or all of the plug-in is not stored in the terminal device; Equipped with when the pre-update plug-in is being used by the application, the terminal device downloads an updated plug-in from the server device, and replaces the pre-update plug-in with the updated plug-in after use of the pre-update plug-in has ended. Home appliances systems.

2. When a certain plug-in is no longer used for remote control of any of the home appliances due to the deletion of the registration of any of the home appliances from the application, the terminal device deletes the certain plug-in stored in the terminal device. The home appliance system of claim 1 .

3. a storage unit that stores plug-ins used when displaying various screens that are displayed by an application for remotely controlling a home appliance in order to provide a predetermined function or information; a plug-in providing unit that transmits a plug-in in response to a request from a terminal device that executes the application when a part or all of a plug-in for displaying a screen related to the operation is not stored in the terminal device every time an operation for displaying each of the screens is input to the application in the terminal device that executes the application is input; A server device comprising: the terminal device downloads an updated plug-in from the server device when the pre-update plug-in is being used by the application, and replaces the pre-update plug-in with the updated plug-in after use of the pre-update plug-in has ended. Server device.

4. When a certain plug-in is no longer used for remote control of any of the home appliances due to a deletion of registration of any of the home appliances from the application, the terminal device deletes the certain plug-in stored in the terminal device. The server device according to claim 3.

5. a communication unit that communicates with a server device that stores plug-ins used when displaying various screens that are displayed by an application that remotely controls a home appliance in order to provide a predetermined function or information; a remote operation unit that, each time an operation for displaying each of the screens is input to the application being executed on the own device, determines whether or not a plug-in for displaying the screen related to the operation is stored in the own device, and downloads the plug-in from the server device if a part or all of the plug-in is not stored in the own device; Equipped with the remote control unit downloads an updated plug-in from the server device when the pre-update plug-in is being used by the application, and replaces the pre-update plug-in with the updated plug-in after use of the pre-update plug-in has ended. Terminal device.

6. when a certain plug-in is no longer used for remote control of any of the home appliances due to a deletion of the registration of any of the home appliances from the application, the remote control unit deletes the certain plug-in stored in the remote control unit. The terminal device according to claim 5.

7. A computer capable of communicating with a server device storing plug-ins used for displaying various screens displayed by an application for remotely controlling a home appliance to provide a predetermined function or information, a step of determining whether or not a plug-in for displaying a screen related to an operation is stored in the computer each time an operation for displaying each screen is input to the application being executed on the computer, and downloading the plug-in from the server device if a part or all of the plug-in is not stored in the computer. A computer program for executing the step of downloading an updated plug-in from the server device when the pre-update plug-in is being used by the application, and replacing the pre-update plug-in with the updated plug-in after use of the pre-update plug-in has ended; Computer program.

8. When the registration of any home appliance is deleted from the application, a certain plug-in is no longer used for remote control of any home appliance, A method for causing the computer to delete the certain plug-in stored in the computer, 8. A computer program according to claim 7.

Images