JP2019106097A - Network system, server, and information processing method - Google Patents

Abstract

To provide a network system, a server, or an information processing method capable of effectively utilizing an acquired image.SOLUTION: A network system 1 is provided which is comprised of: a drive recorder 200B of a first user; databases 120 and 100B for acquiring moving images of the drive recorder 200B; and a server 100 for inquiring of the first user whether a moving image may be provided to a second user and providing the moving image to terminals 300A and 200A of the second user based on a result of the inquiry.SELECTED DRAWING: Figure 9

Description

  The present invention relates to a technique for effectively using image data.

  Conventionally, techniques related to drive recorders are known. For example, an accident notification system, a notification system, an in-vehicle notification device, and an accident notification method are disclosed in JP-A-2017-117005 (Patent Document 1). According to Patent Document 1, a vehicle having detected an accident occurrence transmits an accident occurrence notification including accident occurrence position information to the vehicle and the server device. When the accident occurrence position information and the position information of the own vehicle satisfy the predetermined conditions, the vehicle that has received the accident occurrence notification transmits the captured image of the on-vehicle camera to the server device as the accident condition notification. When receiving the notification from the vehicle or the vehicle, the server device notifies the vehicle existing in the predetermined range from the accident occurrence position of the occurrence of the accident. The vehicle receiving the accident occurrence notification from the server device transmits the captured image of the in-vehicle camera as the accident condition notification to the server device when the notified accident occurrence position information and the position information of the own vehicle satisfy the predetermined conditions.

  Moreover, the accident information acquisition apparatus is disclosed by Unexamined-Japanese-Patent No. 2010-20386 (patent document 2). According to Patent Document 2, the accident information acquisition device is mounted on a vehicle, and includes a control unit, an accident detection unit, a photographing unit, a display unit, a communication unit, and a removable memory. When the occurrence of a vehicle accident is detected, the control unit requests the surrounding vehicle to provide imaging data, and stores the imaging data held by the imaging unit in the removable memory. Also, even when there is a request for provision of imaging data from a surrounding vehicle, the imaging data held by the imaging unit is stored in the removable memory.

  Moreover, the drive recorder system, the drive recorder, and the information processing apparatus are disclosed by Unexamined-Japanese-Patent No. 2010-72845 (patent document 3). According to Patent Document 3, in a drive recorder system in which a drive recorder and an information processing apparatus are connected via a network, the drive recorder comprises an imaging means, a first storage means for storing captured image data, and an accident occurrence. The first storage means comprises image data at the time of occurrence of the accident when the occurrence of the accident is detected by the accident occurrence detection means, the transmission / reception means provided with the detection means, the position detection means, and the transmission / reception means and the drive recorder includes , And transmits information indicating an accident occurrence time and an accident occurrence position, and the information processing apparatus includes second storage means for storing the image data received from the drive recorder, The image data at the time of the accident occurrence is acquired based on the information indicating the accident occurrence time and the accident occurrence position received from the drive recorder It is stored in the second storage means.

JP, 2017-117005, A Unexamined-Japanese-Patent No. 2010-20386 JP, 2010-72845, A

  An object of the present invention is to provide a network system, a server, or an information processing method capable of effectively utilizing an acquired image.

  According to an aspect of the present invention, it is provided to the first user the drive recorder of the first user, the database for acquiring the moving image of the drive recorder, and whether or not the moving image may be provided to the second user. There is provided a network system comprising: a server for inquiring and providing a moving image to a terminal of a second user based on the result of the inquiry.

  As described above, according to the present invention, there is provided a network system, a server, or an information processing method capable of effectively utilizing an acquired image.

FIG. 1 is an image diagram showing an entire configuration of a network system 1 according to a first embodiment. It is an image figure showing communication composition of network system 1 concerning a 1st embodiment. It is a block diagram showing composition of server 100 concerning a 1st embodiment. It is an image figure showing terminal data 121 concerning a 1st embodiment. It is an image figure showing a data structure of event data 122 concerning a 1st embodiment. It is an image figure which shows the data structure of the imaging | photography information data 123 concerning 1st Embodiment. FIG. 1 is a block diagram showing a configuration of a drive recorder 200 according to a first embodiment. It is a block diagram which shows the structure of the communication terminal 300 concerning 1st Embodiment. It is a sequence diagram which shows the process sequence of the network system 1 concerning 1st Embodiment. It is an image figure showing the screen of smart phone 300B concerning a 1st embodiment. It is an image figure showing the screen of smart phone 300A concerning a 1st embodiment. It is a sequence diagram which shows the process sequence of the network system 1 concerning 2nd Embodiment. It is a sequence diagram which shows the process sequence of the network system 1 concerning 3rd Embodiment. It is a sequence diagram which shows the process sequence of the network system 1 concerning 4th Embodiment. It is a sequence diagram which shows the process sequence of the network system 1 concerning 5th Embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, the same components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed description about them will not be repeated.
First Embodiment
<Overall configuration of network system>

First, the overall configuration of the network system 1 according to the present embodiment will be described. Referring to FIG. 1, network system 1 mainly includes server 100 connected to the Internet, drive recorders 200A and 200B mounted on various vehicles, and smartphones 300A and 300B possessed by users of various vehicles. . In the present embodiment, smartphones 300A and 300B are described as an example of the communication terminal, but a tablet, a personal computer, a game machine, a wearable terminal or the like may be used.
<Communication configuration of network system>

Next, the communication configuration of the network system 1 according to the present embodiment will be described. Referring to FIG. 2, drive recorders 200A and 200B communicate with server 100 via a carrier network such as LTE or the Internet. The smartphones 300A and 300B also communicate with the server 100 via a carrier network such as LTE or the Internet. The drive recorders 200A and 200B communicate with the smartphones 300A and 300B using wireless communication such as Bluetooth (registered trademark), WiFi (registered trademark), a carrier network, and the Internet.
<Operation outline of network system>

Returning to FIG. 1, when the vehicle A receives an impact, the network system 1 according to the present embodiment receives the image or the sound captured by the drive recorder 200B of the vehicle B located in the vicinity of the vehicle A. Provided to users of In particular, in the present embodiment, after obtaining confirmation from the user of drive recorder 200B, the image and sound captured by drive recorder 200B are provided to the user of vehicle A. Hereinafter, the network system 1 for realizing such a function will be described in detail.
<Hardware Configuration of Server 100>

  Here, one aspect of the configuration of the server 100 configuring the network system 1 will be described. Referring to FIG. 3, server 100 includes, as main components, central processing unit (CPU) 110, memory 120, operation unit 140, and communication interface 160.

  The CPU 110 controls each part of the server 100 by executing a program stored in the memory 120. For example, the CPU 110 executes a program stored in the memory 120, and executes various processes to be described later by referring to various data.

  The memory 120 may be realized by various RAMs (Random Access Memory), various ROMs (Read-Only Memory), or the like, and may be included in the server 100 or removable from various interfaces of the server 100. It may be the database 100 B in another device accessible from the server 100. The memory 120 is a program executed by the CPU 110, data generated by execution of the program by the CPU 110, terminal data 121, event data 122, shooting information data 123, a shot image itself including audio, a thumbnail image, Image quality image data etc. are stored.

  Here, referring to FIG. 4, the terminal data 121 stores the correspondence between a user and a terminal such as the drive recorders 200A and 200B and the smartphones 300A and 300B.

  Referring to FIG. 5, event data 122 includes identification information, identification information of a terminal related to the event, date and time of occurrence of the event, occurrence location of the event, and the event for each event such as accident or incident. The correspondence relationship such as the traveling direction of the vehicle at the time of occurrence or the shooting direction of the drive recorders 200A and 200B is stored.

  Referring to FIG. 6, the photographing information data 123 includes, for each photographed image, identification information of a terminal that photographed the image, photographing date and time, photographing location, photographing direction, availability of the image, etc. Store the correspondence.

  Returning to FIG. 4, the operation unit 140 receives an operation instruction from a service administrator or the like and inputs the operation instruction to the CPU 110.

The communication interface 160 transmits data from the CPU 110 to other devices such as the drive recorders 200A and 200B and the smartphones 300A and 300B via the Internet, a carrier network, a router or the like. Conversely, the communication interface 160 receives data from other devices via the Internet, a carrier network, a router, etc., and passes it to the CPU 110.
<Hardware Configuration of Drive Recorder 200>

  Next, one aspect of the configuration of drive recorders 200A and 200B will be described. Referring to FIG. 7, drive recorders 200A and 200B each include, as main components, a CPU 210, a memory 220, a communication interface 260, a microphone 280, a camera 290, and a shock sensor 295.

  The CPU 210 controls each part of the drive recorders 200A and 200B by executing a program stored in the memory 220 or an external storage medium. That is, the CPU 210 executes various programs described later by executing a program stored in the memory 220.

  The memory 220 may be realized by various types of RAM, various types of ROM, etc., and may be included in the drive recorders 200A, 200B, or may be removable from various interfaces of the drive recorders 200A, 200B. It may be a recording medium of another device accessible from the drive recorders 200A and 200B. The memory 220 stores various programs executed by the CPU 210 and various data used for the execution of programs by the CPU 210.

  The communication interface 260 is realized by an antenna and a connector, and exchanges data with another device such as a server via the Internet or a carrier network. The communication interface 260 also exchanges data with other devices such as the smartphones 300A and 300B using Bluetooth (registered trademark) or WiFi (registered trademark).

  The microphone 280 inputs audio data to the CPU 210 based on surrounding audio.

  The camera 290 acquires a moving image or a still image and stores it in the memory 220. The CPU 210 combines voice data with moving images and still images, and stores the combined data in the memory 220 as a captured image.

The impact sensor 295 is realized by an acceleration sensor or the like to detect an impact. In the present embodiment, when an impact is detected, the CPU 210 protects the moving image stored in the memory 220, including those before and after it, from being immediately overwritten or deleted.
<Hardware configuration of communication terminal>

  Next, one aspect of the configuration of the communication terminal 300 such as the smartphones 300A and 300B will be described. Referring to FIG. 8, smartphones 300A and 300B each include, as main components, CPU 310, memory 320, touch panel 350 (display 330 and pointing device 340), communication interface 360, speaker 370, and microphone 380. Including.

  The CPU 310 controls each unit of the communication terminal 300 by executing a program stored in the memory 320 or an external storage medium. That is, the CPU 310 executes various programs described later by executing a program stored in the memory 320.

  The memory 320 may be realized by various types of RAM, various types of ROM, etc., and may be included in the communication terminal 300 or may be removable from various interfaces of the communication terminal 300. It may be a recording medium of another device accessible from communication terminal 300. The memory 320 stores various programs executed by the CPU 310, various data used for the execution of programs by the CPU 310, and the like.

  The display 330 outputs characters and an image based on a signal from the CPU 310. The pointing device 340 receives an instruction from the user and inputs the instruction to the CPU 310. In the present embodiment, communication terminal 300 has touch panel 350 in which display 330 and pointing device 340 are combined.

  The communication interface 360 is realized by an antenna and a connector, and exchanges data with another device such as a server via the Internet or a carrier network. The communication interface 360 also exchanges data with other devices such as the drive recorders 200A and 200B using Bluetooth (registered trademark) or WiFi (registered trademark).

The speaker 370 outputs various sounds based on the sound signal from the CPU 310. The microphone 380 inputs audio data to the CPU 310 based on surrounding audio.
<Information processing in network system 1>

  Next, the information processing of the network system 1 according to the present embodiment will be described with reference to FIG.

  First, the CPU 210 of the drive recorder 200A of the vehicle A sequentially stores the data of the photographed image in the memory 220 while photographing the moving image, uploads the photographing position, the photographing direction, the photographing date, etc. to the server 100 (step S102). Similarly, the CPU 210 of the drive recorder 200B of the vehicle B sequentially stores the data of the captured image in the memory 220 while capturing a moving image, uploads the shooting position, the shooting direction, the shooting date, etc. to the server 100 Step S104). The CPU 110 of the server 100 accumulates the shooting position, the shooting direction, the shooting date and time, and the like from the drive recorders 200A and 200B in the shooting information data 123.

  When the vehicle A is caught in an accident or the like and receives an impact, the CPU 210 of the drive recorder 200A transmits the position at which the impact is generated, the date and time when the impact is generated, and the like to the server 100 (step S106). The CPU 110 of the server 100 refers to the shooting information data 123 based on the position where the shock occurred and the date and time when the shock occurred, and searches for another drive recorder 200B that was photographed at the position and the date (step S108). ).

  The CPU 110 of the server 100 specifies another drive recorder 200B that has been photographed at the position and date and time. The CPU 110 refers to the terminal data 121 to specify the user corresponding to the drive recorder 200B and the smartphone 300B of the user. The CPU 110 requests the smartphone 300B to provide a photographed image of the drive recorder 200B via the communication interface 160 (step S110).

  In the present embodiment, based on an instruction from server 100, CPU 310 of smartphone 300B calls on the user to provide a photographed image as shown in FIG. 10 (A). The CPU 310 receives an answer as to whether or not the photographed image may be provided as shown in FIG. 10B based on the instruction from the user. When the CPU 310 receives an answer indicating that the photographed image may be provided, the CPU 310 transmits a message to that effect to the server 100. The server 100 registers in the photographing information data 123 that the provision of the photographed image is permitted. As shown in FIG. 10C, the server 100 gives points to the permitted user (step S122 in FIG. 9).

  Returning to FIG. 9, upon obtaining the permission of the user, the CPU 310 of the smartphone 300B acquires a photographed image from the drive recorder 200B (step S112). The CPU 310 uploads the photographed image to the server 100 via the communication interface 360 (step S114).

  The CPU 110 of the server 100 refers to the terminal data 121 via the communication interface 160 to identify the user corresponding to the drive recorder 200A and the smartphone 300A of the user. The CPU 110 inquires the smartphone 300A via the communication interface 160 (step S116). More specifically, as shown in FIG. 11A, the CPU 310 of the smart phone 300A displays a screen for accepting whether to consider providing a captured image from another drive recorder 200B.

  When the user wishes to confirm the image, the CPU 310 acquires, from the server 100 via the communication interface 360, a thumbnail image of a photographed image for which provision of the photographed image is permitted at that time. As shown in FIG. 11B, the CPU 310 causes the display 330 to selectably display the captured image. When CPU 310 receives the user's selection command, CPU 310 requests server 100 for the photographed image itself via communication interface 360 (step S118). The smartphone 300A downloads the photographed image itself from the server 100 (step S120). Thus, as shown in FIG. 11C, the CPU 310 of the smartphone 300A can display the downloaded captured image on the display 330.

As described above, the network system 1 according to the present embodiment can use the image captured by the other drive recorder 200B, and obtain the permission of the user of the other drive recorder 200B regarding the use of the image. Unintended breach of privacy is unlikely to occur.
Second Embodiment

  In the first embodiment, with emphasis on privacy, image data is uploaded to the server 100 after receiving permission to provide an image. However, if the permission from the user is delayed, there is a high possibility that the image data will be overwritten and deleted. Therefore, as shown in FIG. 12, after the server 100 first acquires the image data, permission for provision to other users may be obtained.

  That is, when the vehicle A is caught in an accident or the like and receives an impact, the CPU 210 of the drive recorder 200A transmits the position where the impact occurred, the date when the impact occurs, and the like to the server 100 (step S106). The CPU 110 of the server 100 refers to the shooting information data 123 based on the position where the shock occurred and the date and time when the shock occurred, and searches for another drive recorder 200B that was photographed at the position and the date (step S108). ).

  The CPU 110 of the server 100 specifies another drive recorder 200B that has been photographed at the position and date and time. The CPU 110 requests the other drive recorder 200B for a photographed image via the communication interface 160 (step S212), and acquires the photographed image (step S214).

  The CPU 110 refers to the terminal data 121 to specify the user corresponding to the drive recorder 200B and the smartphone 300B of the user. The CPU 110 requests the smartphone 300B to permit provision of the photographed image of the drive recorder 200B to other users via the communication interface 160 (step S216).

  In the present embodiment, based on an instruction from server 100, CPU 310 of smartphone 300B calls on the user to provide a photographed image as shown in FIG. 10 (A). The CPU 310 receives an answer as to whether or not the photographed image may be provided as shown in FIG. 10B based on the instruction from the user. When the CPU 310 receives an answer indicating that the photographed image may be provided, the CPU 310 transmits a message to that effect to the server 100. The server 100 registers in the photographing information data 123 that the provision of the photographed image is permitted. As shown in FIG. 10C, the server 100 gives points to the authorized user (step S122).

When the user's permission is obtained from the smartphone 300B (step S218), the CPU 110 of the server 100 refers to the terminal data 121 and identifies the user corresponding to the drive recorder 200A and the smartphone 300A of the user. The CPU 110 inquires the smartphone 300A via the communication interface 160 (step S116). The subsequent processing is the same as that of the first embodiment, and therefore the description thereof will not be repeated here.
Third Embodiment

  Alternatively, as shown in FIG. 13, the server 100 may first acquire a thumbnail image or a low-quality moving image.

  That is, when the vehicle A is caught in an accident or the like and receives an impact, the CPU 210 of the drive recorder 200A transmits the position where the impact occurred, the date when the impact occurs, and the like to the server 100 (step S106). The CPU 110 of the server 100 refers to the shooting information data 123 based on the position where the shock occurred and the date and time when the shock occurred, and searches for another drive recorder 200B that was photographed at the position and the date (step S108). ).

  The CPU 110 of the server 100 specifies another drive recorder 200B that has been photographed at the position and date and time. The CPU 110 requests a thumbnail image or low-quality moving image of the captured image corresponding to the other drive recorder 200B via the communication interface 160 (step S312), and generates a thumbnail image or low-quality moving image of the captured image. Is acquired (step S314).

  The CPU 110 of the server 100 refers to the terminal data 121 via the communication interface 160 to identify the user corresponding to the drive recorder 200A and the smartphone 300A of the user. The CPU 110 inquires the smartphone 300A via the communication interface 160 (step S116). More specifically, as shown in FIG. 11A, the CPU 310 of the smartphone 300A displays a screen for accepting whether to consider providing a captured image of another drive recorder 200B.

  When the user desires to confirm the image, the CPU 310 acquires a thumbnail image of the captured image from the server 100 via the communication interface 360. As shown in FIG. 11B, the CPU 310 causes the display 330 to selectably display the captured image. When the CPU 310 receives the user's selection command, the CPU 310 requests the server 100 to obtain a target photographed image (step S118).

  The CPU 110 of the server 100 refers to the terminal data 121, and identifies the user corresponding to the drive recorder 200B of the selected captured image and the smartphone 300B of the user. The CPU 110 requests the smartphone 300B to provide a photographed image of the drive recorder 200B via the communication interface 160 (step S110).

  In the present embodiment, based on an instruction from server 100, CPU 310 of smartphone 300B calls on the user to provide a photographed image as shown in FIG. 10 (A). The CPU 310 receives an answer as to whether or not the photographed image may be provided as shown in FIG. 10B based on the instruction from the user. When the CPU 310 receives an answer indicating that the photographed image may be provided, the CPU 310 acquires a high-quality photographed image from the drive recorder 200B (step S112). The CPU 310 uploads the photographed image to the server 100 via the communication interface 360 (step S114).

  The server 100 downloads the photographed image itself to the smartphone 300A (step S120). The server 100 registers in the photographing information data 123 that the provision of the photographed image is permitted. As shown in FIG. 10C, the server 100 gives points to the authorized user (step S122).

The CPU 310 of the smartphone 300B can display the downloaded photographed image on the display 330, as shown in FIG.
Fourth Embodiment

  Alternatively, as shown in FIG. 14, the captured image may be constantly uploaded from the drive recorders 200A and 200B to the server 100.

  That is, the CPU 210 of the drive recorder 200A of the vehicle A sequentially stores data in the memory 220 while shooting a moving image, or uploads a shooting position, shooting direction, shooting date, shooting image itself, etc. to the server 100 Step S402). Similarly, the CPU 210 of the drive recorder 200B of the vehicle B sequentially stores data in the memory 220 while shooting a moving image, or uploads a shooting position, a shooting direction, a shooting date, a shooting image itself, etc. to the server 100 (Step S404). The CPU 110 of the server 100 accumulates the shooting position, the shooting direction, the shooting date and time, and the like from the drive recorders 200A and 200B in the shooting information data 123.

  When the vehicle A is caught in an accident or the like and receives an impact, the CPU 210 of the drive recorder 200A transmits the position at which the impact is generated, the date and time when the impact is generated, and the like to the server 100 (step S106). The CPU 110 of the server 100 refers to the shooting information data 123 based on the position where the shock occurred and the date and time when the shock occurred, and searches for another drive recorder 200B that was photographed at the position and the date (step S108). ).

  The CPU 110 of the server 100 specifies another drive recorder 200B that has been photographed at the position and date and time. The CPU 110 refers to the terminal data 121 to specify the user corresponding to the drive recorder 200B and the smartphone 300B of the user. The CPU 110 requests the smartphone 300B to permit provision of the photographed image of the drive recorder 200B to other users via the communication interface 160 (step S216).

  In the present embodiment, based on an instruction from server 100, CPU 310 of smartphone 300B calls on the user to provide a photographed image as shown in FIG. 10 (A). The CPU 310 receives an answer as to whether or not the photographed image may be provided as shown in FIG. 10B based on the instruction from the user. When receiving an answer indicating that the photographed image may be provided, the CPU 310 transmits a message to that effect to the server 100 (step S218). The server 100 registers in the photographing information data 123 that the provision of the photographed image is permitted. As shown in FIG. 10C, the server 100 gives points to the authorized user (step S122).

The CPU 110 of the server 100 refers to the terminal data 121 via the communication interface 160 to identify the user corresponding to the drive recorder 200A and the smartphone 300A of the user. The CPU 110 inquires the smartphone 300A via the communication interface 160 (step S116). The subsequent processing is the same as that of the first embodiment, and therefore the description thereof will not be repeated here.
Fifth Embodiment

Other devices may execute some or all of the roles of the devices of the network system 1 of the above-described embodiment. For example, another device plays a part or all of the roles of each of the server 100, the drive recorders 200A and 200B, and the smartphones 300A and 300B, or the roles of each of the server 100, the drive recorders 200A and 200B, and the smartphones 300A and 300B. Some or all of them may be carried by a plurality of devices. Specifically, the role of the server 100 can be played by a plurality of servers on the cloud, and the role of the server 100 can be played by an application of the smartphones 300A and 300B. Alternatively, as shown in FIG. 15, drive recorders 200A and 200B having a display may play a role of smartphones 300A and 300B, and smartphones 300A and 300B having a camera may play a role of drive recorders 200A and 200B. It is.
<Summary>

  In the above embodiment, the first user's drive recorder 200B, databases 120 and 100B for acquiring the moving image of the drive recorder 200B, and whether or not the moving image may be provided to the second user There is provided a network system 1 comprising: a server 100 for inquiring a first user and providing a moving image to a second user's terminal 300A, 200A based on the result of the inquiry.

  Preferably, when the drive recorder 200A of the second user detects a shock, the first user may determine whether the server 100 may provide the second user with moving images before and after the timing of the shock. Contact

  Preferably, when the drive recorder 200A of the second user detects a shock, the server 100 stores moving images of the drive recorder 200B before and after the timing of the shock in the databases 120 and 100B.

  Preferably, when the server 100 makes an inquiry to the first user whether or not the moving image before and after the timing of the shock may be provided to the second user, the result of the drive recorder 200 B is positive. The moving image is stored in the databases 120 and 100B.

  Preferably, the server 100 inquires of the terminal 300A of the first user different from the drive recorder 200B of the first user whether the moving image may be provided to the second user.

  In the above embodiment, whether or not the moving image acquired from the drive recorder 200B of the first user may be provided to the second user via the communication interface 160 and the communication interface 160 is referred to as “No. There is provided a server 100 including a processor 110 for inquiring one user and providing a moving image to the second user's terminal 300A, 200A based on the result of the inquiry.

  In the above embodiment, an information processing method by the server 100 is provided. The method inquires of the first user whether or not the moving image acquired from the drive recorder 200B of the first user may be provided to the second user, the moving image based on the result of the inquiry Providing the second user's terminal 300A, 200A.

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

1: Network system 100: Server 100B: Other database 110: CPU
120: Database (memory)
121: terminal data 122: event data 123: imaging information data 140: operation unit 160: communication interface 200: communication terminal 200A: drive recorder 200B: drive recorder 210: CPU
220: Memory 260: Communication interface 290: Camera 295: Impact sensor 300: Communication terminal 300A: Smartphone 300B: Smartphone 310: CPU
320: Memory 330: Display 340: Pointing device 350: Touch panel 360: Communication interface 370: Speaker 380: Microphone A: Vehicle B: Vehicle

Claims (7)

A first user's drive recorder,
A database for acquiring moving images of the drive recorder;
A server for asking the first user whether or not the moving image may be provided to a second user, and providing the moving image to the terminal of the second user based on the result of the inquiry And a network system.   When the drive recorder of the second user detects a shock, the first user may indicate whether the server may provide the second user with a moving image before and after the timing of the shock. The network system according to claim 1, which inquires.     The network system according to claim 1, wherein when the second user's drive recorder detects an impact, the server stores moving images of the drive recorder before and after the timing of the impact in the database.   When the server inquires the first user whether or not the moving image before and after the timing of the impact may be provided to the second user, the moving image of the drive recorder is The network system according to claim 1, wherein the image is stored in the database.   The server inquires of the terminal of the first user different from the drive recorder of the first user whether the video may be provided to the second user or not. Network system according to any one of the above. Communication interface,
The first user is inquired as to whether or not the moving image acquired from the drive recorder of the first user may be provided to the second user via the communication interface, and based on the inquiry result A processor for providing the moving image to a terminal of the second user. It is an information processing method by a server, and
Inquiring of the first user whether or not the moving image acquired from the drive recorder of the first user may be provided to the second user;
Providing the moving image to the terminal of the second user based on the inquiry result.

Images