JP5927983B2 - Event collection method, event collection program, and information processing apparatus - Google Patents

Description

  The present invention relates to an event collection method, an event collection program, and an information processing apparatus.

  A sensor network that collects sensing data sensed by a sensor node as an event is known. Various services such as alert transmission and device control are provided according to events collected by the server node via the sensor network.

  As described above, when the event from the sensor node is collected by the server node, all the events are concentrated and notified to the server node. For this reason, the load on the server node increases, and the network bandwidth becomes tight as the network traffic increases.

  As an example of a technique for suppressing the load on the server node and the network traffic, the following technique has been proposed. An example is a system that improves system performance and / or resource consumption by transferring a filter agent that filters data from a consuming node to a data producing node. As another example, there is a sensor network system in which a script is nested and a part of the script is executed by an intermediate node or a sensor node which is a lower node.

JP 2008-97603 A JP 2006-344017 A

  By the way, as an example of a technique for suppressing the load on the server node and the network traffic, the following technique can be considered. In other words, event collection paths are determined according to the event occurrence status and sensor network topology, and modules for processing events are distributed to lower nodes such as intermediate nodes and sensor nodes based on the collection paths. Technology can be considered as an example.

  However, in order to realize the above-described devised technique, it is necessary to construct a network topology. However, the topology is not always constructed every time the network path is changed, such as addition or deletion of nodes. . For this reason, in the above devised technology, there is a case where a module cannot be appropriately deployed according to a change in the network path.

  The disclosed technique has been made in view of the above, and an object thereof is to provide an event collection method, an event collection program, and an information processing apparatus capable of appropriately deploying a module according to a change in a network path. To do.

An event collection method disclosed in the present application is an event collection method executed by a computer, and in one aspect, receives route information related to a route of the network from a plurality of nodes connected to the network. The event collection method generates connection information between the plurality of nodes based on the received route information. In addition, the event collection method may be configured such that when an event is transmitted between nodes indicated by the generated connection information, the module that processes the event is assigned an attribute corresponding to an attribute defined in the module among the plurality of nodes. It is determined whether or not the node can be deployed. Further, in the event collection method, if the module can be deployed in the node, the event transmission destination set for each of the plurality of nodes is changed to a node indicated by the estimated connection information, and the node Deploy the module to

  According to one aspect of the technology disclosed in the present application, there is an effect that modules can be appropriately deployed according to a change in a network path.

FIG. 1 is a diagram illustrating a system configuration of the sensor network system according to the first embodiment. FIG. 2 is a block diagram illustrating a functional configuration of the server node according to the first embodiment. FIG. 3 is a diagram illustrating a configuration example of information stored in the module storage unit. FIG. 4 is a diagram illustrating a configuration example of information stored in the module definition storage unit. FIG. 5 is a diagram illustrating a configuration example of information stored in the route information storage unit. FIG. 6 is a diagram illustrating a configuration example of information stored in the topology storage unit. FIG. 7 is a diagram illustrating a configuration example of information stored in the event storage unit. FIG. 8 is a diagram illustrating a configuration example of information stored in the generated event information storage unit. FIG. 9 is a diagram illustrating a configuration example of information stored in the deployment destination information storage unit. FIG. 10 is a diagram illustrating a transition of the deployment status from the deployment destination information storage unit illustrated in FIG. 9. FIG. 11 is a diagram illustrating a transition of the deployment status from the deployment destination information storage unit illustrated in FIG. FIG. 12 is a diagram illustrating an example of a route change in the sensor network illustrated in FIG. FIG. 13 is a diagram illustrating a transition of route information from the route information storage unit illustrated in FIG. 5. FIG. 14 is a diagram showing the transition of the topology from the topology storage unit shown in FIG. FIG. 15 is a diagram illustrating a transition of the deployment status from the deployment destination information storage unit illustrated in FIG. 11. FIG. 16 is a block diagram illustrating a functional configuration of the sensor node according to the first embodiment. FIG. 17 is a block diagram illustrating a functional configuration of the GW node according to the first embodiment. FIG. 18 is a flowchart of an overall process procedure in the sensor node according to the first embodiment. FIG. 19 is a flowchart illustrating the procedure of module deployment processing according to the first embodiment. FIG. 20 is a flowchart illustrating the procedure of module deployment processing according to the first embodiment. FIG. 21 is a block diagram illustrating a functional configuration of a server node according to the second embodiment. FIG. 22 is a block diagram illustrating a functional configuration of the sensor node according to the second embodiment. FIG. 23 is a block diagram illustrating a functional configuration of a GW node according to the second embodiment. FIG. 24 is a flowchart illustrating an overall process procedure in the sensor node according to the second embodiment. FIG. 25 is a flowchart illustrating a procedure of module deployment processing according to the second embodiment. FIG. 26 is a flowchart illustrating a procedure of module deployment processing according to the second embodiment. FIG. 27 is a diagram illustrating a configuration example of information stored in the route information storage unit. FIG. 28 is a diagram illustrating an example of a computer that executes an event collection program.

  Hereinafter, embodiments of an event collection method, an event collection program, and an information processing apparatus disclosed in the present application will be described in detail based on the drawings. Note that this embodiment does not limit the disclosed technology. Each embodiment can be appropriately combined within a range in which processing contents are not contradictory.

[System configuration]
First, the system configuration of the sensor network system according to the present embodiment will be described. FIG. 1 is a diagram illustrating a system configuration of the sensor network system according to the first embodiment. The sensor network system 1 shown in FIG. 1 collects sensing data sensed by the sensor node 210 as an event, and provides various services according to the collected event.

  As shown in FIG. 1, the sensor network system 1 accommodates a server node 110, sensor nodes 210X-1, 210X-2, 210Y-1 and 210Y-2, and routers 10X, 10Y and 10Z. In the example of FIG. 1, event data is collected from the sensor nodes 210X-1 and 210X-2 accommodated in the X family network under the router 10X to the server node 110 via the routers 10X and 10Z. In the example of FIG. 1, event data is collected from the sensor nodes 210Y-1 and 210Y-2 accommodated in the network of the Y family under the router 10Y to the server node 110 via the routers 10Y and 10Z. Hereinafter, the sensor nodes 210X-1, 210X-2, 210Y-1, and 210Y-2 are collectively referred to as “sensor node 210” when they are collectively referred to. In addition, the routers 10X, 10Y, and 10Z are collectively referred to as “router 10” without distinction.

  The server node 110, the sensor node 210, and the router 10 are connected via the network 5 so that they can communicate with each other. As an example of the network 5, there is a communication network such as the Internet, a LAN (Local Area Network), and a VPN (Virtual Private Network) regardless of wired or wireless. Note that the numbers of sensor nodes 210 and routers 10 are not limited to the example of FIG. 1, and can be applied to cases where an arbitrary number of sensor nodes 210 and routers 10 are accommodated.

  Among these, the router 10 is a device that connects different networks and relays communication. As an example, the router 10 connects networks such as LAN and LAN, LAN and VPN, and relays communication. In the example of FIG. 1, the sensor network includes a plurality of subnets separated by the router 10. That is, the sensor network includes an “X house network” that is a subnet delimited by the router 10X and a “Y house network” that is a subnet delimited by the router Y. In the sensor network, there is a “Z area network” that is a subnet separated by the router 10Z above the X house network and the Y house network, and a “cloud network” that is a subnet above the router 10Z. To do.

  The sensor node 210 is a communication terminal with a sensor. Examples of the sensor node 210 include various devices such as personal computers, peripheral devices, audio devices, mobile phones, PHS (Personal Handyphone System) mobile terminals, and home appliances. Moreover, as one aspect | mode of the sensor mounted in the sensor node 210, environmental sensors, such as a temperature sensor which measures temperature, a humidity sensor which measures humidity, and a temperature / humidity sensor which measures temperature and humidity, are mentioned. Although an environmental sensor is illustrated here as an example of a sensor mounted on the sensor node 210, an arbitrary sensor such as a GPS (Global Positioning System) sensor, an acceleration sensor, or a gyro sensor can be mounted on the sensor node 210.

  The server node 110 is a server device that functions as a root node of the sensor network and provides various services according to events. As an aspect, the server node 110 distributes the event by disposing a module that executes processing of the event received from the sensor node 210 in a node positioned lower than the own device. Such a module incorporates an event filtering process and an aggregation process that trigger a service providing process executed by the service providing application.

  Here, the server node 110 according to the present embodiment receives route information related to the route of the network from a plurality of nodes connected to the network. Further, the server node 110 according to the present embodiment generates connection information between a plurality of nodes based on the received route information. In addition, when an event is transmitted between nodes indicated by the generated connection information, the server node 110 according to the present embodiment can deploy a module for processing an event to one or a plurality of nodes among the plurality of nodes. It is determined whether or not. Further, the server node 110 according to the present embodiment changes the event transmission destination set for each of the plurality of nodes to the node indicated by the estimated connection information if the module can be deployed in the node. Deploy the module to the node.

  For this reason, the server node 110 according to the present embodiment can appropriately deploy modules according to addition or deletion of nodes. Therefore, according to the server node 110 according to the present embodiment, the module can be appropriately arranged in the node on the sensor network, and as a result, the traffic on the sensor network can be suppressed following the network configuration change. Furthermore, since the modules are distributed in the server node 110 according to this embodiment, it is possible to prevent the load from being concentrated on the server node 110.

  In the example of FIG. 1, the sensor node 210 is illustrated as a lower node of the server node 110. However, as described later, the GW node that relays communication between the sensor node 210 and the server node 110 is the server node 110. It may be included as a lower node. Hereinafter, the sensor nodes 210 other than the server node 110 that is the root node and the GW node 310 described later are collectively referred to as “lower nodes”.

  In the example of FIG. 1, it is assumed that the IP address “192.168.100.x” is assigned to the router 10 and the host included in the X area network. As an example, “192.168.100.1” is assigned to the router 10X, “192.168.100.201” is assigned to the sensor node 210X-1, and “192.168.100.10” is assigned to the sensor node 210X-2. .202 "are assigned. Further, it is assumed that the IP address “192.168.101.x” is assigned to the router 10 and the host included in the Y area network. As an example, “192.168.101.1” is assigned to the router 10Y, “192.168.101.203” is assigned to the sensor node 210Y-1, and “192.168.101” is assigned to the sensor node 210Y-2. .204 "are assigned. Further, it is assumed that the IP address “192.168.10.x” is assigned to the router 10 and the host included in the Z area network. As an example, “192.168.10.1” is assigned to the router 10Z, “192.168.10.2” is assigned to the router 10X, and “192.168.10.3” is assigned to the router 10Y. It has been. In addition, it is assumed that the IP address “192.168.1.x” is assigned to the router 10 and the host included in the cloud network. As an example, “192.168.1.10” is assigned to the server node 110 and “192.168.1.1” is assigned to the router 10Z. It is assumed that the “host” mentioned here includes the server node 110 to which an IP address is assigned.

[Server node configuration]
Subsequently, a functional configuration of the server node according to the present embodiment will be described. FIG. 2 is a block diagram illustrating a functional configuration of the server node 110 according to the first embodiment. The server node 110 has functions of various functional units included in a known server device, for example, various input devices and audio output devices, in addition to the functional units illustrated in FIG.

  As shown in FIG. 2, the server node 110 includes a module registration unit 111, a module storage unit 111A, a module definition storage unit 111B, a route information reception unit 112, a route information storage unit 112A, and a topology generation unit 113. And a topology storage unit 113A. Further, the server node 110 includes an event reception unit 114, an event storage unit 114A, a module execution unit 115, an occurrence event registration unit 116, and an occurrence event information storage unit 116A. Further, the server node 110 includes a deployment destination information storage unit 117A, a deployment destination determination unit 117, a transmission destination information transmission unit 118, and a module transmission unit 119.

  The module registration unit 111 is a processing unit that registers a module. As one aspect, the module registration unit 111 accepts an upload of a module programmed by a module developer to filter or aggregate events that trigger various service providing processes. Then, the module registration unit 111 registers the module uploaded to the server node 110 in a module storage unit 111A described later. Further, the module registration unit 111 accepts definitions relating to the uploaded modules via a terminal device used by the developer, and registers the accepted definitions relating to the modules in a module definition storage unit 111B described later.

  The module storage unit 111A is a storage unit that stores modules. As an example, in the module storage unit 111A, when a module is uploaded, the module registration unit 111 registers the module. As another example, the module storage unit 111A is referred to by a module transmission unit 119 described later when modules are deployed in lower nodes such as the sensor node 210 and a GW node 310 described later.

  As an aspect, the module storage unit 111A stores data in which a module identifier and a binary code are associated with each other. The “module identifier” here refers to an identifier for identifying a module. For example, a function name is given to a module programmed in C language, or a class name is given to a module programmed in Java (registered trademark) language, depending on the programming language used for development. An identifier can be assigned. The “binary code” refers to compiled binary data that is a module body.

  FIG. 3 is a diagram illustrating a configuration example of information stored in the module storage unit 111A. In the example of FIG. 3, the module identifier “discomfort index calculation” and its binary code are associated with each other. This “discomfort index calculation” refers to the class name of the module that calculates the discomfort index from temperature and humidity. When this “discomfort index calculation” is deployed to a lower node, events transmitted from the lower node to the server node 110 are aggregated.

  In the example of FIG. 3, the case where the binary code of the module is stored is illustrated, but it is not always necessary to store the module in the binary format, and data other than the binary format may be stored. For example, when the module is a script language, text data in which the script is described may be stored. Also, the source code before compilation may be stored. In this case, the module may be compiled at the stage where the module is deployed to a lower node such as the sensor node 210, or may be compiled at the deployment destination lower node.

  The module definition storage unit 111B is a storage unit that stores definitions related to modules. As an example, the module definition storage unit 111B registers the definition of the module by the module registration unit 111 when the definition regarding the module is uploaded together with the module. As another example, the module definition storage unit 111B is referred to by a later-described deployment destination determining unit 117 in order to determine a module deployment destination.

  As an aspect, the module definition storage unit 111B stores data in which a module identifier, an input event type, an output event type, and an aggregate attribute name are associated. Here, the “input event type” refers to an event type that becomes an input of processing executed by the module. The “output event type” refers to an event type that is an output of the process executed by the module. The “aggregated attribute name” refers to the name of an aggregate attribute that is a framework for aggregating a plurality of nodes.

  FIG. 4 is a diagram illustrating a configuration example of information stored in the module definition storage unit 111B. The example of the module identifier “discomfort index calculation” shown in FIG. 4 indicates that a temperature event and a humidity event are input and a discomfort index event is output. In the case of this “discomfort index calculation”, a temperature event and a humidity event are input in one process, and the temperature sensed by the sensor node 210 housed in the same house is targeted. A house ID is given.

  The route information receiving unit 112 is a processing unit that receives route information of the sensor network from lower nodes including the sensor node 210 and a GW node 310 described later. As one aspect, the route information receiving unit 112 receives route information indicating what kind of router 10 or host passes from each lower node to the server node 110. Then, the route information receiving unit 112 registers the route information of the sensor network received from the lower node in the route information storage unit 112A described later. Note that the route information received by the route information receiving unit 112 is acquired, for example, by executing a command called “traceroute” that designates the server node 110 as a destination at each node. By executing this “traceroute”, the IP address and the number of hops of the router 10 and the host passing from each node to the server node 110 are acquired as route information. The traceroute is also referred to as “tracert”, for example.

  The route information storage unit 112A is a storage unit that stores route information of the sensor network. As an example, the route information storage unit 112A registers the route information by the route information receiving unit 112 when the route information of the sensor network is received from the lower node. As another example, the route information storage unit 112A is referred to by a topology generation unit 113 described later in order to generate a topology.

  As an aspect, the route information storage unit 112A stores data in which a transmission source node ID, the number of hops, and an IP address are associated. The “transmission source node ID” here refers to an identifier for identifying a node that is a transmission source of route information. The “hop number” indicates the number of routers existing on the route from the source node to the router 10 and the host to which the corresponding IP address is assigned. The “IP address” indicates an IP address assigned to the router 10 and the host that passes from the transmission source node to the server node 110.

  FIG. 5 is a diagram illustrating a configuration example of information stored in the route information storage unit 112A. In the example of FIG. 5, the sensor node 210X-1 illustrated in FIG. 1 is the temperature sensor X housed in the X house, and the sensor node 210X-2 is the humidity sensor X housed in the X house. The sensor node 210Y-1 is a temperature sensor Y housed in the Y house, and the sensor node 210Y-2 is a humidity sensor Y housed in the Y house. In the example illustrated in FIG. 5, the IP address assigned to the first router 10 or host that passes from the sensor node 210X-1 that is the temperature sensor X to the server node 110 that is the cloud is “192.168.100.1. ". The IP address “192.168.100.1” is an IP address assigned to the router 10X in the example shown in FIG.

  The topology generation unit 113 is a processing unit that generates connection information between a plurality of nodes in the sensor network, that is, a so-called topology. As an example, when the route information storage unit 112A is updated, that is, when there is a change in the route information of the network, the topology generation unit 113 connects to which upper node each lower node based on the route information. The connection information between the nodes indicating whether or not the connection is made is generated. Then, topology generation unit 113 stores the generated connection information between nodes in topology storage unit 113A described later.

  As an aspect, the topology generation unit 113 refers to the route information storage unit 112A, determines the upper node of each node based on whether or not each node passes through the same route, and connection information between the nodes. Is stored in the topology storage unit 113A described later as a topology. For example, the topology generation unit 113 selects one source node ID stored in the route information storage unit 112A. Then, topology generation unit 113 specifies a node associated with the same IP address as the IP address associated with the selected node. Here, when a plurality of IP addresses are specified for the same node, the topology generation unit 113 specifies an IP address associated with a smaller hop number among the specified IP addresses. Further, when a plurality of nodes are specified, the topology generation unit 113 specifies a node associated with a smaller hop number among the selected nodes. In addition, the topology generation unit 113 generates connection information between the nodes with the selected node as a lower node and the identified node as an upper node, and stores the generated connection information as a topology in a later-described topology storage unit 113A. .

  In the example illustrated in FIG. 5, the topology generation unit 113 first selects “temperature sensor X”. Then, the topology generation unit 113 identifies “cloud” associated with the same IP address as the IP address “192.168.1.10” associated with “temperature sensor X”. For this reason, the topology generation unit 113 identifies “cloud” as the upper node of the lower node “temperature sensor X”. Similarly, for other nodes, the topology generation unit 113 generates a topology by specifying an upper node.

  The topology storage unit 113A is a storage unit that stores the topology of the sensor network. As an example, in the topology storage unit 113A, connection information between nodes is registered as a topology by the topology generation unit 113. As another example, the topology storage unit 113A is referred to by a later-described deployment destination determination unit 117 in order to determine a module deployment destination.

  As an aspect, the topology storage unit 113A stores data in which a lower node ID and an upper node ID are associated with each other. The “lower node ID” here refers to an identifier for identifying a lower node. The “upper node ID” indicates an identifier for identifying an upper node connected to the lower node.

  FIG. 6 is a diagram illustrating a configuration example of information stored in the topology storage unit 113A. In the example of FIG. 3, the upper nodes of the temperature sensor X, the humidity sensor X, the temperature sensor Y, and the humidity sensor Y are all server nodes 110 that are clouds, and between the sensor node 210 and the server node 110, such as the GW node 310 Indicates that no relay node is present.

  The event receiving unit 114 is a processing unit that receives an event. As one aspect, when receiving an event from a lower node such as the sensor node 210 or a GW node 310 described later, the event receiving unit 114 stores the event in an event storage unit 114A described later. At this time, the event receiving unit 114 also outputs the event received from the lower node to the generated event registration unit 116 described later. Note that the event reception unit 114 does not necessarily receive an unprocessed event sensed by the sensor node 210, and the processed event is generated by executing a process by a module deployed in a lower node. It may be received.

  The event storage unit 114A is a storage unit that stores events. The event storage unit 114A is provided to refer to a service providing application that provides a service with the occurrence of an event as a trigger.

  For example, in the event storage unit 114A, when an event is received from a lower node, the event reception unit 114 registers the event. As another example, in the event storage unit 114A, when an event is processed by a module, an event after execution of processing is registered by a module execution unit 115 described later.

  As an aspect, the event storage unit 114A stores data in which an event type name, an event occurrence time, and an event attribute are associated. The “event type” here refers to an identifier for identifying the type of event. “Event occurrence time” refers to the time when an event occurs, that is, the time sensed by the sensor node 210. “Event attribute” refers to the nature and origin of the event. For example, the “event attribute” is a set of attribute data such as sensing data collected as an event or the type of data processed by the event, an occurrence node where the event has occurred, and an aggregation attribute that aggregates a plurality of nodes including the occurrence node. Point to. In the following, a case where each attribute data included in the event attribute includes a pair of attribute name and attribute value is shown.

  FIG. 7 is a diagram illustrating a configuration example of information stored in the event storage unit 114A. The first record shown in FIG. 7 shows an event that a temperature of 28 degrees is measured by the temperature sensor X of the X family at 12:00 on July 13, 2011. The second record shown in FIG. 7 shows an event in which 50% humidity is measured by the X house humidity sensor X at 12:00:10 on July 13, 2011. The third record shown in FIG. 7 shows an event that a temperature of 30 degrees was measured by the temperature sensor Y of the Y family at 12:00:20 on July 13, 2011. The fourth record shown in FIG. 7 indicates an event in which 70% humidity is measured by the humidity sensor Y of the Y house at 12:00:30 on July 13, 2011.

  As described above, the event stored in the event storage unit 114A is referred to as a trigger for executing the service providing process by the service providing application. In the example of FIG. 7, an unprocessed event sensed by the sensor node 210 is illustrated. However, when a module is deployed in a lower node, a new event processed by the module is also stored. become.

  The module execution unit 115 is a processing unit that performs execution control of modules deployed in the server node 110. As one aspect, when an event is received by the event reception unit 114, the module execution unit 115 determines whether or not a module that uses the received event as an input event type is deployed in the server node 110. At this time, when the module is deployed in the server node 110, the module execution unit 115 executes event processing by executing the module. Thereafter, the module execution unit 115 stores the data processed by the module as a new event in the event storage unit 114A.

  The occurrence event registration unit 116 is a processing unit that registers an occurrence event that has occurred in a lower node such as the sensor node 210 or the GW node 310. As an aspect, when the event reception unit 114 receives an event, the occurrence event registration unit 116 determines whether or not the received event has already been registered in the event generation information storage unit 116A described later as an occurrence event. judge. At this time, if the occurrence event registration unit 116 has not yet been registered as the occurrence event, the occurrence event registration unit 116 registers the event received from the lower node in the occurrence event information storage unit 116A described later.

  The occurrence event information storage unit 116A is a storage unit that stores information related to the occurrence event. The generated event information storage unit 116A is provided for managing what event is occurring in a lower node such as the sensor node 210 or the GW node 310.

  As an example, in the occurrence event information storage unit 116A, when an event is received from a lower node, the occurrence event registration unit 116 registers the occurrence event. As another example, the occurrence event information storage unit 116A is referred to by a later-described deployment destination determining unit 117 in order to determine a module deployment destination.

  As one aspect, the generated event information storage unit 116A stores data in which a generated node ID, a generated event type, and a generated event attribute are associated with each other. The “occurrence node ID” here refers to an identifier for identifying the occurrence node. The “occurrence event type” indicates an identifier for identifying the type of the occurrence event. The “occurrence event attribute” indicates an attribute of the occurrence event.

  FIG. 8 is a diagram illustrating a configuration example of information stored in the generated event information storage unit 116A. The first record shown in FIG. 8 indicates that an event occurs in which the temperature is measured by the temperature sensor X of the X family. Further, the second record shown in FIG. 8 indicates that an event occurs in which humidity is measured by the humidity sensor X of the X family. The third record shown in FIG. 8 indicates that an event occurs in which the temperature is measured by the temperature sensor Y of the Y family. The fourth record shown in FIG. 8 indicates that an event occurs in which humidity is measured by the humidity sensor Y of the Y house. In the example of FIG. 8, an unprocessed event sensed by the sensor node 210 is exemplified as an occurrence event. However, when a module is deployed in a lower node, a new event processed by the module also occurs. Stored as an event.

  The deployment destination information storage unit 117A is a storage unit that stores information regarding the deployment destination of the module. As an example, the deployment destination information storage unit 117A is accessed by a deployment destination determination unit 117 described later when the topology of the sensor network has changed.

  As an aspect, the deployment destination information storage unit 117A stores data in which a module identifier, an input event type, an aggregate attribute name, a generated event attribute, a generated node ID, and a deployment destination node ID are associated. The “deployment destination node ID” here refers to an identifier for identifying a sensor node 210 on which a module is deployed, a GW node 310 or a server node 110 described later.

  FIG. 9 is a diagram illustrating a configuration example of information stored in the deployment destination information storage unit 117A. The example of FIG. 9 illustrates an example of a table at a stage where a change in the topology of the sensor network is detected and determination of a module deployment destination by a deployment destination determination unit 117 described later is started. That is, as shown in FIG. 9, a table example at the stage where the module identifier, the input event type, and the aggregate attribute name among all the columns are copied from the module definition storage unit 111B is illustrated. The transition in which the remaining columns including the subsequent deployment destination node ID are filled will be described later with reference to FIGS.

  The deployment destination determination unit 117 is a processing unit that determines a module deployment destination. As one aspect, the deployment destination determination unit 117 executes the process described below when the topology storage unit 113A is updated, that is, when the topology of the sensor network has changed.

  Explaining this, the deployment destination determination unit 117 stores the column data of the module identifier, the input event type, and the aggregate attribute name in the corresponding column of the deployment destination information storage unit 117A among the module definitions stored in the module definition storage unit 111B. Write. At this time, in the deployment destination information storage unit 117A, as shown in FIG. 9, the columns of the occurrence event attribute, the occurrence node ID, and the deployment destination node ID are blank.

  Subsequently, the deployment destination determining unit 117 extracts the generated node ID included in the input event type of the module in which the generated event type is not deployed from the generated node IDs stored in the generated event information storage unit 116A. Further, the deployment destination determination unit 117 extracts nodes having the same attribute value belonging to the same aggregate attribute as the attribute name of the aggregate attribute defined in the undeployed module among the generated node IDs extracted as described above. . Thereafter, the deployment destination determination unit 117 writes the generated node ID obtained as the extraction result and the generated event attribute associated with the generated node ID in the deployment destination information storage unit 117A.

  At this time, the deployment destination determination unit 117 executes the following process when a plurality of generated node IDs are registered in the deployment destination information storage unit 117A. That is, the deployment destination determination unit 117 accommodates all the sensor nodes 210 or GW nodes 310 described later as lower nodes among the upper node IDs stored in the topology storage unit 113A, and the lowest node. The node ID that is the side is extracted. Then, the deployment destination determination unit 117 registers the extracted node ID in the column of the deployment destination node ID as described above.

  Further, when one occurrence node ID is registered in the deployment destination information storage unit 117A, the deployment destination determination unit 117 has no room for selection in the node on which the module is deployed, and is thus obtained as an extraction result first. The generated node ID is registered in the column of the deployment destination node ID.

  When the deployment destination node ID is registered in the deployment destination information storage unit 117A in this way, the module stored in the module storage unit 111A is transmitted to the node corresponding to the deployment destination node ID by the module transmission unit 119 described later. .

  Thereafter, the deployment destination determination unit 117 waits until the occurrence event newly acquired from the lower node by the module deployment is updated in the occurrence event information storage unit 116A, and then deploys the module until there is no undeployed module. Repeatedly.

  As another aspect, the deployment destination determination unit 117 may execute the following process when the topology storage unit 113A is updated, that is, when the topology of the sensor network has changed. That is, the deployment destination determination unit 117 may re-evaluate the deployment destination node ID when the deployment destination node ID registered last time is stored in the deployment destination information storage unit 117A. As an example, the deployment destination determination unit 117 extracts the generated node ID included in the input event type of the module in which the generated event type is not deployed from the generated node IDs stored in the generated event information storage unit 116A. Further, the deployment destination determination unit 117 extracts nodes having the same attribute value belonging to the same aggregate attribute as the attribute name of the aggregate attribute defined in the undeployed module among the generated node IDs extracted as described above. . Thereafter, when the node ID obtained as the extraction result is different from the previously registered deployment destination node ID, the deployment destination determination unit 117 sets the obtained node ID as a new deployment destination node ID, and the deployment destination information storage unit Register at 117A. When the deployment destination node ID is registered in the deployment destination information storage unit 117A in this way, the module stored in the module storage unit 111A is transmitted to the node corresponding to the deployment destination node ID by the module transmission unit 119 described later. .

  In addition, when no occurrence node ID is registered in the deployment destination information storage unit 117A, there is a possibility that the occurrence event notified from the lower node is not completely registered in the occurrence event information storage unit 116A. In this case, the deployment destination determination unit 117 waits until the occurrence event information storage unit 116A is updated, and then repeatedly executes module deployment.

  The transmission destination information transmission unit 118 is a processing unit that transmits transmission destination information to lower nodes such as the sensor node 210 or a GW node 310 described later. As an aspect, when the deployment destination determination unit 117 registers the deployment destination node ID in the deployment destination information storage unit 117A, the transmission destination information transmission unit 118 sets the node ID of the upper node of the registered deployment destination node ID. Read from the topology storage unit 113A. Then, the transmission destination information transmission unit 118 transmits the node ID of the read upper node to the node corresponding to the registered deployment node ID.

  The module transmission unit 119 is a processing unit that transmits a module to a lower node such as the sensor node 210 or a GW node 310 described later. As one aspect, when the deployment destination determination unit 117 registers the deployment destination node ID in the deployment destination information storage unit 117A, the module transmission unit 119 corresponds to the module stored in the module storage unit 111A with the deployment destination node ID. To the node to be

(1) Specific example 1 of module deployment
Here, the specific example 1 of module arrangement | positioning is demonstrated using FIGS. 9-11. FIG. 10 is a diagram showing a transition of the deployment status from the deployment destination information storage unit 117A illustrated in FIG. FIG. 11 is a diagram illustrating a transition of the deployment status from the deployment destination information storage unit 117A illustrated in FIG.

  When the module deployment is started, the generated event type and input event type columns are arranged between the generated event information storage unit 116A shown in FIG. 8 and the deployment destination information storage unit 117A shown in FIG. 117 is compared. At this time, the input event type “temperature” of the module “discomfort index calculation” matches the generation event type “temperature” of the generation node ID “temperature sensor X” and the generation node ID “temperature sensor Y”. Also, the input event type “humidity” of the module “discomfort index calculation” matches the generation event type “humidity” of the generation node ID “humidity sensor X” and generation node ID “humidity sensor Y”. Therefore, regarding the module “discomfort index calculation”, the four generation nodes of the generation node IDs “temperature sensor X”, “humidity sensor X”, “temperature sensor Y”, and “humidity sensor Y” are extracted by the deployment destination determination unit 117. The

  Here, a node having the same attribute value belonging to the same aggregate attribute as the attribute name of the aggregate attribute defined in the undeployed module among the four extracted nodes is extracted by the deployment destination determining unit 117.

  Since this module “discomfort index calculation” is a module that executes event aggregation processing, as shown in FIG. 4, the attribute name “house ID” of the aggregation attribute is defined in the module “discomfort index calculation”. On the other hand, the generation event attributes of the generation node IDs “temperature sensor X” and “humidity sensor X” are configured to include a pair of attribute name “house ID” and attribute value “X house” as shown in FIG. Attribute data for aggregated attributes. Further, the generation event attributes of the generation node IDs “temperature sensor Y” and “humidity sensor Y” are configured to include a pair of attribute name “house ID” and attribute value “Y house” as shown in FIG. Attribute data for aggregated attributes.

  The generation nodes of these generation node IDs “temperature sensor X”, “humidity sensor X”, “temperature sensor Y”, and “humidity sensor Y” all have the attribute name of the aggregate attribute “house ID”. On the other hand, the generation node IDs “temperature sensor X” and “humidity sensor X” are attribute values “X family” of the aggregate attribute, whereas the generation node IDs “temperature sensor Y” and “humidity sensor Y” are The attribute value of the aggregate attribute is “Y house”.

  Accordingly, the module “Calculation of discomfort index” is independently deployed as a module for X house and Y house. That is, as indicated by the shaded portion in FIG. 10, the module “discomfort index calculation” includes the generation node IDs “temperature sensor X” and “humidity sensor X” and the generation event attribute corresponding to the corresponding columns in the deployment destination information storage unit 117A. Is written to. Furthermore, as indicated by the shaded portion in FIG. 10, the module “discomfort index calculation” includes the generation node IDs “temperature sensor Y” and “humidity sensor Y” and the generation event attributes corresponding to the columns in the deployment destination information storage unit 117A. Is written to.

  Among these, the module “discomfort index calculation” for the X family has two generation nodes of generation node IDs “temperature sensor X” and “humidity sensor X”. For this reason, all the generation nodes of the generation node IDs “temperature sensor X” and “humidity sensor X” among the upper node IDs stored in the topology storage unit 113A shown in FIG. The node ID on the lower node side is extracted. In the example of FIG. 6, the generation nodes of the generation node IDs “temperature sensor X” and “humidity sensor X” are both connected to the server node 110 that is a cloud, and between the generation node and the server node 110. There are no relay nodes such as a GW node 310 described later. For this reason, “cloud” is stored in the column of the deployment destination node ID of the module “discomfort index calculation” for the X family, as in the shaded portion shown in FIG. As a result, the module “discomfort index calculation” for the X family is deployed in the server node 110.

  Similarly to the module “discomfort index calculation” for the X house, there are two generation nodes of the generation node ID “temperature sensor Y” and “humidity sensor Y” for the Y house module “discomfort index calculation”. For this reason, the module “uncomfortable” for the Y house is shown in the shaded portion in FIG. 11 by the same process as the process of storing “cloud” in the column of the deployment destination node ID of the module “discomfort index calculation” for the X house. “Cloud” is stored in the column of the deployment destination node ID of “index calculation”. As a result, the module “discomfort index calculation” for the Y family is deployed in the server node 110.

  Thus, the module “discomfort index calculation” for the X house and the module “calculation of discomfort index” for the Y house shown in FIG. 11 are deployed in the cloud. Thus, the temperature event and the humidity event are processed by the server node 110 that is a cloud.

(2) Specific example 2 of module deployment
Next, a specific example 2 of module deployment will be described with reference to FIGS. FIG. 12 is a diagram illustrating an example of a route change in the sensor network illustrated in FIG. FIG. 13 is a diagram illustrating a transition of route information from the route information storage unit illustrated in FIG. 5. FIG. 14 is a diagram showing the transition of the topology from the topology storage unit shown in FIG. FIG. 15 is a diagram illustrating a transition of the deployment status from the deployment destination information storage unit illustrated in FIG. 11.

  Compared to the sensor network system 1 shown in FIG. 1, the sensor network system 3 shown in FIG. 12 has a point that a GW node 310X is further added between the router 10X and the sensor nodes 210X-1 and 210X-2. Different. Furthermore, the sensor network system 3 is different in that a GW node 310Z is further added between the router 10Z, the router 10X, and the router 10Y.

  Thus, when the GW nodes 310X and 310Z are added, the route information of the sensor network changes. In the example of FIG. 13, compared with the example shown in FIG. 5, the route information indicating that three routers 10 or hosts pass from the GW node 310 </ b> X that is GW-X to the server node 110 that is the cloud. Have been added. Further, in the example of FIG. 13, compared to the example shown in FIG. 5, a route indicating that two routers 10 or hosts are routed from the GW node 310 </ b> Z that is the GW-Z to the server node 110 that is the cloud. Information has been added.

  As shown in FIG. 13, when the route information of the sensor network changes, the topology generation unit 113 generates a topology. That is, the topology shown in FIG. 6 is changed to the topology shown in FIG. 14 by specifying the upper nodes of the sensor node 210 and the GW node 310 by the topology generation unit 113.

  In the example illustrated in FIG. 13, “GW-X”, “GW-Z”, and “cloud” can be cited as nodes that can be upper nodes of the “temperature sensor X” that is the sensor node 210 </ b> X. Among these, the IP address associated with “GW-X” is the same as the IP address associated with “temperature sensor X”. Therefore, among these IP addresses, the router 10 through which the “temperature sensor X” and “GW-X” commonly pass the IP address “192.168.100.1” associated with the smaller hop number. Alternatively, the IP address of the host is specified. Further, the IP addresses “192.168.10.1” and “192.168.1.10” associated with “GW-Z” are both IP addresses associated with “temperature sensor X”. Match. For this reason, the router 10 through which the “temperature sensor X” and “GW-Z” commonly pass the IP address “192.168.10.1” associated with the smaller hop number among these IP addresses. Alternatively, the IP address of the host is specified. In addition, the IP address “192.168.1.10” associated with “Cloud” matches the IP address associated with “Temperature Sensor X”. For this reason, the IP address “192.168.1.10” is specified as the IP address of the router 10 or the host through which “temperature sensor X” and “cloud” pass in common.

  As described above, when three nodes “GW-X”, “GW-Z”, and “Cloud” are specified as the upper nodes passing through the same route as the “temperature sensor X”, An upper node passing through the same route on the lowest side is specified. In this case, “GW-X” is associated with the hop number “1” of “temperature sensor X”, and “GW-Z” is associated with the hop number “2” of “temperature sensor X”. “Cloud” is associated with the hop number “3” of “temperature sensor X”. Therefore, “GW-X” is specified as the upper node of the lower node “temperature sensor X”.

  Further, in the example illustrated in FIG. 13, “GW-X”, “GW-Z”, and “cloud” are listed as nodes that can be higher nodes of “humidity sensor X” that is the sensor node 210 </ b> X- 2. Among these, the IP address associated with “GW-X” is the same as the IP address associated with “humidity sensor X”. Therefore, among these IP addresses, the router 10 through which the “humidity sensor X” and “GW-X” commonly pass the IP address “192.168.100.1” associated with the smaller hop number. Alternatively, the IP address of the host is specified. Further, the IP addresses “192.168.10.1” and “192.168.1.10” associated with “GW-Z” are both IP addresses associated with “humidity sensor X”. Match. For this reason, the router 10 through which the “humidity sensor X” and “GW-Z” commonly pass the IP address “192.168.10.1” associated with a smaller hop number among these IP addresses. Alternatively, the IP address of the host is specified. Also, the IP address “192.168.1.10” associated with “Cloud” matches the IP address associated with “Humidity sensor X”. Therefore, the IP address “192.168.1.10” is specified as the IP address of the router 10 or the host through which “humidity sensor X” and “cloud” pass in common.

  As described above, when three nodes “GW-X”, “GW-Z”, and “Cloud” are specified as upper nodes passing through the same route as “humidity sensor X”, An upper node passing through the same route on the lowest side is specified. In this case, “GW-X” is associated with the hop number “1” of “humidity sensor X”, and “GW-Z” is associated with the hop number “2” of “humidity sensor X”. “Cloud” is associated with the hop number “3” of “humidity sensor X”. Therefore, “GW-X” is specified as the upper node of the lower node “humidity sensor X”.

  Further, in the example illustrated in FIG. 13, “GW-Z” and “cloud” may be cited as nodes that can be upper nodes of “temperature sensor Y” that is the sensor node 210 </ b> Y- 1. Among these, the IP addresses “192.168.10.1” and “192.168.1.10” associated with “GW-Z” are both IP addresses associated with “temperature sensor Y”. Matches. Therefore, among these IP addresses, the router 10 through which the “temperature sensor Y” and “GW-Z” commonly pass the IP address “192.168.10.1” associated with the smaller hop number. Alternatively, the IP address of the host is specified. Also, the IP address “192.168.1.10” associated with “Cloud” matches the IP address associated with “Temperature Sensor Y”. Therefore, the IP address “192.168.1.10” is specified as the IP address of the router 10 or the host through which “temperature sensor Y” and “cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as the upper nodes passing through the same route as “temperature sensor Y”, the same is given to the lowest side of these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “temperature sensor Y”, and “cloud” is associated with the hop number “3” of “temperature sensor Y”. . Therefore, “GW-Z” is specified as the upper node of the lower node “temperature sensor Y”.

  Further, in the example illustrated in FIG. 13, “GW-Z” and “cloud” are listed as nodes that can be higher nodes of “humidity sensor Y” that is the sensor node 210Y-2. Among these, the IP addresses “192.168.10.1” and “192.168.1.10” associated with “GW-Z” are both IP addresses associated with “humidity sensor Y”. Matches. Therefore, among these IP addresses, the router 10 through which the “humidity sensor Y” and “GW-Z” commonly pass the IP address “192.168.10.1” associated with the smaller hop number. Alternatively, the IP address of the host is specified. Further, the IP address “192.168.1.10” associated with “cloud” matches the IP address associated with “humidity sensor Y”. Therefore, the IP address “192.168.1.10” is specified as the IP address of the router 10 or the host through which “humidity sensor Y” and “cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as upper nodes passing through the same route as “humidity sensor Y”, the same is given to the lowest side of these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “humidity sensor Y”, and “cloud” is associated with the hop number “3” of “humidity sensor Y”. . Therefore, “GW-Z” is specified as the upper node of the lower node “humidity sensor Y”.

  Further, in the example illustrated in FIG. 13, “GW-Z” and “cloud” are listed as nodes that can be higher nodes of “GW-X” that is the GW node 310 </ b> X. Among these, the IP addresses “192.168.10.1” and “192.168.1.10” associated with “GW-Z” are both IP addresses associated with “GW-X”. Matches. Therefore, among these IP addresses, the router 10 through which the “GW-X” and “GW-Z” commonly pass the IP address “192.168.10.1” associated with the smaller hop number. Alternatively, the IP address of the host is specified. Also, the IP address “192.168.1.10” associated with “Cloud” matches the IP address associated with “GW-X”. For this reason, the IP address “192.168.1.10” is specified as the IP address of the router 10 or host through which “GW-X” and “Cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as the upper nodes passing through the same route as “GW-X”, the same is given to the lowest side among these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “humidity sensor Y”, and “cloud” is associated with the hop number “3” of “humidity sensor Y”. . Therefore, “GW-Z” is specified as an upper node of the lower node “GW-X”.

  In the example illustrated in FIG. 13, “cloud” is an example of a node that can be a higher node of “GW-Z” that is the GW node 310 </ b> Z. The IP address “192.168.1.10” associated with this “cloud” matches the IP address associated with “GW-Z”. For this reason, the IP address “192.168.1.10” is specified as the IP address of the router 10 or host through which “GW-Z” and “Cloud” pass in common. Therefore, “cloud” is specified as an upper node of the lower node “GW-Z”.

  In this way, the topology shown in FIG. 6 is changed to the topology shown in FIG. 14 by specifying the upper node of each lower node included in the sensor network system 3 by the topology generation unit 113.

  As shown in FIG. 14, when the topology of the sensor network changes, the deployed deployment destination node ID stored in the deployment destination information storage unit 117A of FIG. 11 is reevaluated. In the example of FIG. 11, the module “discomfort index calculation” for the X family has two generation nodes of generation node IDs “temperature sensor X” and “humidity sensor X”. For this reason, all the generation nodes of the generation node IDs “temperature sensor X” and “humidity sensor X” among the upper node IDs stored in the topology storage unit 113A shown in FIG. The node ID on the lower node side is extracted. In the example of FIG. 14, the generation nodes of the generation node IDs “temperature sensor X” and “humidity sensor X” are both connected to the GW node 310 that is GW-X. For this reason, “GW-X” is extracted as the deployment destination node ID of the module “discomfort index calculation” for the X family. Thus, since “GW-X” extracted as the deployment destination node ID this time is different from the previously registered deployment destination node ID “cloud”, “GW-X” as in the shaded portion shown in FIG. Is registered in the deployment destination information storage unit 117A as a deployment destination node ID for a new X house.

  Also, the module “discomfort index calculation” for the Y house has two generation nodes of the generation node IDs “temperature sensor Y” and “humidity sensor Y”, similarly to the module “discomfort index calculation” for the X house. In the example illustrated in FIG. 14, the generation nodes having the generation node IDs “temperature sensor Y” and “humidity sensor Y” are both connected to the GW node 310 </ b> Z that is GW-Z. For this reason, “GW-Z” is extracted as the deployment destination node ID of the module “discomfort index calculation” for the Y family. Thus, since “GW-Z” extracted as the deployment destination node ID this time is different from the previously registered deployment destination node ID “cloud”, “GW-Z” like the shaded portion shown in FIG. Is registered in the deployment information storage unit 117A as a new deployment node ID for the Y house.

  In this manner, the module “discomfort index calculation” for the X house shown in FIG. 15 is deployed in the GW-X, and the module “discomfort index calculation” for the Y house is deployed in the GW-Z. Further, the topology shown in FIG. 14 is applied to the sensor network. That is, for each node corresponding to the lower node ID shown in FIG. 14, the corresponding upper node ID is transmitted by the transmission destination information transmission unit 118 as transmission destination information. At this time, the module stored in the module storage unit 111A is also transmitted by the module transmission unit 119 to the node corresponding to the deployment destination node ID.

  Note that various integrated circuits and electronic circuits can be employed for the module registration unit 111, the path information reception unit 112, the topology generation unit 113, the event reception unit 114, and the module execution unit 115. In addition, various integrated circuits and electronic circuits can be adopted for the occurrence event registration unit 116, the deployment destination determination unit 117, the transmission destination information transmission unit 118, and the module transmission unit 119. For example, an ASIC (Application Specific Integrated Circuit) is an example of the integrated circuit. Examples of the electronic circuit include a central processing unit (CPU) and a micro processing unit (MPU).

  Further, the module storage unit 111A, the module definition storage unit 111B, the path information storage unit 112A, the topology storage unit 113A, the event storage unit 114A, the generated event information storage unit 116A, and the deployment destination information storage unit 117A include a semiconductor memory element and a storage device. The device can be adopted. For example, examples of the semiconductor memory element include a video random access memory (VRAM), a random access memory (RAM), and a flash memory. Examples of the storage device include storage devices such as a hard disk and an optical disk.

[Configuration of sensor node]
Next, the functional configuration of the sensor node according to the present embodiment will be described. FIG. 16 is a block diagram illustrating a functional configuration of the sensor node 210 according to the first embodiment. The sensor node 210 illustrated in FIG. 16 includes a sensor information reception unit 211, a module reception unit 212, a module execution unit 213, a transmission destination information reception unit 214, a transmission destination information storage unit 215, and an event transmission unit 216. Have. Further, the sensor node 210 illustrated in FIG. 16 includes a route information acquisition unit 217 and a route information transmission unit 218.

  The sensor information receiving unit 211 is a processing unit that receives sensor information from a sensor device built in or attached to the sensor node 210. As one aspect, when the sensor node 210 includes a temperature sensor, the sensor information receiving unit 211 receives the temperature measured by the temperature sensor. As another aspect, when the sensor node 210 includes a humidity sensor, the sensor information receiving unit 211 receives the humidity measured by the humidity sensor. When a plurality of sensor devices are built in the sensor node 210, a sensor information receiving unit 211 is provided corresponding to each sensor device.

  The module receiving unit 212 is a processing unit that receives a module from the server node 110. The module received by the module reception unit 212 is output to the module execution unit 213 that performs module execution control.

  The module execution unit 213 is a processing unit that performs execution control of modules deployed in the sensor node 210. As one aspect, when the sensor information is received by the sensor information receiving unit 211, the module execution unit 213 determines whether or not a module that uses the received sensor information as an input event type is deployed in the sensor node 210. judge. At this time, when the module is deployed in the sensor node 210, the module execution unit 213 executes event processing by executing the module. Thereafter, the module execution unit 213 outputs the data processed by the module to the event transmission unit 216 as a new event. If the module is not deployed in the sensor node 210, the sensor information is output to the event transmission unit 216 without being processed.

  The transmission destination information receiving unit 214 is a processing unit that receives transmission destination information from the server node 110. As an aspect, the transmission destination information reception unit 214 receives the node ID of the higher-order node that is the transmission destination of the event from the server node 110. Then, the transmission destination information reception unit 214 stores the received node ID of the higher order node in a transmission destination information storage unit 215 described later.

  The transmission destination information storage unit 215 is a storage unit that stores transmission destination information. As one aspect, the transmission destination information storage unit 215 stores the node ID of the higher-order node that is the transmission destination of the event. As another aspect, the transmission destination information storage unit 215 is referred to by an event transmission unit 216 described later in order to determine an upper node that is a transmission destination of an event.

  The event transmission unit 216 is a processing unit that transmits an event to an upper node. As an aspect, the event transmission unit 216 transmits the event processed by the module execution unit 213 or the sensor information received from the sensor device by the sensor information reception unit 211 to the upper node. At this time, when transmitting the sensor information to the upper node, the event transmission unit 216 collects the node ID of the sensor node 210 that is the generation node, the attribute name and attribute value of the aggregate attribute that aggregates a plurality of nodes including the own device. Is added to the sensor information. Then, the event transmission unit 216 refers to the transmission destination information storage unit 215 and determines an upper node that is the transmission destination of the event. After that, the event transmission unit 216 transmits an event including the node ID of the originating node and the aggregate attribute together with the sensor information to the upper node that is the transmission destination.

  Here, the attribute name and attribute value of the “aggregated attribute” can be incorporated into a device driver or the like at the manufacturing stage of the sensor node 210. For example, when the sensor device is a temperature sensor, a humidity sensor, or a temperature / humidity sensor, aggregate attributes such as “house ID”, “room ID”, and “floor ID”, which are a framework for measuring temperature and humidity, are included. Configure the device driver to add to the event. In addition, when the communication connection is established between the sensor node 210 and the server node 110, the attribute value of the house ID given prior to the other sensor nodes 210 that have already subscribed to the service is set as the server node. It can also be automatically acquired from 110. When the floor layout of the X house or the Y house is registered in the server node 110, the attribute value of the aggregate attribute such as “room ID” and “floor ID” in addition to “house ID” is set to the server node 110. Can also be obtained automatically.

  The route information acquisition unit 217 is a processing unit that acquires network route information. As an example, the route information acquisition unit 217 acquires route information representing the router 10 passing from the own node to the server node 110 at a predetermined timing. The route information acquisition unit 217 compares the acquired route information with the previously acquired route information, and determines whether the route information has changed. If there is a change in the route information, the route information acquisition unit 217 outputs the acquired route information to the route information transmission unit 218 described later.

  The route information transmission unit 218 is a processing unit that transmits the route information output from the route information acquisition unit 217 to the server node 110. As one aspect, the route information transmission unit 218 adds the node ID of the own node to the IP address of each relay device acquired by the route information acquisition unit 217 and the number of hops, and transmits the result to the server node 110.

[Configuration of GW node]
Next, a functional configuration of the GW node according to the present embodiment will be described. FIG. 17 is a block diagram illustrating a functional configuration of the GW node 310 according to the first embodiment. The GW node 310 illustrated in FIG. 17 includes an event reception unit 311, a module reception unit 312, a module execution unit 313, a transmission destination information reception unit 314, a transmission destination information storage unit 315, and an event transmission unit 316. . Furthermore, the GW node 310 illustrated in FIG. 17 includes a route information acquisition unit 317 and a route information transmission unit 318.

  The event receiving unit 311 is a processing unit that receives an event. As an aspect, the event reception unit 311 receives an event from the sensor node 210 or another GW node 310 that is a lower node.

  The module receiving unit 312 is a processing unit that receives a module from the server node 110. The module received by the module reception unit 312 is output to the module execution unit 313 that performs module execution control.

  The module execution unit 313 is a processing unit that performs execution control of modules deployed in the GW node 310. As one aspect, when an event is received by the event reception unit 311, the module execution unit 313 determines whether or not a module that uses the received event as an input event type is deployed in the GW node 310. At this time, when the module is deployed in the GW node 310, the module execution unit 313 executes event processing by executing the module. Thereafter, the module execution unit 313 outputs the data processed by the module to the event transmission unit 316 as a new event. If the module is not deployed in the GW node 310, the event is output to the event transmission unit 316 without being processed.

  The transmission destination information receiving unit 314 is a processing unit that receives transmission destination information from the server node 110. As an aspect, the transmission destination information reception unit 314 receives from the server node 110 the node ID of the upper node that is the transmission destination of the event. Then, the transmission destination information reception unit 314 stores the received node ID of the higher order node in a transmission destination information storage unit 315 described later.

  The transmission destination information storage unit 315 is a storage unit that stores transmission destination information. As an aspect, the transmission destination information storage unit 315 stores the node ID of a higher-order node that is an event transmission destination. As another aspect, the transmission destination information storage unit 315 is referred to by an event transmission unit 316 described later in order to determine an upper node that is a transmission destination of an event.

  The event transmission unit 316 is a processing unit that transmits an event to an upper node. As an aspect, the event transmission unit 316 transmits the event processed by the module execution unit 313 or the sensor information received from the sensor device by the event reception unit 311 to the upper node. At this time, when transmitting the sensor information to the upper node, the event transmission unit 316 collects the node ID of the sensor node 210 that is the generation node, the attribute name and attribute value of the aggregate attribute that aggregates a plurality of nodes including the own device. Is added to the sensor information. Then, the event transmission unit 316 refers to the transmission destination information storage unit 315 and determines an upper node that is the transmission destination of the event. After that, the event transmission unit 316 transmits an event including the node ID of the generation node and the aggregation attribute together with the sensor information to the upper node that is the transmission destination.

  The route information acquisition unit 317 is a processing unit that acquires network route information. As an example, the route information acquisition unit 317 acquires route information representing the router 10 passing from the own node to the server node 110 at a predetermined timing. The route information acquisition unit 317 compares the acquired route information with the previously acquired route information, and determines whether the route information has changed. If the route information is changed, the route information acquisition unit 317 outputs the acquired route information to the route information transmission unit 318 described later.

  As an aspect, the route information acquisition unit 317 executes a command “traceroute” that designates the server node 110 as a destination. As a result, the route information acquisition unit 317 acquires the IP address and the hop number of the router 10 that passes from the self node to the server node 110. The route information acquisition unit 317 compares the acquired IP address and hop number of each router 10 with the previously acquired IP address and hop number, and determines whether there is a change. If there is a change, the route information acquisition unit 317 outputs the acquired IP address and the number of hops to the route information transmission unit 318 described later. The traceroute is also referred to as “tracert”, for example.

  The route information transmission unit 318 is a processing unit that transmits the route information output from the route information acquisition unit 317 to the server node 110. As an aspect, the route information transmission unit 318 adds the node ID of the own node to the IP address of each relay device acquired by the route information acquisition unit 317 and the number of hops thereof, and transmits the result to the server node 110.

[Process flow]
Next, a processing flow of the sensor network system according to the present embodiment will be described. Here, after (1) the entire process executed by the sensor node 210 is described, the (2) module deployment process executed by the server node 110 will be described.

(1) Overall Processing FIG. 18 is a flowchart illustrating a procedure of overall processing in the sensor node 210 according to the first embodiment. This entire process is repeatedly executed as long as the power of the sensor node 210 is ON.

  As shown in FIG. 18, the sensor node 210 acquires network route information (step S101). Then, the sensor node 210 determines whether there is a change in the route information (step S102).

  If there is a change in the route information (Yes at Step S102), the sensor node 210 transmits the route information to the server node 110 (Step S103). If there is no change in the route information (No at Step S102), the sensor node 210 proceeds to the process at Step S104 without executing the process at Step S103.

  Subsequently, when the module is received from the server node 110 (Yes at Step S104), the sensor node 210 deploys the module received from the server node 110 (Step S105). If the module has not been received (No at Step S104), the process proceeds to Step S106 without executing Step S105.

  When the destination information is received from the server node 110 (Yes at Step S106), the sensor node 210 stores the received destination information in the destination information storage unit 215 (Step S107). If the destination information has not been received (No at Step S106), the process proceeds to Step S108 without executing Step S107.

  When sensor information is received from the sensor device (Yes at Step S108), the sensor node 210 determines whether or not a module that uses the received sensor information as an input event type is provided (Step S109). If sensor information has not been received (No at Step S108), the process returns to Step S101.

  If the module is deployed (Yes at step S109), the sensor node 210 processes the event by executing the module (step S110). Then, the sensor node 210 transmits the processed event to the higher order node (step S111).

  On the other hand, when the module is not deployed (No at Step S109), the sensor node 210 adds the generated node ID, the aggregation attribute, and the like to the sensor information received from the sensor device and transmits it to the upper node (Step S112). ).

  In this way, the sensor node 210 repeatedly executes the processes from step S101 to step S112 described above until the power is turned off.

  Here, the entire process of the sensor node 210 has been described, but the entire process executed by the GW node 310 as a relay node is the same except for a part. That is, the GW node 310 is the same as the sensor node 210 except that the event is received instead of the sensor information in step S108.

(2) Module Deployment Processing FIGS. 19 and 20 are flowcharts illustrating the module deployment processing procedure according to the first embodiment. For example, the module deployment process is started when the topology of the sensor network changes.

  As shown in FIG. 19, when route information is received from a lower node (Yes at Step S201), the server node 110 stores the received route information in the route information storage unit 112A (Step S202). Then, the server node 110 refers to the route information storage unit 112A, determines an upper node of each node based on whether or not each node passes through the same route, and later describes connection information between the nodes as a topology. Stored in the topology storage unit 113A (step S203). If route information is not received from the lower node (No at Step S201), the process proceeds to Step S208 in FIG.

  Subsequently, when the topology has changed (Yes at Step S204), the server node 110 re-evaluates the deployment destination node ID previously registered in the deployment destination information storage unit 117A (Step S205). When the deployment destination node ID is changed (Yes at Step S206), the server node 110 transmits the upper node ID corresponding to each node as transmission destination information based on the new topology (Step S207). ). At this time, the server node 110 transmits the module stored in the module storage unit 111A to the node corresponding to the deployment destination node ID. When there is no change in the topology (No at Step S204), the process proceeds to Step S208 in FIG. Also, when the deployment destination node ID is not changed (No at Step S206), the process proceeds to Step S208 in FIG.

  Subsequently, the server node 110 waits for the occurrence event information storage unit 116A to be updated (step S208). Then, when the occurrence event information storage unit 116A is updated, it is determined whether or not all the modules have been deployed (step S209). Here, since the process has not been completed for any module (No at Step S209), the process proceeds to Step S210.

  Subsequently, the server node 110 stores the column data of the module identifier, the input event type, and the aggregated attribute name among the module definitions stored in the module definition storage unit 111B in the corresponding column of the deployment destination information storage unit 117A (Step S110). S210).

  And the server node 110 performs the process of step S211 demonstrated below after performing the process of step S210. That is, the server node 110 extracts the occurrence node ID included in the input event type of the module in which the occurrence event type is not deployed from the occurrence node IDs stored in the occurrence event information storage unit 116A. Further, the server node 110 extracts nodes having the same attribute value belonging to the same aggregate attribute as the attribute name of the aggregate attribute defined in the undeployed module between the generated node IDs extracted as described above.

  Thereafter, the server node 110 writes the generated node ID obtained as an extraction result and the generated event attribute associated with the generated node ID in the deployment destination information storage unit 117A (step S212).

  At this time, if the number of generated node IDs is “0” (Yes in step S213), there is a possibility that the generated event notified from the lower node is not completely registered in the generated event information storage unit 116A. In this case, the process proceeds to step S201 in FIG.

  Here, when the number of generated node IDs is plural (Yes at Step S214), the process of Step S215 described below is executed. In other words, the server node 110 is a node that contains all of the sensor nodes 210 or GW nodes 310 corresponding to the generated node IDs as lower nodes among the upper node IDs stored in the topology storage unit 113A and is the lowest node side. Extract the ID. Then, the server node 110 registers the node ID extracted as described above in the column of the deployment destination node ID (step S216).

  If the number of generated node IDs is one (No in step S214), the server node 110 has no room for selection in the node on which the module is deployed, and therefore the generated node ID obtained as the extraction result first. Is registered in the column of the deployment destination node ID (step S216).

  Subsequently, the server node 110 transmits the module stored in the module storage unit 111A to the node corresponding to the deployment destination node ID (step S217), and returns to the process of step S201 in FIG.

  Thereafter, the server node 110 repeatedly executes the processes from step S201 to step S217 until the deployment of all modules is completed (No at step S209). Then, when the deployment of all the modules is completed (Yes at Step S209), the process is terminated.

[Effect of Example 1]
As described above, the server node 110 according to the present embodiment receives route information related to a network route from a plurality of nodes connected to the network. The server node 110 generates connection information between a plurality of nodes based on the received route information. When an event is transmitted between the nodes indicated by the generated connection information, the server node 110 determines whether or not a module for processing the event can be deployed in one or a plurality of nodes among the plurality of nodes. If the module can be deployed to the node, the server node 110 changes the event transmission destination set for each of the plurality of nodes to the node indicated by the generated connection information, and deploys the module to the node. For this reason, the server node 110 can appropriately deploy modules according to changes in the network path. Therefore, the server node 110 can suppress the traffic of the sensor network and can further prevent the load from being concentrated on the server node 110.

  By the way, in the first embodiment described above, an example has been described in which a topology is constructed when a new node is added to the sensor network, and a module is arranged in a lower node as much as possible. However, in the present invention, the node is deleted from the sensor network. It is also applicable to cases where Therefore, in the present embodiment, a method for generating a topology when a node is deleted from the sensor network and deploying modules to the lowest possible nodes will be described.

[Server node configuration]
FIG. 21 is a block diagram illustrating a functional configuration of the server node 120 according to the second embodiment. The server node 120 illustrated in FIG. 21 is different from the server node 110 illustrated in FIG. 2 in that it includes a survival information receiving unit 121 and a survival monitoring unit 122. In the following, functional units that exhibit the same functions as those in the first embodiment are denoted by the same reference numerals, and description thereof is omitted.

  The survival information reception unit 121 is a processing unit that receives survival information indicating that the transmission source node is in a communicable state from lower nodes such as the sensor node 220 and the GW node 320, for example. The survival information receiving unit 121 outputs the received survival information to the later-described survival monitoring unit 122.

  The survival monitoring unit 122 is a processing unit that monitors whether or not lower-level nodes are in a communicable state. As an example, the survival monitoring unit 122 includes an internal memory (not shown), and stores the reception time in the internal memory for each node ID of the transmission source node of the survival information received by the survival information receiving unit 121. Then, the survival monitoring unit 122 monitors whether there is a lower node for which the survival information is not received for a certain period of time, and if there is a lower node for which the survival information is not received for a certain period of time, the path information of the lower node is displayed as path information. Delete from storage unit 112A. Note that the method of monitoring the survival of the lower nodes by the survival monitoring unit 122 is not limited to the above method. For example, when the survival information received at a predetermined interval is not received, the survival information The route information of the source node may be deleted.

  As one aspect, the survival monitoring unit 122 deletes the route information received from the GW-X when the survival information from the GW-X is not received for a certain time or more. In the example illustrated in FIG. 13, the survival monitoring unit 122 uses the data associated with “GW-X”, “1”, and “192.168.100.1” on the 13th row, Delete up to data associated with “GW-X”, “3”, and “192.168.1.10”.

[Configuration of sensor node]
FIG. 22 is a block diagram illustrating a functional configuration of the sensor node 220 according to the second embodiment. The sensor node 220 illustrated in FIG. 22 is different from the sensor node 210 illustrated in FIG. 16 in that it further includes a survival information transmission unit 221.

  The survival information transmission unit 221 is a processing unit that transmits survival information. As one aspect, the survival information transmission unit 221 transmits survival information indicating that the own node is in a communicable state to the server node 120 at a predetermined timing.

[Configuration of GW node]
FIG. 23 is a block diagram illustrating a functional configuration of the GW node 320 according to the second embodiment. The GW node 320 illustrated in FIG. 23 is different from the GW node 310 illustrated in FIG. 17 in that it further includes a survival information transmission unit 321.

  The survival information transmission unit 321 is a processing unit that transmits survival information. As an aspect, the survival information transmission unit 321 transmits survival information indicating that the own node is in a communicable state to the server node 120 at a predetermined timing.

[Process flow]
Next, a processing flow of the sensor network system according to the present embodiment will be described. Here, after (1) the overall process executed by the sensor node 210 is described, the (2) module deployment process executed by the server node 120 will be described.

(1) Overall Processing FIG. 24 is a flowchart illustrating a procedure of overall processing in the sensor node 220 according to the second embodiment. This entire process is repeatedly executed as long as the power of the sensor node 220 is ON. Note that the overall process in the sensor node 220 shown in FIG. 24 is different from the overall process in the sensor node 210 shown in FIG.

  As shown in FIG. 24, the sensor node 220 transmits the survival information to the server node 120 (step S301). Subsequently, the sensor node 220 acquires network route information (step S101). Then, the sensor node 220 determines whether or not there is a change in the route information (Step S102).

  When there is a change in the route information (Yes at Step S102), the sensor node 220 transmits the route information to the server node 120 (Step S103). If there is no change in the route information (No at Step S102), the sensor node 220 proceeds to the process at Step S104 without executing the process at Step S103.

  Subsequently, when the module is received from the server node 120 (Yes at Step S104), the sensor node 220 deploys the module received from the server node 120 (Step S105). If the module has not been received (No at Step S104), the process proceeds to Step S106 without executing Step S105.

  If the destination information is received from the server node 120 (Yes at Step S106), the sensor node 220 stores the received destination information in the destination information storage unit 215 (Step S107). If the destination information has not been received (No at Step S106), the process proceeds to Step S108 without executing Step S107.

  When sensor information is received from the sensor device (Yes at Step S108), the sensor node 220 determines whether or not a module that uses the received sensor information as an input event type is deployed (Step S109). If sensor information is not received (No at Step S108), the process returns to Step S301.

  If the module is deployed (Yes at step S109), the sensor node 220 processes the event by executing the module (step S110). Then, the sensor node 220 transmits the processed event to the upper node (step S111).

  On the other hand, if the module is not deployed (No at Step S109), the sensor node 220 adds the generated node ID and the aggregate attribute to the sensor information received from the sensor device, and transmits it to the upper node (Step S112). ).

  In this way, the sensor node 220 repeatedly executes the processing from step S301 to step S112 described above until the power is turned off.

  Here, the entire process of the sensor node 220 has been described, but the entire process executed by the GW node 320 as a relay node is the same except for a part. That is, the GW node 320 is the same as the sensor node 220 except that the event is received instead of the sensor information in step S108.

(2) Module Deployment Processing FIGS. 25 and 26 are flowcharts illustrating the procedure of module deployment processing according to the second embodiment. For example, the module deployment process is started when the topology of the sensor network changes. Note that the module deployment process in the server node 120 shown in FIGS. 25 and 26 is further executed in steps S401 to S403 as compared to the module deployment process in the server node 110 shown in FIGS. Is different.

  As shown in FIG. 25, the server node 120 receives the survival information from lower nodes such as the sensor node 220 and the GW node 320 (step S401). If there is a lower node for which the survival information has not been received for a certain period of time (Yes in step S402), the server node 120 deletes the route information of the lower node from the route information storage unit 112A (step S403). If there is no lower node for which the survival information has not been received for a certain period of time (No at Step S402), the server node 120 proceeds to the process at Step S201 without executing the process at Step S403.

  Subsequently, when the path information is received from the lower node (Yes at Step S201), the server node 120 stores the received path information in the path information storage unit 112A (Step S202). Then, the server node 120 refers to the route information storage unit 112A, determines an upper node of each node based on whether or not each node passes through the same route, and later describes connection information between the nodes as a topology. Stored in the topology storage unit 113A (step S203). If route information is not received from the lower node (No at Step S201), the process proceeds to Step S208 in FIG.

  Subsequently, when there is a change in topology (Yes at Step S204), the server node 120 re-evaluates the deployment destination node ID previously registered in the deployment destination information storage unit 117A (Step S205). When the deployment destination node ID is changed (Yes at Step S206), the server node 120 transmits the upper node ID corresponding to each node as transmission destination information based on the new topology (Step S207). ). At this time, the server node 120 transmits the module stored in the module storage unit 111A to the node corresponding to the deployment destination node ID. When there is no change in the topology (No at Step S204), the process proceeds to Step S208 in FIG. In addition, when the deployment destination node ID is not changed (No at Step S206), the process proceeds to Step S208 in FIG.

  Subsequently, the server node 120 waits for the occurrence event information storage unit 116A to be updated (step S208). Then, when the occurrence event information storage unit 116A is updated, it is determined whether or not all the modules have been deployed (step S209). Here, since the process has not been completed for any module (No at Step S209), the process proceeds to Step S210.

  Subsequently, the server node 120 stores the column data of the module identifier, the input event type, and the aggregate attribute name among the module definitions stored in the module definition storage unit 111B in the corresponding column of the deployment destination information storage unit 117A (step S210).

  Then, after executing the process of step S210, the server node 120 executes the process of step S211 described below. That is, the server node 120 extracts the occurrence node ID included in the input event type of the module in which the occurrence event type is not deployed from the occurrence node IDs stored in the occurrence event information storage unit 116A. Further, the server node 120 extracts nodes having the same attribute value belonging to the same aggregate attribute as the attribute name of the aggregate attribute defined in the undeployed module between the generated node IDs extracted as described above.

  Thereafter, the server node 120 writes the generated node ID obtained as an extraction result and the generated event attribute associated with the generated node ID in the deployment destination information storage unit 117A (step S212).

  At this time, if the number of generated node IDs is “0” (Yes in step S213), there is a possibility that the generated event notified from the lower node is not completely registered in the generated event information storage unit 116A. In this case, the process proceeds to step S401 in FIG.

  Here, when the number of generated node IDs is plural (Yes at Step S214), the process of Step S215 described below is executed. In other words, the server node 120 is a node that contains all the sensor nodes 210 or GW nodes 310 corresponding to the respective generation node IDs as lower nodes among the upper node IDs stored in the topology storage unit 113A and is the lowest node side. Extract the ID. Then, the server node 120 registers the node ID extracted as described above in the column of the deployment destination node ID (step S216).

  If the number of occurrence node IDs is one (No in step S214), the server node 120 has no room for selection in the node where the module is deployed, and thus the occurrence node ID obtained as the extraction result first. Is registered in the column of the deployment destination node ID (step S216).

  Subsequently, the server node 120 transmits the module stored in the module storage unit 111A to the node corresponding to the deployment destination node ID (step S217), and returns to the process of step S401 in FIG.

  Thereafter, the server node 120 repeatedly executes the processes from step S401 to step S217 until the deployment of all the modules is completed (No at step S209). Then, when the deployment of all the modules is completed (Yes at Step S209), the process is terminated.

[Effect of Example 2]
As described above, the server node 120 according to the present embodiment monitors whether or not each of a plurality of nodes connected to the network is in a communicable state. The server node 120 then deletes the route information received from the node that has become unable to communicate when any of the nodes has become unable to communicate. Then, the server node 120 generates connection information between the plurality of nodes based on the route information from which the route information received from the node in the communication disabled state is deleted. Therefore, the server node 120 can appropriately deploy the module to the lower-level node even when the node is deleted from the sensor network.

  Although the embodiments of the present invention have been described so far, the present invention may be implemented in other embodiments besides the above-described embodiments. Therefore, other embodiments will be described below.

  In the above embodiment, the case where an IP address assigned in a certain LAN is used as route information has been described, but the present invention is not limited to this. For example, a plurality of addresses assigned to identify the router 10 and the host, such as a WAN (Wide Area Network) side IP address and a MAC (Media Access Control) address, may be used in combination. In such a case, for example, a combination of a plurality of addresses is stored in the route information storage unit 112A as route information.

  FIG. 27 is a diagram illustrating a configuration example of information stored in the route information storage unit. In the example illustrated in FIG. 27, the route information storage unit 112A stores data in which a transmission source node ID, the number of hops, an IP address, and a WAN-side IP address are associated with each other. As an example, this WAN-side IP address is detected when a lower node automatically recognizes an upper node using a UPnP (Universal Plug and Play) protocol or the like. As another example, the topology generation unit 113 refers to the generation of the topology.

  As an aspect, the topology generation unit 113 generates a topology by using a combination of an IP address and a WAN side IP address as route information. In the example illustrated in FIG. 27, “GW-X”, “GW-Z”, and “cloud” can be listed as nodes that can be upper nodes of “temperature sensor X”. Among these, the IP address “192.168.100.1” and the WAN side IP address “1.1.10.2” associated with the hop number “1” of “GW-X” are “temperature sensor X ”Matches the IP address and WAN side IP address associated with the hop number“ 1 ”. Therefore, the router 10 through which the “temperature sensor X” and “GW-X” commonly pass the IP address “192.168.100.1” and the WAN-side IP address “1.1.10.2” or It is specified as the IP address of the host. Also, the IP address “1.1.10.1” associated with the hop number “1” of “GW-Z” is the same as the IP address associated with the hop number “2” of “temperature sensor X”. Match. Therefore, the IP address “1.1.10.1” is specified as the IP address of the router 10 or the host through which “temperature sensor X” and “GW-Z” pass in common. Further, the IP address “1.1.1.10” associated with the “hop” “1” of “cloud” matches the IP address associated with the “hop” “3” of “temperature sensor X”. . Therefore, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “temperature sensor X” and “cloud” pass in common.

  As described above, when three nodes “GW-X”, “GW-Z”, and “Cloud” are specified as the upper nodes passing through the same route as the “temperature sensor X”, An upper node passing through the same route on the lowest side is specified. In this case, “GW-X” is associated with the hop number “1” of “temperature sensor X”, and “GW-Z” is associated with the hop number “2” of “temperature sensor X”. “Cloud” is associated with the hop number “3” of “temperature sensor X”. Therefore, “GW-X” is specified as the upper node of the lower node “temperature sensor X”.

  In the example illustrated in FIG. 27, “GW-X”, “GW-Z”, and “cloud” can be listed as nodes that can be upper nodes of “humidity sensor X”. Among these, the IP address “192.168.100.1” and the WAN side IP address “1.1.10.2” associated with the hop number “1” of “GW-X” are “humidity sensor X”. ”Matches the IP address and WAN side IP address associated with the hop number“ 1 ”. For this reason, the router 10 through which the “humidity sensor X” and “GW-X” commonly pass the IP address “192.168.100.1” and the WAN-side IP address “1.1.10.2” or It is specified as the IP address of the host. Also, the IP address “1.1.10.1” associated with the hop number “1” of “GW-Z” is the IP address associated with the hop number “2” of “humidity sensor X”. Match. Therefore, the IP address “1.1.10.1” is specified as the IP address of the router 10 or the host through which “humidity sensor X” and “GW-Z” pass in common. The IP address “1.1.1.10” associated with the “hop” “1” of “cloud” matches the IP address associated with the “hop” “3” of “humidity sensor X”. . For this reason, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “humidity sensor X” and “cloud” pass in common.

  As described above, when three nodes “GW-X”, “GW-Z”, and “Cloud” are specified as upper nodes passing through the same route as “humidity sensor X”, An upper node passing through the same route on the lowest side is specified. In this case, “GW-X” is associated with the hop number “1” of “humidity sensor X”, and “GW-Z” is associated with the hop number “2” of “humidity sensor X”. “Cloud” is associated with the hop number “3” of “humidity sensor X”. Therefore, “GW-X” is specified as the upper node of the lower node “humidity sensor X”.

  In the example illustrated in FIG. 27, “GW-Z” and “cloud” can be cited as nodes that can be upper nodes of “temperature sensor Y”. Among these, the IP address “1.1.10.1” associated with the hop number “1” of “GW-Z” is the IP address associated with the hop number “2” of “temperature sensor Y”. Matches. Therefore, the IP address “1.1.10.1” is specified as the IP address of the router 10 or the host through which “temperature sensor Y” and “GW-Z” pass in common. In addition, the IP address “1.1.1.10” associated with the hop number “1” of “cloud” matches the IP address associated with the hop number “3” of “temperature sensor Y”. . Therefore, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “temperature sensor Y” and “cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as the upper nodes passing through the same route as “temperature sensor Y”, the same is given to the lowest side of these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “temperature sensor X”, and “cloud” is associated with the hop number “3” of “temperature sensor Y”. . Therefore, “GW-Z” is specified as the upper node of the lower node “temperature sensor Y”.

  In the example illustrated in FIG. 27, “GW-Z” and “cloud” can be cited as nodes that can be upper nodes of “humidity sensor Y”. Among these, the IP address “1.1.10.1” associated with the hop number “1” of “GW-Z” is the IP address associated with the hop number “2” of “humidity sensor Y”. Matches. Therefore, the IP address “1.1.10.1” is specified as the IP address of the router 10 or the host through which “humidity sensor Y” and “GW-Z” pass in common. The IP address “1.1.1.10” associated with the “hop” “1” of “cloud” matches the IP address associated with the “hop” “3” of “humidity sensor Y”. . Therefore, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “humidity sensor Y” and “cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as upper nodes passing through the same route as “humidity sensor Y”, the same is given to the lowest side of these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “humidity sensor X”, and “cloud” is associated with the hop number “3” of “humidity sensor Y”. . Therefore, “GW-Z” is specified as the upper node of the lower node “humidity sensor Y”.

  In the example illustrated in FIG. 27, “GW-Z” and “cloud” can be cited as nodes that can be upper nodes of “GW-X”. Among these, the IP address “1.1.10.1” associated with the hop number “1” of “GW-Z” is the IP address associated with the hop number “2” of “GW-X”. Matches. Therefore, the IP address “1.1.10.1” is specified as the IP address of the router 10 or the host through which “GW-X” and “GW-Z” pass in common. Also, the IP address “1.1.1.10” associated with the “cloud” hop number “1” matches the IP address associated with the “GW-X” hop number “3”. . For this reason, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “GW-X” and “Cloud” pass in common.

  As described above, when two nodes, “GW-Z” and “Cloud”, are specified as the upper nodes passing through the same route as “GW-X”, the same is given to the lowest side among these upper nodes. An upper node passing through the route is specified. In this case, “GW-Z” is associated with the hop number “2” of “GW-X”, and “cloud” is associated with the hop number “3” of “GW-X”. . Therefore, “GW-Z” is specified as an upper node of the lower node “GW-X”.

  In the example illustrated in FIG. 27, “cloud” is an example of a node that can be an upper node of “GW-Z”. The IP address “1.1.1.10” associated with the “hop” “1” of “cloud” matches the IP address associated with the “hop” “2” of “GW-Z”. For this reason, the IP address “1.1.1.10” is specified as the IP address of the router 10 or the host through which “GW-Z” and “cloud” pass in common. Therefore, “cloud” is specified as an upper node of the lower node “GW-Z”.

  As described above, the disclosed technique can be used in combination with a plurality of addresses assigned to identify the router 10 and the host. According to this, for example, even when the same private IP address is used in a plurality of networks, such as a network using NAT (Network Address Translation), the disclosed technology can be applied.

  In addition, among the processes described in the above embodiments, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed All or a part of the above can be automatically performed by a known method. In addition, the processing procedures, control procedures, specific names, and information including various data and parameters shown in the above-described document and drawings can be arbitrarily changed unless otherwise specified.

  The components of the server nodes 110 and 120 shown in FIGS. 2 and 21 are functionally conceptual, and need not be physically configured as illustrated. That is, the specific form of distribution / integration of the server nodes 110 and 120 is not limited to that shown in the figure, and all or a part thereof may be functionally or physically in an arbitrary unit according to various loads or usage conditions. Can be distributed and integrated.

[program]
FIG. 28 is a diagram illustrating an example of a computer that executes an event collection program. As illustrated in FIG. 28, the computer 400 includes a CPU 401 that executes various arithmetic processes, an input device 402 that receives data input from a user, and a monitor 403. The computer 400 also includes a medium reading device 404 that reads programs and the like from a storage medium, an interface device 405 for connecting to other devices, and a wireless communication device 406 for connecting to other devices wirelessly. The computer 400 also includes a RAM (Random Access Memory) 307 that temporarily stores various information and a hard disk device 408. Each device 401 to 408 is connected to a bus 409.

  The hard disk device 408 includes the same processing units as the path information receiving unit 112, the topology generating unit 113, the deployment destination determining unit 117, the transmission destination information transmitting unit 118, and the module transmitting unit 119 shown in FIGS. An event collection program having a function is stored. The hard disk device 408 stores various data for realizing the event collection program.

  The CPU 401 reads out each program stored in the hard disk device 408, develops it in the RAM 407, and executes it to perform various processes. These programs cause the computer to function as the route information receiving unit 112, the topology generating unit 113, the deployment destination determining unit 117, the transmission destination information transmitting unit 118, and the module transmitting unit 119 shown in FIGS. Can do.

  Note that the above event collection program is not necessarily stored in the hard disk device 408. For example, the computer 400 may read and execute a program stored in a computer-readable recording medium. The computer-readable recording medium corresponds to, for example, a portable recording medium such as a CD-ROM, a DVD disk, a USB (Universal Serial Bus) memory, a semiconductor memory such as a flash memory, a hard disk drive, and the like. Further, the program may be stored in a device connected to a public line, the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or the like, and the computer 400 may read and execute the program therefrom. good.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Appendix 1) An event collection method executed by a computer,
Computer
Receives route information related to the route of the network from multiple nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
When an event is transmitted between the nodes indicated by the generated connection information, it is determined whether or not a module for processing the event can be deployed in one or a plurality of nodes among the plurality of nodes.
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An event collection method characterized by executing processing.

(Appendix 2) Monitoring whether each of the plurality of nodes is in a communicable state,
When any of the plurality of nodes is in a communication disabled state, further executes a process of deleting the route information received from the node in the communication disabled state,
The connection process between the plurality of nodes is generated based on the path information from which the path information received from the node in the communication disabled state is deleted. Event collection method.

(Appendix 3)
Receives route information related to the route of the network from multiple nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
When an event is transmitted between the nodes indicated by the generated connection information, it is determined whether or not a module for processing the event can be deployed in one or a plurality of nodes among the plurality of nodes.
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An event collection program characterized by causing processing to be executed.

(Appendix 4) Monitoring whether each of the plurality of nodes is in a communicable state,
When any of the plurality of nodes is in a state where communication is disabled, it further executes processing for deleting route information received from the node in communication disabled,
The appending 3 includes generating the connection information between the plurality of nodes based on the route information from which the route information received from the node in the communication disabled state is deleted. Event collection program.

(Appendix 5) Receiving route information related to the route of the network from a plurality of nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
When an event is transmitted between the nodes indicated by the generated connection information, it is determined whether or not a module for processing the event can be deployed in one or a plurality of nodes among the plurality of nodes.
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An information processing apparatus that executes processing.

(Appendix 6) Monitoring whether each of the plurality of nodes is in a communicable state,
When any of the plurality of nodes is in a state where communication is disabled, it further executes processing for deleting route information received from the node in communication disabled,
Item 6. The appendix 5 is characterized in that the generating process generates connection information between the plurality of nodes based on route information from which route information received from a node in an incommunicable state is deleted. Information processing device.

110, 120 Server node 111 Module registration unit 111A Module storage unit 111B Module definition storage unit 112 Route information reception unit 112A Route information storage unit 113 Topology generation unit 113A Topology storage unit 114 Event reception unit 114A Event storage unit 115 Module execution unit 116 Occurrence Event registration unit 116A Occurrence event information storage unit 117 Deployment destination determination unit 117A Deployment destination information storage unit 118 Transmission destination information transmission unit 119 Module transmission unit 121 Life information reception unit 122 Life monitoring unit 400 Computer 401 CPU
402 Input Device 403 Monitor 404 Medium Reading Device 405 Interface Device 406 Wireless Communication Device 407 RAM
408 Hard disk device 409 Bus

Claims (4)

An event collection method executed by a computer,
Computer
Receives route information related to the route of the network from multiple nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
Whether or not a module for processing the event can be deployed to a node having an attribute corresponding to an attribute defined in the module among the plurality of nodes when an event is transmitted between the nodes indicated by the generated connection information Determine whether
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An event collection method characterized by executing processing. Monitoring whether each of the plurality of nodes is in a communicable state;
When any of the plurality of nodes is in a communication disabled state, further executes a process of deleting the route information received from the node in the communication disabled state,
The connection process between the plurality of nodes is generated based on the route information from which the route information received from the node in the communication disabled state is deleted. The event collection method described. On the computer,
Receives route information related to the route of the network from multiple nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
Whether or not a module for processing the event can be deployed to a node having an attribute corresponding to an attribute defined in the module among the plurality of nodes when an event is transmitted between the nodes indicated by the generated connection information Determine whether
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An event collection program characterized by causing processing to be executed. Receives route information related to the route of the network from multiple nodes connected to the network,
Based on the received route information, generate connection information between the plurality of nodes,
Whether or not a module for processing the event can be deployed to a node having an attribute corresponding to an attribute defined in the module among the plurality of nodes when an event is transmitted between the nodes indicated by the generated connection information Determine whether
If the module can be deployed to the node, the event transmission destination set for each of the plurality of nodes is changed to the node indicated by the generated connection information, and the module is deployed to the node. An information processing apparatus that executes processing.

Images