Communication system, inspection device, inspection method, and program

The communication system inspects and ensures correct switching of redundant Pubs in Pub/Sub systems by inserting anomalies, addressing potential data integrity issues and unauthorized data transmission.

JP7578187B2Active Publication Date: 2024-11-06NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023510124
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-04-01
Publication Date
2024-11-06
Estimated Expiration
2041-04-01

AI Technical Summary

Technical Problem

In communication systems using Pub/Sub communication, there is a challenge in ensuring that redundant Publishers (Pubs) are correctly switched when an abnormality occurs, as the priority Pub may not switch as expected, leading to potential data integrity issues.

Method used

A communication system with an inspection management unit that receives inspection instructions for redundant applications, inserting anomalies to verify correct switching of priority Pubs to alternative applications, utilizing configuration information to manage and inspect the Pub side.

Benefits of technology

Ensures that priority Pub switching is performed correctly, preventing data integrity issues by detecting and addressing abnormalities or unauthorized data transmission.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007578187000001
    Figure 0007578187000001
  • Figure 0007578187000002
    Figure 0007578187000002
  • Figure 0007578187000003
    Figure 0007578187000003
Patent Text Reader

Abstract

This communication system performs communication between a plurality of nodes by using a publish / subscribe type model of a broker-less type. By receiving an inspection instruction for one application preferentially operated on a purchase side, among one or more applications that have been made redundant on one or more of the nodes and that function as a publication side, and inserting an abnormality to the one application, the communication system inspects switching of the application preferentially operated on the purchase side to another application different from the one application among the one or more applications.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a technique for inspecting a redundant configuration on the Pub side in a communication system performing Pub / Sub communication. [Background technology]

[0002] In recent years, efforts to realize smart factories have been progressing by connecting devices on information networks with devices on control networks. In the future, it is expected that communication models that interconnect devices and enable one-to-many and many-to-one communication in a lightweight and flexible manner will become more widespread.

[0003] The Publish / Subscribe communication (hereafter referred to as Pub / Sub communication) model has been proposed as a lightweight and flexible communication model as described above. In Pub / Sub communication, there are Publishers, which are clients that create and send (distribute) messages called events, and Subscribers, which are clients that receive (subscribe) to messages.

[0004] Pub / Sub communication has three properties: "spatial separation," "temporal separation," and "asynchronous processing." "Spatial separation" means that the publisher and subscriber do not need to know of each other's existence. "Temporal separation" means that data can be sent and received even if the publisher and subscriber are not on the network at the same time. Furthermore, "asynchronous processing" means that the sending and receiving of events can be processed asynchronously with other processing by the publisher or subscriber.

[0005] There are two types of Pub / Sub communication models: broker type and brokerless type. A broker type configuration is one in which a function called a broker, which is responsible for the properties of spatial separation, temporal separation, and asynchronous processing, is placed between Pub and Sub. A brokerless type configuration is a distributed configuration in which all nodes (Pub and Sub) have the functions to handle the properties of spatial separation, temporal separation, and asynchronous processing. The above brokerless type configuration can be realized by deploying a function called DDS (Data Distribution Service) in each node. The Pub / Sub communication model is also called a publish / subscribe model. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] What's in the DDS Standard, Internet<URL:https: / / www.dds-foundation.org / omg-dds-standard / > Summary of the Invention [Problem to be solved by the invention]

[0007] In a communication system that uses DDS for pub / sub communication, the basic functions of DDS make it possible to make pubs redundant. For example, it is possible to switch which of multiple pubs in a redundant configuration is treated as the prioritized pub (hereinafter referred to as the priority pub).

[0008] However, for example, for some reason, the priority pub may not actually be switched as expected. For this reason, it is desirable to check in advance that the priority pub will be switched as expected.

[0009] The present invention has been made in consideration of the above-mentioned points, and has an object to provide a technique for inspecting a redundant configuration on the Pub side in a communication system performing Pub / Sub communication. [Means for solving the problem]

[0010] According to the disclosed technology, there is provided a communication system for performing communication among a plurality of nodes using a brokerless publish / subscribe model, comprising: an inspection management unit that receives an inspection instruction for one application that is given priority on the subscriber side among one or more applications that are redundantly configured on one or more of the nodes and function as a publisher; an inspection instruction output unit that inspects whether an application that is given priority on the subscriber side is switched to another application different from the one application among the one or more applications by injecting an abnormality into the one application; A communication system is provided having the following: Effect of the Invention

[0011] According to the disclosed technology, a technology is provided for inspecting a redundant configuration on the Pub side in a communication system performing Pub / Sub communication. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a diagram for explaining Pub / Sub communication using DDS. [Diagram 2] FIG. 1 is a diagram illustrating an example of a system configuration in which a DDS is incorporated. [Diagram 3] FIG. 1 is a diagram illustrating an example of the configuration of a system having a plurality of nodes. [Figure 4] FIG. 1 is a diagram for explaining an overview of an embodiment. [Diagram 5] FIG. 1 is a diagram illustrating an example of a system configuration in an embodiment. [Figure 6] FIG. 1 is a diagram for explaining configuration management. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of a configuration management unit in the embodiment. [Figure 8] FIG. 4 is a diagram illustrating a configuration example of a handling unit in the embodiment. [Figure 9] FIG. 2 is a diagram showing a configuration example of a DDS operation function unit in the embodiment. [Figure 10] FIG. 1 is a diagram showing a processing flow in an embodiment. [Figure 11] FIG. 2 illustrates an example of a hardware configuration of the apparatus. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of the present invention (the present embodiment) will be described with reference to the drawings. The embodiment described below is merely an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0014] In the embodiment described below, an example of applying the present invention to a communication system performing Pub / Sub communication using DDS will be described, but the present invention can be applied to systems other than Pub / Sub communication using DDS.

[0015] (About Pub / Sub communication using DDS) First, the DDS that is the premise of this embodiment and Pub / Sub communication using the DDS will be described.

[0016] In this embodiment, the above-mentioned brokerless type configuration is adopted, and the brokerless type is realized by the DDS assuming the function equivalent to the broker.

[0017] Here, we will explain the delivery range management in DDS. In DDS, a delivery network is added to the network interface of the node. The delivery range set by the user operates with this delivery network and a filter inside DDS, enabling the sending and receiving of appropriate data to applications that function as Pub or Sub.

[0018] Specifically, based on the data bus and the delivery range set by the user, DDS assigns multicast addresses to the network interfaces available within the node and prepares a delivery network. When specifying the delivery range, it is also possible to set whether to distribute by unicast using the node's existing IP address or to use a newly assigned multicast address, making it possible to determine the physical data distribution range.

[0019] An example of a delivery range is shown in Figure 1. In the example in Figure 1, domain A and domain B are set as the delivery range. Furthermore, within domain A, a delivery range for topic [I] and a delivery range for topic [Ro] are set. Furthermore, within the delivery range of topic [I], a delivery range for key [II] is set.

[0020] (Example of a system configuration incorporating DDS) DDS is a program that functions as middleware in a node (which may be called a computer, a communications device, etc.). The basic processing programs required for communications in DDS are provided as a library. By using this library, a DDS program can be generated from a data definition file for generating communications programs that has as parameters the definitions (type, size, name, QoS, etc.) of the data sent by the application (written as "APP"). The generation of DDS itself is an existing technology.

[0021] Figure 2 is a diagram showing an example of a system configuration in which a DDS is built in. Figure 2 shows a configuration in which, physically, multiple nodes (computers) to which sensors and control valves are connected are connected to a logical bus-type network.

[0022] Sensors are connected to nodes 1 and 2, and an APP that generates the data to be published and a DDS are installed. Control valves are connected to nodes 2 and 3, and an APP that utilizes the subscribed data and a DDS are installed.

[0023] The example in Figure 2 shows a Pub / Sub configuration with redundant QoS settings achieved by using DDS. Specifically, the DDS in node 1 configures the main Pub and the sub Pub 1, and the DDS in node 2 configures the sub Pub 2. The DDS in node 3 configures the Sub 1 and Sub 2, and the DDS in node 4 configures the Sub 3.

[0024] In the example shown in Figure 2, the APP is written in Python and the DDS is written in C++, but these are just examples and any programming language may be used. When changing the Pub / Sub configuration, some things, such as QoS, can be changed dynamically, while others require a process restart (including program modifications).

[0025] Hereinafter, an example will be described as an example of the technology according to the present embodiment.

[0026] (Example of the system configuration that serves as the basis for this embodiment) Next, an example of a communication system that is the base of this embodiment will be described. In the communication system that is the base of this embodiment, one node may belong to multiple domains. Also, one node may have multiple Pub / Sub. Note that Pub here is an application that generates data to be published, and Sub is an application that utilizes subscribed data. Functions related to Pub / Sub communication are handled by DDS.

[0027] In addition, both Pub / Sub may exist in one node, and Pub / Sub across multiple domains may exist in one node. In addition, multiple Pubs or multiple Subs may exist in one APP. Furthermore, each Pubs and each Sub in the same APP are identifiable. In addition, in the communication system in this embodiment, communication is in plain text.

[0028] An example of the configuration of a communication system that is the base of this embodiment is shown in Fig. 3. As shown in Fig. 3, this communication system includes nodes 10 to 18, L2SWs (Layer 2 switches) 20 and 21, an L3SW (Layer 3 switch) 30, a packet analysis device 40, and a detection unit 50.

[0029] In the example of Figure 3, nodes 10, 11, 12, 15, 16, and 17 belong to domain D1, and nodes 12, 13, 17, and 18 belong to domain D2. The domain to which the node belongs is indicated, for example, D1 for "DDS_D1" of node 10. Nodes 12 and 17 belong to both domain D1 and domain D2.

[0030] For example, in node 10, "Pub1 (APP I)" is an application that publishes data for topic [I], and functions as Pub1 (Publisher 1) in Pub / Sub communication. In node 10, there are two Pubs, Pub1 (APP I) and Pub2 (APP I). This indicates that although there is only one APP, it functions as two Pubs due to the functionality of the DDS. The same is true for Sub, as shown in node 15.

[0031] In addition, node 11 has both a Pub and a Sub, i.e., Pub 3 and Sub 4. Nodes 12 and 14 have multiple APPs functioning as multiple Pubs, and nodes 17 and 18 have multiple APPs functioning as multiple Subs.

[0032] 3, Pub1 (APP I) to Pub4 (APP I) exist, and the Pub in "APP I" is made redundant. Similarly, Pub5 (APP Ro) to Pub6 (APP Ro) exist, and the Pub in "APP Ro" is also made redundant.

[0033] Furthermore, the L3SW 30 is connected to the Internet 55, and each node can communicate with the Internet 55. Furthermore, a packet analysis device 40 is connected to the L2SWs 20 and 21, and a detection unit 50 can detect anomalies based on the packet analysis results.

[0034] (Outline of this embodiment) For example, consider a case where a certain topic is redundantly created with three pubs, 1st Pub, 2nd Pub, and 3rd Pub, and each of the 1st to 3rd Subs treats the 1st Pub as the priority pub. In this case, data is delivered to each Sub from each of the 1st to 3rd Pub, but only data delivered from the 1st Pub is passed to the Sub's APP.

[0035] In this embodiment, if an abnormality occurs in the first Pub, each Sub can switch the priority Pub to the second Pub or the third Pub. An abnormality includes not only a Pub failure, but also, for example, a case where the Pub is taken over by a third party and sends data with illegal contents (for example, data intended to attack the Sub) or is in an illegal state.

[0036] Figure 4 shows how the above-mentioned priority pub switching occurs. In the example of Figure 4, it shows how the priority pub switches to the third pub when an abnormality occurs in the first pub, which is the priority pub. With this switching, data delivered from the third pub is passed to the APP in each Sub.

[0037] In this embodiment, a mechanism is provided that can check whether the priority pub is switched correctly by inserting a pseudo-abnormality, etc. This makes it possible to prevent the occurrence of situations such as "a redundant configuration was thought to be set up, but the priority pub did not switch when an actual abnormality occurred."

[0038] (System Configuration Example in This Embodiment) Fig. 5 shows an example of the configuration of a communication system in this embodiment. As shown in Fig. 5, in the base communication system shown in Fig. 3, each node is provided with a DDS operation function unit, and also has a configuration management unit 60 and a handling unit 70. The DDS operation function unit realizes a function of switching the priority pub in response to an instruction from the handling unit 70. Fig. 5 shows an example in which nodes 10 to 18 are provided with DDS operation function units 101 to 109, respectively. Hereinafter, when there is no need to distinguish between nodes, they will be referred to as DDS operation function unit 100.

[0039] The configuration management unit 60 manages configuration information (network configuration information) of the communication system, and the countermeasure unit 70 executes a priority pub switching inspection in response to an inspection instruction. Although the detection unit 50 is present in the example of FIG. 5, the detection unit 50 is not required when inspecting the priority pub switching. In actual operation, the priority pub is switched in response to an abnormality detected by the detection unit 50. The detection unit 50, the configuration management unit 60, and the countermeasure unit 70 may be included in the packet analysis device 40, or may be included in a device different from the packet analysis device 40. In this embodiment, it is assumed that the packet analysis device 40 includes the detection unit 50, the configuration management unit 60, and the countermeasure unit 70.

[0040] (About configuration management) To perform a priority pub switching inspection, configuration information of the communication system must be managed. This is because it is necessary to specify the inspection points on the communication system (for example, a pub that generates a pseudo anomaly). While such configuration information may be created and managed by any method, in this embodiment, the configuration information is created and managed by combining multiple pieces of relationship information that can be created from the communication (traffic) flowing between nodes.

[0041] As relationship information, three layers are created: an "IP relationship layer," a "participant relationship layer," and a "Pub / Sub relationship layer," which represent the topology of the horizontal axis of the network. The IP relationship layer and the participant relationship layer are related, and the participant relationship layer and the Pub / Sub relationship layer are related, so all three layers are related in the end, and by combining these three layers, a "composite layer" is obtained that represents the topology of the vertical axis of the network. Configuration information is managed by retaining multiple generations of this composite layer. Note that a generation refers to a division, for example, at a certain time division or event division. However, it is not necessary to retain multiple generations, and for example, only the most recent generation may be retained.

[0042] FIG. 6 shows examples of the IP relationship layer, the participant relationship layer, the Pub / Sub relationship layer, and the composition layer. As shown in FIG. 6, the IP relationship layer is represented by a graph structure with IP addresses as vertices and data transmission / reception relationships at the IP level as branches. In the IP relationship layer, if there is a branch between vertices, it indicates that there is a data transmission / reception relationship between the nodes having the IP addresses represented by the vertices. Note that one node may have multiple IP addresses (for example, in addition to an IP address for unicast, it may have an IP address for multicast). The participant relationship layer represents the GUID held by a node with one symbol (a triangle or an inverted triangle symbol), and each symbol represents the domain to which each GUID belongs and whether it is a Pub or Sub. The Pub / Sub relationship layer represents the GUID held by a node with vertices, and the relationship of whether it belongs to the same topic as a branch, and indicates the relationship of the topics to which each GUID belongs. Note that the participant relationship layer is also represented by a graph structure with the above symbols (a triangle or an inverted triangle symbol) as vertices. In the example of FIG. 6, there are no branches in the graph structure representing the participant relationship layer, but for example, vertices belonging to the same domain may be represented by connecting them with branches.

[0043] The Pub / Sub relationship layer can be created with information obtained from communication as data distribution, and the participant relationship layer can be created with information obtained from communication for DDS operation. On the other hand, the IP relationship layer can be created with information obtained from both communication as data distribution and communication for DDS operation. Note that communication for DDS operation refers to communication when a node participates in Pub / Sub communication, communication when searching for other nodes, communication when agreeing on distribution content, etc.

[0044] In the IP relationship layer, one vertex is associated with a 5-tuple (src / dst IP addresses, src / dst port numbers, protocol number) that contains the IP address of the node. In the participant relationship layer, one symbol (triangle or inverted triangle symbol) is associated with a GUID and a port number. In the Pub / Sub relationship layer, one vertex is associated with a GUID and a topic name. A GUID is an identifier used in DDS, and is generated from an IP address, port number, etc. Note that one node may have multiple GUIDs (for example, when one node functions as both a Pub and Sub, or when one node belongs to multiple domains or multiple topics).

[0045] Therefore, it is possible to associate the IP-related layer and the participant-related layer with a port number, and it is possible to associate the participant-related layer and the Pub / Sub-related layer with a GUID. By synthesizing the three layers through these associations, a synthesized layer is obtained as the network configuration information of the communication system that performs Pub / Sub communication. This synthesized layer is retained, for example, for multiple generations.

[0046] Here, when focusing on a certain node in the composition layer, this node corresponds to one or more vertices (5 tuples including an IP address) in the IP relationship layer, and one or more vertices (port number and GUID) in the participant relationship layer are associated with each of these one or more vertices. Also, zero or more vertices (GUID and topic name) in the Pub / Sub relationship layer are associated with each of the one or more vertices in the participant relationship layer. That is, in the composition layer, for each node, a tree structure with the node as the vertex (a tree structure with the IP address at the top layer, the port number at the next layer, the GUID at the next layer, and the topic name at the last layer) is obtained, and this tree structure represents the vertical axis topology.

[0047] (Example of configuration of each part in this embodiment) In this embodiment, a mechanism is provided that can check whether the priority pub is switched correctly by inserting pseudo-anomalies into the test points using the above configuration information.

[0048] Fig. 7 shows an example of the configuration of the configuration management unit 60. As shown in Fig. 7, the configuration management unit 60 has a visualization unit 610 and a relationship recording unit 620. At least one generation of configuration information (IP relationship layer, participant relationship layer, Pub / Sub relationship layer, and composition layer) is recorded in the relationship recording unit 620. It is assumed that the configuration information is created in advance and recorded in the relationship recording unit 620. The operation of each of these units will be described in the sequence section described later.

[0049] Fig. 8 shows an example of the configuration of the handling unit 70. As shown in Fig. 8, the handling unit 70 has an inspection management unit 710, an inspection instruction output unit 720, and an inspection list recording unit 730. The operation of each of these units will be described in the sequence section described later.

[0050] Fig. 9 shows an example of the configuration of the DDS operation function unit 100. As shown in Fig. 9, the DDS operation function unit 100 has a switching unit 110. The operation of the switching unit 110 will be explained in the sequence section described later.

[0051] In this embodiment, each of the above-mentioned units checks whether the priority Pub is switched correctly by inserting pseudo abnormalities at the check points.

[0052] (Example of sequence in this embodiment) Next, an example of the operation of the communication system in this embodiment will be described with reference to the sequence diagram of FIG.

[0053] The inspection management unit 710 requests the visualization unit 610 to check the configuration of the communication system (S101). In response to this configuration check, the visualization unit 610 searches for current configuration information (i.e., the latest generation configuration information) from the relationship recording unit 620, and acquires the configuration information as the search result (S102 to S103). The visualization unit 610 then creates visualization information of the acquired configuration information, and presents it to the inspection management unit 710 (S104 to S105). The visualization information is information for visually displaying the communication system configuration represented by the configuration information, for example, on a display. This allows the user to check the communication system configuration (i.e., Pub / Sub data transmission / reception relationships, domains to which the information belongs, topics, Pub redundancy configuration, etc.).

[0054] The inspection management unit 710 searches the inspection list from the inspection list recording unit 730, and obtains the inspection list as the search result (S106 to S107). The inspection list is a list of inspection locations that can be inspected. Such an inspection list can be created based on the system design specifications, or based on information extracted from communication information before the inspection is performed, but in this embodiment, the method of creation is not limited, and it is sufficient if the list is created in advance. Note that the inspection location is represented by a set of, for example, the ID and name of the priority pub to be inspected, the domain to which it belongs, the topic, QoS information, and the IP address of the node that has this pub.

[0055] Thereafter, the inspection management unit 710 waits for an instruction of an inspection point to be inspected (S108). For example, a user can determine which Pub to inspect from the visualized configuration information and the inspection list.

[0056] When the user or the like designates an inspection location and issues an inspection instruction, and the inspection management unit 710 accepts the designation, the inspection management unit 710 transmits an inspection instruction request for the inspection location to the inspection instruction output unit 720 (S109 to S110). The inspection location designated here is the priority Pub in which an abnormality is deemed to have occurred. In addition, when issuing an inspection instruction, an inspection type (for example, "stop" indicating that the Pub has stopped, or "modify" indicating that the settings of the Pub have been changed) may be designated, and if the inspection type is "modify", the change content may be designated. For example, if an inspection is to be performed when the Pub has stopped due to a malfunction or the like, the inspection type "stop" is designated, and if an inspection is to be performed when the Pub has been taken over by a third party and is sending unauthorized data or is in an unauthorized state, the inspection type "modify" is designated, and the change content is designated to indicate sending unauthorized data or an unauthorized state.

[0057] To give a specific example of an invalid state, let us say that the pub of a certain node belongs to topic "I" in domain A and is sending temperature data, which is the normal state. In this case, if the pub of the node is modified to belong to domain B, this pub can be said to be in an invalid state.

[0058] However, the above inspection types are merely examples, and various types of inspections may be possible. For example, there may be an inspection type that performs an inspection when a new Pub participates in Pub / Sub communication.

[0059] When the inspection instruction output unit 720 receives an inspection instruction request, it searches the inspection list recording unit 730 for a command (hereinafter, inspection command) for switching the priority pub from the inspection location pub to another pub (hereinafter, switching destination pub), and obtains the inspection command as the search result (S111 to S112). The switching destination pub is determined from among pubs that have a redundant configuration with the inspection location pub, and at this time, one pub may be determined in advance, or may be determined according to some rule. In addition, the inspection command is recorded in the inspection list recording unit 730 in advance, but the inspection command may be searched and obtained according to the inspection type, or the inspection command may be searched and obtained according to the inspection target pub, its belonging domain, topic, etc. in addition to the inspection type.

[0060] Next, the inspection instruction output unit 720 transmits the inspection command to the switching unit 110 (S113). The inspection instruction output unit 720 transmits the inspection command to both the switching unit 110 of the switching destination Pub and the Sub that receives data from the switching destination Pub. However, the contents of the inspection command may be different between the switching destination Pub and the Sub that receives data from the switching destination Pub.

[0061] Then, when the switching unit 110 receives the above inspection command, it executes the inspection command to the DDS (S114). At this time, it also restarts the process if necessary. This checks whether the priority pub is switched from the inspection target pub (current priority pub) to the switching destination pub.

[0062] (Hardware configuration example) A node having a DDS operation function unit 100 in this embodiment, and a packet analysis device 40 having a detection unit 50, a configuration management unit 60, and a response unit 70 can be realized, for example, by having a computer execute a program that describes the processing contents described in this embodiment.

[0063] The above program can be recorded on a computer-readable recording medium (such as a portable memory) and can be stored or distributed. The above program can also be provided via a network such as the Internet or e-mail.

[0064] Fig. 11 is a diagram showing an example of the hardware configuration of the computer. The computer in Fig. 11 includes a drive device 1000, an auxiliary storage device 1002, a memory device 1003, a CPU 1004, an interface device 1005, a display device 1006, an input device 1007, an output device 1008, and the like, all of which are interconnected via a bus B.

[0065] The program for realizing the processing on the computer is provided by a recording medium 1001 such as a CD-ROM or a memory card. When the recording medium 1001 storing the program is set in the drive device 1000, the program is installed from the recording medium 1001 to the auxiliary storage device 1002 via the drive device 1000. However, the program does not necessarily have to be installed from the recording medium 1001, but may be downloaded from another computer via a network. The auxiliary storage device 1002 stores the installed program as well as necessary files, data, etc.

[0066] The memory device 1003 reads out and stores the program from the auxiliary storage device 1002 when an instruction to start the program is received. The CPU 1004 realizes the functions related to each of the above-mentioned parts according to the program stored in the memory device 1003. The interface device 1005 is used as an interface for connecting to a network. The display device 1006 displays a GUI (Graphical User Interface) by a program. The input device 1007 is composed of a keyboard and mouse, buttons, a touch panel, or the like, and is used to input various operation instructions. The output device 1008 outputs the calculation results. Note that the node or packet analysis device 40 may not include either or both of the display device 1006 and the input device 1007.

[0067] (Effects of the embodiment) According to the technique of the present embodiment, it is possible to inspect the redundant configuration on the Pub side in a communication system performing Pub / Sub communication.

[0068] (Summary of the embodiment) This specification discloses at least the following communication system, inspection device, inspection method, and program. (Section 1) A communication system for communicating among a plurality of nodes using a brokerless publish / subscribe model, comprising: an inspection management unit that receives an inspection instruction for one application that is given priority on the subscriber side among one or more applications that are redundantly configured on one or more of the nodes and function as a publisher; an inspection instruction output unit that inspects whether an application that is given priority on the subscriber side is switched to another application different from the one application among the one or more applications by injecting an abnormality into the one application; A communication system having the above configuration. (Section 2) The inspection management unit includes: 2. The communication system according to claim 1, further comprising: presenting configuration information indicating a network configuration of the communication system and a pre-created inspection list to a user; and accepting an inspection instruction for the one application from the user. (Section 3) The configuration information is 3. The communication system of claim 2, wherein the system uses first relationship information representing the relationship between the nodes regarding the sending and receiving of the communication, second relationship information representing the relationship between the nodes regarding the domain to which the node belongs and whether the node is the publisher or subscriber, and third relationship information representing the relationship between the nodes regarding the topics to be published and subscribed to, and associates the first relationship information and the second relationship information by IP addresses and port numbers, and associates the second relationship information and the third relationship information by an identifier used in the publish / subscribe model. (Section 4) A test device connected to a plurality of nodes that communicate using a brokerless publish / subscribe model, comprising: an inspection management unit that receives an inspection instruction for one application that is given priority on the subscriber side among one or more applications that are redundantly configured on one or more of the nodes and function as a publisher; an inspection instruction output unit that inspects whether an application that is given priority on the subscriber side is switched to another application different from the one application among the one or more applications by injecting an abnormality into the one application; An inspection device having the above structure. (Section 5) The inspection management unit includes: 5. The inspection device according to claim 4, which presents configuration information representing a network configuration of a communication system composed of the plurality of nodes and a pre-created inspection list to a user, and accepts an inspection instruction for the one application from the user. (Section 6) The configuration information is 6. The inspection device described in claim 5, wherein the inspection device uses first relationship information that represents the relationship between the nodes regarding the sending and receiving of the communication, second relationship information that represents the relationship between the nodes regarding the domain to which the nodes belong and whether they are the publisher or subscriber, and third relationship information that represents the relationship between the nodes regarding the topics to be published and subscribed to, and associates the first relationship information and the second relationship information by IP addresses and port numbers, and associates the second relationship information and the third relationship information by an identifier used in the publish / subscribe model. (Section 7) A test device connected to multiple nodes communicating via a brokerless publish / subscribe model. a test management step of receiving a test instruction for one of the one or more applications that are redundantly configured on one or more of the nodes and function as a publishing side, the one or more applications being given priority on the subscribing side; a test instruction output step of testing whether an application that is given priority on the subscriber side is switched to another application different from the one application among the one or more applications by injecting an anomaly into the one application; The inspection method to be performed. (Section 8) A program for causing a computer to function as the inspection device according to any one of claims 4 to 6.

[0069] Although the present embodiment has been described above, the present invention is not limited to such a specific embodiment, and various modifications and variations are possible within the scope of the gist of the present invention described in the claims. [Explanation of symbols]

[0070] 10~18 nodes 20, 21 L2SW 30 L3SW 40 Packet Analysis Device 50 Detection unit 55 Internet 60 Configuration Management Department 70 Response Department 100 DDS operation function section 110 Switching section 610 Visualization section 620 Relationship Record Section 710 Inspection Management Department 720 Inspection Instruction Output Unit 730 Inspection List Recording Section 1000 Drive Device 1001 Recording media 1002 Auxiliary storage 1003 Memory device 1004 CPU 1005 Interface device 1006 Display device 1007 Input Device 1008 Output device

Claims

1. A communication system for communicating among a plurality of nodes using a brokerless publish / subscribe model, comprising: an inspection management unit that, among the one or more applications that are redundantly provided on the one or more nodes and function as publishing sides, assumes that an abnormality has occurred in one application that is given priority on the subscribing side, and receives an inspection instruction for the one application; an inspection instruction output unit that transmits to the node an inspection command for switching an application that is given priority on the subscriber side to another application different from the one application among the one or more applications based on the inspection instruction; A communication system having the above configuration.

2. The inspection management unit includes:

2. The communication system according to claim 1, further comprising: presenting configuration information indicating a network configuration of the communication system and a previously created inspection list to a user; and accepting an inspection instruction for the one application from the user.

3. The configuration information is 3. The communication system of claim 2, wherein the first relationship information and the second relationship information are associated by IP addresses and port numbers using first relationship information representing the relationship between the nodes regarding the sending and receiving of the communication, second relationship information representing the relationship between the nodes regarding the domain to which the nodes belong and whether they are the publisher or the subscriber, and third relationship information representing the relationship between the nodes regarding the topics to be published and subscribed to, and the second relationship information and the third relationship information are associated by identifiers used in the publish / subscribe model.

4. 1. A testing device connected to a plurality of nodes communicating in a brokerless publish / subscribe model, comprising: an inspection management unit that, among the one or more applications that are redundantly provided on the one or more nodes and function as publishing sides, assumes that an abnormality has occurred in one application that is given priority on the subscribing side, and receives an inspection instruction for the one application; an inspection instruction output unit that transmits to the node an inspection command for switching an application that is given priority on the subscriber side to another application different from the one application among the one or more applications based on the inspection instruction; An inspection device having the above structure.

5. The inspection management unit includes:

5. The inspection device according to claim 4, further comprising: a user-presenting configuration information indicating a network configuration of the communication system constituted by the plurality of nodes and a pre-created inspection list; and a user-presenting an inspection instruction for the one application from the user.

6. The configuration information is 6. The inspection device of claim 5, wherein the inspection device uses first relationship information representing the relationship between the nodes regarding the sending and receiving of the communication, second relationship information representing the relationship between the nodes regarding the domain to which the nodes belong and whether they are the publisher or the subscriber, and third relationship information representing the relationship between the nodes regarding the topics to be published and subscribed to, and associates the first relationship information with the second relationship information by IP addresses and port numbers, and associates the second relationship information with the third relationship information by an identifier used in the publish / subscribe model.

7. A test device connected to multiple nodes communicating via a brokerless publish / subscribe model, an inspection management procedure for accepting an inspection instruction for one application, which is one or more applications that are redundantly provided on one or more of the nodes and function as a publishing side, assuming that an abnormality has occurred in one application that is given priority on the subscribing side; and an inspection instruction output procedure for transmitting an inspection command to the node based on the inspection instruction, for switching an application that is given priority on the subscriber side to another application, different from the one application, among the one or more applications; The inspection method to be performed.

8. A program for causing a computer to function as the inspection device according to any one of claims 4 to 6.

Citation Information

Patent Citations

  • Communications device utilizing central discovery mechanism, and individual method

    JP2015043208A

  • Server apparatus, information sharing system, information sharing method and program

    JP2015232820A

  • Message control system, message control device, message control method, and program

    WO2014203728A1