Server, communication system and communication method

Abstract

In a communication device that communicates with a server based on connection information and firmware for connecting to the server, in order to be able to properly communicate with various other servers, the communication device communicates with the first server based on first connection information and first firmware for connecting to the first server, and obtains second firmware for connecting to a second server different from the first server from the first server.

Description

Technical Field

[0001] The invention relates to a server, a communication system and a communication method. Background Art

[0002] There is a gateway device (hereinafter referred to as a "communication device") that collects data from electronic devices and transmits the collected data to an IoT (Internet of Things) server that provides various services such as monitoring of the electronic devices via a communication network.

[0003] Furthermore, there is known a technology in which such a communication device transmits first identification information to a server in order to be able to connect to an appropriate connection target and acquires information of a second connection target corresponding to the first identification information (for example, see Patent Document 1).

[0004] Patent Document 1: Japanese Patent No. 6813110 Summary of the invention

[0005] <Problems to be Solved by the Invention>

[0006] Since the communication device shown in Patent Document 1 operates based on firmware that is premised on connection with the company's server (cloud service, etc.), it is difficult to connect to other companies' servers when forming an alliance with a partner company, etc. For example, as shown in Patent Document 1, only the information of the second connection target is obtained, and sometimes it is impossible to properly communicate with other communication systems that are operated by various partner companies and continue to develop every day.

[0007] The present invention enables appropriate communication with other various servers in a communication device that communicates with a server based on connection information and firmware for connecting to the server.

[0008] <Methods used to solve the problem>

[0009] The communication device of the first aspect of the present invention communicates with a first server based on first connection information and first firmware for connecting to the first server, and acquires second firmware for connecting to a second server different from the first server from the first server.

[0010] According to the first aspect of the present invention, in a communication device that communicates with a server based on connection information and firmware for connecting to the server, it is possible to appropriately communicate with various other servers.

[0011] A second aspect of the present invention is the communication device according to the first aspect, wherein the communication device acquires second connection information for connecting to the second server from the first server, and the second connection information includes authentication information for connecting to the second server.

[0012] A third aspect of the present invention is the communication device according to the second aspect, wherein the communication device communicates with the second server based on the second connection information and the second firmware.

[0013] The fourth aspect of the present invention is a communication device according to any one of the first to third aspects, wherein, when the second server to which the communication device is connected is changed, the communication device communicates with the first server based on instructions from the outside and again obtains firmware for connecting to a second server different from the second server.

[0014] A fifth aspect of the present invention is the communication device according to any one of the first to fourth aspects, wherein the first connection information and the first firmware are set when the communication device is manufactured.

[0015] The server of the sixth aspect of the present invention is a first server, wherein the first server accepts selection of a service or a second server used by a communication device, receives first connection information including device identification information that identifies the communication device from the communication device, and sends second firmware to the communication device for connecting to a second server that provides a service used by the communication device.

[0016] According to the second aspect of the present invention, the server can appropriately provide the communication device with the second firmware for connecting to the connected second server.

[0017] The seventh aspect of the present invention is a server according to the sixth aspect, wherein the first server stores second connection information and the second firmware for connecting to the second server, and sends the second connection information and the second firmware for connecting to the second server providing a service used by the communication device to the communication device.

[0018] An eighth aspect of the present invention is a server according to the seventh aspect, wherein the second connection information includes authentication information for connecting to the second server, and the first server generates the authentication information for connecting to the second server.

[0019] The ninth aspect of the present invention is a server according to any one of aspects 6 to 8, wherein the first server stores information of the connected second server according to device identification information of each device that identifies the communication device, and determines the second server to which the communication device is connected based on the device identification information.

[0020] The tenth aspect of the present invention is a server according to any one of aspects 6 to 8, wherein the first server stores the services used by the communication device according to the device identification information of each device that identifies the communication device, and determines the second server to which the communication device is connected based on the service.

[0021] The communication system of the eleventh aspect of the present invention is a communication system including a first server and a communication device, wherein the first server accepts a selection of a service to be used by the communication device, receives first connection information including device identification information for identifying the communication device from the communication device, sends second firmware for connecting to a second server providing a service used by the communication device to the communication device, and the communication device communicates with the first server based on the first connection information and the first firmware for connecting to the first server, and obtains the second firmware for connecting to a second server different from the first server from the first server.

[0022] The communication method of the twelfth aspect of the present invention is a communication method in a communication system including a first server and a communication device, wherein the first server accepts a selection of a service used by the communication device, the communication device communicates with the first server based on first connection information and first firmware for connecting to the first server, the first server receives the first connection information containing device identification information for identifying the communication device from the communication device, the first server sends to the communication device second firmware for connecting to a second server that provides a service used by the communication device, and the communication device obtains from the first server the second firmware for connecting to a second server different from the first server. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a diagram showing an example of a system configuration of a communication system according to an embodiment.

[0024] Figure 2 This is a diagram showing an example of the hardware configuration of a computer according to one embodiment.

[0025] Figure 3 This is a diagram showing an example of a functional configuration of a communication system according to an embodiment.

[0026] Figure 4A FIG. 1 is a diagram showing an example of device information managed by a device management DB according to an embodiment.

[0027] Figure 4B FIG. 2 is a diagram showing an example of device information managed by a device management DB according to an embodiment.

[0028] Figure 4C FIG. 3 is a diagram showing an example of device information managed by a device management DB according to an embodiment.

[0029] Figure 4D FIG. 4 is a diagram showing an example of device information managed by a device management DB according to one embodiment.

[0030] Figure 4E FIG. 5 is a diagram showing an example of device information managed by a device management DB according to one embodiment.

[0031] Figure 4F FIG. 6 is a diagram showing an example of device information managed by a device management DB according to an embodiment.

[0032] Figure 5 This is a sequence diagram showing an example of processing during manufacturing of the communication device according to the first embodiment.

[0033] Figure 6 This is a sequence diagram (1) showing an example of processing during installation of the communication device according to the first embodiment.

[0034] Fig. 7A FIG. 1 is a diagram showing an example of a setting screen according to the first embodiment.

[0035] Figure 7B FIG. 2 is a diagram showing an example of a setting screen according to the first embodiment.

[0036] Figure 8 This is a sequence diagram (2) showing an example of the process at the time of installation of the communication device according to the first embodiment.

[0037] Fig. 9 This is a sequence diagram showing an example of processing at the time of data collection in the first embodiment.

[0038] Fig.10 This is a sequence diagram (1) showing an example of connection destination change processing according to the first embodiment.

[0039] Fig.11 This is a sequence diagram (2) showing an example of the connection destination change process according to the first embodiment.

[0040] Fig.12 This is a sequence diagram (3) showing an example of the connection destination change process according to the first embodiment.

[0041] Fig.13 This is a sequence diagram (1) showing an example of processing when the first embodiment is abolished.

[0042] Fig.14 This is a sequence diagram (2) showing an example of processing when the first embodiment is abolished.

[0043] Fig.15 This is a sequence diagram showing an example of processing at the time of installation of the communication device according to the second embodiment.

[0044] Fig.16 This is a sequence diagram showing an example of processing at the time of data collection in the second embodiment. DETAILED DESCRIPTION

[0045] Hereinafter, each embodiment will be described with reference to the drawings. Note that in this specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals to omit repeated description.

[0046] <System Structure>

[0047] Figure 1 1 is a diagram showing an example of a system structure of a communication system according to an embodiment. The communication system 1 includes a management server 10 connected to a communication network N, one or more IoT (Internet of Things) servers 20A, 20B, ..., a terminal device 30, and a communication device 100. Note that in the following description, when referring to any IoT server among one or more IoT servers 20A, 20B, ..., "IoT server 20" is used. In addition, Figure 1 The number of IoT servers 20 shown in FIG. 1 is an example and other numbers are also possible.

[0048] The communication network N is, for example, the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network), etc. The communication network N may include, for example, communication sections based on wireless communication such as a wireless LAN or a wireless WAN.

[0049] The communication device 100 is, for example, connected to a plurality of devices 101A, 101B, 101C, ... in a communication manner, collects data acquired by the plurality of devices 101A, 101B, 101C, ..., and sends it to the edge (gateway device) of the IoT server 20. Note that in the following description, "device 101" is used to represent any device among the plurality of devices 101A, 101B, 101C, .... The communication device 100 may have a function of sending an instructed command to the device 101 according to an instruction from the IoT server 20. The device 101 is a device that acquires specified data and sends it to the communication device 100, such as an air conditioner, various sensors, etc.

[0050] The communication device 100 of this embodiment pre-stores connection information (hereinafter referred to as "first connection information") and firmware (hereinafter referred to as "first firmware") for connecting to the management server 10. In addition, when the communication device 100 is powered on for the first time, for example, it uses the first connection information and the first firmware to connect to the management server 10, and obtains connection information (hereinafter referred to as "second connection information") and firmware (hereinafter referred to as "second firmware") for connecting to the IoT server 20 as the connection target.

[0051] Here, the second connection information includes, for example, the URL (Uniform Resource Locator) of the IoT server as the connection target, authentication information for authenticating the communication device 100, etc. The firmware is a program (software) embedded in the communication device 100 to control the communication device 100. In the second firmware, for example, a communication protocol, an authentication method, a data format, and setting information for communicating with the IoT server 20 as the connection target are embedded.

[0052] The management server (first server) 10 is, for example, an information processing device having a computer structure, or a system including a plurality of computers. The management server 10, for example, causes the terminal device 30 to display a selection screen for selecting a connection target of the communication device 100, and accepts the selection of a service or IoT server (second server) 20 used by the communication device 100. In addition, when the communication device 100 is connected to the management server 100, the management server 10 receives device identification information (hereinafter referred to as "communication device ID") for identifying the communication device 100 from the communication device 100, and determines the IoT server selected on the selection screen as the connection target of the communication device 100. In addition, the management server 10 sends the second connection information and the second firmware for connecting to the IoT server 20 as the connection target of the communication device 100 to the communication device 100. Note that part or all of the second connection information may also be included in the second firmware.

[0053] The terminal device 30 is, for example, an information terminal such as a PC (Personal Computer), a tablet terminal, or a smartphone. The terminal device 30 includes various terminal devices such as a terminal device used by an operator of a production line that manufactures the communication device 100, a terminal device used by an administrator who manages the communication device 100, or a terminal device used by a construction worker who installs the communication device 100.

[0054] The IoT server (second server) 20 is, for example, an information processing device having a computer structure, or a system including a plurality of computers. The IoT server 20 receives IoT data sent by the communication device 100, processes the data, and provides various services such as remote monitoring and fault diagnosis.

[0055] According to the above structure, the communication device 100 of the present embodiment can acquire not only the second connection information of the IoT server 20 as the connection target but also the second firmware for connecting to the IoT server 20 as the connection target from the management server 10. Therefore, the communication device 100 of the present embodiment can appropriately communicate with other communication systems that are operated by various partner companies and are increasingly developed.

[0056] According to the present embodiment, in the communication device 100 that communicates with the server based on the connection information and firmware for connecting to the server, it is possible to appropriately communicate with other communication systems.

[0057] <Hardware Structure>

[0058] The communication device 100, the management server 10, the IoT server 20, and the terminal device 30 of this embodiment have, for example, Figure 2 The hardware configuration of the computer 200 shown in FIG.

[0059] Figure 2 The computer 200 includes, for example, a CPU (Central Processing Unit) 201, a memory 202, a storage device 203, a communication I / F (Interface) 204, an output device 205, an input device 206, and a bus 207.

[0060] The CPU 201 is a processor that realizes various functions by executing a predetermined program stored in a recording medium such as the storage device 203 or the memory 202. The memory 202 includes, for example, a volatile memory RAM (Random Access Memory) used as a work area of ​​the CPU 201, and a non-volatile memory ROM (Read Only Memory) that stores a startup program of the computer 200. The storage device 203 is a large-capacity storage device that stores programs such as an OS (Operating System) and application programs, and various data and information, and is realized by, for example, an SSD (Solid State Drive) or an HDD (Hard Disk Drive).

[0061] The communication I / F 204 includes one or more communication interfaces, such as LAN, WAN (Wide Area Network), etc., to connect the computer 200 to the communication network N and communicate with other devices. The output device 205 includes a display device that displays various display screens, or a sound output device that outputs sound messages, error sounds, etc. The input device 206 is, for example, an input device that receives input such as a touch panel, a keyboard, or a pointing device. Note that the output device 205 and the input device 206 can also be display input devices such as touch panel displays. The bus 207 is connected to the above-mentioned components and transmits, for example, address signals, data signals, and various control signals.

[0062] (Hardware structure of the device)

[0063] In this embodiment, since the hardware structure of the device 101 can be any structure, the description is omitted here.

[0064] <Functional Structure>

[0065] Figure 3 This is a diagram showing an example of a functional configuration of a communication system according to an embodiment.

[0066] (Functional Structure of Communication Device)

[0067] The communication device 100 includes, for example, a communication control unit 301 , an acquisition unit 302 , a device management unit 303 , a storage unit 304 , and the like.

[0068] The communication control unit 301 is implemented by the first firmware (hereinafter referred to as "first FW") 305 or the second firmware (hereinafter referred to as "second FW") 307, etc., which is executed by the CPU 201 of the communication device 100. For example, when the CPU 201 executes the first FW 305, the communication control unit 301 uses the first connection information to communicate with the management server (first server) 10. On the other hand, when the CPU 201 executes the second FW 307, the communication control unit 301 uses the second connection information to communicate with the IoT server (second server) 20 of the connection target.

[0069] The acquisition unit 302 is implemented by a program (first FW 305) executed by the CPU 201, and acquires the second FW 307 for connecting to the IoT server 20 as a connection target, the second connection information 308, etc. from the management server 10. Note that the second connection information 308 may also be included in the second FW 307. In this case, the acquisition unit 302 only needs to acquire the second FW 307 from the management server 10.

[0070] The device management section 303 is realized by a program (second FW 307 ) executed by the CPU 201 , and transmits IoT data collected from a plurality of devices 101 to the IoT server 20 of the connection target via the communication control section 301 .

[0071] The storage section 304 is realized by, for example, the storage device 203 or the like included in the communication apparatus 100, and pre-stores the first FW 305 and the first connection information 306. Furthermore, the storage section 304 stores the second FW 307, the second connection information 308, and the like acquired by the acquisition section 302.

[0072] (Functional structure of management server)

[0073] The management server (first server) 10 implements the sending / receiving unit 311, the receiving unit 312, the first generating unit 313, the device information management unit 314, the device management DB 315, and the FW providing units 316A, 316B, etc. by executing a predetermined program in the computer 200 provided in the management server 10. Note that at least a part of each of the above functional structures can also be implemented by hardware.

[0074] The transmission / reception unit 311 connects the management server 10 to the communication network N using the communication I / F 204 provided in the management server 10 , and executes a transmission process of transmitting data to other devices and a reception process of receiving data from other devices.

[0075] The receiving unit 312 provides a network UI (User Interface) such as a setting screen for setting a connection destination of the communication device 100 to the terminal device 30, and receives setting operations, input operations, or selection operations on the display screen. In addition, the receiving unit 312 provides a network API (Application Programming Interface) for utilizing functions provided by the management server 10 from the IoT server 20, the terminal device 30, or the communication device 100, and receives request information from each device.

[0076] The first generation unit 313 generates the first connection information 306 for connecting the communication device 100 to the management server 10, for example, based on a request for issuing the first connection information from the dedicated terminal device 30 provided on the production line for manufacturing the communication device 100. The first connection information 306 generated by the first generation unit 313 includes the URL information of the management server 10, the authentication information for connecting to the management server 10, and the like.

[0077] The device information management unit 314 stores and manages, for example, Figure 4A to Figure 4E The device information 400a to 400e of the communication device 100 are shown. Note that in the following description, "device information 400" is used when indicating any of the device information 400a to 400e.

[0078] exist FIG. 4A to FIG. 4D In the example of , the device information 400 includes information such as “communication device ID”, “IoT server”, “edge ID”, and “status” as items. “Communication device ID” is identification information for identifying the hardware of the communication device 100. “IoT server” is information such as identification information or a name that identifies an IoT server that is a connection target to which the communication device 100 is connected. “Edge ID” is identification information that identifies the communication device 100 that serves as an edge in a service provided by the “IoT server”. “Status” is information indicating the status of the communication device 100.

[0079] In addition, if Figure 4E As shown, the device information 400 may also include an item of "service" instead of "Iot server". "Service" is information indicating the service provided by the IoT server 20. In this case, Figure 4F As shown, the device information management unit 314 can specify the identification information or name of the IoT server 20 providing the “service” by pre-storing the correspondence information 401 indicating the correspondence relationship between the “service” and the “IoT server” in the device management DB 315 or the like.

[0080] The device management DB 315 is a storage device for example. FIG. 4A to FIG. 4E The device management DB 315 is a database of device information 400 shown in FIG. In the device management DB 315, information of the IoT server 20 as the connection target is stored according to each communication device ID that identifies the communication device 100. Note that a part of the device management DB 315 may also be undertaken by the device management DB 324 that the IoT servers 20A, 20B, ... have. For example, Figure 4A to Figure 4E The device information 400d among the device information 400a to 400e shown may be managed by the device management DB 315 of the management server or the device management DB 324 of the IoT server 20. The device management DBs 315 and 324 may be implemented by another computer 200 different from the management server 10 and the IoT server 20.

[0081] The FW providing units 316A, 316B, ... perform processing for providing the second FW 307 and the second connection information 308 for connecting to the IoT servers 20A, 20B, ... For example, the FW providing unit 316A performs processing for providing the second FW 307, the second connection information 308, etc. to the communication device 100 for connecting to the IoT server 20A. Similarly, the FW providing unit 316B performs processing for providing the second FW 307, the second connection information 308, etc. to the communication device 100 for connecting to the IoT server 20B. Note that in the following description, "FW providing unit 316" is used to represent any of the FW providing units 316A, 316B, ... In addition, in Figure 3 In the figure, it is assumed that the FW providing section 316B, ... has the same functional structure as the FW providing section 316A.

[0082] The FW providing unit 316 includes, for example, a FW managing unit 317 , a second generating unit 318 , a storage unit 319 , and the like.

[0083] The FW management unit 317 stores and manages the second FW 307 for connecting to the IoT server 20 corresponding to the FW providing unit 316 in the storage unit 319 or the like. For example, the FW management unit 317 of the FW providing unit 316A stores and manages the second FW 307 for connecting to the IoT server 20A in the storage unit 319 or the like.

[0084] The second generation unit 318 generates the second connection information 308 for connecting to the IoT server 20 corresponding to the FW providing unit 316. For example, the second generation unit 318 of the FW providing unit 316A generates the second connection information 308 for connecting to the IoT server 20A. Note that the FW providing unit 316 may also entrust the IoT server 20 to generate the second connection information 308. For example, the FW providing unit 316A may not have the second generation unit 318 but entrust the IoT server 20A to generate the second connection information 308. At this time, the FW providing unit 316 acts as a bridge with the IoT server 20. As an example, the second connection information 308 includes the URL of the IoT server 20 as the connection target, the edge ID for identifying the communication device 100 as the edge in the service provided by the IoT server 20 as the connection target, the device certificate (an example of authentication information), and the like.

[0085] The storage unit 319 stores, for example, the second FW 307 managed by the FW management unit 317 and the second connection information 308 generated by the second generation unit 318 .

[0086] (IoT server functional structure)

[0087] The IoT server (second server) 20 implements the transceiver 321, the device information management unit 322, the service provider 323, and the device management DB 324 by executing a predetermined program on the computer 200 of the IoT server 20. Note that at least a part of the above-mentioned functional structures may also be implemented by hardware.

[0088] The transmission / reception unit 321 connects the IoT server 20 to the communication network N using the communication I / F 204 provided in the IoT server 20 , and performs transmission processing of transmitting data to other devices and reception processing of receiving data from other devices.

[0089] The device information management unit 322 stores and manages the status of the communication device 100 connected to the IoT server 20 in the device management DB 324 or the like. Note that the device information management unit 322 may store and manage the status of the communication device 100 connected to the IoT server in the device management DB 324 provided to the management server 10. For example, the device information management unit 322 may register the status of the communication device 100 in the device management DB 315 using the network API provided by the acceptance unit 312, or may notify the status of the communication device 100 to the device information management unit 314 of the management server 10. The device management DB 324 stores information indicating the status of the communication device 100 connected to the IoT server 20, for example Figure 4D Device information 400d is shown.

[0090] The service providing unit 323 provides services provided by the IoT server 20 , such as a remote monitoring service, a fault diagnosis service, and the like.

[0091] <Processing Flow>

[0092] Next, the processing flow of the communication method according to this embodiment will be described.

[0093] [First embodiment]

[0094] (Processing during manufacture of communication device)

[0095] Figure 5 3 is a sequence diagram showing an example of processing during manufacture of the communication device of the first embodiment. This process shows an example of processing for storing the first FW 305, the first connection information 306, etc. in the communication device 100 in a production line for manufacturing the communication device 100. Note that it is assumed that Figure 5 At the start time of the illustrated process, the terminal device 30 has logged into the management server 10 .

[0096] In step S501 , when the production line operator performs the initial setting operation of the communication device 100 on the dedicated terminal device 30 installed on the production line, the communication system 1 executes the processing of step S502 and thereafter.

[0097] In step S502 , the terminal device 30 transmits a first connection information issuance request to the management server 10 for requesting issuance of the first connection information 306 .

[0098] In step S503, when the accepting unit 312 of the management server 10 accepts the request to issue the first connection information, the first generating unit 313 generates the first connection information for the communication device 100 to connect to the management server 10. The first connection information includes a URL for connecting to the management server 10, authentication information, etc. Preferably, the first generating unit 313 generates authentication information unique to each communication device 100.

[0099] In step S504, the device information management section 314 of the management server 10 updates the device management DB 315. For example, Figure 4A As shown, the device information management unit 314 updates the item "status" of the device information 400a of the communication device 100 to "initial state". Here, the communication device ID of the communication device 100 may be issued by the terminal device 30 or by the management server 10. In the case where the communication device ID is issued by the terminal device 30, in step S502, the terminal device 30 sends a request for issuing the first connection information including the communication device ID of the communication device 100 to the management server 10.

[0100] In step S505 , the transmission / reception section 311 of the management server 10 transmits the first connection information 306 generated by the first generation section 313 to the terminal device 30 as the request source.

[0101] In step S506 , the terminal device 30 writes the first connection information 306 and the first FW 305 received from the management server 10 into the communication device 100 .

[0102] In step S507, the first connection information 306 and the first FW 305 are stored in the storage unit 304 of the communication device 100. The communication device 100 is shipped from a factory in this state (initial state), for example.

[0103] (Processing 1 when installing a communication device)

[0104] Figure 6 is a sequence diagram (1) showing an example of the process when the communication device of the first embodiment is installed. Figure 5 The present invention is an example of a process for installing the communication device 100 storing the first FW 305 and the first connection information 306 in the storage unit 304 at a predetermined location and setting the communication device 100 to be connectable to the IoT server 20.

[0105] In step S601, an administrator such as a system administrator who manages the communication system 1 or a shipping administrator who manages the shipping of the communication device 100 (hereinafter referred to as "administrator, etc.") performs a display operation of a setting screen on the terminal device 30. Here, the terminal device 30 is any information terminal that has logged into the management server 10, and can use a web browser or an application (hereinafter referred to as "APP") corresponding to the communication system 1 to display a display screen (web page) provided by the management server 10. Note that Figure 6 The terminal device 30 may be Figure 5 The terminal device 30 is different from the terminal device 30.

[0106] In step S602 , when the terminal device 30 receives the display operation of the setting screen by the administrator or the like, it transmits a display request of the setting screen to the management server 10 .

[0107] In steps S603 and S604, when the receiving unit 312 of the management server 10 receives the request to display the setting screen, for example, the terminal device 30 displays the following Fig. 7A The setting screen 700A shown or Figure 7B The setting screen 700B is shown.

[0108] Fig. 7A FIG. 2 shows an example of a connection destination setting screen displayed on the terminal device 30. Fig. 7AOn the setting screen 700A shown in FIG. 1 , a plurality of selection buttons 701 are displayed so as to selectively display the IoT servers 20A, 20B, ..., which are candidates for the connection target of the communication device 100. When the communication device 100 is connected to the IoT server 20A, the administrator selects the selection button 701A for selecting the "IoT server 20A" from the plurality of selection buttons 701.

[0109] Figure 7B Another example of a connection destination selection screen displayed by the terminal device 30 is shown. Figure 7B In the setting screen 700B shown in FIG. 1 , a plurality of selection buttons 702 are displayed for selectively displaying services (e.g., remote monitoring service, fault diagnosis service, etc.) that can be used by the communication device 100. The receiving unit 312 of the management server 10 may use, for example, Figure 4F The corresponding information 401 showing the corresponding relationship between the IoT servers 20 and the services provided by each IoT server 20 is displayed on the terminal device 30 as shown in FIG. Figure 7B The setting screen 700B is shown.

[0110] Here, return to Figure 6 , continue the description of the sequence diagram. In step S605, the administrator or the like, for example, Fig. 7A , Figure 7B Here, as an example, it is assumed that the administrator or the like selects the connection target from the following setting screen. Fig. 7A The following description is given by selecting a selection button 701A for selecting “IoT server 20A” on the setting screen 700A shown.

[0111] In step S606 , when the terminal device 30 receives the selection operation of the connection target by the administrator or the like, it transmits a setting request including information of the selected connection target (IoT server 20A) and the communication device ID identifying the communication device 100 to the management server 10 .

[0112] In step S607, when the receiving unit 312 of the management server 10 accepts the setting request, the second generation unit 318 of the FW providing unit 316A corresponding to the connection target (IoT server 20A) included in the setting request generates the second connection information 308. For example, the second generation unit 318 generates the second connection information 308 including the URL of the IoT server 20A, the edge ID identifying the communication device 100 as the edge at the IoT server 20A, the device certificate (electronic certificate) of the communication device 100, and the like. Note that the device certificate of the communication device 100 is an example of authentication information, and other authentication information may also be used. In addition, the second generation unit 318 stores the generated second connection information 308 in the storage unit 319, etc., in association with the communication device ID of the communication device 100.

[0113] In step S608, the device information management unit 314 of the management server 10 updates the device management DB 315. For example, Figure 6 The start time of the processing is stored in the device management DB 315 as follows: Figure 4A The device information management unit 314 updates the information such as "IoT server", "edge ID", and "status" of the device information 400a to the following: Figure 4B Device information 400b is shown.

[0114] exist Figure 4B In the device information 400b shown, the item "IoT server" stores information of the IoT server 20A as the connection target, and the item "edge ID" stores the edge ID generated by the second generation unit 318. In addition, the device information management unit 314 updates the item "status" of the device information 400b to "second connection information issued".

[0115] In step S609 , the transmission / reception section 311 of the management server 10 transmits a completion notification indicating that the setting is completed to the terminal device 30 that is the request source.

[0116] After executing the processes of steps S601 to S609 , when a construction worker or the like installs the communication device 100 at an arbitrary timing and turns on the power of the communication device 100 (step S611 ), the communication system 1 executes the processes of step S612 and thereafter.

[0117] In step S612, the communication device 100 is started up by the first FW 305 pre-stored in the storage unit 304. Furthermore, in step S613, the communication control unit 301 of the communication device 100 connects to the management server 10 using the first connection information 306 pre-stored in the storage unit 304. At this time, the communication control unit 301 of the communication device 100 transmits a communication device ID for identifying the communication device 100 to the management server 10.

[0118] In step S614, the device information management unit 314 of the management server 10 updates the device management DB 315. For example, the device information management unit 314 updates the device management DB 315. Figure 4B The item "status" of the device information 400b shown in FIG. 1 is changed to "second connection information notification completed" and updated as shown in FIG. Figure 4C Device information 400c is shown.

[0119] In step S615 , the FW providing section 316A of the management server 10 transmits the second connection information 308 corresponding to the communication device ID of the communication device 100 and the second FW 307 for connecting to the IoT server 20A stored in the storage section 319 to the communication device 100 .

[0120] Note that, as described above, in the device management DB 315, information on the IoT server 20 as a connection target is stored for each communication device ID that identifies the communication device 100. Therefore, the management server 10 can determine the IoT server 20A connected to the communication device 100 and the FW providing unit 316A corresponding to the IoT server 20A based on the communication device ID.

[0121] In step S616 , the acquisition unit 302 of the communication device 100 stores the second FW 307 and the second connection information 308 received from the management server 10 in the storage unit 304 .

[0122] In step S617 , the communication device 100 is restarted by using the second FW 307 stored in the storage unit 304 .

[0123] pass Figure 6 By the processing, the communication device 100 uses the second connection information 308 and the second FW 307 acquired from the management server 10 to connect to the IoT server 20A as the connection target set in the setting screen 700A, etc., and can communicate appropriately.

[0124] (Processing 2 when installing a communication device)

[0125] Figure 8 is a sequence diagram (2) showing an example of the process when the communication device of the first embodiment is installed. Figure 5 Another example of a process for installing the communication device 100 storing the first FW 305 and the first connection information 306 in the storage unit 304 at a predetermined location and setting it to be connectable to the IoT server 20.

[0126] Notice, Figure 8 Step S611 and subsequent processing and use Figure 6 The processing of the communication device installation described in the previous embodiment is the same, so the description is omitted here. In addition, the basic processing contents of the processing of steps S801 to S809 are also the same as those of the previous embodiment. Figure 6 The processing of steps S601 to S609 is the same, so the detailed description of the same processing content is omitted here.

[0127] In step S801 , a construction worker or the like who installs the communication device 100 performs a display operation on the terminal device 30 to display a setting screen.

[0128] In step S802 , when the terminal device 30 receives a display operation of a setting screen by a construction worker or the like, it transmits a display request of the setting screen to the management server 10 .

[0129] In steps S803 and S804, when the receiving unit 312 of the management server 10 receives the request to display the setting screen, for example, the terminal device 30 displays the following Fig. 7A The setting screen 700A shown or Figure 7B The setting screen 700B is shown.

[0130] In step S805, construction personnel, for example, Fig. 7A In the setting screen 700A shown, a selection button 701A for selecting “IoT server 20A” is selected.

[0131] In step S806 , when the terminal device 30 receives the selection operation of the connection target by the construction worker or the like, it transmits a setting request including information of the selected connection target (IoT server 20A) and the communication device ID of the communication device 100 to the management server 10 .

[0132] In step S807 , when the accepting unit 312 of the management server 10 accepts the setting request, the second generating unit 318 of the FW providing unit 316A corresponding to the connection destination (IoT server 20A) included in the setting request generates the second connection information 308 .

[0133] In step S808 , the device information management section 314 of the management server 10 updates the device management DB 315 .

[0134] In step S809 , the transmission / reception section 311 of the management server 10 transmits a completion notification indicating that the setting is completed to the terminal device 30 that is the request source.

[0135] In this way, it can be expected Figure 8 The processing of steps S801 to S809 can be performed by a construction worker or the like even in the absence of an administrator or the like.

[0136] (Processing when collecting data)

[0137] Fig. 9 is a sequence diagram showing an example of the process of collecting data in the first embodiment. Figure 6 , Figure 8 This is an example of the processing performed after the second FW 307 is restarted in step S617.

[0138] In step S901 , when the communication device 100 is restarted through the second FW 307 , it connects to the IoT server 20A as a connection target using the second connection information 308 .

[0139] In step S902, the device information management unit 322 of the IoT server 20A performs authentication processing of the communication device 100 based on the second connection information 308 received from the communication device 100. For example, the device information management unit 322 verifies whether the authentication information (e.g., device certificate) included in the second connection information is legitimate authentication information. Here, since the communication device 100 has the legitimate second connection information 308 issued by the management server 10, the device information management unit 322 permits the connection based on the communication device 100.

[0140] In step S903, the device information management unit 322 of the IoT server 20A updates the device management DB 324. For example, Figure 4D As shown, the device information management unit 322 updates the item "status" of the device information 400d of the communication device 100 stored in the device management DB 324 to "second connection information connection completed". Note that, as described above, the device information management unit 322 may also update the device information 400 stored in the device management DB 315 of the management server 10 using a network API or the like provided by the receiving unit 312 of the management server 10.

[0141] Through the above-described processing, the communication device 100 can be communicatively connected to the IoT server 20A, and can execute the data collection processing shown in steps S911 and S912, for example.

[0142] In step S911 , the device management unit 303 of the communication apparatus 100 collects data transmitted from the plurality of devices 101A, 101B, 101C, . . . .

[0143] In step S912, the device management unit 303 of the communication device 100 sends the collected data as IoT data to the IoT server 20A at a specified timing. At this time, the type of data collected by the device management unit 303, the timing of sending IoT data, and the format of IoT data are all programmed into the second FW 307. Therefore, the communication device 100 can properly communicate with the IoT server 20A as the connection target.

[0144] In this way, the communication device 100 of the present embodiment acquires the second FW 307 in addition to the second connection information 308 according to the IoT server 20 as the connection target, and restarts the communication device 100 using the acquired second FW 307. Therefore, even when the IoT server 20 as the connection target is changed to another IoT server (for example, the IoT server 20B), the communication device 100 can appropriately communicate with the other IoT server.

[0145] (Connection destination change process 1)

[0146] Fig.10 1 is a sequence diagram showing an example of a connection target change process of the first embodiment. This process shows an example of a process in which the communication device 100 communicates with the management server 10 based on an instruction from the outside such as the management server 10 or the IoT server 20A to acquire the second FW 307 for connecting to another IoT server 20B again.

[0147] Note that in the following description, the second connection information 308 for connecting to the IoT server 20A is set as "second connection information A", and the second connection information 308 for connecting to the IoT server 20B is set as "second connection information B" for distinction. In addition, the second FW 307 for connecting to the IoT server 20A is set as "second FWA", and the second FW 307 for connecting to the IoT server 20B is set as "second FWB" for distinction.

[0148] In addition, Fig.10 At the start time of the process shown, the terminal device 30, for example, Figure 8 The same sequence as steps S802 to S804 is performed, and a screen for changing the connection destination of the communication device 100 is displayed.

[0149] In step S1001 , an administrator or the like performs a change operation on a change screen displayed on the terminal device 30 to change the connection destination of the communication device 100 to the connection destination of the IoT server 20B.

[0150] In step S1002 , when the terminal device 30 receives the connection destination change operation by the administrator or the like, it transmits a connection destination change request including information of the changed connection destination IoT server 20B and the communication device ID of the communication device 100 to the management server 10 .

[0151] In step S1003, when the accepting unit 312 of the management server 10 accepts the change request, the second generation unit 318 of the FW providing unit 316B corresponding to the connection target (IoT server 20B) included in the change request generates the second connection information B. For example, the second generation unit 318 generates the second connection information B, which includes the URL of the IoT server 20B, the edge ID for identifying the communication device 100 as the edge in the IoT server 20B, the device certificate of the communication device 100, and the like. In addition, the second generation unit 318 associates the generated second connection information B with the communication device ID of the communication device 100, and stores it in the storage unit 319 of the FW providing unit 316B, etc. Note that, as described above, the FW providing unit 316B may also entrust the IoT server 20B to create the second connection information B. In this case, the FW providing unit 316B associates the second connection information B generated by the IoT server 20B with the communication device ID of the communication device 100, and stores it in the storage unit 319 of the FW providing unit 316B, etc.

[0152] In step S1004, the device information management section 314 of the management server 10 updates the device management DB 315. For example, the device information stored in the device management DB 315 is updated. Figure 4D In the device information 400d shown, the item "IoT server" is updated to "IoT server 20B", and the item "edge ID" is updated to the edge ID included in the second connection information B. In addition, the device information management unit 314 updates the item "status" to "second connection information issued".

[0153] In step S1005 , the FW providing unit 316A corresponding to the IoT server 20A of the management server 10 invalidates the second connection information A for the communication device 100 .

[0154] In step S1006 , the FW providing unit 316A may add, in the “status” item of the device information of the communication device 100 , that the second connection information A is invalid.

[0155] In step S1007 , the FW providing unit 316B of the management server 10 instructs the communication device 100 to acquire the second connection information B and the second FWB.

[0156] In step S1008 , the device management unit 303 of the communication device 100 stops transmitting IoT data to the IoT server 20A.

[0157] In step S1009 , the acquisition unit 302 of the communication device 100 requests the management server 10 to acquire the second connection information B and the second FWB.

[0158] In step S1010 , the device information management unit 314 of the management server 10 updates the “status” item of the device information of the communication device 100 stored in the device management DB 315 to “notification of the second connection information B completed”.

[0159] In step S1011 , the FW providing section 316B of the management server 10 transmits the second connection information B corresponding to the communication device ID of the communication device 100 and stored in the storage section 319 to the communication device 100 and the second FWB for connecting to the IoT server 20B.

[0160] In step S1012 , the acquisition unit 302 of the communication device 100 overwrites the second FWB and the second connection information B received from the management server 10 in the storage unit 304 .

[0161] In step S1013 , the communication device 100 restarts using the second FWB stored in the storage unit 304 .

[0162] In step S1014 , when starting up again through the second FWB, the communication device 100 uses the second connection information B to connect to the IoT server 20B as the connection target.

[0163] In step S1015, the device information management unit 322 of the IoT server 20B performs authentication processing of the communication device 100 based on the second connection information B received from the communication device 100. Here, since the communication device 100 has the legitimate second connection information B issued by the management server 10, the device information management unit 322 permits the connection based on the communication device 100.

[0164] In step S1016 , the device information management unit 322 of the IoT server 20B updates the “status” item of the device information of the communication device 100 stored in the device management DB 315 to “second connection information B connected”.

[0165] Through the above-described processing, the communication device 100 can be connected to the IoT server 20B for communication and can execute various processing.

[0166] (Connection destination change process 2)

[0167] Fig.11 2 is a sequence diagram showing an example of a connection target change process of the first embodiment. This process shows another example of a process in which the communication device 100 communicates with the management server 10 based on an instruction from the outside such as the management server 10 or the IoT server 20A to reacquire the second FW 307 for connecting to another IoT server 20B.

[0168] Note that due to Fig.11 The processing of steps S1001, S1002 and S1008 to S1016 in the process shown in FIG. Fig.10 The processing of steps S1001, S1002, S1008 to S1016 is the same as that of Fig.10 The differences in processing.

[0169] In step S1101, the management server 10 executes the following Fig.10 The issuance process of the second connection information B shown in steps S1003 to S1006.

[0170] In step S1102 , the FW providing unit 316B of the management server 10 requests the IoT server 20A to which the communication device 100 is connected to instruct the communication device 100 to acquire the second connection information B and the second FWB.

[0171] In step S1103 , the transmission / reception section 321 of the IoT server 20A instructs the communication device 100 to acquire the second connection information B and the second FWB.

[0172] In this way, the FW providing unit 316B of the management server 10 may also instruct the communication device 100 to acquire the second connection information B and the second FWB by using the IoT server 20A to which the communication device 100 is connected.

[0173] (Connection destination change process 3)

[0174] Fig.12 This is a sequence diagram (3) showing an example of the connection target change process of the first embodiment. This process shows another example of the process when the administrator or the like changes the IoT server 20 as the connection target to which the installed communication device 100 is connected. Fig.11 The processing of steps S1001, S1002, S1014, and S1015 in the process shown in FIG. Fig.10 The processing of steps S1001, S1002, S1014, and S1015 is the same as that of steps S1001, S1002, S1014, and S1015, so Fig.10The following description will focus on the differences in processing.

[0175] In step S1201, the management server 10 executes the following Fig.10 The issuance process of the second connection information B shown in steps S1003 to S1006.

[0176] In step S1202 , the FW providing unit 316B of the management server 10 requests the IoT server 20A to which the communication device 100 is connected to instruct the communication device 100 to perform initialization.

[0177] In step S1203 , the transmission / reception unit 321 of the IoT server 20A instructs the communication device 100 to perform initialization.

[0178] In step S1204 , the communication device 100 initializes the communication device 100 . For example, the communication device 100 deletes the second FWA and the second connection information A stored in the storage unit 304 , and starts up again through the first FW 305 .

[0179] In step S1205, the communication device 100 and the management server 10 execute, for example, Figure 6 The second connection information acquisition process shown in steps S613 to S617 is restarted by the second FWB.

[0180] (Processing 1 when abolished)

[0181] Fig.13 is a sequence diagram (1) showing an example of the process when the first embodiment is abolished. This process shows an example of the process when the communication device 100 that has been installed is abolished. Note that Fig.13 At the start time of the process shown, the terminal device 30, for example, Figure 8 The setting screen for accepting the cancellation operation of the communication device 100 is displayed in the same sequence as steps S802 to S804.

[0182] In step S1301 , the administrator or the like performs a deactivation operation of the communication device 100 on the setting screen displayed on the terminal device 30 .

[0183] In step S1302 , upon receiving a deactivation operation of the communication device 100 by an administrator or the like, the terminal device 30 transmits a communication device deactivation request including the communication device ID of the communication device 100 to be deactivated to the management server 10 .

[0184] In step S1303 , when the accepting unit 312 of the management server 10 accepts the cancellation request of the communication device 100 , the device information management unit 314 of the management server 10 invalidates the second connection information 308 corresponding to the communication device 100 .

[0185] In step S1304 , the device information management section 314 of the management server 10 sets the “status” item of the device information of the communication device 100 stored in the device management DB 315 to “second connection information invalid” (or “revoked”).

[0186] In step S1305 , the device information management unit 314 of the management server 10 transmits a deactivation instruction to the communication device 100 .

[0187] In step S1306 , the device management unit 303 of the communication device 100 stops sending IoT data.

[0188] In step S1307 , the communication device 100 deletes the second FW 307 and the second connection information 308 stored in the storage unit 304 .

[0189] Through the above-described process, an administrator or the like can execute the deactivation process of the communication device 100 by remote operation.

[0190] (2)

[0191] Fig.14 is a sequence diagram (2) showing an example of the process when the first embodiment is abolished. This process shows another example of the process when the communication device 100 that has been installed is abolished. Note that Fig.14 At the start time of the process shown, the terminal device 30, for example, Figure 8 The setting screen for accepting the cancellation operation of the communication device 100 is displayed in the same sequence as steps S802 to S804.

[0192] In step S1401 , a construction worker or the like performs a deactivation operation of the communication device 100 on the setting screen displayed on the terminal device 30 .

[0193] In step S1402 , when the terminal device 30 receives the deactivation operation of the communication device 100 by the construction worker or the like, it transmits a communication device deactivation request including the communication device ID of the deactivated communication device 100 to the management server 10 .

[0194] In step S1403 , when the accepting unit 312 of the management server 10 accepts the cancellation request of the communication device 100 , the device information management unit 314 of the management server 10 invalidates the second connection information 308 corresponding to the communication device 100 .

[0195] In step S1404 , the device information management section 314 of the management server 10 sets the “status” item of the device information of the communication device 100 stored in the device management DB 315 to “second connection information invalid” (or “revoked”).

[0196] In step S1405 , the construction worker or the like performs a deletion operation on the communication device 100 to delete the second connection information 308 and the second FW 307 .

[0197] In step S1406 , the communication device 100 deletes the second FW 307 and the second connection information 308 stored in the storage unit 304 .

[0198] In this way, it is expected that the decommissioning process of the communication device 100 can be performed by a construction worker or the like even at a location where the communication device 100 is installed.

[0199] [Second embodiment]

[0200] In the first embodiment, an example is described in which the number of IoT servers 20 to which the communication device 100 transmits IoT data is one, but the number of IoT servers to which the communication device 100 transmits IoT data may be plural.

[0201] In the second embodiment, an example of processing when the communication device 100 sends IoT data to two IoT servers 20 is described. Note that the system structure, hardware structure, and functional structure of the communication system 1 according to the second embodiment may be the same as those of the first embodiment.

[0202] (Processing when installing a communication device)

[0203] Fig.15 is a sequence diagram showing an example of processing during installation of the communication device according to the second embodiment. Figure 5 The communication device 100 storing the first FW 305 and the first connection information 306 in the storage unit 304 is installed in a predetermined location and set to be connectable to the IoT server 20A and the IoT server 20B.

[0204] In step S1500, the communication system 1 executes Figure 6 The display processing of the setting screen described in steps S601 to S604 of the embodiment, for example, causes the terminal device 30 to display the following Fig. 7A The setting screen 700A is shown.

[0205] In step S1501, an administrator or the like, for example, Fig. 7A The setting screen 700A shown is used to select a connection destination. Here, for example, an administrator or the like selects a selection button 701A for selecting "IoT server 20A" and a selection button 701B for selecting "IoT server 20B" from the setting screen 700A, and the following description is performed.

[0206] In step S1502 , when the terminal device 30 accepts a selection operation of a connection target based on an administrator or the like, it sends a setting request including information of the selected connection target (IoT server 20A and IoT server 20B) and a communication device ID identifying the communication device 100 to the management server 10 .

[0207] In step S1503, when the receiving unit 312 of the management server 10 accepts the setting request, the second generation unit 318 of the FW providing unit 316A corresponding to the IoT server 20A generates the second connection information according to the setting request. For example, the second generation unit 318 of the FW providing unit 316A generates the second connection information, which includes the URL of the IoT server 20A, the edge ID that identifies the communication device 100 as the edge in the IoT server 20A, the authentication information of the communication device 100, etc. In addition, the second generation unit 318 of the FW providing unit 316A associates the generated second connection information with the communication device ID of the communication device 100 and stores it in the storage unit 319, etc.

[0208] In step S1504, the device information management section 314 of the management server 10 updates the device management DB 315. For example, the device information management section 314 updates the device management DB 315. Figure 4A The device information 400a of the communication device 100 shown stores information of the IoT server 20A in the item “IoT server”, stores the generated edge ID in the item “edge ID”, and stores “second connection information issued” indicating the status in the item “status”.

[0209] In step S1505, the second generation unit 318 of the FW providing unit 316B corresponding to the IoT server 20B generates the third connection information based on the setting information. For example, the second generation unit 318 of the FW providing unit 316B generates the third connection information, which includes the URL of the IoT server 20B, the edge ID that identifies the communication device 100 as the edge in the IoT server 20B, the authentication information of the communication device 100, etc. In addition, the second generation unit 318 of the FW providing unit 316B associates the generated third connection information with the communication device ID of the communication device 100 and stores it in the storage unit 319, etc.

[0210] In step S1506, the device information management section 314 of the management server 10 updates the device management DB 315. For example, the device information management section 314 updates Figure 4BThe device information 400a of the communication device 100 shown in FIG. 4 shows the "IoT server", "edge ID" and "status" items. Specifically, the device information management unit 314 adds information of the IoT server 20B as the connection target to the item "IoT server", adds the edge ID generated by the second generation unit 318 to the item "edge ID", and adds "third connection information issuance completed" indicating the status to the item "status".

[0211] In step S1507 , the transmission / reception section 311 of the management server 10 transmits a completion notification indicating that the setting is completed to the terminal device 30 that is the request source.

[0212] After executing the processes of steps S1501 to S1507 , when a construction worker or the like installs the communication device 100 at an arbitrary timing and turns on the power of the communication device 100 (step S1511 ), the communication system 1 executes the processes of step S1512 and thereafter.

[0213] In step S1512, the communication device 100 is started up by the first FW 305 pre-stored in the storage unit 304. Furthermore, in step S1513, the communication control unit 301 of the communication device 100 connects to the management server 10 using the first connection information 306 pre-stored in the storage unit 304. At this time, the communication control unit 301 of the communication device 100 transmits a communication device ID for identifying the communication device 100 to the management server 10.

[0214] In step S1514, the device information management unit 314 of the management server 10 updates the device management DB 315. For example, the device information management unit 314 updates the item "status" corresponding to the device ID of the communication device in the device information 400 stored in the device management DB 315 to "initial connection completed".

[0215] In step S1515 , the FW providing section 316A of the management server 10 transmits the second connection information 308 corresponding to the communication device ID of the communication device 100 stored in the storage section 319 and the second FW 307 for connecting to the IoT server 20A to the communication device 100 .

[0216] In step S1516 , the acquisition unit 302 of the communication device 100 stores the second FW 307 and the second connection information 308 received from the management server 10 in the storage unit 304 .

[0217] In step S1517 , the FW providing section 316B of the management server 10 transmits the third connection information corresponding to the communication device ID of the communication device 100 stored in the storage section 319 and the third FW (firmware) for connecting to the IoT server 20B to the communication device 100 .

[0218] In step S1518, the acquisition unit 302 of the communication device 100 stores the third FW and the third connection information received from the management server 10 in the storage unit 304. For example, the acquisition unit 302 may overwrite the third FW received from the management server 10 with the first FW 305 stored in the storage unit 304.

[0219] (Processing when collecting data)

[0220] Fig.16 is a sequence diagram showing an example of the processing during data collection in the second embodiment. Fig.15 This is an example of a process at the time of data collection performed by the communication system 1 after the installation process of the communication process described in .

[0221] In step S1601 , the communication device 100 connects to the IoT server 20A as a connection target using, for example, the second connection information 308 and the second FW 307 stored in the storage section 304 .

[0222] In step S1602, the device information management unit 322 of the IoT server 20A performs authentication processing of the communication device 100 based on the second connection information 308 received from the communication device 100. For example, the device information management unit 322 verifies whether the authentication information (e.g., device certificate) included in the second connection information is legitimate authentication information. Here, since the communication device 100 has the legitimate second connection information 308 issued by the management server 10, the device information management unit 322 permits the connection based on the communication device 100.

[0223] In step S1603, the device information management unit 322 of the IoT server 20A updates the device management DB 324. For example, the device information management unit 322 updates the "status" of the communication device 100 stored in the device management DB 324 of the IoT server 20A to "second connection information connection completed". Note that, as described above, the device information management unit 322 may also update the device information 400 stored in the device management DB 315 of the management server 10 using a network API or the like provided by the receiving unit 312 of the management server 10.

[0224] Through the processing of steps S1601 to S1603 , the communication device 100 can transmit IoT data including data received from the devices 101A, 101B, 101C, . . . to the IoT server 20A in steps S1604 and S1605 .

[0225] In step S1611 , the communication device 100 connects to the target IoT server 20B using, for example, the third connection information and the third FW stored in the storage section 304 .

[0226] In step S1612, the device information management unit 322 of the IoT server 20B performs authentication processing of the communication device 100 based on the third connection information received from the communication device 100. For example, the device information management unit 322 verifies whether the authentication information included in the third connection information is legitimate authentication information. Here, since the communication device 100 has the legitimate third connection information issued by the management server 10, the device information management unit 322 permits the connection based on the communication device 100.

[0227] In step S1613, the device information management unit 322 of the IoT server 20B updates the device management DB 324. For example, the device information management unit 322 updates the "status" of the communication device 100 stored in the device management DB 324 of the IoT server 20B to "third connection information connection completed". Note that, as described above, the device information management unit 322 may also update the device information 400 stored in the device management DB 315 of the management server 10 using the network API provided by the receiving unit 312 of the management server 10.

[0228] Through the processing of steps S1611 to S1613 , the communication device 100 can transmit IoT data including data received from the devices 101A, 101B, 101C, . . . to the IoT server 20A in step S1614 .

[0229] The communication device 100 can transmit IoT data to the IoT server 20A and the IoT server 20B by, for example, alternately and repeatedly performing the first connection process shown in steps S1601 to S1603 and steps S1611 to S1613 .

[0230] (Variation Example)

[0231] As a variation, the communication system 1 may also set the second FW and the third FW as common firmware, and use the connection information management device management unit 303 to collect information such as the type of data, the timing of sending IoT data, and the format of IoT data. Fig.15 In step S1503, the second generation unit 318 of the FW providing unit 316A may generate second connection information including the type of data to be collected, the transmission timing and format of the data, in addition to the URL, edge ID and authentication information for the IoT server A. Similarly, in Fig.15In step 1505, the second generation unit 318 of the FW providing unit 316B may generate third connection information including the type of data to be collected, the transmission timing and format of the data, in addition to the URL, edge ID and authentication information for the IoT server B.

[0232] At this time, the communication device 100 can connect to the IoT server 20A using the shared firmware and the second connection information in step S1601, and send IoT data to the IoT server 20A according to the second connection information in step S1605. Similarly, the communication device 100 can connect to the IoT server 20B using the shared firmware and the third connection information in step S1611, and send IoT data to the IoT server 20B according to the third connection information in step S1614.

[0233] In this way, according to the second embodiment, the communication apparatus 100 can transmit IoT data collected from the devices 101A, 101B, 101C, . . . to a plurality of IoT servers 20 .

[0234] As described above, according to the above-described embodiments, in a communication device that communicates with a server based on connection information and firmware for connecting to the server, it is possible to appropriately communicate with various other servers.

[0235] Although the embodiments have been described above, it will be understood that various changes in form and details may be made without departing from the spirit and scope of the claims.

[0236] This application claims the benefit of priority based on basic application No. 2021-078393 filed with the Japan Patent Office on May 6, 2021, the entire contents of which are incorporated herein by reference.

[0237] Description of Reference Numerals

[0238] 1 Communication system

[0239] 10 Management Server (First Server)

[0240] 20, 20A, 20B IoT server (second server)

[0241] 100 communication devices

[0242] 305 First FW (First Firmware)

[0243] 306 First connection information

[0244] 307 Second FW (Second Firmware)

[0245] 308 Second connection information

[0246] 315 Device Management DB

[0247] 319 Memory

[0248] 400, 400a to 400e device information.

Claims

1. A server, which is a first server including a processor and a storage unit, wherein: The processor: accepting a selection of a service provided by a second server to be used by the communication device or a selection of said second server, In response to accepting the selection of the service to be used by the communication device, storing the service in the storage unit according to each device identification information identifying the communication device, After storing the service, accepting a request from the communication device, the request including first connection information including the device identification information identifying the communication device, identifying a designated second server among a plurality of second servers, the designated second server corresponding to the device identification information included in the first connection information, based on the service, determining the designated second server as the second server to be connected by the communication device, sending, to the communication device, second firmware for connecting to the second server that provides the service to the communication device, In response to accepting the selection of the second server, updating the storage unit that stores a plurality of device identification information identifying a plurality of communication devices and a plurality of information on a plurality of second servers to be connected by the plurality of communication devices in association with each other, After the updating, accepting a request from the communication device, the request including first connection information including device identification information for identifying the communication device, identifying a designated second server among the plurality of second servers based on associations between the plurality of device identification information in the storage unit and the plurality of information on the plurality of second servers, the designated second server corresponding to the device identification information in the first connection information, determining the designated second server as the second server to be connected by the communication device, Second firmware for connecting to the second server that provides the service to the communication device is transmitted to the communication device.

2. The server according to claim 1, wherein: The first server stores second connection information for connecting to the second server and the second firmware, The first server transmits, to the communication device, the second connection information and the second firmware for connecting to the second server that provides the service to the communication device.

3. The server according to claim 2, wherein: The second connection information includes authentication information for connecting to the second server, The first server generates the authentication information for connecting to the second server.

4. A communication system, comprising a first server and a communication device, wherein: The first server: accepting a selection of a service provided by a second server to be used by the communication device or a selection of the second server, In response to accepting the selection of the service to be used by the communication device, storing the service in a storage unit according to each device identification information identifying the communication device, After storing the service, accepting a request from the communication device, the request including first connection information including the device identification information identifying the communication device, identifying a designated second server among a plurality of second servers, the designated second server corresponding to the device identification information included in the first connection information, based on the service, determining the designated second server as the second server to be connected by the communication device, sending, to the communication device, second firmware for connecting to the second server that provides the service to the communication device, The communication device: communicating with the first server based on the first connection information and the first firmware for connecting to the first server, acquiring, from the first server, the second firmware for connecting to the second server different from the first server, In response to accepting the selection of the second server, updating a storage unit that stores a plurality of device identification information identifying a plurality of communication devices and a plurality of information on a plurality of second servers to be connected by the plurality of communication devices in association with each other, After the updating, accepting a request from the communication device, the request including first connection information including the device identification information for identifying the communication device, identifying a designated second server among the plurality of second servers based on associations between the plurality of device identification information in the storage unit and the plurality of information on the plurality of second servers, the designated second server corresponding to the device identification information in the first connection information, determining the designated second server as the second server to be connected by the communication device, sending, to the communication device, second firmware for connecting to the second server that provides the service to the communication device, The communication device: communicating with the first server based on the first connection information and the first firmware for connecting to the first server, The second firmware for connecting to the second server different from the first server is acquired from the first server.

5. A communication method, which is a communication method in a communication system including a first server and a communication device, wherein: The first server accepts a selection of a service provided by a second server to be used by the communication device or a selection of the second server, In response to accepting the selection of the service to be used by the communication device, The first server stores the service to be used by the communication device according to the device identification information for each communication device, The communication device communicates with the first server based on first connection information and first firmware for connecting to the first server, The first server receives a request from the communication device, the request including first connection information including the device identification information for identifying the communication device, identifying a designated second server among a plurality of second servers, the designated second server corresponding to the device identification information included in the first connection information, The first server determines the designated second server as the second server to be connected by the communication device based on the service, The first server sends, to the communication device, second firmware for connecting to the second server that provides the service to the communication device. acquiring, by the communication device, from the first server, the second firmware for connecting to the second server different from the first server, In response to accepting the selection of the second server, updating, by the first server, a storage unit that stores a plurality of device identification information identifying a plurality of communication devices and a plurality of information on a plurality of second servers to be connected by the plurality of communication devices in association with each other, The communication device communicates with the first server based on first connection information and first firmware for connecting to the first server, The first server receives a request from the communication device, the request including the first connection information, the first connection information including device identification information for identifying the communication device, The first server identifies a designated second server among the plurality of second servers based on an association between the plurality of device identification information in the storage unit and the plurality of information of the plurality of second servers, the designated second server corresponding to the device identification information in the first connection information, The first server determines the designated second server as the second server to be connected by the communication device, The first server sends, to the communication device, second firmware for connecting to the second server that provides the service to the communication device. The second firmware for connecting to the second server different from the first server is acquired by the communication device from the first server.

Images