Information processing device, information processing method, and program

Abstract

To provide an information processing device, an information processing method and a program for enabling a user to easily switch a device without switching a license associated with the device or performing takeover of device setting when an alternative device is temporarily used because the device fails.SOLUTION: An information processing device according to the present invention includes a device registration part for registering a device, a license management part for allocating a license of an application to the device registered by the device registration part, an application execution function part for executing the application with the license allocated to the device in response to an application execution request of the application from the device, and a device replacement function part for registering the replacement setting of the device to another device, and converting the application execution request from the replaced other device to the application execution request from the device before being replaced.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] IoT (Internet of Things), also known as the Internet of Things, connects various IoT devices such as smartphones and digital home appliances to the Internet, enabling the collection and analysis of data in a comprehensive manner. For example, Patent Document 1 discloses a configuration that aims to solve the problem of a node-locked license system requiring a license to be reissued each time the hardware is changed when a license is granted to only one device, by using a means for performing license management using hardware-specific information during initial license management and a means for performing license management using only a user ID and password during subsequent license management. Summary of the Invention [Problem to be solved by the invention]

[0003] In the case of IoT, when an IoT device breaks down and repairs cannot be completed immediately, a substitute device is temporarily used. However, even though the substitute device is only used temporarily, it is difficult for users to easily switch IoT devices, as it requires switching the license associated with the IoT device and transferring the IoT device settings. Furthermore, in Patent Document 1, when switching hardware, it is necessary to transfer the IoT device settings, making it difficult for users to easily switch IoT devices.

[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 allow a user to easily switch devices when a device breaks down and a replacement device is to be temporarily used, without having to switch the license associated with the device, transfer the device settings, etc. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems and achieve the object, the present invention comprises a device registration unit that registers devices, a license management unit that assigns application licenses to the devices registered by the device registration unit, an application execution function unit that executes the application whose license has been assigned to the device in response to an application execution request for the application from the device, and a device replacement function unit that registers replacement settings for the device with another device and converts the application execution request from the replaced other device into the application execution request from the device before replacement. [Effects of the Invention]

[0006] According to the present invention, when a device breaks down and an alternative device needs to be temporarily used, the user can easily switch devices without having to switch the license associated with the device, take over the device settings, etc. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of an IoT system according to the present embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the hardware configuration of a service provider terminal, an IoT platform, and a user terminal according to the present embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a device according to the present embodiment. [Figure 4] FIG. 4 is a block diagram illustrating an example of a functional configuration of the IoT system according to the present embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of communication processing between a relay application of a user terminal and an IoT platform according to the present embodiment. [Figure 6] FIG. 6 is a sequence diagram showing an example of the flow of a user authentication process in the IoT system according to this embodiment. [Figure 7] FIG. 7 is a sequence diagram showing an example of the flow of a device registration process in the IoT system according to the present embodiment. [Figure 8] FIG. 8 is a sequence diagram showing an example of the flow of a process for changing a device setting value in the IoT system according to the present embodiment. [Figure 9] FIG. 9 is a sequence diagram showing an example of the flow of a process for setting permission for device replacement in the IoT system according to the present embodiment. [Figure 10] FIG. 10 is a sequence diagram showing an example of the flow of the setting process for replacing a device in the IoT system according to the present embodiment. [Figure 11] FIG. 11 is a sequence diagram showing an example of the flow of an application execution process by a device in the IoT system according to this embodiment. [Figure 12] FIG. 12 is a sequence diagram showing an example of the flow of a process for canceling the replacement setting of a device in the IoT system 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] Fig. 1 is a diagram showing an example of the configuration of an IoT system according to this embodiment. As shown in Fig. 1, the IoT system (an example of an information processing system) according to this embodiment includes a service provider terminal 1 having an application for a service provider, a user terminal 2 having a relay application, a device 3, an application 4 running on the cloud, and an IoT platform (an example of an information processing device) 5. Here, the relay application is an application that connects the device 3 to the IoT platform 5.

[0010] 2 is a diagram showing an example of the hardware configuration of a service provider terminal, an IoT platform, and a user terminal according to this embodiment. Here, the hardware configuration of the IoT platform 5 will be described.

[0011] 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.

[0012] 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.

[0013] 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.

[0014] 3 is a diagram illustrating an example of a hardware configuration of a device according to the present embodiment. As illustrated in FIG. 3, an 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.

[0015] 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.

[0016] 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.

[0017] 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.

[0018] 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.

[0019] Fig. 4 is a block diagram showing an example of a functional configuration of an IoT system according to this embodiment. In this embodiment, the service provider terminal 1 has an application for the service provider, as shown in Fig. 4. The application for the service provider realizes a device replacement permission function unit 101.

[0020] The device replacement permission function unit 101 sets a device replacement permission indicating whether or not to permit replacement of the device 3. For example, the device replacement permission function unit 101 displays a device replacement permission screen on the service provider terminal 1, which allows the user to select whether or not to permit replacement of the device 3, and sets the device replacement permission in accordance with the selection on the device replacement permission screen.

[0021] In this embodiment, the IoT platform 5 has a user authentication function unit 521 , a device setting management function unit 522 , a device registration function unit 523 , a license management function unit 524 , an application execution function unit 525 , and a device replacement function unit 526 .

[0022] The user authentication function unit 521 executes login of a pre-registered user to the IoT platform 5. The device setting management function unit 522 manages (records) setting information for the device 3 (hereinafter referred to as device setting values). In this embodiment, the device setting management function unit 522 has a device setting management database. Here, the device setting management database stores user information (e.g., email address), a device type which is the type of device 3, a serial ID of the device 3, and device setting values ​​in association with each other, as shown in Table 1 below. [Table 1]

[0023] Furthermore, the device setting management function unit 522 copies the device setting values ​​of the device 3 before replacement to the replaced device 3. This allows the device setting values ​​to be copied to the replaced device 3 only for the combination of devices 3 for which replacement settings have been performed.

[0024] Furthermore, the device setting management function unit 522 transmits the device setting values ​​of the device 3 before replacement to the relay application of the user terminal 2, and then transmits them to the replaced device 3, and instructs the application to copy the device setting values ​​to the replaced device 3. This allows the device setting values ​​of the device 3 before the failure to be reflected in the replaced device 3.

[0025] The device registration function unit 523 registers the device 3 in the IoT platform 5. The device registration function unit 523 also executes authorization and authentication of the device 3. As a result, the device registration function unit 523 allows access only to the device 3 registered in the IoT platform 5. The license management function unit 524 assigns a license to the registered device 3, thereby managing the execution of the application 4 by the registered device 3.

[0026] The device replacement function unit 526 replaces and cancels the replacement of the device 3 in order to replace the device 3. Specifically, the device replacement function unit 526 registers a replacement setting for the failed device (substitution source device) 3 to another device (substitution destination device) 3.

[0027] In this embodiment, the device replacement function unit 526 has a device replacement database. Here, the device replacement database stores user information, replacement source device information, and replacement destination device information in association with each other, as shown in Table 2 below. Here, the replacement source device information is information that identifies the replacement source device 3, and includes the device type, serial ID, and item name of the replacement source device 3. Also, the replacement destination device information is information that identifies the replacement destination device 3, and includes the device type, serial ID, and item name of the replacement destination device 3.

[0028] When the replacement setting for device 3 is registered, the device replacement function unit 526 registers the replacement source device information and the replacement destination device information in the device replacement database. Furthermore, when the replacement of device 3 is canceled, the device replacement function unit 526 deletes the records of the replacement source device information, the replacement destination device information, etc. from the device replacement database. Specifically, the device replacement function unit 526 cancels the registration of the replacement setting for the replacement destination device 3 in response to a request to cancel the registration of the replacement setting for the replacement destination device from the relay application of the user terminal 2. This allows only registered users to cancel the registration of the replacement setting. [Table 2]

[0029] Furthermore, the device replacement function unit 526 converts an application execution request from the substitute device into an application execution request from the device 3 before replacement (for example, the broken device 3). Here, the application execution request is a request to execute the application 4. This eliminates the need for the user to switch the license from the device 3 to the substitute device when the device 3 is replaced with a substitute device. As a result, when the device 3 breaks down and a substitute device is temporarily used, the user can easily switch the device 3 without having to switch the license associated with the device 3, take over the device settings, etc.

[0030] The application execution function unit 525 executes the application 4 based on an application execution request in accordance with the Message Queuing Telemetry Transport (MQTT) protocol from the device 3. The application execution function unit 525 also executes the application 4 based on an application execution request converted by the device replacement function unit 526.

[0031] The user terminal 2 has a relay application that causes the user terminal 2 to display a user authentication screen, a device setting screen, a device registration screen, a device replacement screen, and a license management screen.

[0032] The user authentication screen is a screen for using the user authentication function unit 521 of the IoT platform 5. The device setting screen is a screen for managing the device setting values ​​of the device 3. The device registration screen is a screen for managing the registration and deregistration of the device 3.

[0033] The license management screen is a screen for registering and canceling the use of the license of the application 4 used by the device 3. The device replacement screen is a screen for replacing and canceling the replacement of the device 3.

[0034] The relay application also includes an application execution request function unit 527. In response to a request from the device 3, the application execution request function unit 527 transmits an application execution request to the IoT platform 5 according to the MQTT protocol.

[0035] Next, an example of communication processing between the relay application of the user terminal 2 and the IoT platform 5 in the IoT system according to the present embodiment will be described with reference to Fig. 5. Fig. 5 is a diagram for explaining an example of communication processing between the relay application of the user terminal and the IoT platform according to the present embodiment.

[0036] The MQTT protocol is a Pub / Sub communication protocol that performs many-to-many communication. The Pub / Sub communication method consists of three parts: a publisher, a broker, and a subscriber. The destination (URI: Uniform Resource Identifier) ​​to which the publisher sends data is called a topic, and consists of a character string.

[0037] The topic has the following characteristics: UTF-8 string Total length is 65,535 bytes or less Starting with " / " Topics have a hierarchy, and each hierarchy is separated by " / ". "+,*" is used as a wildcard for subscription registration, where "+" is a wildcard for a single level (e.g., / topic / sample / + / test), and "*" is a wildcard that refers to all levels below and can only be placed at the end of a topic (e.g., / topic / sample / #).

[0038] Subscribers register with the broker which topics they want to subscribe to. Publishers publish messages to topics. The broker then delivers data sent to a topic to subscribers who have subscribed to that topic.

[0039] 6 is a sequence diagram showing an example of the flow of a user authentication process in the IoT system according to the present embodiment. Next, an example of the flow of a user authentication process in the IoT system according to the present embodiment will be described with reference to FIG.

[0040] First, the user starts the relay application of the user terminal 2, enters an email address and a password on the user authentication screen, and presses the login button (step S601). Next, the relay application transmits a user authentication (login) request to the IoT platform 5 (step S602).

[0041] The user authentication function unit 521 of the IoT platform 5 verifies the user information (e.g., email address) and password, and determines whether the user who logged in to the relay application (i.e., the user indicated by the user information) is a pre-registered user and whether the password matches the pre-registered password.

[0042] If the user who logged in to the relay application is a preset user and the password is a pre-registered password, the user authentication function unit 521 notifies the relay application that the login was successful, otherwise it notifies that the login was unsuccessful (step S603). The relay application displays the user authentication result notified by the user authentication function unit 521 on the user authentication screen (step S604).

[0043] Fig. 7 is a sequence diagram showing an example of the flow of a device registration process in the IoT system according to this embodiment. Next, an example of the flow of a device registration process in the IoT system according to this embodiment will be described with reference to Fig. 7. Here, it is assumed that the user has previously logged in to the IoT platform 5 from the user authentication screen.

[0044] The user starts the relay application of the user terminal 2 and displays the device registration screen. When the user selects the device 3 to be registered on the device registration screen and presses the register button (step S701), the relay application requests registration of the device type and serial ID of the device 3 to be registered in the IoT platform 5 (step S702).

[0045] The device registration function unit 523 of the IoT platform 5 registers the device type and serial ID received from the relay application, and registers the device 3. If the registration of the device 3 is successful, the device registration function unit 523 returns the registration result of the device 3 (for example, the object name that is the name of the device 3, and the device certificate) to the relay application (step S703). On the other hand, if the registration of the device 3 fails, the device registration function unit 523 returns an error to the relay application. In this case, the relay application cannot obtain the device certificate.

[0046] Next, the relay application requests the IoT platform 5 to register initial setting values, which are initial values ​​of the device setting values ​​(step S704). At that time, the relay application passes the device type, serial ID, and device initial setting values ​​to the IoT platform 5. Then, the device setting management function unit 522 of the IoT platform 5 registers the device type, serial ID, device initial setting values, and user information in the device setting database. In addition, the device setting management function unit 522 returns the registration result of the device setting values ​​to the relay application (step S705).

[0047] Next, the relay application of the user terminal 2 requests the IoT platform 5 to grant one license for executing the application 4 in the device 3 (step S706). If the user holds the requested license, the license management function unit 524 of the IoT platform 5 assigns the license to the device 3 and returns the license grant result to the relay application (step S707). The relay application displays the device registration result on the device registration screen (step S708).

[0048] Fig. 8 is a sequence diagram showing an example of the flow of the process of changing the device setting values ​​in the IoT system according to this embodiment. Next, an example of the flow of the process of changing the device setting values ​​in the IoT system according to this embodiment will be described with reference to Fig. 8. Here, it is assumed that the user has previously logged in to the IoT platform 5 from the user authentication screen.

[0049] The user starts the relay application of the user terminal 2 and displays the device setting screen. Next, on the device setting screen, the user selects the device 3 for which the device setting values ​​are to be changed from among the registered devices 3 and presses the setting button (step S801). Next, in order to display the device setting values ​​on the device setting screen, the relay application acquires the device setting values ​​of the selected device 3 from the IoT platform 5 (step S802). At that time, the relay application passes the device type, serial ID, etc. of the selected device 3 to the IoT platform 5 and acquires the device setting values ​​of the selected device 3.

[0050] The device setting management function unit 522 of the IoT platform 5 uses the device type and serial ID received from the relay application as a query, acquires device setting values ​​(setting information) from the device setting database, and returns the acquired information to the relay application (step S803). The relay application displays the device setting screen of the device 3 selected by the user (step S804). At this time, the relay application includes the device setting values ​​acquired from the IoT platform 5 in the device setting screen.

[0051] Next, when the user changes the device setting values ​​on the device setting screen and presses the OK button (step S805), the relay application requests the IoT platform 5 to change the device setting values ​​(step S806). At that time, the relay application passes the device type, serial ID, and device setting values ​​to the IoT platform 5.

[0052] The device setting management function unit 522 of the IoT platform 5 updates the device setting database with the requested device setting values. The device setting management function unit 522 of the IoT platform 5 returns the registration result of the device setting values ​​to the relay application (step S807). Thereafter, the relay application displays the change result of the device setting values ​​on the device setting screen (step S808).

[0053] FIG. 9 is a sequence diagram showing an example of the flow of a setting process for device replacement permission in the IoT system according to this embodiment. Next, an example of the flow of a setting process for device replacement permission in the IoT system according to this embodiment will be described with reference to FIG. 9. Here, it is assumed that a user has previously logged in to the IoT platform 5 from a user authentication screen. Also, here, the broken device 3 is assumed to be a replacement device A, and the device 3 to be replaced is assumed to be a replacement device B. If the replacement device A has broken down and recovery is not expected, the user contacts a service provider (step S901) and requests replacement of the device 3. The service provider arranges for and obtains the replacement device B (step S902).

[0054] The service provider uses a service provider application (device replacement permission function unit 101) included in the service provider terminal 1 to select the failed replacement source device A, input the device type and serial ID of the replacement destination device B, and press the replacement permission button (step S903). The service provider application sends a registration request for device replacement permission to the IoT platform 5 (step S904). At that time, the service provider application includes the user's email address, the device type and serial ID of the replacement source device A, and the device type and serial ID of the replacement destination device B in the registration request for device replacement permission. In this embodiment, the user's email address is included in the registration request for device replacement permission, but any user information that can identify the user may be included, and a user ID other than the user's email address may also be included in the registration request for device replacement permission.

[0055] The device replacement function unit 526 of the IoT platform 5 registers the email address as user information, the replacement source device information of the replacement source device A, and the replacement destination device information of the replacement destination device B in the device replacement database, and returns the registration result to the service provider application (step S905). The service provider application displays the result of the replacement permission to the service provider (step S906). The service provider sends the replacement destination device B to the user and contacts them (step S907).

[0056] 10 is a sequence diagram showing an example of a flow of a setting process for replacing a device in the IoT system according to the present embodiment. Next, an example of a flow of a setting process for replacing a device 3 in the IoT system according to the present embodiment will be described with reference to FIG.

[0057] It is assumed that the user has obtained a replacement device in advance. It is also assumed that the user has started up a relay application on the user terminal 2 and logged in to the user authentication function unit 521 of the IoT platform 5 from the user authentication screen. Here, the faulty device 3 is assumed to be a replacement device A, and the device 3 to be replaced is assumed to be a replacement device B.

[0058] First, the user launches the relay application and displays the device replacement screen. Next, the user selects replacement source device A on the device replacement screen and presses the Replace button (step S1001). The relay application requests the IoT platform 5 to acquire a list of devices 3 that can be replaced by the selected replacement source device A (step S1002). At that time, the relay application passes user information (e.g., email address), the device type and serial ID of replacement source device A to the IoT platform 5.

[0059] The device replacement function unit 526 of the IoT platform 5 searches the device replacement database using the user information (email address), the device type and device ID of the replacement source device A, obtains a list of devices 3 that can be replaced with the replacement source device A, and returns the list to the relay application (step S1003). The relay application displays the list of devices 3 on the device replacement screen (step S1004).

[0060] On the device replacement screen, the user selects replacement device B from the list of devices 3 and presses the Replace button (step S1005). The relay application requests the IoT platform 5 to register replacement device B (step S1006). At that time, the relay application passes the device type and serial ID of replacement device B to the IoT platform 5.

[0061] The device registration function unit 523 of the IoT platform 5 registers the replacement device B and returns the device registration result (for example, the object name of the replacement device B) and the device certificate to the relay application (step S1007). The relay application registers the replacement setting for the replacement source device A in the IoT platform 5 (step S1008). At that time, the relay application passes the device type, serial ID, and object name of the replacement source device A to the IoT platform 5.

[0062] The device replacement function unit 526 of the IoT platform 5 searches the device replacement database using user information (e.g., email address), the device type and serial ID of the replacement source device A, and registers the object name of the replacement source device A. Furthermore, the device replacement function unit 526 of the IoT platform 5 performs subscription settings for MQTT topics ( / service / {object name of device B} / app / request -> / service / {object name of device A} / app / request, / service / {object name of device A} / app / response -> / service / {object name of device B} / app / response) (step S1009). That is, the device replacement function unit 526 converts the request of the replacement destination device B by MQTT into a request of the replacement source device A, and converts the response of the replacement source device A into a response of the replacement destination device B. The device replacement function unit 526 of the IoT platform 5 returns the result of the replacement registration of the device 3 to the relay application (step S1010). However, if the service provider has not set device replacement permission, replacement of device 3 cannot be registered.

[0063] The relay application requests the device setting management function unit 522 of the IoT platform 5 to copy the device setting values ​​of the replacement source device A, which are managed by the device setting management function unit 522, to the replacement destination device B (step S1011). The device setting management function unit 522 of the IoT platform 5 obtains the device setting values ​​of the replacement source device A from the device setting database, copies them to the device setting values ​​of the replacement destination device B, and returns the copy result of the device setting values ​​to the relay application (step S1012). However, if the service provider has not set up permission to replace device 3, the copying of the device setting values ​​fails. Thereafter, the relay application displays the result of replacing device 3 on the device replacement screen (step S1013).

[0064] Fig. 11 is a sequence diagram showing an example of the flow of an application execution process by a device in an IoT system according to this embodiment. Next, an example of the flow of an application execution process by a device 3 in the IoT system according to this embodiment will be described with reference to Fig. 11. Here, it is assumed that registration of the device 3 or replacement setting of the replacement device B has been completed and a device certificate has been obtained. Also, here, the failed device 3 is assumed to be replacement source device A, and the replacement device 3 is assumed to be replacement device B.

[0065] The device 3 requests the relay application (application execution request function unit 527) to execute the application 4 (step S1101). The application execution request function unit 527 sends a device certificate to the device registration function unit 523 of the IoT platform 5 and obtains authorization for the device 3 from the device registration function unit 523 (step S1102). The device registration function unit 523 of the IoT platform 5 returns an access token for the device 3 to the application execution request function unit 527 (step S1103).

[0066] The application execution request function unit 527 publishes a topic name: / service / {device thing name} / app / request to the application execution function unit 525 of the IoT platform 5, and requests execution of the application 4 by MQTT (step S1104). That is, the application execution request function unit 527 passes the access token of the device 3 to the application execution function unit 525.

[0067] The application execution function unit 525 of the IoT platform 5 executes application 4 (step S1105). At this time, if a replacement setting for device 3 (setting to replace original device A with replacement destination device B) has been configured, topic name: / service / {thing name of device B} / app / request is subscribed to and application 4 is executed, so application 4 is executed by original device A.

[0068] When application 4 is executed, application 4 returns the execution result to the IoT platform 5 (step S1106). At this time, if a replacement setting for device 3 (setting to replace replacement source device A with replacement destination device B) has been made, the application execution function unit 525 subscribes to the topic name: / service / {thing name of device A} / app / response and the topic name: / service / {thing name of device B} / app / response, and obtains the execution result of application 4. Thereafter, the application execution function unit 525 of the IoT platform 5 returns the execution result of application 4 to the application execution request function unit 527 of the relay application (step S1107).

[0069] Fig. 12 is a sequence diagram showing an example of the flow of a process for canceling the replacement setting of a device in the IoT system according to this embodiment. Next, an example of the flow of a process for canceling the replacement setting of device 3 in the IoT system according to this embodiment will be described with reference to Fig. 12. Here, it is assumed that a user has logged in to the IoT system in advance. It is also assumed that the replacement setting from replacement source device A to replacement destination device B has been completed. It is also assumed that the failed device 3 is replacement source device A, and the device 3 to be replaced is replacement destination device B.

[0070] The user launches the relay application of the user terminal 2 and displays a replacement setting screen. Furthermore, the user selects the replacement source device A on the replacement setting screen and presses the release button for replacement (step S1201). The relay application confirms that the device A is connected to the IoT system, and if the replacement source device A is connected to the IoT system, requests the device setting management function unit 522 of the IoT platform 5 to copy the device setting values ​​of the replacement destination device B to the replacement source device A (step S1202). At this time, the relay application notifies the device setting management function unit 522 of the IoT platform 5 of the device type and serial ID of the replacement source device A and the device type and serial ID of the replacement destination device B.

[0071] The device setting management function unit 522 of the IoT platform 5 obtains the device setting values ​​of the replacement device B from the device setting database, copies them to the device setting values ​​of the replacement source device A, and returns the copy result of the device setting values ​​to the relay application (step S1203). However, if the service provider has not set up replacement permission for the device 3, the copying of the device setting values ​​fails.

[0072] Next, the relay application requests the device replacement function unit 526 of the IoT platform 5 to cancel the replacement setting of the replacement source device A (step S1204). The device replacement function unit 526 of the IoT platform 5 deletes the subscription setting of the MQTT topic ( / service / {thing name of device B} / app / request -> / service / {thing name of device A} / app / request, / service / {thing name of device A} / app / response -> / service / {thing name of device B} / app / response) (step S1205). That is, the device replacement function unit 526 converts the request from the replacement destination device B by MQTT into a request of the replacement source device A, and converts the response of the replacement source device A into a response of the replacement destination device B. The device replacement function unit 526 of the IoT platform 5 searches the device replacement database for user information (e.g., email address), the device type and serial ID of the replacement source device A, and deletes the record (step S1206). Furthermore, the device replacement function unit 526 of the IoT platform 5 returns the result of the replacement registration of the device 3 to the relay application (step S1207).

[0073] Thereafter, the relay application requests the device registration function unit 523 of the IoT platform 5 to cancel the device registration of the replacement device B (step S1208). Then, the device registration function unit 523 of the IoT platform 5 returns the result of the device cancellation to the relay application (step S1209). Furthermore, the relay application displays the result of the device cancellation on the replacement setting screen.

[0074] As described above, according to the IoT system of the present embodiment, when the device 3 is replaced with an alternative device, the user does not need to switch the license from the device 3 to the alternative device. As a result, when the device 3 breaks down and an alternative device is temporarily used, the user can easily switch the device 3 without having to switch the license associated with the device 3, take over the device settings, etc.

[0075] 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).

[0076] 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.

[0077] The program executed by the IoT platform 5 of this embodiment has a modular configuration including the above-mentioned units (user authentication function unit 521, device setting management function unit 522, device registration function unit 523, license management function unit 524, application execution function unit 525, and device replacement function unit 526), ​​and in actual hardware, the CPU 501 (an example of a processor) reads and executes the program from the ROM 502, thereby loading the above-mentioned units onto the main memory, and the user authentication function unit 521, device setting management function unit 522, device registration function unit 523, license management function unit 524, application execution function unit 525, and device replacement function unit 526 are generated on the main memory. [Explanation of symbols]

[0078] 1. Service provider terminal 2. User terminal 3 Devices 4. Applications 5 IoT Platform 501 CPU 502 ROM 503 RAM 521 User authentication function unit 522 Device setting management function unit 523 Device Registration Function Unit 524 License Management Function Unit 525 Application execution function unit 526 Device Replacement Function Unit 527 Application execution request function unit [Prior art documents] [Patent documents]

[0079] [Patent Document 1] Patent No. 5034109

Claims

1. a device registration unit for registering a device; a license management unit that allocates application licenses to the devices registered by the device registration unit; an application execution function unit that executes the application for which a license is assigned to the device in response to an application execution request for the application from the device; a device replacement function unit that registers a replacement setting of the device with another device and converts the application execution request from the replaced device into the application execution request from the device before replacement; An information processing device comprising:

2. further comprising a user authentication unit that executes login of a registered user; 2. The information processing device according to claim 1, wherein the device replacement function unit registers a replacement setting for the device selected in the relay application to the other device after the user logs in by the user authentication unit, and responds to an inquiry from the relay application about registration of the replacement setting for the other device by replying to the relay application whether or not a replacement setting for the other device has been registered.

3. The information processing apparatus according to claim 2 , further comprising a device setting management function unit that records setting information of the device and copies the setting information of the device before replacement to the other device that has replaced the device.

4. The information processing apparatus according to claim 3 , wherein the device setting management function unit transmits the setting information of the device before replacement to the relay application, and instructs the relay application to copy the setting information to the other device that has replaced the device.

5. The information processing apparatus according to claim 2 , wherein the device replacement function unit cancels the registration of the replacement setting to the other device in response to a request from the relay application to cancel the registration of the replacement setting to the other device.

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 license management unit assigns a license for an application to the device registered by the device registration unit; an application execution function unit executing the application for which a license is assigned to the device in response to an application execution request from the device; a step in which a device replacement function unit registers a replacement setting of the device with another device, and converts the application execution request from the other device into the application execution request from the device before replacement; An information processing method including:

7. Computer, a device registration unit for registering a device; a license management unit that allocates application licenses to the devices registered by the device registration unit; an application execution function unit that executes the application for which a license is assigned to the device in response to an application execution request for the application from the device; a device replacement function unit that registers a replacement setting of the device with another device and converts the application execution request from the replaced device into the application execution request from the device before replacement; A program to make it function as such.

Images