JP5394329B2 - Sensor client device, application client device, sensor information transfer system, command information reception method, command information registration method, sensor information transfer method - Google Patents

Description

  The present invention relates to a stream processing type database system that immediately transfers sensor information.

Conventionally, there has been an information transfer system for sensor data that makes it possible to register data such as sensors and search or transfer data that matches the conditions. One such sensor information transfer system is uTupleSpace (Non-Patent Document 1). One of the features of uTupleSpace is data transfer processing that specifies range conditions.
Conventionally, the transfer of data from a sensor has been a method in which an ID (identifier) of a sensor is designated and the information of the sensor of the ID is delivered to which application. In uTupleSpace, the application can specify a range condition other than the sensor ID, and can deliver sensor data that matches the condition to the application. Thereby, for example, a process of acquiring information of all temperature sensors in a room A can be easily realized.

In addition, one of the features of uTupleSpace is that it supports not only data transmission (event) from the sensor but also control data transmission (command) to the sensor. Also in this case, the application can specify the range condition. Thereby, for example, a process of turning on all the alarm lamps in a certain room A can be easily realized. In this case, there is a usefulness that the processing can be realized even if the application does not manage the list of devices having the alarm lamp.
These are important characteristics that the sensor information transfer system should have in order to construct an application that performs transmission and reception to the sensor.

On the other hand, when the number of sensors becomes large, the processing amount of the transfer server in the sensor information transfer system increases. In order to cope with this, a technique of installing a plurality of transfer servers and appropriately distributing the processing load is important, and has been proposed conventionally.
Non-Patent Document 1 discloses a technique for statically distributing the processing load. The outline of the technology is as follows.
The event data (EA: eventActual) from the sensor and the acquisition request (EF: eventFormal) from the application will be exemplified. When a sensor registers an EA, a hash function is applied to meta information indicating the sensor type, message type, etc., among the contents of the EA, and which server is in charge of processing among a plurality of transfer servers, The sensor transmits EA to the transfer server. That is, all types of EA are sent to the same transfer server.

On the other hand, when an application registers EF, the hash function is similarly applied to meta information indicating the type, message type, etc. of the sensor to be acquired from the contents of the EF. It is determined whether the server is in charge of processing, and the application transmits an EF to the transfer server. As a result of the above processing, a single transfer server receives all registration requests for a certain type of EA and EF, so that all EAs that meet the EF conditions can be delivered to the corresponding application. The process of delivering to the application, that is, the EA transfer process, is executed in a state where the load is distributed to different transfer servers according to the types of EA and EF.
Also, command data (CA: commandActual) from an application and command reception request (CF: commandFormal) from a sensor can be processed in a similar manner by distributing servers in charge of transfer processing.

  Furthermore, Non-Patent Document 2 shows a technique for dynamically distributing processing loads. In the prior art, when there are a large number of types of EA and EF evenly, the processing load can be uniformly distributed. However, when only a specific type of EA and EF exists in a biased amount, There was a problem that processing load was concentrated on a specific transfer server. In the prior art, the problem is solved as follows.

  That is, the load concentration on the transfer server is detected, and the sharing change is determined so that the processing of a specific type of EA and EF is handled by a transfer server group including two or more transfer servers. After the change of assignment, when the sensor registers EA, one of the transfer server groups in charge obtained by the hash function is selected by an arbitrary method such as a random number, and only the EA is transferred to the transfer server. Send. On the other hand, when an application registers an EF, the EF is transmitted to all transfer servers included in the transfer server group in charge obtained by the hash function.

  In addition, after changing the assignment, when the sensor registers CF, one of the transfer server groups in charge obtained by the hash function is selected by an arbitrary method such as a random number, and only the transfer server is selected. The CF is transmitted. On the other hand, when the application registers the CA, the CA transmits the CA to all transfer servers included in the group for the transfer server group in charge obtained by the hash function.

The reason why the above system operates properly is as follows. As a premise, EA is transmitted only to one unit, whereas EF is transmitted to only one unit, and CF is transmitted to only one unit, whereas CA is
Each process is transmitted to all of the transfer server groups. For this reason, no matching omission occurs in the condition matching process.

Next, the processing load will be considered. The processing to be transmitted to all of the transfer server groups may become a problem for the entire system because the overhead of the transmission processing itself increases as the number of servers included in the transfer server group increases.
However, the typical application of uTupleSpace is not a problem because the number of sensors is enormous, while the applications are limited.

  Hereinafter, specific quantities will be exemplified. If there are 100 million sensors and one sensor registers 10,000 EAs, the number of EAs is 1 trillion. That is, the EA registration process is performed 1 trillion times. On the other hand, it is assumed that the average application performs a process of registering EF so as to acquire 10 million EAs at a time. At this time, assuming that all EAs are read once on average, the registration process of EF is performed 100,000 times in total. For this reason, the number of EF registrations is 7 digits less than the number of EA registrations. Assuming that the load is distributed by 100 transfer servers, the EA registered 1 trillion times is transmitted to only one transfer server for each registration process. On the other hand, EF registered 100,000 times is transmitted to a maximum of 100 transfer servers for each registration process, but the number of EF transmission processes is still at least five orders of magnitude less than that of EA. For this reason, the method functions smoothly for load distribution related to EA and EF.

  Similar considerations hold for CA and CF. For example, consider a case where a CF is transmitted and received by a CF, such as turning on all warning lamps in a room A. If there are an average of 100 alarm lamps in the room, the number of CA registrations can be two orders of magnitude less than the number of transfers to the CF. For this reason, for example, if the load distribution is about several to several tens of transfer servers, the processing load becomes lighter when the load is distributed. Thus, the scheme works smoothly under the above assumptions.

Takayuki Nakamura et al., "UTupleSpace: A Bi-Directional Shared Data Space for Wide-Area Sensor Network," 2nd International Workshop on Sensor Networks and Ambient Intelligence (SENAMI 2009), Dec. 2009. Arakawa, et al., "Evaluation of dynamic scaling method in real-world data sharing mechanism uTupleSpace", IEICE Technical Report, IN2009-21, June 2009

However, in the above-described conventional technique for performing dynamic load distribution of sensor information transfer, there is a problem that load cannot be sufficiently reduced by load distribution in a certain type of typical command transmission application. The following is an example of a problem.
Consider an advanced remote control application that connects a sensor device in a room with home appliances, etc., and controls home appliances from a remote location via a sensor information transfer system. Specifically, the control may be, for example, turning on / off the power supply or raising / lowering the air conditioning set temperature. It is assumed that a room layout is displayed as an illustration on the application screen, a home appliance icon is displayed, and a control command can be transmitted by a mouse click or the like.

  In such an application, there is at most one home appliance to be reacted to one home appliance operation command. This is because, when a room is displayed in a layout, each control target home appliance is displayed as an icon, and the user clicks on it, the target to which a control command is to be sent is uniquely determined, and the application sends a specific transmission. This is because the future can be known. In such an application, for example, when the CF receives a total of 100 million CAs, that is, control commands, the CA registration process is also performed 100 million times. For this reason, if 10 transfer servers are used for load distribution, the number of CA registrations is 1 billion at the maximum, which is 10 times higher than the number of transfers to the CF. Thus, the overhead associated with CA registration cannot be ignored, and it can be seen that the dynamic load distribution method does not exhibit the desired performance.

  Note that such applications do not necessarily utilize the features of advanced data transfer processing provided by uTupleSpace. Therefore, if uTupleSpace is not used and the sensor and the application are directly connected via the network, the above-mentioned problem does not occur. However, in that case, it is not possible to utilize the features of advanced data transfer processing provided by uTupleSpace. Therefore, in addition to the above-mentioned application, there is a problem that other applications cannot be used together.

  In view of the circumstances described above, the object of the present invention is to make it possible to easily create a command transmission type application utilizing the features of advanced data transfer processing provided by uTupleSpace, and to provide a static or dynamic load thereof. An object of the present invention is to provide a sensor information transfer system that performs distribution and can efficiently realize a command transmission type application that allows the application to know a specific transmission destination.

In order to solve the above-described problem, the present invention is configured such that a sensor client device (for example, the sensor 101 in the present embodiment) registers a command reception request in the transfer server, and an application client device (for example, the application device 104 in the present embodiment). ) Registers the command information in the transfer server (for example, the transfer server 103 in the present embodiment), and the transfer server satisfies the condition of the command reception request from the sensor client device and the command information from the application client device. The sensor client device constituting the sensor information transfer system for transferring the command information to the sensor client device when the condition is matched, and from the meta information indicating the characteristics of the sensor information, Transfer service A hash calculation unit that identifies one or more transfer servers of the server; an accommodation destination calculation unit that identifies one or more transfer servers of the plurality of transfer servers from the ID of the sensor client device; and Command reception registering a command reception request in one of the transfer servers specified by the hash calculation means and registering a command reception request in one of the transfer servers specified by the accommodation destination calculation means It comprises a request registration means and a command information receiving means for receiving command information from the transfer server.

  In the present invention, the sensor client device registers a command reception request in the transfer server, the application client device registers command information in the transfer server, and the transfer server includes a command reception request from the sensor client device, The application client device constituting a sensor information transfer system that performs a condition comparison with the command information from the application client device and transfers the command information to the sensor client device when the condition is met, The command information to be transmitted by the client device includes either the ID of the sensor client device to which the command information is to be transmitted or meta information indicating the characteristics of the sensor information, and indicates the characteristics of the sensor information. One of the plurality of transfer servers from the hash calculation means for identifying one or more transfer servers of the plurality of transfer servers from the data information, and the ID of the sensor client device to which the command information is to be transmitted. The accommodation destination calculating means for specifying the transfer server and the transfer specified by the accommodation destination calculating means when the command information to be transmitted includes the ID of the sensor client device to which the command information is to be transmitted. When the command information is registered in the server and the ID of the sensor client device to which the command information is to be transmitted is not included in the command information to be transmitted, the command is transmitted to all the transfer servers specified by the hash calculation unit. Command information registration means for registering information.

The present invention also provides a sensor information transfer system in which one or more sensor client devices, one or more application client devices, and one or more transfer servers are connected via a network and load distribution of command transmission is performed. The sensor client device, from the meta information indicating the characteristics of the sensor information, from the first hash calculation means for identifying one or more transfer servers of the plurality of transfer servers, and the ID of the sensor client device, a first accommodating calculating means for identifying one or more transfer server of the plurality of the transfer server, to one of said transfer server identified by the first hash calculation means, command receiving request The command reception registering the command reception request to one of the transfer servers specified by the first accommodation destination calculating means. A request registration unit; and a command information receiving unit configured to receive command information from the transfer server, wherein the application client device transmits a command information to the command information to be transmitted by the application client device. First of all, one of the plurality of transfer servers is specified from the meta information indicating the feature of the sensor information including either the ID of the client device or the meta information indicating the feature of the sensor information. 2 hash calculation means, and second accommodation destination calculation means for specifying one or more transfer servers of the plurality of transfer servers from the ID of the sensor client device to which command information is to be transmitted, and to transmit Sensor client that wants to send command information When the device ID is included, the command information is registered in the transfer server specified by the second accommodation destination calculation means, and the command information to be transmitted is included in the command client information to be transmitted. Command information registration means for registering the command information in all the transfer servers specified by the second hash calculation means when the ID is not included, and the transfer server receives and holds the command reception request Holding means; registration means for registering command information; registered command information; condition comparison means for comparing the conditions included in the held command reception request; and command reception for matching the command information as a result of comparison Transfer means for transferring the request to the registration source of the request.

In the present invention, the sensor client device registers a command reception request in the transfer server, the application client device registers command information in the transfer server, and the transfer server includes a command reception request from the sensor client device, A command information receiving method of the sensor client device that constitutes a sensor information transfer system that performs a condition comparison with the command information from the application client device and transfers the command information to the sensor client device when the condition is met. A hash calculation step of identifying one or more transfer servers among the plurality of transfer servers from the meta information indicating the characteristics of the sensor information, and an ID of the sensor client device, from among the plurality of transfer servers. One or more transfer servers And accommodating calculation step of specifying, in one of the transfer server identified in the hash calculation step, and registering a command received request, to one of the transfer server identified in the accommodating calculating step And a command reception request registration step for registering a command reception request, and a command information reception step for receiving command information from the transfer server.

  In the present invention, the sensor client device registers a command reception request in the transfer server, the application client device registers command information in the transfer server, and the transfer server includes a command reception request from the sensor client device, In the command information registration method of the application client device constituting the sensor information transfer system that performs a condition comparison with the command information from the application client device and transfers the command information to the sensor client device when the condition is met. The command information to be transmitted by the application client device includes either the ID of the sensor client device to which the command information is to be transmitted, or meta information indicating the characteristics of the sensor information, A plurality of transfers based on the hash calculation step of identifying one or more transfer servers among the plurality of transfer servers from the meta information indicating the characteristics of the sensor information, and the ID of the sensor client device to which the command information is to be transmitted. An accommodation destination calculation step for identifying one or more transfer servers among the servers, and an ID of the sensor client device to which the command information is to be transmitted included in the command information to be transmitted. When the command information is registered in the transfer server specified in the process, and the ID of the sensor client device to which the command information is to be transmitted is not included in the command information to be transmitted, it is identified in the hash calculation process. And a command information registration step of registering the command information in all transfer servers.

The present invention also provides sensor information of a sensor information transfer system in which one or more sensor client devices, one or more application client devices, and one or more transfer servers are connected via a network, and load distribution of command transmission is performed. A first hash calculation step in which the sensor client device identifies one or more transfer servers of the plurality of transfer servers from meta information indicating characteristics of sensor information, and the sensor client from the ID of the device, one of the transfer server in which the first accommodating calculating step, identified in the first hash calculation step of identifying one or more transfer server of the plurality of the transfer server The command reception request is registered, and the command reception request is registered to one of the transfer servers specified in the first accommodation destination calculation step. A command reception request registration step for performing command information reception for receiving command information from the transfer server, and the command client to transmit command information to the command information to be transmitted by the application client device. ID or meta information indicating the characteristics of sensor information, and the application client device selects one or more transfer servers of the plurality of transfer servers from the meta information indicating the characteristics of sensor information. A second hash calculation step of specifying, a second accommodation destination calculation step of specifying one or more transfer servers of the plurality of transfer servers from the ID of the sensor client device to which command information is to be transmitted, Try to send command information in the command information to be sent A sensor that registers the command information in the transfer server specified in the second accommodation destination calculation step and transmits the command information in the command information to be transmitted. A command information registration step of registering the command information in all of the transfer servers specified in the second hash calculation step when the client device ID is not included, and the transfer server receives the command reception request A holding step for storing and holding, a registration step for registering command information, a registered command information, a condition comparison step for comparing the conditions included in the command reception request to be held, and the command information matched as a result of the comparison. And a transfer step of transferring to a registration source of the command reception request.

  According to the present invention, it is possible to easily create a command transmission type application that performs advanced data transfer processing, performs static or dynamic load distribution of these, and further, the application knows a specific transmission destination. Such a command transmission type application can also be efficiently realized.

It is a block diagram which shows the whole structure of the sensor information transfer system in one Embodiment of this invention. It is a block diagram which shows an example of a structure of the sensor in the sensor information transfer system in one Embodiment of this invention. It is a block diagram which shows an example of a structure of the application apparatus in the sensor information transfer system in one Embodiment of this invention. It is a block diagram which shows an example of a structure of the transfer server in the sensor information transfer system in one Embodiment of this invention. It is a block diagram which shows an example of a structure of the assignment management server in the sensor information transfer system in one Embodiment of this invention. It is a block diagram which shows an example of a structure of the accommodation destination calculation part in one Embodiment of this invention. It is explanatory drawing of the registration process of the information reception request in one Embodiment of this invention. It is a flowchart used for description of the registration process of the information reception request in one Embodiment of this invention. It is explanatory drawing of the transfer server in the sensor information transfer system in one Embodiment of this invention. It is explanatory drawing of the transfer server in the sensor information transfer system in one Embodiment of this invention. It is explanatory drawing of the transfer server in the sensor information transfer system in one Embodiment of this invention. It is explanatory drawing of the transfer server in the sensor information transfer system in one Embodiment of this invention. It is explanatory drawing of the registration process of the command information in one Embodiment of this invention. It is a flowchart used for description of the registration process of the command information in one Embodiment of this invention.

One embodiment of the present invention is shown below.
FIG. 1 shows a configuration of the entire sensor information transfer system in the present embodiment. Sensor 101A, sensor 101B, sensor 101C, application device 102, transfer server 103A, transfer server 103B, transfer server 103C, transfer server 103D, and sharing management server 104 are connected to network 105. Here, since the plurality of sensors 101 </ b> A to 101 </ b> C have the same configuration, they are described as sensors 101 when it is not particularly necessary to distinguish between them. Similarly, since the transfer servers 103A to 103D have the same configuration, the transfer server 103 will be described when there is no need to distinguish between them.
The sensor group and the application apparatus 102 exchange information with each other by using the functions of the transfer server group in a method described in detail below.

  Here, in the present embodiment, it is assumed that the network is wired by a protocol such as IP (Internet Protocol). The scope of the network in the present invention is not limited to this, and a wide range of networks can be used. In particular, for connection of sensor groups, a wireless network using a protocol other than IP, for example, a mobile phone network may be used. Furthermore, a plurality of types of networks may be mixed, such as interconnecting these networks and wired connection networks such as IP. An appropriate gateway for interconverting media or protocols may be inserted between the mixed networks.

  FIG. 2 shows the configuration of the sensor 101. The sensor 101 has a function of acquiring a temperature by the temperature sensor 126 provided and transmitting the temperature to the server, and further includes an alarm lamp 127 and a buzzer 128. The lamp is lit red and the buzzer sounds according to an instruction from the server. Can be performed. The sensor 101 also includes a client library 120 that has a communication function with the transfer server group. The client library 120 includes an event registration unit 121, a hash calculation unit 122, an accommodation destination calculation unit 123, a reception request registration unit 124, and a command reception unit 125.

FIG. 3 shows the configuration of the application apparatus 102. The application apparatus 102 includes an application logic 131 that provides an input / output function with a user, and a client library 130 that is responsible for a communication function with a transfer server group. The client library 130 includes a hash calculation unit 132, an accommodation destination calculation unit 133, and a command registration unit 134. Here, the hash calculation unit 132 and the accommodation destination calculation unit 133 are functional units similar to the hash calculation unit 122 and the accommodation destination calculation unit 123 included in the sensor 101, perform hash calculation and accommodation destination calculation by the same method, The consistency of the calculation results shall be maintained.
FIG. 4 shows the configuration of the transfer server 103. The transfer server 103 includes an event reception unit 141, a reception request reception unit 142, a reception request holding unit 143, a command reception registration unit 144, a condition comparison unit 145, and a command transfer unit 146.

  In the present embodiment, the entire sensor information transfer system is constructed based on the uTupleSpace technology shown in Non-Patent Document 1 and Non-Patent Document 2. In other words, the transfer server group described above implements the function of “uTupleServer” in Non-Patent Document 1 or “Tuple Server” in Non-Patent Document 2. Further, the client library 120 and the client library 130 implement the function of “uTupleClient” in Non-Patent Document 1. Details of these techniques are fully disclosed and can be implemented by those skilled in the art. In particular, it is possible to process event data from sensors. Alternatively, in particular, a process for installing a plurality of transfer servers and distributing the load among them can be implemented except that the problems of the prior art described above are still unsolved. Here, the problem of the prior art is a problem that in a typical command transmission application of a certain type in the prior art that performs dynamic load distribution of sensor information transfer, sufficient load reduction cannot be achieved by load distribution.

Therefore, in the following, in view of the gist of the present invention to solve the above-described problems of the prior art, an embodiment will be described in detail particularly regarding processing related to transmission of command data to a sensor.
FIG. 5 shows the configuration of the sharing management server 104. The sharing management server 104 includes a sharing management table 150 and a request processing unit 151. The sharing management table 150 is information stored in the storage area of the sharing management server 104, and is managed by a hash table having character strings as keys and values of one or more transfer servers. Here, as will be described later, the hash calculation unit 122 of the sensor 101 or the hash calculation unit 132 of the application apparatus 102 transmits a hash query request including a character string of a type attribute value indicating the type of information to the sharing management server 104. To do. The request processing unit 151 of the sharing management server 104 receives this, searches the hash table using the character string included in the request as a key, and obtains a list of transfer servers. The request processing unit 151 returns the arrangement to the hash calculation unit 122 of the sensor 101 or the hash calculation unit 132 of the application apparatus 102. Through the above-described series of processing procedures, the hash calculation unit 122 of the sensor 101 or the hash calculation unit 132 of the application apparatus 102 performs a calculation process for obtaining a sequence of transfer servers from a character string so that a unique result can be obtained in the entire system. Realize.

In the present embodiment, the output “transfer server C” is returned for the input “alarm_lamp”, and the outputs “transfer server D, transfer server A, transfer server B” are returned for the input “buzzer”. explain. A method for realizing the above-described sharing management server 104 and sharing management table 150 is disclosed in detail in Non-Patent Document 2.
Here, the type attribute value indicating the type of information is meta information indicating the characteristics of the sensor information in the present invention. In the present embodiment, information such as CF and CA or EA and EF is used. Is an attribute representing the sensor type included. Specifically, in a data format exemplified by CF (CF 170 to 172) and CA (230 to 231), which will be described later, for example, a character string “buzzer” described as type = buzzer in CA 230 is shown. However, the scope of the present invention is not limited to this, and the meta information indicating the characteristics of the sensor information in the present invention may be any meta information that is widely given to the sensor information. For example, in addition to those described above, information indicating the application genre, information indicating the owner or viewer of the information, information indicating the business operator, information for distinguishing the name space, and the like may be used. As described above, the data format handled in the present embodiment is expressed as a variable length sequence such as “attribute name = attribute value, attribute name = attribute value, attribute name = attribute value...”.

  FIG. 6 shows the contents of the address table 160 held by the accommodation destination calculation unit 123 (accommodation destination calculation unit 133). In this embodiment, “0x0011” is assigned to the sensor A as a unique identifier (ID), “0x0012” is assigned to the sensor B as a unique ID, and “0x0013” is assigned to the sensor C as a unique ID. It shall be assumed. The address table 160 is a table for obtaining a corresponding transfer server name from the sensor ID. The accommodation destination calculation unit 123 (accommodation destination calculation unit 133) uses the table and implements a calculation function in which the sensor ID is input and the transfer server name is output. Note that the hash calculation unit 122 (hash calculation unit 132) and the accommodation destination calculation unit 123 (accommodation destination calculation unit 133) include systems including the client library 120 in the sensor and the client library 130 in the application apparatus 102. The same calculation result shall be returned as a whole. In particular, the address table 160 of the accommodation destination calculation unit 123 (accommodation destination calculation unit 133) is assumed to be individually held by each device in the present embodiment. However, the scope of the present invention is not limited to this. For example, a server device dedicated to the management of the address table is separately prepared on the network, and the accommodation destination calculation unit 123 (accommodation destination calculation unit 133) in each device By making an inquiry to the server device, the accommodation destination calculation unit 123 (accommodation destination calculation unit 133) may return the same calculation result for the entire system.

  FIG. 7 shows the CF registered in the present embodiment and the CF to be registered. In the following example, a processing procedure when the sensor 101B intends to newly register the CF 172 in a state where the sensor 101A has already registered the CF 170 and the sensor 101C has already registered the CF 171 will be exemplified. For example, CF 171 indicates that it is waiting for a drive request for a buzzer whose sensor ID is 0x0013 and the current position is in room 101. For example, CF 172 indicates that it is waiting for a driving request for an alarm lamp whose sensor ID is 0x0012 and the current position is in room 201.

  FIG. 8 shows the procedure of CF registration processing in the sensor 101B. The sensor 101B starts executing this procedure when the power is turned on (step S101). Here, the CF 172 to be input is easy to generate because the information unique to the sensor 101B is expressed as a character string. First, the type attribute value in the CF 172 is input to the hash calculation unit 122 to obtain a transfer server list, in this example, the transfer server C (step S102). Next, the reception request registration unit 124 generates a new CF from which the address attribute is deleted from the CF, and sets the new CF and the registration reason “hash” for any one of the transfer servers. A CF registration request is transmitted (step S103). The CF registration request is received by the reception request receiving unit 142 of the transfer server 103C and stored in the reception request holding unit 143.

  Next, the sensor 101B inputs the address attribute value in the CF 172 to the accommodation destination calculation unit 123, and obtains the transfer server B (step S104). Next, the reception request registration unit 124 transmits a CF registration request including the CF and the registration reason “address” to the transfer server (step S105). The CF registration request is received by the reception request receiving unit 142 of the transfer server 103B and stored in the reception request holding unit 143. The procedure of the CF registration process in the sensor 101B ends here.

  Note that the case where the list of transfer servers obtained by the hash calculation unit 122 is two or more may occur when dynamic load balancing is performed in the conventional technology. Non-Patent Document 2 discloses details of the implementation method. The outline of the processing method in such a case is as described above. That is, when the sensor 101 registers CF, any one of the transfer servers in charge obtained by the hash function is assigned a random number or the like. The CF is selected by an arbitrary method, and the CF is transmitted only to the transfer server. On the other hand, when the application apparatus 102 registers the CA, the CA is transmitted to all the transfer servers 103 included in the group of transfer servers in charge obtained by the hash function.

  FIG. 9 shows a configuration of the reception request holding unit 143 (reception request holding unit 143A) of the transfer server 101A. The reception request holding unit 143A stores a CF waiting table 180 (CF waiting table 180A). The first row of the table corresponds to CF170. The first digit of each row means the CF held by the table. Further, the second digit of each line means the registration reason transmitted together with the registration request of the CF. The third digit of each row means which sensor has transmitted the registration request for the CF. The table does not change as a result of the CF registration process.

  FIG. 10 shows a configuration of the reception request holding unit 143 (reception request holding unit 143B) of the transfer server 103B. The reception request holding unit 143B stores a CF waiting table 180 (CF waiting table 180B). The first row of the table corresponds to CF171. The second row (symbol a) in the table corresponds to the newly registered CF 172, and is a portion that has been added and saved as a result of the CF registration processing procedure. The first digit of the row indicates the contents of the CF 172, the second digit indicates the registration reason “address”, and the third digit indicates that the registration source sensor is the sensor 101B.

  FIG. 11 shows a configuration of the reception request holding unit 143 (reception request holding unit 143C) of the transfer server 103C. The reception request holding unit 143C stores a CF waiting table 180 (CF waiting table 180C). The first row of the table corresponds to CF170. The second row (symbol a) in the table corresponds to the newly registered CF 172, and is a portion that has been added and saved as a result of the CF registration processing procedure. The first digit of the line is the content of CF 172 with the address attribute deleted in step S103, the second digit is the registration reason “hash”, and the third digit is the registration source sensor 101B. Respectively.

  FIG. 12 shows the configuration of the reception request holding unit 143 (reception request holding unit 143D) of the transfer server 103D. The reception request holding unit 143D stores a CF waiting table 180 (CF waiting table 180D). The first row of the table corresponds to CF171. The table does not change as a result of the CF registration process. For the registration reason “hash” of CF 171, since the search result of “buzzer” in the assignment management table 150 is “transfer server D, transfer server A, transfer server B”, transfer server D, transfer There is a possibility that the reception request holding unit 143 in either one of the server A and the transfer server B holds the CF as a registration reason “hash”. Here, as an example of the description in this embodiment, an example of data is shown assuming that the transfer server D holds the CF. In other words, in order to perform matching between a certain CA and the CF without omission, it is necessary to perform all of the possibilities by performing matching processing in all of the transfer server D, transfer server A, and transfer server B. It is shown that. The flow of this process is as described in detail in the implementation method disclosed in Non-Patent Document 2. Through the CF registration process described above, the CF is registered in the transfer server group, and the entire system is in a state of waiting for the arrival of a new CA.

  FIG. 13 is a diagram showing a CA to be registered in the present embodiment. In the following example, a processing procedure when the application apparatus 102 first newly registers the CA 230 and then further newly registers the CA 231 will be exemplified. For example, CA230 indicates that the request is an on operation for a buzzer with a sensor ID of 0x0013. In this case, the current position indicates that the condition is met regardless of the value. For example, CA (231) indicates that the current position is a red operation request for an alarm lamp included in the range of the 101st room to the 199th room. Thus, each CA includes metadata (conditions) and data. The condition part is subjected to a condition comparison process with the CF in the transfer server, and when the condition is matched, the sensor that registered the CF receives the data of the CA and performs a predetermined operation such as a buzzer or a red alarm. And so on.

FIG. 14 shows the procedure of CA registration processing in the application apparatus 102. In response to the user's operation, the application logic 131 first starts by requesting the client library 130 for registration processing of the CA 230 (step S201). The client library 130 determines whether the CA includes an address attribute (step S202). Since the CA 230 includes the address attribute, next, the address attribute value in the CA is input to the accommodation destination calculation unit 133 to obtain the transfer server 103B (step S203). Next, the command registration unit 134 transmits a CA registration request including the CA as content to the transfer server 103B (step S204).

  The CA registration request is received by the command reception registration unit 144 of the transfer server 103B, and the condition comparison unit 145 performs a condition comparison process between the CA 230 and the CF stored in the reception request holding unit 143. As a result, since it matches the CF held in the first row of the CF waiting table 180 (CF waiting table 180B), the command transfer unit 146 sends the CA to the third digit sensor in the row, that is, the sensor 101C. Send. The command receiving unit 125 of the sensor 101C receives the CA, and since the CA is type = buzzer, the sensor 101C operates the buzzer 128 included in the value on, that is, rings.

  Next, in response to a user operation, the application logic 131 starts by requesting the CA 231 registration processing from the client library 130 (step S201). The client library 130 determines whether the CA includes an address attribute (step S202). Since the CA 231 does not include the address attribute, the type attribute value in the CA is input to the hash calculation unit 132 to obtain a transfer server list, in this example, the transfer server C (step S205). Next, the command registration unit 134 transmits a CA registration request including the CA as content to all the transfer servers included in the transfer server list (step S204). In the present embodiment, if the CA to be processed in step S205 does not include the type attribute value, it is an input error of the client library 130.

  Note that the case where there are two or more transfer server lists obtained by the hash calculation unit 132 may occur when dynamic load balancing is performed in the prior art, and is realized in Non-Patent Document 2. As described above, the details of the method are disclosed. The CA registration request is received by the command reception registration unit 144 of the transfer server 103C, and the condition comparison unit 145 performs a condition comparison process between the CA 231 and the CF held by the reception request holding unit 143. As a result, since it matches the CF held in the first row of the CF waiting table 180C, the command transfer unit 146 transmits the CA to the third digit sensor in the row, that is, the sensor 101A. The command receiving unit 125 of the sensor 101A receives the CA, and since the CA is type = alarm_lamp, the sensor 101A operates the alarm lamp 127 included in the value red, that is, lights in red.

  Here, it will be confirmed how the two types of CA registration processes described above are handled efficiently by the present invention. The CA 230 is an operation including an address attribute, and a typical application for generating such a CA includes an advanced remote control application that controls home appliances from a remote location via a sensor information transfer system. As described above, the application has a problem that the overhead associated with CA registration cannot be ignored due to dynamic load distribution in the prior art. According to the present embodiment, this problem can be solved. Specifically, in the above embodiment, a single transfer server is selected in step S203, and therefore, only one transfer server is required for CA registration processing. . For this reason, for example, according to the above-described quantity example, when the CF receives 100 million CAs, that is, control commands, CA registration processing is also performed 100 million times. Even if the load is distributed among the machines, the number of CA registrations is 100 million, which is equal to the number of transfers to the CF, so that the overhead associated with CA registration can be sufficiently reduced.

  If the present invention is not applied, in the above-described embodiment, according to the transfer server responsible for type = buzzer, that is, according to the sharing management table 150, the CA registration is performed on all three transfer servers D, transfer server A, and transfer server C. For this reason, for example, according to the above-described quantity example, the CA registration process is performed 100 million times, and each process is registered with three transfer servers. The number of registrations is 300 million, and there is a problem that the overhead related to CA registration is so large that it cannot be ignored.

  Next, CA 231 is an operation for transmitting a command specifying a range condition without including an address attribute. Such advanced operations utilize the features of advanced data transfer processing provided by uTupleSpace. If the uTupleSpace is not used and the sensor and the application are directly connected via the network, it is difficult to realize the operation. In the present embodiment, even with such a CA, high functionality can be realized because the CA registration process is performed in the transfer server using the conventional processing procedure in step S205.

  As described above, according to the present embodiment, it is possible to easily create a command transmission type application that performs advanced data transfer processing, while performing static and dynamic load distribution thereof. A command transmission type application that allows the application to know a specific transmission destination can also be efficiently realized.

  As described above, the embodiment of the command data transmission process to the sensor according to the present invention has been described in detail. As already described, in the present embodiment, the entire sensor information transfer system can be constructed based on the uTupleSpace technology shown in Non-Patent Document 1 and Non-Patent Document 2. Details of these techniques are well disclosed and can be implemented by those skilled in the art, especially for processing event data from sensors. For example, the sensor data recording process can be performed as follows. That is, the sensor 101A acquires the temperature by the temperature sensor 126 provided, and the event registration unit 121 in the provided client library 120 sends a registration request to the network 105, so that any one of the transfer servers in the transfer server group. EA registration request is sent to one transfer server. Here, EA is a term representing event data (EA) from a sensor in the uTupleSpace technology, and is disclosed in the above document. In the transfer server, the event receiving unit 141 included in the transfer server receives the request, and records the EA in a storage device managed by the transfer server. As for the method for selecting any one of the above transfer servers, Non-Patent Document 1 discloses a method for selecting based on static load distribution, and a method for selecting based on dynamic load distribution. Non-Patent Document 2 discloses the implementation method.

  In the present embodiment, the CA transmission process including the address attribute is handled by one transfer server determined by the address attribute value. However, the scope of the present invention is not limited to this, and a plurality of transfer servers are determined. One transfer server may be responsible for load distribution. In that case, for example, when a list of transfer servers is returned as a search result of the address table 160 and the calculation result of the accommodation destination calculation unit 123 is a list of two or more transfer servers, A part or all of the included transfer servers may appropriately share the CF or CA registration process.

101A to 101C: Sensor 102: Application devices 103A to 103D: Transfer server 104: Sharing management server 105: Network 120: Client library 121: Event registration unit 122: Hash calculation unit 123: Accommodation destination calculation unit 124: Reception request registration unit 125 : Command reception unit 126: Temperature sensor 127: Alarm lamp 128: Buzzer 130: Client library 131: Application logic 132: Hash calculation unit 133: Accommodation calculation unit 134: Command registration unit 141: Event reception unit 142: Reception request reception unit 143: Reception request holding unit 144: Command reception registration unit 145: Condition comparison unit 146: Command transfer unit 150: Allocation management table 151: Request processing unit

Claims (6)

The sensor client device registers a command reception request with the transfer server, the application client device registers command information with the transfer server, and the transfer server receives the command reception request from the sensor client device and the application client device Comparing the condition with the command information, and when the condition is met, the sensor client device constituting the sensor information transfer system for transferring the command information to the sensor client device,
Hash calculation means for identifying one or more transfer servers among the plurality of transfer servers from meta information indicating characteristics of sensor information;
An accommodation destination calculation means for identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device;
A command for registering a command reception request in one of the transfer servers specified by the hash calculation means and registering a command reception request in one of the transfer servers specified by the accommodation destination calculation means A receipt request registration means;
Command information receiving means for receiving command information from the transfer server;
A sensor client device comprising: The sensor client device registers a command reception request with the transfer server, the application client device registers command information with the transfer server, and the transfer server receives the command reception request from the sensor client device and the application client device A condition comparison with command information is performed, and the application client device constituting a sensor information transfer system that transfers command information to the sensor client device when the condition is met,
The command information to be transmitted by the application client device includes either the ID of the sensor client device to which the command information is to be transmitted, or meta information indicating the characteristics of the sensor information,
Hash calculation means for identifying one or more transfer servers among the plurality of transfer servers from meta information indicating characteristics of sensor information;
Accommodation destination calculating means for identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device that is to transmit command information;
When the command information to be transmitted includes the ID of the sensor client device to which the command information is to be transmitted, the command information is registered and transmitted to the transfer server specified by the accommodation destination calculation means Command information registration means for registering the command information in all the transfer servers specified by the hash calculation means when the command information does not include the ID of the sensor client device to send the command information;
An application client device comprising: A sensor information transfer system in which one or more sensor client devices, one or more application client devices, and one or more transfer servers are connected via a network and load distribution of command transmission is performed.
The sensor client device
First hash calculation means for identifying one or more transfer servers of the plurality of transfer servers from meta information indicating characteristics of sensor information;
First accommodation destination calculation means for identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device;
A command reception request is registered in one of the transfer servers specified by the first hash calculation unit, and a command is stored in one of the transfer servers specified by the first accommodation destination calculation unit. A command reception request registration means for registering a reception request;
Command information receiving means for receiving command information from the transfer server,
The application client device
The command information to be transmitted by the application client device includes either the ID of the sensor client device to which the command information is to be transmitted, or meta information indicating the characteristics of the sensor information,
Second hash calculation means for specifying one or more transfer servers among the plurality of transfer servers from meta information indicating characteristics of sensor information;
Second accommodation destination calculating means for identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device that is to transmit command information;
When the command information to be transmitted includes the ID of the sensor client device to which the command information is to be transmitted, the command information is registered in the transfer server specified by the second accommodation destination calculating means and transmitted. Command information registration for registering the command information in all transfer servers specified by the second hash calculation means when the command information to be transmitted does not include the ID of the sensor client device to which the command information is to be transmitted Means, and
The transfer server
Holding means for receiving and holding a command reception request;
Registration means for registering command information;
A condition comparison means for comparing the registered command information with the condition included in the held command reception request;
Transfer means for transferring the command information matched as a result of the comparison to a registration source of the command reception request;
A sensor information transfer system comprising: The sensor client device registers a command reception request with the transfer server, the application client device registers command information with the transfer server, and the transfer server receives the command reception request from the sensor client device and the application client device A command information reception method for the sensor client device that constitutes a sensor information transfer system that performs a condition comparison with command information and transfers the command information to the sensor client device when the condition is met,
A hash calculation step of identifying one or more transfer servers among the plurality of transfer servers from the meta information indicating the characteristics of the sensor information;
An accommodation destination calculation step for identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device;
A command for registering a command reception request in one of the transfer servers specified in the hash calculation step, and registering a command reception request in one of the transfer servers specified in the accommodation destination calculation step A receipt request registration process;
A command information receiving step for receiving command information from the transfer server;
A command information receiving method comprising: The sensor client device registers a command reception request with the transfer server, the application client device registers command information with the transfer server, and the transfer server receives the command reception request from the sensor client device and the application client device A command information registration method of the application client device that constitutes a sensor information transfer system that performs a condition comparison with command information and transfers the command information to the sensor client device when the condition is met,
The command information to be transmitted by the application client device includes either the ID of the sensor client device to which the command information is to be transmitted, or meta information indicating the characteristics of the sensor information,
A hash calculation step of identifying one or more transfer servers among the plurality of transfer servers from the meta information indicating the characteristics of the sensor information;
An accommodation destination calculating step of identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device that is to transmit command information;
When the command information to be transmitted includes the ID of the sensor client device to which the command information is to be transmitted, the command information is registered and transmitted to the transfer server specified in the accommodation destination calculation step. A command information registration step of registering the command information in all the transfer servers specified in the hash calculation step when the command information does not include the ID of the sensor client device to which the command information is to be transmitted;
A command information registration method comprising: A sensor information transfer method for a sensor information transfer system in which one or more sensor client devices, one or more application client devices, and one or more transfer servers are connected via a network and load distribution of command transmission is performed.
The sensor client device is
A first hash calculation step for identifying one or more transfer servers among the plurality of transfer servers from meta information indicating characteristics of sensor information;
A first accommodation destination calculation step of identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device;
A command reception request is registered in one of the transfer servers specified in the first hash calculation step, and a command is stored in one of the transfer servers specified in the first accommodation destination calculation step. A command reception request registration step for registering a reception request;
A command information receiving step for receiving command information from the transfer server, and
The command information to be transmitted by the application client device includes either the ID of the sensor client device to which the command information is to be transmitted, or meta information indicating the characteristics of the sensor information,
The application client device is
A second hash calculation step of identifying one or more transfer servers among the plurality of transfer servers from meta information indicating the characteristics of sensor information;
A second accommodation destination calculation step of identifying one or more transfer servers among the plurality of transfer servers from the ID of the sensor client device to transmit command information;
When the command information to be transmitted includes the ID of the sensor client device to which the command information is to be transmitted, the command information is registered in the transfer server specified in the second accommodation destination calculation step and transmitted. Command information registration for registering the command information in all the transfer servers specified in the second hash calculation step when the command information to be transmitted does not include the ID of the sensor client device to which the command information is to be transmitted A process,
The transfer server
A holding process for receiving and holding a command reception request;
A registration process for registering command information;
A condition comparison step for comparing the registered command information with the conditions included in the held command reception request;
A transfer step of transferring the command information matched as a result of the comparison to a registration source of the command reception request;
A sensor information transfer method comprising:

Images