JP6332791B2 - Sensor data sharing method, server, and program - Google Patents

Description

  The present invention relates to a sensor data sharing method, a server, and a program, and more particularly, to a sensor data sharing method in which a first server included in a first moving body shares sensor data with a second server included in a second moving body.

  In recent years, the information environment surrounding mobile objects such as cars has been remarkably developed. For example, in-vehicle sensors such as cameras and GPS are becoming smaller and less expensive. Outside the vehicle, for example, an intelligent transportation system (ITS) has been developed. In addition, high-functional smartphones owned by passengers have become widespread.

  Various applications such as a multifunctional navigation system (see Non-Patent Document 1) and a disaster area information collecting / providing system (see Non-Patent Document 2) are shown as applications that utilize such information.

Tomohiro Yamashita and two other authors, “Proposal of collaborative car navigation system for smooth traffic flow (Vehicle-to-vehicle communication technology, <Special issue> Advanced traffic systems and mobile communication systems that bring next-generation social infrastructure)," Journal of Information Processing Society of Japan , 49 (1), 2008, 177-188. Kenta Ito and 3 other authors, “Construction of a spatio-temporal video distribution system that takes into account poor communication environment,” National Conference Proceedings, 2013 (1), 2013, 299-301.

  However, there has not been enough research on a mechanism that handles the collection, sharing, and utilization of data in a unified manner so that applications can use this information in combination.

  Therefore, an object of the present invention is to provide a sensor data sharing method or the like that makes it possible to easily and uniformly manage sensor data in a plurality of moving bodies.

  A first aspect of the present invention is a sensor data sharing method in which a first server included in a first moving body shares sensor data with a second server included in a second moving body, and the second server includes a sensor Includes second storage means for storing measurement data measured by the sensor together with measurement attached data indicating the position and / or time measured by the sensor, and the second connection means provided in the second server is connected to the first server. And a server connection step of transmitting server type information indicating that the server is a server from the first server, and a second communication means provided in the second server includes a location and a position from the first server that has received the server type information. The query communication step of receiving a first query including time data and / or the second search means included in the second server includes the location and / or time included in the first query. A search step for extracting the measurement data by searching for the measurement attached data stored in the second storage means using a data, and the second communication means provided in the second server comprises the first server On the other hand, the search result communication step for transmitting the measurement data extracted in the search step together with the measurement attached data, and the second cutting means provided in the second server are in a state where communication with the first server is not possible. A server disconnecting step of disconnecting the connection with the first server in the event of a failure.

  A second aspect of the present invention is a sensor data sharing method according to the first aspect, wherein the second connection means provided in the second server is connected to the sensor and indicates that the sensor is a sensor. A sensor connection step for receiving sensor type information; a sensor communication step for receiving measurement data measured by the sensor; and a second control means for the second server. And a sensor data management step of storing the received measurement data in the second storage means.

  According to a third aspect of the present invention, there is provided a sensor data sharing method according to the first or second aspect, wherein in the server connection step, the second connection means provided in the second server includes the first server from the first server. Server type information is received, and in the query communication step, the second communication means included in the second server transmits a second query including position and / or time data to the first server, and the search In the result communication step, the second communication means included in the second server is configured to extract measurement data extracted from the first server using the position and / or time data included in the transmitted second query, The second control means included in the second server, which is received together with the measurement attachment data, shares the received measurement data with the measurement attachment data in the second storage means. It is intended to be stored.

  A fourth aspect of the present invention is the sensor data sharing method according to any one of the first to third aspects, wherein, in the query communication step, the position and / or time data included in the query is the first data. In the navigation system provided in one moving body, the first moving body is scheduled to move, and the navigation system uses the measurement data and the measurement attached data received in the search result communication step. In the first moving body, information is displayed together with a position where the first moving body is scheduled to move.

  A fifth aspect of the present invention is a server that can be mounted on a mobile object, and cannot communicate with a connection unit that connects to a peripheral device, a communication unit that communicates with the connected peripheral device, and the connected peripheral device. A disconnecting means for disconnecting the connection with the peripheral device in a state, the peripheral device includes a sensor and another server, and the connecting means is connected to the peripheral device and connected to the peripheral device; If the type information indicates a server, the communication means receives a query including position and / or time data for the peripheral device if the type information indicates a server. The processing result of the query in the peripheral device is received and if the type information indicates a sensor, the measurement data is received from the peripheral device.

  A sixth aspect of the present invention is a program for causing a computer that can be mounted on a mobile object to function as a server according to a fifth aspect.

  The present invention may be regarded as a computer-readable recording medium for recording the program according to the sixth aspect. “A and / or B” means at least one of A and B.

  In order for an application to use sensor data, the sensor type and the data format handled by the sensor need to be known. However, the server included in the mobile body is not only connected to a sensor (such as a camera or GPS) mounted on the mobile body or a device (such as a smartphone) managed by the passenger, but also connected to a sensor or server outside the mobile body. Connection needs to be considered. For a server mounted on a mobile body, in particular, sensors and servers outside the mobile body are unknown devices, and establishment of communication with such unknown devices is important.

Conventionally, a gateway (GW) is arranged between the sensor network and the server network. Therefore, it has been difficult to establish communication with an unknown device. Further, the conventional distributed DB has been designed under the concept of processing large-scale data and high-speed data like the Internet cloud.

  In general Plug and Play such as UBS, when a peripheral device is connected to the computer, the peripheral device transmits the type of the peripheral device to the computer. Recognize the type. The power consumption of processors and wireless communication has been reduced, and by adopting a lightweight protocol, plug and play can be implemented on the sensor node side.

  According to each aspect of the present invention, sensor data can be managed in a plurality of servers by applying this plug-and-play mechanism, recognizing type information at the time of connection and connecting to a server outside the moving body. It can be easily realized. Furthermore, it becomes possible to form a local cloud by connecting moving bodies. Such sharing of sensor data can be used without the passenger being aware of it. Furthermore, although the network configuration changes, it is also possible to construct a distributed database that absorbs the change.

  In particular, since it is mounted on a moving body, sensor data is managed as spatio-temporal sensor data, etc., and sensor data is shared by utilizing position data and / or time data related to the moving body. As in point 4, communication is established with a server mounted on a vehicle that is parked in the oncoming lane waiting for a signal, and the vehicle collects sensor data relating to the position where the vehicle will proceed in the future. It becomes possible.

  Further, the position and time data included in the query are set as the position and time at which the mobile object has passed, and the server that has received the query searches the camera for the passage position taken at the passage time, and the camera took the picture. Still image / moving image data may be transmitted. Thereby, the server mounted on the moving body can obtain image data taken from outside the moving body.

  As described above, by sharing the sensor data using the position data and the time data in the servers between the moving bodies, the quality of the service provided by the server mounted on each moving body can be greatly improved. .

  Furthermore, according to the second aspect of the present invention, a server mounted on a mobile body is connected not only to a server mounted on another mobile body but also to a sensor by utilizing plug and play. Thus, unified communication establishment between the server and the sensor and between the server and the server can be realized. Furthermore, the sensor data is managed in a unified manner by the servers mounted on each mobile body, and the sensor type and data format can be handled in a unified manner.

  Furthermore, according to the 3rd viewpoint of this invention, it becomes possible to mutually share sensor data between the servers of a mobile body.

It is a block diagram which shows the outline | summary of a structure of the sensor data management system which concerns on the Example of this invention. It is a flowchart which shows an example of a process in case the vehicle-mounted server 11 of FIG. 1 applies a plug and play and connects with a connection apparatus. It is a flowchart which shows an example of the process which the client apparatus of FIG. 1 transmits a query with respect to the vehicle-mounted server 11, and provides a service based on a search result. FIG. 2 is a flowchart illustrating an example of a process in which the sensor device of FIG. 1 transmits measurement data to an in-vehicle server 11. It is a flowchart which shows an example of the process which the vehicle-mounted server 11 of FIG. 1 performs. It is a figure which shows the prototype (a) sensor node, (b) sensor server, and (c) application. It is a figure which shows the block diagram of the sensor node of Fig.6 (a). It is a figure which shows the block diagram of the sensor server of FIG.6 (b). It is a display example of the application of FIG.6 (c), and is a figure which shows the display example of a sensor list. It is another example of a display of the application of FIG.6 (c), (a) what plotted the data on the map according to progress of time, and (b) two types of obtained data displayed along time FIG.

  Embodiments of the present invention will be described below with reference to the drawings. The embodiment of the present invention is not limited to the following examples.

  FIG. 1 is a block diagram showing an outline of a sensor data management system according to an embodiment of the present invention. The sensor data management system 1 includes a moving body 3 (an example of “second moving body” in the claims of the present application), a moving body 5 (an example of “first moving body” in the claims of the present application), and an outside sensor 7 (this application). An example of “sensor” in the claims.

  The mobile body 3 includes an in-vehicle server 11 (an example of “second server” in the claims of the present application), an information terminal 13, an in-vehicle sensor 15 (an example of “sensor” in the claims of the present application), and a navigation system 17.

  The in-vehicle server 11 includes a sensor data storage unit 21 (an example of “second storage unit” in the claims of the present application), a search unit 23 (an example of “second search unit” in the claims of the present application), and a server connection unit 25 ( An example of “second connection means” in claims of this application, a server communication unit 27 (an example of “second communication means” in claims of this application), and a server cutting unit 29 (“second cutting means” of claims of this application). And a server control unit 31 (an example of “second control means” in the claims of the present application).

  The information terminal 13 is, for example, a smartphone, and provides a service using data stored in the in-vehicle server 11 or the like in accordance with a passenger's operation. The information terminal 13 includes a terminal control unit 59, a terminal connection unit 61, a terminal disconnection unit 63, and a terminal communication unit 65.

  The in-vehicle sensor 15 is a sensor that is fixed in the moving body, such as a camera. Also, temperature, acceleration, etc. can be measured. The in-vehicle sensor 15 includes an in-vehicle sensor measurement unit 33, an in-vehicle sensor storage unit 35, an in-vehicle sensor connection unit 37, an in-vehicle sensor communication unit 39, an in-vehicle sensor cutting unit 41, and an in-vehicle sensor control unit 42.

  The navigation system 17 obtains the current time, detects the current position where the moving body is located, and obtains the passing position and the passing time from the current position to the destination by the passenger inputting the destination. The navigation system 17 includes an input unit 43, a display unit 45, an NV measurement unit 47, an NV storage unit 49, an NV connection unit 51, an NV communication unit 53, an NV disconnection unit 55, and an NV control unit 57. Prepare.

  The moving body 5 includes an in-vehicle server 67. The in-vehicle server 67 has the same configuration as the in-vehicle server 11.

  The vehicle exterior sensor 7 includes a vehicle exterior sensor measurement unit 71, a vehicle exterior sensor storage unit 73, a vehicle exterior sensor connection unit 75, a vehicle exterior sensor communication unit 77, a vehicle exterior sensor disconnection unit 79, and a vehicle exterior sensor control unit 81. In the present embodiment, the outside sensor measurement unit 71, the outside sensor storage unit 73, the outside sensor connection unit 75, the outside sensor communication unit 77, the outside sensor disconnecting unit 79, and the outside sensor control unit 81 of the outside sensor 7 are respectively The vehicle-mounted sensor measurement unit 33, the vehicle-mounted sensor storage unit 35, the vehicle-mounted sensor connection unit 37, the vehicle-mounted sensor communication unit 39, the vehicle-mounted sensor disconnecting unit 41, and the vehicle-mounted sensor control unit 42 of the vehicle-mounted sensor 15 are configured and unified. Can be managed.

  The in-vehicle server 11 is connected to the information terminal 13, the in-vehicle sensor 15, and the navigation system 17 by applying plug and play. Communication between devices may be wired communication or wireless communication.

  The server control unit 31 of the in-vehicle server 11 stores the measurement data measured by the in-vehicle sensor 15 in the sensor data storage unit 21 together with the current time and the current position obtained by the navigation system 17, thereby storing the sensor data. The unit 21 stores the spatio-temporal sensor data. That is, the sensor data storage unit 21 stores measurement data measured by the in-vehicle sensor 15 together with data indicating the measurement time and the measurement position.

  The information terminal 13 transmits a query for searching the sensor data storage unit 21 to inquire the sensor data necessary for the service to the in-vehicle server 11 by the operation of the passenger. The search unit 23 of the in-vehicle server 11 searches the sensor data 21 using this query, and transmits the search result to the information terminal 13. The terminal control unit 59 of the information terminal 13 performs information processing using the search result and provides a service to the passenger.

  The navigation system 17 includes position and time data indicating the passing position and passing time of the moving body 3 so far, and position and time data indicating the scheduled passing position and the scheduled passing time to the destination set by the operation of the passenger. It manages information such as. The navigation system 17 includes the passing position and the passing time so far for the in-vehicle server 11 when the passenger operates to give an instruction to know a change in temperature at a point that has passed so far. Send a query. The in-vehicle server 11 searches the sensor data storage unit 21 based on the position and time included in the query, and transmits measurement data indicating the temperature corresponding to the passing position and the passing time as a search result. The navigation system 17 can display the temperature along with the passage route.

  Below, what measures and transmits the measurement data which shows a measurement result with respect to a vehicle-mounted server is called "sensor apparatus." A device that transmits a query to the in-vehicle server according to the operation of the passenger and provides a service to the passenger using a search result by the in-vehicle server is referred to as a “client device”. In FIG. 1, the vehicle exterior sensor 7 and the vehicle-mounted sensor 15 are examples of sensor devices. The information terminal 13 is an example of a client device.

  The navigation system 17 is an example of a sensor device in that the current time and current position are transmitted to the server, and is a client device in that it transmits a query to the in-vehicle server 11 and provides a service to the passenger. It is an example. Thus, one device may serve as both the sensor device and the client device. The input unit 43 of the navigation system 17 is for a passenger to input a destination or the like. The display unit 45 displays processing results and the like. The NV measurement unit 47 performs measurement as a sensor device and stores measurement data in the NV storage unit 49. The NV control unit 57 operates in the same manner as the terminal control unit 59 as a client device, and operates in the same manner as the in-vehicle sensor control unit 42 as a sensor device. The NV connection unit 51 and the NV disconnection unit 55 are connected by applying plug and play in the same manner as other devices. The NV communication unit 53 communicates with other devices.

  The in-vehicle server 11 is also connected to the outside sensor 7 and the in-vehicle server 67 of another moving body (the moving body 5). Sensors and servers outside the moving body are unknown to the passenger. Moreover, these need to exist in the range which can communicate with the vehicle-mounted server 11, and connection time also becomes temporary. Therefore, establishment of communication with such unknown sensors and servers is important. The in-vehicle server 11 is connected to the outside sensor 7 and the in-vehicle server 67 by applying plug and play. Thereby, the passenger does not need to be specifically aware of the sensor or server to which the in-vehicle server 11 is connected, and the in-vehicle server 11 can easily connect even if the in-vehicle server 11 is an unknown sensor or server. .

  The vehicle outside sensor 7 manages the measurement data together with the measurement position and the measurement time, and stores the spatiotemporal sensor data. When connected to the in-vehicle server 11, the vehicle exterior sensor 7 may transmit, for example, the temporal and spatial sensor data to be stored together, and subsequently transmit the data measured during the connection at the time of measurement. Moreover, when calculated | required from the vehicle-mounted server 11, you may transmit the spatiotemporal sensor data corresponding to it. Furthermore, Radio on Demand technology may be used. Due to the radio on demand, the outside sensor 7 can sleep when not in use and wake up when in use, and the power consumption of the outside sensor 7 can be greatly reduced. The radio-on-demand is not limited to the sensor 7 outside the vehicle, and may be adopted by other devices as necessary.

  The moving body 5 is a moving body different from the moving body 3. For example, the oncoming vehicle is stopped in the opposite lane when the moving body 3 is stopped waiting for a signal. By connecting the in-vehicle server 11 and the in-vehicle server 67, a temporary cloud service can be provided by these in-vehicle servers. For example, when the navigation system 17 transmits a query including planned future passing position data to the in-vehicle server 11, this position is expected to include the position where the moving body 5 that stops in the oncoming lane has passed. . Therefore, for example, traffic information is provided by using the measurement data measured at the position where the mobile body 3 is scheduled to pass by searching using this position data and utilizing the search result. Or providing information related to road closures and road surface conditions, it is possible to provide useful services to passengers.

  Hereinafter, an example of the operation of the sensor data management system 1 of FIG. 1 will be described with reference to FIGS.

  FIG. 2 is a flowchart showing an example of processing when the in-vehicle server 11 connects to a client device, a sensor device, or another server (referred to as “connection device”) by applying plug and play. .

  First, the in-vehicle server 11 and the connection device perform initial settings (step STCN1).

  Subsequently, it is determined whether or not they are within a range where they can communicate with each other (step STCN2). This process is repeated until connection is established.

  In the case of connection, a service announcement is made between the in-vehicle server 11 and the connection device (step STCN3). The in-vehicle server 11 transmits server type information indicating that it is an in-vehicle server and an information service that can be provided (for example, that temperature data can be searched) to the connection device. If the connection device is a client device, the connection device transmits client type information indicating that the connection device is a client device. If it is a sensor device, it transmits sensor type information indicating that it is a sensor, a sensor type such as one that measures temperature, and format identification information that specifies a data format handled by the sensor. If it is a server, it transmits server type information indicating that it is a server and an information service that can be provided.

  Subsequently, the in-vehicle server 11 and the connection device manage information obtained from the other party to be connected in a list (step STCN4).

  Then, it is determined whether or not it has been disconnected (step STCN5). The disconnection is performed by, for example, being out of a communicable range or operated by a passenger of a moving body. Until disconnected, the connection state is maintained and communication is possible. If disconnected, delete it from the list and return to step STCN2.

  The process of FIG. 2 is performed for each of a plurality of connection devices, and is managed in a unified manner by the list managed in step STCN4.

  Steps STCN1 to STCN4 are performed by the server connection unit 25 in the in-vehicle server 11. Moreover, in the information terminal 13, the terminal connection part 61 performs. In the in-vehicle sensor 15, the in-vehicle sensor connection unit 37 performs this. In the navigation system 17, the NV connection unit 51 performs this. In the vehicle outside sensor 7, the vehicle outside sensor connection part 75 performs.

  Step STCN5 is performed by the server cutting unit 29 in the in-vehicle server 11. Moreover, in the information terminal 13, the terminal cutting part 63 performs. In the in-vehicle sensor 15, the in-vehicle sensor cutting unit 41 performs. In the navigation system 17, the NV cutting unit 55 performs this. In the outside sensor 7, the outside sensor cutting unit 79 performs this.

  Methods for utilizing sensor data obtained from a sensor device include reflection, judgment, learning, and communication stages. Reflection operates directly on the sensor signal. The judgment is based on a plurality of sensor signals. In this case, it is necessary to grasp the sensor type. Learning operates by utilizing past sensor data. In this case, it is necessary to store sensor data. Communication operates using sensor data from the surroundings. In this case, it is necessary to share sensor data. In the present invention, by applying plug and play, the in-vehicle server can easily grasp the sensor type of the sensor device without requiring the setting for grasping the sensor type. Can be stored and shared with other servers, and sensor data can be easily utilized.

  For example, when the in-vehicle server is close to the sensor device and the sensor device joins the network, the in-vehicle server notifies the sensor device that it is a server, and the sensor device notifies that it is an acceleration sensor, for example. When the server requests acceleration data from the sensor device, the sensor device can transmit the acceleration data.

  Further, when storing the sensor data, the in-vehicle server can clearly grasp when, where, and who acquired the sensor data. Plug-and-play can support storage of unknown sensor data. The sensor is not limited to the in-vehicle device, and for example, a hundred-leaf box can be assumed. Such an in-vehicle server is a lightweight database that can be operated by an embedded device. For example, an in-vehicle server not only stores information that the temperature is 23 ° C, but also the time (September 21, 2013 13:00:45, etc.) and location (E141 ° 09'N39 ° 42 ', etc.) ), Including information on how it was obtained (such as in the experimental vehicle A) can be managed as spatiotemporal sensor data.

  Further, a distributed database in which sensor data can be shared and mobile objects exchange data with each other can be easily realized. For example, when it is assumed that communication with the outside of the vehicle is difficult, such as in a moving vehicle, the client device service is realized using only the in-vehicle server. At home or the like, the in-vehicle server can connect to the Internet and use the cloud via the Internet. In addition, when the vehicle is stopped at an intersection or the like, a local cloud can be formed using inter-vehicle communication to realize a client device service. Furthermore, local parking and Internet cloud can be realized in parking lots.

  FIG. 3 is a flowchart illustrating an example of processing in which the client device of FIG. 1 transmits a query to the in-vehicle server 11 and provides a service based on the search result. A case where the information terminal 13 transmits a query to the in-vehicle server 11 and provides a service based on a search result will be described. Other client devices can be similarly realized.

  The information terminal 13 and the in-vehicle server 11 perform initial setting (step STCL1). Subsequently, the terminal control unit 59 of the information terminal 13 determines whether or not the in-vehicle server 11 is connected (step STCL2). Waiting until the information terminal 13 is connected to the in-vehicle server 11, and when the terminal connection unit 61 of the information terminal 13 is connected to the in-vehicle server 11 by the process of FIG. 2, the terminal communication unit 65 provides the service to the in-vehicle server 11. A query required to do this is transmitted (step STCL3). Hereinafter, a case where position data is included in the query will be described.

  Terminal control unit 59 determines whether or not a search result has been received (step STCL4). If the search result has not been received, it is determined whether or not it has been disconnected (step STCL5). If not disconnected, the process returns to step STCL4. If disconnected, the process returns to step STCL2.

  When the search result is received, the terminal control unit 59 provides a service to the passenger (step STCL6). And it is judged whether it cut | disconnected (step STCL7). If not disconnected, the process returns to step STCL3. If disconnected, the process returns to step STCL2.

  FIG. 4 is a flowchart illustrating an example of a process in which the sensor device of FIG. 1 transmits measurement data to the in-vehicle server 11. A case where the in-vehicle sensor 15 transmits measurement data to the in-vehicle server 11 will be described. Other sensor devices can be similarly realized.

  The in-vehicle sensor 15 and the in-vehicle server 11 perform initial settings (step STS1). In the in-vehicle sensor 15, the measurement data obtained by measurement by the in-vehicle sensor measurement unit 33 is stored in the in-vehicle sensor storage unit 35. For example, the in-vehicle sensor measurement unit 33 measures temperature and acceleration, and stores the measurement data in the in-vehicle sensor storage unit 35 in time series.

  Subsequently, the in-vehicle sensor control unit 42 of the in-vehicle sensor 15 determines whether it is connected to the in-vehicle server 11 (step STS2). The in-vehicle sensor 15 waits until the in-vehicle sensor 15 is connected to the in-vehicle server 11, and when the in-vehicle sensor connection unit 37 of the in-vehicle sensor 15 is connected to the in-vehicle server 11 by the process of FIG. The measurement data stored in the sensor storage unit 35 is transmitted (step STS3). Here, the type of data to be transmitted may be limited to acceleration data, for example, according to a request from the server. In addition, measurement data that has already been transmitted may not be transmitted.

  Subsequently, the in-vehicle sensor control unit 42 determines whether or not a query has been received from the in-vehicle server 11 (step STS4). The query is, for example, for searching temperature information measured from a certain time to a later time. When receiving the query, the in-vehicle sensor control unit 42 searches the in-vehicle sensor storage unit 35 using the query, and transmits the search result to the in-vehicle server 11 (step STS5). Then, it is determined whether or not it has been cut (step STS6), and if cut, the process returns to step STS2, and if not cut, the process returns to step STS3. If no query is received in step STS4, the process proceeds to step STS6.

  FIG. 5 is a flowchart showing an example of processing performed by the in-vehicle server 11 of FIG. The in-vehicle server 11 performs initial setting (step STSR1).

  Subsequently, the server control unit 31 determines whether or not the client device is connected (step STSR2). If not connected, the process proceeds to step STSR5. If connected, a query is received from the client device (step STSR3) (see step STCL3 in FIG. 3). Then, the search unit 23 searches the sensor data storage unit 21 using the received query. The server communication unit 27 transmits the search result to the client device (step STSR4). The in-vehicle server 11 transmits the query received from the client device to the sensor device as necessary (see step STSR8) or to another server (see step STSR14). The search result by these is also transmitted to the client device. Then, the process proceeds to step STSR5.

  In step STSR5, the server control unit 31 determines whether or not it is connected to the sensor device. If the sensor device is not connected, the process proceeds to step STSR10. If connected, it receives data from the sensor device and stores it in the sensor data storage unit 21 (step STSR6) (see step STS3 in FIG. 4). Subsequently, using the type information received from the sensor device, it is determined whether there is an information service corresponding to the query (step STSR7). If there is no information service, the process proceeds to step STSR10. If there is an information service, a query is transmitted to the sensor device (step STSR8), the search result is received (step STSR9), and the process proceeds to step STSR10. The received search result is transmitted to the client device (see step STSR4).

  In step STSR10, the server control unit 31 determines whether or not it is connected to another server (step STSR10). If not connected to the server, the process returns to step STSR2. If connected to the server, the server communication unit 27 receives a query from the partner server (step STSR11), and the search unit 23 performs a search process of the sensor data storage unit 21 using the query, and the server communication unit 27 transmits the search result (step STSR12). Subsequently, the server control unit 31 determines whether there is an information service corresponding to the query of the own server using the type information received from the counterpart server (step STSR13). If there is no information service, the process returns to step STSR2. If there is an information service, the server communication unit 27 transmits a query to the partner server (step STSR14), receives the search result from the partner server, and returns to step STSR2. The received search result is transmitted to the client device (see step STSR4).

  Although the spatio-temporal sensor data has been described as an example, for example, there may be a service that stores only sensor data or a service that stores and services time sensor data. There may be one that memorizes and services. In addition, the spatio-temporal sensor data stored in the in-vehicle server 11 is not only obtained by directly connecting the measurement data measured by the vehicle outside sensor 7 to the vehicle outside sensor 7 but also obtained via the Internet or the like. May be included.

  Moreover, according to this invention, the vehicle-mounted server 11 accumulate | stores the query from the information terminal 13 until the process using the query is implement | achieved, and after the process using a query is performed, information terminal 13 provides a service using the obtained information. Therefore, for example, the in-vehicle server stores a query for public communication such as the Internet, performs a process using the query when connected to the public communication, and then provides a service by the information terminal 13 You may have.

  As described above, the in-vehicle server of the present invention obtains the surrounding environment (location, weather, date, etc.) and vehicle status (vehicle type, maintenance status, driving history, etc.) by using a sensor, and from a public institution, etc. Obtain road conditions, infrastructure information, etc. In addition, obtain information on other vehicles from other vehicles, identify the person, obtain action history, and provide services according to preferences It becomes possible. In this way, advanced services can be realized. In this way, it is possible to enhance the car navigation system and the like.

  In particular, the information obtained from each vehicle can be shared, and any vehicle can be connected to public communication so that the information on the entire vehicle can be shared. Useful for. Until now, most of the information on disaster areas has been obtained from each vehicle. For this reason, information obtained from vehicles that can be connected outside the disaster area has been mainly utilized. According to the present invention, it is possible to share a lot of vehicle information outside the disaster area if any vehicle can be shared and connected to public communication.

  The in-vehicle sensor information server that has been prototyped and verified will be described with reference to FIGS. FIG. 6 is a diagram showing a prototype (a) sensor node, (b) sensor server, and (c) application.

  The sensor node in FIG. 6A is provided with a wireless terminal (Raspberry Pi), a sensor controller (Arduino Mega), and a sensor (acceleration, etc.). FIG. 7 shows a block diagram of the sensor node of FIG.

  The sensor server in FIG. 6B is configured by PC based Linux (registered trademark) (Ubuntu 12.0.4). FIG. 8 shows a block diagram of the sensor server of FIG.

  9 and 10 show display examples of the application shown in FIG. FIG. 9 shows a display example of the sensor list. A sensor server is displayed on the left and a sensor list is displayed on the right, and a sensor can be selected. FIG. 10A is a plot of data on a map over time. FIG. 10B shows the two types of data obtained along time.

  Further, according to the present invention, it is possible to realize a moving image or the like by utilizing not only the image of the in-vehicle camera of the own vehicle but also the image of the own vehicle taken by another vehicle, the image of the sightseeing spot fixed point camera, or the like.

  DESCRIPTION OF SYMBOLS 1 Sensor data management system, 3, 5 Mobile body, 7 Outside sensor, 11, 67 Vehicle-mounted server, 13 Information terminal, 15 Vehicle-mounted sensor, 17 Navigation system, 21 Sensor data storage part, 23 Search part, 25 Server connection part, 27 Server communication unit, 29 Server disconnection unit, 31 Server control unit, 33 In-vehicle sensor measurement unit, 35 In-vehicle sensor storage unit, 37 In-vehicle sensor connection unit, 39 In-vehicle sensor communication unit, 41 In-vehicle sensor disconnection unit, 42 In-vehicle sensor control unit, 43 input unit, 45 display unit, 47 NV measurement unit, 49 NV storage unit, 51 NV connection unit, 53 NV communication unit, 55 NV disconnection unit, 57 NV control unit, 59 terminal control unit, 61 terminal connection unit, 63 terminal Cutting unit, 65 Terminal communication unit, 71 Outside sensor measurement unit, 73 Outside sensor storage unit, 75 Outside sensor contact Parts, 77 exterior sensor communication unit, 79 outside the sensor cut portion, 81 outside the sensor control unit

Claims (6)

The first server included in the first mobile body is a sensor data sharing method in which sensor data is shared with the second server included in the second mobile body,
The second server includes second storage means for storing measurement data measured by the sensor together with measurement attached data indicating a position and / or time measured by the sensor,
Second connecting means for said second server provided in a server connected sending server type information indicating that the first connected to the server, a server to the first server,
A query communication step in which a second communication means included in the second server receives a first query including position and / or time data from the first server that has received the server type information;
The second search means included in the second server searches the measurement attached data stored in the second storage means by using the position and / or time data included in the first query, thereby measuring the measurement data. A search step to extract
A search result communication step in which the second communication means included in the second server transmits the measurement data extracted in the search step together with the measurement attached data to the first server;
A sensor data sharing method including a server disconnecting step of disconnecting a connection with the first server when a second disconnecting unit included in the second server becomes unable to communicate with the first server. A sensor connection step in which the second connection means included in the second server is connected to the sensor and receives sensor type information indicating that the sensor is a sensor from the sensor;
A sensor communication step in which the second communication means provided in the second server receives measurement data measured by the sensor; and
The sensor data sharing method according to claim 1, wherein the second control means included in the second server includes a sensor data management step of storing the received measurement data in the second storage means. In the server connection step, the second connection means included in the second server receives the server type information from the first server,
In the query communication step, the second communication means included in the second server transmits a second query including position and / or time data to the first server,
In the search result communication step,
The second communication means included in the second server receives measurement data extracted from the first server using the position and / or time data included in the transmitted second query together with measurement attached data. And
The sensor data sharing method according to claim 1 or 2, wherein the second control means provided in the second server causes the second storage means to store the received measurement data together with the measurement attached data. In the query communication step, the position and / or time data included in the first query is intended to move the first moving body in a navigation system provided in the first moving body,
The navigation system uses the measurement data and the measurement attached data received in the search result communication step to display information on the first moving body together with a position where the first moving body is scheduled to move. The sensor data sharing method according to claim 1. A server that can be mounted on a mobile unit,
Connection means for connecting with peripheral devices;
Communication means for communicating with the connected peripheral device;
A disconnect means for disconnecting the connection with the peripheral device when communication with the connected peripheral device is disabled;
The peripheral devices include sensors and other servers,
The connection means is connected to the peripheral device and receives type information indicating the type of device from the connected peripheral device,
The communication means includes
If the type information indicates a server, a query including position and / or time data is transmitted to the peripheral device, and the processing result of the query in the peripheral device is received,
If the type information indicates a sensor, the server receives measurement data from the peripheral device.   The program for functioning the computer which can be mounted in a moving body as a server of Claim 5.