Gateway device, information processing system, information processing method and program

Abstract

To provide a gateway device capable of preventing data from an IoT corresponding to a service from being collected and stored if the service is not contracted, an information processing system, an information processing method and a program.SOLUTION: A gateway device with a plug-in for performing data communication with one or more IoT devices installed includes a setting holding part for holding setting information for associating a device schema for performing data conversion about data received from an IoT device with a validation flag showing whether to validate the data conversion, a request part for requesting a cloud system of association information showing a service and the device schema, and a specification part for specifying the device schema on the basis of the association information and the setting information, and the setting holding part validates the validation flag corresponding to the specified device schema and nullifies the validation flag corresponding to an unspecified device schema.SELECTED DRAWING: Figure 4

Description

[Technical Field]

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

[0002] IoT (Internet of Things) is a technology that connects various devices (IoT devices) such as sensors, mobile terminals, digital home appliances, and various industrial devices to the Internet, collects and stores data in the cloud, and uses that data to provide services such as visualization, analysis, and device control.

[0003] As an IoT technology, a gateway configuration has been disclosed for collecting and storing various types of sensor data in the cloud (for example, Patent Document 1). The gateway supports various communication standards and has a plug-in that converts sensor data received from IoT devices into a predefined data structure. The data converted by the gateway's plug-in is then sent to the cloud. Summary of the Invention [Problem to be solved by the invention]

[0004] However, the technology described in Patent Document 1 has the problem that if a user does not sign a contract for the service, unnecessary data is collected and stored in the cloud from IoT devices that are compatible with the service.

[0005] The present invention has been made in consideration of the above, and aims to provide a gateway device, an information processing system, an information processing method, and a program that can prevent data from being collected and stored from IoT devices that are compatible with a service when a service contract has not been made. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the object, the present invention provides a gateway device having a plug-in installed therein for communicating data with one or more IoT devices, the gateway device comprising: a setting storage unit that stores setting information associating a device schema for converting data received from an IoT device with an activation flag indicating whether data conversion using the device schema is enabled; a request unit that requests association information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; and an identification unit that identifies a device schema to be used in the service based on the association information received from the cloud system in response to a request by the request unit and the setting information stored in the setting storage unit, wherein the setting storage unit enables the activation flag corresponding to the device schema identified by the identification unit and disables the activation flag corresponding to an unidentified device schema. [Effects of the Invention]

[0007] According to the present invention, if a service contract has not been made, it is possible to prevent data from being collected and stored from IoT devices that are compatible with the service. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of the overall configuration of an information processing system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a gateway according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a hardware configuration of a cloud system according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a functional block configuration of the information processing system according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the data configuration of the device cooperation management information. [Figure 6]FIG. 6 is a diagram illustrating an example of a data configuration of device cooperation information transmitted to the gateway. [Figure 7-1] FIG. 7A is a sequence diagram illustrating an example of the flow of operations when a service of the information processing system according to the embodiment is cancelled. [Figure 7-2] FIG. 7B is a sequence diagram illustrating an example of the flow of operations when a service of the information processing system according to the embodiment is cancelled. [Figure 8] FIG. 8 is a diagram showing an example of a state when a service of the information processing system according to the embodiment is cancelled. [Figure 9] FIG. 9 is a diagram illustrating an example of the data configuration of device cooperation information transmitted to the gateway when a service is canceled. [Figure 10-1] FIG. 10A is a sequence diagram illustrating an example of an operation flow when a new IoT device becomes able to cooperate with a contracted service of the information processing system according to the embodiment. [Figure 10-2] FIG. 10B is a sequence diagram illustrating an example of an operation flow when a new IoT device becomes able to cooperate with a contracted service of the information processing system according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of a state in which a new IoT device becomes able to cooperate with a contracted service of the information processing system according to the embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of the data configuration of device linkage information transmitted to the gateway when a new IoT device becomes able to link with a contracted service. [Figure 13] FIG. 13 is a sequence diagram showing an example of the flow of operations when a new service contract is made in the information processing system according to the embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a state in which a new service contract is made in the information processing system according to the embodiment. [Figure 15]FIG. 15 is a diagram illustrating an example of the data configuration of device cooperation information transmitted to the gateway when a new service contract is made. [Figure 16] FIG. 16 is a sequence diagram showing an example of the flow of operations when a contract for a service of the information processing system according to the embodiment is further made. [Figure 17] FIG. 17 is a diagram showing an example of a state when an additional service contract is made for the information processing system according to the embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of the data configuration of device cooperation information transmitted to the gateway when an additional service contract is made. [Figure 19-1] FIG. 19A is a sequence diagram illustrating an example of an operation flow when a contract is further made for services corresponding to input and output devices of the information processing system according to the embodiment. [Figure 19-2] FIG. 19B is a sequence diagram illustrating an example of an operation flow when a contract is further made for services corresponding to the input device and the output device of the information processing system according to the embodiment. [Figure 20] FIG. 20 is a diagram showing an example of a state in which a contract is further made for services corresponding to input and output devices of the information processing system according to the embodiment. [Figure 21] FIG. 21 is a diagram illustrating an example of a state when a new IoT device is added to the information processing system according to the embodiment. [Figure 22] FIG. 22 is a diagram illustrating an example of a state when a new plug-in is developed in the information processing system according to the embodiment. [Figure 23] FIG. 23 is a diagram illustrating an example of a state in which a plug-in is updated in the information processing system according to the embodiment. [Figure 24] FIG. 24 is a diagram illustrating an example of a state in which a new device schema is enabled in the information processing system according to the embodiment. [Figure 25]FIG. 25 is a diagram illustrating a state in which the structure of an existing device schema is changed in an information processing system according to a modified example. [Figure 26] FIG. 26 is a diagram illustrating an operation of updating a device schema in an information processing system according to a modified example. DETAILED DESCRIPTION OF THE INVENTION

[0009] Below, with reference to the drawings, embodiments of a gateway device, an information processing system, an information processing method, and a program according to the present invention will be described in detail. Furthermore, the present invention is not limited to the following embodiments, and the components in the following embodiments include those that would be easily conceived by a person skilled in the art, those that are substantially the same, and those that are within the scope of what is called equivalents. Furthermore, various omissions, substitutions, modifications, and combinations of the components can be made without departing from the spirit of the following embodiments.

[0010] (Overall configuration of information processing system) 1 is a diagram showing an example of the overall configuration of an information processing system according to an embodiment, and the overall configuration of the information processing system 1 according to this embodiment will be described with reference to FIG.

[0011] The information processing system 1 shown in Fig. 1 is an information processing system for collecting and storing data acquired from IoT devices and providing various cloud services using the data. As shown in Fig. 1, the information processing system 1 includes a gateway 10, IoT devices 20-1 to 20-3, and a cloud system 30. The gateway 10 and the cloud system 30 are capable of communicating data with each other via a network N such as the Internet.

[0012] The gateway 10 is an IoT gateway that converts data detected by the IoT devices 20-1 to 20-3 into a predetermined data structure using an installed plug-in and transmits the data to the cloud system 30 via the network N. The gateway 10 is installed, for example, in the residence or office of a subscriber who has signed up for a cloud service provided by the cloud system 30.

[0013] The IoT devices 20-1 to 20-3 are IoT devices that detect and acquire (hereinafter simply referred to as "detection") various data used by the cloud system 30 to provide cloud services, and transmit the data to the gateway 10, or perform output operations related to the provision of the cloud services. The IoT devices 20-1 to 20-3 are installed, for example, in the living space or office of a subscriber who has signed up for the cloud services provided by the cloud system 30.

[0014] Note that the IoT devices 20-1 to 20-3 will be referred to simply as "IoT devices 20" when referring to any IoT device or when collectively referring to the IoT devices. Although FIG. 1 shows three IoT devices 20-1 to 20-3, the number of devices is not limited to this. Among the IoT devices 20, an IoT device that detects various data used by the cloud system 30 to provide cloud services and transmits the data to the gateway 10 may be referred to as an "input device," and an IoT device that performs output operations related to the provision of the cloud services may be referred to as an "output device." Examples of input devices include environmental sensors that detect temperature, humidity, or carbon dioxide levels, cameras that capture images, and illuminance sensors that detect illuminance. Examples of output devices include warning lights such as PATLITE (registered trademark) that issue warnings, display devices that display messages, and control devices that control specific devices in response to instructions from the cloud system 30.

[0015] The cloud system 30 is an information processing system that collects and stores data detected by the IoT devices 20 and provides various cloud services using the data.

[0016] The cloud system 30 may be configured by a single information processing device, or may be configured by a plurality of information processing devices.

[0017] (Gateway hardware configuration) 2 is a diagram showing an example of the hardware configuration of a gateway according to an embodiment, and the hardware configuration of the gateway 10 according to this embodiment will be described with reference to FIG.

[0018] As shown in FIG. 2, the gateway 10 includes a CPU (Central Processing Unit) 501, a RAM (Random Access Memory) 502, a storage 503 (memory unit), a long-distance communication circuit 511, and a short-distance communication circuit 512.

[0019] The CPU 501 is a computing device that controls the overall operation of the gateway 10. The RAM 502 is a volatile storage device that is used as a work area for the CPU 501.

[0020] The storage 503 is a non-volatile storage device such as a semiconductor memory that stores plug-ins for communicating with the IoT device 20, programs such as a gateway application that controls the operation of the gateway 10, and control data.

[0021] The long-distance communication circuit 511 is a communication circuit that performs wireless communication with other devices such as the cloud system 30 via the network N in accordance with standards such as Wi-Fi (registered trademark). Note that the long-distance communication circuit 511 is not limited to performing wireless communication, and may also perform wired communication.

[0022] The short-distance communication circuit 512 is a communication circuit that performs short-distance wireless communication with the IoT device 20 according to standards such as NFC (Near Field Communication) or Bluetooth (registered trademark). Note that the long-distance communication circuit 511 is not limited to performing wireless communication, and may perform wired communication according to, for example, the USB (Universal Serial Bus) standard.

[0023] The above-mentioned CPU 501, RAM 502, storage 503, long-distance communication circuit 511, and short-distance communication circuit 512 are communicatively connected to one another by a bus 510 such as an address bus and a data bus.

[0024] The hardware configuration of the gateway 10 shown in FIG. 2 is an example, and it is not necessary for the gateway 10 to include all of the components, and other components may also be included.

[0025] (Cloud system hardware configuration) 3 is a diagram showing an example of the hardware configuration of a cloud system according to an embodiment, The hardware configuration of a cloud system 30 according to this embodiment will be described with reference to FIG.

[0026] As shown in FIG. 3, the cloud system 30 includes a CPU 601, a ROM 602, a RAM 603, an auxiliary storage device 605, a media drive 607, a display 608, a network I / F 609, a keyboard 611, a mouse 612, and a DVD (Digital Versatile Disc) drive 614.

[0027] The CPU 601 is a computing device that controls the overall operation of the cloud system 30. The ROM 602 is a non-volatile storage device that stores programs for the cloud system 30. The RAM 603 is a volatile storage device that is used as a work area for the CPU 601.

[0028] The auxiliary storage device 605 is a storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) that stores information relating a subscriber, a cloud service, and a device schema of data used in the cloud service, as well as detailed information about the device schema. Here, the device schema refers to a predetermined data structure of data used by the cloud system 30 to provide the cloud service.

[0029] The media drive 607 is a device that controls reading and writing of data from and to a recording medium 606 such as a flash memory under the control of the CPU 601 .

[0030] The display 608 is a display device configured with a liquid crystal or organic EL (Electro Luminescence) display, etc., that displays various information such as a cursor, a menu, a window, characters, or an image.

[0031] The network I / F 609 is an interface for communicating data with external devices such as the gateway 10 using the network N. The network I / F 609 is, for example, a NIC (Network Interface Card) that supports Ethernet (registered trademark) and is capable of communication in accordance with TCP (Transmission Control Protocol) / IP (Internet Protocol) or the like.

[0032] The keyboard 611 is an input device for selecting letters, numbers, and various instructions, moving the cursor, etc. The mouse 612 is an input device for selecting and executing various instructions, selecting a processing target, moving the cursor, etc.

[0033] The DVD drive 614 is a device that controls reading and writing of data from and to a DVD 613 such as a DVD-ROM or a DVD-R (Digital Versatile Disk Recordable) as an example of a removable storage medium.

[0034] The above-mentioned CPU 601, ROM 602, RAM 603, auxiliary storage device 605, media drive 607, display 608, network I / F 609, keyboard 611, mouse 612 and DVD drive 614 are communicatively connected to each other via a bus 610 such as an address bus and a data bus.

[0035] The hardware configuration of the cloud system 30 shown in FIG. 3 is an example, and it is not necessary to include all of the components shown in FIG. 3, or other components may be included.

[0036] (Configuration and operation of functional blocks of information processing systems) Fig. 4 is a diagram showing an example of the configuration of functional blocks of an information processing system according to an embodiment. Fig. 5 is a diagram showing an example of the data configuration of device cooperation management information. Fig. 6 is a diagram showing an example of the data configuration of device cooperation information transmitted to a gateway. The configuration and operation of functional blocks of the information processing system 1 according to this embodiment will be described with reference to Figs. 4 to 6. Note that in Fig. 4, the information processing system 1 will be described as including input devices 20A1, 20A2, and 20B and output devices 20C and 20D as IoT devices 20.

[0037] As shown in Fig. 4, the gateway 10 has installed therein a plug-in PA and a PC, and also has installed therein a gateway application GA. The gateway 10 has a device communication unit 101a, a data conversion unit 102a, and a linked device settings storage unit 103a as functional units realized by the CPU 501 executing the plug-in PA. The gateway 10 also has a device communication unit 101c, a data conversion unit 102c, and a linked device settings storage unit 103c as functional units realized by the CPU 501 executing the plug-in PC. The gateway 10 also has a communication unit 111, a linked information request unit 112 (request unit), a specification unit 113, an update confirmation unit 114 (confirmation unit), and an update unit 115 as functional units realized by the CPU 501 executing the gateway application GA.

[0038] The device communication unit 101a is a functional unit that performs data communication with the input devices 20A1, 20A2, and 20B via the short-range communication circuit 512. For example, the device communication unit 101a receives data detected by the input devices 20A1, 20A2, and 20B via the short-range communication circuit 512.

[0039] The data conversion unit 102a is a functional unit that converts data received by the device communication unit 101a into a corresponding device schema using the linked device setting information stored in the linked device setting storage unit 103a.

[0040] The linked device setting storage unit 103a is a functional unit (setting storage unit) that stores linked device setting information (setting information) in which information on a device schema for data conversion of data received from the IoT device 20 is associated with an enable flag indicating whether data conversion using the device schema is enabled or disabled. The linked device setting information is information in which information on a device schema is associated with an enable flag indicating whether data conversion using the device schema is enabled or disabled. In the example shown in FIG. 4, the linked device setting information includes information on device schemas DSA1, DSA2, and DSB as device schema information, and stores an enable flag corresponding to each device schema in association with each other. Among these, device schema DSA1 is a device schema used for data conversion of data detected by the input device 20A1, device schema DSA2 is a device schema used for data conversion of data detected by the input device 20A2, and device schema DSB is a device schema used for data conversion of data detected by the input device 20B. Furthermore, the linked device setting storage unit 103a disables the device schema by turning OFF the enable flag of the device schema in the linked device setting information stored in the linked device setting storage unit 103a based on the identification information. Furthermore, the linked device setting storage unit 103a enables the device schema by turning ON the enable flag of the device schema in the linked device setting information stored in the linked device setting storage unit 103a based on the identification information.

[0041] The activation flag in the linked device setting information may be stored in the storage 503 so that it can be updated by a gateway application GA (described later). The device schema information in the linked device setting information may be directly incorporated in the plug-in PA, or may be expanded and stored in the storage 503 when the plug-in PA is installed.

[0042] The device communication unit 101c is a functional unit that performs data communication with the output devices 20C and 20D via the short-range communication circuit 512. For example, the device communication unit 101c transmits control data and the like for causing the output devices 20C and 20D to perform output operations via the short-range communication circuit 512.

[0043] The data conversion unit 102c is a functional unit that converts data to be transmitted to the device communication unit 101c into a corresponding device schema using the linked device setting information stored in the linked device setting storage unit 103c.

[0044] The linked device setting storage unit 103c is a functional unit (setting storage unit) that stores linked device setting information (setting information) that associates information about a device schema for converting data to be transmitted to the IoT device 20 with an enable flag indicating whether data conversion using the device schema is enabled or disabled. In the example shown in FIG. 4, the linked device setting information includes information about the device schemas DSC and DSD as device schema information, and an enable flag corresponding to each device schema is associated and stored. Among these, the device schema DSC is a device schema used for data conversion of data received from the output device 20C, and the device schema DSD is a device schema used for data conversion of data received from the output device 20D. Furthermore, the linked device setting storage unit 103c disables the device schema by turning off the enable flag of the device schema in the linked device setting information stored in the linked device setting storage unit 103c based on the specific information. Furthermore, the linked device setting storage unit 103c sets the validity flag of the device schema to ON in the linked device setting information stored in the linked device setting storage unit 103c based on the identification information, thereby validating the device schema.

[0045] The activation flag in the linked device setting information may be stored in the storage 503 so that it can be updated by a gateway application GA, which will be described later. The device schema information in the linked device setting information may be directly embedded in the plug-in PC, or may be expanded and stored in the storage 503 when the plug-in PC is installed.

[0046] The communication unit 111 is a functional unit that performs data communication with the cloud system 30 via a long-distance communication circuit 511 .

[0047] The cooperation information request unit 112 is a functional unit that requests device cooperation information (cooperation information), which is a list of services subscribed to by the user and device schemas used in the services, from the cloud system 30 via the communication unit 111 at predetermined intervals (for example, 12 hours). The cooperation information request unit 112 receives the device cooperation information (cooperation information) from the cloud system 30 via the communication unit 111.

[0048] The identification unit 113 is a functional unit that compares the device collaboration information acquired by the collaboration information request unit 112 with the collaboration device setting information stored in the collaboration device setting storage units 103a and 103c to identify the device schema to be used in the plug-in PA and PC. Note that identifying the device schema to be used in the plug-in includes any of the following meanings: identifying only the device schema to be used in the plug-in, identifying a device schema that does not use the plug-in, and identifying both the device schema to be used in the plug-in and the device schema that is not used.

[0049] The update confirmation unit 114 is a functional unit that requests the cloud system 30, via the communication unit 111, to confirm whether or not a plug-in (plug-in PA, PC in the example shown in FIG. 4) installed in the gateway 10 needs to be updated at predetermined intervals (for example, once a day). Note that the update confirmation unit 114 may also request the cloud system 30 to confirm whether or not a plug-in needs to be updated by manual operation using a user's PC or the like that is communicably connected to the gateway 10.

[0050] The update unit 115 is a functional unit that updates an existing plug-in installed in the gateway 10 with an update plug-in received from the cloud system 30 in response to a request from the update check unit 114 .

[0051] At least a portion of each functional unit realized by executing the gateway application GA shown in FIG. 4 may be realized by a hardware circuit such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit).

[0052] Furthermore, the functional units realized by executing the gateway application GA shown in Fig. 4 are conceptual representations of functions, and are not limited to such configurations. For example, the multiple functional units illustrated as independent functional units in the gateway application GA shown in Fig. 4 may be configured as a single functional unit. On the other hand, the function of a single functional unit in the gateway application GA shown in Fig. 4 may be divided into multiple functional units and configured as multiple functional units.

[0053] 4, the cloud system 30 includes a communication unit 301, a linkage information processing unit 302, an update management unit 303, a device linkage management DB 304, and a device schema information DB 305. In the example shown in Fig. 4, the cloud system 30 is capable of providing a food temperature management service 311, a CO2 concentration measurement service 312, and a temperature anomaly detection service 313 as linkage services 310, which are cloud services that can be provided.

[0054] The communication unit 301 is a functional unit that performs data communication with the gateway 10 via the network I / F 609 .

[0055] The collaboration information processing unit 302 is a functional unit that, in response to a request for device collaboration information from the gateway 10, refers to the device collaboration management DB 304, extracts device collaboration information corresponding to the user corresponding to the request, and transmits the device collaboration information to the gateway 10 via the communication unit 301. The device collaboration information is information that associates a user (contractor), a service to which the user has subscribed, and a device schema used in the service. For example, FIG. 6 shows an example of device collaboration information extracted by the collaboration information processing unit 302 from device collaboration management information (described later) in the device collaboration management DB 304 in response to a request for device collaboration information from the gateway 10 corresponding to the contractor "customer CA." The device collaboration information shown in FIG. 6 indicates that the contractor "customer CA" has subscribed to the "food temperature management service," "CO2 concentration measurement service," and "temperature abnormality detection service," and that the device schema used in the "food temperature management service" is device schema DSA1, the device schema used in the "CO2 concentration measurement service" is device schema DSA2, and the device schemas used in the "temperature abnormality detection service" are device schemas DSA1, DSB, DSC, and DSD.

[0056] The update management unit 303 is a functional unit that, in response to a request from the gateway 10 to confirm whether a plug-in needs to be updated, checks whether a plug-in needs to be updated for the gateway 10. If a plug-in for update is available, the update management unit 303 transmits the plug-in for update to the gateway 10 via the communication unit 301.

[0057] The device cooperation management DB 304 is a database that stores and manages device cooperation management information. The device cooperation management information is, for example, information that associates a contractor who is a user (customer), an cooperation service to which the contractor has subscribed, and a device schema used in the cooperation service, as shown in FIG. 5. That is, in the device cooperation management DB 304, the cooperation service to which each contractor has subscribed and the device schema used in the cooperation service are collectively managed as device cooperation management information. The device cooperation management DB 304 is realized, for example, as a database stored in the auxiliary storage device 605 shown in FIG. 3. The device cooperation management DB 304 may be stored and managed in storage on a network separate from the cloud system 30.

[0058] The device schema information DB 305 is a database that stores and manages device schema information, as shown in Fig. 4. Device schema information is, for example, information that associates a device schema name, a device type that is the type of device schema referred to by the device schema name, and the data structure of the device schema, as shown in Fig. 4. The device schema information DB 305 is realized, for example, as a database stored in the auxiliary storage device 605 shown in Fig. 3. Note that the device schema information DB 305 may also be stored and managed in storage on a network separate from the cloud system 30.

[0059] The above-described communication unit 301, cooperation information processing unit 302, and update management unit 303 are realized by executing a program by CPU 601 shown in Fig. 3. Note that at least a part of the communication unit 301, cooperation information processing unit 302, and update management unit 303 may be realized by a hardware circuit such as an FPGA or an ASIC.

[0060] Furthermore, the functional units of the cloud system 30 shown in Fig. 4 are conceptual representations of functions, and are not limited to such a configuration. For example, the multiple functional units illustrated as independent functional units in the cloud system 30 shown in Fig. 4 may be configured as a single functional unit. On the other hand, the function of a single functional unit in the cloud system 30 shown in Fig. 4 may be divided into multiple functional units, and configured as multiple functional units.

[0061] As shown in Table 1 below, the food temperature control service 311 is a service that accumulates temperature data detected by input devices installed in restaurants, kitchens, food factories, etc., and displays the temperature data via a browser. The device schema of the input device that can be used by (i.e., can be linked with) the food temperature control service 311 is device schema DSA1, as shown in Figure 4.

[0062] [Table 1]

[0063] As shown in Table 1 above, the CO2 concentration measurement service 312 is a service that checks carbon dioxide data detected by an input device installed in a room, and sends an alert email to a pre-registered email address if the carbon dioxide concentration indicated by the carbon dioxide data exceeds a predetermined threshold. Also, the device schema of an input device that can be used (i.e., linked) by the CO2 concentration measurement service 312 is device schema DSA2, as shown in Fig. 4.

[0064] The temperature anomaly detection service 313 is a service that checks temperature data detected by an input device such as a thermal camera that captures images of facilities or equipment, and issues a warning by turning on a warning light such as a patrol light, which is an output device, if the temperature indicated by the temperature data exceeds a predetermined threshold. Furthermore, the device schemas of input devices that can be used (i.e., can be linked with) the temperature anomaly detection service 313 are device schemas DSA1 and DSB, as shown in Fig. 4. Furthermore, the device schemas of output devices that can be used (i.e., can be linked with) the temperature anomaly detection service 313 are device schemas DSC and DSD, as shown in Fig. 4.

[0065] (Flow of operations when canceling the service) 7-1 and 7-2 are sequence diagrams illustrating an example of the flow of operations when a service of the information processing system according to the embodiment is canceled. FIG. 8 is a diagram illustrating an example of a state when a service of the information processing system according to the embodiment is canceled. FIG. 9 is a diagram illustrating an example of the data configuration of device linkage information transmitted to the gateway when a service is canceled. A flow of operations when a linkage service is canceled in the information processing system 1 according to the embodiment will be described with reference to FIGS. 7-1, 7-2, 8, and 9. Note that before the operations illustrated in FIGS. 7-1 and 7-2, a user who is "customer CA" is assumed to have contracts with the food temperature management service 311, the CO2 concentration measurement service 312, and the temperature anomaly detection service 313. Therefore, in the linkage device setting information stored in the linkage device setting storage unit 103a, the enable flags of the device schemata DSA1, DSA2, and DSB are each set to ON, and in the linkage device setting information stored in the linkage device setting storage unit 103c, the enable flags of the device schemata DSC and DSD are each set to ON.

[0066] <Step S11> The cooperation information request unit 112 of the gateway application GA of the gateway 10 requests device cooperation information, which is a list of services subscribed to by the user and device schemas used in the services, from the cloud system 30 via the communication unit 111. The request for device cooperation information is transmitted to the cloud system 30 at predetermined time intervals (e.g., every 12 hours). The communication unit 301 of the cloud system 30 then receives the request for device cooperation information.

[0067] <Step S12> The communication unit 301 sends a request for device collaboration information to the collaboration information processing unit 302 .

[0068] <Steps S13 to S15> In response to a request for device collaboration information, collaboration information processing unit 302 refers to device collaboration management DB 304, extracts device collaboration information corresponding to the user corresponding to the request, and sends the device collaboration information to communication unit 301. In this example, it is assumed that the user, "customer CA," has canceled his / her contract for CO2 concentration measurement service 312, and the device collaboration information indicates that the collaborative services subscribed to by the user are food temperature management service 311 and temperature abnormality detection service 313, as shown in Fig. 9, the device schema used for food temperature management service 311 is device schema DSA1, and the device schemas used for temperature abnormality detection service 313 are device schemas DSA1, DSB, DSC, and DSD.

[0069] <Step S16> The communication unit 301 transmits the device cooperation information to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the device cooperation information. Then, the cooperation information request unit 112 acquires the device cooperation information received by the communication unit 111.

[0070] <Steps S17 and S18> The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c to identify the device schemas to be used by the plug-in PA and PC. Specifically, the identification unit 113 identifies the device schemas (DSA1, DSB) that overlap between the data configuration (DSA1, DSB, DSC, DSD) of the device collaboration information shown in Fig. 9 and the device schema information (DSA1, DSA2, DSB) in the collaborative device setting information held by the collaborative device setting holding unit 103a in Fig. 4 as the device schemas to be used by the plug-in PA. Furthermore, the identification unit 113 identifies the device schemas (DSC, DSD) that overlap between the data configuration (DSA1, DSB, DSC, DSD) of the device collaboration information shown in Fig. 9 and the collaborative device setting holding unit 103c (DSC, DSD) in Fig. 4 as the device schemas to be used by the plug-in PC. As a result of comparing the device collaboration information with the collaborative device setting information stored in the collaborative device setting storage units 103a and 103c, the identification unit 113 identifies device schemas DSA1 and DSB as device schemas to be used in the plug-in PA, and device schemas DSC and DSD as device schemas to be used in the plug-in PC.The identification unit 113 then sends identification information indicating the identification results to the plug-in PA and PC.Note that the identification unit 113 may not send the identification information to the plug-in PC because the device collaboration information includes each device schema already used in the plug-in PC.

[0071] <Step S19> 8, the linked device setting storage unit 103a of the plug-in PA turns OFF the enable flag of the device schema DSA2 that has not been identified by the identification unit 113 in the linked device setting information, thereby invalidating the device schema DSA2. That is, the linked device setting storage unit 103a turns OFF the enable flag of the device schema DSA2 in the linked device setting information stored in the linked device setting storage unit 103a, based on the identification information, thereby invalidating the device schema DSA2.

[0072] <Step S20> The input device 20A1 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0073] <Step S21> The data conversion unit 102a of the plug-in PA of the gateway 10 converts the detection data of the input device 20A1 received by the device communication unit 101a into the data structure of the device schema DSA1 of the linked device setting information stored in the linked device setting storage unit 103a.

[0074] <Step S22> Then, the data conversion unit 102a sends the converted detected data (converted data) to the gateway application GA.

[0075] <Step S23> The communication unit 111 of the gateway application GA transmits the converted data to the cloud system 30. Then, the communication unit 301 of the cloud system 30 receives the converted data.

[0076] <Steps S24 and S25> The communication unit 301 refers to the device cooperation management DB 304 and acquires information about the cooperation service 310 that uses the converted data.

[0077] <Steps S26 and S27> Communication unit 301 transmits a service execution request for requesting execution of a service and the converted data to each of food temperature management service 311 and temperature abnormality detection service 313 indicated by the acquired information of linked service 310. As a result, food temperature management service 311 and temperature abnormality detection service 313 each execute a service according to the received converted data of input device 20A1.

[0078] <Steps S28 and S29> The temperature abnormality detection service 313 transmits an output device processing request to the communication unit 301 to request that an output device using the device schemas DSC and DSD execute a predetermined process as a service of the temperature abnormality detection service 313 provided in accordance with the converted data of the input device 20A1. Then, the communication unit 301 transmits the output device processing request to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the output device processing request.

[0079] <Step S30> The communication unit 111 sends the received output device processing request to the plug-in PC.

[0080] <Step S31> In response to an output device processing request, the device communication unit 101c of the plug-in PC transmits control data for executing a specified function to the output device 20C that uses the device schema DSC of the linked device setting information stored in the linked device setting storage unit 103c.

[0081] <Step S32> The output device 20C executes a predetermined function in accordance with the control data received from the plug-in PC.

[0082] <Step S33> In response to an output device processing request, the device communication unit 101c of the plug-in PC transmits control data for executing a predetermined function to the output device 20D that uses the device schema DSD of the linked device setting information stored in the linked device setting storage unit 103c.

[0083] <Step S34> The output device 20D executes a predetermined function in accordance with the control data received from the plug-in PC.

[0084] <Step S35> The input device 20A2 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0085] <Step S36> The data conversion unit 102a of the plug-in PA of the gateway 10 discards the detection data of the input device 20A2 received by the device communication unit 101a because the device schema DSA2 of the linked device setting information stored in the linked device setting storage unit 103a is invalid.

[0086] <Step S37> The input device 20B transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0087] <Step S38> The data conversion unit 102a of the plug-in PA of the gateway 10 converts the detection data of the input device 20B received by the device communication unit 101a into the data structure of the device schema DSB of the linked device setting information stored in the linked device setting storage unit 103a.

[0088] <Step S39> Then, the data conversion unit 102a sends the converted detected data (converted data) to the gateway application GA.

[0089] <Step S40> The communication unit 111 of the gateway application GA transmits the converted data to the cloud system 30. Then, the communication unit 301 of the cloud system 30 receives the converted data.

[0090] <Steps S41 and S42> The communication unit 301 refers to the device cooperation management DB 304 and acquires information about the cooperation service 310 that uses the converted data.

[0091] <Step S43> The communication unit 301 transmits a service execution request for requesting execution of a service and the converted data to the temperature anomaly detection service 313 indicated by the acquired information of the linked service 310. As a result, the temperature anomaly detection service 313 executes the service according to the received converted data of the input device 20B.

[0092] <Steps S44 and S45> The temperature abnormality detection service 313 transmits an output device processing request to the communication unit 301 to request that an output device using the device schemas DSC and DSD execute a predetermined process as a service of the temperature abnormality detection service 313 provided in accordance with the converted data of the input device 20B. Then, the communication unit 301 transmits the output device processing request to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the output device processing request.

[0093] <Step S46> The communication unit 111 sends the received output device processing request to the plug-in PC.

[0094] <Step S47> In response to an output device processing request, the device communication unit 101c of the plug-in PC transmits control data for executing a specified function to the output device 20C that uses the device schema DSC of the linked device setting information stored in the linked device setting storage unit 103c.

[0095] <Step S48> The output device 20C executes a predetermined function in accordance with the control data received from the plug-in PC.

[0096] <Step S49> In response to an output device processing request, the device communication unit 101c of the plug-in PC transmits control data for executing a predetermined function to the output device 20D that uses the device schema DSD of the linked device setting information stored in the linked device setting storage unit 103c.

[0097] <Step S50> The output device 20D executes a predetermined function in accordance with the control data received from the plug-in PC.

[0098] (Flow of operations when a new IoT device becomes able to connect to a contracted service) 10-1 and 10-2 are sequence diagrams showing an example of the flow of operations when a new IoT device becomes able to link with a contracted service of the information processing system according to the embodiment. FIG. 11 is a diagram showing an example of a state when a new IoT device becomes able to link with a contracted service of the information processing system according to the embodiment. FIG. 12 is a diagram showing an example of the data configuration of device link information transmitted to the gateway when a new IoT device becomes able to link with a contracted service. With reference to FIGS. 10-1, 10-2, 11, and 12, the flow of operations when a new IoT device becomes able to link with a contracted service in the information processing system 1 according to the present embodiment will be described. Note that before the operations shown in FIGS. 10-1 and 10-2, the state is assumed to be the state at the time when the operations shown in FIGS. 7-1 and 7-2 described above are completed. Therefore, in the linked device setting information held by the linked device setting holding unit 103a, the enable flags for the device schemas DSA1 and DSB are set to ON, and the enable flag for the device schema DSA2 is set to OFF, and in the linked device setting information held by the linked device setting holding unit 103c, the enable flags for the device schemas DSC and DSD are set to ON.

[0099] <Steps S111 and S112> The processes in steps S111 and S112 are the same as the processes in steps S11 and S12 shown in FIGS. 7-1 and 7-2, respectively.

[0100] <Steps S113 to S115> In response to a request for device collaboration information, collaboration information processing unit 302 refers to device collaboration management DB 304, extracts device collaboration information corresponding to the user who responded to the request, and sends the device collaboration information to communication unit 301. Here, it is assumed that an input device using device schema DSA2 has newly become collaborable with food temperature management service 311 subscribed to by user "customer CA." As a result, the device collaboration information extracted by collaboration information processing unit 302 indicates, as shown in FIG. 12, that the collaborative services subscribed to by the user are food temperature management service 311 and temperature abnormality detection service 313, that the device schemas used in food temperature management service 311 are device schemas DSA1 and DSA2, and that the device schemas used in temperature abnormality detection service 313 are device schemas DSA1, DSB, DSC, and DSD.

[0101] <Step S116> The communication unit 301 transmits the device cooperation information to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the device cooperation information. Then, the cooperation information request unit 112 acquires the device cooperation information received by the communication unit 111.

[0102] <Steps S117 and S118> The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information stored in the collaborative device setting storage units 103a and 103c to identify the device schemas to be used by the plug-in PA and PC. Specifically, as a result of comparing the device collaboration information with the collaborative device setting information stored in the collaborative device setting storage units 103a and 103c, the identification unit 113 identifies device schemas DSA1, DSA2, and DSB as device schemas to be used by the plug-in PA, and device schemas DSC and DSD as device schemas to be used by the plug-in PC. The identification unit 113 then sends identification information indicating the identification results to the plug-in PA and PC. Note that the identification unit 113 may not send the identification information to the plug-in PC because the device collaboration information includes each device schema already used by the plug-in PC.

[0103] <Step S119> 12, the linked device setting storage unit 103a of the plug-in PA sets the enable flag of the device schema DSA2 newly identified by the identification unit 113 to ON in the linked device setting information, thereby enabling the device schema DSA2. That is, the linked device setting storage unit 103a sets the enable flag of the device schema DSA2 to ON in the linked device setting information stored in the linked device setting storage unit 103a in accordance with the identification information, thereby enabling the device schema DSA2.

[0104] <Steps S120 to S134> The processes in steps S120 to S134 are the same as the processes in steps S20 to S34 shown in FIGS. 7-1 and 7-2, respectively.

[0105] <Step S135> The input device 20A2 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0106] <Step S136> The data conversion unit 102a of the plug-in PA of the gateway 10 converts the detection data of the input device 20A2 received by the device communication unit 101a into the data structure of the device schema DSA2 of the linked device setting information stored in the linked device setting storage unit 103a.

[0107] <Step S137> Then, the data conversion unit 102a sends the converted detected data (converted data) to the gateway application GA.

[0108] <Step S138> The communication unit 111 of the gateway application GA transmits the converted data to the cloud system 30. Then, the communication unit 301 of the cloud system 30 receives the converted data.

[0109] <Steps S139 and S140> The communication unit 301 refers to the device cooperation management DB 304 and acquires information about the cooperation service 310 that uses the converted data.

[0110] <Step S141> Communication unit 301 transmits a service execution request for requesting execution of a service and the converted data to food temperature management service 311 indicated by the acquired information of linked service 310. In response, food temperature management service 311 executes the service according to the received converted data of input device 20A2.

[0111] <Steps S142 to S155> The processes in steps S142 to S155 are similar to the processes in steps S37 to S50 shown in FIGS. 7-1 and 7-2, respectively.

[0112] (Flow of operations when signing up for a new service) FIG. 13 is a sequence diagram showing an example of the flow of operations when a new service contract is made in the information processing system according to the embodiment. FIG. 14 is a diagram showing an example of a state when a new service contract is made in the information processing system according to the embodiment. FIG. 15 is a diagram showing an example of a data configuration of device linkage information transmitted to a gateway when a new service contract is made. With reference to FIGS. 13 to 15, the flow of operations when a new linkage service contract is made in the information processing system 1 according to the embodiment will be described. That is, before the operations shown in FIG. 13, it is assumed that a user who is "customer CA" has not subscribed to any linkage service. Therefore, it is assumed that in the linkage device setting information held by the linkage device setting holding unit 103a, the enable flags of the device schemata DSA1, DSA2, and DSB are each OFF, and in the linkage device setting information held by the linkage device setting holding unit 103c, the enable flags of the device schemata DSC and DSD are each OFF.

[0113] <Steps S211 and S212> The processes in steps S211 and S212 are similar to the processes in steps S11 and S12 shown in FIGS. 7-1 and 7-2, respectively.

[0114] <Steps S213 to S215> In response to a request for device linkage information, linkage information processing unit 302 refers to device linkage management DB 304, extracts device linkage information corresponding to the user corresponding to the request, and sends the device linkage information to communication unit 301. Here, it is assumed that a user who is "customer CA" has newly subscribed to food temperature control service 311, and that an input device using device schema DSA1 has become linkable. As a result, the device linkage information extracted by linkage information processing unit 302 indicates, as shown in FIG. 15, that the linked service subscribed to by the user is food temperature control service 311, and that the device schema used by food temperature control service 311 is device schema DSA1.

[0115] <Step S216> The communication unit 301 transmits the device cooperation information to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the device cooperation information. Then, the cooperation information request unit 112 acquires the device cooperation information received by the communication unit 111.

[0116] <Steps S217 and S218> The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c to identify the device schema to be used in the plug-in PA and the PC. Specifically, the identification unit 113 identifies device schema DSA1 as the device schema to be used in the plug-in PA as a result of comparing the device collaboration information with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c, and then sends identification information indicating the identification result to the plug-in PA.

[0117] <Step S219> 14, the linked device setting storage unit 103a of the plug-in PA sets the enable flag of the device schema DSA1 identified by the identification unit 113 to ON in the linked device setting information, thereby enabling the device schema DSA1. That is, the linked device setting storage unit 103a sets the enable flag of the device schema DSA1 to ON in the linked device setting information stored in the linked device setting storage unit 103a in accordance with the identification information, thereby enabling the device schema DSA1.

[0118] <Steps S220 to S225> The processes in steps S220 to S225 are the same as the processes in steps S20 to S25 shown in FIGS. 7-1 and 7-2, respectively.

[0119] <Step S226> Communication unit 301 transmits a service execution request for requesting execution of a service and the converted data to food temperature management service 311 indicated by the acquired information of linked service 310. In response, food temperature management service 311 executes the service according to the received converted data of input device 20A1.

[0120] <Step S227> The input device 20A2 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0121] <Step S228> The data conversion unit 102a of the plug-in PA of the gateway 10 discards the detection data of the input device 20A2 received by the device communication unit 101a because the device schema DSA2 of the linked device setting information stored in the linked device setting storage unit 103a is invalid.

[0122] <Step S229> The input device 20B transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0123] <Step S230> The data conversion unit 102a of the plug-in PA of the gateway 10 discards the detection data of the input device 20B received by the device communication unit 101a because the device schema DSB of the linked device setting information stored in the linked device setting storage unit 103a is invalid.

[0124] (Flow of operations when you sign up for additional services) FIG. 16 is a sequence diagram showing an example of the flow of operations when an additional service contract is made for the information processing system according to the embodiment. FIG. 17 is a diagram showing an example of a state when an additional service contract is made for the information processing system according to the embodiment. FIG. 18 is a diagram showing an example of a data configuration of device linkage information transmitted to the gateway when an additional service contract is made. With reference to FIGS. 16 to 18, the flow of operations when an additional linkage service contract is made in the information processing system 1 according to the present embodiment. Note that the state before the operations shown in FIG. 16 is the state when the operations shown in FIG. 13 described above are completed. Therefore, in the linked device setting information held by the linked device setting holding unit 103a, the enable flag for device schema DSA1 is ON, and the enable flags for device schemas DSA2 and DSB are OFF, respectively, and in the linked device setting information held by the linked device setting holding unit 103c, the enable flags for device schemas DSC and DSD are OFF, respectively.

[0125] <Steps S311 and S312> The processes in steps S311 and S312 are similar to the processes in steps S11 and S12 shown in FIGS. 7-1 and 7-2, respectively.

[0126] <Steps S313 to S315> In response to a request for device linkage information, linkage information processing unit 302 refers to device linkage management DB 304, extracts device linkage information corresponding to the user corresponding to the request, and sends the device linkage information to communication unit 301. Here, it is assumed that user "customer CA" has also subscribed to CO2 concentration measurement service 312, and that an input device using device schema DSA2 has become linkable. As a result, the device linkage information extracted by linkage information processing unit 302 indicates, as shown in FIG. 18, that the linked services subscribed to by the user are food temperature management service 311 and CO2 concentration measurement service 312, that the device schema used in food temperature management service 311 is device schema DSA1, and that the device schema used in CO2 concentration measurement service 312 is device schema DSA2.

[0127] <Step S316> The communication unit 301 transmits the device cooperation information to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the device cooperation information. Then, the cooperation information request unit 112 acquires the device cooperation information received by the communication unit 111.

[0128] <Steps S317 and S318> The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c to identify the device schemas to be used in the plug-in PA and the PC. Specifically, the identification unit 113 identifies device schemas DSA1 and DSA2 as device schemas to be used in the plug-in PA as a result of comparing the device collaboration information with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c, and then sends identification information indicating the identification result to the plug-in PA.

[0129] <Step S319> 17, the linked device setting storage unit 103a of the plug-in PA turns on the enable flag of the device schema DSA2 identified by the identification unit 113 in the linked device setting information, thereby enabling the device schema DSA2. That is, the linked device setting storage unit 103a turns on the enable flag of the device schema DSA2 in the linked device setting information stored in the linked device setting storage unit 103a, according to the identification information, thereby enabling the device schema DSA2.

[0130] <Steps S320 to S325> The processes in steps S320 to S325 are the same as the processes in steps S20 to S25 shown in FIGS. 7-1 and 7-2, respectively.

[0131] <Step S326> Communication unit 301 transmits a service execution request for requesting execution of a service and the converted data to food temperature management service 311 indicated by the acquired information of linked service 310. In response, food temperature management service 311 executes the service according to the received converted data of input device 20A1.

[0132] <Step S327> The input device 20A2 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0133] <Step S328> The data conversion unit 102a of the plug-in PA of the gateway 10 converts the detection data of the input device 20A2 received by the device communication unit 101a into the data structure of the device schema DSA2 of the linked device setting information stored in the linked device setting storage unit 103a.

[0134] <Step S329> Then, the data conversion unit 102a sends the converted detected data (converted data) to the gateway application GA.

[0135] <Step S330> The communication unit 111 of the gateway application GA transmits the converted data to the cloud system 30. Then, the communication unit 301 of the cloud system 30 receives the converted data.

[0136] <Steps S331 and S332> The communication unit 301 refers to the device cooperation management DB 304 and acquires information about the cooperation service 310 that uses the converted data.

[0137] <Step S333> The communication unit 301 transmits a service execution request for requesting execution of a service and the conversion data to the CO2 concentration measurement service 312 indicated by the acquired information of the linked service 310. As a result, the CO2 concentration measurement service 312 executes the service according to the received conversion data of the input device 20A2.

[0138] <Step S334> The input device 20B transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0139] <Step S335> The data conversion unit 102a of the plug-in PA of the gateway 10 discards the detection data of the input device 20B received by the device communication unit 101a because the device schema DSB of the linked device setting information stored in the linked device setting storage unit 103a is invalid.

[0140] (Operation flow when you subscribe to additional services compatible with input and output devices) 19-1 and 19-2 are sequence diagrams showing an example of the flow of operations when a contract is made for services corresponding to the input device and the output device of the information processing system according to the embodiment. FIG. 20 is a diagram showing an example of a state when a contract is made for services corresponding to the input device and the output device of the information processing system according to the embodiment. The flow of operations when a contract is made for linked services corresponding to the input device and the output device in the information processing system 1 according to the embodiment will be described with reference to FIGS. 19-1, 19-2, and 20. Note that the state before the operations shown in FIGS. 19-1 and 19-2 is the state at the end of the operations shown in FIG. 16. Therefore, in the linked device setting information held by the linked device setting holding unit 103a, the enable flags of the device schemas DSA1 and DSA2 are set to ON, the enable flag of the device schema DSB is set to OFF, and the enable flag of the device schemas DSC and DSD is set to OFF.

[0141] <Steps S411 and S412> The processes in steps S411 and S412 are similar to the processes in steps S11 and S12 shown in FIGS. 7-1 and 7-2, respectively.

[0142] <Steps S413 to S415> In response to a request for device linkage information, the linkage information processing unit 302 references the device linkage management DB 304, extracts device linkage information corresponding to the user corresponding to the request, and sends the device linkage information to the communication unit 301. Here, it is assumed that the user, "customer CA," has also subscribed to the temperature abnormality detection service 313, and that input devices using device schemas DSA1 and DSB have become linkable with the temperature abnormality detection service 313, and that output devices using device schemas DSC and DSD have become linkable with the temperature abnormality detection service 313. As a result, the device linkage information extracted by the linkage information processing unit 302 indicates, as shown in FIG. 6 above, that the linked services subscribed to by the user are the food temperature management service 311, the CO2 concentration measurement service 312, and the temperature abnormality detection service 313, that the device schema used by the food temperature management service 311 is device schema DSA1, that the device schema used by the CO2 concentration measurement service 312 is device schema DSA2, and that the device schemas used by the temperature abnormality detection service 313 are device schemas DSA1, DSB, DSC, and DSD.

[0143] <Step S416> The communication unit 301 transmits the device cooperation information to the gateway 10. Then, the communication unit 111 of the gateway application GA of the gateway 10 receives the device cooperation information. Then, the cooperation information request unit 112 acquires the device cooperation information received by the communication unit 111.

[0144] <Step S417> The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c to identify the device schemas to be used by the plug-in PA and PC. Specifically, as a result of comparing the device collaboration information with the collaborative device setting information held by the collaborative device setting holding units 103a and 103c, the identification unit 113 identifies device schemas DSA1, DSA2, and DSB as device schemas to be used by the plug-in PA, and device schemas DSC and DSD as device schemas to be used by the plug-in PC.

[0145] <Step S418> The identification unit 113 sends identification information indicating the identification result to the plug-in PA.

[0146] <Step S419> The linked device setting storage unit 103a of the plug-in PA turns on the enable flag of the device schema DSB identified by the identification unit 113 in the linked device setting information in accordance with the identification information, as shown in Fig. 20, to enable the device schema DSB. That is, the linked device setting storage unit 103a turns on the enable flag of the device schema DSB in the linked device setting information stored in the linked device setting storage unit 103a in accordance with the identification information, to enable the device schema DSB.

[0147] <Step S420> Furthermore, the identification unit 113 sends identification information indicating the identification result to the plug-in PC.

[0148] <Step S421> 20, the linked device setting storage unit 103c of the plug-in PA sets the enable flags of the device schemas DSC and DSD identified by the identification unit 113 to ON in the linked device setting information, thereby enabling the device schemas DSC and DSD. That is, the linked device setting storage unit 103a sets the enable flags of the device schemas DSC and DSD to ON in the linked device setting information stored in the linked device setting storage unit 103c in accordance with the identification information, thereby enabling the device schemas DSC and DSD.

[0149] <Steps S422 to S436> The processes in steps S422 to S436 are similar to the processes in steps S20 to S34 shown in FIGS. 7-1 and 7-2, respectively.

[0150] <Step S437> The input device 20A2 transmits the detected data (detection data) to the gateway 10. The device communication unit 101a of the plug-in PA of the gateway 10 receives the detection data.

[0151] <Step S438> The data conversion unit 102a of the plug-in PA of the gateway 10 converts the detection data of the input device 20A2 received by the device communication unit 101a into the data structure of the device schema DSA2 of the linked device setting information stored in the linked device setting storage unit 103a.

[0152] <Step S439> Then, the data conversion unit 102a sends the converted detected data (converted data) to the gateway application GA.

[0153] <Step S440> The communication unit 111 of the gateway application GA transmits the converted data to the cloud system 30. Then, the communication unit 301 of the cloud system 30 receives the converted data.

[0154] <Steps S441 and S442> The communication unit 301 refers to the device cooperation management DB 304 and acquires information about the cooperation service 310 that uses the converted data.

[0155] <Step S443> The communication unit 301 transmits a service execution request for requesting execution of a service and the conversion data to the CO2 concentration measurement service 312 indicated by the acquired information of the linked service 310. As a result, the CO2 concentration measurement service 312 executes the service according to the received conversion data of the input device 20A2.

[0156] <Steps S444 to S457> The processes in steps S444 to S457 are similar to the processes in steps S37 to S50 shown in FIGS. 7-1 and 7-2, respectively.

[0157] (When a new IoT device is added that requires a new device schema) FIG. 21 is a diagram illustrating an example of a state when a new IoT device is added to the information processing system according to the embodiment. FIG. 22 is a diagram illustrating an example of a state when a new plug-in is developed in the information processing system according to the embodiment. FIG. 23 is a diagram illustrating an example of a state when a plug-in is updated in the information processing system according to the embodiment. FIG. 24 is a diagram illustrating an example of a state when a new device schema is enabled in the information processing system according to the embodiment. A case where a new IoT device requiring a new device schema is added to the information processing system 1 according to the embodiment will be described with reference to FIGS. 21 to 24. It is assumed that a contractor user has contracted with the food temperature management service 311 and the CO2 concentration measurement service 312. Therefore, in the coordinated device setting information held by the coordinated device setting holding unit 103a, the enable flags of the device schemas DSA1 and DSA2 are set to ON, the enable flag of the device schema DSB is set to OFF, and the enable flag of the device schemas DSC and DSD is set to OFF.

[0158] As shown in FIG. 21 , assume that an input device 20X is installed in a user's living space or office, requiring data conversion using a device schema that is not included in the linked device setting information stored in the linked device setting storage unit 103a of the plug-in PA and the linked device setting storage unit 103c of the plug-in PC. In this case, the existing plug-in PA and PC installed in the gateway 10 cannot convert data detected by the input device 20X into a specific device schema. In this case, in order to provide a service using the data detected by the input device 20X, a developer of the linked service provider 310 must develop a plug-in PA2 that can convert data detected by the input device 20X into an appropriate device schema DSX, as shown in FIG. 22 . Once the plug-in PA2 is developed, information about the device schema DSX for converting the data detected by the input device 20X is added to the device schema information in the device schema information DB 305, as shown in FIG. 22 . The plug-in PA2 is then set (registered) in the cloud system 30 so that it can be provided as an update plug-in.

[0159] As described above, the update confirmation unit 114 of the gateway application GA of the gateway 10 requests the cloud system 30 via the communication unit 111 to confirm whether or not the plug-ins installed in the gateway 10 (the plug-ins PA and PC in the example shown in FIG. 23 ) need to be updated at predetermined intervals (for example, once a day). The update management unit 303 of the cloud system 30 confirms whether or not the plug-in for the gateway 10 needs to be updated in response to the request from the gateway 10 to confirm whether or not the plug-in needs to be updated. The update management unit 303 then confirms that the existing plug-in PA installed in the gateway 10 needs to be updated by the plug-in PA2 that can be converted into the device schema DSX. Next, the update management unit 303 transmits the plug-in PA2, which is the plug-in for update, to the gateway 10 via the communication unit 301. The update unit 115 of the gateway application GA of the gateway 10 then updates the plug-in PA installed in the gateway 10 by the plug-in PA2 for update received from the cloud system 30 in response to the request from the update confirmation unit 114, as shown in FIG. 23 . The gateway 10 includes a device communication unit 101a-2, a data conversion unit 102a-2, and a linked device settings storage unit 103a-2 as functional units realized by the CPU 501 executing the plug-in PA2. The functions of the device communication unit 101a-2 and the data conversion unit 102a-2 are similar to those of the device communication unit 101a and the data conversion unit 102a described above. The linked device setting information stored in the linked device settings storage unit 103a-2 includes information on device schemas DSA1, DSA2, DSB, and DSX, and associates an enable flag corresponding to each device schema. Of these, the device schema DSX is a device schema used for data conversion of data detected by the input device 20X, as described above.However, since the gateway 10 has been updated with a new plug-in PA2 and the activation flags for the device schemas DSA1, DSA2, DSB, and DSX are all OFF in the linked device setting information held by the linked device setting holding unit 103a-2, in this state the data conversion unit 102a-2 cannot convert the data detected by the input device 20X into the device schema DSX.

[0160] 23, the provider of the collaboration service 310 starts providing a service on the food temperature management service 311 using data obtained by converting detection data from the input device 20X or the like into device schema DSX. The collaboration information request unit 112 of the gateway application GA of the gateway 10 requests device collaboration information, which is a list of services subscribed to by the user and the device schemas used in the services, from the cloud system 30 via the communication unit 111 at predetermined intervals (e.g., 12 hours). In response to the request for device collaboration information from the gateway 10, the collaboration information processing unit 302 of the cloud system 30 references the device collaboration management DB 304, extracts device collaboration information corresponding to the user corresponding to the request, and transmits the device collaboration information to the gateway 10 via the communication unit 301. In this case, the device collaboration information indicates that the collaboration services 310 subscribed to by the user are the food temperature management service 311 and the CO2 concentration measurement service 312, that the device schemas used in the food temperature management service 311 are device schemas DSA1 and DSX, and that the device schema used in the CO2 concentration measurement service 312 is device schema DSA2. Then, the cooperation information request unit 112 acquires the device cooperation information via the communication unit 111.

[0161] The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information stored in the collaborative device setting storage units 103a-2 and 103c to identify the device schemas to be used by the plug-in PA2 and the PC. Specifically, the identification unit 113 identifies the device schemas DSA1, DSA2, and DSX as the device schemas to be used by the plug-in PA2 as a result of comparing the device collaboration information with the collaborative device setting information stored in the collaborative device setting storage units 103a-2 and 103c, and sends identification information indicating the identification result to the plug-in PA2. Then, the collaborative device setting storage unit 103a-2 of the plug-in PA turns on the enable flags of the device schemas DSA1, DSA2, and DSX identified by the identification unit 113 in the collaborative device setting information in accordance with the identification information, as shown in FIG. 24, thereby enabling the device schemas DSA1, DSA2, and DSX. As a result, the detection data of the input device 20X is converted into the device schema DSX by the plug-in PA2 and transmitted to the cloud system 30, and the food temperature management service 311 provides a service according to the converted data of the input device 20X.

[0162] Although the above-described FIGS. 21 to 24 show examples in which an input device is added, the same applies to the case in which an output device is added.

[0163] As described above, in the gateway 10 according to this embodiment, the linked device setting storage unit 103c (103a, 103a-2) stores linked device setting information that associates a device schema for converting data received from the IoT device 20 with an activation flag that indicates whether data conversion using the device schema is enabled. The link information request unit 112 requests device link information indicating the service to which the user has subscribed and the device schema to be used in the service from the cloud system 30 that provides the service. The identification unit 113 identifies the device schema to be used in the service based on the device link information received from the cloud system 30 in response to the request by the link information request unit 112 and the linked device setting information stored in the linked device setting storage unit 103c (103a, 103a-2). The linked device setting storage unit 103c (103a, 103a-2) activates the activation flag corresponding to the device schema identified by the identification unit 113 and deactivates the activation flag corresponding to the device schema that has not been identified. In this way, because the device linkage information can identify the device schema used by the plug-in, if you have not subscribed to the service or after suspending or canceling the service, you can disable the enable flag for the device schema used by the service to prevent data collection and storage from IoT devices corresponding to that device schema. Also, because you can switch the device schema used for plug-in data conversion by disabling or enabling the enable flag, there is no need to update the plug-in itself, saving the user effort.

[0164] (Variation) The information processing system 1 according to this modification will be described, focusing on the differences from the information processing system 1 according to the above-described embodiment. In the above-described embodiment, when a service using a new device schema is provided, an operation of updating an existing plug-in with a plug-in corresponding to the new device schema will be described. In this modification, an operation of updating an existing device schema with a new device schema will be described. Note that the hardware configuration and functional block configuration of the gateway 10 and cloud system 30 of the information processing system 1 according to this modification are the same as the configurations described in the above-described embodiment.

[0165] FIG. 25 is a diagram illustrating a state in which the structure of an existing device schema is changed in an information processing system according to a modified example. FIG. 26 is a diagram illustrating an operation of updating a device schema in an information processing system according to a modified example. The operation of updating an existing device schema with a new device schema in the information processing system 1 according to this modified example will be described with reference to FIGS. 25 and 26. It is assumed that the contractor user has a contract with the food temperature management service 311. Therefore, in the coordinated device setting information held by the coordinated device setting holding unit 103a, the enable flag of device schema DSA1 is ON, and the enable flags of device schemas DSA2 and DSB are OFF.

[0166] Assume that the developer on the cloud system 30 side has redefined device schema DSA1 by simplifying the data structure of device schema DSA1 used in the provision of services by food temperature control service 311, as shown in Fig. 25. In this case, as a new data schema is defined, information on device schema DSA1a for converting data detected by input device 20A1 is added to the device schema information in device schema information DB 305, as shown in Fig. 26. Then, the information on the redefined device schema DSA1 is set (registered) in the cloud system 30 so that it can be provided.

[0167] The update confirmation unit 114 of the gateway application GA of the gateway 10 requests the cloud system 30, via the communication unit 111, at predetermined intervals (e.g., once a day) to confirm whether or not a device schema used by the plug-ins (plug-ins PA and PC in the example shown in FIG. 26 ) installed in the gateway 10 needs to be updated. In response to the request from the gateway 10 to confirm whether or not a device schema needs to be updated, the update management unit 303 of the cloud system 30 confirms whether or not a device schema for the gateway 10 needs to be updated. The update management unit 303 then confirms that the device schema DSA1 of the existing plug-in PA installed in the gateway 10 needs to be updated. Next, the update management unit 303 transmits information about the device schema DSA1a for update to the gateway 10 via the communication unit 301. The update unit 115 of the gateway application GA of the gateway 10 then updates the information about the device schema DSA1 of the linked device setting information stored in the linked device setting storage unit 103a of the plug-in PA, using the information about the device schema DSA1a for update received from the cloud system 30 in response to the request from the update confirmation unit 114, as shown in FIG. 26 . As a result, the linked device setting information held by the linked device setting holding unit 103a includes information on the device schemas DSA1a, DSA2, and DSB as device schema information, and associates an activation flag corresponding to each device schema. As a result, the device schema DSA1a is used for data conversion of data detected by the input device 20A1. However, since the gateway 10 has updated the device schema DSA1a and the activation flag for the device schema DSA1a is OFF in the linked device setting information held by the linked device setting holding unit 103a, in this state the data conversion unit 102a cannot convert the data detected by the input device 20A1 into the device schema DSA1a.

[0168] The provider of the linked service 310 then begins providing a service on the food temperature management service 311 using data obtained by converting detection data from the input device 20A1 or the like into device schema DSA1a. The link information request unit 112 of the gateway app GA of the gateway 10 requests device link information, which is a list of services subscribed to by the user and device schemas used in the services, from the cloud system 30 via the communication unit 111 at predetermined intervals (e.g., 12 hours). In response to the request for device link information from the gateway 10, the link information processing unit 302 of the cloud system 30 references the device link management DB 304, extracts device link information corresponding to the user corresponding to the request, and transmits the device link information to the gateway 10 via the communication unit 301. In this case, the device link information indicates that the linked service 310 subscribed to by the user is the food temperature management service 311 and that the device schema used in the food temperature management service 311 is the device schema DSA1a. The link information request unit 112 then acquires the device link information via the communication unit 111.

[0169] The identification unit 113 of the gateway application GA of the gateway 10 compares the device collaboration information acquired by the collaboration information request unit 112 with the collaborative device setting information stored in the collaborative device setting storage units 103a and 103c to identify the device schema to be used in the plug-in PA and the PC. Specifically, the identification unit 113 identifies the device schema DSA1a as the device schema to be used in the plug-in PA as a result of comparing the device collaboration information with the collaborative device setting information stored in the collaborative device setting storage units 103a and 103c, and sends identification information indicating the identification result to the plug-in PA. Then, the collaborative device setting storage unit 103a of the plug-in PA sets the enable flag of the device schema DSA1a identified by the identification unit 113 to ON in the collaborative device setting information in accordance with the identification information, as shown in FIG. 26, to enable the device schema DSA1a. As a result, the detection data of the input device 20A1 is converted into device schema DSA1a by the plug-in PA and transmitted to the cloud system 30, and the food temperature control service 311 provides a service according to the converted data of the input device 20A1.

[0170] As described above, in the information processing system 1 according to this modification, it is only necessary to update the device schema held by the existing plug-in, and therefore there is no need to update by a plug-in for using a new device schema, as in the information processing system 1 according to the above-described embodiment. 25 and 26 show that the information of the existing device schema DSA1 in the plug-in PA is updated with the information of the redefined new device schema DSA1a, but this is not limiting, and it is also possible to add the information of the new device schema to the linked device setting information in the linked device setting holding unit 103a.

[0171] In the above-described embodiments and modifications, when at least one of the functional units of the gateway 10 and the cloud system 30 is realized by executing a program, the program is provided by being pre-installed in a ROM or the like. In the above-described embodiments and modifications, the programs executed by the gateway 10 and the cloud system 30 may be provided by being recorded in an installable or executable file format on a computer-readable recording medium such as a CD-ROM (Compact Disc Read Only Memory), a flexible disk (FD), a CD-R (Compact Disk-Recordable), or a DVD (Digital Versatile Disc). In the above-described embodiments and modifications, the programs executed by the gateway 10 and the cloud system 30 may be provided by being stored on a computer connected to a network such as the Internet and downloaded via the network. In the above-described embodiments and modifications, the programs executed by the gateway 10 and the cloud system 30 may be provided or distributed via a network such as the Internet. Furthermore, in the above-described embodiments and variations, the programs executed by the gateway 10 and the cloud system 30 are modularly structured to include at least one of the above-described functional units, and in terms of actual hardware, the CPUs 501 and 601 read and execute the programs from the above-described storage devices (e.g., storage 503, auxiliary storage device 605, etc.), thereby loading and generating the above-described functional units onto the main storage device.

[0172] The aspects of the present invention are as follows. <1> A gateway device having a plug-in installed therein for data communication with one or more IoT devices, a setting storage unit that stores setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether data conversion based on the device schema is enabled; a request unit that requests collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system in response to a request by the request unit; the setting information stored in the setting storage unit; an identification unit that identifies a device schema to be used in the service based on the Equipped with The setting holding unit is a gateway device that enables the enable flag corresponding to the device schema identified by the identifying unit and disables the enable flag corresponding to the device schema that is not identified. <2> The plug-in is receiving data detected by the IoT device; referring to the setting information, if the validation flag of the device schema corresponding to the IoT device indicates valid, converting the data using the device schema, and if the validation flag indicates invalid, discarding the data; transmitting the converted data to the cloud system; <1> 2. The gateway device according to claim 1 . <3> when the user subscribes to a new service provided by the cloud system, the request unit acquires, by a request to the cloud system, the collaboration information including information on the new service and a device schema used in the new service; the identification unit compares the link information with the setting information to identify a device schema to be used in the new service; the setting holding unit enables the enable flag corresponding to the device schema identified by the identifying unit. <1> or <2> 2. The gateway device according to claim 1 . <4> when the user cancels a contracted service provided by the cloud system, the request unit acquires, by a request to the cloud system, the collaboration information that does not include information on the canceled service and device schema used in the service; the identification unit compares the link information with the setting information, and does not identify a device schema to be used in the canceled service; the setting holding unit invalidates the enable flag corresponding to the device schema that is not identified by the identifying unit. <1> or <2> 2. The gateway device according to claim 1 . <5> when a new device schema to be used in a contracted service provided by the cloud system is defined, the request unit acquires the collaboration information including information on the service and the new device schema to be used in the service by requesting the cloud system; the identifying unit compares the link information with the setting information to identify the new device schema; the setting holding unit enables the enable flag corresponding to the new device schema identified by the identifying unit. <1> or <2> 2. The gateway device according to claim 1 . <6> a confirmation unit in the cloud system that requests the cloud system to confirm whether or not a new plug-in that uses a new device schema is registered in correspondence with the plug-in installed in the gateway device, and the cloud system confirms whether or not the plug-in in the gateway device needs to be updated; an update unit that receives the new plug-in from the cloud system in response to the confirmation by the confirmation unit, and updates the plug-in installed in the gateway device with the new plug-in; The said further comprising <1> or <2> 2. The gateway device according to claim 1 . <7> a confirmation unit that requests the cloud system to confirm whether a device schema used in the service under contract by the user needs to be newly registered or redefined, and whether the device schema needs to be added or updated in the plug-in of the gateway device; an update unit that receives new device schema information from the cloud system in response to the confirmation by the confirmation unit, and adds the new device schema information to the setting information or updates the device schema of the setting information with the new device schema information; The said further comprising <1> or <2> 2. The gateway device according to claim 1 . <8> An information processing system including a gateway device in which a plug-in for data communication with one or more IoT devices is installed, and a cloud system that provides a service, The gateway device a setting storage unit that stores setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether data conversion based on the device schema is enabled; a request unit that requests, from the cloud system, link information indicating the service to which the user has subscribed and a device schema used in the service; The collaboration information received from the cloud system in response to a request by the request unit; the setting information stored in the setting storage unit; an identification unit that identifies a device schema to be used in the service based on the Equipped with The setting holding unit is an information processing system that enables the enable flag corresponding to the device schema identified by the identifying unit and disables the enable flag corresponding to the device schema that has not been identified. <9> An information processing method for a gateway device in which a plug-in for data communication with one or more IoT devices is installed, comprising: a setting holding step of holding setting information that associates a device schema for converting data received from an IoT device with an enable flag indicating whether or not data conversion based on the device schema is enabled; a request step of requesting collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system upon request; The setting information to be held; identifying a device schema to be used with the service based on the and the setting maintaining step includes a step of enabling the enable flag corresponding to the device schema identified in the identifying step and disabling the enable flag corresponding to the device schema that has not been identified; The information processing method has the following features. <10> A computer with a plug-in installed to communicate with one or more IoT devices. a setting holding step of holding setting information that associates a device schema for converting data received from an IoT device with an enable flag indicating whether or not data conversion based on the device schema is enabled; a request step of requesting collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system upon request; The setting information to be held; identifying a device schema to be used with the service based on the Execute The setting and maintaining step is a program for enabling the enable flag corresponding to the device schema identified in the identifying step and disabling the enable flag corresponding to the device schema that has not been identified. [Explanation of symbols]

[0173] 1. Information Processing Systems 10 Gateway 20, 20-1 to 20-3 IoT devices 20A1, 20A2, 20B input devices 20C, 20D output device 20X Input Devices 30 Cloud System 101a, 101a-2, 101c Device communication section 102a, 102a-2, 102c Data conversion unit 103a, 103a-2, 103c linked device setting storage unit 111 Communications Department 112 Linkage information request unit 113 Specific section 114 Update Verification Section 115 Update Department 301 Communications Department 302 Collaboration Information Processing Unit 303 Update Management Department 304 Device Linkage Management DB 305 Device Schema Information DB 310 Collaborative Services 311 Food Temperature Control Service 312 CO2 concentration measurement service 313 Temperature Abnormality Detection Service 501 CPU 502 RAM 503 Storage 510 Bus 511 Telecommunications circuit 512 Near field communication circuit 601 CPU 602 ROM 603 RAM 605 Auxiliary storage 606 Recording Media 607 Media Drive 608 Display 609 Network I / F 610 Bus 611 keyboard 612 Mouse 613 DVD 614 DVD drive DSA1, DSA1a, DSA2, DSB, DSC, DSD, DSX device schemas GA Gateway App PA, PA2, and PC Plug-ins N Network [Prior art documents] [Patent documents]

[0174] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-243478

Claims

1. A gateway device having a plug-in installed therein for data communication with one or more IoT devices, a setting storage unit that stores setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether data conversion based on the device schema is enabled; a request unit that requests collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system in response to a request by the request unit; the setting information stored in the setting storage unit; an identification unit that identifies a device schema to be used in the service based on the Equipped with The setting holding unit enables the enable flag corresponding to the device schema identified by the identifying unit, and disables the enable flag corresponding to the device schema not identified.

2. The plug-in is receiving data detected by the IoT device; By referring to the setting information, if the validation flag of the device schema corresponding to the IoT device indicates valid, convert the data using the device schema, and if the validation flag indicates invalid, discard the data; The gateway device according to claim 1 , wherein the converted data is transmitted to the cloud system.

3. when the user subscribes to a new service provided by the cloud system, the request unit acquires, by a request to the cloud system, the collaboration information including information on the new service and a device schema used in the new service; the identification unit compares the link information with the setting information to identify a device schema to be used in the new service; 3. The gateway device according to claim 1, wherein the setting holding unit enables the enable flag corresponding to the device schema identified by the identifying unit.

4. when the user cancels a contracted service provided by the cloud system, the request unit acquires, by a request to the cloud system, the collaboration information that does not include information on the canceled service and device schema used in the service; the identification unit compares the link information with the setting information, and does not identify a device schema to be used in the canceled service; 3. The gateway device according to claim 1, wherein the setting holding unit invalidates the validation flag corresponding to the device schema that is not identified by the identifying unit.

5. when a new device schema to be used in a contracted service provided by the cloud system is defined, the request unit acquires the collaboration information including information on the service and the new device schema to be used in the service by requesting the cloud system; the identifying unit compares the link information with the setting information to identify the new device schema; 3. The gateway device according to claim 1, wherein the setting holding unit enables the enable flag corresponding to the new device schema identified by the identifying unit.

6. a confirmation unit in the cloud system that requests the cloud system to confirm whether or not a new plug-in that uses a new device schema is registered in correspondence with the plug-in installed in the gateway device, and the cloud system confirms whether or not the plug-in in the gateway device needs to be updated; an update unit that receives the new plug-in from the cloud system in response to the confirmation by the confirmation unit, and updates the plug-in installed in the gateway device with the new plug-in; The gateway device according to claim 1 or 2, further comprising:

7. a confirmation unit that requests the cloud system to confirm whether a device schema used in the service under contract by the user needs to be newly registered or redefined, and whether the device schema needs to be added or updated in the plug-in of the gateway device; an update unit that receives new device schema information from the cloud system in response to the confirmation by the confirmation unit, and adds the new device schema information to the setting information or updates the device schema of the setting information with the new device schema information; The gateway device according to claim 1 or 2, further comprising:

8. An information processing system including a gateway device in which a plug-in for data communication with one or more IoT devices is installed, and a cloud system that provides a service, The gateway device a setting storage unit that stores setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether data conversion based on the device schema is enabled; a request unit that requests, from the cloud system, link information indicating the service to which the user has subscribed and a device schema used in the service; The collaboration information received from the cloud system in response to a request by the request unit; the setting information stored in the setting storage unit; an identification unit that identifies a device schema to be used in the service based on the Equipped with The setting holding unit enables the enable flag corresponding to the device schema identified by the identifying unit, and disables the enable flag corresponding to the device schema that is not identified.

9. An information processing method for a gateway device in which a plug-in for data communication with one or more IoT devices is installed, comprising: a setting holding step of holding setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether the data conversion according to the device schema is enabled; a request step of requesting collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system upon request; The setting information to be held; identifying a device schema to be used with the service based on the and The setting maintaining step enables the enable flag corresponding to the device schema identified in the identifying step, and disables the enable flag corresponding to the device schema that has not been identified.

10. A computer on which a plug-in for data communication with one or more IoT devices is installed, a setting holding step of holding setting information that associates a device schema for converting data received from an IoT device with an enable flag that indicates whether the data conversion according to the device schema is enabled; a request step of requesting collaboration information indicating a service subscribed to by a user and a device schema used in the service from a cloud system that provides the service; The collaboration information received from the cloud system upon request; The setting information to be held; identifying a device schema to be used with the service based on the Execute The setting maintaining step is a program for enabling the enable flag corresponding to the device schema identified in the identifying step and disabling the enable flag corresponding to the device schema that is not identified.

Images