Communication management method and communication management system

Abstract

To provide a communication management method and a communication management system capable of managing entities by using low resources in a unified manner.SOLUTION: In a communication management method for managing communication between entity groups that process data, by a first device and a second device, the first device has a DB that registers entity IDs, and the second device has an entity management function of managing entities and a block-chain network implementation function of issuing non-overlapping address codes in a block-chain network. The entity management function obtains a first address code from the block-chain network implementation function. The entity management function transmits a subscription request for the block-chain network containing an address code. When the first device receives a response including the address code and approving the subscription request, it registers the address code in the DB as an entity ID.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a communication management method and a communication management system for managing communications. [Background technology]

[0002] With the recent spread of the Internet of Things (IoT), there is a growing need for IoT systems that provide stable services by linking a large number of IoT entities (sensor devices, actuators, applications, network switches, servers, data storage) from multiple vendors.

[0003] IoT systems are expected to improve productivity by linking production management information in factories and operation and maintenance information for manufacturing equipment, as well as provide highly reliable and safe services for connected cars. In particular, to ensure such reliability and safety, it is desirable to unify and manage meta-information queries (identity verification queries) for the potentially large number of IoT entities.

[0004] Note that the IoT entity referred to here refers to an element that constitutes an IoT system. Also, in the following description and drawings, for ease of reading, "IoT entity identification ID" may be abbreviated to "entity ID," "application" may be abbreviated to "AP," and "database" may be abbreviated to "DB." Also, "IoT" may be abbreviated, such as "IoT device" being referred to as "device" and "IoT entity" being referred to as "entity." Also, "AP program" refers to program code, and when simply written as "AP," it refers to the instance (process, thread, container, virtual machine) in which the AP program code is running.

[0005] Patent Document 1 discloses a mechanism for centrally managing meta-information (inventory information) of content when sharing information (content such as files) that is stored in a distributed manner. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] U.S. Patent No. 6,044,374 Summary of the Invention [Problem to be solved by the invention]

[0007] Recently, with the increase in devices, there are concerns that the following issues will arise. The Internet is used for communication between devices and APs. As the number of IoT entities continues to increase, the currently widespread Internet will run out of IP addresses to identify entities when communicating with APs. This raises concerns that stable communication will become difficult in the case of a constant connection.

[0008] This also means that IP addresses will no longer be usable as identification IDs to distinguish between devices. Communication will also require management that can communicate with this large number of devices and distinguish between them. Mission-critical applications, in particular, require stable IoT systems, including always-on communication.

[0009] Furthermore, for the convenience and reliability of IoT systems, it is necessary to centrally manage a huge number of devices from multiple vendors. Centralized management of meta information (including inventory information) of IoT entities using a Database Management System (DBMS) also requires a huge amount of computational and storage resources, which is costly and difficult to implement.

[0010] The present invention aims to centrally manage entities with low resource requirements. [Means for solving the problem]

[0011] A communication management method according to one aspect of the invention disclosed in the present application is a communication management method for managing communication between a group of entities that process data by a first device and a second device, wherein the first device includes a first database that registers entity IDs that uniquely identify entities within the group of entities. and a function to determine whether or not to approve a request to join the blockchain network. the second device has an entity management function for managing the entity; The aforementioned a blockchain network realization function that issues a unique address code in the blockchain network to realize the blockchain network, wherein the entity management function obtains a first address code from the blockchain network realization function, and the entity management function issues a first joining request to the blockchain network including the first address code. The first device Send the above Entity Management Functions sends a first response including the first address code and acknowledging the first subscription request. From the first device Upon receiving the first address code, the first address code is registered as the entity ID in the first database. [Effects of the Invention]

[0012] According to the exemplary embodiment of the present invention, entities can be centrally managed with low resource consumption. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiment. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is an explanatory diagram illustrating an example of the overall configuration of an IoT system. [Figure 2] FIG. 2 is a block diagram illustrating an example of the hardware configuration of the server device. [Figure 3] FIG. 3 is a block diagram illustrating an example of the hardware configuration of the device. [Figure 4] FIG. 4 is a block diagram illustrating an example of the hardware configuration of a user terminal. [Figure 5]FIG. 5 is a block diagram illustrating an example of a hardware configuration of a network switching device. [Figure 6] FIG. 6 is an explanatory diagram showing an example of data stored in the main storage device of the server device of the management site. [Figure 7] FIG. 7 is an explanatory diagram showing an example of data stored in the main storage device of the server device at the site of company A. [Figure 8] FIG. 8 is an explanatory diagram showing an example of data stored in the main storage device of the server device at the company B site. [Figure 9] FIG. 9 is an explanatory diagram showing an example of the connection relationships between instances of each AP program in an IoT system. [Figure 10] FIG. 10 is an explanatory diagram showing an example of a unified management process for background confirmation. [Figure 11] FIG. 11 is an explanatory diagram showing an example of a network management process. [Figure 12] FIG. 12 is an explanatory diagram illustrating an example of a process for joining an entity management AP instance to a blockchain network. [Figure 13] FIG. 13 is an explanatory diagram showing an example of a process for joining a device management AP instance and a device AP instance to a blockchain network. [Figure 14] FIG. 14 is an explanatory diagram illustrating an example of a process for collecting data from a device AP instance. [Figure 15] FIG. 15 is an explanatory diagram showing an example of device operation. [Figure 16] FIG. 16 is an explanatory diagram illustrating an example of the entity management table. [Figure 17] FIG. 17 is an explanatory diagram illustrating an example of the query intermediation management table. [Figure 18] FIG. 18 is an explanatory diagram illustrating an example of a table group in the business DB. [Figure 19] FIG. 19 is an explanatory diagram illustrating an example of the access control management table. [Figure 20] FIG. 20 is a flowchart illustrating an example of an entity integration management processing procedure by an entity integration management AP instance. [Figure 21] FIG. 21 is a flowchart showing an example (first half) of an entity management processing procedure by an entity management AP instance. [Figure 22] FIG. 22 is a flowchart showing an example (second half) of the entity management processing procedure by the entity management AP instance. [Figure 23] FIG. 23 is a flowchart illustrating an example of a device management processing procedure performed by a device management AP instance. [Figure 24] FIG. 24 is a flowchart illustrating an example of a device processing procedure by a device AP instance. [Figure 25] FIG. 25 is a flowchart showing an example of a terminal processing procedure by a user terminal AP instance. [Figure 26] FIG. 26 is a flowchart showing an example of a management processing procedure by a network management AP instance. [Figure 27] FIG. 27 is a flowchart illustrating an example of a processing procedure performed by a network switch AP instance. [Figure 28] FIG. 28 is a flowchart showing an example of a processing procedure by a BCNAP instance. [Figure 29] FIG. 29 is a flowchart showing an example of a supply chain management AP instance management processing procedure. DETAILED DESCRIPTION OF THE INVENTION

[0014] Embodiments of the present invention will be described with reference to the accompanying drawings. In the following description, regarding the internal operation and specifications of a blockchain network program (hereinafter, BCNAPP or blockchain network implementation function) that realizes a blockchain network, for example, there are several blockchain platforms publicly available as Open Source Software (OSS), such as Hyperledger Fabric, Ethereum, Quorum, Bitcore, Lisk, etc., which are well-known. Although the function names for calling their functions may differ, since the use of functions provided by any blockchain platform is assumed, the detailed description of the internal operation will be omitted hereinafter.

[0015] <Example of the overall configuration of the IoT system> FIG. 1 is an explanatory diagram showing an example of the overall configuration of an IoT system. The IoT system 1 includes a management site 101 and one or more managed sites (in this example, Company A site 102 and Company B site 103). The management site 101, Company A site 102, and Company B site 103 are each connected to a data communication network 107 such as the Internet, LAN (Local Area Network), or WAN (Wide Area Network) via a network switch device 500. In addition, the device 301 of Company A is connected to the data communication network 107, and the device 302 of Company A and the user terminal 401 of Company B are connected to the data communication network 107 via a communication carrier network 108 for mobile communication.

[0016] The server device 111 at the management site 101 has management-related programs such as a supply chain management AP program, an entity integration management program, and a network management AP program, as well as a query intermediation management DB (Database), an access control management DB 1900, and BCNAPP. Also, as an example, the server device 112 at Company A's site 102 has a device management AP program, a business data DB, an entity management AP program, an entity management DB 1600, and BCNAPP, and the server device 113 at Company B's site 103 has an entity management AP program, an entity management DB 1600, and BCNAPP. These are the minimum resources required in this embodiment.

[0017] <Example of hardware configuration of server devices 111 to 113> 2 is a block diagram showing an example of the hardware configuration of the server devices 111 to 113. When the server devices 111 to 113 are not distinguished from one another, they are referred to as server device 201. The server devices 111 to 113 are distinguished from one another by the program codes and data stored in main storage device 209, and details will be described with reference to FIGS. 6 to 8.

[0018] The server device 201 has a processor 204, a user IF (Interface) 205, a NIC (Network Interface Card) 207 connected to the network switch device 500, a main memory device 209, a DB 210 (e.g., data storage), a data bus 213 connecting them, and a display 202 and keyboard 203 connected to the user IF 205.

[0019] The processor 204 executes the various programs shown in Fig. 1 stored in the main storage device 209. The main storage device 209 stores the various programs shown in Fig. 1 in the server device 201. The DB 210 is the various DBs shown in Fig. 1 in the server device 201.

[0020] <Example of hardware configuration of devices 301 and 302> 3 is a block diagram showing an example of the hardware configuration of devices 301 and 302. When there is no need to distinguish between the devices 301 and 302, they will be referred to as device 300. The device 300 has a processor 303 that executes a program stored in a main memory 306, a wireless communication IF 304 or a NIC 305 that ultimately connects to the data communication network 107, the main memory 306 that stores the program, a group of sensors 307, an actuator IF 308, a data bus 411 that connects them, and an actuator 320 that is connected and controlled by the actuator IF 308. The main memory 306 has a device AP program 309, a work area 410, and a BCNAPP 604.

[0021] <Example of user terminal hardware configuration> 4 is a block diagram showing an example of the hardware configuration of a user terminal 401. In the following description of the user terminal 401, a smartphone is used as an example, but a personal computer may also be used. The user terminal 401 has a touch display 402, an audio input / output 403, a user IF 405 connected to them, a processor 404 that executes programs, a wireless communication IF 406 (corresponding to a NIC) that connects to a communication carrier network, a main memory device 407, and a data bus 411 that connects them. The main memory device 407 has a user terminal AP program 408, a work area 409, and a BCNAPP 604.

[0022] 5 is a block diagram showing an example of the hardware configuration of a network switching device 500. The network switching device 500 has a controller 501 that executes programs, one or more NICs 502, a main memory device 505, and a data bus 508 that connects them. The network switching devices 500, 502, and 503 mediate communications from the server devices 111, 112, and 113, respectively, to the data communication network. The main memory device 505 has a network switch AP program 506, access control information 507, and a BCNAPP 604.

[0023] <Example of data stored in the main memory device 209 of the server device 201> Next, an example of the stored data of the server device 201 will be described using FIGS. 6 to 8.

[0024] FIG. 6 is an explanatory diagram showing an example of data stored in the main memory device 209 (hereinafter, main memory device 601) of the server device 111 of the management site 101. The main memory device 601 of the server device 111 includes a supply chain management AP program 602, an entity integration management AP program 603, a BCNAPP 604, and a network management AP program 605, and a work area 606.

[0025] FIG. 7 is an explanatory diagram showing an example of data stored in the main memory device 209 (hereinafter, main memory device 701) of the server device 112 of Company A site 102. The main memory device 701 includes a device management AP program 702, an entity management AP program 703, and a BCNAPP 604.

[0026] FIG. 8 is an explanatory diagram showing an example of data stored in the main memory device 209 (hereinafter, main memory device 801) of the server device 112 of Company B site 103. The main memory device 801 includes an entity management AP program 802 and a BCNAPP 604.

[0027] The hardware configuration has been described above. Hereinafter, the operations of the programs executed on this hardware configuration will be described. First, cross-sectionally, after briefly explaining the macro operations involving each AP program, the processing flow of each AP program will be described.

[0028] <Example of instance configuration of AP programs included in the IoT system 1> FIG. 9 is an explanatory diagram showing an example of the connection relationship of instances of each AP program included in the IoT system 1.

[0029] The BCNAP instance 901 is an instance of BCNAPP604. The BCNAP instance 901 is a blockchain network realization function that issues unique address codes in the blockchain network in order to realize the blockchain network, and is specifically realized, for example, by having the processors 204, 303, the processor 404, and the controller 501 each execute BCNAPP604. The BCNAP instance 901 does not change an address code once assigned to an address code requester. If multiple address code requests are received from the same requester, the BCNAP instance 901 returns the address code assigned the first time to the requester.

[0030] The network switch AP instance group 902 is a collection of instances (network switch AP instances) of the network switch AP program 506 that controls the network switch device 500, i.e., a collection of network switch control functions. Specifically, the network switch AP instance is realized by, for example, having the controller 501 execute the network switch AP program 506.

[0031] The device management AP instance 903 is an instance of the device management AP program 702 of company A that manages (for example, maintains) the devices 301 and 302 under the jurisdiction of company A. The device management AP instance 903 is a device management function that manages the managed devices such as the device 300, and is specifically realized by, for example, having the processor 204 execute the device management AP program 702.

[0032] The entity management AP instance 904 is an instance of the entity management AP program 703, for example a database management system, that manages the entity IDs of the devices 301 and 302 under the jurisdiction of Company A (for example, managing the entities under its jurisdiction and verifying their identity). The entity management AP instance 904 is an entity management function that manages entities, which are data processing devices or data processing functions implemented by software, and is specifically implemented, for example, by having the processor 204 execute the entity management AP program 703.

[0033] The device AP instance 905 is an instance of the device AP program 309 that executes the operations of the devices 301 and 302 under the jurisdiction of company A. The device AP instance 905 is a device control function that controls managed devices such as the devices 301 and 302, and is specifically realized by, for example, having the processor 303 execute the device AP program 309.

[0034] The user terminal AP instance 906 is an instance of the user terminal AP program 408 that controls the user terminal 401 under the jurisdiction of company B. The user terminal AP instance 906 is a terminal control function that controls the user terminal 401, and is specifically realized, for example, by having the processor 404 execute the user terminal AP program 408.

[0035] The entity management AP instance 907 is an instance of the entity management AP program 703 under the jurisdiction of company B. Like the entity management AP instance 904, the entity management AP instance 907 is an entity management function that manages entities, and is specifically realized by, for example, having the processor 204 execute the entity management AP program 802.

[0036] The network management AP instance 908 is an instance of the network management AP program 605. The network management AP instance 908 is a network management function that manages the network switching device 500, and is specifically realized, for example, by having the processor 204 execute the network management AP program 605.

[0037] The entity integration management AP instance 909 is an instance of the entity integration management AP program 603. The entity integration management AP instance 909 is an entity integration management function that performs integrated management of all entities, and is specifically realized, for example, by having the processor 204 execute the entity integration management AP program 603.

[0038] The supply chain management AP instance 910 is an instance of the supply chain management AP program 602 that manages the supply chain. The supply chain management AP instance 910 is a supply chain management function that manages the supply chain, and is specifically realized, for example, by having the processor 204 execute the supply chain management AP program 602.

[0039] A device management AP instance 903 to a supply chain management AP instance 910 are each connected between the instances 901 and 902. The BCNAP instance 901 exists distributed among the server devices 111 to 113, but because it has the property of operating as a single instance across the devices, it is shown as a single instance in FIG.

[0040] <Centralized management of background checks> 10 is an explanatory diagram showing an example of a centralized management process for background check. In Fig. 10, an external jurisdiction entity 1001 connected to a BCNAP instance 901, which is a blockchain network, is set as the source of background check.

[0041] (1) Inquiry An external authority 1001 issues a background check to a BCNAP instance 901. The background check includes the entity ID of the entity being background checked or information about the entity being background checked that identifies the entity ID.

[0042] (2) Inquiry The entity integration management AP instance 909 of the server device 111 receives background confirmation from the CNAP instance 901. If the background confirmation includes the entity ID of the entity whose background is to be confirmed, the entity integration management AP instance 909 executes (3) a query. If the background confirmation includes information about the entity whose background is to be confirmed that identifies the entity ID, the entity integration management AP instance 909 identifies the entity ID whose background is to be confirmed by referencing a virtual entity management DB that associates the entity ID whose background is to be confirmed with information about the entity whose background is to be confirmed.

[0043] (3) Inquiry The entity integration management AP instance 909 of the server device 111 searches the query intermediation management DB 1700 using the entity ID of the target of background verification to obtain the referenced entity ID associated with the entity ID of the target of background verification. The entity integration management AP instance 909 mediates the background verification to the entity management AP instance 904 of company A identified by the referenced entity ID. In other words, the entity integration management AP instance 909 requests the entity management AP instance 904 of company A identified by the referenced entity ID to make a query using the entity ID of the target of background verification.

[0044] (4)(3) Response to inquiries Company A's entity management AP instance 904 refers to the entity management DB 1600 it holds, performs background check on the entity identified by the entity ID of the background check target, and returns the background check result to the entity integration management AP instance 909. The background check result includes meta information (or inventory information) of the entity identified by the entity ID of the background check target.

[0045] (5)(2) Response to inquiries The entity integration management AP instance 909 stores the identity verification result received from Company A's entity management AP instance 904 in the work area 606, converts it into a predetermined format, and sends it to the BCNAP instance 901 that is the source of the inquiry. When a device 300 is added to the inquiry intermediation management DB 1700, a record is added that associates the entity ID of the device 300 with the referenced entity ID.

[0046] (6)(3) Response to inquiries The BCNAP instance 901 returns the result of the identity verification received from the entity integration management AP instance 909 to the external jurisdiction entity 1001. This makes it possible to verify the identity of the device 300 that is the subject of identity verification.

[0047] <Network Management> 11 is an explanatory diagram showing an example of network management processing. In order to transfer large amounts of data that are not suitable for transfer via the BCNAP instance 901, the IoT system 1 uses the data communication network 107 without going through the BCNAP instance 901. To ensure a reliable connection between communication entities, the IoT system 1 uses the data communication network 107 via the access control of the network switch device 500.

[0048] (1) Settings The entity integrated management AP instance 909 of the server device 111 sets the entity IDs for which connection is permitted in the network management AP instance 908 via the BCNAP instance 901. Since the network management AP instance 908 can access the access control management DB 1900, the entity IDs for which connection is permitted are set in the access control management DB 1900. The access control management DB 1900 has the entity IDs of the network APs, the entity IDs of the senders, and the entity IDs of the receivers. The entity IDs for which connection is permitted are set as either the entity IDs of the senders or the entity IDs of the receivers.

[0049] (2) Control The network management AP instance 908 controls the network switch AP with the entity of the entity ID set in the access control management DB 1900 in the setting (1). This controls communication. That is, when the entity ID for which connection is permitted is set as the entity ID of the sender, the entity integrated management AP instance 909 of the server device 111 receives data from the sender entity and forwards it to the existing destination entity. Also, when the entity ID for which connection is permitted is set as the entity ID of the receiver, the entity integrated management AP instance 909 of the server device 111 receives data from the existing source entity and forwards it to the destination entity.

[0050] <Entity management AP instances 904 and 907 join the blockchain network> Fig. 12 is an explanatory diagram showing an example of processing for joining a blockchain network by the entity management AP instances 904 and 907. Fig. 12 shows, as an example, an example of processing for joining the entity management AP program 703 of company A itself to the blockchain network.

[0051] (1) Joining request The entity management AP instance 904, which is an entity of Company A's entity management AP program 703, obtains an address code from the BCNAP instance 901 by applying to join the blockchain network, and sends a joining request including the obtained address code to the supply chain management AP instance 910.

[0052] (2) Acknowledgment response The supply chain management AP instance 910 sends a manual or automatic approval response to the received join request to the entity management AP instance 904 and the entity integration management AP instance 909 via the BCNAP instance 901.

[0053] The entity management AP instance 904 uses the acquired address code as an entity ID, associates it with the meta information (or inventory information) of the entity management AP instance 904, and registers it in the entity management DB 1600.

[0054] The entity integration management AP instance 909 registers the address code acquired by the entity management AP instance 904 that requested the subscription as an entity ID in the query intermediation management DB 1700. As a result, the entity management AP instance 904 becomes subordinate to the entity integration management AP instance 909.

[0055] <Device management AP instance and device AP instance join the blockchain network> 13 is an explanatory diagram showing an example of a process for joining a blockchain network for a device management AP instance 903 and a device AP instance 905. In FIG. 13, an example of a process for joining Company A's device management AP instance 903 and Company A's device AP instance 905 to an entity management AP instance 904 and coming under the umbrella of an entity integration management AP instance 909 is shown.

[0056] (1) Joining request Company A's device management AP instance 903 obtains an address code from the BCNAP instance 901 by applying to join the blockchain network, and sends a join request to Company A's entity management AP instance 904, including the obtained address code and meta information (or inventory information) of the device management AP instance 903.

[0057] (2) Acknowledgment response The entity management AP instance 904 of company A (1) returns an approval response to the subscription request to the device management AP instance 903 of company A ((2)-1) and also sends it to the BCNAP instance 901 ((2)-2). The approval response includes the address code acquired by the device management AP instance 903 of company A and the entity ID of the entity management AP instance 904 of company A.

[0058] The entity management AP instance 904 of company A uses the address code of the device management AP instance 903 of company A as the entity ID, associates it with the meta information (or inventory information) of the device management AP instance 903 of company A, and registers it in the entity management DB 1600.

[0059] (3) Acknowledgment response The BCNAP instance 901 sends the approval response from company A's entity management AP instance 904 to the entity integration management AP instance 909. The entity integration management AP instance 909 registers the address code acquired by company A's device management AP instance 903 as the entity ID and the entity ID of company A's entity management AP instance 904 as the reference entity ID in the query intermediation management DB 1700.

[0060] (4) Joining request Company A's device AP instance 905 obtains an address code from the BCNAP instance 901 by applying to join the blockchain network, and sends a join request to Company A's entity management AP instance 904, including the obtained address code and meta information (or inventory information) of the device AP instance 905.

[0061] (5) Acknowledgment response The entity management AP instance 904 of company A returns an approval response to the join request (4) to the device AP instance 905 of company A ((5)-1) and also sends it to the BCNAP instance 901 ((5)-2). The approval response includes the address code acquired by the device AP instance 905 of company A and the entity ID of the entity management AP instance 904 of company A. The address code acquired by the device AP instance 905 of company A does not overlap with the address code acquired by the device management AP instance 903 of company A.

[0062] The entity management AP instance 904 of company A uses the address code of the device AP instance 905 of company A as the entity ID, associates it with the meta information (or inventory information) of the device AP instance 905 of company A, and registers it in the entity management DB 1600.

[0063] (6) Acknowledgment response The BCNAP instance 901 sends the approval response from company A's entity management AP instance 904 to the entity integration management AP instance 909. The entity integration management AP instance 909 registers the address code acquired by company A's device AP instance 905 as the entity ID and the entity ID of company A's entity management AP instance 904 as the reference entity ID in the query intermediation management DB 1700.

[0064] <Data collection from device AP instances> 14 is an explanatory diagram showing an example of a process for collecting data from a device AP instance, in which a device management AP instance 903 of company A collects data from a device AP instance 905 of company A.

[0065] (1) Company A device connection application The device management AP instance 903 of company A sends a connection request to the device AP instance 905 to the entity management AP instance 904 of company A via the BCNAP instance 901 .

[0066] (2) Application for connection to Company A's AP The device AP instance 905 sends a connection request to the device management AP instance 903 to the entity management AP instance 904 via the BCNAP instance 901 .

[0067] (3) Connection permission notification The entity management AP instance 904 transmits (1) the company A's device connection request and (2) the entity connection permission notification for the company A's AP connection request to the entity integration management AP instance 909 via the BCNAP instance 901 .

[0068] 10 to the entity integration management AP instance 909 for each of the device management AP instance 903 and the device AP instance 905. As a result, if the identity is confirmed, the entity management AP instance 904 transmits to the entity integration management AP instance 909 an entity connection permission notification for (1) Company A's device connection request and (2) Company A's AP connection request.

[0069] (4) Network connection permission settings The entity integrated management AP instance 909 transmits a connection permission setting to the network management AP instance 908. As a result, the network management AP instance 908 controls the network switch AP instance group 902 to permit communication between the device AP instance 905 and the device management AP instance 903.

[0070] (5) Data collection After communication between the device AP instance 905 and the device management AP instance 903 is permitted, the device management AP instance 903 receives data from the device AP instance 905 and stores it in the business DB 1800 .

[0071] <Device Operation> Fig. 15 is an explanatory diagram showing an example of device operation. Fig. 15 shows an example of processing in which a maintenance technician has a user terminal 401 of company B, operates a user terminal AP 401 held by the user terminal 401, and operates a device AP instance 905 of company A.

[0072] 12 and 13, it is assumed that the entity ID of company B's entity management AP instance 907 has been acquired in advance as an address code from the BCNAP instance 901 and registered in the query intermediation management DB 1700. It is also assumed that the entity ID of company B's entity management AP instance 907 and the entity ID of the user terminal AP instance 906 have been acquired in advance as address codes from the BCNAP instance 901 and associated with the entity ID (queried entity ID) of company B's entity management AP instance 907 and registered in the query intermediation management DB 1700. It is also assumed that company B's entity management DB 1600 has registered the entity ID of company B's entity management AP instance 907 and the entity ID of the user terminal AP instance 906.

[0073] (1) Operation of the user terminal 401 The user terminal 401 inputs the entity ID of the user terminal AP instance 906 either manually by a maintenance technician or via wireless communication (for example, infrared or Bluetooth (registered trademark)).

[0074] (2) Company B user device connection application By operating the user terminal 401, the device AP instance 905 of company A sends a connection request to the entity management AP instance 904 of company A. The connection request includes the entity ID of the user terminal AP instance 906.

[0075] (3) Company B user device identity verification The entity management AP instance 904 of company A sends an identity verification request to the entity integration management AP instance 909 via the BCNAP instance 901. The identity verification request includes the entity ID of the user terminal AP instance 906.

[0076] (4) Company B's user device identity verification request The entity integration management AP instance 909 searches its query intermediation management DB 1700 to obtain the referenced entity ID, and transmits background confirmation to the entity management AP instance 907 of company B. The background confirmation includes the obtained referenced entity ID.

[0077] (5) Response to (4) The entity management AP instance 907 transmits an identity confirmation response to the identity confirmation of (4) to the entity integration management AP instance 909. The entity integration management AP instance 909 transmits the identity confirmation response to the entity management AP instance 904.

[0078] (6) Connection permission notification Based on the identity confirmation response from the entity integration management AP instance 909 , the entity management AP instance 904 sends a connection permission notification to the entity integration management AP instance 909 .

[0079] (7) Network connection permission setting When the entity integration management AP instance 909 receives the (6) connection permission notification, it sends the network connection permission setting to the network management AP instance 908, and controls the network switch AP group instance to permit the communication between the device AP instance 905 and the user terminal AP.

[0080] (8) Operation (after permission) After the connection is permitted, the user terminal 401 operates the device AP instance 905 of Company A through the user terminal AP instance 906.

[0081] (9) Information provision (after permission) After the connection is permitted, the entity management AP instance 904 provides information to the user terminal AP instance 906. This information is the record of the device AP instance 905 registered in the entity management DB 1600 held by the entity management AP instance 904.

[0082] Above, the macro operations that intervene through each AP program have been briefly described cross-sectionally. Next, the record definition of the DB will be described, and the operations of each AP program will be described.

[0083] <Record definition of DB> 16 is an explanatory diagram showing an example of an entity management table. The entity management table 1610 is provided in the entity management DB 1600. The entity management table 1610 has, as columns of records, an entity ID 1611 that uniquely identifies an entity, a validity period start date and time 1612 for the validity period during which the record is valid, a validity period end date and time 1613 for the validity period during which the record is valid, a type 1614 of the entity identified by the entity ID, and a client digital certificate 1615. The type 1614 holds a code or character string that can distinguish not only the type of device (sensor, actuator) but also APs (entity management APs, etc.) and other services. The validity period start date and time 1612, the validity period end date and time 1613, the type 1614, and the client digital certificate 1615 are examples of meta-information (or inventory information).

[0084] 17 is an explanatory diagram showing an example of a query intermediation management table. The query intermediation management table 1710 is provided in the query intermediation management DB 1700. The query intermediation management table 1710 has, as record columns, an entity ID 1611 and a reference entity ID 1711. The reference entity ID 1711 is the entity ID 1611 that uniquely identifies the reference entity. The reference entity is an entity that can query the entity whose identity is to be verified.

[0085] In the approval response (2) of FIG. 12, the address code of the entity management AP instance 904 that requested the subscription is registered in each of the entity ID 1611 and the referenced entity ID 1711, and a record is created.

[0086] In the approval response (3) of Figure 13, the address code acquired by Company A's device management AP instance 903 is registered in entity ID 1611, and the entity ID of the entity management AP instance 904 associated with the entity ID 1611 is registered in reference entity ID 1711, and a record is created.

[0087] In the approval response (6) of Figure 13, the address code acquired by Company A's device AP instance 905 is registered as entity ID 1611, and the entity ID of the entity management AP instance 904 associated with the entity ID 1611 is registered as reference entity ID 1711, and a record is created.

[0088] 18 is an explanatory diagram showing an example of a group of tables in a business DB 1800. The business DB 1800 has a device table 1801 and a device data table 1802. The device table 1801 has a managed entity ID 1810 as a column of records. The managed entity ID 1810 is an entity ID 1611 that uniquely identifies a managed entity. A managed entity is an entity managed by the server device 201 that holds the business DB 1800. In this example, the business DB 1800 is provided only in the server device 112 of the A company site 102, and therefore the managed entities are the devices 301 and 302 managed by A company.

[0089] The device data table 1802 has, as columns of records, a managed entity ID 1810 and acquired data 1820. The acquired data 1820 is data acquired by the managed entity identified by the managed entity ID 1810.

[0090] 19 is an explanatory diagram showing an example of an access control management table. The access control management table 1910 is provided in the access control management DB 1900. The access control management table 1910 has, as columns of records that are the access control information 507, a network switch AP entity ID 1911, a sending entity ID 1912, and a receiving entity ID 1913.

[0091] The network switch AP entity ID 1911 is the entity ID 1611 that uniquely identifies a network switch AP instance within the network switch AP instance group 902 .

[0092] The sending entity ID 1912 is the entity ID 1611 that uniquely identifies the sending entity. The sending entity is the entity that is the source of the transmission. The receiving entity ID 1913 is the entity ID 1611 that uniquely identifies the receiving entity. The receiving entity is the entity that is the destination.

[0093] In the initial state, only record 1921 is registered in the access control management table 1910. Record 1921 specifies a communication path from the device AP instance 905 in the existing device apparatus 301 of company A, identified by a sending entity ID 1912 (xxx...x), via a network switch AP instance identified by a network switch AP entity ID 1911 (aaa...a), to the device management AP instance 903 of company A, identified by a receiving entity ID 1913 (ddd...d).

[0094] 14 is performed at Company A's site 102, record 1922 is added. Record 1922 specifies a communication path from the device AP instance 905 in the new device apparatus 302 of Company A, identified by the sending entity ID 1912 (yyy...y), via the network switch AP instance identified by the network switch AP entity ID 1911 (aaa...a), to Company A's device management AP instance 903, identified by the receiving entity ID 1913 (ddd...d). By adding record 1922, a connection between Company A's device AP instance 905 and Company A's device management AP instance 903 is permitted, as shown in FIG. 14.

[0095] 15 is performed between company A's site 102 and company B's site 103, record 1923 is added. Record 1923 specifies a communication path from the device AP instance 905 in the new user terminal 401 of company B, identified by the sending entity ID 1912 (bbb...b), via the network switch AP instance identified by the network switch AP entity ID 1911 (aaa...a), to the device AP instance 905 in the device apparatus 302 of company AA, identified by the receiving entity ID 1913 (yyy...y). By adding record 1923, connection between company A's device AP instance 905 and company B's user terminal 401 is permitted, as shown in FIG. 15.

[0096] Next, an example of the processing procedure by the above-mentioned AP program will be explained. In the processing by the AP program below, the AP program is executed by a processor, so the AP program is executed by the processor, but for convenience of explanation, the AP program will be used as the subject in the explanation.

[0097] <Entity integration management processing by entity integration management AP instance 909> FIG. 20 is a flowchart showing an example of the entity integration management processing procedure by the entity integration management AP instance 909.

[0098] [Step S2001] The entity integration management AP instance 909 determines whether or not there is an identity verification request. If there is an identity verification request (step S2001: Yes), the entity integration management AP instance 909 proceeds to step S2004, and if there is no identity verification request (step S2001: No), the entity integration management AP instance 909 proceeds to step S2002.

[0099] [Step S2002] The entity integration management AP instance 909 determines whether an approval response has been received, and if an approval response has been received (step S2002: Yes), the process proceeds to step S2008. If an approval response has not been received (step S2002: No), the process proceeds to step S2003.

[0100] [Step S2003] The entity integrated management AP instance 909 determines whether a connection permission notification has been received. If a connection permission notification has been received (step S2003: Yes), the process proceeds to step S2009. If a connection permission notification has not been received (step S2003: No), the process ends.

[0101] [Step S2004] The entity integration management AP instance 909 receives the data including the entity ID 1611 to be verified, searches the query intermediation management table for the entity ID 1611, and proceeds to step S2005.

[0102] [Step S2005] The entity integration management AP instance 909 determines whether or not there is registration based on the search result of step S2004. If there is registration (step S2005: Yes), step S2006 is executed. If there is no registration (step S2005: No), the process proceeds to step S2007.

[0103] [Step S2006] The entity integration management AP instance 909 mediates the identity verification to the entity management AP instance specified by the referenced entity ID, and responds with the mediation result to the source of the identity verification inquiry, thereby completing the process.

[0104] [Step S2007] The entity integration management AP instance 909 responds to the source of the identity verification inquiry that there is no registration, thereby completing the process.

[0105] [Step S2008] The entity integration management AP instance 909 receives the approved entity ID 1611 and data including the approved entity ID 1611, and registers them in the query intermediation management table. In the case of a notification without an intermediary, the entity integration management AP instance 909 may register the intermediary by leaving it blank or by setting the value to the same as the notified entity ID. In this case, if the record has already been registered, the entity integration management AP instance 909 updates the record. This completes the processing.

[0106] [Step S2009] The entity integrated management AP instance 909 sends a setting that enables communication between the entity IDs that have been permitted to be connected to the network management AP instance 908. This completes the processing. The processing of the entity integrated management AP instance 909 has been described above.

[0107] <Entity management processing by entity management AP instances 904 and 907> FIG. 21 is a flowchart showing an example (first half) of the entity management processing procedure by the entity management AP instances 904 and 907.

[0108] [Step S2101] The entity management AP instances 904 and 907 determine whether a join request has been received. If a join request has been received (step S2101: Yes), the process proceeds to step S2104, and if a join request has not been received (step S2101: No), the process proceeds to step S2102.

[0109] [Step S2102] The entity management AP instances 904 and 907 determine whether or not identity confirmation has been received, and if identity confirmation has been received (step S2102: Yes), proceed to step S2105, and if identity confirmation has not been received (step S2102: No), proceed to step S2103.

[0110] [Step S2103] The entity management AP instances 904 and 907 determine whether or not to accept the joining request, and if a joining request is required (step S2103: Yes), the process proceeds to step S2106, and if a joining request is not required (step S2103: No), the process proceeds to step S2201 in Fig. 22. Note that a joining request occurs when the entity management AP instances 904 and 907 themselves are newly added to the IoT system 1.

[0111] [Step S2104] The entity management AP instances 904, 907 receive input of approval or disapproval for the entity ID for which joining is being sought, and proceed to step S2107. This input of approval or disapproval may be done manually using the keyboard 203 of the server device 201, or data to be approved may be prepared in advance and a determination may be made based on that data.

[0112] [Step S2107] The entity management AP instances 904, 907 determine whether the result of step S2104 is approval or not, and if approval is obtained (step S2107: Yes), the process proceeds to step S2109, and if not approval is obtained (step S2107: No), the process proceeds to step S2108.

[0113] [Step S2109] The entity management AP instances 904 and 907 register the entity ID for which joining is requested in the entity management table, and respond with "approval" to the entity identified by the entity ID for which joining is requested, thereby completing the process.

[0114] [Step S2108] The entity management AP instances 904 and 907 respond with "unapproved" to the entity identified by the entity ID requesting to join, thereby completing the process.

[0115] [Step S2105] The entity management AP instances 904 and 907 search the entity management table for the entity ID to be verified. The entity management AP instances 904 and 907 respond to the query source with the presence or absence of the entity ID to be verified, which is obtained from the search results. This completes the process.

[0116] [Step S2106] The entity management AP instances 904 and 907 acquire the address code from the BCNAP instance 901, use the acquired address code as an entity ID, send a join request to themselves, and receive an approval response, thereby completing the process.

[0117] FIG. 22 is a flowchart showing an example (second half) of the entity management processing procedure by the entity management AP instances 904 and 907.

[0118] [Step S2201] The entity management AP instances 904 and 907 determine whether a connection request has been received, and if a connection request has been received (step S2101: Yes), proceed to step S2202, and if no connection request has been received (step S2101: No), end the process.

[0119] [Step S2202] The entity management AP instances 904 and 907 confirm the identity of the entity ID for which a connection request has been made with the entity integrated management AP instance 909, and the process proceeds to step S2203.

[0120] [Step S2203] The entity management AP instances 904, 907 determine whether the entity ID requested for connection is registered based on the identity verification results of step S2202, and if the entity ID requested for connection is registered (step S2203: Yes), proceed to step S2205; if the entity ID requested for connection is not registered (step S2203: No), proceed to step S2204.

[0121] [Step S2205] The entity management AP instances 904 and 907 receive input from the operator or the like as to whether or not connection permission is required, and proceed to step S2206.

[0122] [Step S2206] If the result of the connection permission necessity test shows that connection permission is necessary (step S2206: Yes), the entity management AP instances 904 and 907 proceed to step S2207, and if connection permission is not necessary (step S2206: No), the process ends.

[0123] [Step S2204] The entity management AP instances 904 and 907 respond with "denial" and terminate the processing. The processing of the entity management AP instances 904 and 907 has been described above.

[0124] <Entity Management Processing by Device Management AP Instance 903> FIG. 23 is a flowchart showing an example of a device management processing procedure performed by the device management AP instance 903.

[0125] [Step S2301] The device management AP instance 903 determines whether a connection request has been received, and if a connection request has been received (step S2301: Yes), proceeds to step S2304, and if no connection request has been received (step S2301: No), proceeds to step S2302.

[0126] [Step S2302] The device management AP instance 903 determines whether a membership application is required, and if a membership application is required (step S2302: Yes), the process proceeds to step S2310, and if a membership application is not required (step S2302: No), the process proceeds to step S2303. The determination of whether a membership application is required occurs when the device management AP instance 903 is added to the IoT system 1.

[0127] [Step S2303] The device management AP instance 903 determines whether data has been received from the device 300, and if data has been received (step S2303: Yes), proceeds to step S2311, and if data has not been received (step S2303: No), ends the process.

[0128] [Step S2304] The device management AP instance 903 confirms the identity of the entity ID for which a connection request has been made with the entity integrated management AP instance 909, and proceeds to step S2305.

[0129] [Step S2305] If the result of the identity verification in step S2304 is that the entity ID requested for connection is registered (step S2305: Yes), the device management AP instance 903 proceeds to step S2307; if the entity ID requested for connection is not registered (step S2305: No), the device management AP instance 903 proceeds to step S2306.

[0130] [Step S2307] The device management AP instance 903 receives an input as to whether connection permission is required and proceeds to step S2308. This input as to whether connection permission is required may be manual, or list data of entity IDs for which connection permission is to be issued may be prepared in advance, and the device management AP instance 903 may make a determination based on that data.

[0131] [Step S2306] The device management AP instance 903 responds with a denial of permission and proceeds to step S2302.

[0132] [Step S2308] The device management AP instance 903 determines whether connection permission is required, and if connection permission is required (step S2308: Yes), proceeds to step S2309, and if connection permission is not required (step S2308: No), proceeds to step S2302.

[0133] [Step S2309] The device management AP instance 903 sends a connection permission notification to the request source and the entity integration management AP instance 909, and proceeds to step S2302.

[0134] [Step S2302] The device management AP instance 903 determines whether a joining application is required, and if a joining application is required (step S2302: Yes), proceeds to step S2310, and if a joining application is not required (step S2302: No), proceeds to step S2303. Step S2302 occurs when the device management AP instance 903 is added to the IoT system 1.

[0135] [Step S2310] The device management AP instance 903 acquires the address code from the BCNAP instance 901, sends a join request to the entity management AP instances 904 and 907 using the acquired address code as the entity ID, receives an approval response from the entity management AP instances 904 and 907, and proceeds to step S2303.

[0136] [Step S2311] The device management AP instance 903 registers the data received from the device 300 in the device data table 1802. This completes the process. The process of the device management AP instance 903 has been described above.

[0137] <Device processing by device AP instance 905> FIG. 24 is a flowchart showing an example of a device processing procedure performed by the device AP instance 905.

[0138] [Step S2401] The device AP instance 905 determines whether a subscription application is required, and if a subscription application is required (step S2401: Yes), proceeds to step S2403, and if a subscription application is not required (step S2401: No), proceeds to step S2402.

[0139] [Step S2403] The device AP instance 905 acquires the address code from the BCNAP instance 901, sends a join request to the entity management AP instances 904 and 907 using the acquired address code as the entity ID, receives an approval response from the entity management AP instances 904 and 907, and proceeds to step S2402.

[0140] [Step S2402] The device AP instance 905 determines whether a connection request is required, and if a connection request is required (step S2402: Yes), proceeds to step S2404, and if a connection request is not required (step S2402: No), proceeds to step S2405. The determination of whether a connection request is required may be made by manual input, or a mechanism such as a timer may be provided to make the necessary request at regular intervals or at a fixed time.

[0141] [Step S2404] The device AP instance 905 sends a connection request to the device management AP instance 903 to the entity management AP instances 904 and 907, and the process proceeds to step S2405.

[0142] [Step S2405] The device AP instance 905 determines whether connection permission and data transmission are required, and if connection permission and data transmission are required (step S2405: Yes), proceeds to step S2406, and if connection permission and data transmission are not required (step S2405: No), ends the process. Regarding the determination of whether connection permission and data transmission are required, the device AP instance 905 may determine that they are required in conjunction with step S2402 if there is data to transmit.

[0143] [Step S2406] The device AP instance 905 transmits the data to the device management AP instance 903 and ends the processing. The processing of the device AP instance 905 has been described above.

[0144] <Terminal Processing by User Terminal AP Instance 906> FIG. 25 is a flowchart showing an example of a terminal processing procedure by the user terminal AP instance 906.

[0145] [Step S2501] The user terminal AP instance 906 determines whether a subscription application is required, and if a subscription application is required (step S2501: Yes), proceeds to step S2503, and if a subscription application is not required (step S2501: No), proceeds to step S2502.

[0146] [Step S2502] The user terminal AP instance 906 determines whether or not the operation is a maintenance operation, and if it is a maintenance operation (step S2502: Yes), the process proceeds to step S2504, and if it is not a maintenance operation (step S2502: No), the process ends.

[0147] [Step S2503] The user terminal AP instance 906 acquires an address code from the BCNAP instance 901, sends a join request to the entity management AP instances 904 and 907 using the acquired address code as the entity ID, receives an approval response from the entity management AP instances 904 and 907, and proceeds to step S2502. Note that if an address code is acquired for the first time in step S2504, the user terminal AP instance 906 acquires the same address code.

[0148] [Step S2504] The user terminal AP instance 906 acquires an address code from the BCNAP instance 901, inputs the acquired address code as an entity ID to the device AP instance 905 to be maintained, requests connection permission from the entity management AP instance 904 to which the device apparatus 300 belongs, and proceeds to step S2505. Note that if an address code was acquired for the first time in step S2503, the user terminal AP instance 906 acquires the same address code.

[0149] [Step S2505] The user terminal AP instance 906 determines whether the connection is permitted, and if the connection is permitted (step S2505: Yes), proceeds to step S2506, and if the connection is not permitted (step S2505: No), ends the process.

[0150] [Step S2506] The user terminal AP instance 906 performs an operation on the device and ends the processing. The operation on the device may be performed by the operator directly operating the device, as well as via the user terminal AP instance 906. The terminal processing of the user terminal AP instance 906 has been described above.

[0151] <Management process by network management AP instance 908> FIG. 26 is a flowchart showing an example of a management processing procedure performed by the network management AP instance 908.

[0152] [Step S2601] The network management AP instance 908 determines whether a connection permission notification has been received, and if a connection permission notification has been received (step S2601: Yes), proceeds to step S2602, and if a connection permission notification has not been received (step S2601: No), ends the process.

[0153] [Step S2602] The network management AP instance 908 updates the access control management table and proceeds to step S2909.

[0154] [Step S2603] The network management AP instance 908 distributes the configuration information to the network switch AP instance. Thereby, the process ends. Above, the process of the network management AP instance 908 has been described.

[0155] <Processing by the network switch AP instance> FIG. 27 is a flowchart showing an example of a processing procedure by the network switch AP instance.

[0156] [Step S2701] The network switch AP instance determines whether the configuration information has been received. If the configuration information has been received (Step S2701: Yes), it proceeds to Step S2702. If the configuration information has not been received (Step S2701: No), it proceeds to Step S2703.

[0157] [Step S2702] The network switch AP instance updates the connection availability status and proceeds to Step S2703.

[0158] [Step S2703] The network switch AP instance maintains the connection availability status based on the configuration information. Thereby, the process ends. Above, the process of the network switch AP instance has been described. <Processing by the BCNAP instance 901> FIG. 28 is a flowchart showing an example of a processing procedure by the BCNAP instance 901. The BCNAP instance 901 is an instance that is widespread in OSS (Open Source Software). In FIG. 28, only the processing related to this embodiment will be described.

[0159] [Step S2801] The BCNAP instance 901 determines whether or not it is an initial startup, and if it is an initial startup (step S2801: Yes), proceeds to step S2805, and if it is not an initial startup (step S2801: No), proceeds to step S2802.

[0160] [Step S2802] The BCNAP instance 901 determines whether or not it is an address code inquiry, and if it is an inquiry (step S2802: Yes), proceeds to step S2806, and if it is not an inquiry (step S2802: No), proceeds to step S2803.

[0161] [Step S2803] The BCNAP instance 901 determines whether or not there is a data transmission request, and if there is a data transmission request (step S2803: Yes), proceeds to step S2807, and if there is no data transmission request (step S2803: No), proceeds to step S2804.

[0162] [Step S2804] The BCNAP instance 901 determines whether or not there is a data reception request, and if there is a data reception request (step S2804: Yes), proceeds to step S2808, and if there is no data reception request (step S2804: No), ends the process.

[0163] [Step S2805] The BCNAP instance 901 generates and stores an address code that has never been duplicated before, and proceeds to step S2802.

[0164] [Step S2806] The BCNAP instance 901 returns the address code it holds to the address code query source, and proceeds to step S2803.

[0165] [Step S2807] The BCNAP instance 901 sends the data to the destination address and proceeds to step S2804.

[0166] [Step S2808] The BCNAP instance 901 acquires the received data. This completes the processing. The processing of the BCNAP instance 901 has been described above.

[0167] <Management process of supply chain management AP instance 910> FIG. 29 is a flowchart showing an example of a management processing procedure of the supply chain management AP instance 910.

[0168] [Step S2901] Supply Chain Management AP Instance 910 is the first period Start or not Or If it is the initial startup (step S2901: Yes), the process proceeds to step S2903. If it is not the initial startup (step S2901: No), the process proceeds to step S2902.

[0169] [Step S2902] The supply chain management AP instance 910 determines whether a join request has been received, and if a join request has been received (step S2902: Yes), proceeds to step S2904. If a join request has not been received (step S2902: No), the process ends.

[0170] [Step S2903] The supply chain management AP instance 910 acquires the address code from the BCNAP instance 901, stores the acquired address code as its own entity ID, sends an approval response (ID notification) to the entity integration management AP instance 909, and proceeds to step S2902.

[0171] [Step S2904] The supply chain management AP instance 910 acquires the input of whether or not to approve in step S2903, and proceeds to step S2905. The means for acquiring the input of whether or not to approve may be input from the keyboard 203, or a list of targets to be approved may be stored in advance in the main storage device 209. The target list is a list of entity IDs. The supply chain management AP instance 910 may perform approval based on the target list. Specifically, for example, the supply chain management AP instance 910 will perform approval if the entity ID (address code) included in the joining request matches any of the entity IDs in the target list.

[0172] [Step S2905] If the supply chain management AP instance 910 determines that the request is approved (step S2904: Yes), the process proceeds to step S2906. If the supply chain management AP instance 910 determines that the request is not approved (step S2904: No), the process proceeds to step S2907.

[0173] [Step S2906] The supply chain management AP instance 910 responds with approval to the sender of the join request and the entity integration management AP instance 909, and then ends the process.

[0174] [Step S2907] The supply chain management AP instance 910 responds with a denial to the sender of the join request. This completes the processing. The processing of the supply chain management AP instance 910 has been explained above. The processing of each AP instance has now been explained.

[0175] As described above, the IoT system 1 includes the devices 301 and 302, the user terminal 401, the server devices 111 to 113, and the network switch device 500 that connects them to provide mutual data communication and connection to the data communication network 107.

[0176] The server device 111 also has a BCNAP program that assigns unique address codes to some or all of the components of the IoT system 1, i.e., entities, via the network switch device 500 to provide mutual data communication, and an entity management database 1600 that uses the address codes assigned by the BCNAP program as entity IDs and holds records that associate the address codes with meta information (inventory information) of the entities to which they are assigned.

[0177] As a result, the product vendor allows each entity to participate in the blockchain network generated by the BCNAP instance 901, obtains a unique address code assigned on the blockchain network, uses this address code as the entity's identification ID, and manages the entities through entity management AP instances 904 and 907 provided by companies A and B. Here, by treating not only the devices 301 and 302 as entities but also programmatic instances such as applications and services as entities, it is possible to reduce resources.

[0178] Furthermore, the IoT system 1 may build a blockchain network for each corporate group that requires communication, and provide communication only between entities participating in the blockchain network. In this example, a blockchain network is built for one corporate group consisting of companies A and B, but separate blockchain networks may also be built for companies B, C, and D, for example.

[0179] In response to participation applications, the blockchain network issues a unique, non-duplicate address code upon approval by an administrator or management application, and enables data communication between entities and service provision through smart construct functions (remote AP execution functions) based on the unique address code.

[0180] The server device 111 also has an entity integrated management AP instance 909 and a query intermediation management table 1710. The server device 111 refers to the query intermediation management table 1710, identifies the reference entity ID of the IoT entity management application program that holds the inventory information or meta information from the entity ID, and operates to obtain the inventory information or meta information by querying the entity management AP instances 904, 907 associated with the identified reference entity ID, thereby providing unified management of the inventory information or meta information.

[0181] Based on the entity ID of the entity for which identity verification (meta information query) has been requested, the entity integration management AP instance 909 issues a query via its smart construct function to the entity management AP instance 904 of the company that holds the entity information, obtains the entity's meta information, and returns it to the requestor. As a result, when the entity integration management AP instance 909 provides one-stop centralized management to the IoT system 1, it does not need to hold meta information for all the entities it handles, enabling the IoT system 1 to reduce resource usage.

[0182] As a result, it is possible to reduce the resources used in the centralized management of a huge number of entities in the IoT system 1. In communications between entities, it becomes possible to communicate using entity IDs as addresses, which also makes it possible to reduce the number of IP addresses used, which are a concern as they may become depleted.

[0183] The present invention is not limited to the above-described embodiments, and includes various modifications and equivalent configurations within the spirit and scope of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to configurations including all of the described configurations. Furthermore, part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, part of the configuration of each embodiment may be added to, deleted from, or replaced with other configurations.

[0184] Furthermore, each of the aforementioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example, by designing some or all of them as integrated circuits, or may be realized in software, by a processor interpreting and executing instances that realize each function.

[0185] Information such as instances, tables, and files that realize each function can be stored in storage devices such as memory, hard disks, and SSDs (Solid State Drives), or on recording media such as IC (Integrated Circuit) cards, SD cards, and DVDs (Digital Versatile Discs).

[0186] In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and do not necessarily show all the control lines and information lines that are necessary for implementation. In reality, it can be assumed that almost all components are interconnected. [Explanation of symbols]

[0187] 101 Management Site 102 Company A website 103 Company B website 107 Data Communication Network 108 Telecommunications Carrier Network 111~113 Server equipment 301, 302 Device (Management Device) 401 User terminal 500 Network Switching Device 901 BCNAP instances (blockchain network realization function) 902 Network Switch AP Instance Group (Network Switch Control Function) 903 Device management AP instance (device management function) 904,907 Entity management AP instance (entity management function) 905 Device AP Instance (Device Control Function) 906 User terminal AP instance (terminal control function) 908 Network Management AP Instance (Network Management Function) 909 Entity Integration Management AP Instance (Entity Integration Management Function) 910 Supply Chain Management AP Instance (Supply Chain Management Function) 1600 Entity Management DB 1610 Entity Management Table 1611 Entity ID 1700 Inquiry Brokerage Management DB 1710 Inquiry Brokerage Management Table 1711 Reference Entity ID 1800 Business DB 1801 Device Table 1802 Device Data Table 1900 Access Control Management DB 1910 Access Control Management Table

Claims

1. 1. A method of managing communications between entities that process data, by a first device and a second device, comprising: The first device has a first database that registers an entity ID that uniquely identifies an entity within the entity group, and a function that determines whether to approve a request to join the blockchain network, The second device has an entity management function that manages the entity, and a blockchain network implementation function that issues a unique address code in the blockchain network to implement the blockchain network, The entity management function obtains a first address code from the blockchain network realization function; The entity management function sends a first join request to the blockchain network to the first device, the first join request including the first address code; when the entity management function receives a first response from the first device that includes the first address code and acknowledges the first subscription request, it registers the first address code as the entity ID in the first database. A communication management method comprising:

2. 2. The communication management method according to claim 1, the second device has a second database associating information about the entity with the entity ID; When the entity management function receives the first response from the first device, the entity management function registers the first address code as the entity ID in the second database in association with information about the entity management function. A communication management method comprising:

3. 2. The communication management method according to claim 1, the second device has a device management function for managing a managed device that is the entity of the first device; The device management function acquires a second address code from the blockchain network realization function; The device management function sends a second join request to the blockchain network, including the second address code, to the entity management function; the entity management function sending a second response to the first device, the second response including the first address code and the second address code and acknowledging the second subscription request; When the first device receives the second response, the first device registers the second address code as the entity ID and the first address code as the entity ID of the entity to be queried by the device management function in the first database in association with the first address code and the second address code. A communication management method comprising:

4. 4. The communication management method according to claim 3, the second device has a second database associating information about the entity with the entity ID; the entity management function registers the second address code as the entity ID in the second database in association with information about the device management function; A communication management method comprising:

5. 4. The communication management method according to claim 3, The management target device has a device control function that controls the management target device and the blockchain network realization function, The device control function acquires a third address code from the block chain network realization function possessed by the device control function, The device control function sends a third join request to the blockchain network, including the third address code, to the entity management function; the entity management function sending a third response to the first device, the third response including the first address code and the third address code and acknowledging the third subscription request; When the first device receives the third response, the first device registers the third address code as the entity ID and the first address code as the entity ID of the entity to which the device control function is referred in the first database in association with the first address code and the third address code. A communication management method comprising:

6. 6. The communication management method according to claim 5, the second device has a second database associating information about the entity with the entity ID; the entity management function registers the third address code as the entity ID in the second database in association with information about the device control function; A communication management method comprising:

7. 6. The communication management method according to claim 5, the device management function sends a first connection request to the device control function, the first connection request including the second address code, to the entity management function; When the entity management function receives the first connection request, the entity management function sends a first connection permission notification to the device management function and the first device, the first connection permission notification permitting connection to the device control function; the device control function sends a second connection request to the device management function, the second connection request including the third address code, to the entity management function; When the entity management function receives the second connection request, the entity management function sends a second connection permission notification to the device control function and the first device, the second connection permission notification permitting connection to the device management function; When the first device receives the first connection permission notification and the second connection permission notification, the first device sets up a connection between the device management function and the device control function so that they can communicate with each other. A communication management method comprising:

8. 8. The communication management method according to claim 7, When the entity management function receives the first connection request, it sends a first identity verification request including the second address code to the first device; When the first device receives the first identity verification request, the first device refers to the first database to check whether the second address code exists, and if the second address code exists, sends a first identity verification result indicating the existence of the second address code to the entity management function; When the entity management function receives the first identity verification result, the entity management function sends the first connection permission notification to the device management function and the first device; When the entity management function receives the second connection request, it sends a second identity verification request including the third address code to the first device; When the first device receives the second identity verification request, the first device refers to the first database to check whether the third address code exists, and if the third address code exists, sends a second identity verification result indicating the existence of the third address code to the entity management function; When the entity management function receives the second identity verification result, the entity management function sends the second connection permission notification to the device control function and the first device. A communication management method comprising:

9. 1. A communications management system for managing communications between entities that process data by a first device and a second device, comprising: The first device has a first database that registers an entity ID that uniquely identifies an entity in a group of entities, which is a data processing device or a data processing function realized by software, and a function that determines whether to approve a request to join the blockchain network, The second device has an entity management function that manages the entity, and a blockchain network implementation function that issues a unique address code in the blockchain network to implement the blockchain network, The entity management function obtains a first address code from the blockchain network realization function; The entity management function sends a first join request to the blockchain network to the first device, the first join request including the first address code; when the entity management function receives a first response from the first device that includes the first address code and acknowledges the first subscription request, it registers the first address code as the entity ID in the first database. A communication management system characterized by:

Images