Information processing device, information processing method, and program

Abstract

To provide an information processing device, an information processing method, and a program for, when functional expansions occur in a chronological perspective such as the addition of novel devices or the function update of devices, enabling responding in a swift manner in response to receiving information relating to these functional expansions.SOLUTION: The information processing device comprises: a device registration unit that registers a device; a device communication unit that communicates with the device registered by the device registration unit; a device linking unit that links the device for performing communication by the device communication unit to an application; and a service monitoring unit that, when a novel device or a novel function is added to the device and a device catalog indicating functions of the device, executes, to at least one of a user's end user terminal of the device and a service vendor terminal of a service vendor which develops the application, recommendation of updating to or being replaced with the novel device or the novel function.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] The Internet of Things (IoT) is a technology that connects various devices (e.g., smartphones, digital home appliances, and industrial equipment) to the Internet, enabling the collection and analysis of complex data. To facilitate communication with a wide variety of devices and the development of applications or solutions using each device, technologies have been developed to define a common schema (called a universal schema). For example, Patent Document 1 discloses a configuration that provides a comprehensive IoT device universal schema that defines all aspects of interaction between IoT devices, including their types, functions, attributes, actions, inputs, outputs, resources, and commands, with the aim of enabling discovery, interaction, association, and collaboration between heterogeneous IoT devices and networks. Summary of the Invention [Problem to be solved by the invention]

[0003] The above technology enables the development of applications or solutions that utilize devices using pre-defined definition information, such as schemas. However, when functional expansions occur over time, such as the addition of new devices or updates to device functions (e.g., the addition or deletion of capabilities), information about the addition of new devices or updates to device functions must be promptly reflected in the definition information and notified to developers. However, this type of post-release issue remains unresolved. As a result, for example, if a device's functionality is reduced, an application may suddenly stop working. Furthermore, when new devices are added and their capabilities increase, application developers are required to be able to handle these devices immediately.

[0004] The present invention has been made in consideration of the above, and aims to provide an information processing device, an information processing method, and a program that can receive information about functional expansions from a chronological perspective, such as the addition of a new device or updating the functions of a device, and respond quickly when such expansions occur. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems and achieve the object, the present invention provides a device registration unit that registers devices, a device communication unit that communicates with the devices registered by the device registration unit, a device linking unit that links the devices that communicate by the device communication unit with an application, and a service monitoring unit that, when a new device or a new function is added to a device catalog that indicates the devices and the functions of the devices, recommends updating or replacing the new device or new function to at least one of an end user terminal of a user of the device and a service vendor terminal of a service vendor that develops the application; an update unit that requests the device to update or replace with the new device or the new function, and the service monitoring unit further instructs the update unit to update or replace with the new device or the new function when the end user terminal instructs the update unit to update or replace with the new device or the new function. . [Effects of the Invention]

[0006] According to the present invention, when a function expansion occurs from a chronological viewpoint, such as the addition of a new device or an update of a device's function, information about the function expansion can be received and a quick response can be made. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of an information processing system according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of hardware configurations of a device vendor terminal, a service vendor terminal, an end user terminal, and a PC which is an example of an IoT platform according to the present embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of an MFP, which is an example of a device according to the present embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a functional configuration of an IoT platform according to the present embodiment. [Figure 5] FIG. 5 is a sequence diagram showing an example of a flow of updating a device in the information processing system according to the present embodiment. [Figure 6] FIG. 6 is a sequence diagram showing an example of a flow of updating a device in the information processing system according to the present embodiment. [Figure 7] FIG. 7 is a sequence diagram showing an example of the flow of a notification process of the suspension of service provision in the information processing system according to the present embodiment. [Figure 8] FIG. 8 is a diagram showing an example of a screen displayed by the portal site of the IoT platform according to the present embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of an information processing device, an information processing method, and a program will be described in detail with reference to the accompanying drawings.

[0009] 1 is a block diagram showing an example of the configuration of an information processing system according to the present embodiment. As shown in FIG. 1, the information processing system according to the present embodiment includes a device vendor terminal 1, a service vendor terminal 2, a device 3, an end user terminal 4, an IoT platform (an example of an information processing device) 5, and a relay device 6.

[0010] The device vendor terminal 1 is a terminal used by a partner (device vendor) that develops the device 3. The service vendor terminal 2 is a terminal used by a service vendor that develops an application to be linked with the device 3. The device 3 is an example of a device that is connected to the Internet, such as an MFP (Multi-Function Peripheral).

[0011] The end user terminal 4 is a terminal used by an end user who uses a service (for example, an application) developed by a service vendor. The IoT platform 5 is a platform that provides users with IoT-based services. The relay device 6 is equipped with a relay application (referred to as a general-purpose relay app) that relays communication between the IoT platform 5 and the device 3.

[0012] 2 is a diagram illustrating an example of the hardware configuration of a device vendor terminal, a service vendor terminal, an end user terminal, and a PC which is an example of an IoT platform according to this embodiment. Here, the hardware configuration of the IoT platform 5 will be described.

[0013] As shown in Figure 2, the IoT platform 5 is constructed by a computer, and as shown in Figure 2, it includes a CPU 501, a ROM 502, a RAM 503, an HD 504, an HDD (Hard Disk Drive) controller 505, a display 506, an external device connection I / F (Interface) 508, a network I / F 509, a data bus 510, a keyboard 511, a pointing device 512, a DVD-RW (Digital Versatile Disk Rewritable) drive 514, and a media I / F 516.

[0014] Of these, the CPU 501 controls the overall operation of the IoT platform 5. The ROM 502 stores programs used to drive the CPU 501, such as an IPL. The RAM 503 is used as a work area for the CPU 501. The HD 504 stores various data, such as programs. The HDD controller 505 controls the reading and writing of various data from and to the HD 504 under the control of the CPU 501. The display 506 displays various information, such as a cursor, menu, window, text, or image. The external device connection I / F 508 is an interface for connecting various external devices. In this case, the external device is, for example, a USB (Universal Serial Bus) memory or a printer. The network I / F 509 is an interface for data communication using the communication network 100. The data bus 510 is an address bus, a data bus, or the like, for electrically connecting the components, such as the CPU 501, shown in FIG. 2.

[0015] The keyboard 511 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 512 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The DVD-RW drive 514 controls reading and writing of various data from a DVD-RW 513, which is an example of a removable recording medium. Note that this is not limited to a DVD-RW, and may be a DVD-R, etc. The media I / F 516 controls reading and writing (storing) of data from a recording medium 515, such as a flash memory.

[0016] 3 is a diagram showing an example of the hardware configuration of an MFP, which is an example of a device according to the present embodiment. As shown in Fig. 3, the MFP (Multi-function Peripheral / Product / Printer), which is an example of a device 3, includes a controller 910, a short-range communication circuit 920, an engine control unit 930, an operation panel 940, and a network I / F 950.

[0017] Of these, the controller 910 has a CPU 901, which is the main part of the computer, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a local memory (MEM-C) 907, which is a storage unit, an HDD controller 908, and an HD 909, which is also a storage unit, and is configured such that the NB 903 and the ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921.

[0018] Of these, the CPU 901 is a control unit that performs overall control of the MFP 9. The NB 903 is a bridge that connects the CPU 901 with the MEM-P 902, the SB 904, and the AGP bus 921, and includes a memory controller that controls reading and writing to and from the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target.

[0019] The MEM-P 902 comprises a ROM 902a, which is memory for storing programs and data that realize the functions of the controller 910, and a RAM 902b, which is used for expanding the programs and data and as a drawing memory during memory printing. The programs stored in the RAM 902b may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM, CD-R, or DVD.

[0020] The SB 904 is a bridge for connecting the NB 903 with PCI devices and peripheral devices. The ASIC 906 is an integrated circuit (IC) for image processing applications that has hardware elements for image processing and functions as a bridge connecting the AGP bus 921, PCI bus 922, HDD 908, and MEM-C 907. The ASIC 906 includes a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 906, a memory controller that controls the MEM-C 907, multiple direct memory access controllers (DMACs) that perform image data rotation and other operations using hardware logic, and a PCI unit that transfers data between the scanner unit 931 and printer unit 932 via the PCI bus 922. A USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers) interface may also be connected to the ASIC 906.

[0021] 4 is a diagram illustrating an example of the functional configuration of the IoT platform according to the present embodiment. In the present embodiment, the IoT platform 5 includes a device registration unit 401, a device communication unit 402, a device cooperation unit 403, an OTA update unit 404, a service monitoring unit 405, a device catalog management unit 406, a service catalog management unit 407, and an application development tool 408, as shown in FIG.

[0022] The device registration unit 401 registers the device 3 in the IoT platform 5. The device communication unit 402 communicates with the device 3 registered by the device registration unit 401. Specifically, the device communication unit 402 authenticates or authorizes the device 3, and communicates with devices that have been successfully authenticated or authorized. The device cooperation unit 403 cooperates with an application developed by a service vendor and the device 3. In this way, the device cooperation unit 403 provides the user with a service that utilizes IoT.

[0023] The OTA (Over The Air) update unit 404 is an example of an update unit that requests an update from the device 3 and a relay application, etc., when an instruction to update or replace with a new device 3 or a new function is received from the end user terminal 4. Furthermore, if the device 3 is a device that cannot be directly connected to the IoT platform 5 (for example, a device from another company, a low-spec device such as a sensor), the OTA update unit 404 requests the device 3 to update or replace with a new device 3 or a new function via the relay application of the relay device 6. This allows a request to update or replace with a new device 3 or a new function even for a device 3 that cannot be directly connected to the IoT platform 5 (a device from another company, a low-spec device such as a sensor).

[0024] The device catalog management unit 406, the service catalog management unit 407, and the application development tool 408 are components of a portal site that facilitates communication between providers of the IoT platform 5.

[0025] The device catalog management unit 406 stores a device catalog. Here, the device catalog includes the lineup of devices 3, the functions of the devices 3, the schema (digital schema) of the device catalog, user setting information (notification settings) related to recommendations for end users and service vendors, etc. Furthermore, when a new device 3 or function is added to the device catalog, the device catalog management unit 406 adds the new device 3 or function to the device catalog and notifies the service monitoring unit 405 of the addition of the new device 3 or function.

[0026] The service catalog management unit 407 stores a service catalog that indicates services to be provided to end users. Here, the services include communication between the device 3 and the end user terminal 4, which is provided to end users by the device 3 and the application. The application development tool 408 is a tool used by the service vendor terminal 2 to develop applications.

[0027] When a new device 3 or a new function is added to the device catalog, the service monitoring unit 405 recommends updating or replacing to the new device 3 or new function to the end user terminal 4 and the service vendor terminal 2. In this embodiment, the service monitoring unit 405 makes the recommendation when the service catalog management unit 407 notifies the end user terminal 4 and the service vendor terminal 2 that a new device 3 or a new function has been added to the device catalog. Furthermore, the service monitoring unit 405 instructs the OTA update unit 404 to update or replace to the new device 3 or new function in response to a request from the end user terminal 4 or the service vendor terminal 2 to instruct updating or replacing to the new device 3 or new function. This allows the OTA update unit 404 to receive information about these function extensions when function extensions occur from a chronological perspective, such as the addition of a new device 3 or a function update of the device 3, and therefore allows the function extension of the device 3 to be handled promptly.

[0028] The service monitoring unit 405 also makes recommendations to end users or service vendors in accordance with user setting information (recommendation notification settings) included in the device catalog. This allows the service vendor or end user to turn off unwanted notifications (recommendations) in advance.

[0029] Furthermore, the service monitoring unit 405 makes recommendations to end users or service vendors based on the usage history of the devices 3 and functions, allowing the end users or service vendors to select devices 3 or functions to update or replace, taking into account the usage history of the devices 3 and functions.

[0030] Furthermore, if the service monitoring unit 405 detects a vulnerability in the device 3 or a function, it notifies the service vendor or end user that provision of the device 3 or the function will be discontinued. This allows the service vendor or end user to quickly use an updated version of the device 3 or the function, and enables a quick response to the discontinuation of provision of the device 3 or the function.

[0031] Here, an outline of an example of the flow of a process for requesting an update of a device 3 or a function by the IoT platform 5 according to the present embodiment will be described with reference to Fig. 4. As shown in Fig. 4, when a device 3 is added, the device vendor terminal 1 adds the added device 3 to the device catalog of the device catalog management unit 406 of the portal site (step S401). At the time when the device 3 is added to the device catalog, the device catalog management unit 406 notifies the service monitoring unit 405 that a new device or a new function has been added (step S402).

[0032] The service monitoring unit 405 determines whether or not a recommendation needs to be sent to the service vendor or end user, according to the user setting information included in the device catalog (step S403). Next, the service monitoring unit 405 recommends newly added devices 3, functions, and use cases for the devices or functions to the service vendor terminal 2 of the service vendor (partner developing the application) for which it has determined that a recommendation needs to be sent (step S404). The service vendor then plans and develops new applications and services based on the contents of the recommendations. The service vendor and end user may be notified of the recommendations via email, Slack, Teams, etc.

[0033] Furthermore, the service monitoring unit 405 makes a recommendation such as replacing the device 3 to the end user terminal 4 of the end user for which it is determined that a recommendation needs to be notified, such as when the newly added device 3 and its functions are upwardly compatible (step S405). The end user checks the content of the recommendation and issues an update instruction and additional order to the service monitoring unit 405 from the end user terminal 4 (step S406). The OTA update unit 404 requests the device 3 to replace the device 3 and update its functions (step S407), and updates the relay application and the firmware of the device 3 remotely or the like.

[0034] Fig. 5 is a sequence diagram showing an example of a flow of updating a device in the information processing system according to the present embodiment. Next, an example of a flow of a process of updating a device 3 without using a relay application when a new device 3 or a new function is added will be described with reference to Fig. 5.

[0035] A device vendor adds a new device 3 lineup or a new function to the device catalog using the portal site of the IoT platform 5 from the device vendor terminal 1 (step S521). The service monitoring unit 405 of the IoT platform 5 checks whether notifications to end users and service vendors are required according to the user setting information included in the device catalog, and identifies the end users and service vendors requesting notifications (recommendations) (step S522).

[0036] Next, the service monitoring unit 405 makes recommendations to the end user terminal 4 of the end user requesting the recommendation and the service vendor terminal 2 of the service vendor requesting the recommendation (steps S523 and S524). At this time, the service monitoring unit 405 searches for related devices 3 and services based on the keywords registered by the user (keywords included in the user setting information), and performs recommendations by giving priority to services with a high frequency of purchase applications and actual use among the searched devices 3 and services.

[0037] The service vendor can create a new service menu with the added devices and functions based on the recommendations from the IoT platform 5. If the end user likes the newly available service menu after receiving the notification, the end user can apply for the new service or send a request for additional purchase from the end user terminal 4 (step S525).

[0038] When the service monitoring unit 405 of the IoT platform 5 receives a request from the end user terminal 4, it instructs the OTA update unit 404 to update to a new device 3 or a new function. The OTA update unit 404 transmits an update request to the device 3 (step S526). The device 3 that has received the update request executes the update (step S527) and notifies the OTA update unit 404 of the result (step S528). Thereafter, the service monitoring unit 405 notifies the end user terminal 4 that the update of the device 3 has been completed (step S529).

[0039] Fig. 6 is a sequence diagram showing an example of a flow of updating a device in the information processing system according to the present embodiment. Next, an example of a flow of a process for updating a device 3 via a relay application when a new device 3 or a new function is added will be described with reference to Fig. 6. In the following description, a description of processes similar to those shown in Fig. 5 will be omitted.

[0040] If the device 3 to be updated cannot be directly connected to the IoT platform 5, the service monitoring unit 405 of the IoT platform 5 transmits an update request for the device 3 to the relay application of the relay device 6 (step S601). The relay application of the relay device 6 executes an update of the relay application itself (step S602). Furthermore, the relay application transmits an update request to the device 3 (step S603).

[0041] Upon receiving the update request, the device 3 executes the update (step S604) and notifies the relay application of the relay device 6 of the result (step S605). After that, the relay application notifies the IoT platform 5 that the update of the device 3 has been completed (step S606). Furthermore, the service monitoring unit 405 of the IoT platform 5 notifies the end user terminal 4 that the update of the device 3 has been completed (step S607).

[0042] 7 is a sequence diagram showing an example of a flow of a notification process of stopping the provision of a service in the information processing system according to the present embodiment. Next, an example of a flow of a process of stopping the provision of a service by the device 3 etc. when a vulnerability of the device 3 etc. is detected in the information processing system according to the present embodiment will be described with reference to FIG.

[0043] The service monitoring unit 405 of the IoT platform 5 detects vulnerabilities in services provided by the devices 3 and applications (step S701). In this embodiment, the service monitoring unit 405 automatically detects vulnerabilities in services, but this is not limiting, and for example, information indicating vulnerabilities in services may be obtained from information on the Web.

[0044] When the service monitoring unit 405 of the IoT platform 5 detects a vulnerability in a service, it first notifies the service vendor terminal 2 of the service provider, that is, the service vendor, of whether to continue providing the service and the risks involved in continuing to provide the service (step S702). The service vendor terminal 2 then displays the risks involved in continuing to provide the service, allowing the service vendor to confirm the risks (step S703). If the service vendor decides to continue providing the service, the response is completed by simply notifying the service vendor of the risks involved in continuing to provide the service. However, if the service vendor wishes to suspend the provision of the service, the service vendor terminal 2 requests the IoT platform 5 to suspend the provision of the service from the screen of the portal site of the IoT platform 5 (step S704).

[0045] The service monitoring unit 405 of the IoT platform 5 transmits a request to suspend the service to the relay application of the relay device 6 and the device 3 (steps S705 and S706). Then, the relay application and the device 3 suspend the provision of the service (steps S707 and S708). Thereafter, the relay application and the device 3 periodically check whether an instruction to resume the provision of the service has been issued to the IoT platform 5 in preparation for starting the service. Furthermore, the service monitoring unit 405 of the IoT platform 5 notifies the end user terminal 4 of the end user that the service has been temporarily suspended due to the detection of a vulnerability (step S709). Thereafter, when the vulnerability in the service can be addressed and the provision of the service is started, the service monitoring unit 405 notifies the service vendor terminal 2 of the resumption of the provision of the service, following the same flow as when the provision of the service was temporarily suspended, and resumes the provision of the service to the end user terminal 4 and resumes control of the relay application and the device 3.

[0046] Fig. 8 is a diagram showing an example of a screen displayed by the portal site of the IoT platform according to the present embodiment. Next, an example of a device dialogue update process by the portal site of the IoT platform 5 according to the present embodiment will be described with reference to Fig. 8.

[0047] The portal site screen displayed by the IoT platform 5 first displays a screen G1 listing devices 3 supported by the IoT platform 5. After that, when a device 3 is selected by the device vendor terminal 1, a details screen G2 for the device 3 is displayed on the portal site screen. The details screen G2 includes information such as the device type, version, compatibility, release notes, and schema details (e.g., a device schema in JSON schema format). The device schema may be, for example, a device schema for a temperature measurement device, which defines the user name and body temperature data of the person who took the temperature. The device vendor terminal 1 of the device vendor, which has the authority to update the device catalog, can update the schema details. Meanwhile, the service vendor terminal 2 of the service vendor can only view the schema details. The portal site screen may also include a user settings screen G3 that allows the user to turn on or off user settings such as whether to receive recommendation notifications and keywords for recommendations to be notified.

[0048] In this way, according to the information processing system of this embodiment, when functional expansion from a chronological perspective occurs, such as the addition of a new device 3 or an update to the functions of a device 3, information about these functional expansions can be received, so that the functional expansion of the device 3 can be responded to promptly.

[0049] The programs executed by the IoT platform 5 of this embodiment are provided by being pre-installed in the ROM 502 or the like. The programs executed by the IoT platform 5 of this embodiment may be provided by being recorded in an installable or executable format on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD).

[0050] Furthermore, the program executed by the IoT platform 5 of this embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Also, the program executed by the IoT platform 5 of this embodiment may be provided or distributed via a network such as the Internet.

[0051] The program executed by the IoT platform 5 of this embodiment has a modular configuration including the above-mentioned units (device registration unit 401, device communication unit 402, device collaboration unit 403, OTA update unit 404, service monitoring unit 405, device catalog management unit 406, service catalog management unit 407, and application development tool 408), and in actual hardware, the CPU 501 (an example of a processor) reads and executes the program from the above-mentioned ROM 502, thereby loading the above-mentioned units onto the main memory device, and the device registration unit 401, device communication unit 402, device collaboration unit 403, OTA update unit 404, service monitoring unit 405, device catalog management unit 406, service catalog management unit 407, and application development tool 408 are generated on the main memory device. [Explanation of symbols]

[0052] 1. Device vendor terminal 2 Service vendor terminal 3 Devices 4 End-user terminals 5 IoT Platform 6. Relay Device 401 Device Registration 402 Device Communication Unit 403 Device Linkage Department 404 OTA update section 405 Service Monitoring Department 406 Device Catalog Management Department 407 Service Catalog Management Department 408 App Development Tools 501 CPU 502 ROM 503 RAM [Prior art documents] [Patent documents]

[0053] [Patent Document 1] Patent No. 6363628

Claims

1. a device registration unit for registering a device; a device communication unit that communicates with the device registered by the device registration unit; a device linking unit that links the device communicating via the device communication unit with an application; a service monitoring unit that, when a new device or a new function is added to a device catalog indicating the device and the function of the device, recommends updating or replacing the device or the function to the new device or the new function to at least one of an end user terminal of a user of the device and a service vendor terminal of a service vendor that develops the application; an update unit that requests the device to be updated or replaced with a new device or new function; The information processing device, wherein the service monitoring unit further instructs the update unit to update or replace with a new device or a new function when the end user terminal instructs the update unit to update or replace with a new device or a new function.

2. The information processing device according to claim 1, wherein the update unit requests the device to update or replace the device with a new device or a new function via a relay application that relays communication between the information processing device and the device when the device cannot be directly connected to the information processing device.

3. The information processing device according to claim 1 , wherein the service monitoring unit executes the recommendation in accordance with a notification setting for the recommendation.

4. 4. The information processing device according to claim 1, wherein the service monitoring unit notifies the end user terminal or the service vendor terminal of discontinuing provision of the device or the function when the service monitoring unit detects a vulnerability in the device or the function.

5. The information processing apparatus according to claim 1 , wherein the service monitoring unit executes the recommendation based on a usage history of the device and the function.

6. An information processing method executed by an information processing device, a step of a device registration unit registering a device; a step in which a device communication unit communicates with the device registered by the device registration unit; a step in which a device linking unit links the device communicating via the device communication unit with an application; a step in which, when a new device or a new function is added to a device catalog indicating the device and the function of the device, a service monitoring unit recommends updating or replacing the new device or the new function to at least one of an end user terminal of a user of the device and a service vendor terminal of a service vendor that develops the application; an update unit requesting the device to be updated or replaced with a new device or new function; a step in which the service monitoring unit further instructs the update unit to update or replace the device or function to a new device or function when the end user terminal instructs the update unit to update or replace the device or function to a new device or function; An information processing method including:

7. Computer, a device registration unit for registering a device; a device communication unit that communicates with the device registered by the device registration unit; a device linking unit that links the device communicating via the device communication unit with an application; a service monitoring unit that, when a new device or a new function is added to a device catalog indicating the device and the function of the device, recommends updating or replacing the device or the function to the new device or the new function to at least one of an end user terminal of a user of the device and a service vendor terminal of a service vendor that develops the application; an update unit that requests the device to be updated or replaced with a new device or new function; The service monitoring unit further instructs the update unit to update or replace with a new device or a new function when the end user terminal instructs the update unit to update or replace with a new device or a new function.

Images