JP7000884B2 - Data acquisition system and server - Google Patents

Description

The present invention relates to a data acquisition system and a server included in the data acquisition system.

Patent Document 1 discloses a system including a mobile terminal device and a management center. In the system disclosed in Patent Document 1, the management center includes a storage unit that manages the positions and attributes of the registered moving objects. The mobile terminal device that wants to discover a mobile body notifies the management center of the discovery conditions including the position of the mobile body. The management center notified of the discovery condition searches the storage unit for a moving object that matches the discovery condition. Then, the position of the mobile body found as a result of the search is transmitted to the mobile terminal device that has notified the discovery condition.

Japanese Patent No. 372001

In the technique of Patent Document 1, the management center registers the attributes of each mobile body in advance, and the mobile terminal uploads the updated position data to the management center when the position data is updated. Each item of the discovery condition transmitted by the mobile terminal device to the management center corresponds to any item of the mobile data stored in the storage unit of the management center. The purpose of Patent Document 1 is to discover a moving object having a certain attribute. For this purpose, each mobile terminal device sequentially uploads the current position to the management sensor.

In Patent Document 1, the data sequentially updated by the mobile terminal device is only the position data, but the terminal used in the mobile acquires data that changes sequentially such as image data and audio data in addition to the position data. It is widely known that you can do it. For example, in-vehicle devices and mobile terminals that can acquire image data and audio data and upload them to a center or the like are known. Further, the use of the data provided by the terminal is not limited to the use of discovering a moving object, and various uses can be considered. The more types of data there are, the more possible uses the data can be.

When the data has various uses, various attributes that specify the data can be considered. When various attributes for specifying data are considered, the attribute for specifying data in a terminal that provides data to another device (hereinafter, data providing terminal) is a device used by a user who needs the data (hereinafter, user device). ) Is often different from the attribute that specifies the data.

An example will be described. For example, since the user device needs an image of the intersection x, the data is specified by using the data type as an image and the target position, that is, the position shown in the image as the intersection x. On the other hand, the data providing terminal identifies the image data in association with the data imaging position. Therefore, even if the image shows the intersection x, the attribute for specifying the data is the image data captured at a position y different from the intersection x.

The data required by the user device, in other words, the data requested by the user device to be acquired is not the data that can be provided by the data providing terminal, but the data derived from the data provided by one or more data providing terminals. In some cases.

In order for the user device to acquire the required data, the data providing terminal can specify the required data by knowing what kind of attribute the data required by the user device is specified by the data providing terminal. It can be expressed by various attributes. However, it is often difficult for a user who uses the user device to express the data required by the user device with an attribute that can be specified by the data providing terminal.

The present invention has been made based on this circumstance, and an object of the present invention is to provide a data acquisition system in which a user apparatus can easily acquire necessary data, and a server included in the data acquisition system. There is something in it.

The above object is achieved by a combination of the features described in the independent claims, and the subclaims provide for further advantageous embodiments of the invention. The reference numerals in parentheses described in the claims indicate, as one embodiment, the correspondence with the specific means described in the embodiments described later, and do not limit the technical scope of the present invention. ..

The invention relating to the data acquisition system for achieving the above object is
From the user device (2), the server (3, 103, 203, 903) that acquires a primary query that is a data acquisition request including the requirement of the user request data requested by the user device, and the user request data and the user request data are obtained. It is a data acquisition system that includes a data providing terminal (4) that provides terminal-provided data that is any of the derivable data, and the user apparatus acquires user request data.
The server is
The primary query acquisition unit (331) that acquires the primary query from the user device,
From the primary query acquired by the primary query acquisition unit, the data providing terminal determines the secondary query that is the data acquisition request that specifies the user request data requested by the primary query with the attribute that can specify the terminal provided data. Secondary query determination unit (333, 1333) and
It is equipped with a server transmission unit (311) that sends the secondary query determined by the secondary query determination unit to the data providing terminal.
The data providing terminal is
A terminal receiver (412) that receives the secondary query sent by the server, and
A data acquisition unit (442) that executes a secondary query received by the terminal reception unit to acquire terminal-provided data, and
It includes a terminal transmission unit (411) that transmits the terminal-provided data acquired by the data acquisition unit to a device determined by a secondary query.

Further, the invention relating to the server for achieving the above object is
A server (3, 103, 203) that acquires a primary query, which is a data acquisition request including a requirement of user request data, which is data requested by the user device, from the user device (2).
The primary query acquisition unit (331) that acquires the primary query from the user device,
Primary query An attribute that can identify the terminal-provided data, which is either the user request data or the data from which the user request data can be derived, from the primary query acquired by the primary query acquisition unit. The secondary query determination unit (333, 1333) that determines the secondary query that is the data acquisition request that specifies the user request data requested by the query, and
It includes a server transmission unit (311) that transmits a secondary query determined by the secondary query determination unit to a data providing terminal.

According to these inventions, when the user apparatus transmits a primary query to the server, the server requests the user request by the primary query with an attribute that allows the data providing terminal to identify the terminal-provided data from the primary query. Determines a secondary query that is a data acquisition request that identifies terminal-provided data that is either data or data that can be derived from user request data. Since this secondary query is sent to the data providing terminal, the data providing terminal can be used even if the user using the user device does not express the data required by the user device with an attribute that can be identified by the data providing terminal. It is possible to specify the terminal-provided data to be provided. Therefore, the user device can easily acquire the necessary data.

It is an overall block diagram of the data acquisition system 1 of 1st Embodiment. It is a block diagram which shows the structure of the remote monitoring apparatus 2 of FIG. It is a block diagram which shows the structure of the server 3 of FIG. It is a figure which shows the terminal requirement correspondence table. It is a figure which shows the query correspondence table. It is a block diagram which shows the structure of the data providing terminal 4 of FIG. It is a flowchart which shows the process which the control unit 33 of FIG. 3 executes. It is a figure which shows the query correspondence table used in 2nd Embodiment. It is a figure which shows the receiving terminal requirement determined in 3rd Embodiment. It is a figure which shows the secondary query determined in 3rd Embodiment. It is a block diagram which shows the structure of the server 103 of 4th Embodiment. It is a block diagram which shows the structure of the server 203 of 5th Embodiment. It is a block diagram which shows the structure of the server 903 of the 9th Embodiment.

Hereinafter, a plurality of embodiments of the present disclosure will be described with reference to the drawings. In addition, duplicate description may be omitted by assigning the same reference numerals to the corresponding components in each embodiment and modification. When only a part of the configuration is described in each embodiment and modification, the configuration of the other embodiment and modification described above can be applied to the other part of the configuration. Further, not only the combination of the configurations specified in the description of each embodiment and the modified example, but also the configurations of the plurality of embodiments and the modified example are partially combined even if the combination is not specified. Can be combined with. Further, an unspecified combination of the configurations described in the plurality of embodiments and modifications is also disclosed by the following description.

<First Embodiment>
As shown in FIG. 1, the data acquisition system 1 according to the first embodiment includes a remote monitoring device 2, a server 3, and a data providing terminal 4. The outline of the data acquisition system 1 will be described with reference to FIG.

The remote monitoring device 2 corresponds to a user device operated by a user who requests user request data. Further, the user request data is data requested by the user apparatus. The remote monitoring device 2 is used for the purpose of acquiring image data and remotely monitoring the points reflected in the image data. The remote monitoring device 2 sends a primary query to the server 3. The details of the primary query will be described later, but in the first embodiment, the primary query is a request for transmitting image data to a query request source, and the data specified by this primary query is user request data. The query request source means the source of the primary query.

The server 3 acquires the primary query and determines the secondary query from the primary query. Then, the determined secondary query is transmitted to the data providing terminal 4. The details of the secondary query will be described later, but in the first embodiment, the secondary query is a request to acquire image data and send the acquired image data to the server 3.

The data providing terminal 4 is mounted on the vehicle 5. Here, the vehicle 5 is a four-wheeled vehicle traveling on a road or a vehicle having more tires than four wheels such as a large truck. However, a two-wheeled vehicle may be included in the vehicle.

When the data providing terminal 4 acquires the secondary query, the data providing terminal 4 executes the secondary query. In the first embodiment, the secondary query is a request to acquire image data and transmit the acquired image data to the server 3. Therefore, the data providing terminal 4 acquires the image data and transmits the acquired image data to the server 3. The data provided by the data providing terminal 4 by executing the secondary query is the terminal provided data.

The server 3 transmits the acquired image data to the remote monitoring device 2. As a result, the remote monitoring device 2 can acquire image data.

[Configuration of remote monitoring device 2]
As shown in FIG. 2, the remote monitoring device 2 includes an input unit 21, a communication unit 22, a storage unit 23, a display unit 24, and a control unit 25. The input unit 21 is a part operated by the user to input a primary query, and is, for example, a keyboard. The communication unit 22 transmits / receives data to / from the server 3. The communication unit 22 may be wireless communication or wired communication. The storage unit 23 stores image data transmitted from the server 3. The display unit 24 displays the image indicated by the image data transmitted from the server 3.

The control unit 25 controls the communication unit 22, the storage unit 23, and the display unit 24. When the primary query is input from the input unit 21, the control unit 25 transmits the primary query from the communication unit 22 to the server 3. When the image data requested by the primary query is transmitted from the server 3, the image data is stored in the storage unit 23, and the image indicated by the image data is displayed on the display unit 24.

[Configuration of server 3]
As shown in FIG. 3, the server 3 includes a server communication unit 31, a storage unit 32, and a control unit 33. The server communication unit 31 includes a server transmission unit 311 and a server reception unit 312. The server transmission unit 311 transmits data to the data providing terminal 4 and the remote monitoring device 2. The data transmitted to the data providing terminal 4 is a secondary query, and the data transmitted to the remote monitoring device 2 is the data requested by the primary query.

The server transmission unit 311 may separately include a portion for transmitting data to the data providing terminal 4 and a portion for transmitting data to the remote monitoring device 2, or the data providing terminal 4 and the remote monitoring device may be provided with the same configuration. Data may be transmitted to 2. Since the data providing terminal 4 is mounted on the vehicle 5 which is a mobile body, the data transmission to the data providing terminal 4 is wireless transmission. Note that wireless transmission means that the transmission path from the base station to the data providing terminal 4 is wireless, and the communication between the base station and the server 3 may be wired.

The server receiving unit 312 receives data from the data providing terminal 4 and the remote monitoring device 2. The data received from the data providing terminal 4 is the data requested by the secondary query, and the data received from the remote monitoring device 2 is the primary query.

The server receiving unit 312 may separately include a part for receiving data from the data providing terminal 4 and a part for receiving data from the remote monitoring device 2, or the data providing terminal 4 and the remote monitoring device have the same configuration. Data may be received from 2. However, the reception of data from the data providing terminal 4 is wireless reception. As with wireless transmission, wireless reception means that the reception path from the base station to the data providing terminal 4 is wireless.

The storage unit 32 includes a writable non-transitional substantive storage medium such as a flash memory, and functions as a data holding unit 321, a query correspondence table storage unit 322, and a terminal requirement correspondence table storage unit 323.

The data holding unit 321 holds the data transmitted from the data providing terminal 4 and received by the server receiving unit 312. The data held in the data holding unit 321 includes the terminal ID of the data providing terminal 4, the information of the secondary query that can be executed by the data providing terminal 4, and the IP address of the data providing terminal 4. The information determined for each of these data providing terminals 4 is called probe information. The secondary query information included in the probe information that can be executed by the data providing terminal 4 is used by the terminal communication unit 41 of the data providing terminal 4 to determine what kind of sensor the sensor unit 42 of the data providing terminal 4 has. It may include possible communication line types, communication speeds, and the like.

Further, the data providing terminal 4 periodically transmits the position of the data providing terminal 4 to the server 3, and the data holding unit 321 also includes the latest position and the past position of the data providing terminal 4 together with the terminal ID. Be retained. The latest position and the past position of the data providing terminal 4 are also a part of the probe information. The history of the past position means the movement history of the data providing terminal 4. In addition, the vehicle speed can be calculated from the position history. The probe information may include the vehicle speed.

Further, the data holding unit 321 also stores information for determining whether or not each data providing terminal 4 corresponds to the receiving terminal requirement. This information is, for example, the type of sensor included in the data providing terminal 4. Further, the latest position of the data providing terminal 4 can also be information for determining whether or not each data providing terminal 4 corresponds to the receiving terminal requirement. The information of the secondary query that can be executed by the data providing terminal 4 can also be used as information for determining the data providing terminal 4 that receives the secondary query. Further, the data holding unit 321 also holds the data transmitted to the server 3 by the data providing terminal 4 by executing the secondary query.

The query correspondence table storage unit 322 stores the query correspondence table, and the terminal requirement correspondence table storage unit 323 stores the terminal requirement correspondence table. The query correspondence table is a correspondence table between a primary query and a secondary query. The terminal requirement correspondence table is a correspondence table between the primary query and the receiving terminal requirement.

Both the query correspondence table and the terminal requirement correspondence table are prepared regardless of whether or not the user apparatus sends a primary query, and are sequentially updated by the administrator of the server 3.

[Terminal requirement correspondence table]
The terminal requirement correspondence table will be described with reference to FIG. The server 3 determines the data providing terminal 4 to send the secondary query based on the terminal requirement correspondence table. Since a primary query is required to explain the terminal requirement correspondence table, the primary query will be explained first.

The primary query is a data acquisition request including a requirement for data (that is, user request data) requested by the remote monitoring device 2 which is a user device. That is, the primary query represents what kind of requirement data is needed. The requested data (hereinafter referred to as target data) is represented by an attribute and requirements for that attribute. This requirement is called the target data requirement. Requirements can also be said to be conditions. A query is a request including a target data requirement and a process for the target data (hereinafter referred to as a target process).

As a specific example, first, No. 1 in the table shown in FIG. The primary query described in 1 will be described. No. The primary query of 1 is a process in which the target process transfers data to the query request source. The target data requirements define requirements for two attributes. The first attribute is the data type, and the requirement for that attribute is an image. The second attribute is the target position, the requirement of which is the intersection x. The target position means the position shown in the image. Therefore, No. The target data requirement of the primary query of 1 is the requirement of image data in which the intersection x is shown. The intersection x may be coordinates, but here it is a name. If you have map data, if you know the name of the intersection, you can specify the position, which is an attribute, by coordinates. The intersection x, which is the name, is an attribute that can be identified from the map data.

No. The primary query described in 2 is No. Same as 1. No. In the primary query described in 3, the target process is No. Same as 1. On the other hand, the target data requirements are No. Different from 1. No. The target data requirements of the primary query described in 3 define the requirements for the three attributes. The first attribute is the data type, and the requirement for this is the average moving speed. The second attribute is the position area, and the requirement for this is a circle with a radius of 100 m centered on the intersection x. The third attribute is time, and the requirement for this is time t.

Next, the receiving terminal requirements will be described. The receiving terminal requirement is a requirement included in the data providing terminal 4 that receives the secondary query. The receiving terminal requirement includes a terminal type C. Terminal type C is also one of the requirements. In the example of FIG. 4, requirements are set for two attributes apart from the terminal type C.

A specific example of the receiving terminal requirement will be described. No. The receiving terminal requirement of 1 is that the terminal type C is the terminal type C1. The terminal type C1 is a data providing terminal 4 provided with a front camera 421 (see FIG. 6). No. The first attribute in the receiving terminal requirement of 1 is the latest own vehicle position, and the requirement for this is within a circle having a radius of 100 m centered on the coordinates (a, b) of the intersection x.

The inside of a circle having a radius of 100 m centered on the coordinates (a, b) of the intersection x is determined as a map range in which the target data (that is, the image of the intersection x) requested by the primary query can be acquired. Instead of this radius of 100 m, the visibility distance of the front camera 421 may be used. When the visibility distance is used, the visibility distance of the front camera 421 is acquired in advance for each data providing terminal 4.

The second attribute is the position of the own vehicle one second before the latest time, and the requirement for this is that the position is farther from the coordinates (a, b) of the intersection x than the latest position of the own vehicle. This requires that the vehicle is close to the coordinates (a, b). In order to determine the second requirement, for example, if the latest vehicle position is y (0) and the vehicle position one second ago is y (-1), | y (0) -x | ≦ It will be determined whether | y (-1) -x | holds.

No. In the receiving terminal requirement of 2, the terminal type C is the terminal type C2. The terminal type C2 is a data providing terminal 4 having a rear camera 422 (see FIG. 6) in addition to the front camera 421. No. The first attribute and requirement in the receiving terminal requirement of No. 2 is No. Same as 1. However, No. As for the receiving terminal requirement of 2, the requirement for the second attribute is not defined. The reason for this is that since the cameras are provided in the front and rear, there is a possibility that an image showing the intersection x can be acquired even if the distance is away from the coordinates (a, b) of the intersection x.

No. In the receiving terminal requirement of 3, the terminal type C is not specified. The reason for this is that it is premised that the position can be acquired by any data providing terminal. The server 3 registers in advance the terminal ID of the data providing terminal 4 and the information of the secondary query that can be executed by the data providing terminal 4. In this embodiment, it is a condition of registration that the position can be acquired.

No. As for the receiving terminal requirement of 3, the requirement is defined for two attributes. The first attribute is the position, and the requirement for this is a circle having a radius of 100-position accuracy (m) centered on the coordinates (a, b) of the intersection x. In the primary query, the second requirement is a circle with a radius of 100 m centered on x, so in order to ensure that it is limited to the data providing terminal 4 within the circle with a radius of 100 m centered on x, the position The value obtained by subtracting the error from 100 m is the requirement for the position.

The second attribute and characteristic is the same as the third attribute and requirement of the primary query, which is the requirement that the time is t. Therefore, in order to determine whether or not the receiving terminal requirement is satisfied, the position of the data providing terminal 4 at time t is required. The server 3 sequentially acquires the position of the data providing terminal 4 as probe information. However, since the acquisition cycle is discrete, it is not always possible to acquire the position at time t. When the position of the data providing terminal 4 at the time t has not been acquired, the position of the data providing terminal 4 at the time t may be obtained by interpolation from the position acquired at the time of acquiring the probe information before and after the time t. The position here is data corresponding to the receiving terminal requirement.

In addition, No. 1, No. The receiving terminal requirement of 2 includes a sufficiency score. The sufficiency score is a value obtained by quantifying the degree to which the requirements are satisfied for at least one requirement included in the receiving terminal requirements. The requirement quantified in this embodiment is the first requirement.

No. The sufficiency score in 1 is represented by 1 / {max (10 m, | y-x |)}. In this equation representing the sufficiency score, y means that the latest vehicle position is adopted, and max means that the larger side of the numerical values shown in () is adopted. Therefore, the denominator of the formula for calculating the sufficiency score is 10 m, which is the larger value of the distance from the latest vehicle position to the coordinates (a, b) of the intersection x. The reason why the distance from the latest vehicle position to the coordinates (a, b) is compared with 10 m is that if the vehicle position is too close to the coordinates (a, b), the intersection x may be difficult to appear in the image. This is because it was taken into consideration.

No. The sufficiency score in 2 is represented by 2 / {max (10 m, | y-x |)}. No. Compared with the formula for calculating the sufficiency score in 1, the difference is that the numerator changes from 1 to 2. No. The receiving terminal requirement in 2 requires that the terminal type C is a terminal including the front camera 421 and the rear camera 422. Therefore, No. which requires only the front camera 421. Compared with the case where the receiving terminal requirement of 1 is satisfied, the possibility of satisfying the receiving terminal requirement is doubled. For this reason, No. The sufficiency score in 2 is No. The formula for calculating the sufficiency score is defined so as to be twice as high as the sufficiency score in 2.

The two sufficiency scores shown in FIG. 4 become higher as the denominator is smaller. Therefore, if the latest vehicle position is near the intersection x, the sufficiency score will be high. The sufficiency score is used to determine the data providing terminal 4 to which the secondary query is transmitted when the number of data providing terminals 4 satisfying the requirements excluding the sufficiency score among the receiving terminal requirements is larger than the required number. The required number is preset for each primary query based on the data type included in the primary query and the like.

[Query Response Table]
Next, the query correspondence table will be described with reference to FIG. The query correspondence table is a correspondence table between the primary query and the secondary query, and since the primary query has already been explained, the secondary query will be described. The secondary query is an attribute that allows the data providing terminal 4 to specify the data, and is a data acquisition that specifies the terminal-provided data that is either the user request data requested by the primary query or the data from which the user request data can be derived. It is a request and is transmitted to the data providing terminal 4. The data from which the user request data can be derived is not limited to the data from which the user request data can be derived from one type of data, but also includes the data from which the user request data can be derived by combining a plurality of types of data.

The reason why the primary query is not sent to the data providing terminal as it is is that the primary query may not be represented by an executable expression of the data providing terminal 4. Therefore, from the primary query, the data providing terminal 4 determines the secondary query in which the data requested by the primary query is specified by the attribute that can identify the data. The secondary query also includes the target data and the target process.

A specific example of the secondary query shown in FIG. 5 will be described. No. shown in FIG. 1 to No. In each of the secondary queries of 3, the target process is a process of sending to the server 3. No. The target data requirement of the secondary query of 1 defines the requirement for two attributes. The first attribute is the sensor type, and the requirement for this is the front camera. The second attribute is the position of the own vehicle, and the requirement for this is that the position of the own vehicle is located within the visibility range in front of the intersection x which is the target position. The visibility distance is a range of distance and viewing angle determined by predetermined items such as the resolution of the front camera 421, camera performance such as lens f-number, and weather.

The data providing terminals 4 that transmit the secondary query are narrowed down in the receiving terminal table described with reference to FIG. The secondary query of 1 is transmitted to the data providing terminal 4 approaching the intersection x. Therefore, the second requirement is that the position of the own vehicle is limited to the front of the intersection x.

No. The target data requirement of the secondary query of 2 also defines the requirement for two attributes. The first attribute is the sensor type, and the requirement for this is the camera on the intersection x side of the front camera 421 and the rear camera 422.

The second attribute is the position of the own vehicle, and the requirement for this is that the position of the own vehicle is located within the visibility range from the coordinates (a, b) of the intersection x. No. In the secondary query of 1, the second requirement was before the intersection x. On the other hand, No. In the secondary query of 2, the reason why the distance from the vehicle position to the coordinates (a, b) of the intersection x is simply set instead of the distance before the intersection x is that the data providing terminal 4 that executes this secondary query has the data providing terminal 4. This is because the front camera 421 and the rear camera 422 are provided.

No. The target data requirement of the secondary query of 3 also defines the requirement for two attributes. The first attribute is the target data type to be transmitted. The requirement for this is the speed of movement. Only the moving speed is specified, and the sensor type is not specified. Therefore, the speed is not limited to the speed acquired by the vehicle speed sensor, and may be a speed obtained by integrating the acceleration obtained by the acceleration sensor or the wheel speed obtained from the wheel speed sensor. Further, the speed calculated from the signal received by the GPS receiver based on the Doppler effect may be used. The requirement here is the moving speed, not the average moving speed required by the primary query. The reason for this is that the server 3 performs the average processing. No. The data requested in the secondary query of 3 is data that can derive the average moving speed, which is the user-requested data requested in the primary query. As for the second attribute and requirement, the attribute is time and the requirement is time t, as in the primary query.

Further, although the position area is specified in the primary query, there is no requirement regarding the position in this secondary query. The reason for this is that the receiving terminal requirements already take into account the location requirement.

In this embodiment, the terminal requirement correspondence table and the query correspondence table are described separately, but it may be a table in which the query correspondence table and the terminal requirement correspondence table are combined. This is because the query correspondence table and the terminal requirement correspondence table are both tables having a primary query, so that the two tables can be combined.

[Function of control unit 33]
The explanation is returned to FIG. The control unit 33 is a computer equipped with a CPU, ROM, RAM, etc., and the CPU uses the temporary storage function of the RAM as a non-transitory tangible storage medium such as a ROM. By executing the stored program, it functions as a primary query acquisition unit 331, a receiving terminal determination unit 332, a secondary query determination unit 333, and a data processing unit 334.

The above-mentioned program may be stored in a non-transitionary tangible storage medium, and the specific storage medium is not limited to the ROM. For example, the program may be stored in flash memory. Executing the program by the CPU corresponds to executing the method corresponding to the program.

Further, a part or all of the functional blocks included in the control unit 33 may be realized by using one or a plurality of ICs (in other words, as hardware). Further, a part or all of the functional blocks included in the control unit 33 may be realized by the combination of software execution by the CPU and hardware members.

The primary query acquisition unit 331 acquires the primary query transmitted from the remote monitoring device 2 and received by the server reception unit 312 from the server reception unit 312.

The receiving terminal determination unit 332 determines the receiving terminal requirement from the primary query acquired by the primary query acquisition unit 331. This is done using the terminal requirement correspondence table stored in the terminal requirement correspondence table storage unit 323. That is, the primary query acquired by the primary query acquisition unit 331 is determined from the terminal requirement correspondence table, and the receiving terminal requirement corresponding to the determined primary query is determined.

If the acquired primary query is not included in the terminal requirement correspondence table, the requirements required to acquire these processes and target data are sequentially determined from the processes and target data requested by the acquired primary query. And make it a receiving terminal requirement. Further, the receiving terminal requirement may be determined from the contents of the secondary query by referring to the secondary query determined by the secondary query determination unit 333 described below.

Further, the receiving terminal determination unit 332 determines the receiving terminal requirement, and then determines the data providing terminal 4 to receive the secondary query based on the receiving terminal requirement. As described above, the data holding unit 321 also stores information for determining whether or not each data providing terminal 4 meets the receiving terminal requirements. Based on this information stored in the data holding unit 321, the data providing terminal 4 that satisfies the receiving terminal requirement determined from the primary query is determined.

If the receiving terminal requirements include the sufficiency score and the number of data providing terminals 4 that satisfy the receiving terminal requirements excluding the sufficiency score is larger than the required number, the required number is in order from the side with the highest sufficiency score. The data providing terminal 4 of the above is determined to be the data providing terminal 4 that receives the secondary query.

The secondary query determination unit 333 determines a secondary query from the primary query acquired by the primary query acquisition unit 331 and the query correspondence table stored in the query correspondence table storage unit 322.

If the acquired primary query is not included in the query correspondence table, the processing and target data requested by the acquired primary query are expressed by the secondary query that the data providing terminal 4 can handle, and the data is provided. Determine the secondary query to be sent to the terminal 4.

When the target data is transmitted from the data providing terminal 4, the data processing unit 334 executes the target processing determined by the primary query for the target data. If this target process is a process of forwarding to the query request source, the target data received from the data providing terminal 4 is transferred to the user device that has sent the primary query.

Further, the data processing unit 334 stores the target data in the data holding unit 321 in case it is requested by the primary query to be acquired in the future. In the first embodiment, all the target data is stored once in the data holding unit 321 and the storage period is a predetermined fixed period. An embodiment for determining whether or not to store the target data in the data holding unit 321 will also be described later.

[Configuration of data providing terminal 4]
As shown in FIG. 6, the data providing terminal 4 includes a terminal communication unit 41, a sensor unit 42, a storage unit 43, and a control unit 44. The terminal communication unit 41 includes a terminal transmission unit 411 and a terminal reception unit 412. The terminal transmission unit 411 wirelessly transmits data to an external device. The external device is, for example, a server 3. Further, the data may be transmitted to the user device, or the data may be transmitted to another data providing terminal 4. The data to be transmitted includes the target data acquired by executing the secondary query. Further, the position of the own vehicle, that is, the position of the data providing terminal 4, is also transmitted from the terminal transmitting unit 411.

The terminal receiving unit 412 receives data transmitted wirelessly from the outside. The data to be received is, for example, a secondary query transmitted by the server 3.

As the wireless communication means used by the terminal communication unit 41, one or more types of various wireless communication means such as a telephone line network such as LTE and a public wireless LAN can be used. The telephone line network may be either an MNO (Mobile Network Operator) or an MVNO (Mobile Virtual Network Operator). Further, it is preferable that both MVNO and MNO can be used.

The sensor unit 42 includes various sensors. In FIG. 6, the sensor unit 42 includes a front camera 421, a rear camera 422, an acceleration sensor 423, a speed sensor 424, and a position detection sensor 425. These sensors are an example and may not include a part thereof, or may include other sensors not shown in FIG.

The front camera 421 captures an image in front of the vehicle 5. The rear camera 422 captures an image of the rear of the vehicle 5. The acceleration sensor 423 detects the acceleration generated in the vehicle 5. The speed sensor 424 detects the speed of the vehicle 5, that is, the vehicle speed. The position detection sensor 425 detects the current position of the vehicle 5.

The storage unit 43 includes a writable non-transitional substantive storage medium such as a flash memory, and stores the target data acquired by executing the secondary query.

The control unit 44 includes a communication control unit 441 and a data acquisition unit 442. The communication control unit 441 controls the terminal communication unit 41 to transmit and receive data.

When the terminal receiving unit 412 receives the secondary query, the data acquisition unit 442 executes the secondary query and acquires the target data from the sensor unit 42 while the secondary query can be executed. Even if the secondary query is executable when the secondary query is received, if the secondary query contains a location requirement, if the position changes from the time the secondary query is received, then 2 The next query may not be executable. Therefore, as a condition for executing the secondary query, there is a period during which the secondary query can be executed.

Further, when the secondary query is executed in the past and the target data requested by the secondary query is stored in the storage unit 43, the target data is acquired from the storage unit 43.

When the data acquisition unit 442 acquires the target data, the communication control unit 441 transmits the target data from the terminal transmission unit 411 to the device determined by the secondary query. When the terminal communication unit 41 can use a plurality of types of wireless communication means, the wireless transmission means capable of transmitting the data at the lowest cost is used when transmitting the target data. When the target process determined by the secondary query is the accumulation in the storage unit 43, the data acquisition unit 442 stores the acquired target data in the storage unit 43.

[Process executed by the control unit 33 of the server 3]
The processing of the control unit 33 described with reference to FIG. 3 is an outline. Next, the process executed by the control unit 33 will be described in more detail using the flowchart shown in FIG. 7. The control unit 33 periodically executes the process shown in FIG. 7.

Step (hereinafter, the step is omitted) In S1, it is determined whether or not the primary query has been received. S1 is executed by the primary query acquisition unit 331. If the judgment of S1 is NO, the process proceeds to S8 described later. If the judgment of S1 is YES, the process proceeds to S2.

In S2, it is determined whether or not the target data requested by the primary query is stored in the data holding unit 321. S2 is executed by the data processing unit 334.

S3 and S4 are executed by the secondary query determination unit 333. In S3, it is determined whether or not the target data requested by the primary query is scheduled to be received. As illustrated in FIG. 5, the primary query and the secondary query are different. This means that different primary queries can have the same secondary query. Therefore, in this S3, it is determined from the transmission history of the secondary query already transmitted whether or not there is a plan to receive the target data requested by the primary query received this time. If this judgment is YES, the process proceeds to S8, and if NO, the process proceeds to S4. In S4, the secondary query is determined from the primary query received this time.

S5 to S7 are executed by the receiving terminal determination unit 332. In S5, the receiving terminal requirement is determined from the primary query received this time. In S6, the data providing terminal 4 to which the secondary query is transmitted is determined from the receiving terminal requirement determined in S5 and the information of each data providing terminal 4 stored in the data holding unit 321. In S7, a secondary query is transmitted to the data providing terminal 4 determined in S6.

The data processing unit 334 executes S8 to S10. In S8, it is determined whether or not the target data is received from the data providing terminal 4. If this determination is NO, the process shown in FIG. 7 is terminated. If the judgment of S8 is YES, the process proceeds to S9. In S9, the received target data or the already stored target data is transferred to the user device that has transmitted the primary query. Note that the process shown in S9 means that the target process indicated by the primary query is executed, and if this target process is not transferred to the query request source, the target process of the primary query is executed. The process determined by is executed in this S9.

In S10, the received target data is stored in the data holding unit 321. In addition, the target data whose retention period has passed a certain period is deleted from the data holding unit 321.

[Summary of the first embodiment]
Even if the data providing terminal 4 acquires the request that the target position is the intersection x, it often cannot understand the request that the target position is the intersection x. It is also difficult for the remote monitoring device 2 to create a data acquisition request for each data providing terminal 4 in an expression that each data providing terminal 4 can understand.

Further, when the remote monitoring device 2 tries to acquire the average speed in the vicinity of the intersection x, the data providing terminal 4 existing in the vicinity of the intersection x is specified, and the moving speed is transmitted to the specified data providing terminal 4. It is also difficult to average the moving speeds obtained from each data providing terminal 4.

However, in the present embodiment, when the remote monitoring device 2 sends a primary query to the server 3, the server 3 requests the primary query with an attribute that the data providing terminal 4 can specify the data from the primary query. Determine the secondary query that specified the target data to be executed. Since this secondary query is transmitted to the data providing terminal 4, the user who uses the remote monitoring device 2 does not need to represent the required data with an attribute that can be specified by the data providing terminal 4, but the data providing terminal 4 Can specify the data to be provided. Therefore, the remote monitoring device 2 can easily acquire necessary data.

<Second Embodiment>
Next, the second embodiment will be described. The hardware configuration of the data acquisition system of the second embodiment is the same as that of the first embodiment. In the second embodiment, the primary query, the secondary query, and the receiving terminal requirements different from those in the first embodiment will be described.

In the first embodiment, the remote monitoring device 2 is No. 1 or No. When the primary query of 2 is transmitted to the server 3, the image data in which the intersection x is captured is transferred in real time. As a result, the remote monitoring device 2 can temporarily monitor the intersection x in real time.

However, if the frame rate of the data providing terminal 4 is slow, or if the time required for the image transfer processing is long, real-time monitoring will be hindered. Similarly, when the communication speed of the wireless line is slow, real-time monitoring is hindered.

It is often difficult for the user who operates the remote monitoring device 2 to specify these parameters that affect real-time monitoring, such as the frame rate, the image transfer time, and the communication speed of the wireless line, in the primary query.

In addition to real-time monitoring, a primary query that needs to set requirements for attributes related to time can be considered, instead of a primary query that processing for target data should be executed regardless of time.

In the second embodiment, an example in which the execution requirement is included in the primary query will be described. The performance requirement is the processing of the target data, that is, the requirement of the attribute regarding the time for the target processing. FIG. 8 shows a query correspondence table in the second embodiment. The secondary query shown in FIG. 8 omits the target process and the target data requirement. No. In the primary query of 4, the target processing and the target data requirements are the No. 1 described in the first embodiment. Same as 1 query. Therefore, the target processing and target data requirements of the secondary query omitted in FIG. 8 are No. It is the same as the secondary query of 1.

The primary query shown in FIG. 8 includes the performance requirements described above. No. As the execution requirement in the primary query of 4, the requirement for two attributes is defined. The first attribute is use, and the requirement for that attribute is real-time monitoring. Real-time monitoring has the same meaning as real-time monitoring.

The processing requirement of the secondary query shown in FIG. 8 is an attribute requirement determined in accordance with the execution requirement of the primary query. No. As for the processing requirements of the secondary query of 4, the requirements for the three attributes are defined. The first requirement is the wireless line speed, and the requirement for this is that it is faster than 5 Mbps. The second attribute is the frame rate, and the requirement for this is faster than 10 fps, that is, the requirement to capture more than 10 frames per second. This requirement determines the frequency of data acquisition. The third attribute is the transfer delay, which is required to be shorter than 1 second. The transfer delay means the time required for internal processing from the acquisition of image data to the transmission of the image data. If these three requirements are met, the image data will be sent to the destination without much delay. Therefore, real-time monitoring, which is a requirement for executing the primary query, becomes possible.

In addition, No. The processing requirement of 4 includes the sufficiency cost. The sufficiency cost represents the burden required to meet the processing requirements. The burden here is specifically the communication cost, that is, the charge, and the sufficiency cost is the product of the toll line usage time and the bit unit price of the toll line. The toll line usage time is determined from the distance and travel speed at which the toll line is used. Whether or not each position uses a toll line is determined from the communication resource map. The communication resource map is a map showing whether or not a free line can be used at each location. This communication resource map is acquired from a terminal managed by a provider that provides the map.

No. In the primary query of 5, the target process is conservation. The preservation is a process of temporarily storing the target data in the storage medium of the data providing terminal 4 because the target data may be required later.

No. The target data requirement in 5 defines the requirements for the two attributes. The first is a requirement for an attribute called data type, and a requirement for audio data in MP3 format. The second is a requirement for the attribute of the target position and a requirement for the intersection x.

In addition, No. As for the performance requirements in 5, the requirements for the two attributes are defined. The first is a requirement for the attribute of retention period and a requirement for period T. The retention period means the period during which the target data is retained, that is, recorded. The second is a requirement for the attribute of data rate, which is faster than w (kbps). This No. The performance requirement of No. 5 also defines a requirement for a time-related attribute called a retention period.

No. The processing requirement of the secondary query corresponding to the execution requirement of 5 is that the attribute of free storage capacity is larger than that of wT. This is because the execution requirement in the primary query is that the retention period is T and the data rate is faster than w, so that at least the data capacity of wT, which is the product of these, is recorded.

[Processing example of control unit 33]
Next, No. Taking the case where the remote monitoring device 2 transmits the primary query of 4 to the server 3 as an example, the processing of the control unit 33 of the server 3 in the second embodiment will be described with reference to the flowchart shown in FIG.

No. When the remote monitoring device 2 sends the primary query of 4 to the server 3 and the server 3 receives the primary query, S1 becomes YES and the process proceeds to S2. Here, it is assumed that the target data is not saved and there is no schedule for receiving the target data. Therefore, the judgments of S2 and S3 are both NO, and the process proceeds to S4. In S4, No. 2 shown in FIG. The secondary query of 4 will be determined.

In the following S5, the receiving terminal requirement is determined. The receiving terminal requirements determined here are No. 4 shown in FIG. 1 or No. It has 2 receiving terminal requirements. In addition to this, the requirement that the upstream communication speed is faster than 5 Mbps may be added. If this requirement is added, the possibility of sending the secondary query to the data providing terminal 4 that does not satisfy the processing requirement of the secondary query is reduced.

In S6, the data providing terminal 4 satisfying the receiving terminal requirement determined in S5 is determined as the secondary query transmission destination. In order to enable the processing of S6, in the second embodiment, the communication speed that can be executed by the terminal transmission unit 411, the frame rate that the front camera 421 and the rear camera 422 can capture, and the transfer delay time are probe information. It is included in the data holding unit 321 and stored in the data holding unit 321.

If the number of data providing terminals 4 satisfying the receiving terminal requirements is larger than the required number and the satisfying cost is included in the processing requirements of the secondary query, the data providing terminals 4 satisfying the receiving terminal requirements. Among them, the required number of data providing terminals 4 are determined to be the data providing terminals 4 that receive the secondary query in order from the data providing terminal 4 having the lowest sufficiency cost. As described in the first embodiment, the required number is preset for each primary query based on the data type included in the primary query and the like.

In S7, a secondary query is transmitted to the data providing terminal 4 determined in S6. Since S8 to S10 are the same as those in the first embodiment, the description thereof will be omitted.

When the execution requirement is included in the primary query as in the second embodiment, if the secondary query includes the processing requirement determined in accordance with the execution requirement, the user apparatus can use the necessary data. Will be easier to obtain.

<Third Embodiment>
In the third embodiment, the primary query, the secondary query, and the receiving terminal requirements different from those of the first embodiment and the second embodiment will be described. In the third embodiment, the user device is a road abnormality detection device. The road anomaly detection device periodically requires images of the road in order to sequentially confirm whether or not any abnormal condition has occurred on the road.

Hereinafter, an example will be described in which this road abnormality detection device requests image data of an x intersection for 10 seconds from 9:00 to confirm the road condition. 9 and 10 show a primary query transmitted by the road abnormality detection device to the server 3. In the primary query shown in FIGS. 9 and 10, the target process is a process of forwarding to the query request source as in the first embodiment.

The target data requirements are defined for the three attributes. The first attribute and requirement are the second attributes and requirements shown in FIGS. 4 and 5. It is the same as the primary query of 1. In addition, the target data requirements of the primary query shown in FIGS. 9 and 10 have a third attribute and requirement. The third attribute is time, and the requirement for this is 10 seconds from 9:00.

In addition, this primary query includes performance requirements. As for the performance requirement, the attribute is the purpose, and the requirement for this is the road condition confirmation.

FIG. 9 shows the receiving terminal requirement determined by the receiving terminal determining unit 332 for this primary query. FIG. 9 shows two types of receiving terminal requirements corresponding to one primary query. In the upper receiving terminal requirement, the terminal type C is the terminal type C1, and in the lower receiving terminal requirement, the terminal type C is the terminal type C2. The terminal type C1 and the terminal type C2 have the same meaning as in FIG. 4, the terminal type C1 means the data providing terminal 4 provided with the front camera 421, and the terminal type C2 includes the front camera 421 and the rear camera 422. It means a data providing terminal 4.

Further, the receiving terminal requirements shown in FIG. 9 are defined for three attributes. The first attribute is the position of the own vehicle, and the requirement for this is that it is within 100 m from the coordinates (a, b) of the intersection x at 9:00.

The second requirement is defined only for the upper receiving terminal requirement, and is a requirement that the coordinates (a, b) are approached at 9:00 with respect to the attribute of the traveling direction. This requirement is different only in whether the judgment time is the present or 9:00, and the No. 1 shown in FIG. 4 is different. It is the same as the second requirement in the receiving terminal requirement of 1. The reason why the receiving terminal requirement in the lower part of FIG. 9 does not have a requirement for the traveling direction is No. 4 in FIG. The reason why there is no requirement for the second attribute in 2 is that the data providing terminal 4 includes the rear camera 422 in addition to the front camera 421.

The third requirement is the same requirement for the upper receiving terminal requirement and the lower receiving terminal requirement. The third requirement is the communication speed, and the requirement for this is that the current communication speed is faster than 5 Mbps, or the current location is within 1 km from the communication area of the wireless LAN. Since the data type requested by the primary query is image data, the communication speed needs to be high to some extent. Therefore, there is a requirement that it be faster than 5 Mbps. In addition to this requirement, the reason why the requirement that it is within 1 km from the communication area of the wireless LAN is set is that unlike the first embodiment, the data requested by the primary query is the data that is immediately required. do not have. Therefore, the data may be transmitted a little later. In addition, the wireless LAN has a communication speed that does not hinder the transmission of image data, and in many cases, the communication cost is free. Therefore, the requirement of being within 1 km from the wireless LAN area has been added. Whether or not it is within 1 km from the wireless LAN area is determined based on the wireless LAN communication area map.

FIG. 10 shows a secondary query determined by the secondary query determination unit 333 with respect to the primary query. The primary query shown in FIG. 10 is the same as in FIG. There are two secondary queries shown in FIG. 10, each of which is a secondary query corresponding to the two receiving terminal requirements shown in FIG.

In the two secondary queries shown in FIG. 10, the target processing is both sent to the server. The target data requirements are defined for three attributes. The first attribute and requirement are No. 5 shown in FIG. 1, No. Same as the first attribute and requirement of the second secondary query. The second attribute is also No. 2 shown in FIG. 1, No. It is the same as the second attribute of the secondary query of 2. The requirement for the second attribute is No. 5 shown in FIG. 5, except that the time is 9:00. 1, No. It is the same as the second requirement of the secondary query of 2. The third attribute and requirement are the same as the third attribute and requirement of the same primary query in FIG.

Processing requirements are also defined in the secondary query shown in FIG. As for the processing requirement, the requirement of 5 minutes or less is defined for the attribute of transfer delay. This processing requirement is a requirement determined from the performance requirement shown in the primary query. Since the performance requirement is road condition confirmation, it is not necessary to send the image data immediately. Therefore, as a processing requirement, a requirement that the transfer delay is within 5 minutes is stipulated.

[Processing example in the third embodiment]
Next, a processing example in the third embodiment will be described. It is assumed that the road abnormality detection device, which is a user device, sends the primary query shown in FIGS. 9 and 10 to the server 3. When the server 3 receives this primary query, S1 in FIG. 7 becomes YES and the process proceeds to S2. If the target data has not been saved and there is no schedule for receiving the target data, the process proceeds to S4. In S4, the secondary query shown in FIG. 10 is determined. In S5, the receiving terminal requirement shown in FIG. 9 is determined.

In S6, the data providing terminal 4 satisfying the receiving terminal requirement determined in S5 is determined as the destination of the secondary query. If the number of data providing terminals 4 satisfying the receiving terminal requirements shown in FIG. 9 is larger than the required number, the wireless LAN area of the data providing terminals 4 satisfying the receiving terminal requirements is further reached within 5 minutes. The required number of data providing terminals 4 may be determined as the secondary query transmission destination in order from the data providing terminal 4 having the highest possibility. For this purpose, it is preferable to sequentially acquire the movement plan from the data providing terminal 4 and store it as probe information. Further, the future movement route of the data providing terminal 4 may be estimated from the movement history included in the probe information, and the possibility of reaching the wireless LAN area within 5 minutes may be estimated.

In S7, the secondary query is transmitted to the secondary query destination determined in S6. Since the data providing terminal 4 that has received the secondary query has a processing requirement of 5 minutes or less, it searches for the communication means having the lowest communication cost among the communication means that can complete the transfer within 5 minutes.

For example, if it can be estimated that the data will enter the wireless LAN communication area after 3 minutes and the storage capacity is sufficient, even if the target data is stored, it will enter the wireless LAN area without being transmitted immediately. After that, it is decided to send the target data. However, even when the target data is transmitted later in this way, executing the transmitted secondary query is transmitted to the server 3 first.

Further, it is not always possible for the data providing terminal 4 that satisfies the receiving terminal requirements to execute the secondary query. If the data providing terminal 4 receives the secondary query but cannot execute the secondary query, it responds to the server 3 to that effect.

When the data providing terminal 4 transmits the target data and the server 3 receives the target data, the determination in S8 becomes YES, and the target data is transferred to the road abnormality detection device in S9. As a result, the road abnormality detection device can acquire the image data of the intersection x, so that the road state of the intersection x can be confirmed from the image. Further, the server 3 executes S10 to temporarily store the image data transmitted from the data providing terminal 4 in the data holding unit 321.

As shown in the third embodiment, the user apparatus can easily acquire the necessary data even if the necessary data is past data.

<Fourth Embodiment>
In the previous embodiments, the server 3 has been supposed to be able to determine a secondary query from a primary query. However, as a matter of course, it is not possible to determine a secondary query for any primary query, and it may not be possible to determine a secondary query from a primary query.

In the fourth embodiment, the server 103 shown in FIG. 11 includes a public unit 134 that publishes a list of primary queries that can determine a secondary query. The public unit 134 is a recording medium that can be accessed from the outside via a communication line such as the Internet. Therefore, the user device can access the public unit 134 to know the primary query that the server 103 can handle.

The control unit 133 of the server 103 includes an update unit 1335. The update unit 1335 is a function for updating the corresponding primary query published to the public unit 134. The update process of the update unit 1335 will be described with a specific example.

For example, initially, the target data is (1) the position where the vehicle is specified and (2) the image where the position is specified, and for these, (A) transfer and (B) maintenance are possible as target processing. Suppose that something is open to the public.

In addition, the target data includes (3) average moving speed with specified position, (4) average wiper operating state with specified position, (5) position with specified time and wiper movable state, and (6) vehicle and time. It is assumed that the designated positions are used, and that (A) transfer is possible as a target process for these positions.

The update unit 1335 sets the target data as (7) an image in which the vehicle and the time are specified, and (8) an image in which the position and the time are specified as the corresponding primary query, and (A) as the target process for these. Add that transfer is possible.

By providing the update unit 1335, the user apparatus can increase the number of primary queries that can determine the secondary query published in the public unit 134, so that the user can easily request the primary query. Further, it is possible to suppress the transmission of the primary query to which the server 3 cannot determine the secondary query to the server 3.

Further, in the fourth embodiment, the function of the secondary query determination unit 1333 of the control unit 133 is different from that of the secondary query determination unit 333 of the previous embodiments. The secondary query determination unit 1333 of the present embodiment determines a stationary query as a secondary query in addition to the functions provided by the secondary query determination unit 333 of the previous embodiments. The stationary query is a data acquisition request for the data requested to the data providing terminal 4 regardless of the primary query. This steady-state query is transmitted from the server transmission unit 311 to the data providing terminal 4 capable of executing the steady-state query. The transmission timing may be periodic or may be once for each data providing terminal 4. Further, a query instructing the stop of the transmitted stationary query is transmitted to the data providing terminal 4 that has transmitted the steady query.

The stationary query is a query corresponding to the primary query published in the public unit 134. In other words, a part of the primary query published to the public unit 134 is a primary query that can be dealt with by the data that can be acquired by the stationary query. When a new stationary query is transmitted, the update unit 1335 adds a new primary query that can be dealt with by the stationary query to the public unit 134.

If the target process of the primary query is maintenance, the routine query is also the target process of maintenance. Further, if the target process of the primary query is transfer, the regular query also targets transfer. In the case of transfer, the frequency of data transmission is also specified by a regular query. If the handling process of the steady query is transfer to the server 3 and the transmission frequency is specified, the target data is transmitted to the server 3 from the data providing terminal 4 at any time. If this target data is data necessary for determining the receiving terminal requirement such as the current position, the server 3 provides each data in order to search for the data providing terminal 4 that satisfies the receiving terminal requirement after receiving the primary query. There is no need to acquire data from the terminal 4. Therefore, it is possible to quickly determine the data providing terminal 4 that satisfies the receiving terminal requirements.

The current position is one of the probe information. Therefore, the data providing terminal 4 is requested to obtain the probe information that needs to be updated by the steady query.

The target data transmitted to the server 103 by executing the steady query is temporarily held in the data holding unit 321. This is because the user device for transferring this target data has not been decided yet.

By transmitting the stationary query to the data providing terminal 4, the server 103 can quickly provide the target data requested by the primary query to the user apparatus when the primary query is acquired from the user apparatus. ..

For example, to show an example of a steady query, the target process is conservation, and the target data is an image with a frame rate of 10 fps captured by the front camera 421. Since maintenance means accumulating data, the data providing terminal 4 that has received this stationary query accumulates the target data specified by the stationary query in the accumulating unit 43.

The data providing terminal 4 to which the stationary query is transmitted is, for example, a data providing terminal 4 capable of executing the stationary query at the time of transmission. Further, a steady query may be transmitted to the data providing terminal 4 which may be able to execute the secondary query due to a change in position or the like.

Further, since the data providing terminal 4 may decide whether or not to finally execute the stationary query, the stationary query may be transmitted to all the registered data providing terminals 4. In this case, when a new data providing terminal 4 is additionally registered, a steady query is transmitted to the newly registered data providing terminal 4 each time it is registered. As a result, the target data defined by the steady query can be acquired from the newly registered data providing terminal 4. The newly registered data providing terminal 4 transmits a message requesting registration to the server 103. As a result, the server 103 can register the data providing terminal 4.

<Fifth Embodiment>
In the first embodiment, the server 3 stores all the target data transmitted from the data providing terminal 4 for a predetermined period of time. On the other hand, as shown in FIG. 12, the control unit 233 included in the server 203 of the fifth embodiment includes a holding determination unit 2334 that determines whether or not to store the target data in the data holding unit 321.

When a large amount of data is transmitted per unit time, such as when image data is constantly transmitted from a large number of data providing terminals 4 to the server 203, there is a risk that the free space of the data holding unit 321 will be exhausted. be. Therefore, the retention determination unit 2334 determines whether or not to store the target data in the data retention unit 321.

The retention determination unit 2334 determines the target data to be stored in the data retention unit 321 based on the transmission history of transmitting the target data to the user apparatus. The more times the target data is transmitted to the user device, the more valuable the data is to be retained. Therefore, the target data to be stored is determined based on the transmission history of the target data transmitted to the user device.

In order to determine the target data to be stored in the data holding unit 321, the discard priority is determined for the target data. As for the discard priority, for example, the target data that has not been transmitted to the user device for a certain period of time increases the discard priority by a certain value. Then, the target data is discarded in order from the target data having the highest discard priority until the free capacity of the data holding unit 321 becomes larger than the specified free capacity. The holding determination unit 2334 periodically executes this process.

By providing the retention determination unit 2334, useful target data can be preferentially stored in the data retention unit 321. When the target data requested by the primary query is stored in the data holding unit 321, the target data stored in the data holding unit 321 may be transmitted to the user apparatus.

Considering the remote monitoring device 2 and the road abnormality detection device, which are specific examples of the user device, it is considered that the user device and the server 203 are connected by wired communication and can often communicate at low cost. On the other hand, the communication between the server 203 and the data providing terminal 4 is wireless communication, which is higher in cost than the communication between the server 203 and the user device. Therefore, as in the present embodiment, the data acquisition cost of the entire system can be suppressed by allowing the data holding unit 321 to preferentially store useful target data.

<Sixth Embodiment>
In the embodiments described so far, the destination of the target data defined in the secondary query is the server 3. However, in the secondary query, a terminal different from the server 3 can be specified as the transmission destination of the target data.

In the sixth embodiment, the target data acquired by the data providing terminal 4 is transmitted to another data providing terminal 4 by vehicle-to-vehicle communication. In this case, the data providing terminal 4 that receives the target data is a user device. The data providing terminal 4, which is a user device, sends a primary query to the server 3.

This primary query will be described below assuming that it is the next query. That is, in the primary query received by the server 3, the target process is forwarded to the query request source, the target data is the current image and sound near the position y, and the usage of the execution requirement is to check the road condition. The server 3 that has received this primary query sets S1 to YES in the process shown in FIG. 7, and proceeds to S2.

If the target data has not been saved and there is no scheduled reception, the process proceeds to S4. In S4, the secondary query is determined. The secondary query determined here is a process in which the target process sends to the data providing terminal 4 which is the query request source, the target data is an image of a camera whose position y is within the visibility, and the processing requirement is. The communication speed is 1 Mbps or more, and the communication delay is 10 seconds or less. In addition, in order to execute the process of transmitting to the data providing terminal 4, the secondary query also includes the destination of the data providing terminal of the transmission destination. The server 3 has received this destination as probe information in advance.

In S5, the receiving terminal requirement is determined. The receiving terminal requirement is, for example, that the current position is within 100 m from the position y, vehicle-to-vehicle communication is possible, and the image and sound associated with the position can be acquired. The vehicle-to-vehicle communication includes direct vehicle-to-vehicle communication and indirect vehicle-to-vehicle communication. Indirect vehicle-to-vehicle communication is vehicle-to-vehicle communication via a base station, and direct vehicle-to-vehicle communication is vehicle-to-vehicle communication that does not go through a base station.

In S6, the destination of the secondary query is determined. When there are more data providing terminals 4 satisfying the receiving terminal requirements than the required number, only the data providing terminals 4 capable of direct vehicle-to-vehicle-to-vehicle communication may be the destination of the secondary query. In order to perform this processing, it is also possible to use a sufficiency score having a different score depending on whether or not direct vehicle-to-vehicle communication is possible.

In S7, the secondary query is transmitted to the destination determined in S6. Since the vehicle-to-vehicle communication is requested by the secondary query, in the sixth embodiment, it will not be executed after S8.

<7th Embodiment>
In the previous embodiments, the time specified by the primary query is only the time when the data is acquired. However, the primary query may include a terminal time requirement, which is a requirement for the time when the data providing terminal 4 acquires the data. In this embodiment, it is assumed that the data providing terminal 4 is not mounted on the vehicle 5 but is installed indoors.

An example of a primary query that includes terminal time requirements is shown below. The target process is transmission to the query request source. The target data requirement includes the requirement that the data type is location and current indoor image. In addition, the target data requirements further define the terminal state, which is an attribute, and the requirement for the validity period of the terminal state.

The requirement for the terminal state is that the maximum acceleration is greater than 500 gal. The validity period of the terminal state is a requirement that the time when the requirement for the maximum acceleration is satisfied is between 9:00 and 9:05. 9: 00-9: 05 is the terminal time requirement.

This primary query is a query for acquiring the position where a large vibration is generated by the earthquake and the current image of the position for the earthquake that shook greatly between 9:00 and 9:05. This primary query is sent, for example, from a device operated by a user who conducts a disaster damage investigation.

When the server 3 receives this primary query, S1 in FIG. 7 becomes YES. It is assumed that the target data is not saved and there is no schedule for receiving the target data. Therefore, the judgments of S2 and S3 are both NO, and the process proceeds to S4. In S4, the secondary query is determined. An example of the secondary query determined here is shown below. In the secondary query, the target process is sent to the server, and the target data is an indoor image. In addition, the requirement of the target data includes the requirement that the time is the latest time. Further, it is assumed that the processing requirement includes a requirement that the transfer delay is 5 minutes or less.

In S5, the receiving terminal requirement is determined. An example of the receiving terminal requirement determined here is shown below. The receiving terminal requirement is that the terminal type C is a terminal capable of acquiring an indoor image, and the maximum acceleration detected in the terminal state from 9:00 to 9:05 is larger than 500 gal. In order to determine these requirements, in the present embodiment, it is assumed that the probe information including the acceleration is transmitted to the server 3 in a cycle shorter than 5 minutes. Further, the requirement that the latest probe information received from the data providing terminal 4 is within 1 minute from the present time is also included in the receiving terminal requirement. This requirement is a requirement for confirming that the data providing terminal 4 is not damaged.

In S6, the data providing terminal 4 satisfying the above-mentioned receiving terminal requirement is determined as the destination of the secondary query, and in S7, the secondary query is transmitted.

The data providing terminal 4 that has received the secondary query captures a still image at the present time and transmits the image to the server 3. As a result, S8 in FIG. 7 becomes YES, so that the server 3 transfers the still image to the user device.

According to this seventh embodiment, the user apparatus can easily acquire the position where the earthquake has shaken and the current image of the position after the earthquake. Of course, the phenomena that occurred at the past time are not limited to earthquakes. As another example, if the data providing terminal 4 is provided with a rainfall sensor and a humidity sensor, the indoor humidity after the guerrilla rainstorm has passed can be easily acquired.

<8th Embodiment>
In the seventh embodiment described above, it has been described that the terminal time requirement can be included in the primary query. The terminal time requirement in the seventh embodiment specifies a past time. However, future times may be specified in the terminal time requirements.

In this eighth embodiment, the primary query includes a terminal time requirement that specifies a future time. An example of this primary query is shown below. The following primary query is a primary query sent to the server 3 by a device that provides merging support when a vehicle that is scheduled to join another road at point m requests merging support from a device that supports merging. Is an example of. In this example, the device that supports merging is the user device. Further, in this embodiment, the data providing terminal 4 is mounted on the vehicle 5.

The primary query sent by the device that supports merging is a query that frequently sends data satisfying the following requirements to the own vehicle during time t1-time t3. That is, in this embodiment, the time for sending the query is also specified.

The requirement of this primary query is that the target is the terminal position, the terminal state is traveling in lane A to which the junction of the roads near the point m is connected, and the valid period of the terminal state is time t2-time. It is a requirement of t3. Time t2-time t3 is a future time, and in this embodiment, this time t2-time t3 is a terminal time requirement. Further, the point m is a requirement for a position that exists at a future time determined by the terminal time requirement.

Note that this primary query is different from the primary query described in the previous embodiments, and does not clearly indicate what the target processing and the target data requirements are. However, the server 3 can analyze this primary query to extract target processing, target data requirements, and the like.

When the server 3 receives this primary query, the determination in S1 in FIG. 7 becomes YES and the process proceeds to S2. Since the target data requested by the primary query is the data at a future point in time, the judgment of S2 becomes NO and the process proceeds to S3. Assuming that the judgment of S3 is also NO, the secondary query is determined in S4.

An example of the secondary query determined here is shown below. In the secondary query, the target process is sent to the server, and the target data is the current position at time t2-time t3. Further, it is assumed that the processing requirements include a requirement that the transfer cycle is 5 seconds or less and a requirement that the transfer delay is 1 second or less. This processing requirement is a requirement determined by the server 3 by determining that the high frequency of the primary query is an execution requirement.

In S5, the receiving terminal requirement is determined. An example of the receiving terminal requirement determined here is shown below. The receiving terminal requirement is that the terminal type C is a data providing terminal 4 that can transmit the current position in a cycle of 5 seconds or less and can detect a position that is distinguished up to the lane.

The reason why the terminal is capable of transmitting the current position in a cycle of 5 seconds or less is that the primary query requires that the vehicle position be transmitted frequently. The reason why the terminal can detect the position that distinguishes up to the lane is that it is required that the terminal is traveling in the lane A by the primary query. The receiving terminal requirement further requires that the vehicle is scheduled to pass the point m in lane A between time t2-time t3.

In S6, the data providing terminal 4 satisfying the receiving terminal requirement is searched based on the probe information stored in the data holding unit 321. When the movement plan is sequentially transmitted from the data providing terminal 4 in order to determine whether or not the requirement that the point m of the lane A is to be passed between the time t2-time t3 is satisfied among the receiving terminal requirements. Predicts the position where the data providing terminal 4 exists at time t2-time 3 based on the movement plan.

The movement plan is, for example, a guide route during route guidance and a scheduled time to pass each point on the route. Further, if the vehicle is in automatic driving, it is a movement route planned by the automatic driving system and a scheduled time to pass each point on the route.

For the data providing terminal 4 for which the movement plan has not been acquired, the data providing terminal is set at time t2-time 3 from the movement locus of the past constant distance sentence from the latest time point and the road shape in front of the traveling direction of the data providing terminal 4. Predict the position where 4 exists.

After determining the data providing terminal 4 that satisfies the receiving terminal requirement as the destination of the secondary query, S7 is executed to transmit the secondary query. However, since the primary query specifies that the time to send the query is between time t1 and time t3, if it is not time t1, it waits and then 2 after time t1. Send the next query.

Then proceed to S8. However, in this eighth embodiment, S6 and S7 are continued together with the determination in S8 until the time t3. This is because there is a possibility that there is a data providing terminal 4 that satisfies the receiving terminal requirement due to a change in the situation from the time when S6 is first executed. For example, a vehicle that has been traveling in the lane next to the lane A may be traveling in the lane A due to a lane change.

The data providing terminal 4 that received the secondary query before the time t2 executes the secondary query from the time t2 to the time t3 and transmits the current position to the server 3. On the other hand, the data providing terminal 4 that has received the secondary query after the time t2 executes the secondary query from the time when the secondary query is received until the time t3, and transmits the current position to the server 3.

According to this eighth embodiment, the user apparatus can easily acquire the target data at a future time.

<9th embodiment>
FIG. 13 shows the configuration of the server 903 of the ninth embodiment. In the third embodiment described above, it has been described that when the data providing terminal 4 cannot execute the secondary query, when the secondary query is received, the data providing terminal 4 responds to the server 3 to that effect. The server 3 that has acquired this answer can determine whether or not the target data can be provided to the user device based on this answer.

In the ninth embodiment, when the target data cannot be provided to the user apparatus or it is predicted that the target data cannot be provided, the server 903 has a function of notifying the user apparatus to that effect. This function will be described in detail below.

Similar to the third embodiment, in the ninth embodiment, the primary query includes the execution requirement. The query satisfaction determination unit 9334 determines the primary query satisfaction information. The primary query satisfaction information is information indicating the possibility that the user request data can be provided to the user apparatus according to the execution requirements included in the primary query.

[Specific content of primary query satisfaction information]
The specific content of the primary query satisfaction information is, for example, information indicating whether or not all the execution requirements included in the primary query can be satisfied. Further, information indicating unsatisfied performance requirements, that is, information indicating which performance requirements cannot be satisfied may be used, such as a list. If the information indicates an unsatisfied performance requirement, it can be determined whether or not all the performance requirements can be satisfied depending on the presence or absence of the unsatisfied performance requirement. Therefore, the information indicating whether or not all the performance requirements can be satisfied may be omitted. Further, both the information indicating whether or not all the performance requirements can be satisfied and the information indicating the performance requirements that cannot be satisfied may be included in the primary query satisfaction information.

Further, if the future position of the data providing terminal 4 can be predicted when determining the primary query satisfaction information, the content of the primary query satisfaction information is included in the primary query until a certain time t10. Although the user request data can be provided to the user apparatus according to the requirements, it may indicate that the user request data cannot be provided according to the execution requirements after the time t10.

[Timing of determining primary query satisfaction information]
The query satisfaction determination unit 9334 determines the primary query satisfaction information when the primary query acquisition unit 331 acquires the primary query. Further, after that, the primary query satisfaction information is sequentially determined. The time point for determining the primary query satisfaction information can be, for example, at regular intervals. Further, instead of or in addition to them, the primary query satisfaction information can be determined when a notification indicating that the secondary query cannot be executed is received from the data providing terminal 4.

[Method of determining primary query satisfaction information]
When the primary query acquisition unit 331 acquires the primary query, the primary query satisfaction information is determined from the information stored in the data holding unit 321. The information stored in the data holding unit 321 used for determining the primary query satisfaction information is information for determining whether or not the receiving terminal requirement is satisfied. The information for determining whether or not the receiving terminal requirement is met is, for example, the position of the data providing terminal 4, the type of the sensor provided in the data providing terminal 4, and the type of the communication line that can be used by the data providing terminal 4. , Communication speed, etc.

When the primary query acquisition unit 331 determines the primary query satisfaction information at a time after the primary query is acquired, it is stored in the data holding unit 321 as in the case when the primary query is acquired. The primary query satisfaction information can be determined from the information.

Further, when the requirement of the primary query includes the requirement of the position or section for acquiring the target data, and the movement plan of the data providing terminal 4 is sequentially acquired and stored as probe information, the following It is also possible to determine the primary query satisfaction information in this way.

First, the position of the data providing terminal 4 can be sequentially updated based on the latest probe information, and it can be determined whether the position of the data providing terminal 4 satisfies the requirements of the primary query. Further, since the movement plans are sequentially acquired from the data providing terminal 4, the latest movement plan acquired from a certain data providing terminal 4 is changed from the previously acquired movement plan from the same data providing terminal 4. There is also. In the pre-change travel plan, it can be determined that the requirements for the position or section included in the primary query are satisfied, but in the latest travel plan, it may be determined that the requirements cannot be satisfied in the future. In this case, the number of data providing terminals 4 satisfying the requirements of the primary query is reduced from the position where the position of the data providing terminal 4 does not satisfy the requirements of the primary query. If the number of data providing terminals 4 satisfying the requirements of the primary query decreases and the number of data providing terminals 4 satisfying the requirements of the primary query becomes less than the required number, the primary query satisfying information is the primary query satisfaction information. Information that indicates that the performance requirements contained in the query cannot be met.

Further, the primary query satisfaction information can be determined based on the information transmitted from the data providing terminal 4. Hereinafter, it will be described in detail. Similar to the third embodiment, in the ninth embodiment, when the data providing terminal 4 receives the secondary query, if the secondary query cannot be executed, the data providing terminal 4 responds to the server 903 to that effect. .. In addition, in the ninth embodiment, the server 903 determines whether or not the data providing terminal 4 continues to be able to execute the secondary query, in other words, whether or not the secondary query cannot be executed. Send to. Also, if it is determined that the secondary query cannot be executed in the future, that fact is transmitted to the server 903.

A specific explanation will be given to determine whether or not the situation in which the secondary query can be executed continues. For example, suppose that the requirements for a secondary query include a requirement for communication speed. The communication speed fluctuates due to changes in the communication environment such as location. Therefore, even if the secondary query can be executed when the secondary query is received, the data providing terminal 4 may not be able to execute the secondary query if the communication environment deteriorates thereafter. .. In addition, it is provided with a communication speed map, and it may be determined that the communication speed will not meet the processing requirements of the secondary query in the near future.

These are an example in which the data providing terminal 4 cannot execute the secondary query, and an example in which it is determined that the secondary query cannot be executed in the future. The data providing terminal 4 notifies the server 903 when it becomes impossible to execute the secondary query and when it is determined that the secondary query cannot be executed in the future. It is preferable that the notification includes a cause (for example, a decrease in communication speed) that the secondary query cannot be executed.

The query satisfaction determination unit 9334 is notified from the data providing terminal 4 that the secondary query cannot be executed, or when it is notified that the secondary query cannot be executed in the future. Reduce the number of data providing terminals 4 that satisfy the primary query. Further, as a result of reducing the number of data providing terminals 4 satisfying the primary query, when the number of data providing terminals 4 satisfying the primary query becomes less than the required number, the primary query satisfying information is displayed. Update. If the content of the primary query satisfaction information is the number of data providing terminals 4 that satisfy the primary query, whether the number of data providing terminals 4 satisfying the primary query is less than the required number. Regardless, the primary query satisfaction information is updated.

If the notification from the data providing terminal 4 includes a cause that the secondary query cannot be executed, determine which requirement cannot be satisfied in the primary query from the cause and the query correspondence table. You can also. Then, the primary query satisfaction information can include information indicating which performance requirement cannot be satisfied.

[When sending primary query satisfaction information]
The query satisfaction determination unit 9334 transmits the primary query satisfaction information from the server transmission unit 311 to the user device. The query satisfaction determination unit 9334 determines the target data according to the execution requirement from at least the content of the primary query satisfaction information indicating that the target data (that is, the user request data) can be provided to the user device according to the execution requirement of the primary query. When it becomes an indication that it cannot be provided to the user device, the primary query satisfaction information is transmitted.

At this time, in order to be able to transmit the primary query satisfaction information, the query satisfaction determination unit 9334 determines the primary query satisfaction information sequentially after the secondary query determination unit 333 determines the secondary query.

Further, when the primary query is acquired from the user device, the primary query satisfaction information may be determined and the determined primary query satisfaction information may be transmitted to the user device. Further, after the secondary query determination unit 333 determines the secondary query, the primary query satisfaction information may be periodically transmitted to the user apparatus.

[User device support]
When the user device is notified of the primary query satisfaction information, measures such as stopping the standby state on the premise that the target data is provided or issuing a new primary query with relaxed requirements are taken. Can be done early.

Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and the following modifications are also included in the technical scope of the present invention. Various changes can be made within the range that does not deviate.

<Modification 1>
As shown in FIGS. 5 and 10, the secondary query also includes requirements that do not change. It is possible to determine in advance whether or not the requirements that do not change can be executed for each data providing terminal 4. Therefore, it is possible to create a terminal-specific secondary query table that stores the secondary queries that can be executed by the data providing terminal 4 for each data providing terminal 4.

Executable secondary queries are, for example, position acquisition, positioning accuracy acquisition, image preservation, sensor operation, position-specified image acquisition, time-specified image acquisition, and the like. Of these, the process to be acquired is a target data requirement. In addition, maintenance is a target process. Sensor operation means changing the sensor settings, and changing the settings changes the data that can be acquired, so this is also a target data requirement.

When determining the data providing terminal 4 to receive the secondary query, each data providing terminal 4 refers to what kind of secondary query can be executed. Therefore, if a secondary query correspondence table for each terminal is created, the data providing terminal 4 to which the secondary query is sent can be easily determined. Also, by keeping it as a table, it becomes easy to make additions and changes.

1: Data acquisition system 2: Remote monitoring device (user device) 3: Server 4: Data providing terminal 5: Vehicle 31: Server communication unit 32: Storage unit 33: Control unit 41: Terminal communication unit 42: Sensor unit 43: Storage Unit 44: Control unit 103: Server 133: Control unit 134: Public unit 203: Server 233: Control unit 311: Server transmission unit 312: Server reception unit 321: Data retention unit 322: Query support table storage unit 323: Terminal requirement support Table storage unit 331: Primary query acquisition unit 332: Receiving terminal determination unit 333: Secondary query determination unit 334: Data processing unit 411: Terminal transmission unit 412: Terminal reception unit 421: Front camera 422: Rear camera 441: Communication control Part 442: Data acquisition part 903: Server 1333: Secondary query determination part 1335: Update part 2334: Retention judgment part 9334: Query satisfaction judgment part

Claims (29)

A server (3, 103, 203, 903) that acquires a primary query that is a data acquisition request including a requirement of the user request data requested by the user device from the user device (2), the user request data, and the user. A data acquisition system including a data providing terminal (4) that provides terminal-provided data that is any of the data from which request data can be derived, and the user apparatus acquires the user request data.
The server
A primary query acquisition unit (331) that acquires the primary query from the user device, and
From the primary query acquired by the primary query acquisition unit, the data providing terminal determines a secondary query which is a data acquisition request specifying the terminal provided data with an attribute capable of specifying the terminal provided data. Next query determination unit (333, 1333) and
A server transmission unit (311) for transmitting the secondary query determined by the secondary query determination unit to the data providing terminal is provided.
The data providing terminal is
A terminal receiving unit (412) that receives the secondary query transmitted by the server, and
A data acquisition unit (442) that executes the secondary query received by the terminal receiving unit to acquire the terminal-provided data, and
A data acquisition system including a terminal transmission unit (411) that transmits the terminal-provided data acquired by the data acquisition unit to a device determined by the secondary query. In claim 1,
The server determines a receiving terminal requirement, which is a requirement of the data providing terminal to receive the secondary query, based on the primary query acquired by the primary query acquisition unit, and the receiving terminal requirement is used as the basis for the receiving terminal requirement. A receiving terminal determination unit (332) for determining the data providing terminal for receiving a secondary query is provided.
The server transmission unit is a data acquisition system that transmits the secondary query determined by the secondary query determination unit to the data providing terminal determined by the reception terminal determination unit. In claim 1 or 2,
The terminal transmission unit transmits the terminal-provided data acquired by the data acquisition unit to the server.
The server
A server receiving unit (312) for receiving the terminal-provided data transmitted by the terminal transmitting unit, and
A data holding unit (321) for holding the terminal-provided data received by the server receiving unit is provided.
When the server transmission unit can determine the user request data requested by the primary query acquired by the primary query acquisition unit from the terminal-provided data held in the data holding unit, the server transmission unit may use the data holding unit. The user request data requested by the primary query determined based on the retained terminal-provided data is transmitted to the user device.
When the user request data requested by the primary query acquired by the primary query acquisition unit can be determined from the terminal-provided data held in the data holding unit, the secondary query determination unit may determine the secondary query. A data acquisition system that does not determine queries. In any one of claims 1 to 3,
The secondary query determination unit determines that the user request data requested by the primary query acquired by the primary query acquisition unit is not scheduled to be received based on the history of the secondary query. A data acquisition system that determines secondary queries. In any one of claims 1 to 4,
The primary query includes a performance requirement, which is an attribute requirement regarding the processing time for the user request data.
The secondary query is a data acquisition system including a processing requirement which is a requirement of an attribute determined corresponding to the execution requirement included in the primary query. In claim 5,
A data acquisition system including a requirement for determining the acquisition frequency of the user request data as the execution requirement. In claim 3,
The server is a data acquisition system including a holding determination unit (2334) that determines the terminal-provided data to be stored in the data holding unit based on the transmission history transmitted to the user apparatus. In any one of claims 1 to 7,
A data acquisition system in which the server (103) includes a public unit (134) that publishes the primary query that can determine the secondary query. In claim 3 or 7,
The secondary query determination unit (1333) determines, as the secondary query, a stationary query that is a data acquisition request for the terminal-provided data requested to the data-providing terminal regardless of the primary query.
The server transmission unit is a data acquisition system that transmits the steady-state query to the data providing terminal. In claim 9.
The routine query is a data acquisition system that includes the frequency of transmission of the terminal-provided data in addition to the requested attributes of the terminal-provided data. In claim 2,
The secondary query determination unit (1333) determines, as the secondary query, a stationary query that is a data acquisition request for the terminal-provided data requested to the data-providing terminal regardless of the primary query.
The server transmission unit sends the stationary query to the data providing terminal, and the server transmission unit sends the stationary query to the data providing terminal.
The terminal transmission unit executes the steady query and transmits the terminal-provided data acquired by the data acquisition unit to the server.
The server
A server receiving unit (312) for receiving the terminal-provided data transmitted by the terminal transmitting unit, and
A data holding unit (321) for holding the terminal-provided data received by the server receiving unit is provided.
The receiving terminal determination unit is a data acquisition system that determines whether or not the data providing terminal satisfies the receiving terminal requirements by interpolating the terminal providing data held in the data holding unit. In claim 9 or 10.
The routine query includes, in addition to the attributes of the terminal-provided data to be requested, a request to store the terminal-provided data in preparation for a transmission request of the terminal-provided data.
The data providing terminal is a data acquisition system including a storage unit (43) for accumulating the terminal-provided data when the stationary query including a request for accumulating the terminal-provided data is received. In any one of claims 9, 10 and 12,
The server
A public unit (134) that publishes the primary query that can determine the secondary query, and
When the constant query is transmitted, data acquisition including an update unit (1335) that adds the primary query that can provide the user request data to the public unit with the terminal-provided data that can be acquired by the stationary query. system. In claim 2,
When the primary query includes an attribute that can be specified from the map data, the receiving terminal determination unit determines and determines a map range in which the user request data requested by the primary query can be acquired. A data acquisition system that includes the map range in the receiving terminal requirement and determines the data providing terminal that receives the secondary query. In any one of claims 1 to 14,
The server includes a query correspondence table storage unit (322) that stores a query correspondence table that is a correspondence table between the primary query and the secondary query.
The secondary query determination unit is a data acquisition system that determines the secondary query to be transmitted to the data providing terminal from the primary query acquired by the primary query acquisition unit and the query correspondence table. In claim 2 or 14,
The server includes a terminal requirement correspondence table storage unit (323) that stores a terminal requirement correspondence table that is a correspondence table between the primary query and the receiving terminal requirement.
The receiving terminal determination unit is a data acquisition system that determines the data providing terminal that receives the secondary query from the primary query acquired by the primary query acquisition unit and the terminal requirement correspondence table. In claim 16,
The terminal requirement correspondence table has a sufficiency score in which the higher the degree to which the requirement is satisfied for at least one receiving terminal requirement, the higher the value.
The receiving terminal determination unit receives the secondary query from the required number of the data providing terminals in order from the data providing terminal having the highest sufficiency score among the data providing terminals satisfying the receiving terminal requirements. A data acquisition system that is determined by the providing terminal. In claim 5,
The server includes a query correspondence table storage unit (322) that stores a query correspondence table that is a correspondence table between the primary query and the secondary query.
The query correspondence table defines the correspondence between the execution requirement of the primary query and the processing requirement of the secondary query.
The secondary query determination unit determines data for determining the processing requirement of the secondary query from the execution requirement included in the primary query acquired by the primary query acquisition unit and the query correspondence table. Acquisition system. In any one of claims 2, 14 and 16.
The primary query includes a performance requirement, which is an attribute requirement regarding the processing time for the user request data.
The secondary query includes processing requirements that are attribute requirements that are determined in response to the performance requirements included in the primary query.
The processing requirement has a sufficiency cost in which the value increases as the burden required to satisfy the requirement increases.
The receiving terminal determination unit receives the secondary query from the required number of the data providing terminals in order from the data providing terminal having the lowest sufficiency cost among the data providing terminals satisfying the receiving terminal requirements. The data acquisition system that determines the terminal. In claim 19.
The sufficiency cost is a data acquisition system which is a communication cost when the terminal-provided data is transmitted from the terminal transmission unit. In any one of claims 2, 14, 16, 17, and 19.
The receiving terminal determination unit determines the data providing terminal capable of executing the secondary query based on the terminal-specific secondary query table that stores the secondary query that can be executed by the data providing terminal for each data providing terminal. The data acquisition system to decide. In any one of claims 9, 10, 12, and 13,
The server transmission unit transmits the stationary query to the registered data providing terminal, and when the data providing terminal is newly registered, the stationary query is also sent to the newly registered data providing terminal. Data acquisition system to send. In any one of claims 1 to 22,
The primary query is a data acquisition system including a terminal time requirement, which is a requirement for the time when the data providing terminal acquires the terminal provided data. In claim 2,
The primary query includes a terminal time requirement that is a requirement for the time when the data providing terminal acquires the terminal provided data, and the time when the data providing terminal acquires the terminal provided data includes a future time. If you are
The receiving terminal determination unit searches for the data providing terminal capable of executing the secondary query at the future time, and as a result of the search, the data providing terminal that receives the secondary query is determined. Until a future time, the data providing terminal capable of executing the secondary query at the future time is repeatedly searched, and the newly searched data providing terminal capable of executing the secondary query at the future time. Also, a data acquisition system that determines the data providing terminal that receives the secondary query. 24.
In addition to the terminal time requirement, the primary query also includes a requirement for the location of the data providing terminal at the future time determined by the terminal time requirement.
The receiving terminal determination unit is a data acquisition system that predicts a position where the data providing terminal exists at the future time determined by the terminal time requirement and determines the data providing terminal that receives the secondary query. In claim 25
When the receiving terminal determination unit can acquire the movement plan of the data providing terminal, the data acquisition unit predicts the position where the data providing terminal exists at the future time determined by the terminal time requirement based on the moving plan. system. In any one of claims 5, 6 and 18.
The server
The primary query satisfaction information indicating the possibility of providing the user request data to the user apparatus is determined according to the execution requirements included in the primary query, and the determined primary query satisfaction information is transmitted to the server. A data acquisition system including a query satisfaction determination unit (9334) to be transmitted from the unit to the user device. 27.
The query satisfaction determination unit sequentially determines the primary query satisfaction information after the secondary query determination unit determines the secondary query, and the content of the primary query satisfaction information is the same according to the execution requirement. When the user request data can be provided to the user device to indicate that the user request data cannot be provided to the user device in accordance with the execution requirements, the primary query satisfaction information is transmitted to the server. A data acquisition system that is transmitted from a transmission unit to the user device. A server (3, 103, 203) that acquires a primary query, which is a data acquisition request including a requirement of user request data, which is data requested by the user device, from the user device (2).
A primary query acquisition unit (331) that acquires the primary query from the user device, and
From the primary query acquired by the primary query acquisition unit, the data providing terminal that provides the terminal-provided data that is either the user request data or the data from which the user request data can be derived identifies the terminal-provided data. A secondary query determination unit (333, 1333) that determines a secondary query that is a data acquisition request that specifies the terminal-provided data with possible attributes.
A server including a server transmission unit (311) that transmits the secondary query determined by the secondary query determination unit to the data providing terminal.

Images