JP5678819B2 - COMMUNICATION DEVICE, COMMUNICATION PROGRAM, AND COMMUNICATION METHOD - Google Patents

Description

  The present invention relates to a communication device, a communication program, and a communication method for communicating.

  In recent years, a smart meter system that collects power usage information in a server by using a smart meter, which is a high-performance power meter having a device management function and a communication function, and is applied to a billing service or the like is being provided. In the following description, collection processing and analysis processing of power information, temperature information, etc. from each smart meter in each smart meter system are referred to as tasks, and each smart such as power information, temperature information, which is a measurement target attribute. Information that can be measured by the meter is called an event. The smart meter system includes a server that executes a task, a repeater that is connected to the server and has a hierarchical structure, and a smart meter that is connected to the repeater.

  As a technique for collecting events, there is, for example, Publish / Subscribe. Specifically, a transmission device that requests an event transmits an event request. The receiving device that has received the event request transmits the event transmitted from the lower device to the transmitting device. In addition, in order to transmit the transmitted event to the transmission device, the reception device registers route information including the event and the identification information of the transmission device. When the event is received, the reception device receives the event according to the registered route information. The event is transmitted to the transmission device.

  In the smart meter system, the load on the server increases with an increase in events and tasks. Therefore, the smart meter system can reduce the load on the server by delegating the task to the repeater. As a technology related to the task delegation technology, for example, each repeater registers information on the processing capability of its own device, and the server delegating the task includes the task processing capability among the registered information. There are things such as delegating tasks to repeaters that meet the conditions.

Japanese Patent Laid-Open No. 2003-167808

  However, in the above-described prior art, the relay device that has received the event request registers the route information, but the relay device may not receive an event corresponding to the event request, and in this case, a route that is not used. Information has been registered. When an event is delegated, event information is registered in each repeater, so that there is a problem in that registered route information increases.

  An object of the present invention is to provide a communication device, a communication program, and a communication method that can suppress an increase in route information in order to solve the above-described problems caused by the related art.

  In order to solve the above-described problems and achieve the object, according to one aspect of the present invention, a measurement target exists in a tree-structured network and receives a feature amount collection request regarding the measurement target attribute from a lower-level device. The communication apparatus transmits the collection request to the upper apparatus while storing the attribute information and the identification information of the lower apparatus in the storage area of the own apparatus. Sets the evaluation value that indicates whether the highest device in the network is the device that collects from the network, and indicates the device that has the highest evaluation value when the collection request is received. A communication device, a communication program, and a communication method are proposed for controlling so that a collection request is not transmitted to a higher-order device when it is determined that the device has the highest evaluation value. .

  According to one aspect of the present invention, there is an effect that an increase in route information can be suppressed.

1-1 is an explanatory diagram (part 1) of an operation example of the smart meter system 100. FIG. FIG. 1-2 is an explanatory diagram (part 2) of an operation example of the smart meter system 100. FIG. 2 is a block diagram of hardware of the communication device 102 according to the embodiment. FIG. 3 is a block diagram illustrating functions of the smart meter system 100. FIG. 4 is an explanatory diagram illustrating an example of the contents stored in the route information table 104. FIG. 5 is an explanatory diagram showing an example of the contents stored in the process division table 311. FIG. 6 is an explanatory diagram showing an example of the contents stored in the message task relation table 312. FIG. 7 is an explanatory diagram showing a format example of the task information 313. FIG. 8 is an explanatory diagram illustrating a processing example of the task information 313 in the server 101. FIG. 9 is an explanatory diagram showing an example of the stored contents of the message storage table 331. FIG. 10 is an explanatory diagram showing a format example of the event request message 332. FIG. 11 is an explanatory diagram (part 1) illustrating a state in which tasks are delegated. FIG. 12 is an explanatory diagram (part 2) of the task being delegated. FIG. 13 is an explanatory diagram (part 3) illustrating a state where tasks are delegated. FIG. 14 is an explanatory diagram (part 4) illustrating a state in which tasks are delegated. FIG. 15 is an explanatory diagram showing a state in which the event request message 332 has been transmitted. FIG. 16 is an explanatory diagram showing a state in which the event 333 is collected. FIG. 17 is a flowchart illustrating an example of task delegation execution processing in the smart meter system 100. FIG. 18 is a flowchart illustrating an example of task delegation processing in the server 101. FIG. 19 is a flowchart illustrating an example of the communication device task delegation process. FIG. 20 is a flowchart illustrating an example of event branch setting processing in the communication apparatus 102. FIG. 21 is a flowchart illustrating an example of an event request message transmission process in the communication apparatus 102. FIG. 22 is a flowchart illustrating an example of route information setting processing in the communication apparatus 102. FIG. 23 is a flowchart illustrating an example of event collection processing in the communication apparatus 102. FIG. 24 is a flowchart illustrating an example of task completion processing in the communication apparatus 102.

  Exemplary embodiments of a disclosed communication device, communication program, and communication method will be described below in detail with reference to the accompanying drawings.

  FIGS. 1-1 and 1-2 are explanatory diagrams illustrating an operation example of the smart meter system 100. FIG. The smart meter system 100 includes a server 101 that executes a task, a communication device 102 that serves as a relay, and a terminal 103 that includes a smart meter. The explanatory diagram shown in FIG. 1A shows an example of operation when a task is delegated, and the explanatory diagram shown in FIG. 1B shows an example of operation when an event is collected.

  The server 101 is a server to which a technique called CEP (Complex Event Processing) that executes a task using an event transmitted from the terminal 103 is applied. The communication device 102 relays the event from the terminal 103 and transmits it to the server 101. The terminal 103 is installed in a building or house to be measured, and periodically transmits an event to the communication device 102.

  As a connection relationship between the server 101, the communication device 102, and the terminal 103, the smart meter system 100 is a tree-structured network, the server 101 is the highest-level device, and the terminal 103 is the terminal device. The server 101 is connected to the communication device 102-G as a lower device. The communication device 102-G is connected to the communication device 102-E and the communication device 102-F as lower devices. The communication device 102-F is connected to a terminal 103-F1 installed in a house as a lower device.

  The communication device 102-E is connected to the communication device 102-C and the communication device 102-D as lower devices. The communication device 102-D is connected to a terminal 103-D1 and a terminal 103-D2 installed in a house as lower devices. The communication device 102-C is connected to the communication device 102-A and the communication device 102-B as lower devices. The communication device 102-B is connected to a terminal 103-B1 installed in a house and a terminal 103-B2 installed in a building as lower devices. The communication device 102-A is connected to a terminal 103-A1 installed in the building as a lower device.

  In the following description, when the suffix of “−S” is added to the hardware and software codes, this indicates hardware and software related to the server 101. Further, when suffixes “-A” to “-G” are given to the hardware and software codes, the hardware and software are related to the communication devices 102-A to 102-G. Show.

  Further, the server 101 and the communication device 102 have a route information table 104. The route information table 104 is a table that stores a message or event transfer destination device when a message or event requesting task delegation is received. Also, one record of the route information table 104 is defined as route information. For example, in the path information table 104-G, a temperature sensor capable of measuring building temperature information and house temperature information is registered in the direction of the communication device 102-E, and a house temperature sensor is registered in the direction of the communication device 102-F. It has been shown that. Therefore, when receiving a task delegation request that uses building temperature information, the communication device 102-G transmits a delegation request to the communication device 102-E.

  In FIG. 1, the server 101 transmits a task delegation request message, which is a message for delegating a task 111 for calculating the average temperature of a building to one of the communication devices 102, to the communication device 102 -G. The communication device 102 that has received the task delegation request message receives an evaluation value indicating whether or not the highest device in the smart meter system 100 among the devices that collect events from a plurality of lower devices is its own device. Set. In the following description, when the above-described condition is satisfied, the communication apparatus 102 sets the evaluation value as “start of branch”.

  In addition, the communication apparatus 102 transmits setting information indicating whether the evaluation value is set as “branch start” to the lower apparatus. In the present embodiment, communication device 102 transmits setting information included in a task delegation request message. When the evaluation value is not set as “branch start”, the setting information is defined as “unbranched”, and when set, it is defined as “branched”.

  First, the communication device 102-G determines whether it is a device that collects a corresponding event from a plurality of lower devices. Since the building temperature information is collected from one communication device 102-E, the communication device 102-G does not set the evaluation value as “branch start”, and the setting information is “unbranched” according to the route information table 104-G. The task delegation request message that becomes “is transferred to the communication apparatus 102 -E. Similarly, the communication device 102-E also transfers the task delegation request message to the communication device 102-C according to the route information table 104-E without setting the evaluation value as “start of branch”.

  The communication device 102-C that has received the task delegation request message has the setting information “unbranched” and the building temperature information is collected from a plurality of communication devices 102-A and 102-B. 112 is set as “start of branch”. After the setting, the communication device 102-C transmits a task delegation request message in which the setting information becomes “branched” to the communication device 102-A. The communication device 102-A executes the task 111.

  As described above, the smart meter system 100 sets an evaluation value in the highest device in the smart meter system 100 among devices that collect the corresponding event from a plurality of lower devices, so that the branch start point of the event is set. I can judge. In the example of FIG. 1-1, the communication device 102-D to the communication device 102-F do not collect building temperature information, and therefore do not have route information corresponding to the event.

  Next, in the explanatory diagram illustrated in FIG. 1B, when the communication apparatus 102-A executes the task 111, the communication apparatus 102-C transmits an event request message that is an event collection request as a higher-level communication apparatus. Send to. Receiving the event request message, the communication device 102-C adds route information for transmitting the building temperature information to the communication device 102-A to the route information table 104-C. Thereby, in event collection, when receiving an event from the communication device 102-B, the communication device 102-C transmits the event to the communication device 102-A according to the added path information.

  Further, the communication apparatus 102-C determines whether or not the evaluation value 112 is “start of branch”. Since the evaluation value 112 is “start of branch”, the communication device 102-C controls not to transmit the event request message to the communication device 102-E.

  Accordingly, since the communication device 102-E does not receive the event request message, the smart meter system 100 can suppress an increase in the route information without adding route information. Subsequently, hardware and software for realizing the operations performed in FIGS. 1-1 and 1-2 will be described with reference to FIGS.

  FIG. 2 is a block diagram of hardware of the communication device 102 according to the embodiment. In FIG. 2, the communication apparatus 102 includes a CPU (Central Processing Unit) 201, a ROM (Read-Only Memory) 202, and a RAM (Random Access Memory) 203. The communication device 102 includes a flash ROM 204 and an I / F (Interface) 205. Each unit is connected by a bus 206.

  Here, the CPU 201 governs overall control of the communication apparatus 102. Note that the communication device 102 may be a multi-core processor system including a plurality of CPUs. Here, the multi-core processor system is a computer system including a processor in which a plurality of cores are mounted.

  The ROM 202 stores a program such as a boot program. The RAM 203 is used as a work area for the CPU 201. The flash ROM 204 stores system software such as an OS (Operating System), application software, a communication program according to the present embodiment, and the like. For example, when updating the OS, the communication apparatus 102 receives the new OS by the I / F 205 and updates the old OS stored in the flash ROM 204 to the received new OS.

  The I / F 205 is connected to an external device such as the server 101, another communication device 102, and the terminal 103 through a communication line. The I / F 205 manages an internal interface with the external device group and controls data input / output from the external device.

  Note that the server 101 to the terminal 103 may be directly connected, or the server 101 to the terminal 103 exist in the same LAN (Local Area Network) and are connected to each other via an L2 switch or the like. May be. The server 101 to the terminal 103 may be connected via a network such as a WAN (Wide Area Network) and the Internet. In this case, in order to encrypt the information, the server 101 to the terminal 103 may employ SSL (Secure Socket Layer) or IPsec (security architecture for Internet Protocol). Moreover, between the communication apparatus 102 and the terminal 103 may be via power line carrier communication.

  The hardware of the server 101 includes, for example, a magnetic disk drive, a magnetic disk, an optical disk drive, and an optical disk in addition to the CPU, ROM, and RAM. The magnetic disk drive controls data read / write with respect to the magnetic disk according to the control of the CPU in the server 101. The magnetic disk stores data written under the control of the magnetic disk drive. The optical disc drive controls reading / writing of data with respect to the optical disc according to the control of the CPU in the server 101. The optical disk stores data written under the control of the optical disk drive, and allows the computer to read data stored on the optical disk.

  Further, the hardware of the terminal 103 includes a sensor that measures power consumption in a house or building in addition to the hardware included in the communication device 102. Furthermore, the terminal 103 may include a sensor that measures the temperature in the house or building, and may be connected to an air conditioner in the house or building.

(Function of smart meter system 100)
Next, functions of the smart meter system 100 will be described. FIG. 3 is a block diagram illustrating functions of the smart meter system 100. Smart meter system 100 includes a control unit 301, a syntax analysis unit 302, a generation unit 303, and a transmission unit 304. The functions (control unit 301 to transmission unit 304) serving as the control unit are realized by the CPU of the server 101 executing the program stored in the storage device. Specifically, the storage device is a ROM, a RAM, a flash ROM, or the like of the server 101, for example. Alternatively, the function may be realized by another CPU executing via the I / F of the server 101.

  The smart meter system 100 includes a storage unit 320, a reception unit 321, a setting unit 322, a determination unit 323, a control unit 324, a transmission unit 325, a reception unit 326, an addition unit 327, and a transmission unit. 328. The functions (reception unit 321 to transmission unit 328) serving as the control unit are realized by the CPU 201 executing the program stored in the storage device.

  Specifically, the storage device is, for example, the ROM 202, the RAM 203, the flash ROM 204, or the like shown in FIG. Alternatively, the function may be realized by execution by another CPU via the I / F 205. The storage unit 320 is a storage device such as the RAM 203 and the flash ROM 204. In addition, the storage unit 320 to the transmission unit 328 illustrated in FIG. 3 are illustrated as functions of the communication device 102-C, but are also included in the communication device 102-A to the communication device 102-G.

  Further, the smart meter system 100 can access the route information table 104, the process division table 311, the message task relation table 312, and the message storage table 331. In addition, the smart meter system 100 generates task information 313, a task delegation request message 314, and an event request message 332. Moreover, the smart meter system 100 acquires the event 333 periodically.

  Note that the path information table 104 is stored in each storage area of the server 101 and the communication device 102. Specifically, the server 101 has a route information table 104-S, and the communication devices 102-A to 102-G have route information tables 104-A to 104-G, respectively. doing. The process division table 311 and the message task relation table 312 are stored in the storage area of the server 101. The message storage table 331 is stored in each storage area of the communication device 102. The task information 313 and the task delegation request message 314 are generated by the server 101. The event request message 332 is generated by the communication device 102 to which the task is delegated.

  The communication device 102 exists in the smart meter system 100 having a tree structure. The number of lower-level devices connected to the communication device may be one or two or more. In addition, when the communication device 102 receives a collection request for the feature amount related to the attribute of the measurement target from the lower device, the communication device 102 stores the attribute information of the measurement target and the identification information of the lower device in the storage area of the own device, Is sent to the host device.

  The measurement object indicates an object to be measured by a sensor attached to the smart meter, such as a building or a house. The attribute information of the measurement object is a characteristic type of the measurement object, and indicates, for example, a type such as temperature information and power information. The characteristic amount of the attribute of the measurement target is a specific value of the attribute. For example, if the attribute information of the measurement target is temperature information, the characteristic amount is 20 [degrees]. Further, the feature quantity of the attribute to be measured need not be a numerical value, and may be information such as power information: high, medium, low, for example.

  The route information table 104 is a table that stores a device to which the task delegation request message 314 and the event 333 are transferred when the task delegation request message 314 or the event 333 is received. Details of the route information table 104 will be described later with reference to FIG. The process division table 311 is a table that stores whether or not a process executed by a task can be divided by a plurality of communication apparatuses 102. Details of the process division table 311 will be described later with reference to FIG. The message task relationship table 312 is a table that stores associations between tasks and task delegation request messages 314. Details of the message task relation table 312 will be described later with reference to FIG.

  The task information 313 is data obtained by parsing the task. Details of the task information 313 will be described later with reference to FIG. The task delegation request message 314 is a message transmitted to the lower-level communication device 102 when requesting task delegation. Details of the task delegation request message 314 will be described later with reference to FIG.

  The message storage table 331 stores an evaluation value corresponding to the event. Details of the message storage table 331 will be described later with reference to FIG. The event request message 332 is a message for transmitting an event collection request to the higher-level communication device 102. Details of the event request message 332 will be described later with reference to FIG.

  The control unit 301 manages the server 101 and has a function of delegating a task to one of the communication devices 102 when the load on the server 101 increases, for example. For example, the control unit 301 selects one task from a task queue in which a list of tasks is stored, and sets it as a task to be delegated. The set task identification information is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, or the flash ROM 204.

  The syntax analysis unit 302 parses the task to be transferred selected by the control unit 301. Specifically, the syntax analysis unit 302 performs syntax analysis in accordance with a convention that the task complies with. For example, when a task is described according to CQL (Continuous Query Language) adopted in the CEP technology, the CQL parser in the server 101 performs syntax analysis. Data obtained by parsing is task information 313. The task information 313 is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, and the flash ROM 204.

  The generation unit 303 has a function of generating a task delegation request message 314 from the task information 313. For example, the generation unit 303 adds an ID (IDentification) unique to the task delegation request message 314 and setting information indicating whether the evaluation value is set as “start of branch” from the task information 313, and sends the task delegation request message 314 is generated.

  The transmission unit 304 transmits the generated task delegation request message 314 to the lower communication apparatus 102. For example, the transmission unit 304 transmits a task delegation request message 314 to the communication device 102-G.

  The storage unit 320 stores a combination of the attribute information of the measurement target and the identification information of the lower device that can acquire the feature amount of the measurement target attribute. Specifically, the storage unit 320 stores a combination of the attribute information of the measurement target and the identification information of the lower-level apparatus that can acquire the feature amount of the attribute of the measurement target in the route information table 104.

  The receiving unit 321 has a function of receiving setting information indicating whether or not the evaluation value is set as “branch start” from a higher-level device. Specifically, the receiving unit 321 receives setting information from the communication device 102-E. When the connection state of the smart meter system 100 does not change, the location where the setting information changes does not change. Specifically, in FIG. 1-1, when the event is building temperature information, the setting information is always set to “branched” in the communication device 102-C.

  Therefore, when different tasks using the same event are delegated, the first task delegation request message 314 includes setting information, and the second task delegation request message 314 does not include setting information. May be. The upper apparatus may transmit the setting information alone. The received setting information is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, and the flash ROM 204.

  The setting unit 322 has a function of setting an evaluation value indicating whether or not the highest device in the network among the devices that collect the feature values related to the measurement target attribute from a plurality of lower devices is the own device. . In addition, when the setting unit 322 receives the setting information by the receiving unit 321, the setting unit 322 automatically determines, based on the number of lower-level devices that can acquire the feature amount of the measurement target attribute stored in the storage unit 320 and the setting information. You may set the evaluation value of an apparatus.

  Specifically, the setting unit 322 sets the evaluation value as “branch start” when there are a plurality of lower-level devices that can acquire the feature quantity of the measurement target attribute and the setting information is “unbranched”. . In addition, the setting unit 322 does not set the evaluation value when there is a single lower apparatus that can acquire the feature amount of the attribute to be measured. Furthermore, the setting unit 322 does not set an evaluation value when the setting information is “branched”.

  The evaluation value may be set when the smart meter system 100 is designed. When the connection state of the smart meter system 100 does not change, the communication device 102 to which the evaluation value is set does not change. Specifically, in FIG. 1-1, when the event is building temperature information, the evaluation value is always set to “start of branching” in the communication device 102-C. Therefore, in the smart meter system 100, an evaluation value corresponding to the building temperature information may be set in advance for the communication device 102-C at the time of design. The set evaluation value is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, or the flash ROM 204.

  When receiving the collection request, the determination unit 323 has a function of determining whether or not the evaluation value set by the setting unit 322 indicates “branch start”. The determination result is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, or the flash ROM 204.

  The control unit 324 has a function of controlling the collection request not to be transmitted to a higher-level device when the determination unit 323 determines that the evaluation value is “start of branching”. For example, the control unit 324 controls the event request message 332 not to be transmitted to the communication device 102-E.

  The transmission unit 325 has a function of transmitting a collection request to a higher-level device. For example, when it is determined that the evaluation value is not set, the transmission unit 325 transmits the event request message 332 to the communication device 102-E.

  The receiving unit 326 has a function of receiving an event collection request from a lower apparatus. For example, the reception unit 326 receives the event request message 332 from the communication device 102-A. The received event request message 332 is stored in a storage area such as the general-purpose register of the CPU 201, the RAM 203, or the flash ROM 204.

  The addition unit 327 has a function of adding the attribute information of the measurement target and the identification information of the lower device to the storage unit 320 when receiving the collection request by the reception unit 326. For example, when the event to be collected is building temperature information and the event request message 332 is received from the communication device 102-A, the adding unit 327 includes the building temperature information and the identification information of the communication device 102-A. The route information is added to the route information table 104-C.

  The transmission unit 328 has a function of transmitting the feature amount of the measurement target attribute with reference to the storage unit 320 added by the addition unit 327 when receiving the feature amount of the measurement target attribute from the lower apparatus. For example, when receiving the event 333 from the communication device 102-B, the transmission unit 328 refers to the route information added to the route information table 104-C and transmits the event 333 to the communication device 102-A.

  FIG. 4 is an explanatory diagram illustrating an example of the contents stored in the route information table 104. In the route information table 104, information of the terminal 103 and the communication device 102 connected in the lower direction is registered. The route information table 104 includes two tables, and includes a task delegation table 401 that is referred to when a task is delegated, and an event collection table 402 that is referred to when an event is collected. Note that the route information table 104 illustrated in FIG. 4 is an example of the route information table 104-C existing in the communication device 102-C.

  The task delegation table 401 includes three fields: sensor type, measurement object, and delegation destination identification information. In the sensor type field, an identifier of a sensor measured by a task command is stored. The sensor identifier is, for example, an identifier indicating a temperature sensor that measures temperature, an identifier indicating a power sensor that measures power, or the like. In the measurement object field, an identifier indicating an object to be measured by the sensor is stored. In the delegation destination identification information field, identification information of a device that is a task delegation destination is stored. As device identification information, for example, an IP (Internet Protocol) address, a MAC (Media Access Control) address, or the like of the device is employed.

  Next, a trigger for registering a record in the task delegation table 401 will be described. When the communication device 102-A is connected to the smart meter system 100, the communication device 102-A transmits the contents of its own task delegation table 401-A to the communication device 102-C as a Subscribe message. Subsequently, the communication apparatus 102-C registers the received Subscribe message in the task delegation table 401-C. For example, if the Subscribe message from the communication device 102-A is “sensor type: temperature sensor, measurement target: building”, the communication device 102-C registers the Subscribe message as the record 401-C-1.

  Similarly, the communication device 102-C registers the Subscribe message from the communication device 102-B as a record 401-C-2 and a record 401-C-3. Thus, the task delegation table 401 is added with a record when the communication apparatus 102 and the terminal 103 are connected, and is fixed thereafter. A specific method for referencing the task delegation table 401 when delegating a task will be described later with reference to FIGS.

  The event collection table 402 includes three fields: event type, measurement target, and collection destination identification information. The event type field stores the type of event to be collected. For example, temperature information, power information, and the like are stored in the event type field. In the measurement object field, an identifier indicating an object to be measured by the sensor is stored. In the collection destination identification information field, identification information of a communication device that is an event collection destination is stored. The trigger for registering a record in the event collection table 402 will be described later with reference to FIG. 15, and a specific method for referring to the event collection table 402 when collecting an event will be described later with reference to FIG. .

  The table 403 displays the task delegation table 401-C and the event collection table 402-C in combination. In the following figure, the data of the route information table 104 are combined and displayed as a table 403.

  Note that the measurement target fields of the task delegation table 401 and the event collection table 402 are information used to classify events. In the example of FIG. 4, events such as temperature information and power information can be classified as building temperature information and house temperature information. When classifying events under other conditions, the task delegation table 401 and the event collection table 402 include fields for storing other conditions.

  FIG. 5 is an explanatory diagram showing an example of the contents stored in the process division table 311. The process division table 311 includes two fields, a process name and a process division flag. The process name field stores the name of the process executed by the task. The process division flag field stores a flag indicating whether or not the corresponding process can be divided. Specifically, in the process division flag field, either a “permitted” identifier indicating that division is possible or a “not permitted” identifier indicating that division is not possible is stored.

  For example, the record 311-1 indicates that the process executed by the task is an average, and the process that performs the average cannot be divided. Subsequently, the record 311-2 indicates that the process executed by the task is a notification, and the process of performing the notification can be divided. Further, the record 311-3 indicates that the process executed by the task is cumulative, and the process for performing accumulation cannot be divided. The processes that can be executed by the smart meter system 100 are determined at the design stage, and which processes can be divided are determined at the design stage.

  FIG. 6 is an explanatory diagram showing an example of the contents stored in the message task relation table 312. The message task relationship table 312 is a table that stores the relationship between the task delegation request message 314 generated when delegating a task to the communication apparatus 102 and the task of delegation. The message task relation table 312 is stored for each task to be delegated.

  The message task relationship table 312 includes two fields: message ID and task. In the message ID field, the ID of the task delegation request message 314 is stored. The message ID only needs to be a value that uniquely identifies the message, and may be, for example, a random value that does not overlap. The task field stores a task to be delegated. When there is a task ID that can uniquely identify a task, the message task relation table 312 may have a task ID field for storing the task ID instead of the task field.

  For example, the record 312-1 illustrated in FIG. 6 indicates that the message ID is “0x153959b2”, and the task is “select average (building temperature information) from area A and area B where X> 30”. . The record 312-2 indicates that the message ID is “0x15638092” and the task is “select average (building temperature information) from area A where X> 30”.

  FIG. 7 is an explanatory diagram showing a format example of the task information 313. The explanatory diagram shown in FIG. 7 shows a task 701 and task information 313 obtained by parsing the task 701. The task 701 is information shown below.

  select average (building temperature information) from area A and area B where X> 30

  The server 101 parses the task 701 and generates task information 313. The task information 313 includes four fields: process name, event, result notification condition, and process division flag.

  The process name field stores the name of the process executed by the task. The event field stores an event required when the task is executed. The event field may store events classified into classes. The classified event is an event classified according to a measurement object such as building temperature information and house temperature information with respect to the temperature information in the smart meter system 100, for example. The events may be classified according to information other than buildings such as buildings and houses. For example, when an office, a store, and a restaurant are in the building, the smart meter system 100 classifies the building temperature information into office temperature information, store temperature information, restaurant temperature information, and the like. May be.

  The result notification condition field stores a condition for performing notification as a result of task processing. The process division flag field stores a flag indicating whether or not the corresponding process can be divided. For example, the task information 313 shown in FIG. 7 is when the processing executed by the task is average, the event requested by the task is building temperature information, and the result notification condition is when the average temperature is 30 ° C. or higher. This indicates that the process cannot be divided.

  FIG. 8 is an explanatory diagram illustrating a processing example of the task information 313 in the server 101. The server 101 generates a task delegation request message 314 from the task information 313. In the task delegation request message 314, a multi-communication device event branched flag field and a message ID field are added to the task information 313.

  The multi-communication device event branch completed flag field stores setting information indicating whether the evaluation value is set as “branch start”. In the multi-communication device event branch completed flag field, for example, when the evaluation value is set to “branch start” in any of the communication devices 102, “branched” is stored, and the evaluation value is “branch start”. If not set, “unbranched” is stored. At the time when the task delegation request message 314 is generated, the multi-communication device event branched flag field stores “unbranched”. The message ID field is an ID for identifying the task delegation request message 314, and stores the value of the message ID field of the message task relation table 312.

  For example, the task delegation request message 314 shown in the example of FIG. 8 indicates that the evaluation value is not set as “start of branching” and the message ID is “0x153959b2”.

  FIG. 9 is an explanatory diagram showing an example of the stored contents of the message storage table 331. The message storage table 331 includes two fields, message ID and event status. In the message ID field, the message ID of the received task delegation request message 314 is stored. The event status field stores an evaluation value indicating whether or not the highest device in the smart meter system 100 among the devices that collect events from a plurality of lower devices is the self device. Specifically, the event status field stores “branch start” as an identifier when collecting events from a plurality of lower-level communication devices 102 and becoming the highest-level device in the smart meter system 100. When the communication device 102 is connected to the terminal 103, the event status field stores “terminal” as an identifier.

  For example, the record 331-1 illustrated in FIG. 9 indicates that the event of the task delegation request message 314 indicated by the message ID “0x153959b2” is collected from two or more communication devices 102 among the lower-level communication devices 102. Yes. The record 331-2 indicates that the corresponding communication apparatus 102 that has received the task delegation request message 314 indicated by the message ID “0x15638092” is connected to the terminal 103.

  FIG. 10 is an explanatory diagram showing a format example of the event request message 332. The table includes two fields: event and message ID. The event field stores the event requested by the task delegation request message 314. The message ID of the task delegation request message 314 is stored in the message ID field. For example, the event request message 332 illustrated in FIG. 10 indicates that the requested event is building temperature information and the message ID is “0x153959b2”.

  The smart meter system 100 according to the present embodiment performs task delegation and event collection based on the functions shown in FIG. 3 and the data shown in FIGS. Next, a state where tasks are delegated in the smart meter system 100 and a state where events are collected will be described with reference to FIGS.

  FIG. 11 is an explanatory diagram (part 1) illustrating a state in which tasks are delegated. In the smart meter system 100 illustrated in FIG. 11, the server 101 transmits a task delegation request message 314 to the communication device 102 -G. The communication apparatus 102-G detects the communication apparatus 102 that can acquire the event stored in the event field of the task delegation request message 314 from the route information table 104-G. From the route information table 104-G, there is one communication device 102-E that can acquire building temperature information. Therefore, the communication apparatus 102-G does not add a record to the message storage table 331-G, and transmits the task delegation request message 314 to the communication apparatus 102-E without changing it.

  FIG. 12 is an explanatory diagram (part 2) of the task being delegated. The smart meter system 100 illustrated in FIG. 12 is in a state where the communication device 102-E has received the task delegation request message 314 from the communication device 102-G. The communication device 102-E detects from the route information table 104-E the communication device 102 that can acquire the event stored in the event field of the task delegation request message 314. From the route information table 104-E, the number of communication devices 102 that can acquire building temperature information is one communication device 102-C. Therefore, the communication device 102-E does not add a record to the message storage table 331-E, and transmits the task delegation request message 314 to the communication device 102-C without changing it.

  FIG. 13 is an explanatory diagram (part 3) illustrating a state where tasks are delegated. The smart meter system 100 illustrated in FIG. 13 is in a state where the communication device 102-C has received the task delegation request message 314 from the communication device 102-E. The communication device 102-C detects the communication device 102 that can acquire the event stored in the event field of the task delegation request message 314 from the route information table 104-C. Two communication devices 102 that can acquire building temperature information are the communication device 102-A and the communication device 102-B based on the route information table 104-C.

  Thus, since a plurality of communication devices 102 are detected, the communication device 102-C sets the multi-communication device event branch completed flag of the task delegation request message 314 from “not branched” to “branched”. Subsequently, the communication apparatus 102-C adds a new record to the message storage table 331-C, sets the value of the message ID field of the task delegation request message 314 in the message ID field, and “starts branching” in the event status field. Set. After the setting, the communication apparatus 102-C selects the communication apparatus 102-A as the communication apparatus 102 that delegates the task, and transmits a task delegation request message 314 in which the field value is changed to the communication apparatus 102-A.

  FIG. 14 is an explanatory diagram (part 4) illustrating a state in which tasks are delegated. In the smart meter system 100 illustrated in FIG. 14, the communication device 102 -A has received the task delegation request message 314 from the communication device 102 -C. The communication device 102-A does not have the lower-level communication device 102 and is connected to the terminal 103-A1. In this state, the communication apparatus 102-A adds a new record to the message storage table 331-A, sets the value of the message ID field of the task delegation request message 314 in the message ID field, and sets “end” in the event status field. Set. Further, the communication device 102-A determines the value of the multi-communication device event branching flag field of the task delegation request message 314.

  In the example of FIG. 14, since the multi-communication device event branching flag field is “branched”, it indicates that the higher-level communication device 102 collects events. Accordingly, the communication device 102-A transmits the event request message 332 to the communication device 102-C. The manner in which the event request message 332 is transmitted will be described later with reference to FIG.

  FIG. 15 is an explanatory diagram showing a state in which the event request message 332 has been transmitted. The smart meter system 100 illustrated in FIG. 15 is in a state where the communication device 102-C has received the event request message 332 from the communication device 102-A. The communication apparatus 102-C receives the event request message 332 and adds route information to the event collection table 402-C. In the example of FIG. 15, the communication device 102-C sets “temperature information” in the event type field, “building” in the measurement target field, and “communication device 102-A” in the collection destination identification information field.

  Further, the communication apparatus 102-C determines whether the same message ID as the message ID field of the event request message 332 exists in the message storage table 331-C, and the event state of the corresponding record is “branch start”. to decide. In the example of FIG. 15, since the condition is met, the communication device 102-C does not transmit the event request message 332 to the communication device 102-E.

  FIG. 16 is an explanatory diagram showing a state in which the event 333 is collected. The smart meter system 100 illustrated in FIG. 16 illustrates a state in which an event 333 is transmitted from the communication device 102-B and received by the communication device 102-C. The communication apparatus 102-C determines whether route information corresponding to the received event 333 is registered in the event collection table 402-C. In the example of FIG. 16, it is assumed that the record 1601 is corresponding route information. The communication device 102-C transmits the received event 333 to the communication device 102-A according to the record 1601.

  Next, a flowchart of task delegation execution processing for performing the operations shown in FIGS. 11 to 16 will be described with reference to FIG. The task delegation execution process is a process executed when the load on the server 101 increases.

  FIG. 17 is a flowchart illustrating an example of task delegation execution processing in the smart meter system 100. The task delegation execution process executes five processes: a task delegation process, a route information setting process, an event collection process, and a task completion process. The task delegation process includes a server task delegation process executed by the server 101 and a communication apparatus task delegation process executed by the communication apparatus 102.

  The server 101 executes server task delegation processing (step S1701). Next, the communication device 102 executes communication device task delegation processing (step S1702). After the task delegation process is determined by the communication apparatus task delegation process, the communication apparatus 102 executes a route information setting process (step S1703). After the route information is set, the communication device 102, which is the host device of the communication device 102 to which the task is delegated, executes event collection processing (step S1704). After the events are collected, the communication device 102 to which the task has been delegated executes a task completion process (step S1705), and the smart meter system 100 ends the task delegation execution process.

  FIG. 18 is a flowchart illustrating an example of task delegation processing in the server 101. The server 101 receives a task from the control unit 301 (step S1801). If the task has a task ID, the server 101 may accept the task ID from the control unit 301. Subsequently, the server 101 determines whether or not it has the communication device 102 at the lower level (step S1802). If there is no communication device 102 (step S1802: No), the server 101 ends the task delegation process because there is no communication device 102 to delegate the task. In this case, the server 101 executes the task that was scheduled to be delegated as it is.

  When the communication apparatus 102 is included (step S1802: Yes), the server 101 parses the received task and generates task information 313 (step S1803). Specifically, the server 101 obtains a part corresponding to the process name, event, result notification condition, and process division flag from the received task from the syntax analysis, and generates task information 313. The process division flag is set with reference to the process division table 311.

  After generating the task information 313, the server 101 generates a task delegation request message 314 from the task information 313 (step S1804). Specifically, the server 101 adds a multiple communication device event branched flag field and a message ID field to the task information 313 to generate a task delegation request message 314. Note that “unbranched” is set in the multi-communication device event branched flag field, and the message ID field is set with reference to the message task relation table 312.

  After the task delegation request message 314 is generated, the server 101 determines whether or not a plurality of communication devices 102 among the lower-level communication devices 102 can acquire the event stored in the event field of the task delegation request message 314 ( Step S1805). If a plurality of communication devices 102 can acquire the event (step S1805: YES), the server 101 sets the multi-communication device event branch completed flag field flag of the task delegation request message 314 to “branched” ( Step S1806).

  After the setting of the multi-communication device event branched flag field or when a single communication device 102 can acquire the event (step S1805: No), the server 101 sends a task delegation request message 314 to the lower communication device 102. (Step S1807). After the transmission, the server 101 accepts the end of the task (step S1808). Specifically, the server 101 receives the task end by receiving the task result message. After accepting the end of the task, the server 101 executes server task delegation processing. Subsequently, the communication device 102 that has received the task delegation request message 314 executes communication device task delegation processing.

  FIG. 19 is a flowchart illustrating an example of the communication device task delegation process. The communication device task delegation process is executed when a task delegation request message 314 is received from a server task delegation process executed by the server 101 or a higher-level communication device task delegation process.

  The communication device 102 receives the task delegation request message 314 (step S1901). After reception, the communication device 102 determines whether or not it has the communication device 102 at the lower level (step S1902). When there is no communication device 102 (step S1902: No), the communication device 102 determines whether or not the multi-communication device event branched flag field of the task delegation request message 314 is “branched” (step S1903). If it is “branched” (step S1903: YES), the communication apparatus 102 executes an event request message transmission process (step S1904). Details of the event request message transmission process will be described later with reference to FIG. In addition, the higher-level communication device that has received the event request message executes route information setting processing (step S1703).

  After the end of the event request message transmission process or when it is “unbranched” (step S1903: No), the communication apparatus 102 executes a process corresponding to the process name field of the task delegation request message 314 (step S1905). After executing the process, the communication apparatus 102 ends the communication apparatus task delegation process and executes a task completion process (step S1705). Further, a route information setting process is executed (step S1703).

  When the communication device 102 is included (step S1902: Yes), the communication device 102 determines whether or not the plurality of communication devices 102 among the lower-level communication devices 102 can acquire the event in the event field of the task delegation request message 314. (Step S1906). When a plurality of communication devices 102 can acquire the corresponding event (step S1906: Yes), the communication device 102 determines whether or not processing division is possible (step S1907). The determination of whether or not the process division is possible can be made by referring to the process division flag field of the received task delegation request message 314.

  If the process can be divided (step S1907: YES), the communication apparatus 102 transfers the task delegation request message 314 to all lower-level communication apparatuses 102 that can acquire the event (step S1908). As a result, the task is divided and processed.

  If the process division is not possible (step S1907: NO), the communication apparatus 102 executes an event branch setting process (step S1909). Details of the event branch setting process will be described later with reference to FIG. When the single communication device 102 can acquire the event (step S1906: No), the communication device 102 transmits the task delegation request message 314 to the lower communication device 102 that can acquire the event (step S1910). .

  The communication apparatus 102 that has transmitted the task delegation request message 314 in steps S1908 to S1910 ends the communication apparatus task delegation process. Subsequently, the lower-level communication device 102 that has received the task delegation request message 314 executes communication device task delegation processing.

  FIG. 20 is a flowchart illustrating an example of event branch setting processing in the communication apparatus 102. The event branch setting process is executed when the route of step S1907: No is passed. The communication device 102 determines whether or not the multi-communication device event branched flag field of the task delegation request message 314 is “branched” (step S2001). If it is “unbranched” (step S2001: No), the communication device 102 sets the multi-communication device event branch completed flag field of the task delegation request message 314 to “branched” (step S2002).

  Subsequently, the communication apparatus 102 adds a new record to the message storage table 331 (step S2003), and sets the message ID of the task delegation request message 314 in the message ID field of the added record (step S2004). After storage, the communication apparatus 102 sets “branch start” in the event branch state field of the added record (step S2005).

  After the process of step S2005 is completed, or when it is “branched” (step S2001: Yes), the communication apparatus 102 selects the communication apparatus 102 that delegates the task from the lower-level communication apparatuses 102 (step S2006). As a specific selection method, the communication device 102 may be selected at random from among the lower-level communication devices 102, or the communication device 102 that is likely to transmit many events is selected as the communication device 102 that delegates the task. May be.

  After the selection, the communication device 102 transmits a task delegation request message 314 to the selected communication device 102 (step S2007). After the transmission, the communication apparatus 102 ends the event branch setting process. The selected communication device 102 executes communication device task delegation processing (step S1702).

  FIG. 21 is a flowchart illustrating an example of an event request message transmission process in the communication apparatus 102. The event request message transmission process is executed when the route of step S1903: Yes is passed. The communication apparatus 102 generates an event request message 332 from the received task delegation request message 314 (step S2101). Specifically, the communication apparatus 102 generates an event request message 332 from the event field and message ID field of the task delegation request message 314.

  Subsequently, the communication apparatus 102 adds a new record to the message storage table 331 (step S2102). After the addition, the communication apparatus 102 sets the message ID of the task delegation request message 314 in the message ID field of the added record (step S2103). After the setting, the communication apparatus 102 sets “end” in the event branch state field of the added record (step S2104).

  After setting in the message storage table 331, the communication device 102 transmits an event request message 332 to the higher-level communication device 102 (step S2105). If the upper level is the server 101, the communication apparatus 102 transmits an event request message 332 to the server 101. After the process of step S2105 is completed, the communication apparatus 102 executes the process of step S1905.

  FIG. 22 is a flowchart illustrating an example of route information setting processing in the communication apparatus 102. The path information setting process is executed from the communication apparatus task delegation process executed by the lower communication apparatus 102 or the path information setting process executed by the lower communication apparatus 102.

  The communication device 102 receives the event request message 332 (step S2201). Subsequently, the communication apparatus 102 determines whether the same message ID as the message ID field of the received event request message 332 exists in the message storage table 331 (step S2202). If the same message ID exists (step S2202: YES), the communication apparatus 102 determines whether the event branch state of the record with the existing message ID is “start of branch” (step S2203).

  When the event branch state is “start of branch” (step S2203: Yes), the communication apparatus 102 sets route information in the event collection table 402 (step S2204). Specifically, as route information, the communication apparatus 102 sets an event type field and a measurement target field from the event field of the event request message 332. Further, the communication apparatus 102 sets a collection destination identification information field from the identification information of the communication apparatus 102 that is the transmission destination of the event request message 332. After setting the route information, the communication apparatus 102 executes an event collection process (step S1704).

  When the same message ID does not exist (step S2202: No), or when it is not “start of branch” (step S2203: No), the communication apparatus 102 sets route information in the event collection table 402 (step S2205). . After setting the route information, the communication apparatus 102 transmits the received event request message 332 to the upper communication apparatus 102 (step S2206). After transmitting the event request message 332, the communication device 102 executes event collection processing. In addition, the higher-level communication device 102 that has received the event request message 332 executes route information setting processing (step S1703).

  FIG. 23 is a flowchart illustrating an example of event collection processing in the communication apparatus 102. The event collection process is executed when the event 333 is received after the route information is set in step S2204 or step S2206. Note that the event transmission from the terminal 103 is performed in a predetermined cycle.

  The communication device 102 receives the event 333 from the lower-level communication device 102 (step S2301). After receiving the event 333, the communication apparatus 102 determines whether route information corresponding to the received event 333 is registered in the event collection table 402 (step S2302). As a specific determination method, the communication apparatus 102 confirms whether or not there is a record in which the received event matches the event type field of the event collection table 402, so that a route corresponding to the received event 333 is obtained. Determine that the information is registered.

  When the corresponding route information is registered (step S2302: Yes), the communication device 102 transmits the received event 333 to the communication device 102 according to the route information (step S2303). After transmitting the event 333, the communication apparatus 102 ends the event collection process. When the corresponding route information is not registered (step S2302: No), the communication apparatus 102 transmits the received event 333 to the higher-level communication apparatus 102 (step S2304), and ends the event collection process.

  FIG. 24 is a flowchart illustrating an example of task completion processing in the communication apparatus 102. The task completion process is executed after the process is executed in step S1905. The communication apparatus 102 receives the event 333 and inputs it to the delegated task (step S2401). Next, the communication apparatus 102 determines whether or not there is a result from the task (step S2402). When there is no result from a task (step S2402: No), the communication apparatus 102 transfers to the process of step S2401.

  When there is a result from the task (step S2402: Yes), the communication apparatus 102 generates a task result message (step S2403). The task result message includes two fields for storing a message ID and a task result. After the generation, the communication device 102 transmits a task result message to the higher-level communication device 102 (step S2404). When the upper communication device 102 does not exist and is the server 101, the communication device 102 transmits a task result message to the server 101. After the transmission, the communication apparatus 102 ends the task completion process.

  The server 101 that has received the task result message in step S1808 can determine which task has been completed by referring to the message task relation table 312. In addition, the communication apparatus 102 that has received the task result message may delete a record in which the message ID of the task result message matches the message ID field of the message storage table 331.

  As described above, according to the communication device, the communication program, and the communication method, when an event collection request is received from a lower device, the highest device among the devices that collect events from a plurality of lower devices It is determined whether or not an evaluation value indicating that the own apparatus is set. When set, the communication device does not transmit the collection request to the higher-level device. As a result, the communication device does not transmit an event collection request to the higher-level device, so that unused route information is not added, so that an increase in the route information of the higher-level device can be suppressed.

  Further, since the collection request is not transmitted, the communication device can reduce the communication amount in the network. Furthermore, by suppressing the increase in route information, the communication device can search faster because the population of route information to be searched becomes smaller when searching for a destination for task delegation and event collection. become.

  In addition, the communication device stores the event and the identification information of the lower device from which the event can be acquired, and when the setting information indicating whether the evaluation value is set is received from the upper device, the number of devices from which the event can be acquired. Based on the setting information, the evaluation value of the own device may be set. Thereby, the communication device can set the evaluation value according to the collected event without holding the evaluation value in advance. For example, when receiving a task delegation request using an event, the communication device can set the evaluation value of the device itself.

  Further, when the communication device receives setting information from the upper device, the communication device may set an evaluation value when there are a plurality of lower devices that can acquire the event and the setting information is not set. Good. As a result, the communication device can determine that the host device does not acquire an event from a device other than its own device, and thus can set an evaluation value and suppress an increase in route information.

  The communication method described in this embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The communication program is recorded on a computer-readable recording medium such as a hard disk, a flexible disk, a CD-ROM, an MO, and a DVD, and is executed by being read from the recording medium by the computer. The communication program may be distributed via a network such as the Internet.

DESCRIPTION OF SYMBOLS 100 Smart meter system 101 Server 102 Communication apparatus 103 Terminal 104 Path | route information table 301,324 Control part 302 Syntax analysis part 303 Generation | occurrence | production part 304,325,328 Transmission part 311 Process division | segmentation table 312 Message task relation table 313 Task information 314 Task transfer request Message 320 Storage unit 321, 326 Reception unit 322 Setting unit 323 Judgment unit 327 Addition unit 331 Message storage table 332 Event request message 333 Event

Claims (3)

When a feature quantity collection request regarding the measurement target attribute is received from a lower-level device that exists in the tree-structured network, the measurement target attribute information and the lower-level device identification information are stored in the storage area of the own device. Meanwhile, a communication device that transmits the collection request to a host device,
A storage unit that stores a combination of the attribute information of the measurement target and the identification information of the lower-level device capable of acquiring the feature amount of the attribute of the measurement target;
As an apparatus that has the highest evaluation value indicating whether or not the highest apparatus in the network is the self apparatus among the apparatuses that collect the feature quantities related to the measurement target attribute from the plurality of lower apparatuses. A receiving unit that receives setting information indicating whether or not the setting has been made from the higher-level device; and
When the setting information is received by the receiving unit, there are a plurality of the lower devices capable of acquiring the feature quantity of the attribute of the measurement target stored in the storage unit, and the setting information is the highest device A setting unit that sets the evaluation value as the highest-level device when indicating that it is not set to,
When receiving the collection request, a determination unit that determines whether the evaluation value set by the setting unit indicates the highest-level device;
A control unit that controls not to transmit the collection request to the higher-level device when the determination unit determines that the evaluation value is the highest-level device;
A communication apparatus comprising: Receiving a feature amount collection request relating to a measurement target attribute from a lower-level device that exists in a tree-structured network, the measurement target attribute information and the lower-level device identification information are stored in a storage area of a specific device. However, the storage unit stores the combination of the attribute information of the measurement object and the identification information of the lower apparatus that can acquire the feature amount of the attribute of the measurement object by transmitting the collection request to the upper apparatus. A communication program to be executed by a communication device,
A device having the highest evaluation value indicating whether or not the highest device in the network is the specific device among the devices that collect the feature quantities related to the measurement target attribute from the plurality of lower devices. Receiving setting information indicating whether or not it is set as from the higher-level device,
When the setting information is received, there are a plurality of lower-level devices that can acquire the feature quantity of the measurement target attribute stored in the storage unit, and the setting information is set in the highest-level device. When indicating that there is no, set the evaluation value as the top-level device,
When the collection request is received, it is determined whether or not the set evaluation value indicates the highest-level device;
When it is determined that the evaluation value is the highest-level device, control is performed so that the collection request is not transmitted to the higher-level device.
A communication program for causing the specific device to execute processing. Receiving a feature amount collection request relating to a measurement target attribute from a lower-level device that exists in a tree-structured network, the measurement target attribute information and the lower-level device identification information are stored in a storage area of a specific device. However, the storage unit stores the combination of the attribute information of the measurement object and the identification information of the lower apparatus that can acquire the feature amount of the attribute of the measurement object by transmitting the collection request to the upper apparatus. A communication method executed by a communication device,
A device having the highest evaluation value indicating whether or not the highest device in the network is the specific device among the devices that collect the feature quantities related to the measurement target attribute from the plurality of lower devices. Receiving setting information indicating whether or not it is set as from the higher-level device,
When the setting information is received, there are a plurality of lower-level devices that can acquire the feature quantity of the measurement target attribute stored in the storage unit, and the setting information is set in the highest-level device. When indicating that there is no, set the evaluation value as the top-level device,
When the collection request is received, it is determined whether or not the set evaluation value indicates the highest-level device;
When it is determined that the evaluation value is the highest-level device, control is performed so that the collection request is not transmitted to the higher-level device.
A communication method in which the specific device executes processing.

Images