JP2019078649A - Communication system, onboard device and program - Google Patents

Abstract

To provide a communication system, an onboard device and a program for improving a user's convenience regarding a request for captured images.SOLUTION: Provided is a communication system 1 equipped with an approval-side vehicle 20 and a server 50 capable of communicating with the approval-side vehicle 20, wherein the approval-side vehicle 20 includes a navigation device 250 capable of searching for a route from the present location to a destination. The server 50 receives, from the outside, request information that includes a request for a captured image at a specific imaging site, and transmits the request information received by a communication interface to the navigation device 250 in accordance with a motive from the approval-side vehicle 20. The navigation device 250 updates the result of route search on the basis of the request information when a user approves the request included in the request information from the communication interface.SELECTED DRAWING: Figure 1

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 included in the vehicle capable of communicating with the server, and a program executed by a computer capable of communicating with the server.

  2. Description of the Related Art Conventionally, a vehicle provided with a navigation device capable of searching for a route from a current location to a destination is known. For example, Japanese Patent Application Laid-Open No. 2016-90515 (Patent Document 1) has a function of guiding a route from the current location to a destination, and displays an image showing the guidance route and an image showing the distance to the destination on the display. Discloses a vehicle provided with a navigation device.

JP, 2016-90515, A

  By the way, it is common for people to forget to take a picture accidentally on the go, such as a travel destination. In such a case, a system that allows someone to take a picture they missed is desired. For example, if it is possible to construct a system that allows other users to smoothly take photos that they forgot to take using the route guidance of the navigation device provided in the vehicle disclosed in Patent Document 1, user convenience Improve.

  The present disclosure has been made to solve the above-described problems, and an object thereof is to provide a communication system, an on-vehicle apparatus, and a program that improve the convenience of the user regarding the request for a captured image.

  A communication system according to an aspect of the present disclosure is a communication system including a vehicle and a server capable of communicating with the vehicle. The vehicle includes an on-vehicle device capable of searching for a route from a current location to a 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 to the in-vehicle device according to a trigger from the vehicle. . The in-vehicle apparatus includes an updating unit that updates the search result of the route based on the request information when the user accepts the request included in the request information from the transmitting unit.

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

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

  In this way, the user can grant the request included in at least one of the plurality of pieces of request information, and the search result of the route is based on the at least one request information including the granted request. Because it is updated, the options of the user are expanded.

  In one embodiment, 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 in-vehicle device and the specific imaging location included in the request information. The transmission unit transmits the request information to the in-vehicle apparatus when it is determined by the determination unit that the transmission is present.

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

  In one embodiment, the in-vehicle device further includes a display unit that displays an image. The display unit displays an image that can specify the request included in the request information, as well as an image that can specify the search result of the route.

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

  In one embodiment, the server further includes a management unit that manages benefits owned by the requester user who requests the photographed image and the user of the vehicle. When the user of the vehicle satisfies the request included in the request information, the management unit adds the benefit owned by the requesting user to the benefit owned by the user of the vehicle.

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

  An on-vehicle apparatus according to another aspect of the present disclosure is an on-vehicle apparatus provided in a vehicle that can communicate with a server. The in-vehicle apparatus includes a route search unit capable of searching for a route from the current location to a destination, a trigger unit that triggers the server, and a captured image at a specific shooting location included in the request information transmitted from the server according to the trigger. And an update unit configured to update the search result of the route based on the request information when the user accepts the request.

  A program according to another aspect of the present disclosure is a program executed by a computer that can communicate with a server. This program searches the computer for the route from the current location to the destination, the step for triggering the server, and the request for a photographed image at a specific shooting location included in the request information transmitted from the server according to the trigger. And (c) updating the route search result based on the request information.

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

It is a figure for demonstrating the outline | summary of the imaging | photography request | requirement service which the communication system which concerns on this Embodiment provides. It is a block diagram which shows an example of the hardware constitutions of the communication system which concerns on this Embodiment. It is a block diagram which shows an example of a function structure of the communication system which concerns on this Embodiment. It is a figure which shows an example of the user information table which the server which concerns on this Embodiment memorize | stores. It is a figure which shows an example of the request | requirement information table which the server which concerns on this Embodiment memorize | stores. It is a flowchart for demonstrating the main processing content which the communication system which concerns on this Embodiment performs. It is a flowchart for demonstrating the main processing content which the communication system which concerns on this Embodiment performs. It is a flowchart for demonstrating the main processing content which the communication system which concerns on this Embodiment performs. It is a figure which shows an example of a display of a display about the navigation apparatus in the request side vehicle which concerns on this Embodiment. It is a figure which shows an example of a display of a display about the navigation apparatus in the license side vehicle which concerns on this Embodiment.

  Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding portions are denoted by the same reference characters and description thereof will not be repeated.

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

  It is often the case that a user accidentally forgets to take a picture on the way, such as a travel destination, but using the picture taking request service provided by the communication system 1 according to the present embodiment allows the user to take pictures at a specific picture taking place. Images can be requested from other users. On the other hand, when the other user accepts the request for the photographed image, the navigation device of the vehicle can update the route search result based on the request information. Hereinafter, the photographing request service provided by the communication system 1 will be specifically described.

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

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

  Furthermore, the server 50 is communicably connected to one or more portable terminals 30 owned by the requesting user. In the example illustrated in FIG. 1, the server 50 is communicably connected to the portable terminal 30 a of the request user a and the portable terminal 30 b of the request user b.

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

  Furthermore, the server 50 is communicably connected to one or more portable terminals 40 owned by the licensee user. In the example shown in FIG. 1, the server 50 is communicably connected to the portable terminal 40a of the granting side user a.

  In the communication system 1 having such a configuration, it is assumed that the request-side user a forgot to take a picture (for example, a landscape picture of Lake Yamanaka) on the way out and arrived at home as it is (step 1a). The requester user a transmits request information including a request for a photographed image (for example, a scenic image of Lake Yamanaka) to a server 50 using the navigation device 150a or the portable terminal 30a. (Step 2a). When receiving the request information from the navigation device 150a or the mobile terminal 30a, the server 50 stores the received request information (step 3).

  Similarly, it is assumed that the request side user b forgets to take a picture (for example, a picture of an art museum near Lake Yamanaka) on the way out and arrives at home as it is (step 1 b). The request user b uses the navigation device 150b or the portable terminal 30b to request information including a request for a photographed image (for example, an appearance image of a museum) at a specific photographing location (for example, a museum near Lake Yamanaka). To (step 2b). When the server 50 receives the request information from the navigation device 150 b or the portable terminal 30 b, the server 50 stores the received request information (step 3).

  Thus, the server 50 accumulates and stores one or more request information sent by one or more requesters.

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

  When receiving the route search result from the granting side vehicle 20a, the server 50 collates the received route search result with the stored request information (step 5). Specifically, the server 50 determines, among the request information stored in advance, whether or not the request information whose route is on or near the route searched by the route search result exists. Then, when it is determined that the request information matching the route search result is present, the server 50 transmits the matching request information to the granting side vehicle 20a (step 6).

  In the granting side vehicle 20a, when receiving 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 granting side user a grants the photographing 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 search result of the route is updated so as to drop in the flag of the selected one of the two flags (for example, the photographing place requested by the requesting user a).

  Then, although illustration is omitted, the permission user a acquires a target photographed image (for example, a landscape image of Lake Yamanaka) at the photographing site where the user stopped by the camera of the portable terminal 40a or the like. The granting side user a transmits the acquired photographed image data to the server 50 via the portable terminal 40 a. Alternatively, the granting side user a temporarily stores the acquired photographed image data in the memory of the navigation device 250a, and transmits it to the server 50 via the navigation device 250a.

  The license user a is not limited to one for acquiring a captured image with the camera of the portable terminal 40a, and may use another digital camera or video camera owned by the user or a camera of a drive recorder provided in the license vehicle 20a. A photographed image may be acquired. In any case, the granting side user a transmits the acquired photographed image data to the server 50 via the portable terminal 40a or the navigation device 250a.

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

<Configuration of communication system>
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 a 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 request side vehicle 10 of a request side user, a portable terminal 30 of a request side user, a server 50, a permission side vehicle 20 of a permission side user, and a permission side. And a portable terminal 40 of the user. The server 50 is communicably connected to each of the request side vehicle 10, the portable terminal 30, the permission side vehicle 20, and the portable terminal 40. In the communication system 1, the server 50 may be connected communicably to either the request vehicle 10 or the portable terminal 30 on the request side, and the communication system 1 may not necessarily be connected to both the request vehicle 10 and the portable terminal 30. It does not need to be communicably connected. In addition, with regard to the granting side, the server 50 only needs to be communicably connected to at least the licensing side vehicle 20, and does not necessarily have to be communicably connected to the portable terminal 40.

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

  The request-side vehicle 10 includes a communication module 103, a drive recorder 120, and a navigation device 150, and these components are communicably connected to each other via a communication line 110.

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

  The drive recorder 120 is a device that captures an image of the inside and outside of the vehicle as a still image or a moving image while the vehicle is traveling or stops, and stores the captured image data. Drive recorder 120 includes a camera 121 and a memory 122. The camera 121 has a photographing unit 121 a that photographs an object. The memory 122 includes a storage unit 122 a that stores various types of information such as photographed image data acquired by the camera 121. The drive recorder 120 may be configured to capture an appearance when an abnormality occurs in a vehicle such as at the time of an accident, or to capture an appearance inside and outside the vehicle when desired by the operation of the request side user. It 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 distance communication device 156.

  The display 151 has a display unit 151a that displays an image showing various information such as a route search result from the current location to the destination and a photographed image stored in the memory 122 of the drive recorder 120. The touch panel 152 is attached to the display 151, and includes a receiving unit 152a that receives an input to the CPU 155 by a pressing operation of the user. The memory 153 stores various information such as map data used for route search, photographed 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. Have. The GPS receiver 154 has a position information receiving unit 154 a that receives current position information of the request-side vehicle 10 based on radio waves from artificial satellites.

  The CPU 155 executes various processes based on the information stored in the memory 153 (for example, a program for providing a photographing request service). Specifically, CPU 155 is based on the current position information of request-side vehicle 10 acquired by GPS receiver 154, the destination input from touch panel 152, and the map data stored in memory 153. And a route search unit 155a that searches for a route from the destination to the destination. The CPU 155 also has a request information acquisition unit 155 b that acquires 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 distance communication device 156 has a short distance communication unit 156 a that enables wireless communication with a terminal located in the short distance of the navigation device 150. In the present embodiment, the short distance communication device 156 establishes wireless communication with the portable terminal 30 of the requesting user.

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

(Configuration of licensor vehicle)
The license side vehicle 20 is an electric car using a motor driven by the electric power supplied by the power supply unit 290a of the battery 290 as a driving power source as in the case of the request side vehicle 10 described above. It may be a car.

  The grant side vehicle 20 includes a communication module 203, a drive recorder 220, and a navigation device 250, and these components are communicably connected to each other via a communication line 210.

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

  The drive recorder 220 has the same configuration and function as the drive recorder 120 of the request side 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 a destination, as in the navigation device 150 of the request-side vehicle 10 described above. The navigation device 250 is an embodiment of the “in-vehicle 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 includes a display unit 251a that displays an image indicating various information, such as a route search result from the current location to the destination and a photographed image stored in the memory 222 of the drive recorder 220. The touch panel 252 is attached to the display 251, and includes a receiving unit 252a that receives an input to the CPU 255 by the pressing operation of the user. In the photographing request service, the user on the approval side can approve the request included in the request information by pressing the touch panel 252. The memory 253 stores various information such as map data used for route search, photographed 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. Have. The GPS receiver 254 has a position information receiving unit 254 a that receives current position information of the grant side vehicle 20 based on radio waves from the artificial satellite.

  The CPU 255 executes various processes based on the information (for example, a program for providing a photographing request service) stored in the memory 253. Specifically, CPU 255 is based on the current position information of granting side vehicle 20 acquired by GPS receiver 254, the destination input from touch panel 252, and the map data stored in memory 253. And a route search unit 255a that searches for a route from the destination to the destination. The CPU 255 also has a trigger unit 255 b that gives the server 50 a trigger for transmitting request information from the request vehicle 10. Specifically, the trigger unit 255b of the CPU 255 transmits a route search result obtained by the route search unit 255a to the server 50 via the communication module 203, thereby providing the server 50 with a trigger for transmitting request information. give. Accordingly, the server 50 that has received the route search result transmits request information matching the route search result to the navigation device 250. The CPU 255 further includes an updating unit 255 c that updates the search result of the route based on the request information acquired from the request vehicle 10 via the server 50.

  The short distance communication device 256 has a short distance communication unit 256 a that enables wireless communication with a terminal located in the short distance of the navigation device 250. In the present embodiment, the short distance communication device 256 establishes wireless communication with the portable terminal 40 of the granting user.

  The configuration of the license side vehicle 20 shown in FIGS. 2 and 3 is an example, and the license side vehicle 20 naturally has other configurations such as a configuration for traveling.

(Configuration of mobile terminal)
The portable 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 these components are communicably connected to each other via a communication line 310.

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

  The display 301 includes a display unit 301 a that displays an image indicating various information such as a photographed image stored in the memory 304. The touch panel 302 is attached to the display 301, and includes a receiving unit 302a that receives an input to the CPU 305 by a pressing operation of the user.

  The CPU 305 executes various processes based on the information stored in the memory 304 (for example, a program for providing a photographing request service). Specifically, the CPU 305 includes a request information acquisition unit 305 a that acquires 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 portable terminal 30 shown in FIGS. 2 and 3 is an example, and the portable terminal 30 naturally has other configurations. In addition, since the portable terminal 40 basically has the same configuration as the above-described portable terminal 30, a specific description is omitted.

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

  The communication interface 503 enables communication between each component in the server connected via the communication line 510 and the request vehicle 10, the portable terminal 30, the permit vehicle 20, the portable terminal 40, and the like. It has a portion 503a. The communication unit 503 a of the communication interface 503 is an embodiment of the “reception unit” and the “transmission unit”.

  The memory 502 stores various types of information such as user information included in a user information table in FIG. 4 described later, request information included in the request information table in FIG. 5, and a program for executing the imaging request service in the server 50. Storage unit 502a. The storage unit 502 a 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 photographing request service). Specifically, the CPU 501 collates the route search result received from the permission side vehicle 20 with the request information stored in the memory 502, and determines whether or not there is request information matching the route search result. It has a portion 501a. The request information matching with the route search result is transmitted to the license side 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 license side vehicle 20 and the specific imaging location included in the request information stored in the memory 502. Have a function to

<User information table>
A user who uses the photographing request service provided by the communication system 1 is to register predetermined information in the server 50. The registered user information is stored in a user information table stored in the memory 502. FIG. 4 is a diagram showing an example of a user information table stored by 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 linked to the “user ID” for identifying the user. “Terminal ID” for identifying the terminal, “e-mail address” owned by the user, and information indicating “point” owned by the user are stored. The “vehicle ID” may be an identification ID associated with the vehicle itself, or may be an identification ID associated with a navigation device provided in the vehicle.

  Here, in the present embodiment, the point system is introduced in the photographing request service, and the requesting user can request the photographing user for the photographed image by consuming the points. On the other hand, the granting-side user can obtain points possessed 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 to request a photographed image, and may be used to purchase a product or receive other services. In addition, a point is one embodiment of "a privilege".

<Required information table>
The server 50 stores the request information received from the navigation device 150 or the portable terminal 30 of the request-side 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 by the server 50 according to the present embodiment.

  As shown in FIG. 5, in the request information table, the "user ID" of the requesting user, the current "status", and the "shooting location" are linked to the "task ID" for identifying the request information. And, "request information" including detailed information of "captured image", "Thank you point" for the user of the licensor, and information indicating "request date" are stored.

  In the photographing 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 types of "status", "searching for a licensor", "licensed", and "completed" are stored. If no licensee has been found yet after the request for the photographed image is made, “searching for licensee” is stored as the “status”. If the permitted party has been found but the photographed image has not been provided to the requesting user yet, "approved" is stored as the "status". If the photographed image has already been provided to the requesting user, "completed" is stored as the "status".

  As the "photographing place" included in the "request information", information of the photographing place requested by the request-side user is stored. As the "captured image" included in the "request information", information of the details (for example, the composition of the photo, the shooting target, etc.) of the captured image requested by the requesting user is stored.

  As a "Thanks Points", when the licensor user provides the requester user with a photographed image, the points of the points possessed by the requester user are added to the points possessed by the licensor user as a thank you. Information is stored. In the present embodiment, although the requesting user can determine the thank-you point, the present invention is not limited to this, and the thank-you point may be determined in advance.

<Main processing content executed by communication system>
6-8 is a flowchart for demonstrating the main processing content which the communication system 1 performs. Each step shown in the flowcharts shown in FIG. 6 to FIG. 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".

(Required stage of shooting image)
First, with reference to FIG. 6, the processing flow at the stage when the request user requests the server 50 for a photographed image will be described. At this stage, the request-side user can request the server 50 for a photographed image using any of the navigation device 150 and the portable terminal 30 of the request-side vehicle 10. 6 is executed by the CPU 155 of the navigation device 150 or the CPU 305 of the portable terminal 30 on the request side, and is executed by the CPU 501 of the server 50 on the server 50 side. In this example, an example in which the navigation device 150 of the request-side vehicle 10 transmits the request information to the server 50 will be described.

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

  Here, FIG. 9 is a view showing an example of the display of the display 151 for the navigation device 150 in the request side vehicle 10 according to the present embodiment. As shown in FIG. 9A, in the main menu of the navigation device 150, a destination icon 161 operated to search for a route from the current location to a destination, and listening to music and watching a moving image In order to obtain various information such as an AV icon 162 operated for setting, a setting icon 163 operated for performing various settings, an imaging request icon 164 operated for requesting imaging, traffic information, etc. And an information icon 165 to be operated. The request side user can use the imaging request service by selecting the imaging 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 the shooting request icon 164 has been selected. The navigation device 150 repeats this processing flow again when the request for the photographed image is not received (NO in S110), that is, when the photographing request icon 164 is not selected.

  On the other hand, when the navigation device 150 receives a request for a photographed image (YES in S110), that is, when the photographing request icon 164 is selected, the navigation device 150 determines whether the request information has been acquired (S120). As this request information, at least the "photographed place" and the "photographed image" shown in FIG. 5 can be mentioned.

  Here, as shown in FIG. 9B, when the photographing request icon 164 is selected, the screen shifts to a photographing request service menu. The shooting request service menu includes a shooting location input field 171 for inputting "shooting location" as request information, a shooting image input field 172 for entering "shooting image" as request information, and "thank you". It includes a thank-you point input field 173 for inputting. The request-side user selects a desired character or number using the cursor 175 from among the characters or numbers arranged in the character selection field 174, thereby the photographing location input field 171, the photographed image input field 172, and the thank you image. Information can be input to each of the point input fields 173. The request-side user may select the delete icon 176 if he wants to delete characters and numbers, or may select the back icon 177 if he wants to return to the main menu. Also, the request-side 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 the request information and the thank-you point have been determined. If the navigation device 150 does not acquire the request information (NO in S120), that is, if the request information and the thank-you point are not determined, the processing of S120 is repeated until the request information is acquired.

  On the other hand, when the navigation device 150 acquires the request information (YES in S120), that is, when the request information and the thank-you point are determined, the navigation device 150 transmits the acquired request information to the server 50 (S130). The navigation device 150 transmits the vehicle ID to the server 50 in the process of S130. In addition, when a request | requirement user makes a imaging | photography request | requirement using the portable terminal 30, the portable terminal 30 transmits terminal ID to the server 50 in the process of S130. Thereafter, 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 display 151 displays a character image of “I have made a shooting request. Please wait for a while”.

  Returning to FIG. 6, the server 50 determines whether the request information has been received together with the vehicle ID from the navigation device 150 (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 process flow is repeated 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 links the vehicle ID and the user ID of the request user to the request information. Then, the server 50 causes “searching for a licensor” as the “status” to correspond to the request information. Thereafter, the server 50 repeats this processing flow again.

  In this manner, the requesting user can transmit the request information to the server 50 using the navigation device 150. Meanwhile, the server 50 can store request information received from the navigation device 150. The server 50 can acquire and store the request information from the same navigation device 150 multiple times, and the navigation device 150 or the portable terminal 30 of another request-side vehicle can be further processed by the same processing flow. Request information can also be obtained and stored. Thereby, a plurality of pieces of request information are accumulated in the request information table. Although FIG. 9 shows an example of the display on the display 151 of the navigation device 150, the icon for selecting the imaging request, the request information and the thank-you point are also input similarly for the display 301 of the portable terminal 30. An input field for the user is displayed.

(Performing stage of the imaging request)
Next, with reference to FIG. 7, a processing flow at a stage where the granting side user grants a photographing request will be described. The CPU 501 of the server 50 executes the process flow illustrated in FIG. 7 on the server 50 side, and the CPU 255 of the navigation device 250 executes the process on the approval side.

  As shown in FIG. 7, the navigation device 250 determines whether or not there is a route search acceptance (S210). Specifically, the navigation device 250 determines whether or not there is a request for a route search from the current location to the destination by the granting-side user. When the navigation device 250 does not receive a route search (NO in S210), the navigation device 250 repeats this processing flow again.

  On the other hand, when the navigation device 250 receives a route search (YES in S210), the navigation device 250 searches for a route (S220). Thereafter, the navigation device 250 transmits the route search result to the server 50 (S230). The request information can be transmitted to the server 50 by such a trigger.

  In response to this, the server 50 determines whether or not the route search result has been received (S560). When the server 50 has not received the route search result (NO in S560), the process flow is repeated 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 makes a request for matching with the route search result It is determined whether there is information (S580). Specifically, the server 50 determines, among the request information stored in advance, whether or not the request information whose route is on or near the route searched by the route search result exists. 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 there is request information matching with the route search result (YES in S580), the server 50 transmits the matching request information together with the task ID to the navigation device 250 (S590).

  In response to this, the navigation device 250 determines whether the request information has been received within a predetermined time (S240). When the navigation device 250 does not receive the request information within the time (NO in S240), this processing flow is repeated 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 specifies location information (for example, longitude and latitude) from the address of the shooting location included in the request information, and based on the specified location information, displays an image indicating the shooting location on the route. indicate.

  Here, FIG. 10 is a view showing an example of the display of the display 251 of the navigation device 250 in the license side 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 indicating a route to the destination and a distance image 261 indicating the distance to the destination on the map. When the request information is notified to the display 251 in the process of S250 of FIG. 9, the display shifts to a display as shown in FIG.

  FIG. 10B shows an example in which the request information of task ID “005” and 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 task ID “005” and task ID “006” all includes the vicinity of Lake Yamanaka in Yamanashi Prefecture as a shooting site. Then, if the current location of the granting side user is near Lake Yamanaka, the request information will match the route search result.

  As shown in FIG. 10 (b), in displaying the route search result when the request information is notified, a flag image 264 indicating the photographing location corresponding to the task ID "005" is displayed together with the route image 260 on the map. , And a flag mark 263 indicating a shooting location corresponding to the task ID "005". Furthermore, at the right end of the display 251, a detail column 265 for viewing the details of the request information is displayed. In the details column 265, a point image 266 indicating thanks points, a detail icon 267 for viewing details of the request information, and a request for each request information of the task ID "005" and the task ID "006" are accepted. And a permission icon 268 which is operated to do this. 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 the granting-side user has accepted the request (S260). That is, the navigation device 250 determines whether the permission icon 268 is selected for the request information of any of the task ID "005" and the task ID "006". The navigation device 250 repeats this processing flow again when the granting-side user does not grant the request (NO in S260).

  On the other hand, when the granting-side user grants the request (YES in S260), the navigation device 250 transmits, to the server 50, grant information indicating that the granting-side user has granted the request (S270). For example, as shown in FIG. 10C, when the licensor side user accepts a request corresponding to the task ID "005", a circle mark is displayed on the flag mark 264 indicating the photographing location corresponding to the task ID "005". It is indicated that permission has been granted to the licensor by some effect such as blinking or color change.

  Referring back to FIG. 7, the server 50 determines whether the permission information has been received within a predetermined time (S600). When the server 50 does not receive the permission information within the time (NO in S600), the process flow is repeated again.

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

  In response to this, the navigation device 250 determines whether or not the update permission information has been received within a predetermined time (S280). When the navigation device 250 does not receive the update permission information in time (NO in S280), the processing flow is repeated 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, while the flag 263 indicating the shooting location corresponding to the task ID "006" disappears, 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 as to return to the route to the original destination after the route image 260 stops by the flag 264. Furthermore, in addition to the distance image 261 indicating the distance to the destination, a distance image 262 indicating the distance to the shooting location stopped in the middle is displayed on the display 251.

  If the licensor side user also accepts the request corresponding to the task ID “006” in addition to the request corresponding to the task ID “005”, the route image 260 stops after both the flag 263 and the flag 264 are dropped. The route search results are updated to return to the route to the destination. Returning to FIG. 7, the server 50 repeats the present process flow again after the process of S290.

(Acquisition stage of the photographed image)
Next, the processing flow at the stage when the request-side user acquires a photographed image from the permit-side user will be described with reference to FIG. Note that at this stage, the license user can transmit the photographed image to the server 50 regardless of which of the navigation device 250 and the portable terminal 40 of the license vehicle 20 is used. Also, at this stage, the request-side user can receive the photographed image from the server 50 regardless of which of the navigation device 150 and the portable terminal 30 of the request-side vehicle 10 is used. The process flow shown in FIG. 8 is executed by the CPU 255 of the navigation device 250 or the CPU (not shown) of the portable terminal 40 on the permission side, and by the CPU 501 of the server 50 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 it. In this example, an example will be described in which a photographed image is transmitted from the portable terminal 40 of the permission user to the portable terminal 30 of the request user.

  As shown in FIG. 8, the portable terminal 40 of the user on the approval side determines whether or not transmission of the photographed image data has been accepted (S2010). At this point, the portable terminal 40 has already acquired a photographed image from the camera of the portable terminal 40 or the camera 221 of the drive recorder 220 of the approval side vehicle 20 or the like.

  When the portable terminal 40 does not receive the transmission of the photographed image data (NO in S2010), this processing flow is repeated again. On the other hand, when the portable terminal 40 receives the transmission of the photographed image data (YES in S2010), it transmits the photographed image data to the server 50 together with the task ID (S2020). The task ID may be input to the portable terminal 40 by the granting side user, or may be acquired by the portable terminal 40 from the navigation device 250 using near-field communication.

  In response to this, the server 50 determines whether the photographed image data has been received (S5010). When the server 50 has not received the photographed image data (NO in S5010), the process flow is repeated again.

  On the other hand, when the server 50 receives the photographed image data (YES in S5010), the server 50 transmits the photographed image data together with the task ID to the portable terminal 30 of the request user (S5020). Specifically, the server 50 specifies the user ID linked to the task ID based on the request information table. Then, the server 50 transmits the photographed image data to the mail address associated with the specified user ID based on the user information table. If the navigation device 150 owns an e-mail address, the server 50 may transmit the photographed image data to the e-mail address of the navigation device 150 linked to the user ID.

  On the other hand, the portable terminal 30 of the request-side user determines whether the photographed image data has been received (S1010). When the mobile terminal 30 has not received the photographed image data (NO in S1010), this processing flow is repeated again.

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

  In response to this, the server 50 determines whether the acquired information has been received (S5030). When the server 50 has not received the acquired information (NO in S5030), the process of S5030 is repeated.

  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). Thereafter, the server 50 moves points of the thank-you point corresponding to the task ID from the point of the requesting user to the point of the permitting user and stores them (S5050).

  Thereafter, the server 50 transmits point information indicating points after movement to the portable terminal 30 of the requesting user and the portable terminal 40 of the permitting user (S5060), and repeats this processing flow again.

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

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

  Similarly, the portable terminal 40 of the granting side user determines whether point information has been received within a predetermined time (S2030). When the portable terminal 40 does not receive point information in time (NO in S2030), the processing flow is repeated again.

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

<About 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 in accordance with the trigger from the permit side vehicle 20 When the granting side user accepts 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 licensee user who has accepted the request can grasp the route to the shooting location based on the updated search result of the route. On the other hand, the requester user can acquire the photographed image acquired by the permitter user via the navigation device 150 or the portable terminal 30. This improves the convenience of the user regarding the request for the photographed image.

  The granting-side user can grant a request corresponding to at least one task ID among a plurality of task IDs, and the search result of the route is updated based on at least one request information including the granted request Therefore, the choice of the licensee user is expanded.

  Request information matching the route search result is transmitted to the navigation device 250 based on the route search result by the navigation device 250 and the specific shooting location included in the request information. 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 on the consent side is further improved.

  Since the navigation device 250 displays the route image 260 that can specify the route search result, the flag 263 or 264 that can specify the request, and the details of the request information, the licensor user visually requests the route search result Can understand.

  Since the granting side user can obtain points owned by the requester user by providing the requester user with the photographed image, the utilization rate of the photographing request service can be increased.

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

  In the present embodiment, among the request information stored in advance in the license side vehicle 20, matching is performed only when there is request information whose route is on or near the route searched by the route search result. Request information was notified. However, even if there is no request information whose shooting location is on or near the route found in the route search result (that is, the shooting location is far from the route), the request information is notified. May be

  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 permit side vehicle 20. However, if the navigation device 250 is configured to allow the user of the licensor to select whether or not to notify the request information, and even if the request information is to be notified, the photographing site to be notified can be selected. May send the request information according to the selected content.

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

  In the present embodiment, points are given to the licensor side user as a benefit in the photographing request service, but of course the licensor side user can volunteer the request of the requester user without a point system being introduced. It may be filled. The benefit is not limited to points, and may be a virtual currency usable in a virtual world such as a game, or may be electronic money.

  The above-described modifications may be implemented in combination of all or part thereof. It should be understood that the embodiments disclosed herein are illustrative and non-restrictive in every respect. The scope of the present disclosure is indicated not by the description of the embodiments described above but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.

  Reference Signs List 1 communication system, 10 requester vehicle, 20 licensee vehicle, 30, 40 portable 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 distance communication device, 190, 290 battery, 303, 503 communication interface.

Claims (7)

A communication system comprising a vehicle and a server capable of communicating with the vehicle, the communication system comprising:
The vehicle includes an in-vehicle device capable of searching for a route from a current location to a destination,
The server is
A receiving unit that externally receives request information including a request for a captured image at a specific shooting location;
And a transmitter configured to transmit the request information received by the receiver to the in-vehicle device according to a trigger from the vehicle.
The communication system further includes an updating unit that updates the search result of the route based on the request information when the user accepts a request included in the request information from the transmitting unit. The server further includes a storage unit that stores a plurality of the request information received by the receiving unit,
The transmission unit can transmit the plurality of request information stored in the storage unit to the in-vehicle device.
When the user accepts a request included in at least one request information of the plurality of request information from the transmission unit, the update unit is configured to search the route based on the at least one request information. The communication system according to claim 1, which updates. The server further includes a determination unit that determines whether to transmit the request information based on a search result of the route by the in-vehicle 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 on-vehicle apparatus when it is determined by the determination unit that the transmission is present. The in-vehicle apparatus further includes a display unit that displays an image;
The communication system according to any one of claims 1 to 3, wherein the display unit displays an image capable of specifying a request included in the request information, together with an image capable of specifying a search result of the route. The server further includes a management unit that manages benefits owned by the requester user who requests the photographed image and the user of the vehicle.
The said management part adds the privilege which the said request | requirement user owns to the privilege which the user of the vehicle owns, when the user of the said vehicle satisfy | fills the request | requirement contained in the said request information. The communication system according to any one of Items 4. An on-vehicle device provided in a vehicle that can communicate with a server,
The route search part which can search the route from the present location to the destination,
A trigger unit for triggering the server;
An updating unit for updating the search result of the route based on the request information when the user accepts a request for a captured image at a specific shooting location included in the request information transmitted from the server according to the trigger; An on-vehicle device. A program executed by a computer that can communicate with a server,
On the computer
Searching for a route from the current location to the destination;
Triggering the server;
Performing a step of updating the search result of the route based on the request information when the user accepts a request for a photographed image at a specific shooting location included in the request information transmitted from the server according to the trigger Make a program.

Images