JP6926941B2 - Communication systems, in-vehicle devices, and programs - Google Patents

Description

The present disclosure relates to a communication system including a vehicle and a server capable of communicating with the vehicle, an in-vehicle device provided by the vehicle capable of communicating with the server, and a program executed by a computer capable of communicating with the server.

Conventionally, a vehicle equipped with a navigation device capable of searching a route from a current location to a destination has been known. For example, Japanese Patent Application Laid-Open No. 2016-90515 (Patent Document 1) has a function of guiding a route from a current location to a destination, and displays an image showing a guidance route and an image showing a distance to the destination on a display. A vehicle equipped with a navigation device to be operated is disclosed.

Japanese Unexamined Patent Publication No. 2016-90515

By the way, it is common to inadvertently forget to take a picture while traveling. In such a case, there is a demand for a system that allows someone to take a picture that they have forgotten to take. For example, it would be convenient for users if a system could be constructed that allows other users to smoothly take pictures that they forgot to take by using the route guidance of the navigation device provided in the vehicle disclosed in Patent Document 1. Is improved.

The present disclosure has been made to solve the above problems, and an object of the present disclosure is to provide a communication system, an in-vehicle device, and a program that improve the convenience of a user with respect to a request for a captured image.

The communication system according to a certain aspect of the present disclosure is a communication system including a vehicle and a server capable of communicating with the vehicle. The vehicle is equipped with an in-vehicle device capable of searching a route from the current location to the destination. The server includes a receiving unit that receives request information including a request for a captured image at a specific shooting location from the outside, and a transmitting unit that transmits the request information received by the receiving unit according to an opportunity from the vehicle to an in-vehicle device. .. The in-vehicle device includes an update unit that updates the route search result based on the request information when the user permits the request included in the request information from the transmission unit.

In this way, when the request information including the request for the captured image at a specific shooting location is transmitted from the server to the in-vehicle device according to the opportunity from the vehicle and the user permits the request included in the request information, the in-vehicle device The route search result is updated based on the request information. As a result, the user who has granted the request can grasp the route to the shooting location from the updated route search result, and the convenience of the user is improved.

In certain embodiments, the server further comprises a storage unit that stores a plurality of request information received by the receiving unit. The transmission unit can transmit a plurality of request information stored in the storage unit to the in-vehicle device. When the user grants a request included in at least one of the plurality of request information from the transmission unit, the update unit updates the route search result based on the at least one request information.

In this way, the user can grant the request included in at least one of the plurality of request information, and the route search result is based on at least one request information including the granted request. As it is updated, users have more choices.

In certain embodiments, the server further comprises a decision unit that determines whether or not to transmit the request information based on the route search result by the vehicle-mounted device and the specific shooting location included in the request information. The transmission unit transmits the request information to the in-vehicle device when the determination unit determines that transmission is possible.

In this way, when it is determined to transmit the request information based on the route search result by the in-vehicle device and the specific shooting location included in the request information, the request information is transmitted to the in-vehicle device. As a result, the route search result is updated in consideration of the route search result and the specific shooting location, so that the convenience of the user is further improved.

In certain embodiments, the vehicle-mounted device further comprises a display unit for displaying an image. The display unit displays an image in which the search result of the route can be specified and an image in which the request included in the request information can be specified.

In this way, the image that can identify the request is displayed together with the image that can identify the route search result, so that the user can visually grasp the request together with the route search result.

In certain embodiments, the server further comprises a management unit that manages the benefits owned by the requesting user requesting the captured image and the vehicle user, respectively. When the vehicle user satisfies the request included in the request information, the management unit adds the privilege owned by the requesting user to the privilege owned by the vehicle user.

In this way, the user can obtain the privilege owned by the requesting user by satisfying the request, so that the utilization rate of the service provided by the communication system can be increased.

An in-vehicle device according to another aspect of the present disclosure is an in-vehicle device included in a vehicle capable of communicating with a server. This in-vehicle device has a route search unit that can search for a route from the current location to the destination, an opportunity unit that gives an opportunity to the server, and an image taken at a specific shooting location included in the request information transmitted from the server according to the opportunity. It is provided with an update unit that updates the route search result based on the request information when the user permits the request.

The program according to another aspect of the present disclosure is a program executed by a computer capable of communicating with a server. This program asks the computer to search for a route from the current location to the destination, to trigger the server, and to request an image taken at a specific shooting location included in the request information sent from the server according to the trigger. When the user permits, the step of updating the search result of the route based on the request information is executed.

According to the present disclosure, it is possible to provide a communication system, an in-vehicle device, and a program that improve the convenience of a user with respect to a request for a captured image.

It is a figure for demonstrating the outline of the photographing request service provided by the communication system which concerns on this Embodiment. It is a block diagram which shows an example of the hardware configuration of the communication system which concerns on this Embodiment. It is a block diagram which shows an example of the functional structure of the communication system which concerns on this embodiment. It is a figure which shows an example of the user information table stored in the server which concerns on this embodiment. It is a figure which shows an example of the request information table stored in the server which concerns on this embodiment. It is a flowchart for demonstrating the main processing contents executed by the communication system which concerns on this Embodiment. It is a flowchart for demonstrating the main processing contents executed by the communication system which concerns on this Embodiment. It is a flowchart for demonstrating the main processing contents executed by the communication system which concerns on this Embodiment. It is a figure which shows an example of the display of the navigation device in the request side vehicle which concerns on this embodiment. It is a figure which shows an example of the display of the navigation device in the licensed vehicle which concerns on this embodiment.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. The same or corresponding parts in the drawings are designated by the same reference numerals, and the description thereof will not be repeated.

<Outline of shooting request service provided by communication system>
FIG. 1 is a diagram for explaining an outline of a photographing request service provided by the communication system 1 according to the present embodiment.

It is common to inadvertently forget to take a picture while traveling, but if the shooting request service provided by the communication system 1 according to the present embodiment is used, the user can take a picture at a specific shooting location. Images can be requested from other users. On the other hand, when the request for the captured image is permitted, another user can update the route search result based on the request information in the vehicle navigation device. Hereinafter, the photographing request service provided by the communication system 1 will be specifically described.

As shown in FIG. 1, the communication system 1 requests a vehicle (hereinafter, also referred to as a “requesting vehicle”) 10 of a user (hereinafter, also referred to as a “requesting user”) who requests a captured image, and a request for a captured image. A vehicle (hereinafter, also referred to as a “licensing vehicle”) 20 of a licensing user (hereinafter, also referred to as a “licensing user”) and a server 50 capable of communicating with these vehicles are provided.

The server 50 is communicably connected to one or more requesting vehicles 10. In the example shown in FIG. 1, the server 50 is communicably connected to each of the requesting vehicle 10a and the requesting vehicle 10b. More specifically, the server 50 is communicably connected to each of the navigation device 150a of the requesting vehicle 10a and the navigation device 150b of the requesting vehicle 10b.

Further, the server 50 is communicably connected to one or more mobile terminals 30 owned by the requesting user. In the example shown in FIG. 1, the server 50 is communicably connected to each of the mobile terminal 30a of the requesting user a and the mobile terminal 30b of the requesting user b.

On the other hand, the server 50 is communicably connected to one or more licensed vehicles 20. In the example shown in FIG. 1, the server 50 is communicably connected to the licensed vehicle 20a. More specifically, the server 50 is communicably connected to the navigation device 250a of the licensed vehicle 20a.

Further, the server 50 is communicably connected to one or more mobile terminals 40 owned by the licensed user. In the example shown in FIG. 1, the server 50 is communicably connected to the mobile terminal 40a of the licensing side user a.

In the communication system 1 having such a configuration, it is assumed that the requesting user a forgets to take a picture (for example, a landscape photograph of Lake Yamanaka) on the go and arrives at his / her home as it is (step 1a). The requesting user a uses the navigation device 150a or the mobile terminal 30a to transmit request information including a request for a captured image (for example, a landscape image of Lake Yamanaka) at a specific shooting location (for example, Lake Yamanaka) to the server 50. (Step 2a). When the server 50 receives the request information from the navigation device 150a or the mobile terminal 30a, the server 50 stores the received request information (step 3).

Similarly, suppose that the requesting user b forgets to take a picture (for example, a picture of a museum near Lake Yamanaka) on the go and arrives at his / her home as it is (step 1b). The requesting user b uses the navigation device 150b or the mobile terminal 30b to send request information including a request for a photographed image (for example, an external image of the museum) at a specific shooting location (for example, a museum near Lake Yamanaka) to the server 50. (Step 2b). When the server 50 receives the request information from the navigation device 150b or the mobile terminal 30b, the server 50 stores the received request information (step 3).

In this way, the server 50 accumulates and stores one or more request information transmitted by one or more requesting users.

In such a situation, if the licensed user a subsequently searches for a route from the current location to the destination using the navigation device 250a in the licensed vehicle 20a, the route search result is transmitted to the server 50 (step). 4).

When the server 50 receives the route search result from the licensed vehicle 20a, the server 50 collates the received route search result with the stored request information (step 5). Specifically, the server 50 determines whether or not, among the request information stored in advance, there is request information whose shooting location is on or near the route searched in the route search result. Then, when the server 50 determines that the request information matching the route search result exists, the server 50 transmits the matched request information to the licensed vehicle 20a (step 6).

When the licensed vehicle 20a receives the request information from the server 50, the navigation device 250a notifies the request information on the searched route (step 7). Specifically, in the navigation device 250a, the shooting location is indicated by a flag on the searched route. In the example shown in FIG. 1, two flags are shown on the route.

When the licensing user a grants the shooting request included in the request information (step 8), the navigation device 250a updates the route search result based on the request information (step 9). In the example shown in FIG. 1, the route search result is updated so as to stop by the selected one of the two flags (for example, the shooting location requested by the requesting user a).

After that, although not shown, the licensee user a acquires a target photographed image (for example, a landscape image of Lake Yamanaka) at the photographed place where he / she stopped by with a camera of the mobile terminal 40a or the like. The licensed user a transmits the acquired captured image data to the server 50 via the mobile terminal 40a. Alternatively, the licensed user a temporarily stores the acquired captured image data in the memory of the navigation device 250a, and transmits the acquired image data to the server 50 via the navigation device 250a.

The licensed user a is not limited to the one that acquires the captured image with the camera of the mobile terminal 40a, but uses another digital camera or video camera owned by the licensed user, or the camera of the drive recorder provided in the licensed vehicle 20a. The captured image may be acquired. In either case, the licensed user a transmits the acquired captured image data to the server 50 via the mobile terminal 40a or the navigation device 250a.

On the other hand, the server 50 transmits the captured image data received from the mobile terminal 40a or the navigation device 250a to the navigation device 150 or the mobile terminal 30 of the requesting user. In this way, the requesting user can acquire the requested captured image.

<Communication system configuration>
FIG. 2 is a block diagram showing an example of the hardware configuration of the communication system 1 according to the present embodiment. FIG. 3 is a block diagram showing an example of the functional configuration of the communication system 1 according to the present embodiment.

As shown in FIGS. 2 and 3, the communication system 1 includes a requesting vehicle 10 of a requesting user, a mobile terminal 30 of a requesting user, a server 50, a licensing vehicle 20 of a licensing user, and a licensing side. It includes a user's mobile terminal 40. The server 50 is communicably connected to each of the requesting vehicle 10, the mobile terminal 30, the licensing vehicle 20, and the mobile terminal 40. In the communication system 1, the server 50 may be communicably connected to either the requesting vehicle 10 or the mobile terminal 30 on the requesting side, and is not necessarily connected to both the requesting vehicle 10 and the mobile terminal 30. It does not need to be communicatively connected. Further, regarding the licensing side, the server 50 may be connected to at least the licensing side vehicle 20 so as to be communicable, and does not necessarily have to be connected to the mobile terminal 40 so as to be communicable.

(Configuration of requesting vehicle)
The requesting vehicle 10 is an electric vehicle using an electric motor as a traveling power source, which is driven by using the electric power supplied by the electric power supply unit 190a of the battery 190. The requesting vehicle 10 is not limited to an electric vehicle, but may be a gasoline vehicle using an internal combustion engine as a traveling power source, or a hybrid vehicle using both an electric motor and an internal combustion engine as a traveling power source.

The requesting vehicle 10 includes a communication module 103, a drive recorder 120, and a navigation device 150, and each of these configurations is communicably connected to each other via a communication line 110.

The communication module 103 is, for example, an in-vehicle DCM (Data Communication Module), and is a communication unit that enables communication between each configuration in a vehicle connected via a communication line 110 and an external device such as a server 50. It has 103a.

The drive recorder 120 is a device that captures a still image or a moving image of the inside and outside of the vehicle while the vehicle is running or stopped, and stores the captured image data. The drive recorder 120 includes a camera 121 and a memory 122. The camera 121 has a photographing unit 121a for photographing an object. The memory 122 has a storage unit 122a that stores various information such as captured image data acquired by the camera 121. The drive recorder 120 may take a picture of an abnormality in the vehicle such as in an accident, or may take a picture of the inside and outside of the vehicle at any time by the operation of the requesting user. There may be.

The navigation device 150 can search for a route from the current location to the destination. The navigation device 150 includes a display 151, a touch panel 152, a memory 153, a GPS (Global Positioning System) receiver 154, a CPU (Central Processing Unit) 155, and a short-range communication device 156.

The display 151 has a display unit 151a that displays images showing various information such as a route search result from the current location to the destination and a captured image stored in the memory 122 of the drive recorder 120. The touch panel 152 is attached to the display 151, and has a reception unit 152a that receives an input to the CPU 155 by a user's pressing operation. The memory 153 is a storage unit 153a that stores various information such as map data used for route search, captured image data stored in the memory 122 of the drive recorder 120, and a program for providing a photographing request service in the navigation device 150. Has. The GPS receiver 154 has a position information receiving unit 154a that receives the current position information of the requesting vehicle 10 based on the radio waves from the artificial satellite.

The CPU 155 executes various processes based on the information stored in the memory 153 (for example, a program for providing a shooting request service). Specifically, the CPU 155 is based on the current position information of the requesting vehicle 10 acquired by the GPS receiver 154, the destination input from the touch panel 152, and the map data stored in the memory 153. It has a route search unit 155a for searching a route from to the destination. Further, the CPU 155 has a request information acquisition unit 155b for acquiring the request information input from the touch panel 152. The acquired request information is transmitted to the server 50 via the communication module 103.

The short-range communication device 156 has a short-range communication unit 156a that enables wireless communication with a terminal located at a short distance of the navigation device 150. In the present embodiment, the short-range communication device 156 establishes wireless communication with the mobile terminal 30 of the requesting user.

The configuration of the requesting vehicle 10 shown in FIGS. 2 and 3 is an example, and the requesting vehicle 10 of course has other configurations such as a configuration for traveling.

(Composition of licensed vehicle)
The licensed vehicle 20 is an electric vehicle whose running power source is an electric motor driven by the electric power supplied by the power supply unit 290a of the battery 290, like the requesting vehicle 10 described above, but is a gasoline vehicle or a hybrid. It may be a car.

The licensed vehicle 20 includes a communication module 203, a drive recorder 220, and a navigation device 250, and each of these configurations is communicably connected to each other via a communication line 210.

The communication module 203 is, for example, an in-vehicle DCM, and has a communication unit 203a that enables communication between each configuration in the vehicle connected via the communication line 210 and an external device such as a server 50.

The drive recorder 220 has the same configuration and function as the drive recorder 120 of the requesting vehicle 10 described above, and includes a camera 221 having a photographing unit 221a and a memory 222 having a storage unit 222a.

The navigation device 250 can search for a route from the current location to the destination, similarly to the navigation device 150 of the requesting vehicle 10 described above. The navigation device 250 is an embodiment of the "vehicle-mounted device". The navigation device 250 includes a display 251, a touch panel 252, a memory 253, a GPS receiver 254, a CPU 255, and a short-range communication device 256.

The display 251 has a display unit 251a that displays images showing various information such as a route search result from the current location to the destination and a captured image stored in the memory 222 of the drive recorder 220. The touch panel 252 is attached to the display 251 and has a reception unit 252a that receives an input to the CPU 255 by a user's pressing operation. In the shooting request service, the licensee user can grant the request included in the request information by pressing the touch panel 252. The memory 253a stores various information such as map data used for route search, captured image data stored in the memory 222 of the drive recorder 220, and a program for providing a photographing request service in the navigation device 250. Has. The GPS receiver 254 has a position information receiving unit 254a that receives the current position information of the licensed vehicle 20 based on the radio waves from the artificial satellite.

The CPU 255 executes various processes based on the information stored in the memory 253 (for example, a program for providing a shooting request service). Specifically, the CPU 255 is based on the current position information of the licensed vehicle 20 acquired by the GPS receiver 254, the destination input from the touch panel 252, and the map data stored in the memory 253. It has a route search unit 255a for searching a route from to the destination. Further, the CPU 255 has a trigger unit 255b that gives a trigger for transmitting the request information from the request side vehicle 10 to the server 50. Specifically, the trigger unit 255b of the CPU 255 transmits the route search result obtained by the route search unit 255a to the server 50 via the communication module 203, thereby giving the server 50 an opportunity to transmit the request information. give. As a result, the server 50 that has received the route search result transmits the request information that matches the route search result to the navigation device 250. Further, the CPU 255 has an update unit 255c that updates the search result of the route based on the request information acquired from the request side vehicle 10 via the server 50.

The short-range communication device 256 has a short-range communication unit 256a that enables wireless communication with a terminal located at a short distance of the navigation device 250. In the present embodiment, the short-range communication device 256 establishes wireless communication with the mobile terminal 40 of the licensed user.

The configuration of the licensed vehicle 20 shown in FIGS. 2 and 3 is an example, and the licensed vehicle 20 is of course provided with other configurations such as a configuration for traveling.

(Configuration of mobile terminal)
The mobile terminal 30 includes a communication interface 303, a camera 306, a memory 304, a display 301, a touch panel 302, and a CPU 305, and each of these configurations is communicably connected to each other via a communication line 310.

The communication interface 303 includes a communication unit 303a that enables communication between each configuration in the mobile terminal connected via the communication line 310 and an external device such as the navigation device 150 of the server 50 and the requesting vehicle 10. Have. The camera 306 has a photographing unit 306a for photographing an object. The memory 304 has a storage unit 304a that stores various information such as captured image data acquired by the camera 306 and a program for executing a photographing request service on the mobile terminal 30.

The display 301 has a display unit 301a that displays an image showing various information such as a captured image stored in the memory 304. The touch panel 302 is attached to the display 301, and has a reception unit 302a that receives an input to the CPU 305 by a user's pressing operation.

The CPU 305 executes various processes based on the information stored in the memory 304 (for example, a program for providing a shooting request service). Specifically, the CPU 305 has a request information acquisition unit 305a that acquires the request information input from the touch panel 302. The acquired request information is transmitted to the server 50 via the communication interface 303.

The configuration of the mobile terminal 30 shown in FIGS. 2 and 3 is an example, and the mobile terminal 30 of course has other configurations. Further, since the mobile terminal 40 has basically the same configuration as the mobile terminal 30 described above, a specific description thereof will be omitted.

(Server configuration)
The server 50 includes a communication interface 503, a memory 502, and a CPU 501, and each of these configurations is communicably connected to each other via a communication line 510.

The communication interface 503 enables communication between each configuration in the server connected via the communication line 510 and the requesting side vehicle 10, the mobile terminal 30, the licensed side vehicle 20, the mobile terminal 40, and the like. It has a part 503a. The communication unit 503a of the communication interface 503 is an embodiment of the "reception unit" and the "transmission unit".

The memory 502 stores various information such as user information included in the user information table of FIG. 4, which will be described later, request information included in the request information table of FIG. 5, and a program for executing a shooting request service on the server 50. It has a storage unit 502a to be used. The storage unit 502a of the memory 502 is an embodiment of the "management unit".

The CPU 501 executes various processes based on the information stored in the memory 502 (for example, a program for providing a shooting request service). Specifically, the CPU 501 collates the route search result received from the licensed vehicle 20 with the request information stored in the memory 502, and determines whether or not there is request information that matches the route search result. It has a part 501a. The request information that matches the route search result is transmitted to the licensed vehicle 20 via the communication interface 503. That is, the determination unit 501a determines whether or not to transmit the request information based on the route search result by the navigation device 250 of the licensed vehicle 20 and the specific shooting location included in the request information stored in the memory 502. Has the function of

<User information table>
A user who uses the photographing request service provided by the communication system 1 is supposed to register predetermined information in the server 50. The registered user information is stored in the user information table stored in the memory 502. FIG. 4 is a diagram showing an example of a user information table stored in the server 50 according to the present embodiment.

As shown in FIG. 4, in the user information table, a "vehicle ID" for identifying a vehicle owned by the user and a mobile phone owned by the user are associated with the "user ID" for identifying the user. Information indicating a "terminal ID" for identifying the terminal, a "email address" owned by the user, and a "point" owned by the user is stored. The "vehicle ID" may be an identification ID associated with the vehicle itself, or may be an identification ID associated with the navigation device included in the vehicle.

Here, in the present embodiment, the point system is introduced in the shooting request service, and the requesting user can request the shooting image from the licensing side user by consuming the points. On the other hand, the licensing side user can acquire points owned by the requesting side user by acquiring the requested photographed image and providing it to the requesting side user. The points are not limited to those used for requesting a photographed image, and may be used for purchasing a product or receiving provision of other services. The point is an embodiment of the "privilege".

<Request information table>
The server 50 stores the request information received from the navigation device 150 or the mobile terminal 30 of the requesting vehicle 10 in the request information table stored in the memory 502. FIG. 5 is a diagram showing an example of a request information table stored in the server 50 according to the present embodiment.

As shown in FIG. 5, in the request information table, the "user ID", the current "status", and the "shooting location" of the requesting user are associated with the "task ID" for identifying the request information. And "request information" including detailed information of "photographed image", "thank you point" for the licensed user, and information indicating "request date and time" are stored.

In the shooting request service, since one user can make a plurality of requests, the same user ID may be associated with a plurality of task IDs. For example, the same "user ID" "001abc" is associated with the "task ID" "001" and "005".

As the type of "status", "searching for a licensee", "licensed", and "completed" are stored. If the licensee has not been found since the request for the captured image was made, "Searching for the licensee" is stored as the "status". If the licensee has been found but the captured image has not yet been provided to the requesting user, "licensed" is stored as the "status". If the captured image has already been provided to the requesting user, "completed" is stored as the "status".

As the "shooting location" included in the "request information", information on the shooting location requested by the requesting user is stored. As the "photographed image" included in the "request information", information on the details of the photographed image (for example, the composition of the photograph and the object to be photographed) requested by the requesting user is stored.

"Thank you points" are points that are added to the points owned by the licensed user among the points owned by the requesting user as a thank-you when the licensed user provides the captured image to the requesting user. Information is stored. In the present embodiment, the requesting user can determine the thank-you point, but the present invention is not limited to this, and the thank-you point may be predetermined.

<Main processing contents executed by the communication system>
6 to 8 are flowcharts for explaining the main processing contents executed by the communication system 1. Each step shown in the flowcharts shown in FIGS. 6 to 8 is realized by software processing by each CPU, but may be realized by hardware (electric circuit) manufactured in the CPU. In the following, each step is simply abbreviated as "S".

(Request stage of captured image)
First, with reference to FIG. 6, the processing flow at the stage where the requesting user requests the captured image from the server 50 will be described. At this stage, the requesting user can request the captured image from the server 50 by using either the navigation device 150 or the mobile terminal 30 of the requesting vehicle 10. Regarding the processing flow shown in FIG. 6, the CPU 155 of the navigation device 150 or the CPU 305 of the mobile terminal 30 executes the processing flow on the request side, and the CPU 501 of the server 50 executes the processing flow on the server 50 side. In this example, an example in which the navigation device 150 of the requesting vehicle 10 transmits the request information to the server 50 will be described.

As shown in FIG. 6, the navigation device 150 determines whether or not the request for the captured image has been accepted (S110).

Here, FIG. 9 is a diagram showing an example of the display 151 of the navigation device 150 in the requesting vehicle 10 according to the present embodiment. As shown in FIG. 9A, the main menu of the navigation device 150 includes a destination icon 161 operated to search for a route from the current location to the destination, and listening to music or watching a video. To acquire various information such as an AV icon 162 operated for the purpose, a setting icon 163 operated for making various settings, a shooting request icon 164 operated for making a shooting request, and traffic jam information. The information icon 165 to be operated is included. The requesting user can use the shooting request service by selecting the shooting request icon 164. The shooting request icon 164 may be provided from the initial shipment of the navigation device 150, may be added by user setting, or may be added by updating the software of the navigation device 150.

Returning to FIG. 6, in the process of S110 described above, the navigation device 150 determines whether or not the shooting request icon 164 is selected. The navigation device 150 repeats this processing flow again when the request for the captured image is not accepted (NO in S110), that is, when the capture request icon 164 is not selected.

On the other hand, when the navigation device 150 receives the request for the captured image (YES in S110), that is, when the shooting request icon 164 is selected, the navigation device 150 determines whether or not the request information has been acquired (S120). The required information includes at least the “photographed location” and the “photographed image” shown in FIG.

Here, as shown in FIG. 9B, when the shooting request icon 164 is selected, the screen shifts to the shooting request service menu. In the shooting request service menu, there are a shooting location input field 171 for inputting "shooting location" as request information, a shooting image input field 172 for inputting "shooting image" as request information, and a "thank you point". A thank-you point input field 173 for input is included. The requesting user selects a desired character or number from the characters or numbers arranged in the character selection field 174 by using the cursor 175 to select the shooting location input field 171, the shooting image input field 172, and thank you. Information can be input in each of the point input fields 173. The requesting user may select the delete icon 176 if he / she wants to delete characters and numbers, and may select the return icon 177 if he / she wants to return to the main menu. In addition, the requesting user can confirm the input request information and thank-you points by selecting the confirmation icon 178.

Returning to FIG. 6, in the process of S120 described above, the navigation device 150 determines whether or not the request information and the thank-you point have been determined. When the request information has not been acquired (NO in S120), that is, when the request information and the thank-you point have not been determined, the navigation device 150 repeats the process of S120 until the request information is acquired.

On the other hand, the navigation device 150 transmits the acquired request information to the server 50 when the request information is acquired (YES in S120), that is, when the request information and the thank-you point are confirmed (S130). The navigation device 150 transmits the vehicle ID to the server 50 in the process of S130. When the requesting user makes a shooting request using the mobile terminal 30, the mobile terminal 30 transmits the terminal ID to the server 50 in the process of S130. After that, the navigation device 150 repeats this processing flow again.

Here, as shown in FIG. 9C, when the navigation device 150 transmits the request information to the server 50, the character image of "Request for shooting. Please wait for a while." Is displayed on the display 151.

Returning to FIG. 6, the server 50 determines whether or not the request information is received from the navigation device 150 together with the vehicle ID (S510). When the server 50 has not received the request information together with the vehicle ID from the navigation device 150 (NO in S510), the server 50 repeats this processing flow again.

On the other hand, when the server 50 receives the request information together with the vehicle ID from the navigation device 150 (YES in S510), the server 50 stores the received request information in the request information table shown in FIG. 5 (S520). At this time, the server 50 assigns a new task ID to the request information and associates the vehicle ID and the user ID of the requesting user with the request information. Then, the server 50 makes "searching for a licensee" correspond to the request information as the "status". After that, the server 50 repeats this processing flow again.

In this way, the requesting user can transmit the request information to the server 50 using the navigation device 150. On the other hand, the server 50 can store the request information received from the navigation device 150. The server 50 can acquire and store request information from the same navigation device 150 multiple times, and further, by the same processing flow, the navigation device 150 and the mobile terminal 30 of another requesting vehicle. Request information can also be acquired and stored from. As a result, a plurality of request information is accumulated in the request information table. In addition, although FIG. 9 shows an example of the display 151 of the navigation device 150, similarly, the icon for selecting the shooting request, the request information, and the thank-you point are input to the display 301 of the mobile terminal 30. An input field for inputting is displayed.

(Shooting request permission stage)
Next, with reference to FIG. 7, the processing flow at the stage where the licensing user grants the shooting request will be described. Regarding the processing flow shown in FIG. 7, the CPU 501 of the server 50 executes the processing flow on the server 50 side, and the CPU 255 of the navigation device 250 executes the processing flow on the licensing side.

As shown in FIG. 7, the navigation device 250 determines whether or not a route search has been received (S210). Specifically, the navigation device 250 determines whether or not the licensee user has requested a route search from the current location to the destination. When the navigation device 250 does not receive the route search (NO in S210), the navigation device 250 repeats this processing flow again.

On the other hand, the navigation device 250 searches for a route (S220) when the route search is accepted (YES in S210). After that, the navigation device 250 transmits the route search result to the server 50 (S230). With such an opportunity, the request information can be transmitted to the server 50.

On the other hand, the server 50 determines whether or not the route search result has been received (S560). If the server 50 has not received the route search result (NO in S560), the server 50 repeats this processing flow again.

On the other hand, when the server 50 receives the route search result (YES in S560), the server 50 collates the received route search result with the request information stored in the request information table (S570), and requests to match the route search result. It is determined whether or not there is information (S580). Specifically, the server 50 determines whether or not, among the request information stored in advance, there is request information whose shooting location is on or near the route searched in the route search result. If there is no request information that matches the route search result (NO in S580), the server 50 repeats this processing flow again.

On the other hand, when the server 50 has request information matching with the route search result (YES in S580), the server 50 transmits the matched request information together with the task ID to the navigation device 250 (S590).

On the other hand, the navigation device 250 determines whether or not the request information has been received within a predetermined time (S240). If the navigation device 250 does not receive the request information within the time (NO in S240), the navigation device 250 repeats this processing flow again.

On the other hand, when the navigation device 250 receives the request information within the time (YES in S240), the navigation device 250 notifies the display 251 of the request information (S250). Specifically, the navigation device 250 identifies position information (for example, longitude and latitude) from the address of the shooting location included in the request information, and based on the specified position information, displays an image indicating the shooting location on the route. indicate.

Here, FIG. 10 is a diagram showing an example of the display 251 of the navigation device 250 in the licensed vehicle 20 according to the present embodiment. As shown in FIG. 10A, the route search result acquired in the process of S220 of FIG. 9 is displayed on the display 251. The display of the route search result includes a route image 260 showing the route to the destination and a distance image 261 showing the distance to the destination on the map. When the request information is notified to the display 251 by the process of S250 of FIG. 9, the display shifts to the display as shown in FIG. 10 (b).

FIG. 10B shows an example in which the request information of the task ID “005” and the task ID “006” stored in the request information table of FIG. 5 is matched with the route search result. For example, the request information of the task ID "005" and the task ID "006" includes the vicinity of Lake Yamanaka in Yamanashi Prefecture as the shooting location. If the licensed user's current location is near Lake Yamanaka, the request information will match the route search result.

As shown in FIG. 10B, when the request information is notified, the route search result is displayed on the map together with the route image 260 and the flag 264 indicating the shooting location corresponding to the task ID “005”. , The flag 263 indicating the shooting location corresponding to the task ID “005” is included. Further, a detail column 265 for viewing the details of the request information is displayed at the right end of the display 251. In the detail column 265, for each request information of the task ID "005" and the task ID "006", a point image 266 showing a thank-you point, a detail icon 267 for viewing the details of the request information, and a request are granted. Includes a license icon 268 that is manipulated to do so. The navigation device 250 may display the task ID on the display 251 together with the request information.

Returning to FIG. 7, the navigation device 250 determines whether or not the licensing user has granted the request (S260). That is, the navigation device 250 determines whether or not the permission icon 268 is selected for the request information of any of the task ID "005" and the task ID "006". When the licensee user does not grant the request (NO in S260), the navigation device 250 repeats this processing flow again.

On the other hand, when the licensed user grants the request (YES in S260), the navigation device 250 transmits the licensed information indicating that the licensed user has granted the request to the server 50 (S270). For example, as shown in FIG. 10C, when the licensing user grants the request corresponding to the task ID “005”, a yen mark is displayed on the flag 264 indicating the shooting location corresponding to the task ID “005”. It is indicated to the licensing user that the permission has been granted by some effect such as blinking, blinking, or changing the color.

Returning to FIG. 7, the server 50 determines whether or not the permission information has been received within a predetermined time (S600). If the server 50 does not receive the permission information within the time (NO in S600), the server 50 repeats this processing flow again.

On the other hand, when the server 50 receives the license information within the time (YES in S600), the server 50 changes the "status" corresponding to the licensed request information to "licensed" in the request information storage table (S610). After that, the server 50 transmits the update permission information indicating that the update of the route search is permitted in the navigation device 250 of the licensed user who has granted the request to the licensed user (S620), and repeats this processing flow again.

On the other hand, the navigation device 250 determines whether or not the update permission information has been received within a predetermined time (S280). If the navigation device 250 does not receive the update permission information within the time (NO in S280), the navigation device 250 repeats this processing flow again.

On the other hand, when the navigation device 250 receives the update permission information within the time (YES in S280), the navigation device 250 updates the route search result displayed on the display 251 (S290). For example, as shown in FIG. 10D, the flag 263 indicating the shooting location corresponding to the task ID “006” disappears, while the flag 264 indicating the shooting location corresponding to the task ID “005” remains. Then, on the map, the route search result is updated so that the route image 260 stops at the flag 264 and then returns to the route to the original destination. Further, in addition to the distance image 261 showing the distance to the destination, the distance image 262 showing the distance to the shooting place to stop in the middle is displayed on the display 251.

If the licensing user also grants a request corresponding to the task ID "006" in addition to the request corresponding to the task ID "005", the root image 260 stops at both the flag 263 and the flag 264 and then the original. The route search results are updated to return to the route to the destination. Returning to FIG. 7, the server 50 repeats this processing flow again after the processing of S290.

(Acquisition stage of captured image)
Next, the processing flow at the stage where the requesting user acquires the captured image from the licensing user will be described with reference to FIG. At this stage, the licensed user can transmit the captured image to the server 50 by using either the navigation device 250 or the mobile terminal 40 of the licensed vehicle 20. Further, at this stage, the requesting user can receive the captured image from the server 50 by using either the navigation device 150 or the mobile terminal 30 of the requesting vehicle 10. Regarding the processing flow shown in FIG. 8, the CPU 255 of the navigation device 250 or the CPU of the mobile terminal 40 (not shown) executes the processing flow on the licensing side, and the CPU 501 of the server 50 executes the processing flow on the server 50 side. On the request side, the CPU 155 of the navigation device 150 or the CPU 305 of the mobile terminal 30 executes the execution. In this example, an example in which a captured image is transmitted from the mobile terminal 40 of the licensing side user to the mobile terminal 30 of the requesting side user will be described.

As shown in FIG. 8, the mobile terminal 40 of the licensing side user determines whether or not the transmission of the captured image data has been received (S2010). At this point, the mobile terminal 40 has already acquired the captured image from the camera of the mobile terminal 40, the camera 221 of the drive recorder 220 of the licensed vehicle 20, and the like.

When the mobile terminal 40 does not receive the transmission of the captured image data (NO in S2010), the mobile terminal 40 repeats this processing flow again. On the other hand, when the mobile terminal 40 receives the reception of the transmission of the captured image data (YES in S2010), the mobile terminal 40 transmits the captured image data to the server 50 together with the task ID (S2020). The task ID may be input to the mobile terminal 40 by the licensing user, or may be acquired by the mobile terminal 40 from the navigation device 250 using short-range communication.

On the other hand, the server 50 determines whether or not the captured image data has been received (S5010). When the server 50 has not received the captured image data (NO in S5010), the server 50 repeats this processing flow again.

On the other hand, when the server 50 receives the captured image data (YES in S5010), the server 50 transmits the captured image data together with the task ID to the mobile terminal 30 of the requesting user (S5020). Specifically, the server 50 identifies the user ID associated with the task ID based on the request information table. Then, the server 50 transmits the captured image data to the e-mail address associated with the specified user ID based on the user information table. If the navigation device 150 has an e-mail address, the server 50 may send the captured image data to the e-mail address of the navigation device 150 associated with the user ID.

On the other hand, the mobile terminal 30 of the requesting user determines whether or not the captured image data has been received (S1010). When the mobile terminal 30 has not received the captured image data (NO in S1010), the mobile terminal 30 repeats this processing flow again.

On the other hand, when the mobile terminal 30 receives the captured image data (YES in S1010), the mobile terminal 30 transmits the acquired information indicating that the captured image data has been received together with the task ID to the server 50 (S1020), and stores the captured image data in the memory 304. It is stored in (S1030).

On the other hand, the server 50 determines whether or not the acquired information has been received (S5030). When the server 50 has not received the acquired information (NO in S5030), the server 50 repeats the process of S5030.

On the other hand, when the server 50 receives the acquired information (YES in S5030), the server 50 changes the "status" corresponding to the task ID to "completed" in the request information storage table (S5040). After that, the server 50 moves and stores the points corresponding to the task ID for the thank-you points from the points of the requesting user to the points of the licensing side user (S5050).

After that, the server 50 transmits the point information indicating the moved point to the mobile terminal 30 of the requesting user and the mobile terminal 40 of the licensing side user (S5060), and repeats this processing flow again.

On the other hand, the mobile terminal 30 of the requesting user determines whether or not the point information has been received within a predetermined time (S1040). If the mobile terminal 30 does not receive the point information within the time (NO in S1040), the mobile terminal 30 repeats this processing flow again.

On the other hand, when the mobile terminal 30 receives the point information within the time (YES in S1040), the mobile terminal 30 displays the points currently owned by the requesting user on the display 301 based on the point information (S1050), and repeats this processing flow. repeat.

Similarly, the mobile terminal 40 of the licensing side user determines whether or not the point information has been received within a predetermined time (S2030). If the mobile terminal 40 does not receive the point information within the time (NO in S2030), the mobile terminal 40 repeats this processing flow again.

On the other hand, when the mobile terminal 40 receives the point information within the time (YES in S2030), the mobile terminal 40 displays the points currently owned by the licensed user on the display based on the point information (S2040), and repeats this processing flow again. ..

<About action and effect>
As described above, according to the communication system 1 according to the present embodiment, the request information including the request for the photographed image at the specific photographing location is transmitted from the server 50 to the navigation device 250 according to the opportunity from the licensed vehicle 20. Then, when the licensing user grants the request included in the request information, the navigation device 250 updates the route search result based on the request information. As a result, the licensed user who has granted the request can grasp the route to the shooting location from the updated route search result. On the other hand, the requesting user can acquire the captured image acquired by the licensing user via the navigation device 150 or the mobile terminal 30. This improves user convenience with respect to the request for captured images.

The licensing user can grant the request corresponding to at least one task ID among the plurality of task IDs, and the route search result is updated based on at least one request information including the granted request. Therefore, the options of the licensed user are expanded.

Based on the route search result by the navigation device 250 and the specific shooting location included in the request information, the request information matching the route search result is transmitted to the navigation device 250. As a result, the route search result is updated in consideration of the route search result and the specific shooting location, so that the convenience of the licensee user is further improved.

In the navigation device 250, the route image 260 that can specify the route search result, the flags 263 and 264 that can specify the request, and the details of the request information are displayed, so that the licensee user visually requests the route along with the route search result. Can be grasped.

By providing the photographed image to the requesting user, the licensing side user can obtain points owned by the requesting user, so that the utilization rate of the photographing request service can be increased.

<Modification example>
In the present embodiment, in the process of S250 of FIG. 7, when the navigation device 250 notifies the request information via the display 251, the location information (for example, the location information (for example) from the address of the shooting location included in the request information received from the server 50). , Longitude and latitude) were specified by the navigation device 250. However, the server 50 may specify the location information from the address of the shooting location included in the request information, and the server 50 may transmit the location information to the navigation device 250.

In the present embodiment, in the licensed vehicle 20, matching is performed only when there is request information in which the shooting location is on or near the route searched in the route search result among the request information stored in advance. The request information was notified. However, even if there is no request information for the shooting location on or near the route searched in the route search results (that is, the shooting location is far away from the route), the request information is notified. You may.

In the present embodiment, when the route search result and the request information match, the server 50 always transmits the request information to the navigation device 250 of the licensed vehicle 20. However, the server 50 is configured so that the licensee user can select whether or not to notify the request information in the navigation device 250, and even when the request information is notified, the shooting location to be notified can be selected. May send request information according to its selection.

In the present embodiment, the server 50 transmits the request information matching with the route search result to the navigation device 250 when the route search result is received from the navigation device 250. However, if the navigation device 250 has a configuration in which request information can be requested (for example, display of a switch or an operable switch icon), the licensee user requests the server 50 by operating the configuration. It may be possible to give an opportunity to transmit information. In this way, the licensed user can obtain the request information by a predetermined operation without performing a route search on the navigation device 250.

In the present embodiment, points are given to the licensed user as a privilege in the shooting request service, but of course, the licensed user volunteers to request the requesting user without introducing the point system. It may be the one that satisfies. Further, the privilege is not limited to points, and may be a virtual currency that can be used in a virtual world such as a game, or may be electronic money.

The above-mentioned modification may be carried out in whole or in combination. The embodiments disclosed this time should be considered to be exemplary in all respects and not restrictive. The scope of the present disclosure is shown by the scope of claims rather than the description of the embodiment described above, and is intended to include all modifications within the meaning and scope equivalent to the scope of claims.

1 communication system, 10 requesting vehicle, 20 licensed vehicle, 30,40 mobile terminal, 50 server, 103,203 communication module, 110,210,310,510 communication line, 120,220 drive recorder, 121,221,306 Camera, 122,153,222,253,304,502 memory, 150,250 navigation device, 151,251,301 display, 152,252,302 touch panel, 154,254 GPS receiver, 156,256 short-range communication system, 190,290 battery, 303,503 communication interface.

Claims (7)

A communication system including a vehicle and a server capable of communicating with the vehicle.
The vehicle is equipped with an in-vehicle device capable of searching a route from the current location to the destination.
The server
A receiver that receives request information from the outside, including requests for images taken at a specific shooting location,
A transmission unit that transmits the request information received by the reception unit to the in-vehicle device according to an opportunity from the vehicle is provided.
The in-vehicle device is a communication system including an update unit that updates a search result of the route based on the request information when the user permits a request included in the request information from the transmission unit. The server further includes a storage unit that stores a plurality of the request information received by the reception unit.
The transmission unit can transmit a plurality of the request information stored in the storage unit to the vehicle-mounted device.
When the user grants a request included in at least one of the plurality of request information from the transmission unit, the update unit obtains the search result of the route based on the at least one request information. The communication system according to claim 1, which is updated. The server further includes a determination unit that determines whether or not to transmit the request information based on the search result of the route by the vehicle-mounted device and the specific shooting location included in the request information.
The communication system according to claim 1 or 2, wherein the transmission unit transmits the request information to the in-vehicle device when the determination unit determines that transmission is possible. The in-vehicle device further includes a display unit for displaying an image.
The communication system according to any one of claims 1 to 3, wherein the display unit displays an image in which the search result of the route can be specified and an image in which the request included in the request information can be specified. The server further includes a management unit that manages the benefits owned by the requesting user who requests the captured image and the user of the vehicle.
Claims 1 to claim that the management unit adds a privilege owned by the requesting user to a privilege owned by the user of the vehicle when the user of the vehicle satisfies the request included in the request information. Item 4. The communication system according to any one of items 4. An in-vehicle device provided in a vehicle capable of communicating with a server.
A route search unit that can search for routes from your current location to your destination,
The trigger part that gives the trigger to the server and
When the user permits a request for a photographed image at a specific shooting location included in the request information transmitted from the server in accordance with the above-mentioned opportunity, an update unit that updates the search result of the route based on the request information is provided. In-vehicle device to be equipped. A program run by a computer that can communicate with a server
On the computer
Steps to find a route from your current location to your destination,
The steps that give an opportunity to the server and
When the user permits a request for a photographed image at a specific shooting location included in the request information transmitted from the server in accordance with the above-mentioned opportunity, a step of updating the search result of the route based on the request information is executed. Let the program.

Images