Drive record display system and drive record display method

Abstract

To improve the convenience of users who utilize the drive record display system. [Solution] The drive record display system M comprises an information terminal 8 owned by the user of vehicle Q and a content management server 1. The content management server 1 saves positioning data Dp and video data Dv1 received when the vehicle starts driving as a drive record, while transmitting display data V to the information terminal 8, and sends a drive completion notification when the drive ends. The information terminal 8 displays an image showing the driving status of vehicle Q based on the display data V on the lower layer L1 of the display screen, and when it receives a drive completion notification, it displays a reception image TB on the upper layer L2 that accepts the operation of a drive record creation request or editing request.

Description

Technical Field

[0006] , ,

[0001] The technology disclosed herein belongs to the technical field of a drive recording display system and a drive recording display method for recording video data during vehicle driving.

Background Art

[0002] In recent years, cameras (hereinafter referred to as "in-vehicle cameras") for capturing video data within a predetermined range inside and outside the vehicle during vehicle driving have been arranged in vehicles for purposes such as a drive recorder, a driving support system, and grasping the driver's state.

[0003] As a technology for effectively utilizing in-vehicle cameras, Patent Document 1 is known. In the technology of Patent Document 1, captured image data and captured location data captured by in-vehicle cameras are collected from a plurality of vehicles and provided in a form that can be browsed by a terminal device.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] By the way, generally, a drive recorder does not have a function of determining the start or end of a drive. Then, when utilizing the video content captured by the drive recorder for creating a memory movie or the like, the user needs to perform an operation for starting or ending drive recording every time the drive starts or ends. However, the user may forget to perform the operation for starting or ending drive recording, and since an operation is required every time of driving, there is room for improvement in terms of convenience.

[0006] The technology disclosed herein was developed in view of these points and aims to improve the convenience of the drive record display system. [Means for solving the problem]

[0007] To solve the aforementioned problems, a first aspect of the technology disclosed herein relates to a drive record display system for displaying a record of a vehicle's drive, comprising an information terminal owned by the vehicle's user and a content management server having storage and capable of communicating with the information terminal, wherein the content management server receives positioning data acquired at predetermined intervals by a positioning system installed in the vehicle and video data captured by a camera installed in the vehicle when the vehicle's drive begins, and stores them in the storage as a record of the vehicle's drive, and transmits display data based on the positioning data and video data to the information terminal, the information terminal displays a screen showing the vehicle's driving status based on the display data on a lower layer of the display screen, the content management server transmits a drive completion notification to the information terminal indicating that the vehicle's drive has ended after the state changes from receiving the positioning data or video data to not receiving it, and when the information terminal receives the drive completion notification, it displays a reception image on an upper layer superimposed on a part of the lower layer of the display screen to accept an operation for a request to create or edit the drive record.

[0008] In the drive record display system according to the above embodiment, upon the start of a vehicle drive, positioning data acquired at predetermined intervals by a positioning system installed in the vehicle and video data captured by a camera installed in the vehicle are received and stored in storage as a record of the vehicle's drive. Furthermore, the system automatically determines the end of the drive based on the reception status of the positioning data or video data, and displays a reception image that accepts the operation of a drive record creation request or editing request. This allows the drive record from the start to the end of the drive to be saved without any special operation by the user. Also, since the reception image is automatically displayed when the drive ends, the user can easily request the creation of a drive record or move to the drive record editing screen and start editing immediately. This allows the drive record to be created and edited while the drive memory is still fresh, so that the latest and most realistic information can be reflected. In other words, user convenience can be enhanced.

[0009] In a second aspect of the technology disclosed herein, in the first aspect, the display data includes vehicle trajectory data on map data generated based on the positioning data, the information terminal displays a drive map screen on the lower layer, which includes a display of the vehicle's driving status with the trajectory data superimposed on the map data, and when the drive completion notification is received, the reception image is displayed so as to overlap a part of the drive map screen.

[0010] In the second embodiment, the reception image is displayed with the drive map screen visible in the background, providing the user with reference information when considering whether to create or edit a drive record, thus increasing convenience.

[0011] In a third aspect of the technology disclosed herein, in the second aspect, the information terminal transitions to a settings screen related to a request to create a record on the drive when an input operation related to the request to create a record on the drive is detected in the received image.

[0012] As in the third embodiment, the use of a settings screen increases the degree of freedom users have in configuring settings, thereby improving convenience.

[0013] In a fourth aspect of the technology disclosed herein, in the first aspect, when the information terminal detects an input operation relating to a request to create a record of the drive in the received image, it automatically sends the creation request to the content management server without transitioning to a settings screen relating to the creation request.

[0014] According to the fourth aspect, users can easily request the creation and editing of drive records after the drive has finished, making it highly convenient.

[0015] A fifth aspect of the technology disclosed herein is a drive record display method for displaying a record of a vehicle's drive, wherein a content management server having storage and capable of communicating with an information terminal receives positioning data acquired at predetermined time intervals by a positioning system installed in the vehicle and video data captured by a camera installed in the vehicle when the vehicle's drive begins, and stores them in the storage as a record of the vehicle's drive, and transmits display data based on the positioning data and video data to the information terminal, the information terminal displays a screen showing the vehicle's driving status based on the display data on a lower layer of the display screen, the content management server transmits a drive completion notification to the information terminal indicating that the vehicle's drive has ended after the state of receiving the positioning data or video data changes from a state of receiving to a state of not receiving, and when the information terminal receives the drive completion notification, displays a reception image on an upper layer superimposed on a part of the lower layer of the display screen to accept an operation for a request to create or edit the drive record.

[0016] As a result, similar to the first aspect, drive records from the start to the end of a drive can be saved without any special operations by the user. Also, since the drive memory is in a new state and the user can create and edit drive records, the latest and real information can be reflected, enhancing the convenience for the user.

Effect of the Invention

[0017] According to the technology disclosed herein, in a drive record display system that displays drive records of a vehicle, the end of a drive is automatically determined, and an acceptance image for accepting an operation of a drive record creation request or an edit request is automatically displayed on the upper layer of an information terminal, thus enhancing the convenience for the user.

Brief Description of the Drawings

[0018] [Figure 1] Conceptual diagram schematically showing a configuration example of a drive record display system [Figure 2] Block diagram showing an example of the configuration of a content management server [Figure 3] Diagram for explaining data stored in a storage [Figure 4] Diagram showing an example of content information [Figure 5] Block diagram showing an example of the configuration of a drive recorder and an in-vehicle system [Figure 6] Block diagram showing an example of the configuration of a device management server [Figure 7] Conceptual diagram showing an example of the configuration of a network [Figure 8] Block diagram showing an example of the configuration of an information terminal [Figure 9] Flowchart for determining the start and end of a drive [Figure 10] Flowchart showing event determination processing and message sending processing [Figure 11] Flowchart showing an example of video data acquisition processing and storage processing [Figure 12] A flowchart showing an example of an operation for causing an information terminal to display travel history information [Figure 13] A diagram showing an example of a screen display of a mobile application related to drive start [Figure 14] A diagram showing an example of a drive log screen of a mobile application [Figure 15] A diagram showing an example of a drive map screen of a mobile application [Figure 16] A flowchart showing an example of an operation related to drive end determination [Figure 17] A diagram showing an example of a screen display of a mobile application related to drive end [Figure 18] A diagram showing an example of a setting screen for creating or editing a drive record

Embodiments for Carrying Out the Invention

[0019] Hereinafter, exemplary embodiments will be described in detail with reference to the drawings. The same or corresponding parts in the drawings are denoted by the same reference numerals, and repeated explanations may be omitted. Also, in the following embodiments, the description will focus on the configurations highly relevant to the content of the present disclosure.

[0020] The following embodiments are illustrative, and there is no intention to limit the content of this disclosure by the presence or absence of descriptions or by the numerical values ​​provided as examples. Furthermore, the components constituting the systems, servers, etc., described herein, and the functions realized by the components such as functional blocks and modules described herein, may be implemented in circuitry or processing circuitry, including general-purpose processors such as CPUs (Central Processing Units) and GPUs (Graphics Processing Units), application-specific processors, integrated circuits, ASICs (Application Specific Integrated Circuits), conventional circuits, and / or combinations thereof, programmed to realize the described functions. A processor includes transistors and other circuits and is considered circuitry or processing circuitry. A processor may be configured to execute a program stored in memory. Memory includes, for example, volatile memory such as RAM, and non-volatile memory such as ROM and flash memory.

[0021] Figure 1 shows an example configuration of a drive recording and display system M according to the first embodiment. The drive recording and display system M includes a content management server 1 that records video data while a vehicle Q (e.g., an automobile) is in motion. As mentioned above, the functions of the content management server 1 described below can be implemented in a processor, integrated circuit, conventional circuit, circuitry, or processing circuitry that performs specific functions by executing instructions (e.g., programs) stored in memory or the like that can be read by a computer, and by executing predetermined processing steps.

[0022] (1) Content management server Figure 2 shows an example configuration of the content management server 1. As shown in Figures 1 and 2, the content management server 1 comprises a device gateway 2, a content manager 3, a backend for frontend (BFF) 4, a messaging basis 11, and a set of functions 14. The content management server 1 is a cloud-type server that receives and manages event notifications or content data Dc from vehicles Q (Q1, Q2, Q3, ...).

[0023] Content management server 1 may be configured to automatically link predetermined data using technologies such as API integration or SFTP integration. While a detailed explanation is omitted as it is outside the scope of the disclosed technology, content management server 1 consists of hardware such as a processor, memory, and storage, and software such as control programs and data implemented in memory. The various functions of content management server 1 described later are realized by the execution of programs stored in memory by a processor such as a CPU or GPU. Note that content management server 1 is not limited to a cloud server; an on-premises server may also be used.

[0024] The following describes the configuration of content management server 1.

[0025] (1-2) Device Gateway As shown in Figure 2, the device gateway 2 comprises a communication interface 21, an event determination unit 22, and a transmission unit 23.

[0026] The communication interface 21 is a circuit or device connected to a network such as the Internet, for communicating with other computers, servers, information terminals, etc.

[0027] The communication interface 21 is connected to the Internet Network (see Figure 7) and communicates with the device management server 5 via the Internet Network. The communication interface 21 receives event notifications and content data Dc from the device management server 5. Event notifications include, for example, notifications that content data Dc (video data Dv1 and / or positioning data Dp) has been acquired. The content data Dc includes positioning data Dp acquired at predetermined intervals by the positioning system 65 installed in the vehicle Q, and video data Dv1 captured by the camera 61 installed in the vehicle. The positioning system and camera installed in the vehicle Q will be described later along with other components of the vehicle Q.

[0028] Content management server 1 may be linked with device management server 5 for data exchange. In this case, when content data Dc is transmitted from a designated vehicle Q to device management server 5, device management server 5 transmits the content data Dc of that vehicle Q to content management server 1. As described above, content data Dc includes positioning data Dp and video data Dv1. For example, positioning data Dp and video data Dv1 are received by content management server 1 as separate files.

[0029] The following provides a more detailed explanation of the data included in content data Dc.

[0030] -Positioning data- Positioning data Dp is positioning information of vehicle Q at a predetermined time, and includes, for example, the date of acquisition of positioning information (data acquisition date), the time of acquisition of positioning information (data acquisition time), the location information of vehicle Q (e.g., latitude and longitude), the direction of travel information of vehicle Q, the direction and bearing information, the speed of vehicle Q, and some or all of the identification ID. Positioning data Dp is transmitted from device management server 5 to content management server 1 as a separate file from video data Dv1, for example. The file format of positioning data Dp is not particularly limited, but for example, it is a text file conforming to the NMEA format.

[0031] -Video Data- As described above, video data Dv1 is video data captured by a camera (hereinafter referred to as "in-vehicle camera") located on vehicle Q. In the drive recording display system M, the video data Dv1 to be recorded is not particularly limited. Video data Dv1 includes either still images, videos (including those captured in time lapse), or both. Video data Dv1 may also include audio. For example, video data Dv1 may include "video data of a predetermined range outside the vehicle (e.g., a predetermined range in the direction of travel of the vehicle) captured by an in-vehicle camera while the vehicle is in motion and linked to positioning data", "video data of the outside or inside of the vehicle captured based on input received directly or indirectly from the driver and / or passengers", "video data of the outside or inside of the vehicle automatically captured when a specific location or condition is observed by a sensor, etc.", and "time lapse video data of the outside of the vehicle captured semi-automatically and continuously". Examples of specific states include, for instance, "a state where the atmosphere inside the vehicle is lively" or "a state where scenery or buildings in a tourist area are within the camera's frame." For the sake of explanation, when the driver and passengers are not specifically distinguished, the driver and passengers may be collectively referred to as "User U of Vehicle Q" or simply "User U." Positioning data Dp linked to video data Dv1 only needs to be related to each other; for example, positioning data Dp at the time video data Dv1 was taken can be said to be positioning data Dp linked to video data Dv1.

[0032] The camera that captures the video data Dv1 includes a camera positioned in vehicle Q that captures a predetermined area outside the vehicle (also simply called "outside the vehicle") (hereinafter referred to as the "external camera") and a camera positioned in vehicle Q that captures a predetermined area inside the vehicle (hereinafter referred to as the "interior camera"). For example, examples of cameras positioned in a vehicle include "an external camera that captures the area in front of or behind vehicle Q for use as a drive recorder," "an external camera that captures the area outside the vehicle for automatic vehicle control such as ADAS," "an interior camera that captures the driver for driver status confirmation and driving assistance," and "an interior camera that captures the interior of the vehicle to capture the atmosphere and conditions inside the vehicle." A camera provided in a drive recorder may be, for example, "a camera provided in a dedicated drive recorder device," or "a camera provided in an information terminal owned by user U when an application that functions as a drive recorder is installed on the information terminal and positioned in vehicle Q for operation."

[0033] -Other Content Data- Content data Dc may include data other than video data Dv1 and positioning data Dp. Content data Dc may include, for example, "audio data acquired by a microphone placed inside the vehicle's cabin" or "a file or data in a specific format created by a specific application."

[0034] The event determination unit 22 determines events occurring within the vehicle based on content data Dc. The events determined by the event determination unit 22 include drive-related events such as vehicle location information and the drive route (start of drive to arrival at destination), and in-vehicle events related to events inside the vehicle during the drive. In this disclosure, “drive” refers to a route from a predetermined first point to a predetermined second point. For example, it may be a route from a departure point (corresponding to the first point) to a destination point (corresponding to the second point) in a trip, or it may be a route from the departure point (corresponding to the first point) via one or more destination points to the final destination or return to the departure point (corresponding to the second point).

[0035] The video data Dv1 is linked to the positioning data Dp and includes driving video data captured using an external camera to photograph the area in front of vehicle Q while vehicle Q is in motion. The event determination unit 22 determines, for example, that a vehicle Q drive start event has occurred when it starts receiving positioning data Dp or driving video data. The event determination unit 22 then determines that a vehicle drive end event has occurred when, for example, the positioning data Dp or video data Dv changes from a received state to a not received state. The method for identifying the no-reception state is not particularly limited. For example, it may be determined that a no-reception state has occurred when a predetermined time has elapsed since the no-reception state began, or it may be determined that the no-reception state has occurred when a flag, signal sequence, specific pattern, etc., indicating that a no-reception state has occurred is received. The predetermined time here is not particularly limited and may be set in advance or configured to be changeable. The event determination unit 22 may determine that a vehicle Q drive start (restart) event has occurred if, after a predetermined period of time or longer has elapsed during which positioning data Dp or video data Dv1 has not been received via the communication interface 21, the unit begins receiving positioning data Dp or video data Dv1 again.

[0036] The "predetermined time" for determining the occurrence of drive start and drive end events is not particularly limited. The "predetermined time" may be set in advance, or it may be configured to be set and changed externally. Furthermore, the event determination unit 22 may be configured to accept input from an information terminal held by user U via the Internet NW, and user U may be able to set or change the "predetermined time" via that information terminal. The drive start and drive end determination flow in the event determination unit 22 is shown in Figure 9 and will be explained in more detail later.

[0037] The transmission unit 23 transmits part or all of the content data Dc received via the communication interface 21 to the content management unit 3. In this example, video data Dv1 is transmitted from the transmission unit 23 to the content management unit 3 as content data Dc. As will be explained in detail later, the video data Dv1 transmitted from the transmission unit 23 to the content management unit 3 is stored in the storage 33. At this time, a content ID is assigned as an identifier to each piece of content data Dc.

[0038] The transmission unit 23 transmits topic information Dm (see Figure 1), which is the key to sending and receiving messages, to the event hub 12 of the messaging infrastructure 11. The topic information Dm includes, for example, "positioning data Dp", "simple location information obtained from positioning data Dp", "content ID of video data Dv1 to video data Dv2 (described later)", "storage information indicating that video data Dv1 to video data Dv2 with the assigned content ID has been stored in the storage 33 of the content management unit 3", "information of an event determined by the event determination unit 22", "status notification from the device management server 5", and "information on user usage cooperation". Information of an event determined by the event determination unit 22 is transmitted, for example, embedded in the header of the message router 13. If drive start and drive end events are received externally via the communication interface 21, the transmission unit 23 may also transmit the information of the received events to the event hub 12 as the topic information described above. The topic information Dm is used by the message router 13, described later, to determine which function or service application module (hereinafter simply referred to as "application module" (indicated as "function" in the diagram)) to which it should send a message.

[0039] (1-3) Messaging infrastructure The messaging infrastructure 11 comprises an event hub 12 and a message router 13. The messaging infrastructure 11 is a messaging system used for sending and receiving messages to and from the application module 15, and for exchanging messages between the application modules 15. The application module 15 will be described later.

[0040] The event hub 12 obtains topic information Dm from the transmission unit 23. As mentioned above, the topic information Dm includes "positioning data Dp", "content IDs of video data Dv1 and Dv2", and "information about the event determined by the event determination unit 22". The topic information Dm obtained by the event hub 12 is passed to the message router 13.

[0041] The message router 13 determines which application module 15 to send the message (each topic information Dm) to and passes it back to the event hub 12. The event hub 12 distributes each topic information Dm to the application module 15 according to the decision made by the message router 13.

[0042] (1-4) Functional Groups Function group 14 includes application modules 15 for realizing various functions and services. Application modules 15 include memory for storing application programs and a processor for executing those application programs. In application modules 15, for example, various functions are realized when the processor executes the application programs stored in memory. When an application module 15 receives topic information Dm, it performs processing according to the function it realizes. Examples of functions realized in function group 14 include, for example, "user information management function," "drive log management function," "video data management function," and "memory movie creation and editing function."

[0043] More specifically, an example of the application module 15 that implements the function of creating and editing memory movies will be described. Based on the positioning data Dp and the event information determined by the event determination unit 22, the application module 15 identifies a content ID related to a common drive from among the content IDs. Then, it obtains video data Dv1 and Dv2, to which the identified content ID has been assigned, from the content management unit 3 (described later), and creates a short movie based on the video data Dv1 and Dv2. In the following description, video data Dv1 and video data Dv2 (described later) may be referred to collectively as video data Dv. In other words, video data Dv includes at least one of video data Dv1 and Dv2.

[0044] Furthermore, based on messages received by the messaging infrastructure 11, various processing requests may be sent from the event hub 12 to the application module 15. Examples of processing requests include, for example, "a request to create a new record to the drive log management function when a drive start event occurs," and "an instruction to the drive log management function to retrieve the drive end point from the storage 33 when a drive end event occurs."

[0045] The application module 15, which generates a driving trajectory as one of the drive record management functions, generates vehicle driving trajectory data RT on map data MP based on positioning data Dp. Specifically, the application module 15 identifies the position of vehicle Q from the acquired positioning data Dp and draws a line connecting the previously acquired position of vehicle Q and the currently acquired position of vehicle Q. The starting point of the driving trajectory is the point where the event determination unit 22 determines that the drive has started. The ending point of the driving trajectory is the point where the event determination unit 22 determines that the drive has ended. The driving trajectory is continuously generated and updated as long as the vehicle Q is driving. That is, as long as the vehicle Q is driving, the driving trajectory from the starting point of the drive to the point where the vehicle is currently driving (hereinafter also referred to as the "current location" for convenience) is generated and updated. The updated driving trajectory data RT is transmitted to BFF4. The method of acquiring map data MP is not particularly limited. For example, location information may be provided to a platform that provides digital maps, and map data MP corresponding to the provided location information may be acquired.

[0046] (1-5) Content Management Department The content management unit 3 comprises a communication interface 31, a content processing unit 32, and storage 33. The components of the content management unit 3 will be described in detail below.

[0047] The communication interface 31 is a circuit or device connected to a network such as the Internet, for communicating with other computers, servers, information terminals, etc. In this embodiment, the communication interface 31 is connected to the Internet NW (see Figure 7) and communicates with the information terminal 8 via the Internet NW. The communication interface 31 also communicates with the communication interface 21 of the device gateway 2 within the content management server 1. The communication interface 31 communicates with the information terminal 8 owned by user U of vehicle Q and receives video data Dv2 captured by the camera 81 of the information terminal 8 from the information terminal 8. The information terminal 8 will be described later.

[0048] Storage 33 is a recording medium intended for long-term storage of digital data, and examples include magnetic recording media such as HDDs (Hard Disk Drives), semiconductor recording media such as SSDs (Solid State Drives), and optical recording media such as DVDs. Storage 33 may also be a distributed storage system, meaning the data to be stored may be distributed. As mentioned above, "content files" and "content information" are stored separately in storage 33. Storage 33 includes, for example, a first area 33a where "content information" is stored and a second area 33b where "content files" are stored. Figure 3 shows an example of data stored in the first area 33a and second area 33b of storage 33, and Figure 4 shows an example of content information. In this embodiment, an example of content information being stored in a table format is shown, but the storage format is not particularly limited and may be other formats, such as a tree format.

[0049] In this embodiment, an example is described in which video data Dv from the first drive D1 and the second drive D2 are stored in storage 33. The video data Dv from the first drive D1 includes video data 11 to 15, numbered No. 11 to No. 15, and the video data Dv from the second drive D2 includes video data 21 to 25, numbered No. 21 to No. 25. In the example in Figures 3 and 4, video data 11, 12, 15, 21, 23, and 25 are time-lapse videos taken at predetermined intervals by the drive recorder 6's camera 61 (external camera) during normal driving of vehicle Q, and are examples of video data Dv1 and examples of normal driving video data. Video data 13 and 24 are still images or videos taken by the drive recorder 6's camera 61 (internal or external camera) within drives D1 and D2 of vehicle Q, and are examples of video data Dv1 and examples of event video data. Video data 14 and 22 are still images or videos captured by the camera 81 of the information terminal 8 during vehicle Q's drives D1 and D2, and are examples of video data Dv2 and event video data. Normal driving video data refers to video data captured at predetermined intervals during normal driving of vehicle Q. Event video data, unlike normal driving video data, is video data captured based on predetermined inputs.

[0050] The content processing unit 32 assigns a content ID to the video data Dv1 received from the device gateway 2 and stores the content ID in the first area 33a of the storage 33. The content processing unit 32 saves the content file of the video data Dv1 to the second area 33b. The content processing unit 32 executes a process to obtain the content information of the video data Dv1. The content information is linked to the corresponding content ID and stored in the first area 33a of the storage 33. The content ID is sent to the messaging infrastructure 11 as topic information Dm via the device gateway 2.

[0051] The content processing unit 32 assigns a content ID to the video data Dv2 received from the information terminal 8. The content ID is stored in the first area 33a of the storage 33. The content processing unit 32 saves the content file of the video data Dv2 to the second area 33b. The content processing unit 32 executes a process to obtain content information of the video data Dv2 from the video data Dv2 or the metadata of the video data Dv2. It is saved in association with the content ID corresponding to the first area 33a of the storage 33. The content information is saved in association with the corresponding content ID to the first area 33a of the storage 33. The content ID is sent to the messaging infrastructure 11 as topic information Dm via the device gateway 2.

[0052] Furthermore, when event video data is received as video data Dv1, the content processing unit 32 may generate accompanying video data and save the content files of the event video data and the accompanying video data in the second area 33b of the storage 33. The accompanying video data is not particularly limited, but for example, it is a thumbnail of the event video data. The path of the accompanying video data is saved in the first area 33a of the storage 33 as content information of the original event video data. In the example in Figures 3 and 4, two thumbnails (video data 131, 132) are generated for video data 13, which is event video data. Video data 131 and 132 are, for example, thumbnails of different sizes. In the example in Figure 4, thumbnails are generated for video data 13, 22, and 24, which are event video data.

[0053] In summary, the content management unit 3 integrates the video data Dv1 received via the communication interface 21 and the video data Dv2 received via the communication interface 31 and stores them in the storage 33. As a result, video data Dv1 and Dv2 are centrally managed by the content management unit 3.

[0054] (1-6)BFF(Backend for frontend) As shown in Figure 2, the BFF4 comprises a communication interface 41 and a command processing unit 42. The BFF4 functions as a data exchange window with a mobile application (hereinafter referred to as "mobile app") implemented on the information terminal 8. Specifically, the communication interface 41 receives and processes commands from the mobile app implemented on the user U's information terminal 8. For example, the BFF4 obtains the shooting location of the event video and a thumbnail of the event video from the storage of the content management unit 3, and transmits them to the information terminal 8 as display data V, along with the driving trajectory data received from the application module 15.

[0055] The communication interface 41 is a circuit or device connected to a network such as the Internet, for communicating with other computers, servers, information terminals, etc. In this example, the communication interface 41 is connected to the Internet NW (see Figure 7) and communicates with the information terminal 8 via the Internet NW. The communication interface 41 also communicates with the communication interface 31 of the content management unit 3 within the content management server 1. Although Figure 1 shows an example where video data Dv2 is directly transmitted from the information terminal 8 to the content management unit 3, the video data Dv2 may also be transmitted from the information terminal 8 to the content management unit 3 via the BFF 4.

[0056] The command processing unit 42 executes processing in response to commands from the mobile application on the information terminal 8. For example, the BFF4 receives commands from the mobile application such as "request to view drive logs and videos / still images," "request to create a memory movie," and "instruction to edit the drive log," and the command processing unit 42 executes processing in response to these commands. Specifically, when the command processing unit 42 receives a "request to create a memory movie" from the information terminal 8, it notifies the application module 15, which has a "memory movie creation function," receives the memory movie created by the application module 15, and sends it to the information terminal 8 (mobile application). Also, when the command processing unit 42 receives a command from the information terminal 8 to view drive logs and videos / still images, it retrieves the corresponding video / still image from the storage 33 and sends it to the information terminal 8.

[0057] (2) Device management server As shown in Figure 6, the device management server 5 comprises a communication interface 51, a content management unit 52, and storage 53 (for example, a recording medium such as an HDD). The device management server 5 acquires content data Dc (including positioning data Dp and video data Dv1) acquired by the managed drive recorder 6 through data exchange. Furthermore, for drive recorders 6 that are linked with the content management server 1, the device management server 5 exchanges the content data Dc acquired from that drive recorder 6 with the content management server 1.

[0058] The communication interface 51 is a circuit or device connected to a network such as the Internet, for communicating with other computers, servers, information terminals, etc. In the example in Figure 1, the communication interface 51 is connected to the Internet NW (see Figure 7) and communicates with the content management server 1 and the drive recorder 6 via the Internet NW. Data exchange with the drive recorder 6 and data exchange with the content management server 1 are performed via the communication interface 51.

[0059] The content management unit 52 manages the content data Dc in the storage 53. Specifically, it saves the content data Dc received from the managed drive recorder 6 to the storage 33. Figure 5 shows an example in which content data Dc is received from each of the vehicles Q (Q1, Q2, Q3, ...) and saved to the respective storage areas (53a, 53b, 53c) of the storage 53. It also retrieves the content data Dc to be transmitted from the storage 53 and sends it to the content management server 1 via the communication interface 51.

[0060] (3) Vehicles Next, the configuration of vehicle Q will be described with reference to Figure 5. In this example, vehicle Q is equipped with a general in-vehicle system 7, and a drive recorder 6 has been added later by user U.

[0061] (3-1) Dashcam The drive recorder 6 is a device that acquires driving log data of vehicle Q, and comprises a camera 61, an input unit 62, an output unit 63, a communication interface 64, a positioning system 65, and a storage unit 66. The drive recorder 6 acquires positioning data Dp using the positioning system and takes pictures of a predetermined range with the camera at predetermined times (at predetermined intervals), and transmits the acquired positioning data Dp and captured video data Dv1 to the device management server 5. The drive recorder 6 may be in the form of a dedicated drive recorder device for the purpose of acquiring driving log data, or it may be in the form of an information terminal such as a smartphone with a mobile application for acquiring driving logs installed and the information terminal used for drive recorder purposes.

[0062] Camera 61 includes a front camera that captures a predetermined range in front of the vehicle when the housing of the drive recorder 6 (not shown) is installed in a predetermined position on the vehicle (installation state). Alternatively, camera 61 may include a rear camera that captures a predetermined range behind the vehicle when the drive recorder 6 is installed, or it may include an interior camera that captures the interior of the vehicle Q to acquire interior video data. The video data Dv1 captured by camera 61 is linked to the positioning data Dp acquired by the positioning system 65 and stored in the storage unit 66.

[0063] The input unit 62 accepts various types of input. Specifically, the input unit 62 includes, for example, a microphone for acquiring audio from inside the vehicle and an operation reception unit for receiving input operations from user U. Examples of the operation reception unit include a push-button switch and a touch-sensor touch panel. Alternatively, user U's input operations may be accepted via voice recognition through the microphone. In other words, the microphone may also function as the operation reception unit. Furthermore, in this disclosure, the microphone located inside the vehicle may be a microphone that is standardly installed in the vehicle as part of the in-vehicle system 7, a microphone from an aftermarket device such as a drive recorder 6 that is retrofitted to the vehicle Q, or a microphone provided on an information terminal 8 that is brought into the vehicle by user U during driving.

[0064] The output unit 63 is used to output various types of information. Specifically, the output unit 63 may include, for example, a display panel that displays output information on a display screen, a speaker that outputs audio information, or a liquid crystal display unit that presents information by turning on or off.

[0065] The communication interface 64 is a circuit that is connected to the Internet network (see Figure 7) and communicates with the device management server 5 via the Internet network. The drive recorder 6 does not communicate with the communication interface of the in-vehicle system 7, which will be described later. Also, in this example, the communication interface 64 does not communicate with the communication interfaces 21, 31, and 41 of the content management server 1.

[0066] The positioning system 65 can use a conventionally known configuration (e.g., GPS), receive radio waves from satellites, and acquire positioning data Dp based on those satellite radio waves. As described above, the positioning data Dp is linked to the video data Dv1 captured by the camera 61 from the drive recorder and stored in the storage unit 66.

[0067] The storage unit 66 is composed of, for example, volatile memory such as RAM, and non-volatile semiconductor memory such as ROM or flash memory. The storage unit 66 stores the program for operating the drive recorder 6. The storage unit 66 also temporarily records positioning data Dp acquired by the positioning system 65 and video data Dv1 captured by the camera 61. The positioning data Dp acquired by the positioning system 65 and the video data Dv1 captured by the camera 61 are communicated with the device management server 5 via the communication interface 64.

[0068] (3-2) In-vehicle systems The in-vehicle system 7 is briefly described in parts relevant to the subject of the disclosed technology, while configurations less relevant to the subject of the disclosed technology are omitted from the description. In this example, the in-vehicle system 7 comprises an input unit 71, an output unit 72, a communication interface 73, a sensor group 74, a controller group 75, an actuator group 76, and a storage unit 77.

[0069] The input unit 71 accepts various types of input. Specifically, the input unit 71 includes, for example, a microphone for acquiring sound from inside the vehicle and an operation reception unit for receiving user U input operations. Examples of the operation reception unit include a push-button switch and a touch-sensor touch panel. Alternatively, user U input operations may be accepted via voice recognition through the microphone. In other words, the microphone may also function as the operation reception unit.

[0070] The output unit 72 is used to output various types of information. Specifically, the output unit 72 may include, for example, a display panel that displays output information on a display screen, a speaker that outputs audio information, or a liquid crystal display unit that presents information by turning on / off.

[0071] The communication interface 73 is a circuit or device connected to the Internet NW (see Figure 7) for communication with other computers, servers, information terminals, etc. In the example in Figure 1, the communication interface 73 does not communicate with the device management server 5, the drive recorder 6, or the content management server 1.

[0072] The sensor group 74 includes a camera 741 positioned on the vehicle and a positioning system 742 used for autonomous driving or driver assistance. The camera 741 includes an exterior camera that captures a predetermined area outside the vehicle and an interior camera that captures the inside of the vehicle. Although not shown, the exterior camera is composed of multiple cameras, for example, and the combined shooting ranges of each camera are arranged to capture a 360-degree area around the vehicle.

[0073] The controller group 75 consists of various controllers that control the in-vehicle system. The controller group 75 is composed of ECUs (Electronic Control Units) located in various places on the vehicle Q, and controls the actuator group 76 based on inputs from, for example, the input unit 71 and the sensor group 74. The controller group 75 may also include ADAS (Advanced driver-assistance systems) to support the driving of the vehicle Q. The actuator group 76 includes drive system actuators related to the driving of the vehicle Q, braking system actuators related to the braking of the vehicle Q, and steering system actuators related to the steering of the vehicle Q.

[0074] The memory unit 77 includes, for example, memory and storage. The memory includes, for example, volatile memory such as RAM and non-volatile memory such as ROM and flash memory. The storage includes, for example, magnetic recording media such as HDD (Hard Disk Drive), semiconductor recording media such as SDD (Solid State Drive), and optical recording media such as DVD. Positioning data Dp acquired by the positioning system 742 and video data Dv1 captured by the camera 741 are temporarily recorded in the memory unit 77.

[0075] (4) Information terminals As shown in Figure 8, the information terminal 8 includes a camera 81, a communication interface 82, an input unit 83, an output unit 84, and a storage unit 86.

[0076] Camera 81 is a camera mounted on the main body of the information terminal 8. It captures optical images and generates video data Dv2. The video data Dv2 is not particularly limited. The video data Dv2 may be a still image or a video. Camera 81 acquires the video data Dv2 upon request from user U. Multiple cameras 81 may be provided on the information terminal 8.

[0077] The communication interface 82 is connected to the internet and communicates with the content management server 1. The communication interface 82 transmits video data Dv2 and positioning data Dp captured by the camera 81 to the content management server 1. The communication interface 82 transmits commands from the mobile application to the content management server 1. The communication interface 82 obtains the location information of vehicle Q from the content management server 1 at predetermined intervals. The predetermined interval is not particularly limited, but for example, it is 1 second. It receives memory information transmitted from the content management server 1.

[0078] The input unit 83 accepts various inputs from user U. The input unit 83 includes a push-button switch, a touch-sensor touch panel, and a microphone for acquiring user U's voice.

[0079] The output unit 84 is used to output various types of information. Examples of the output unit 84 include a display panel that displays output information on a display screen, and a speaker that outputs audio information. If the input unit 83 is configured as a touch panel, the output unit 84 and the input unit 83 are configured as the same panel. The output unit 84 reflects the location information and driving trajectory of vehicle Q received from the content management server 1 into map data and displays it together with the map image. The output unit 84 also displays memory information received from the content management server 1.

[0080] The storage unit 86 is composed of, for example, volatile memory such as RAM, and non-volatile semiconductor memory such as ROM or flash memory. The storage unit 86 stores the video data Dv2 and positioning data Dp acquired by the camera 81. The video data Dv2 and positioning data Dp stored in the storage unit 86 are transmitted to the content management server 1 via the communication interface 82.

[0081] (5) Operation of the drive record display system The drive record display system M operates by downloading a mobile application for using the drive record display system M to the information terminal 8 and operating the mobile application on the information terminal 8.

[0082] As part of the initial setup of the mobile app, user U pre-registers information identifying the drive recorder 6 installed in their vehicle Q (manufacturer, model, ID, name of vehicle Q, etc.) with the content management server 1 via the information terminal 8. The content management server 1 identifies the device management server 5 for the drive recorder of that manufacturer and model, and communicates with this device management server 5. The content management server 1 receives video data Dv1 recorded by the drive recorder with the ID registered by user U from the device management server 5. When user U changes the drive recorder 6 in their vehicle Q, they register information identifying the new drive recorder 6 (manufacturer, model, ID, name of vehicle Q, etc.) with the content management server 1 via the information terminal 8. The content management server 1 then identifies the device management server 5 for the new drive recorder and communicates with this device management server 5. The content management server 1 receives video data Dv1 recorded by the drive recorder with the ID registered by user U from the new device management server 5.

[0083] Next, we will explain the sequence of operations of the drive recording and display system M, from the start of the drive to the end of the drive.

[0084] (5-1) Start and end of drive Figure 9 describes the drive start and drive end determination operations and processing. In Figure 9, the initial state is after the drive end determination, and the content management server 1 has not received positioning data Dp.

[0085] When the vehicle Q is powered on, power is supplied to the drive recorder 6, and the drive recorder 6 turns on. The drive recorder 6 starts recording with the camera 61 and acquiring positioning data Dp with the positioning system 65. When the drive recorder 6 is powered on, the drive recorder 6 and the device management server 5 begin coordinating. The drive recorder 6 exchanges data with the device management server 5, including video data Dv1 recorded by the camera 61 and content data Dc, which includes positioning data Dp acquired by the positioning system 65.

[0086] When data is exchanged between the drive recorder 6 and the device management server 5, data exchange between the device management server 5 and the content management server 1 begins. When the device management server 5 receives content data Dc (including video data Dv1 and positioning data Dp) from the drive recorder 6, which is the target of data exchange with the content management server 1, it sends an event notification to the content management server 1.

[0087] In step S11, when the content management server 1 receives positioning data Dp from the device management server 5, in step S12, the content management server 1 determines that a drive has started. The positioning data Dp includes positioning data Dp associated with video data Dv1. In other words, the positioning data Dp may be included in the content data Dc, or it may be received as positioning data Dp on its own.

[0088] Next, in step S13, the content management server 1 determines whether the state in which positioning data Dp has not been received at the device gateway 2 (hereinafter referred to as "non-reception state") has exceeded a predetermined time. If the duration of the non-reception state of positioning data Dp is less than or equal to the predetermined time (NO), the content management server 1 determines in step S15 that the drive is continuing. On the other hand, if the duration of the non-reception state of positioning data Dp is longer than or equal to the predetermined time (YES), the content management server 1 determines in step S14 that the drive has ended.

[0089] The "predetermined period" for determining the occurrence of drive start and drive end events is not particularly limited. The "predetermined period" may be set in advance, or it may be configured to be set and changed externally. In addition, the content management server 1 may allow user U to set or change the "predetermined period".

[0090] (5-2) Acquisition and storage of video data Figure 10 is a flowchart showing an example of the video data acquisition and saving process. This flowchart is executed repeatedly from the time the drive starts until it continues to run.

[0091] When the vehicle Q is powered on, power is supplied to the drive recorder 6 and the drive recorder 6 starts operating. Specifically, the drive recorder 6 starts taking pictures with the camera 61 and acquiring positioning data Dp with the positioning system 65. The drive recorder 6 exchanges data with the device management server 5, including the video data Dv1 taken by the camera 61 and the content data Dc which includes the positioning data Dp acquired by the positioning system 65.

[0092] When the device management server 5 receives content data Dc (including video data Dv1 and positioning data Dp) from the drive recorder 6, which is the target of data exchange with the content management server 1, it sends an event notification to the content management server 1.

[0093] In step S21 of Figure 10, when the device gateway 2 receives an event notification from the device management server 5, it determines whether the event notification is for the acquisition of video data Dv1 (S22). The device gateway 2 also performs additional event determination processing and message sending processing (S24). In the example in Figure 9, the processing of steps S22 and S24 is described in parallel, but steps S22 and S24 may be processed in series. For example, the processing of step S24 may be performed after the processing of step S22, or the processing of step S22 may be performed after the processing of step S24.

[0094] In step S22, if the event notification is related to the acquisition of video data Dv1 (YES in S22), the content management server 1 executes the video data Dv1 acquisition and saving process in step S23. In the flowchart, the process proceeds to step S32 in Figure 11.

[0095] Figure 11 is a flowchart showing an example of the video data acquisition and storage process.

[0096] In step S32, the device gateway 2 requests the device management server 5 to acquire video data Dv1. The device management server 5 then sends video data Dv1 to the device gateway 2, and the device gateway 2 receives the video data Dv1 (S33). At this time, the positioning data Dp and the video data Dv1 associated with the positioning data Dp are received separately. Note that the timing at which the positioning data Dp and video data Dv1, which are associated with each other, are received does not need to be the same; they may be received at different times. The video data Dv1 received by the device gateway 2 is sent to the content management unit 3, and the positioning data Dp is sent to the event hub 12 as topic information Dm. Note that the determination of drive start may be performed by the device gateway 2 when the positioning data Dp is received, or it may be performed by the application that receives the topic information Dm. The same applies to the determination of drive end.

[0097] In step S34, the content management unit 3 determines whether the received video data Dv1 is a normal driving image (e.g., a time-lapse video) taken during normal vehicle driving, or an event video taken based on a predetermined input at a different timing than the normal driving image.

[0098] In step S34, if the video data Dv1 is a normal driving image, the flow proceeds to step S35. In step S35, the content management unit 3 assigns a content ID to the video data Dv1 and sends the content ID to the device gateway 2. The content ID of the video data Dv1 received by the device gateway 2 is sent to the event hub 12 as topic information Dm. Once the security of the data is confirmed, the content management unit 3 saves the video data Dv1 to the second area 33b of the storage 33. The content management unit 3 also acquires the content information of the video data Dv1. The acquired content information is linked to the content ID created earlier and saved to the first area 33a of the storage 33. A specific example of content information is shown in Figure 4.

[0099] In step S34, if the video data Dv1 is event video data, the flow proceeds to step S36. In step S36, the same processing as in step S35 is performed. In the next step S37, the content management unit 3 creates additional content based on the video data Dv1. The additional content is not particularly limited, but for example, it may be a thumbnail of the video data Dv1. The path of the additional content is stored in the first area 33a of the storage 33, and the video data of the additional content is stored in the second area 33b of the storage 33. Note that the processing in steps S36 and S37 may be executed in parallel.

[0100] (5-3) Displaying the drive map screen Figure 12 is a flowchart illustrating an example of the operation in which the driving map screen of vehicle Q is displayed on the information terminal 8 as the driving status of vehicle Q while vehicle Q is being driven.

[0101] -Startup process and display of past drive records- When user U wants to display the drive map screen of vehicle Q while driving vehicle Q, they perform an input operation on the information terminal 8 to launch the mobile application for displaying the drive map (hereinafter simply referred to as "mobile application"). Then, as part of the launch process, the information terminal 8 displays the launch screen of the mobile application on the display screen W (hereinafter simply referred to as "display screen W") (step S41). Figure 13 shows an example of the information terminal screen display when the mobile application is launched. In Figure 13, the left figure shows the launch state before starting to drive vehicle Q.

[0102] The startup screen of a mobile app is not particularly limited, but for example, multiple navigation bars N are displayed. The configuration of navigation bars N is not particularly limited, but this example shows an example where navigation bars N1 and N2 are displayed on the startup screen. Navigation bar N1 is located at the bottom of the display screen W, and multiple operation icons are arranged horizontally on the screen. In Figure 13, examples of icons for tap operation include a drive icon for displaying drive information, a media icon for accessing media such as video content, a notification icon for checking notification information, and a settings icon for making various settings. Navigation bar N2 is located in the center of the display screen W and is arranged vertically on the screen. Navigation bar N2 displays information that allows the user to identify registered drive records, for example. In the example in Figure 13, for each registered drive record, the date of the drive, the start and end points of the drive, the start and end times of the drive, and the drive distance are displayed. Note that navigation bar N2 only needs to allow the user U to identify the drive record. In other words, the displayed items are merely examples, and additional items may be displayed, or some of the displayed items may be omitted. When a tap operation by user U is received on any of the navigation bars N2, the system is configured to allow access to the corresponding drive record. That is, the corresponding drive record is displayed on the display screen W. Figure 14 is an example of a drive log screen that transitions from the state in Figure 13 based on a tap operation on the navigation bar N2. In the example screen in Figure 14, the date and time of the drive, the driving trajectory of vehicle Q, and a thumbnail P of the video data Dv are displayed. As shown in Figure 14, the drive map screen of vehicle Q may be displayed in its entirety on the lower layer L1 of the display screen W, and the date and time of the drive, the driving trajectory of vehicle Q, and the video data Dv may be displayed on the bottom sheet N5 as the upper layer L2, and the bottom sheet N5 may be configured to slide up and down. In this disclosure, the bottom sheet refers to an overlay placed at the bottom end of the display screen W that displays additional information (in this case, information related to the drive).

[0103] -Displaying the drive map screen while driving- In step S42 of Figure 12, when the content management server 1 determines that the vehicle Q (hereinafter simply referred to as "vehicle Q"), which is linked to the information terminal 8, has started driving (see step S12 in Figure 9), it notifies the information terminal 8 that the vehicle has started driving. In step S45, the content management server 1 executes the process described in "(5-2) Acquisition and saving of video data" above, and in step S46, it executes the process of generating the driving trajectory data RT. As described above, the process of generating the driving trajectory data RT is generated, for example, by the application module 15 for generating the driving trajectory data RT. The driving trajectory data RT is updated as needed while the vehicle Q is driving.

[0104] When the information terminal 8 receives notification that vehicle Q has started driving, it displays a navigation bar N3 indicating the start of driving on the startup screen of the display screen W (step S43). The display position of the navigation bar N3 is not particularly limited. The right-hand figure of Figure 13 shows an example of the display screen W after vehicle Q has started driving. In the example of Figure 13, the navigation bar N3 is displayed above the navigation bar N1 and superimposed in front of the navigation bar N2. In other words, the navigation bar N2 as the content screen of the mobile application is displayed on the lower layer L1, and the navigation bar N3 as a navigation image is displayed on the upper layer L2 superimposed on the navigation bar N2. The display items of the navigation bar N3 are not particularly limited, but for example, the region being driven, the driving time which is the elapsed time since the start of driving, an icon C1 indicating that driving is in progress, an arrow-shaped operation icon C2 that transitions to the drive map screen, and an operation icon C3 that accepts the selection operation of the shooting menu may be displayed.

[0105] In step S44, when the user U taps the operation icon C2, the information terminal 8 requests the content management server 1 to send display data V for displaying the drive map screen. When the content management server 1 receives the transmission request from the information terminal 8, it starts sending the display data V to the information terminal 8 (step S47). As described above, the display data V includes the shooting location and thumbnail of each video data Dv1, as well as the driving trajectory data RT.

[0106] In step S48, the information terminal 8 receives display data V. In step S49, based on the display data V, the information terminal 8 displays a drive map screen on the display screen W, in which map data MP and driving trajectory RT are overlaid. Furthermore, on the drive map screen, the information terminal 8 displays a thumbnail P at a position adjacent to the shooting location of the video data Dv1 on the map data MP. The transmission of display data V is repeated until a stop request is received from the information terminal 8 or until it is determined that the vehicle Q has finished driving. The method of repetition is not particularly limited, but for example, the display data V is updated at predetermined time intervals (for example, every second).

[0107] Figure 15 shows an example of the drive map screen of the mobile application related to the first drive described above. In Figure 15, the screens after 5 minutes, 20 minutes, 45 minutes, and 1 hour and 20 minutes from the start of the drive are shown from left to right. As shown in Figure 14, on the drive map screen, the map data MP, driving trajectory RT, and thumbnail P are displayed simultaneously on a single screen on the display screen W of the information terminal 8. In Figure 15, the information terminal 8 displays the drive map screen on the lower layer L1 of the display screen W. In addition, at the bottom of the display screen W, a bottom sheet N5 containing information such as the driving time and distance of the vehicle Q is displayed on the upper layer L2, superimposed on a part of the lower layer L1. Furthermore, on the bottom sheet N5 of the upper layer L2, a shooting icon is displayed to instruct the camera 61 of the drive recorder 6 to take a picture while the vehicle is in motion.

[0108] In summary, when vehicle Q starts driving, content management server 1 receives positioning data Dp acquired at predetermined intervals by positioning system 65 located on vehicle Q and video data Dv1 captured by camera 61 located on vehicle Q, and saves them to storage 33 as a record of vehicle Q's drive. Furthermore, content management server 1 transmits display data V based on positioning data Dp and video data Dv1 to information terminal 8. Based on the display data V received from content management server 1, information terminal 8 displays a screen showing the driving status of vehicle Q on a lower layer of display screen W. Here, an example is shown where the drive map screen is displayed as the screen showing the driving status of vehicle Q. The drive map screen displays map data MP, driving trajectory RT, and thumbnail P simultaneously on a single screen. Note that the screen showing the driving status of vehicle Q is not limited to the drive map screen; any image that shows the driving status of vehicle Q is acceptable. For example, images other than the drive map screen may be used, or the map data MP, driving trajectory RT, or thumbnail P may be omitted from the drive map screen.

[0109] -Drive termination detection- Figure 16 is a flowchart showing an example of the operation related to the determination of the end of a drive. Figure 17 shows an example of the screen transition at the end of a drive. In Figure 17, the left figure shows an example of the display screen W while the vehicle is in motion, and the right figure shows an example of the display screen W after the determination that the vehicle has ended its drive. The left figure of Figure 17 shows the display screen W after 1 hour and 20 minutes have elapsed in Figure 15, with the bottom sheet N5 slid upwards. The bottom sheet N5 displays drive information such as the driving area in which the vehicle is traveling, the starting point of the drive, the elapsed time since the start of the drive, the distance traveled since the start of the drive, and thumbnails of video data taken during the drive. On the other hand, the aforementioned reception image TB is not displayed on the bottom sheet N5 while the vehicle Q is in motion.

[0110] In step S51, when the content management server 1 determines that the vehicle Q (hereinafter simply referred to as "vehicle Q") which is linked to the information terminal 8 has finished driving (see step S14 in Figure 9), it notifies the information terminal 8 that the drive has finished.

[0111] In step S52, when the information terminal 8 receives a drive completion notification from the content management server 1, it displays a reception image TB on the upper layer L2 superimposed on a portion of the lower layer L1 of the display screen W. The reception image TB is an image for accepting requests to create or edit drive records. The reception image TB may include operation icons for accepting various operations. Specifically, in the example in Figure 17, the information terminal 8 automatically slides the bottom sheet N5 further upward from the state shown in the left figure to display the reception image TB below the aforementioned drive information. In this example, the reception image TB includes a navigation bar TB1 for accepting requests to create memory movies, a navigation bar TB2 for accepting requests to create or edit log cards, and a navigation bar TB3 for accepting requests to view the photo library. Icons for accepting user U operations are displayed on each of the navigation bars TB1 to TB3. Memory movies, log cards, and photo libraries are examples of drive records.

[0112] In step S53, the information terminal 8 detects a tap operation by user U related to a request to create or edit a drive record. Then, in the next step S54, the information terminal 8 displays the corresponding setting screen W2 for creating or editing a drive record on the display screen W. Figure 18 shows an example of the log card setting screen W2 that is accessed when the "Create" icon on the navigation bar TB2 is touched in Figure 17. As shown in the right figure of Figure 18, the information terminal 8 may also display information about the most recent drive on the log card setting screen W2. This supports editing by user U. The information about the most recent drive is not particularly limited and should be content that allows user U to recall information about the most recent drive. In this example, the information about the most recent drive displayed is a thumbnail of the driving trajectory RT 101, origin and destination data 102, vehicle name data 103, mileage data 104, driving time data 105, and drive date data 106. In addition, the drive log title 110 is editable on the drive record setting screen W2. In other words, Figure 18 is the settings screen W2 related to the request to create a log card, and at the same time, it corresponds to the editing screen for editing the log card information. In this example, it shows an instance where user U entered "Family Trip During Golden Week" as the title 110 of the drive log, replacing the existing title (not shown).

[0113] In step S55, the information terminal 8 receives an operation related to the request to create a drive record. When the information terminal 8 detects an operation related to the request to create a drive record, it sends a drive record creation request to the content management server 1. To illustrate with a specific example, in the example in Figure 18, when the information terminal 8 detects a tap operation on the "Save" icon displayed at the bottom of the settings screen W2, it sends a drive log creation request to the content management server 1.

[0114] In step S56, when the content management server 1 receives a drive log creation request from the information terminal 8, it creates and saves the drive log. Specifically, the content management server 1 creates a drive log for the drive associated with the display data V that was sent immediately before the drive termination notification in the application of function group 14, and saves it to storage 33. Once the content management server 1 has finished creating the drive log, it sends a drive log creation completion notification to the information terminal 8.

[0115] In step S57, when the information terminal 8 receives a drive log creation completion notification, it displays the content based on the completion notification on the display screen W. In the example in Figure 18, an icon C5 with the message "Drive log created" is displayed at the top of the display screen W as the above content.

[0116] To summarize the operation in Figure 16, the content management server 1 sends a drive completion notification to the information terminal 8 indicating that the vehicle Q has finished driving, after the state changes from receiving positioning data Dp or video data Dv1 to not receiving. When the information terminal 8 receives the drive completion notification from the content management server 1, it displays a reception image TB on the upper layer L2 superimposed on a part of the lower layer L1 of the display screen W, which accepts the operation of a drive record creation request or editing request.

[0117] Note that steps S54 and S55 may be omitted in the flowchart of Figure 16. In this case, in step S53, when the information terminal 8 detects an operation for creating or editing a drive record, it sends a drive record creation request to the content management server 1 without displaying the settings screen W2. The subsequent processing is as described above. Specifically, in step S56, when the content management server 1 receives a drive record creation request from the information terminal 8, it creates and saves the drive record. When the content management server 1 has finished creating the drive record, it sends a drive record creation completion notification to the information terminal 8. In step S57, when the information terminal 8 receives the drive log creation completion notification, it displays the content based on the creation completion notification on the display screen W.

[0118] As described above, the drive record display system according to this embodiment automatically determines the end of the drive based on the reception status of positioning data Dp or video data Dv1, and displays a reception image to accept a request to create or edit the drive record. In other words, when the drive ends, user U can confirm the reception image for the drive record creation or editing request without any special operation, and immediately start the drive record creation request or editing operation. As a result, the drive record can be created and edited while the drive memory is still fresh, so the latest and most realistic information can be reflected. In other words, the convenience of user U can be enhanced.

[0119] The above describes embodiments as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited thereto and can be applied to embodiments that are modified, replaced, added, or omitted as appropriate. Furthermore, it is possible to combine the components described in the above embodiments to create new embodiments.

[0120] For example, in the above embodiment, the vehicle may be a bicycle, motorbike, railway vehicle, electric kick scooter, rickshaw, etc. When the vehicle is a bicycle, motorbike, or railway vehicle, the device capable of acquiring location information is, for example, a drive recorder. When the vehicle is an electric kick scooter, bicycle, or motorbike, the linking of the mobile terminal and the drive recorder can be done in the same manner as in the above embodiment. When the vehicle is a railway vehicle, the railway company approves the user registration when linking the mobile terminal and the drive recorder. When the vehicle is a rickshaw, for example, the camera placed on the vehicle is attached to the rickshaw. The device that acquires the vehicle's positioning data is not particularly limited. For example, it may be attached to the rickshaw, or it may also be an information terminal held by the rickshaw driver. In this case, the positioning data acquired by the positioning function of the information terminal held by the rickshaw driver may be used as the vehicle's positioning data. Alternatively, the information terminal held by a passenger riding in the rickshaw may also serve as the device that acquires the vehicle's positioning data.

[0121] Furthermore, as a reference example, the technology disclosed herein can also be applied to aircraft. When applied to aircraft, the device capable of acquiring location information is a flight recorder. In linking a mobile terminal with a drive recorder, user registration approval is performed by the airline. As another reference example, the technology disclosed herein can be applied to privately operated vessels such as pleasure boats. For vessels, the system of the above embodiment configured for vehicles can be easily adapted by replacing the map with a nautical chart and the driving trajectory with a navigation trajectory.

[0122] In the above embodiment, the driving trajectory data RT is assumed to be generated by the content management server 1, but this is not limited to that. For example, the content management server 1 may provide the information terminal 8 with positioning data Dp or similar data for generating driving trajectory data RT, and the information terminal 8 may generate the driving trajectory data RT. [Industrial applicability]

[0123] The technology disclosed herein is useful as a drive recording and display system for recording video data while a vehicle is in motion. [Explanation of symbols]

[0124] M Drive Recording and Display System 1. Content Management Server 33 Storage 8. Information terminals 61 Camera 65 Positioning Systems Dv1 video data Dp positioning data N3 Navigation Bar Q Vehicle TB reception image

Claims

1. A drive record display system that displays a record of a vehicle's driving, The information terminal held by the user of the aforementioned vehicle, The system includes a content management server that has storage and can communicate with the information terminal, The aforementioned content management server is Upon commencement of the vehicle's drive, positioning data acquired at predetermined intervals by a positioning system installed in the vehicle and video data captured by a camera installed in the vehicle are received and stored in the storage as a record of the vehicle's drive, and display data based on the positioning data and video data is transmitted to the information terminal. The aforementioned information terminal is Based on the aforementioned display data, an image showing the vehicle's driving status is displayed on a lower layer of the display screen. The aforementioned content management server is After the state changes from receiving positioning data or video data to not receiving data, a drive completion notification indicating that the vehicle has finished driving is sent to the information terminal. The aforementioned information terminal is When the aforementioned drive termination notification is received, an acceptance image that accepts the operation of a request to create or edit the drive's records is displayed on an upper layer superimposed on a part of the lower layer of the display screen. Drive record display system.

2. In the drive recording and display system according to claim 1, The aforementioned display data is: This includes the vehicle's driving trajectory data on map data generated based on the positioning data, The aforementioned information terminal is The lower layer displays a drive map screen that includes a display of the vehicle's driving status, with the driving trajectory data overlaid on the map data. When the aforementioned drive completion notification is received, the reception image is displayed so as to overlap a portion of the drive map screen. Drive record display system.

3. In the drive recording and display system according to claim 1, When the information terminal detects an input operation related to a request to create a record on the drive in the reception image, it transitions to the settings screen related to the creation request. Drive record display system.

4. In the drive recording and display system according to claim 1, When the information terminal detects an input operation related to a request to create a record of the drive in the reception image, it automatically sends the creation request to the content management server without transitioning to the settings screen related to the creation request. Drive record display system.

5. A drive record display method for displaying a record of a vehicle's drives, A content management server having storage and capable of communicating with an information terminal receives positioning data acquired at predetermined intervals by a positioning system installed in the vehicle and video data captured by a camera installed in the vehicle, as well as storing them in the storage as a record of the vehicle's drive, and transmits display data based on the positioning data and video data to the information terminal. The information terminal displays a screen showing the vehicle's driving status based on the display data on a lower layer of the display screen. After the content management server changes from a state of receiving positioning data or video data to a state of not receiving data, it sends a drive completion notification to the information terminal indicating that the vehicle's drive has ended. When the information terminal receives the drive termination notification, it displays a reception image on an upper layer superimposed on a portion of the lower layer of the display screen, which accepts the operation of a request to create or edit the drive's record. How to display driving records.

Images