JP2014160901A - Communication system, device, communication method, communication program, and server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a server and devices to efficiently collect data.SOLUTION: A server 2 outputs to respective devices, path table data which associates entry identifiers (Entry) from 0 to m-1, identifiers of transfer destination devices generated by adding 2to the identifiers (Entry) of the corresponding devices, and addresses of the transfer destination devices. A device 1 comprises: path table control means 22 which receives the path table data 11 of the device from the server 2, and stores the path table data 11 of the device; and control means 21 which, when the device 1 receives request data from the server 2 or another device, sets the received request data and transmits the request data to another device according to the path table data 11, and also transmits response data to the received request data to the other device or the server 2 having transmitted the request data.

Description

  The present invention relates to a communication system, a device, a communication method, a communication program, and a server including a server and a plurality of devices that can communicate with each other and are connected to the server.

  In recent years, services that collect large amounts of data and use the collected data have attracted attention. Data collection from a web server or the like arranged on a communication network such as the Internet is the mainstream. In the future, a variety of devices such as home appliances and sensors installed in homes and offices will be considered as data transmission sources. These devices are large in number and periodically transmit information to a server or the like.

  Therefore, a server-side facility that collects data from these devices needs to collect high-frequency data from enormous devices without loss. Therefore, it is expected that a large-scale resource is required for the server. Further, each time a new device appears, the load on the server increases dramatically, and further, it is necessary to make an investment for further increasing the scale of the server to cope with the load.

  On the other hand, a technique for efficiently collecting data from an enormous amount of equipment is expected. In general, data from home appliances, sensors, and the like is generally transmitted to a server via one or more gateway devices installed in a home or office. By using this gateway device, it is expected to reduce the cost of the server and improve the data collection performance.

  In general, a method for efficiently broadcasting data to a ring network device is proposed (see Non-Patent Document 1). Non-Patent Document 1 discloses a method of transmitting a response directly to a broadcast transmission source when transmitting a response to data, or a method of transmitting a response by tracing the broadcast route in reverse.

El-Ansary, Sameh and Brand, Per and Haridi, Seif, et al. (2003) Efficient broadcast in structured P2P networks. 2nd International Workshop On Peer-To-Peer Systems (IPTPS'03), 20-21 Feb 2003, Berkeley , CA, USA.

  However, there is a problem that the method described in Non-Patent Document 1 cannot be used in communication between a broadcast transmission source server and a gateway device that transmits a response.

  When the responses are directly transmitted from the gateway device to the server, the responses from the respective gateway devices are concentrated on the server, which causes a problem that the server has to process a large number of responses.

  In order to solve the above problem, there are also two problems when the gateway device transmits a response by tracing back the broadcast route. The first problem is that the load continues to be concentrated on the gateway device closer to the server. Unless the broadcast path represented by the tree structure is changed, the load continues to be biased to the gateway device. Generally, gateway devices installed in homes and offices handle such a large amount of data because it is practically difficult to handle a large amount of communications compared to servers and general personal computers. This is considered difficult in practice.

The second is a problem of waiting time. In the tree-like topology, each gateway device goes through the same number of gateway devices as the broadcast transmission from the server. This increases the waiting time for the server to receive all responses.

  Therefore, a communication method that allows the server and each device to efficiently collect data is expected.

  Accordingly, an object of the present invention is to provide a communication system, a device, a communication method, a communication program, and a server in which the server and each device can efficiently collect data.

In order to solve the above-described problem, a first feature of the present invention relates to a communication system including a server and a plurality of mutually communicable devices connected to the server. In the first feature of the present invention, each of the plurality of devices is assigned an identifier of any integer value from 0 to 2 ^m −1. The server corresponds to each of a plurality of devices with an entry identifier (Entry) from 0 to m−1, an identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device. Route table output means for outputting the attached route table data, request transmission means for sending request data for data collection to one of the plurality of devices as a representative device, and data from the device Data receiving means for receiving. When the device receives the routing table data of the device from the server and receives the request data from the server or another device, the device changes the received request data according to the routing table data, and transmits the received request data to the other device. Control means for transmitting response data to the request data to another apparatus or server is provided. The request data transmitted by the server to the representative device indicates an aggregation allocation range in which the representative device specifies the lower limit value and upper limit value of the identifier of the device that aggregates the data, and indicates a range in which the request data is spread between the devices. To m, and the aggregated transmission destination address in which the address of the representative device is set. When the control means of the device receives (1) the request data, it stores the aggregated transmission destination address of the received request data and the aggregate allocation range, and (2) when the transfer depth of the received request data is 0, Response data including the own device aggregated data aggregated by the device is generated and transmitted to the aggregate transmission destination address. (3) When the response data is received, the aggregated data included in the received response data is converted into the own device aggregated data. When the merged self-device aggregate data satisfies all the aggregate allocation ranges of the received request data, response data including the self-device aggregate data is transmitted to the aggregate transmission destination address, and (4) the received request When the data transfer depth is not 0, with reference to the routing table data, for each entry identifier of 0 or more and less than the transfer depth, the entry identifier In order, for an entry identifier having an identifier of a device within the aggregate allocation range received by the device, the aggregate transmission destination address of the received request data is the device closest to the upper limit value of the aggregate allocation range received by the device. For the entry identifier having an identifier, the aggregated transmission destination address received by the device is set, and for the other entry identifiers, the address of the device associated with the entry identifier incremented in the entry identifier in the routing table data The aggregate allocation range is set to the range of the device identifier corresponding to the entry identifier from the device identifier of the entry identifier 0 in the routing table data, and the transfer range is changed to the entry identifier. The request data is the entry identifier in the routing table data. The process of transmitting the address of the corresponding device repeats.

  Here, when the control unit generates the changed request data from the received request data, if the device is a representative device, the aggregate transmission destination address is set to the address of the representative device, and the aggregate allocation range is In the routing table data, the device identifier corresponding to the entry identifier-1 may be set within the range of the device identifier corresponding to the entry identifier, and the transfer range may be set as the entry identifier.

A second feature of the present invention relates to an apparatus in a communication system including a server and a plurality of apparatuses that can communicate with the server. The device according to the second aspect of the present invention is given an integer identifier of 0 to 2 ^m −1. The device stores route table data in which an entry identifier (Entry) from 0 to m−1, an identifier of a transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device are associated with each other. When the request data is received from the server or other device, the received request data is changed according to the routing table data and transmitted to the other device, and the response data for the received request data is transmitted to the other device or server. The control means to perform is provided. The request data transmitted from the server to the device indicates an aggregation allocation range that specifies the lower limit value and the upper limit value of the identifier of the device for which the device aggregates data, and indicates a range in which the device spreads the request data from 0 It includes a transfer depth that takes values up to m and an aggregate transmission destination address that is a transmission destination of response data. When the control means receives (1) the request data, it stores the aggregated transmission destination address of the received request data and the aggregate allocation range. (2) If the transfer depth of the received request data is 0, the control device Generate response data including the aggregated own device aggregated data, send it to the aggregated transmission destination address, and (3) upon receiving the response data, merge the aggregated data included in the received response data into the own device aggregated data Then, the merged own device aggregated data satisfies the aggregate allocation range of the received request data, and transmits response data including the own device aggregated data to the aggregate transmission destination address. (4) Transfer of received request data If the depth is not 0, the routing table data is referenced, and for each entry identifier that is 0 or more and less than the transfer depth, the entry identifiers are assigned in descending order. For the entry identifier having the identifier of the device within the aggregate allocation range received by the device, the aggregate transmission destination address in the received request data has the identifier of the device closest to the upper limit value of the aggregate allocation range received by the device. The entry identifier is set by taking over the aggregated transmission destination address received by the device, and the other entry identifier is set in the routing table data to the address of the device associated with the incremented entry identifier. The aggregated allocation range is set to the range of the device identifier corresponding to the entry identifier from the device identifier of the entry identifier 0 in the routing table data, and the transfer range is changed to the entry identifier. Corresponding to the entry identifier in the routing table data The process of transmitting the location of the address is repeated.

  Here, if the device is a representative device that has received request data from the server, the control means sets the aggregated transmission destination address to the address of the device when generating changed request data from the received request data. Then, the aggregate allocation range may be set in the route table data from the device identifier of the entry identifier-1 to the device identifier range corresponding to the entry identifier, and the transfer range may be set in the entry identifier.

A third feature of the present invention relates to a communication method used for an apparatus in a communication system including a server and a plurality of apparatuses capable of communicating with each other connected to the server. In the third feature of the present invention, the device is given an identifier having an integer value of 0 to 2 ^m −1, and an entry identifier (Entry) from 0 to m−1, A step of receiving routing table data in which the identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier and the address of the transfer destination device are associated with each other. The request data transmitted from the server to the device includes an aggregate allocation range that specifies the lower limit value and upper limit value of the identifier of the device that the device aggregates data, and a range in which the request data is spread between the device and another device. The transfer depth that takes a value from 0 to m and the aggregated transmission destination address that is the transmission destination of the response data are included. The communication method includes (1) when the device receives the request data, storing an aggregate transmission destination address of the received request data and an aggregate allocation range; and (2) a transfer depth of the received request data by the device. Is 0, a step of generating response data including own device aggregated data aggregated by the device and transmitting it to the aggregated transmission destination address; and (3) when the device receives the response data, When the aggregated data included is merged with the aggregated data of the own device and the aggregated data of the own device satisfies all the aggregate allocation ranges of the received request data, the response data including the aggregated data of the own device is And (4) when the transfer depth of the received request data is not 0, the device refers to the route table data, For each entry identifier less than the above transfer depth, for the entry identifier having the identifier of the device within the aggregate allocation range received by the device in descending order of the entry identifier, the aggregate transmission destination address of the received request data for the entry identifier For the entry identifier having the identifier of the device closest to the upper limit value of the aggregate allocation range received by the device, taking over the aggregated transmission destination address received by the device and setting the entry in the routing table data for the other entry identifiers. Set the identifier to the address of the device associated with the incremented entry identifier, and set the aggregate allocation range from the device identifier of entry identifier 0 to the range of device identifiers corresponding to the entry identifier in the routing table data; Change the transfer range to the entry identifier The request data, the process of transmitting the address of the device corresponding to the entry identifier in the path table data, comprising the step of repeating.

  Here, if the device is a representative device that has received request data from the server, the control means uses the aggregated transmission destination address as the address of the representative device when generating changed request data from the received request data. The aggregation allocation range may be set to the range of the device identifier corresponding to the entry identifier from the device identifier of the entry identifier-1 in the routing table data, and the transfer range may be set to the entry identifier. good.

  A fourth feature of the present invention relates to a communication program for causing a computer to function as each unit of the device according to the second feature of the present invention.

A fifth feature of the present invention relates to a server of a communication system including a server and a plurality of devices including a representative device connected to the server and capable of communicating with each other. In the server relating to the fifth aspect of the present invention, each of the plurality of devices is assigned an identifier of any integer value from 0 to 2 ^m −1, and each of the plurality of devices from 0 to m−1. A route table output means for outputting route table data in which the entry identifier (Entry) of the device, the identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and the address of the transfer destination device are associated with each other; Among the devices, one device as a representative device includes request transmission means for transmitting request data for data collection, and data reception means for receiving data from the device. The request data transmitted from the server to the representative device is a transfer that takes a value from 0 to m indicating the aggregate allocation range that identifies the device that the representative device aggregates data and the range in which the request data is diffused between the devices. A depth, and an aggregate transmission destination address in which the address of the representative device is set.

  According to the present invention, it is possible to provide a communication system, a device, a communication method, a communication program, and a server that enable the server and each device to efficiently collect data.

It is a figure explaining the system configuration | structure of the communication system which concerns on embodiment of this invention. It is a figure explaining ID space of the apparatus of the communication system which concerns on embodiment of this invention. It is a figure explaining an example of the data structure of the request data of the communication system which concerns on embodiment of this invention. It is a figure explaining an example of the data structure of the response data of the communication system which concerns on embodiment of this invention. It is a figure explaining the hardware constitutions and functional block of the server which concern on embodiment of this invention. It is a figure explaining an example of the data structure of the apparatus list data of the server which concerns on embodiment of this invention. It is an example of the data structure and data of the routing table data which the server which concerns on embodiment of this invention produces | generates. It is a figure explaining the hardware constitutions and functional block of the apparatus which concern on embodiment of this invention. It is a figure explaining an example of the data structure of the sequence setting data of the apparatus which concerns on embodiment of this invention. It is a figure explaining the control processing by the control means of the apparatus which concerns on embodiment of this invention. It is a figure explaining the spreading | diffusion process by the spreading | diffusion means of the apparatus which concerns on embodiment of this invention. It is a figure explaining the aggregation process by the aggregation means of the apparatus which concerns on embodiment of this invention. It is a figure explaining the data flow of the communication method which concerns on embodiment of this invention. It is a figure explaining the flow of data in the 1st phase of the communication method concerning an embodiment of the invention. It is a figure explaining the flow of the data in the 2nd phase of the communication method which concerns on embodiment of this invention. It is a figure explaining the flow of the data in the 3rd phase of the communication method which concerns on embodiment of this invention. It is a figure explaining the flow of data in the 4th phase of the communication method concerning an embodiment of the invention. It is a figure explaining the flow of data in the 5th phase of the communication method concerning an embodiment of the invention. It is a figure explaining the flow of data when ID is missing in the communication method concerning an embodiment of the invention. It is a figure explaining the data flow of the communication method which concerns on the 1st modification of this invention. It is a figure explaining the spreading | diffusion process by the spreading | diffusion means of the apparatus which concerns on the 1st modification of this invention. It is a figure explaining the effect of the communication method which concerns on embodiment of this invention, and the communication method which concerns on a 1st modification. It is a figure explaining the data flow of the conventional communication method.

  Next, embodiments of the present invention will be described with reference to the drawings. In the following description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

  In the embodiment of the present invention, the notation [a, b] indicates “a or more and b or less”, and the notation [a, b) indicates “a or more and less than b”.

  In the embodiment of the present invention, “spreading” refers to distributing the request data transmitted by the server to a plurality of devices specified by the server. “Aggregation” refers to collecting data held by each device between devices or in a specific device. “Collecting” means that the server receives data collected by a plurality of devices specified by the server in response to request data transmitted by the server.

(Communications system)
The communication system 3 according to the embodiment of the present invention includes a server 2 and a plurality of devices 1a, 1b, 1c,. When there is no particular distinction between the plurality of devices 1a, 1b, 1c,... In the communication system 3 according to the embodiment of the present invention, “spreading”, “aggregation”, and “collection” of data are performed.

  In the embodiment of the present invention, the device 1 is, for example, a gateway device installed in a home or office. The device 1 is connected to devices (not shown) such as home appliances and sensors installed in a home or office. The device 1 transmits data received from these devices directly to the server 2 or indirectly to the server 2 via other devices. In the embodiment of the present invention, the device 1 that receives a request from the server 2 may be particularly referred to as a representative device. The representative device is determined by the server 2. The representative device may always be the same device, or may be changed at every request. A plurality of devices including the representative device can be connected to each other, and can also be connected to the server 2.

  The server 2 requests each device 1 to transmit data and receives data collected in response to the request.

  In the communication system 3 shown in FIG. 1, the server 2 and the apparatus 1 are connected by an IP network such as the Internet or NGN. The devices 1 can communicate with each other at least at the IP layer level, and construct an overlay (P2P) network on the IP network.

Each device 1 is divided into at least one or more groups. In the example shown in FIG. 1, the devices 1a, 1b, and 1c belong to the first group G1, and the other devices belong to the second group G2. The server 2 holds a list of devices belonging to each group and a group size m corresponding to the size of each group. A plurality of devices belonging to each group are assigned a device ID of any integer value from 0 to 2 ^m −1 so that they do not overlap with other devices.

  The server 2 transmits request data independently for each group, and collects data of the devices 1 belonging to the group. When the server 2 transmits request data to a specific group of devices, the server 2 transmits the request data to the representative device of the group. The representative device transmits the request data directly or indirectly to other devices in the group. This representative device may always be the same device or may be changed each time a request is transmitted. The representative device transmits the data transmitted by each device to the server 2 or a server designated by the server.

In the embodiment of the present invention, each group uses an integer value from 0 to 2 ^m −1 as the ID space of the device 1 as shown in FIG. Each device 1 is logically arranged in a ring topology. Each device 1 may be logically arranged in a ring topology, and may actually be arranged in a tree topology capable of communicating with each other at the IP layer level.

Since the group shown in FIG. 2 has 16 devices corresponding to m = 4, IDs from 0 to 15 are assigned to each device. In the example illustrated in FIG. 2, the ascending direction of the ID is a forward direction, and in this forward direction, ID = 2 ^m −1 returns to ID = 0.

  In the embodiment of the present invention, the server 2 transmits request data to the representative device. The representative device transmits request data obtained by appropriately changing the received request message to another device 1 or transmits response data to the server 2.

  With reference to FIG. 3, request data according to the embodiment of the present invention will be described. The request data includes items of a sequence number, an aggregation allocation range, a transfer depth, a collection destination address, an aggregation transmission source, route update information, and a collection target list.

  The sequence number identifies the request transmitted by the server 2. The sequence number may be expressed as “Sequence” in this specification and the like. Each time the server 2 issues a request, it simply increments the sequence number. As a method of increasing the sequence number, a method of incrementing, a method of setting the transmission time or the clock value of the server 2 to the sequence number, and the like can be considered. The sequence number is not rewritten when the device 1 spreads the request, and the aggregated data of each device 1 aggregated for one sequence number is finally associated with the sequence number. It is included in one response data and transmitted to the server 2.

The aggregation allocation range specifies the lower limit value and the upper limit value of the device ID for the device that receives the request and the device 1 that aggregates the data. The aggregate allocation range may be expressed as “Allot” in this specification and the like. Further, when the range of IDs of the aggregation target devices 1 is limited to a part of the ring shown in FIG. 2, the aggregation allocation range indicates from an arbitrary lower limit value s to an arbitrary upper limit value t in the forward direction [s. , T]. At this time, the server 2 transmits request data to the representative device with the device whose device ID is s as the representative device. In the request data, the ID of the device 1 that the server 2 wants to collect data is set in the aggregate allocation range. Each device 1 that has received the request data sets the ID range of the device 1 to be aggregated by the device to which the request data is to be spread when the request data is spread. When the server 2 aggregates data from all the devices 1 belonging to the group, the server 2 sets the ID of the representative device and a value obtained by adding 2 ^m −1 to the ID of the representative device as the aggregation allocation range. However, if the value after adding 2m-1 to ID of the representative device is not less than ^{2 m,} a value obtained by subtracting ^{2 m} from the value obtained by adding ² m -1 in ID of the representative device, i.e., the ID of the representative apparatus The value is -1. Further, in the ^{2 4} ID space as shown in FIG. 2, when it is set aggregate allocation range [13, 2] represents the range from the lower value 13 to the upper limit value 2 in the forward direction, device ID = 13, 14, 15, 0, 1, and 2 are indicated.

The transfer depth indicates the depth at which the request is transferred. The transfer depth may be expressed as “Degree” in this specification and the like. The transfer depth is determined according to the aggregate allocation range. For example, when the aggregate allocation range is [s, t], the transfer depth is a round-up number of log ₂ (t−s + 1). Further, in the case of all the devices 1 whose aggregate allocation range belongs to the group, the transfer depth is m.

  The collection destination address is an address of a server that is a collection destination that is designated when the server 2 that transmitted the request wants to collect data collected by a server other than itself. The collection destination address may be expressed as “Collector” in this specification and the like. The collection destination address is arbitrarily designated in the IP address or FQDN (Fully Qualified Domain Name) format.

  The aggregate transmission destination is a transmission destination address of the aggregate data. The aggregate transmission destination may be described as “Nexthop” in this specification and the like. In the request data transmitted by the server 2, the IP address of the representative device is set as the aggregate transmission destination. When the device 1 spreads request data to other devices, the spreading device 1 appropriately sets the aggregate transmission destination.

  The route update information is arbitrarily set as a new device 1 joins the group or the device 1 leaves the group. The route update information may be described as “Updates” in this specification and the like. The route update information will be described later in detail.

  The collection target list includes items of data to be collected by each device 1. The collection target list includes, for example, the types of sensors to be collected and items of data acquired by the sensors. The collection target list is appropriately set by the server 2.

  With reference to FIG. 4, the response data according to the embodiment of the present invention will be described. The response data includes items of a sequence number, an aggregation range, and aggregated data.

  The sequence number is given the same number as the sequence number set in the request data corresponding to the aggregated data. The sequence number may be expressed as “Sequence” in this specification and the like.

  The aggregation range includes an identifier of a device that aggregates the aggregation data included in the response data. The aggregation range may be expressed as “Range” in this specification and the like.

  The aggregated data is aggregated data to be transmitted toward the server 2 that transmitted the request. The aggregated data is data acquired by each device 1 from a collection target sensor or the like based on a collection target list of request data. The aggregated data may be set corresponding to the ID of the device 1 acquired from the device. In the aggregated data, the device ID and the data acquired from the device by this device are stored in association with each other, so that the device that has received the response data responds regardless of the aggregated range ("Range") setting data. It is possible to specify the identifier of the device that aggregates the aggregated data included in the data.

(server)
With reference to FIG. 5, the server 2 which concerns on embodiment of this invention is demonstrated. The server 2 is a general computer including a storage device 210, a central processing control device 220, a communication control device 230, and the like. The server 2 implements each function shown in FIG. 5 by executing a predetermined program.

  The storage device 210 stores device list data 211, update data 212, route table data 213a, 213b,.

  The device list data 211 is data in which a device ID of a device belonging to a predetermined group is associated with an IP address of the device. As illustrated in FIG. 6, the device list data 211 associates the device ID of the device 1 belonging to the group with the IP address of the device in units of groups that the server 2 transmits request data. The device IDs in the device list data 211 may not be consecutively numbered or may be missing.

  The update data 212 stores information related to joining a new device 1 and leaving the device 1 in the group.

The route table data 213a, 213b,... Is output to each of a plurality of devices 1 belonging to a predetermined group, and is referred to when each device determines a transmission destination of request data. 7, the route table data 213a, 213b,... Are prepared for each device 1. The route table data 213a, 213b,... Are respectively an entry identifier (Entry) from 0 to m−1, an ID (ID (Entry)) of a transfer destination device obtained by adding 2 ^Entry to the device ID of the device, This data is associated with the IP address (IP (Entry)) of the transfer destination device. The route table data 213a, 213b,... Does not have to be stored in the storage device 210 after the server 2 transmits to the device 1, and is stored in a storage device for work such as a RAM (Random Access Memory), for example. May be.

  The central processing control device 220 includes device list control means 221, route table output means 222, request transmission means 223, and data reception means 224.

  The device list control means 221 stores the information of the detached device 1 and the subscribed device 1 acquired by the device 1 and the server 2 itself as the update data 212 and sequentially updates the device list data 211.

  The routing table output means 222 generates routing table data 213a, 213b,... For each device belonging to a predetermined group, and outputs it to each device.

The routing table output unit 222 refers to the device list data 211 and generates a routing table according to the following procedure. Here, the routing table output unit 222 circulates and refers to the device ID of the device list data 211 so as to return to 0 which is the smallest ID after 2 ^m −1.

  First, when receiving a connection notification from the device 1, the routing table output unit 222 determines the device ID of the device 1 as x and stores it in the device list data 211. Here, the device ID of the device 1 may be determined by the device 1 and transmitted to the server 2. Next, the routing table output unit 222 creates the routing table with the device ID = x with the number of entries 0, and sets “0” in the variable Entry.

  The routing table output unit 222 sets the device ID = x as the start point of the linear search of the device list data 211. The device list data 211 is referred to in a state in which the device ID is sorted in ascending order of the device ID, with the direction from the minimum value to the maximum value of the device ID as the forward direction and circulated from the maximum value of the device ID to the minimum value of the device ID. The

The routing table output unit 222 linearly searches the device list data 211 in the forward direction, and identifies a device having a value of device ID = x + 2 ^Entry . Here, if there is no device having the value of device ID = x + 2 ^Entry , the device having the device ID searched through x + 2 ^Entry in the forward direction is specified. The routing table output unit 222 associates the specified device with the entry, the device ID, and the IP address of this device and adds them to the routing table data entry.

  The process of adding entries in the routing table data is repeated until Entry = m−1 while Entry starts from 0 and increments by one. Further, the routing table output unit 222 repeats this process for all devices belonging to the group, and generates the routing table data 213a, 213b,... For each device, and the generated routing table data 213a, 213b,. To the device.

In FIG. 7, three types of routing table data 213a, 213b and 213n are shown. The route table data 213a in FIG. 7A is transmitted to the device with m = 4 and device ID = 0. The routing table data 213a has entries from 0 to 3, and a value obtained by adding 2 ^entries to the device ID = 0 of this device is set in the ID column of each entry. The routing table data 213b in FIG. 7B is transmitted to the device with device ID = 1 at m = 4. The routing table data 213b has entries from 0 to 3, and a value obtained by adding 2 ^entries to the device ID = 1 of this device is set in the ID column of each entry. The routing table data 213n in FIG. 7C is transmitted to the device with device ID = n at m = 4. The routing table data 213a has entries from 0 to 3, and in the ID column of each entry, a value obtained by adding 2 ^entries to the device ID = n of this device is set.

In the embodiment of the present invention, a device ID of an arbitrary device ID = n may be expressed as ID _n or IDn as shown in FIG. The IP address of device ID = n may be expressed as IP _n or IPn. Further, in the path table data 213n of this ID _n, Entry = i correlated is the device ID in the record is labeled as _ID n (i), IP address of the device is denoted as _IP n (i) There is a case.

  The request transmission unit 223 transmits request data for data collection to one of the plurality of devices in the group as a representative device. The request transmission unit 223 may select a representative device at random. Further, in the group shown in FIG. 2, devices with ID = 0, devices with ID = 1, etc. may be selected in order clockwise. The request transmission unit 223 sets each data in the request data described with reference to FIG. 3, and transmits the data to the representative device.

  The request transmission means 223 sets a sequence number (Sequence) larger than the sequence number of the previously transmitted request. The request transmission unit 223 sets information for identifying a device for which the representative device aggregates data in the aggregation allocation range (Allot). The request transmission unit 223 sets a value from 0 to m indicating a range in which the request data is diffused between apparatuses in the transfer depth (Degree). The request transmission unit 223 sets the address of the representative device as the aggregate transmission destination address (Nexthop). In addition, the request transmission unit 223 sets necessary data as appropriate.

  The data receiving unit 224 receives data from the devices in the group. The data receiving unit 224 receives the response data described with reference to FIG. 4 and acquires the collection data set in the response data.

(apparatus)
With reference to FIG. 8, the apparatus 1 which concerns on embodiment of this invention is demonstrated. The device 1 is a general computer including a storage device 10, a central processing control device 20, a communication control device 30, and the like. The apparatus 1 implements each function shown in FIG. 8 by executing a predetermined communication program.

  The storage device 110 stores route table data 11, sequence setting data 12, and own device consolidated data 16.

As shown in FIG. 7, the routing table data 11 includes an entry identifier (Entry) from 0 to m−1, an identifier of the transfer destination device (ID (Entry)) obtained by adding 2 ^Entry to the identifier of the device, This data is associated with the address (IP (Entry)) of the transfer destination device. The route table data 11 is generated by the server 2 and transmitted from the server.

  The sequence setting data 12 includes data related to request data received from the server 2 or another device. As shown in FIG. 9, the sequence setting data 12 is provided for each sequence number included in the request data, and includes an aggregate transmission destination address 13, a collection destination address 14, and aggregate allocation range data 15.

  The aggregate transmission destination address 13 is data set in “Nexthop” of the received request data. The collection destination address 14 is data set in “Collector” of the received request data. The aggregate allocation range data 15 is set based on data set in “Allot” of the received request data. The aggregate allocation range data 15 is data in which an identifier of another device specified by the aggregate allocation range “Allot” is associated with a reception flag indicating whether aggregate data has been received from another device. The aggregate allocation range data 15 is generated when the request data is received and the reception flag is set to “not received”, and each time the apparatus 1 receives aggregate data from another apparatus, the aggregate allocation range data 15 of the aggregate data transmission source apparatus. The reception flag associated with the device ID is updated to “Received”.

  The own device consolidated data 16 is data received from home appliances or sensors connected to the device 1. When the own device aggregated data 16 receives aggregated data from another device, the aggregated data is also merged.

  The central processing control device 20 includes a control unit 21 and a data acquisition unit 25 that control processing of request data, response data, and the like according to the embodiment of the present invention.

  The data acquisition unit 25 acquires data from devices such as home appliances and sensors to which the device 1 is connected. The data acquisition unit 25 requests and acquires data from a device to which the apparatus 1 is connected according to information set in the request data collection target list. The data acquisition unit 25 stores the acquired data in the storage device 10 as the own device consolidated data 16. The data acquisition unit 25 may store the own device aggregated data 16 in association with the sequence number of the request data from which data is acquired.

  The control means 21 receives the routing table data 11 of the device from the server 2 and controls processing to be stored in the storage device 10. When the control means 21 receives the request data from the server 2 or another device, the control means 21 changes the received request data according to the routing table data 11 and transmits the request data to the other device. Alternatively, processing to be transmitted to the server 2 is controlled.

  When receiving the request data, the control unit 21 stores the aggregate transmission destination address (Nexthop) and the aggregate allocation range (Allot) of the received request data, and stores them in the sequence setting data 12. The control unit 21 includes a routing table control unit 22, a spreading unit 23, and an aggregating unit 24. Depending on the type and setting value of the received data, the control unit 21 processes the routing table control unit 22, the spreading unit 23, and the aggregating unit 24. Let

  The routing table control means 22 receives the routing table data of the device from the server 2 and stores it in the storage device 10. Further, the route table control means 22 updates the route table data 11 as necessary when the route update information “Updates” is included in the request data. The update process of the routing table data 11 will be described in detail later.

  The spreading means 23 transfers the request data received from the server 2 or another device to another device. When the transfer depth “Degree” of the received request data is 0, the spreading unit 23 causes the aggregation unit 24 to process new response data. If the transfer depth “Degree” of the received request data is not 0, the spreading means 23 refers to the routing table data 11, changes the request data, and transmits the changed request data to another device.

  The spreading means 23 receives the received requests in descending order of the entry identifiers for each entry identifier (each entry = i satisfying 0 ≦ Entry <Degree) that is 0 or more and less than the transfer depth (Degree) of the received request data. Generate changed request data from the data. Further, the spreading means 23 repeats the process of transmitting the changed request data to the address (IP (i)) of the device corresponding to the entry identifier (i) in the routing table data 11. At this time, processing is performed in descending order from an entry whose entry identifier is transfer depth -1. The spreading unit 23 skips the process related to the entry having the device ID outside the aggregate allocation range. For example, when the device identifier having the transfer identifier of transfer depth −1 is 8 and the aggregate allocation range is [0, 7], the processing related to the entry is skipped. Also, if the device ID with the entry identifier of transfer depth −2 is 4, since it is within the aggregate allocation range, the spreading means 23 is executed for the entry.

  Here, the spreading means 23 sets each item of the aggregate transmission destination address (Nexthop), aggregate allocation range (Allot), and transfer range (Degree) of request data. The spreading means 23 receives the aggregated destination address (Nexthop) as the aggregated destination address for the entry identifier having the device ID (i) closest to the upper limit of Allot within the range of the received Allot. Set the destination address as it is. For the other entry identifiers, the spreading means 23 sets the aggregate destination address to the address (IP (i + 1)) of the device associated with the entry identifier (i + 1) obtained by incrementing the entry identifier (i). Set. The spreading means 23 changes the aggregate allocation range (Allot) from the identifier (ID (0)) of the device with the entry identifier 0 in the routing table data 11 to the identifier range of the device (ID (i)) corresponding to the entry identifier. Set. The spreading means 23 sets the transfer range (Degree) to the entry identifier (i).

  The aggregation unit 24 transmits the response data to the other device and the server 2 together with the own device aggregation data 16 when the request data without the spreading destination is received or when the response data is received.

  When the transfer depth “Degree” of the received request data is 0, the aggregation unit 24 newly generates response data. When the transfer depth (Degree) of the received request data is 0, the aggregating unit 24 generates response data including the own device aggregated data 16 aggregated by the device 1 and transmits the response data to the aggregated transmission destination address (Nexthop).

  Further, when receiving the response data from the other device, the aggregation unit 24 merges the aggregated data included in the received response data into the own device aggregated data 16. The aggregation unit 24, when the merged own device aggregated data 16 includes aggregated data of the devices specified in the aggregated allocation range (Allot) of the received request data, the response data including the own device aggregated data 16 is Sent to the aggregate destination address (Nexthop).

  Here, the processing of the control means 21 will be described with reference to FIGS. The order of processing in FIGS. 10 to 12 is an example, and is not limited to this.

  With reference to FIG. 10, the control process by the control means 21 is demonstrated. The control unit 21 causes the route table control unit 22, the diffusion unit 23, and the aggregation unit 24 to perform processing according to the type of received data.

  In step S1, the control means 21 proceeds to step S2 when the type of received data is request data. In step S2, the control means 21 determines whether or not the newly received sequence number is larger than the previously received sequence number. If the newly received sequence number is less than or equal to the previously received sequence number, the control means 21 has already processed this request data, so the received request data is discarded and the processing ends.

  On the other hand, if the newly received sequence number is larger than the previously received sequence number, the process proceeds to step S3. In step S3, when the content of the route update is set in the route update information “Updates” field of the received request data, the control means 21 updates the route table data 11 in step S4, and proceeds to step S4. This process will be described later in detail.

  Next, sequence setting data 12 is generated corresponding to the sequence number of the received request data. Specifically, in step S <b> 5, the control unit 21 sets the set value of the aggregated transmission destination “Nexthop” of the received request data in the aggregated transmission destination address 13. In step S <b> 6, when the collection destination address “Collector” of the received request data is set, the control unit 21 sets the collection destination address “Collector” to the collection destination address 14. In step S7, the control means 21 generates aggregate allocation range data 15 based on the aggregate allocation range “Allot” of the received request data. Here, the control means 21 generates a table in which the identifier of each device 1 specified by the aggregate allocation range “Allot” is associated with the reception flag indicating whether or not the aggregated data has been received from this device. The flag is initially set to “not received”.

  Next, in step S8, the control means 21 determines whether or not the transfer depth “Degree” of the received request data is zero. If it is not 0, the process proceeds to step S9. In step S9, the spreading means 23 processes the received request.

  If it is determined in step S8 that the transfer depth “Degree” of the request data received by the control means 21 is 0, or if the data received by the control means 21 is response data in step S1, the process proceeds to step S10. . In step S10, the aggregation unit 24 processes the received request data or response data.

  On the other hand, if the data received by the control means 21 is route table data in step S1, the control means 21 stores the received route table data 11 in the storage device 10 in step S11.

  With reference to FIG. 11, the diffusion process by the diffusion means 23 according to the embodiment of the present invention will be described. Here, it is assumed that the device 1 has ID = n and holds the route table data shown in FIG. The spreading means 23 sets predetermined items of the received request and transmits request data to other devices.

Based on the routing table data 11, the diffusing unit 23 repeats the processing from step S101 to step S105 in the descending order of i for each i from i = Degree-1 to 0. Here, “Degree” is a set value of the transfer depth of the received request data. If the device corresponding to an Entry is the same as the device corresponding to an Entry that is one larger than that Entry, if IP _n (i) = IP _n (i + 1), the processing for this Entry = i is skipped, Duplicate requests are not sent.

First, in step S101, the spreading means 23 determines whether or not the ID _n (i) of the device corresponding to the entry identifier is within the range of the aggregate allocation range “Allot”. When ID _n (i) is outside the range of the aggregate allocation range “Allot”, the process for the entry identifier i is terminated, and the next i−1 is processed. If ID _n (i) is within the range of the aggregate allocation range “Allot”, the process proceeds to step S102.

In step S102, when the ID _n (i) of the entry identifier i is closest to the upper limit value of the aggregate allocation range “Allot”, the spreading means 23 does not change the aggregate transmission destination “Nexthop”. On the other hand, in other cases, IP _n (i + 1) is set to the aggregate transmission destination “Nexthop”. In step S _< b> 103, the spreading unit 23 sets [ID _n (0), ID _n (i)] in the aggregate allocation range “Allot”. In step S104, the diffusing unit 23 sets the value of i to the transfer depth “Degree”.

In step S105, the diffusing unit 23 transfers the request data rewritten by the processing in steps S102 to S104 to the IP _n (i) device. Here, the sequence number “Sequence”, the collection destination address “Collector”, the route update information “Updates”, and each item of the collection target list are not rewritten.

  When the processing from step S101 to step S105 is completed while decrementing each i from i = Degree-1 to 0, the diffusing unit 23 ends the processing.

  With reference to FIG. 12, the aggregation process by the aggregation means 24 which concerns on embodiment of this invention is demonstrated. Here, it is assumed that the device 1 has ID = n and holds the route table data shown in FIG. When the aggregation means 24 merges the received response data with its own device aggregated data 16 and receives aggregated data of all devices within the aggregate allocation range, it sets a predetermined item of response data and responds to another device. Send data.

  First, in step S201, the aggregation unit 24 determines whether or not the process is after the request data is received. In the case of processing after reception of request data, the aggregation means 24 is specifically set to 0 when the transfer depth “Degree” of the received request data is set, and the aggregation processing is performed according to the determination in step S8 of FIG. The process proceeds to S202.

In the processing from step S202 to step S204, the aggregation unit 24 generates response data. Specifically, in step S202, the aggregation unit 24 sets the setting value of the sequence number “Sequence” of the received request data to the sequence number “Sequence” of the response data. In step S203, the aggregation unit 24 sets [n, ID _n (0)) as the set value of the aggregation range “Range”. In step S <b> 204, the aggregation unit 24 sets the data acquired from the device by the own device in the aggregation data item.

  Then, it progresses to step S211. In step S211, the aggregation unit 24 generates the value set in the aggregate transmission destination address 13 of the sequence setting data 12, specifically, the address set in the “Nexthop” item of the request data in steps S202 to S204. Response data sent.

  On the other hand, if it is determined in step S201 that the process is not after receiving request data, the aggregation unit 24 proceeds to step S205. In the processing from step S205 to step S212, the aggregation unit 24 processes the response data generated and transmitted by another device.

  First, in step S205, the aggregation unit 24 merges the aggregated data included in the received response data with its own apparatus aggregated data 16 in step S205. Further, in step S206, the aggregation unit 24 updates the aggregate allocation range data 15 corresponding to the value of the sequence number “Sequence” included in the received response data. Specifically, the aggregating unit 24 changes the reception flag associated with the device identifier set in the aggregation range “Range” of the received response data to “Received”.

  In step S207, the aggregation unit 24 refers to the aggregate allocation range data 15 and determines whether or not all the reception flags of the aggregate allocation range data 15 are set to “Received”. If it is not set to have been received, the process ends as it is in order to wait for response data from the “unreceived” device.

On the other hand, if it is determined in step S207 that all the reception flags of the aggregate allocation range data 15 are set to “Received”, response data to be transmitted to another device is generated. Specifically, in step S208, the aggregation range “Range” of the received response data is updated to the device range corresponding to the own device aggregation data generated in step S205. For example, when the aggregation range “Range” of the received response data is [s, n), it is corrected to [s, ID _n (0)). In step S209, the aggregating unit 24 sets the own apparatus aggregated data 16 in the aggregated data of the received response data. In other words, aggregated data of all devices that should be aggregated by this device 1 is set as aggregated data of response data transmitted by this device 1.

  Next, in step S210, it is determined whether the own apparatus is a representative apparatus. If it is not a representative device, the aggregation unit 24 transmits the response data updated in steps S208 to S209 to the address set in the aggregate transmission destination address 13 of the sequence setting data 12 in step S211. On the other hand, in the case of a representative device, in step S212, the aggregation unit 24 updates the collection destination address 14 when the collection destination address 14 is set, or updates the server 2 when the collection destination address 14 is not set, in steps S208 to S209. Send response data.

(Concrete example)
Next, a communication method according to an embodiment of the present invention will be described with reference to FIGS. This communication method will be described on the premise of a group including each device having m = 4 and an address space of ID = 0 to ID = 15. Here, the representative device is a device with ID = 0.

  In the example shown in FIG. 13 to FIG. 18, the diffusion processing or aggregation processing of one device 1 will be described as a processing unit indicated by one phase. For example, when one apparatus 1 transmits data to a plurality of other apparatuses in the spreading process, the process is performed within one phase. If processing of one device and processing of another device can be performed in parallel, the processing of these devices is also processing within one phase. In the examples shown in FIGS. 13 to 18, (a) shows the data flow in spreading, and (b) shows the data flow in aggregation. FIG. 13 shows the data flow from the first phase to the fifth phase. FIG. 14 to FIG. 18 show the flow of data between devices in each phase from the first phase to the fifth phase, respectively. The data flow in the phase is a solid line, and the data flow before the phase is a broken line. It shows with. In FIG. 14 to FIG. 18B, black circles indicate devices that have received request data.

<First phase>
First, the first phase will be described.

The device with ID ₀ receives request data from the server 2. The aggregate allocation range of request data “Allot” = [ID ₀ , ID ₁₅ ], the transfer depth “Degree” = m = 4, and the aggregate transmission destination address “Nexthop” = IP ₀ are set. Here, the device with ID ₀ grasps that it is the representative device because the aggregated transmission destination address “Nexthop” is its own IP address. Thus, device ID ₀ is, the aggregate data _{ID 15} from the apparatus ID _0, it will be transmitted to the server 2 or collecting destination address 14.

The device with ID ₀ extracts the sequence setting data 12 from the received request data and stores it in its storage device 10. Further, since the device with ID ₀ has a received request data whose Degree is not 0, the spreading process of FIG. 11 is executed.

The device with ID ₀ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in the first phase of FIG. 13A and FIG. 14A, the device of ID ₀ converts the received request data into the device of ID ₈ , the device of ID ₄ , the device of ID ₂ , and Sent to device with ID ₁ . At this time, since no device has received the request data with Degree = 0, nothing is shown in the first phase of FIG. 13B and FIG. 14B.

  Here, the request data transmitted in the first phase will be described in detail.

(1-1) The device of ID ₀ performs the processing of i = 3, the device of ID ₀ (3) = ID ₈ , and Degree = 3, Allot = [ID ₀ (0), ID ₀ (3)] = Request data in which [ID ₁ , ID ₈ ] and Nexthop = IP ₀ are set is transmitted. Accordingly, device ID ₀ is, the device ID _8, the aggregate data for device ID ₈ from the apparatus of ID _1, to transmit to the device ID _0, request. Here, i = the device ID _{8 in} the Degree-1 entry of the received request data is closest to ID ₁₅ that is the upper limit value of the aggregate allocation range within the received aggregate allocation range [ID ₀ , ID ₁₅ ]. Since it is an ID, Nexthop takes over the received address IP ₀ and sets it.

(1-2) The device with ID ₀ performs processing of i = 2 to the device with ID ₀ (2) = ID ₄ , and Degree = 2, Allot = [ID ₀ (0), ID ₀ (2)] = Request data in which [ID ₁ , ID ₄ ] and Nexthop = IP ₀ (2 + 1) = IP ₈ is transmitted. Accordingly, device ID ₀ is, the device ID _4, the aggregate data for device ID ₄ from device ID _1, to transmit to the device ID _8, request.

(1-3) The device with ID ₀ performs processing of i = 1 to the device with ID ₀ (1) = ID ₂ , and Degree = 1, Allot = [ID ₀ (0), ID ₀ (1)] = Request data in which [ID ₁ , ID ₂ ], Nexthop = IP ₀ (1 + 1) = IP ₄ is transmitted. Accordingly, device ID ₀ is, the device ID _2, the aggregate data for device ID ₂ from device ID _1, to transmit to the device ID _4, request.

(1-4) The device with ID ₀ performs processing of i = _{0 to} the device with ID ₀ (0) = ID ₁ , and Degree = 0, Allot = [ID ₀ (0), ID ₀ (0)] = Request data in which [ID ₁ , ID ₁ ], Nexthop = IP ₀ (0 + 1) = IP ₂ is transmitted. Accordingly, device ID ₀ is, the apparatus ID _1, the aggregate data for device ID _1, to transmit to the device ID _2, requests.

<Second phase>
The second phase will be described.

In the first phase, the device of ID ₈ , the device of ID ₄ , the device of ID ₂ , and the device of ID ₁ that received the request data extract the sequence setting data 12 from the received request data, and store their own storage devices 10 To remember. Of these, the ID ₈ device, the ID ₄ device, and the ID ₂ device that have received the request data with Degree> 0 perform the spreading process, and the ID ₁ device that has received the request data with Degree = 0 is aggregated. Process.

The apparatus of ID ₂ sets the aggregate allocation range “Allot” = [ID ₁ , ID ₂ ], the transfer depth “Degree” = 1, and the aggregate transmission destination address “Nexthop” = IP ₄ by the process (1-3). Received request data. The apparatus of ID ₂ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in FIGS. 13A and 15A, the ID ₂ device transmits the received request data to the ID ₃ device.

The apparatus of ID ₄ sets the aggregate allocation range “Allot” = [ID ₁ , ID ₄ ], the transfer depth “Degree” = 2, and the aggregate transmission destination address “Nexthop” = IP ₈ by the process of (1-2). Received request data. The apparatus of ID ₄ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in FIGS. 13A and 15A, the device with ID ₄ transmits the received request data to the device with ID _{6 and} the device with ID ₅ .

The apparatus of ID ₈ sets the aggregate allocation range “Allot” = [ID ₁ , ID ₈ ], the transfer depth “Degree” = 3, and the aggregate transmission destination address “Nexthop” = IP ₀ by the process (1-1). Received request data. The device of ID ₈ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. Accordingly, as shown in FIGS. 13A and 15A, the device of ID ₈ transmits the received request data to the device of ID ₁₂ , the device of ID ₁₀ , and the device of ID ₉ .

On the other hand, the device of ID ₁ performs the processing of (1-4), the aggregate allocation range “Allot” = [ID ₁ , ID ₁ ], the transfer depth “Degree” = 0, and the aggregate destination address “Nexthop” = IP _2. Receives request data set with. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device ID ₁ generates the response data including the self apparatus aggregated data 16, ID ₂ To the device.

  Here, the request data transmitted in the second phase will be described in detail.

(2-1) The device of ID ₂ receives the processing of (1-3) and performs processing of i = 0 to the device of ID ₂ (0) = ID ₃ to Degree = 0, Allot = [ID ₂ Request data in which (0), ID ₂ (0)] = [ID ₃ , ID ₃ ] and Nexthop = IP ₄ is transmitted. Accordingly, device ID ₂ is the device of ID _3, the aggregate data for device ID _3, as to send the device ID _4, request.

(2-2) The device of ID ₄ receives the processing of (1-2), and the processing of i = 1 makes the device of ID ₄ (1) = ID ₆ Degree = 1, Allot = [ID ₄ Request data in which (0), ID ₄ (1)] = [ID ₅ , ID ₆ ], Nexthop = IP ₈ is transmitted. Accordingly, device ID ₄ is the device of ID _6, the aggregate data for device ID ₆ from a device ID _5, to transmit to the device ID _8, request.

(2-3) The device of ID ₄ receives the processing of (1-2) and performs processing of i = 0 to the device of ID ₄ (0) = ID ₅ to Degree = 0, Allot = [ID ₄ Request data in which (0), ID ₄ (0)] = [ID ₅ , ID ₅ ], Nexthop = IP ₄ (0 + 1) = IP ₆ is transmitted. Accordingly, device ID ₄ is the device of ID _5, the aggregate data for device ID _5, to transmit to the device ID _6, request.

(2-4) The device of ID ₈ receives the processing of (1-1), and the processing of i = 2 makes the device of ID ₈ (2) = ID ₁₂ Degree = 2, Allot = [ID ₈ Request data in which (0), ID ₈ (2)] = [ID ₉ , ID ₁₂ ] and Nexthop = IP ₀ are transmitted. Accordingly, device ID ₈ is the device _{ID 12,} the aggregate data for device _{ID 12} from the apparatus ID _9, to transmit the device ID _0, request.

(2-5) The device of ID ₈ receives the processing of (1-1), and the processing of i = 1 makes the device of ID ₈ (1) = ID ₁₀ have Degree = 1, Allot = [ID ₈ Request data in which (0), ID ₈ (1)] = [ID ₉ , ID ₁₀ ], Nexthop = IP ₈ (1 + 1) = IP ₁₂ is transmitted. Accordingly, device ID ₈ is the apparatus _{ID 10,} the aggregate data for device _{ID 10} from the apparatus ID _9, to transmit the device _{ID 12,} request.

(2-6) The device of ID ₈ receives the processing of (1-1), and the processing of i = 0 makes the device of ID ₈ (0) = ID ₉ Degree = 0, Allot = [ID ₈ Request data in which (0), ID ₈ (0)] = [ID ₉ , ID ₉ ], Nexthop = IP ₈ (0 + 1) = IP ₁₀ is transmitted. Accordingly, device ID ₈ is the apparatus ID _9, the aggregate data for device ID _9, to transmit the device _{ID 10,} request.

  Here, the response data transmitted in the second phase will be described in detail.

(2-7) The device with ID ₁ receives the request data in which Nexthop = IP ₂ is set in (1-4). Therefore, the device of ID ₁ receives the processing of (1-4), and the device of Nexthop = IP ₂ has the aggregation range “Range” = [ID ₀ (0), ID ₁ (0)) = [ID ₁ , ID ₂ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (1-4), the ID ₁ apparatus, the aggregate data for device ID _1, and transmits the device ID _2.

<Third phase>
The third phase will be described.

In the second phase, the device of ID ₁₂ , the device of ID ₁₀ , the device of ID ₉ , the device of ID ₆ , the device of ID ₅ , and the device of ID ₃ that received the request data receive the sequence setting data from the received request data. 12 is extracted and stored in its own storage device 10. Among these, the device of ID ₁₂ , the device of ID ₁₀ , and the device of ID ₆ that have received the request data of Degree> 0 each perform a spreading process. The device of ID ₉ , the device of ID ₅ , and the device of ID ₃ that have received the request data of Degree = 0 newly generate response data and perform aggregation processing. In addition, the ID ₂ device that has received the response data in the second phase also performs aggregation processing.

The apparatus of ID ₆ sets the aggregate allocation range “Allot” = [ID ₅ , ID ₆ ], the transfer depth “Degree” = 1, and the aggregate destination address “Nexthop” = IP ₈ by the process of (2-2). Received request data. The apparatus of ID ₆ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in FIGS. 13A and 16A, the device with ID ₆ transmits the received request data to the device with ID ₇ .

The apparatus of ID ₁₀ sets the aggregate allocation range “Allot” = [ID ₉ , ID ₁₀ ], the transfer depth “Degree” = 1, and the aggregate transmission destination address “Nexthop” = IP ₁₂ by the processing of (2-5). Received request data. The apparatus of ID ₁₀ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in FIGS. 13A and 16A, the device with ID ₁₀ transmits the received request data to the device with ID ₁₁ .

The apparatus of ID ₁₂ sets the aggregate allocation range “Allot” = [ID ₉ , ID ₁₂ ], the transfer depth “Degree” = 2, and the aggregate transmission destination address “Nexthop” = IP ₀ by the processing of (2-4). Received request data. The apparatus of ID ₁₂ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. As a result, as shown in FIGS. 13A and 16A, the device of ID ₁₂ transmits the received request data to the device of ID _{13 and} the device of ID ₁₄ .

On the other hand, the apparatus of ID ₃ performs the process of (2-1), the aggregate allocation range “Allot” = [ID ₃ , ID ₃ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP _4. Receives request data set with. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device ID ₃ generates response data including the self apparatus aggregated data 16, ID ₄ To the device.

The apparatus of ID ₅ sets the aggregate allocation range “Allot” = [ID ₅ , ID ₅ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP ₆ by the process of (2-3). Received request data. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device ID ₅ generates response data including the self apparatus aggregated data 16, ID ₆ To the device.

The apparatus of ID ₉ sets the aggregate allocation range “Allot” = [ID ₉ , ID ₉ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP ₁₀ by the processing of (2-6). Received request data. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device ID ₉ generates response data including the self apparatus aggregated data 16, _{ID 10} To the device.

In response to the processing of (2-7), the ID ₂ device includes the aggregated data of the ID ₁ device from the ID ₁ device, and a response in which the aggregation range “Range” = [ID ₁ , ID ₂ ) is set. Receive data. Here, the device of ID ₂ is requested to transmit the aggregated data of the device of ID ₂ from the device of ID _{1 to} the device of ID ₄ by the process (1-3). Accordingly, the ID ₂ device combines the aggregated data of the ID ₁ device received in the process (2-7) and the aggregated data of the ID ₁ device with the aggregated data of the ID ₂ device from the ID ₁ device. ₄ device.

  Here, the request data transmitted in the third phase will be described in detail.

(3-1) The device of ID ₆ receives the processing of (2-2) and performs processing of i = 0 to the device of ID ₆ (0) = ID ₇ to Degree = 0, Allot = [ID ₆ Request data in which (0), ID ₆ (0)] = [ID ₇ , ID ₇ ], Nexthop = IP ₈ is transmitted. Accordingly, device ID ₆ is the device ID _7, the aggregate data for device ID _7, to request to transmit the device ID _8.

(3-2) The device of ID ₁₀ receives the processing of (2-5), and the processing of i = 0, the device of ID ₁₀ (0) = ID ₁₁ is changed to Degree = 0, Allot = [ID ₁₀ Request data in which (0), ID ₁₀ (0)] = [ID ₁₁ , ID ₁₁ ], Nexthop = IP ₁₂ is transmitted. Accordingly, device _{ID 10} is the device _{ID 11,} the aggregate data for device _{ID 11,} to request to transmit the device _{ID 12.}

(3-3) The device of ID ₁₂ receives the processing of (2-4), and the processing of i = 1 makes the device of ID ₁₂ (1) = ID ₁₄ have Degree = 1, Allot = [ID ₁₂ Request data in which (0), ID ₁₂ (1)] = [ID ₁₃ , ID ₁₄ ], Nexthop = IP ₀ is transmitted. Accordingly, device _{ID 12} is the device _{ID 14,} the aggregate data for device _{ID 14} from the apparatus _{ID 13,} to transmit the device ID _0, request.

(3-4) The device of ID ₁₂ receives the processing of (2-4) and performs processing of i = 0 to the device of ID ₁₂ (0) = ID ₁₃ to Degree = 0, Allot = [ID ₁₂ Request data in which (0), ID ₁₂ (0)] = [ID ₁₃ , ID ₁₃ ], Nexthop = IP ₁₂ (0 + 1) = IP ₁₄ is transmitted. Accordingly, device _{ID 12} is the device _{ID 13,} the aggregate data for device _{ID 13,} to request to transmit the device _{ID 14.}

  Here, the response data transmitted in the third phase will be described in detail.

(3-5) The device of ID ₂ receives the response data including the aggregated data of the device of ID ₁ by the process of (2-7). Here, the device of ID ₂ is requested to transmit the aggregated data of the device of ID ₂ from the device of ID _{1 to} the device of ID ₄ by the process (1-3). Thus, the device of the ID ₂ is (2-7) together and aggregate data for device ID ₁ received, with their aggregate data, from a device ID ₁ aggregated data devices ID _2, the ID ₄ Send to device.

(3-6) The device of ID ₃ receives the request data in which Nexthop = IP ₄ is set in (2-1). So device ID ₃ receives the process (2-1), the apparatus Nexthop = IP _4, aggregate range _{"Range" = [ID 2 (} 0), ID 3 (0)) = [ID 3, ID ₄ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (2-1), device ID ₃ is the aggregate data for device ID _3, and transmits the device ID _4.

(3-7) The device of ID ₅ receives the request data in which Nexthop = IP ₆ is set in (2-3). Therefore, the device of ID ₅ receives the processing of (2-3), and the nexthop = IP ₆ device receives the aggregation range “Range” = [ID ₄ (0), ID ₅ (0)) = [ID ₅ , ID ₆ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (2-3), device ID ₅ is the aggregate data for device ID _5, and transmits to the device ID _6.

(3-8) The device of ID ₉ receives the request data in which Nexthop = IP ₁₀ is set in (2-6). Therefore, the device of ID ₉ receives the processing of (2-6), and the nexthop = IP ₁₀ device receives the aggregation range “Range” = [ID ₈ (0), ID ₉ (0)) = [ID ₉ , ID ₁₀ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (2-6), device ID ₉ are aggregated data devices ID _9, and transmits the device _{ID 10.}

<Fourth phase>
The fourth phase will be described.

In the third phase, the device of ID ₁₄ , the device of ID ₁₃ , the device of ID ₁₁ , and the device of ID ₇ that have received the request data extract the sequence setting data 12 from the received request data, and their own storage device 10 To remember. Among these, the device of ID ₁₄ that has received the request data of Degree> 0 performs the spreading process. The ID ₁₃ device, the ID ₁₁ device, and the ID ₇ device that have received the request data for Degree = 0 newly generate response data and perform aggregation processing. The ID ₄ device, the ID ₆ device, and the ID ₁₀ device that have received the response data in the third phase also perform aggregation processing.

The apparatus of ID ₁₄ sets the aggregate allocation range “Allot” = [ID ₁₃ , ID ₁₄ ], the transfer depth “Degree” = 1, and the aggregate transmission destination address “Nexthop” = IP ₀ by the processing of (3-3). Received request data. The device of ID ₁₄ repeats the processing from step S101 to step S104 in FIG. 11 in descending order for each i of 0 ≦ i <Degree. Thereby, as shown in FIG. 13A and FIG. 17A, the device of ID ₁₄ transmits the received request data to the device of ID ₁₅ .

On the other hand, the device of ID ₇ performs the processing of (3-1), the aggregate allocation range “Allot” = [ID ₇ , ID ₇ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP _8. Receives request data set with. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device ID ₇ generates response data including the self apparatus aggregated data 16, ID ₈ To the device.

The apparatus of ID ₁₁ sets the aggregate allocation range “Allot” = [ID ₁₁ , ID ₁₁ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP ₁₂ by the process of (3-2). Received request data. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device _{ID 11} generates response data including the self apparatus aggregated data 16, _{ID 12} To the device.

The apparatus of ID ₁₃ sets the aggregate allocation range “Allot” = [ID ₁₃ , ID ₁₃ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP ₁₄ by the processing of (3-4). Received request data. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device _{ID 13} generates response data including the self apparatus aggregated data 16, _{ID 14} To the device.

The device of ID ₄ receives the response data in which the aggregation range “Range” = [ID ₁ , ID ₃ ) is set by the processing of (3-5), and aggregates by the processing of (3-6). Response data in which the range “Range” = [ID ₃ , ID ₄ ) is set is received. Here, the device of ID ₄ is requested to transmit the aggregated data of the device of ID ₄ from the device of ID _{1 to} the device of ID ₈ by the process (1-2). Accordingly, by the processing from step S205 to step S211 in FIG. 12, the device of ID ₄ receives the aggregated data of the device of ID ₃ from the device of ID ₁ received in (3-5) and (3-6), and its own Together with the aggregated data, the aggregated data of the apparatus with ID ₄ is transmitted from the apparatus with ID _{1 to} the apparatus with ID ₈ .

Device ID ₆ is (3-7) by treatment with, for receiving the aggregate range "Range" _{= [response} data ID 5, ID ₆₎ is set. Here, the device of ID ₆ is requested to transmit the aggregated data of the device of ID ₆ from the device of ID _{5 to} the device of ID ₈ by the process (2-2). Accordingly, by the processing from step S205 to step S211 in FIG. 12, the device of ID ₆ adds the aggregated data of the device of ID ₅ received in (3-7) and the aggregated data of itself to the device of ID ₅ . The aggregated data of the device with ID ₆ is transmitted to the device with ID ₈ .

Device ID ₁₀ is (3-8) by treatment with, receives the response data intensive range _{"Range" = [ID 9,} ID 10) is set. Here, the device of ID ₁₀ is requested to transmit the aggregated data of the device of ID ₁₀ from the device of ID _{9 to} the device of ID ₁₂ by the process (2-5). Accordingly, by the processing from step S205 to step S211 in FIG. 12, the device of ID ₁₀ adds the aggregated data of the device of ID ₉ received in (3-8) and its aggregated data from the device of ID ₉ together. The aggregated data of the device with ID ₁₀ is transmitted to the device with ID ₁₂ .

  Here, the request data transmitted in the fourth phase will be described in detail.

(4-1) The device of ID ₁₄ receives the processing of (3-3) and performs processing of i = 0 to the device of ID ₁₄ (0) = ID ₁₅ to Degree = 0, Allot = [ID ₁₄ Request data in which (0), ID ₁₄ (0)] = [ID ₁₅ , ID ₁₅ ], Nexthop = IP ₀ is transmitted. Accordingly, device _{ID 14} is the device _{ID 15,} the aggregate data for device _{ID 15,} to request to transmit the device ID _0.

  Here, the response data transmitted in the fourth phase will be described in detail.

(4-2) The device of ID ₄ receives the response data including the aggregated data of the device of ID ₂ from the device of ID ₁ by the processing of (3-5), and the processing of (3-6) Response data including aggregated data of the device with ID ₃ is received. Here, the device of ID ₄ is requested to transmit the aggregated data of the device of ID ₄ from the device of ID _{1 to} the device of ID ₈ by the process (1-2). Therefore, the device with ID ₄ receives the ID from the device with ID ₁ together with the aggregated data of the device with ID ₃ from the devices with ID ₁ received in (3-5) and (3-6), and its own aggregated data. The aggregated data of the device of ₄ is transmitted to the device of ID ₈ .

(4-3) The device of ID ₆ receives the response data including the aggregated data of the device of ID ₅ by the process of (3-7). Here, the device of ID ₆ is requested to transmit the aggregated data of the device of ID ₆ from the device of ID _{5 to} the device of ID ₈ by the process (2-2). Thus, the device of the ID ₆ is (3-7) together and aggregate data for device ID ₅ received, its own aggregated data, from the device ID ₅ aggregated data devices ID _6, the ID ₈ Send to device.

(4-4) The device with ID ₇ receives the request data in which Nexthop = IP ₈ is set in (3-1). So device ID ₇ receives the process (3-1), the apparatus Nexthop = IP _8, aggregate range _{"Range" = [ID 6 (} 0), ID 7 (0)) = [ID 7, ID ₈ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (3-1), device ID ₇ is the aggregate data for device ID _7, and transmits the device ID _8.

(4-5) The device of ID ₁₀ receives the response data including the aggregated data of the device of ID ₉ by the process of (3-8). Here, the device of ID ₁₀ is requested to transmit the aggregated data of the device of ID ₁₀ from the device of ID _{9 to} the device of ID ₁₂ by the process (2-5). Thus, apparatus _{ID 10} is (3-8) together and aggregate data for device ID ₉ received, its own aggregated data, from the device ID ₉ aggregated data devices _{ID 10,} the _{ID 12} Send to device.

(4-6) The device with ID ₁₁ receives the request data in which Nexthop = IP ₁₂ is set in (3-2). Accordingly, the device of ID ₁₁ receives the processing of (3-2), and the device of Nexthop = IP ₁₂ receives the aggregation range “Range” = [ID ₁₀ (0), ID ₁₁ (0)) = [ID ₁₁ , ID ₁₂ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (3-2), device _{ID 11} is the aggregate data for device _{ID 11,} and transmits the device _{ID 12.}

(4-7) The device of ID ₁₃ receives the request data in which Nexthop = IP ₁₄ is set in (3-4). Therefore, the device of ID ₁₃ receives the processing of (3-4), and the device of Nexthop = IP ₁₄ receives the aggregation range “Range” = [ID ₁₂ (0), ID ₁₃ (0)) = [ID ₁₃ , ID ₁₄ ) is set, and response data in which aggregated data in the range of this range is set is transmitted. Thus, as requested by (3-4), device _{ID 13} is the aggregate data for device _{ID 13,} and transmits the device _{ID 14.}

<Fifth phase>
The fifth phase will be described.

In the fourth phase, the device of ID ₁₅ that has received the request data extracts the sequence setting data 12 from the received request data and stores it in its own storage device 10. The device of ID ₁₅ that has received the request data with Degree = 0 newly generates response data and performs aggregation processing. Further, the ID ₈ device, the ID ₁₂ device, and the ID ₁₄ device that received the response data in the fourth phase also perform aggregation processing.

The apparatus of ID ₁₅ sets the aggregate allocation range “Allot” = [ID ₁₅ , ID ₁₅ ], the transfer depth “Degree” = 0, and the aggregate transmission destination address “Nexthop” = IP ₀ by the process of (4-1). Received request data. Here, since Degree = 0 the request data received, step S202 to step S204 of FIG. 12, and the processing of step S211, device _{ID 15} generates response data including the self apparatus aggregated data 16, ID ₀ To the device.

The device of ID ₈ receives the response data in which the aggregation range “Range” = [ID ₁ , ID ₅ ) is set by the process (4-2), and aggregates by the process (4-3). The response data in which the range “Range” = [ID ₅ , ID ₇ ) is set is received, and the response data in which the aggregation range “Range” = [ID ₇ , ID ₈ ) is set by the process (4-4) Receive. Here, the device of ID ₈ is requested to transmit the aggregated data of the device of ID ₈ from the device of ID _{1 to} the device of ID ₀ by the process (1-1). Accordingly, by the processing from step S205 to step S211 in FIG. 12, the device of ID ₈ changes from the device of ID ₁ received in (4-2), (4-3) and (4-4) to the device of ID ₇ . and aggregated data, together with their aggregate data, the aggregate data for device ID ₈ from the apparatus of ID _1, and transmits the device ID _0.

The apparatus of ID ₁₂ receives the response data in which the aggregation range “Range” = [ID ₉ , ID ₁₁ ) is set by the process (4-5), and the aggregation range by the process (4-6). Response data in which “Range” = [ID ₁₁ , ID ₁₂ ) is set is received. Here, the device of ID ₁₂ is requested to transmit the aggregated data of the device of ID ₁₂ from the device of ID _{9 to} the device of ID ₀ by the process (2-4). Accordingly, through the processing from step S205 to step S211 in FIG. 12, the device of ID ₁₂ receives the aggregated data of the device of ID ₁₁ from the device of ID ₉ received in (4-5) and (4-6), and its own Together with the aggregated data, the aggregated data of the apparatus with ID ₁₂ is transmitted from the apparatus with ID _{9 to} the apparatus with ID ₀ .

Device ID ₁₄ is (4-7) by treatment with, for receiving the aggregate range _{"Range" =} [response data ID 13, _{ID 14)} is set. Here, the device of ID ₁₄ is requested to transmit the aggregated data of the device of ID ₁₄ from the device of ID _{13 to} the device of ID ₀ by the process of (3-3). Accordingly, by the processing from step S205 to step S211 in FIG. 12, the device of ID ₁₄ adds the aggregated data of the device of ID ₁₃ received in (4-7) and the aggregated data of ID _{13 from} the device of ID ₁₃ . The aggregated data of the device with ID ₁₄ is transmitted to the device with ID ₀ .

  Here, the response data transmitted in the fifth phase will be described in detail.

(5-1) The device of ID ₈ receives response data including aggregated data of the device of ID ₇ from the device of ID ₁ through the processes of (4-2), (4-3) and (4-4). To do. Here, the device of ID ₈ is requested to transmit the aggregated data of the device of ID ₈ from the device of ID _{1 to} the device of ID ₀ by the process (1-1). Therefore, the device of ID ₈ combines the aggregated data of the device of ID ₇ from the device of ID ₁ received in (4-2), (4-3) and (4-4) with its own aggregated data. The aggregated data of the device of ID ₈ is transmitted from the device of ID _{1 to} the device of ID ₀ .

(5-2) The device of ID ₁₂ receives response data including aggregated data of the device of ID ₁₁ from the device of ID ₉ by the processes of (4-5) and (4-6). Here, the device of ID ₁₂ is requested to transmit the aggregated data of the device of ID ₁₂ from the device of ID _{9 to} the device of ID ₀ by the process (2-4). Accordingly, the device of ID ₁₂ receives the ID data from the device of ID ₉ together with the aggregated data of the device of ID ₁₁ from the devices of ID ₉ received in (4-5) and (4-6) and its own aggregated data. The aggregated data of ₁₂ devices is transmitted to the device with ID ₀ .

(5-3) The device of ID ₁₄ receives the response data including the aggregated data of the device of ID ₁₃ by the process of (4-7). Here, the device of ID ₁₄ is requested to transmit the aggregated data of the device of ID ₁₄ from the device of ID _{13 to} the device of ID ₀ by the process of (3-3). Thus, apparatus _{ID 13} is (4-7) together and aggregate data for device _{ID 13} received, its own aggregated data, aggregated data devices _{ID 14} from the apparatus _{ID 13,} the ID ₀ Send to device.

(5-4) The device of ID ₁₅ receives the request data in which Nexthop = IP ₀ is set in (4-1). Therefore apparatus _{ID 15} receives the process (4-1), the apparatus Nexthop = IP _0, the aggregation range _{"Range" = [ID 14 (} 0), ID 15 (0)) = [ID 15, ID ₀ ) is set, and response data in which aggregate data in the range of this range is set is transmitted. Thus, as requested by (4-1), device _{ID 15} is the aggregate data for device _{ID 15,} and transmits the device ID _0.

In this way, the device with ID ₀ distributes request data from the device with ID _{1 to} the device with ID ₁₅ by the processing from the first phase to the fifth phase, and acquires aggregated data of these devices. Here, since the device with ID ₀ is a representative device, the device with ID ₀ becomes (5-1), (5-2), (5) by the processing of step S205 to step S210 and step S212 in FIG. −3) and the aggregated data of the device of ID ₁₅ received from the devices of ID ₁ and the aggregated data of the device of ID ₁₅ received from (5-4) and the aggregated data of the device of ID ₁₅ from the device of ID ₀ Send to. Here, the request data received device ID ₀ from the server 2, if the collection destination address "Collect" is set, device ID ₀ is, at the address specified by the collection destination address "Collect", ID The aggregated data of the device of ID ₁₅ is transmitted from the device of ₀ .

(Join and withdraw equipment)
In the above description, a case has been described in which a continuous ID is assigned to the device 1 and all devices communicate normally in the group. However, a case will be described in which the device 1 is disconnected due to a power cut or the like during communication.

  For example, when the device 1 is disconnected during aggregation, the operation is as follows. When a certain device 1 fails to transmit response data, it is determined that the transmission destination device has left, and the aggregated data aggregated up to that point is transmitted to the server 2. At this time, the apparatus 1 notifies the server 2 of information on the transmission destination determined to have left.

  Here, when a certain device 1 leaves before the aggregated data is transmitted after the aggregated data of the aggregate allocation range is prepared, the communication system 3 cannot detect the separation of this device 1. On the other hand, when each device 1 receives the request data, it sets a timeout until the response data is transmitted. When each device 1 times out, the aggregated data up to that time is transmitted to the server 2 regardless of whether aggregated data in the aggregate allocation range is available. Similarly, the server 2 waits for reception of response data for a certain fixed time after transmitting the request data to the representative device. After the time has elapsed, the server 2 determines a range that cannot be received, sets the missing range to Allot, and transmits new request data.

  When a new device is connected to the network and newly joins a group, the server 2 assigns a device ID to the device, generates route table data for the device, and transmits the route table data to the new device. For example, when a new device notifies that it has connected to the server 2, the server 2 determines the device ID of the new device, constructs routing table data corresponding to the device ID, and transmits it to the new device. To do.

  In addition, when the server 2 acquires the information of the disconnected device 1 or the information of the device 1 that newly joins the group, the server 2 stores the information of the device 1 that has joined and withdrawn in each device 1 in the next request data to be transmitted. Set route update information to update. Specifically, the device list control means 221 of the server 2 stores the information of the detached device and the information of the device to join in the update data 212 and updates the device list data 211. Further, the route table output unit 222 sets the data in the route update information “Updates” of the request data in consideration of the update data 212 and informs the devices 1 belonging to the group of the joining and leaving of the device 1. .

  When a new device joins, the “Updates” field sets the ID of the new subscribing device, the IP address of the new subscribing device, and the ID of the first neighboring device existing in the forward direction from the ID of the new subscribing device. When the device leaves, the “Updates” field sets the ID of the leaving device, the ID of the first neighboring device existing in the forward direction from the ID of the leaving device, and the IP address.

  When each device receives the request data, each device refers to the “Updates” field to determine whether or not the routing table data needs to be updated.

When a new device joins, the routing table data 11 has a record related to the neighboring device, and the ID of the new joining device is 2 ^Entry distances from the ID of the request receiving device with respect to the entry number in the routing table data of the neighboring device. When the distance is more than the above, the record of the routing table data 11 of the entry is replaced with information of the new joining device. On the other hand, when this condition is not satisfied, the routing table data 11 is not updated.

  On the other hand, when the device leaves, if the routing table data 11 has a record relating to the leaving device, the record is replaced with information on the neighboring device. This is based on the fact that the communication method according to the embodiment forms a similar tree shape even when the number of devices is smaller than the size of the ID space, and therefore corresponds to an arbitrary number of devices below the ID space.

  For example, consider a case where there is no ID4 device. In the example shown in FIG. 19, compared to the example shown in FIG. 13, the ID0 device should be sent to the ID4 device due to the missing number of the ID4 device. Absent. This is achieved by holding the device closest in the clockwise direction when there is no device having an ID that matches each entry in the routing table data of each device. At this time, the device of ID8 receives requests from the device of ID0 and the device of ID7 redundantly. However, as shown in step S2 of FIG. 10, request data having the same sequence number is simply discarded. Since each device searches the routing table data in descending order and forwards the request, the request that should be determined to be duplicate never arrives first.

  When there is no ID1 device, Entry = 0 and Entry = 1 in the ID0 routing table data both indicate the ID2 device. Accordingly, since the device indicated by Entry = 0 is the same as the device indicated by Entry = 0 + 1, the processing at Entry = 0 is skipped.

  In the communication method according to the embodiment of the present invention, the representative device that has received the request data from the server 2 can aggregate the data through an asymmetric path while spreading the request data. Thereby, as shown in FIG. 13, in the second phase to the fourth phase, it is possible to increase the number of simultaneous executions of request data spreading and data aggregation. On the other hand, as shown in FIG. 23, the number of execution phases m-1 times can be reduced and the processing time can be shortened as compared with the case where the data is collected by reversing the diffusion process.

  As described above, the communication system 3 according to the embodiment of the present invention uses devices such as gateway devices, for example, each device aggregates device information, and devices construct a P2P network to collect data. To do. As a result, the data collection efficiency of the server 2 and the collection load of the server 2 are reduced.

(Modification)
In the modification of the present invention, a communication method that further improves the processing efficiency as compared with the communication method according to the embodiment of the present invention will be described. FIG. 20 shows a data flow of the communication method according to the modification of the present invention. Compared with the communication method according to the embodiment of the present invention described with reference to FIG. 13, the data flow illustrated in FIG. 20 is a device that has received request data from the representative device ID 0 in the aggregation processing of (b). The behaviors of the devices with IDs 1, 2, 4 and 8 are different. Receiving the request data from the representative apparatus (ID0 apparatus), each of the apparatus IDs 1, 2, 4, and 8 transmits the aggregated data directly to the representative apparatus.

  Regarding the second phase, in the example illustrated in FIG. 13, the ID1 device transmits response data to the ID2 device. On the other hand, in the example illustrated in FIG. 20, the ID1 device transmits response data including aggregated data of the ID1 device to the representative device.

  In the example shown in FIG. 13 for the third phase, after receiving the response data from the ID1 device, the ID2 device sends response data including aggregated data of the ID2 device from the ID1 device to the ID4 device. . On the other hand, in the example illustrated in FIG. 20, the ID2 device transmits response data including the aggregated data of the ID2 device to the representative device without waiting for the aggregated data of the ID1 device.

  In the example shown in FIG. 13 for the fourth phase, after receiving the response data from the ID2 device and the ID3 device, the ID4 device sends the response data including the aggregated data of the ID4 device to the ID8 device from the ID1 device. Had been sent to. In the example illustrated in FIG. 20, the ID4 device transmits response data including aggregated data of the ID4 device from the ID3 device to the representative device without waiting for reception of response data from the ID2 device.

  In the example shown in FIG. 13 for the fifth phase, the ID8 device receives response data including aggregated data of the ID8 device from the ID1 device after receiving response data from the ID4 device, the ID6 device, and the ID7 device. , It was transmitted to the device of ID0. In the example illustrated in FIG. 20, the ID8 device transmits response data including aggregated data of the ID8 device from the ID5 device to the representative device without waiting for reception of the response data of the ID4 device.

  In the communication method according to such a modification, the range of allot of each device is small except for the representative device, so the size of each aggregated data is smaller than that of the communication method according to the embodiment of the present invention. Become. Thereby, as a whole communication system, the total amount of data to be transmitted can be reduced, and the processing load can be reduced.

  In order to realize such a communication method, compared to the embodiment of the present invention, the representative apparatus, in spreading the request data, collects the aggregated transmission destination address (Nexthop) and aggregated allocation range of each item of the received request data. The setting method of each item of (Allot) is different. The spreading means 23 of the representative device sets the aggregated transmission destination address (Nexthop) of the received request data to the IP address of the representative device. The spreading means 23 of the representative device corresponds to the entry allocation identifier (ID (i-1)) from the device identifier (ID (i-1)) of the entry identifier-1 in the routing table data 11 for the aggregate allocation range (Allot) of the received request data. Set to the identifier range of the device (ID (i)). The spreading means 23 of the representative device sets the transfer range (Degree) of the received request data to the entry identifier (i).

  With reference to FIG. 21, the diffusion process according to the modification will be described. Based on the routing table data 11, the diffusing unit 23 according to the modified example repeats the processing from step S301 to step S308 for each i from i = Degree-1 to 0.

First, in step S301, the spreading means 23 determines whether or not the ID _n (i) of the device corresponding to the entry identifier is within the aggregate allocation range “Allot”. When ID _n (i) is outside the range of the aggregate allocation range “Allot”, the process for the entry identifier i is terminated, and the next i−1 is processed. If ID _n (i) is within the range of the aggregate allocation range “Allot”, the process proceeds to step S302.

  In step S302, the diffusing unit 23 determines whether or not the own device is a representative device. If it is not the representative device, the changed request data is generated by the processing of step S303, step S304, and step S307, and the changed request data is transmitted to another device in step S308. This processing corresponds to the processing in steps S102 to S105 in FIG.

  On the other hand, when the own device is a representative device, the request data after the change is generated by the processing from step S305 to step S307, and the request data after the change is transmitted to another device in step S308.

  As a result, the device that has received the request from the representative device can aggregate only the aggregated data of the device identified in step S305, and can transmit the aggregated data to the IP address of the representative device identified in step S306. .

(Verification)
The effect of the communication method according to the embodiment of the present invention will be verified.

The total time T _g ′ required for collection is represented by the sum of the following items. At this time, S is the amount of data per device, 2 ^m is the number of devices in one group, c is the internal processing time of the device, d is the transfer delay between devices, B is between the devices and between the devices and the server. Use bandwidth. The total time T _g ′ is calculated as the time required for the range surrounded by the solid line in the message flow of FIG. In addition, since the processing outside the frame is performed in parallel, the collection time in the frame is not affected.

(1) Sending time in bandwidth B of the total amount of data transmission performed sequentially The circled numbers in the frame of FIG. 20B indicate the data amount per device. The total amount of data transmitted by the message in the range surrounded by the solid line, specifically, the sum of the circled numbers in FIG. The sum of the circled numbers is represented by N _g ′ in the following formula. Multiply by S to get the actual amount of data, and multiply by 8 to convert it to bits. Divide this by the bandwidth to make the total transmission time.

(2) Sequential total sum of transmission times of the data transmission delay performed in, the number of arrows in the range in particular surrounded by the solid line in FIG. 20, expressed in N _r, multiplied by the transfer delay d between the respective devices to this To do. This is the total transmission delay.

(3) The total internal processing time N _g ′ associated with the data transmission is multiplied by the internal processing time c to obtain the total internal processing time.

(4) Transmission time of aggregated data of devices (within the same group) to server Based on the above assumption, T _g ′ is calculated as follows.

Tg ′ = Ng ′ * 8 * S / B + Nr * d + Ng ′ * c + S * 2 ^m * 8 / B + d + c
At this time, Ng = 2 ^m -1, Nr = m * (m + 1) / 2.

FIG. 22 shows a comparison result between the collection time T _g in the embodiment of the present invention and the collection time T _g ′ in the modification. Here, the horizontal axis is the value of m, and the vertical axis is the collection time. The parameters are S for 1 KB, m for 10, c for 100 milliseconds, d for 1 second, and B for 128 kbps. As the group size (m) increases, the effect in the modified example becomes more prominent. When targeting a larger number of devices, the communication method according to the modification is more effective. When m = 10, a shortening effect of about 3 minutes can be expected.

(Other embodiments)
As described above, the embodiments and modifications of the present invention have been described. However, it should not be understood that the descriptions and drawings constituting a part of this disclosure limit the present invention. From this disclosure, various alternative embodiments, examples, and operational techniques will be apparent to those skilled in the art.

  For example, in the embodiment of the present invention, the case where the server spreads request data to a plurality of devices and aggregates the data of each device has been described. However, the present invention is not limited to this. The server request data spreading logic may be diverted to data transmission from the server to a plurality of terminals.

  It goes without saying that the present invention includes various embodiments not described herein. Therefore, the technical scope of the present invention is defined only by the invention specifying matters according to the scope of claims reasonable from the above description.

DESCRIPTION OF SYMBOLS 1 apparatus 2 server 3 communication system 10,210 memory | storage device 11,213 routing table data 12 sequence setting data 13 aggregation transmission destination address 14 collection destination address 15 aggregation allocation range data 16 own apparatus aggregation data 20, 220 central processing control apparatus 21 control Means 22 Route table control means 23 Spreading means 24 Aggregation means 25 Data acquisition means 30, 230 Communication control device 211 Device list data 212 Update data 221 Device list control means 222 Route table output means 223 Request transmission means 224 Data reception means

Claims (8)

A communication system comprising a server and a plurality of mutually communicable devices connected to the server,
Each of the plurality of devices is assigned an identifier of any integer value from 0 to 2 ^m −1,
The server
Each of the plurality of devices is associated with an entry identifier (Entry) from 0 to m−1, an identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device. Routing table output means for outputting routing table data;
Request transmission means for transmitting request data for data collection to one of the plurality of devices as a representative device;
Data receiving means for receiving the data from the device;
The device is
Receiving routing table data of the device from the server;
When request data is received from the server or another device, the received request data is changed according to the routing table data and transmitted to the other device, and response data for the received request data is transmitted to the other device or server. With control means,
Request data that the server sends to the representative device is:
An aggregation allocation range that specifies a lower limit value and an upper limit value of an identifier of a device from which the representative device aggregates data; and
A transfer depth taking a value from 0 to m indicating a range in which the request data is diffused between the devices;
An aggregate transmission destination address in which the address of the representative device is set,
The control means of the device is:
(1) Upon receiving the request data,
Stores the aggregate destination address of the received request data and the aggregate allocation range,
(2) If the transfer depth of the received request data is 0,
Generate response data including the own device aggregated data aggregated by the device, and transmit it to the aggregated transmission destination address.
(3) When response data is received,
Merge the aggregated data included in the received response data into the aggregated data of own device,
When the own device aggregated data after merging satisfies all the aggregate allocation ranges of the received request data, response data including the own device aggregated data is transmitted to the aggregate transmission destination address,
(4) If the transfer depth of the received request data is not 0, refer to the routing table data,
For each entry identifier of 0 or more and less than the transfer depth, for the entry identifier having the identifier of the device within the aggregate allocation range received by the device in descending order of the entry identifier,
For the entry identifier having the identifier of the device closest to the upper limit value of the aggregate allocation range received by the device, the aggregate transmission destination address is set by taking over the aggregate transmission destination address received by the device, and other entry identifiers. For the routing table data, set the entry identifier to the address of the device associated with the incremented entry identifier,
Setting the aggregate allocation range to the range of the identifier of the device corresponding to the entry identifier from the identifier of the device of the entry identifier 0 in the routing table data;
The transfer range is set to the entry identifier,
A communication system, wherein the process of transmitting the changed request data to the address of the device corresponding to the entry identifier in the routing table data is repeated. When the control unit generates the changed request data from the received request data, when the device is a representative device,
Set the aggregate destination address to the address of the representative device,
The aggregate allocation range is set from the device identifier of the entry identifier-1 to the device identifier range corresponding to the entry identifier in the routing table data;
The communication system according to claim 1, wherein the transfer range is set to the entry identifier. A device in a communication system comprising a server and a plurality of devices capable of communicating with each other,
The device is given an identifier of any integer value from 0 to 2 ^m −1,
Receiving route table data in which an entry identifier (Entry) from 0 to m−1, an identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device are associated;
When request data is received from the server or another device, the received request data is changed according to the routing table data and transmitted to the other device, and response data for the received request data is transmitted to the other device or server. With control means,
The request data that the server sends to the device is:
An aggregation allocation range that specifies a lower limit value and an upper limit value of an identifier of a device for which the device aggregates data; and
A transfer depth taking a value from 0 to m, indicating a range in which the device spreads the request data;
An aggregate destination address that is a destination of response data, and
The control means includes
(1) Upon receiving the request data,
Stores the aggregate destination address of the received request data and the aggregate allocation range,
(2) If the transfer depth of the received request data is 0,
Generate response data including the own device aggregated data aggregated by the device, and transmit it to the aggregated transmission destination address.
(3) When response data is received,
Merge the aggregated data included in the received response data into the aggregated data of own device,
When the own device aggregated data after merging satisfies all the aggregate allocation ranges of the received request data, response data including the own device aggregated data is transmitted to the aggregate transmission destination address,
(4) If the transfer depth of the received request data is not 0, refer to the routing table data,
For each entry identifier of 0 or more and less than the transfer depth, for the entry identifier having the identifier of the device within the aggregate allocation range received by the device in descending order of the entry identifier,
For the entry identifier having the identifier of the device closest to the upper limit value of the aggregate allocation range received by the device, the aggregate transmission destination address is set by taking over the aggregate transmission destination address received by the device, and other entry identifiers. For the routing table data, set the entry identifier to the address of the device associated with the incremented entry identifier,
Setting the aggregate allocation range to the range of the identifier of the device corresponding to the entry identifier from the identifier of the device of the entry identifier 0 in the routing table data;
The transfer range is set to the entry identifier,
A device that repeats the process of transmitting the changed request data to the address of the device corresponding to the entry identifier in the routing table data. In the case where the device is a representative device that has received request data from the server, the control means generates the changed request data from the received request data.
Set the aggregate destination address to the address of the device,
The aggregate allocation range is set from the device identifier of the entry identifier-1 to the device identifier range corresponding to the entry identifier in the routing table data;
The apparatus according to claim 3, wherein the transfer range is set to the entry identifier. A communication method used for a device in a communication system including a server and a plurality of devices that can communicate with each other connected to the server,
The device is given an identifier of any integer value from 0 to 2 ^m −1,
A step of receiving route table data in which an entry identifier (Entry) from 0 to m−1, an identifier of a transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device are associated with each other With
The request data that the server sends to the device is:
An aggregation allocation range that specifies a lower limit value and an upper limit value of an identifier of a device for which the device aggregates data; and
A transfer depth taking a value from 0 to m indicating a range in which the request data is diffused between the device and the other device;
An aggregate destination address that is a destination of response data, and
The communication method is:
(1) When the device receives the request data,
Storing the aggregated transmission destination address of the received request data and the aggregated allocation range;
(2) When the transfer depth of the received request data is 0,
Generating response data including the own device aggregated data aggregated by the device and transmitting the response data to the aggregated transmission destination address;
(3) When the device receives response data,
Merge the aggregated data included in the received response data into the aggregated data of own device,
When the merged self-device aggregate data satisfies all the aggregate allocation ranges of the received request data, the response data including the self-device aggregate data is transmitted to the aggregate transmission destination address;
(4) When the transfer depth of the received request data is not 0, the device refers to the route table data,
For each entry identifier of 0 or more and less than the transfer depth, for the entry identifier having the identifier of the device within the aggregate allocation range received by the device in descending order of the entry identifier,
For the entry identifier having the identifier of the device closest to the upper limit value of the aggregate allocation range received by the device, the aggregate transmission destination address is set by taking over the aggregate transmission destination address received by the device, and other entry identifiers. For the routing table data, set the entry identifier to the address of the device associated with the incremented entry identifier,
Setting the aggregate allocation range to the range of the identifier of the device corresponding to the entry identifier from the identifier of the device of the entry identifier 0 in the routing table data;
The transfer range is set to the entry identifier,
A communication method comprising the step of repeating the process of transmitting the changed request data to the address of the device corresponding to the entry identifier in the routing table data. In the case where the device is a representative device that has received request data from the server, the control means generates the changed request data from the received request data.
Set the aggregate destination address to the address of the representative device,
The aggregate allocation range is set from the device identifier of the entry identifier-1 to the device identifier range corresponding to the entry identifier in the routing table data;
The communication method according to claim 5, wherein the transfer range is set to the entry identifier.   A communication program for causing a computer to function as each unit of the apparatus according to claim 3. A server of a communication system comprising a server and a plurality of devices capable of communicating with each other including a representative device connected to the server,
Each of the plurality of devices is assigned an identifier of any integer value from 0 to 2 ^m −1,
Each of the plurality of devices is associated with an entry identifier (Entry) from 0 to m−1, an identifier of the transfer destination device obtained by adding 2 ^Entry to the identifier of the device, and an address of the transfer destination device. Routing table output means for outputting routing table data;
Request transmission means for transmitting request data for data collection to one of the plurality of devices as a representative device;
Data receiving means for receiving the data from the device;
Request data that the server sends to the representative device is:
An aggregation allocation range that identifies a device for which the representative device aggregates data; and
A transfer depth taking a value from 0 to m indicating a range in which the request data is diffused between the devices;
And a consolidated transmission destination address in which an address of the representative device is set.

Images