Traveling video data recording system and traveling video data recording method

Abstract

To centrally manage vehicle events on a content management server.SOLUTION: A traveling video data recording system M includes a content management server 1. The content management server 1 includes a communication interface 21 that receives content data Dc, a storage 33 that stores the content data Dc received by the communication interface 21, an event determination unit 22 that determines an event occurring inside a vehicle based on the content data Dc, and an event hub 12. The event hub 12 acquires storage information of video data Dv1 in the storage and information about the event determined by the event determination unit 22, and transmits the information to a function that is a transmission target.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technology disclosed herein belongs to the technical field of a driving video data recording system and a driving video data recording method that record video data while a vehicle is driving. [Background technology]

[0002] Modern vehicles are equipped with cameras (hereinafter referred to as "on-board cameras") that capture video data of a specified range inside and outside the vehicle while the vehicle is traveling, for purposes such as drive recorders, driving assistance systems, and understanding the driver's condition.

[0003] Patent Documents 1 and 2 are known as technologies for effectively utilizing in-vehicle cameras. The technology in Patent Document 1 collects image data and shooting location data captured by in-vehicle cameras from multiple vehicles and provides the data in a format that can be viewed on a terminal device. The technology in Patent Document 2 is configured so that memory information acquired by an in-vehicle device or a mobile terminal is transmitted to a server via the in-vehicle device and stored, and then the memory information is distributed from the server to the mobile terminal. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-28492 [Patent Document 2] Japanese Patent Application Laid-Open No. 2015-230519 Summary of the Invention [Problem to be solved by the invention]

[0005] However, since in-vehicle cameras are generally placed in predetermined positions on the vehicle and each has its own purpose, there is a problem that the user cannot arbitrarily set the camera angle. The technology of Patent Document 2 transmits memory information acquired by a mobile terminal to a server via an in-vehicle device and stores it, but it is necessary to install a dedicated in-vehicle device in the vehicle that has the function of integrating memory information.

[0006] In addition, a drive recorder generally does not have a function for determining the start or end of a drive. Therefore, when using the video content captured by the drive recorder to create a memorable movie, for example, it may not be possible to fully grasp events occurring in the vehicle.

[0007] The technology disclosed herein has been made in consideration of the above points, and aims to increase the comprehensiveness of events when video data captured by vehicle-mounted cameras is centrally managed by a content management server. [Means for solving the problem]

[0008] In order to solve the above problem, the technology disclosed herein is directed to a driving video data recording system that records video data while a vehicle is driving, and is equipped with a content management server, and the content management server is equipped with a communication interface that receives content data including 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, and an event determination unit that determines events occurring in the vehicle based on the content data.

[0009] According to the above aspect, the event determination unit determines an event occurring in the vehicle based on content data including vehicle positioning data and video data. As a result, when video data captured by a camera installed in the vehicle is centrally managed by a content management server, it is possible to improve the comprehensiveness of events occurring in the vehicle even if there is no direct information on the events occurring in the vehicle. [Effects of the Invention]

[0010] According to the technology disclosed herein, the comprehensiveness of events can be improved when video data captured by cameras installed in vehicles is centrally managed by a content management server. [Brief explanation of the drawings]

[0011] [Figure 1] A conceptual diagram showing a typical configuration example of a driving video data recording system [Figure 2] Block diagram showing an example of the configuration of a content management server [Figure 3] Diagram explaining data stored in storage [Figure 4] A diagram showing an example of content information [Figure 5] A 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 a network configuration [Figure 8] Flowchart showing an example of the operation of the driving video data recording system [Figure 9] 10 is a flowchart showing an example of a process for acquiring and saving video data; [Figure 10] Flowchart showing additional event determination processing and message transmission processing [Figure 11] A conceptual diagram showing another example of the configuration of a driving video data recording system. [Figure 12] A conceptual diagram showing another example of the configuration of a driving video data recording system. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, exemplary embodiments will be described in detail with reference to the drawings. In the drawings, identical or corresponding parts will be designated by the same reference numerals, and repeated explanations may be omitted. In the following embodiments, the description will focus on configurations that are highly relevant to the contents of the present disclosure.

[0013] The following embodiments are illustrative, and the contents of the present disclosure are not limited by the presence or absence of descriptions or exemplified numerical values. Furthermore, the components constituting the systems, servers, etc. described in this specification, and the functions realized by the components such as functional blocks and modules described in this specification, 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. Processors include transistors and other circuits and are considered to be circuitry or processing circuitry. Processors may be configured to execute programs stored in memory. Memory includes, for example, volatile memory such as RAM, and non-volatile memory such as ROM and flash memory.

[0014] 1 is a diagram showing an example of the configuration of a driving video data recording system M according to a first embodiment. The driving video data recording system M includes a content management server 1 that records video data of a vehicle Q (e.g., an automobile) while it is driving. 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 is stored in a memory or the like and executes computer-readable instructions (e.g., a program) to perform predetermined processing steps to perform a specific function.

[0015] <Content management server> Fig. 2 is a diagram showing an example of the configuration of the content management server 1. As shown in Fig. 1 and Fig. 2, the content management server 1 includes a device gateway 2, a content manager (Contents Manager) 3, a BFF (Backend for frontend) 4, a messaging basis 11, and a function group 14. The content management server 1 is a cloud-based server that receives and manages event notifications or content data Dc from vehicles Q (Q1, Q2, Q3, ...).

[0016] The content management server 1 may be configured to automatically link predetermined data using, for example, technology such as API linkage or SFTP linkage. Although a detailed description is omitted because it is not the subject of the disclosed technology, the content management server 1 is configured with hardware such as a processor, memory, and storage, and software such as control programs and data implemented in the memory. Each function of the content management server 1, which will be described later, is realized by a processor such as a CPU or GPU executing a program stored in the memory. The content management server 1 is not limited to a cloud server, and an on-premise server may also be used.

[0017] The configuration of the content management server 1 will be described below.

[0018] <Device Gateway> As shown in FIG. 2, the device gateway 2 includes a communication interface 21, an event determination unit 22, and a transmission unit .

[0019] [Communication Interface] The communication interface 21 is a circuit or device that is connected to a network such as the Internet and that communicates with other computers, servers, information terminals, and the like.

[0020] The communication interface 21 is connected to the Internet N (see FIG. 7) and communicates with the device management server 5 via the Internet N. The communication interface 21 receives an event notification and content data Dc from the device management server 5. The event notification includes, for example, a notification that the 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 time intervals by a positioning system 65 provided in the vehicle Q, and video data Dv1 captured by a camera 61 arranged in the vehicle. The positioning system and camera provided in the vehicle Q will be described later together with other components of the vehicle Q.

[0021] The content management server 1 may be data-linked with the device management server 5. In this case, when content data Dc is transmitted from a specific vehicle Q to the device management server 5, the device management server 5 transmits the content data Dc of that vehicle Q to the content management server 1. The content data Dc includes positioning data Dp and video data Dv1. The content management server 1 receives the positioning data Dp and the video data Dv1 as separate files.

[0022] The data included in the content data Dc will be described in more detail below.

[0023] -Positioning data- The positioning data Dp is positioning information of the vehicle Q at a predetermined time, and includes, for example, some or all of the following: the date the positioning information was acquired (data acquisition date), the time the positioning information was acquired (data acquisition time), the position information of the vehicle Q (for example, latitude and longitude), the traveling direction information of the vehicle Q, information on the direction and orientation, the moving speed of the vehicle Q, and an identification ID. The positioning data Dp is transmitted, for example, from the device management server 5 to the content management server 1 as a file separate from the video data Dv1. The file format of the positioning data Dp is not particularly limited, but may be, for example, a text file conforming to the NMEA format.

[0024] -Video data- As described above, the video data Dv1 is data of video captured by a camera (hereinafter referred to as an "on-board camera") installed in the vehicle Q. In the driving video data recording system M, the video data Dv1 to be recorded is not particularly limited. The video data Dv1 includes one or both of still images and videos (including those captured in a time-lapse manner). The video data Dv1 may also include audio. For example, the video data Dv1 includes "video data captured by an on-board camera while the vehicle is traveling and capturing a predetermined range outside the vehicle (e.g., a predetermined range in the direction of travel of the vehicle) that is linked to positioning data," "video data of the outside of the vehicle or the inside of the vehicle captured based on input received directly or indirectly from the driver and / or passengers," "video data of the outside of the vehicle or the inside of the vehicle that is automatically captured when a specific location or condition is observed by a sensor or the like," and "time-lapse video data that captures the outside of the vehicle semi-automatically and continuously." Examples of the specific state include "a state in which the atmosphere inside the vehicle is lively" and "a state in which scenery, buildings, etc. of a tourist spot are included in the camera frame." Hereinafter, for convenience of explanation, when no particular distinction is made between the driver and the passengers, the driver and passengers may be collectively referred to as "user U of vehicle Q" or simply "user U." The positioning data Dp linked to the video data Dv1 only needs to be related to each other; for example, the positioning data Dp at the time the video data Dv1 was captured can be said to be the positioning data Dp linked to the video data Dv1.

[0025] The cameras that capture the video data Dv1 include a camera (hereinafter referred to as an "exterior camera") that is installed in the vehicle Q and captures a predetermined range outside the vehicle (also simply referred to as "outside the vehicle"), and a camera (hereinafter referred to as an "interior camera") that is installed in the vehicle Q and captures a predetermined range inside the vehicle cabin. For example, examples of cameras that are installed in a vehicle include an "exterior camera that captures the front or rear of the vehicle Q for use as a drive recorder," an "exterior camera that captures the outside of the vehicle for automatic vehicle control such as ADAS," an "interior camera that captures the driver to check the driver's condition or to provide driving assistance," and an "interior camera that captures the interior of the vehicle to capture the atmosphere and state inside the vehicle cabin." The camera installed in the drive recorder may be, for example, a "camera installed in a dedicated device for the drive recorder" or a "camera installed in an information terminal owned by a user U when an application functioning as a drive recorder is installed in the information terminal and operated in the vehicle Q."

[0026] -Other content data- The content data Dc may include data other than the video data Dv1 and the positioning data Dp. For example, the content data Dc may include "audio data acquired by a microphone placed in the passenger compartment of a vehicle" or "files or data in a specific format created by a specific application."

[0027] [Event Judgment Department] The event determination unit 22 determines events occurring inside the vehicle based on the content data Dc. The events determined by the event determination unit 22 include driving events related to the drive, such as vehicle location information and the journey (from the start of the drive to arriving at the destination), and in-vehicle events related to events that occur inside the vehicle during the drive. Here, a "drive" refers to a journey from a predetermined first point to a predetermined second point. For example, it may be a journey from a departure point (corresponding to the first point) to a destination point (corresponding to the second point) on a certain trip, or a journey from the departure point (corresponding to the first point) via one or more destination points to a final destination or a return to the departure point (corresponding to the second point).

[0028] As described above, the video data Dv1 is linked to the positioning data Dp and includes driving video data Dv3 captured by an external camera while the vehicle Q is driving. For example, the event determination unit 22 determines that an event of starting driving of the vehicle Q has occurred when, after a predetermined time or more has passed during which the positioning data Dp or driving video data Dv3 has not been received via the communication interface 21, the reception of the positioning data Dp or driving video data Dv3 begins again. For example, the event determination unit 22 determines that an event of ending driving of the vehicle has occurred when, after a state in which the positioning data Dp or driving video data Dv3 has been received changes to a state in which the positioning data Dp or driving video data Dv3 has not been received and a predetermined time has passed since the state in which the positioning data Dp or driving video data Dv3 has been received.

[0029] The "predetermined time" for determining the occurrence of the drive start and drive end events is not particularly limited. The "predetermined time" may be set in advance, or may be configured to be set and changed externally. Alternatively, the event determination unit 22 may be configured to receive input from an information terminal or the like held by the user U via the Internet N, so that the user U can set or change the "predetermined time" via the information terminal.

[0030] [Transmitter] The transmitter 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 as content data Dc from the transmitter 23 to the content management unit 3. As will be explained in detail later, the video data Dv1 transmitted from the transmitter 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.

[0031] The transmitter 23 transmits topic information Dm, which is a key for transmitting 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 acquired from the positioning data Dp,” “content ID of the video data Dv1 and / or the video data Dv2 described later,” “storage information indicating that the video data Dv1 and / or the video data Dv2 assigned with the content ID have been stored in the storage 33 of the content management unit 3,” “event information determined by the event determination unit 22,” “status notification of the device management server 5,” and “user usage association information.” The event information determined by the event determination unit 22 is transmitted, for example, embedded in the header of the message router 13. Note that, when drive start and drive end events are received from the outside via the communication interface 21, the transmitter 23 may transmit the received event information to the event hub 12 as the above-mentioned topic information. The topic information Dm is used by the message router 13 described later to determine to which application module (hereinafter simply referred to as "application module" (written as "function" in the drawings)) related to which function or service a message should be sent.

[0032] <Messaging infrastructure> The messaging infrastructure 11 includes an event hub 12 and a message router 13. The messaging infrastructure 11 is a messaging system used to send and receive messages to and from application modules 15 and to exchange messages between application modules 15. The application modules 15 will be described later.

[0033] The event hub 12 acquires the topic information Dm from the transmission unit 23. As described above, the topic information Dm includes the “positioning data Dp,” the “content ID of the video data Dv1 and / or video data Dv2,” and “information on the event determined by the event determination unit 22.” The topic information Dm acquired by the event hub 12 is passed to the message router 13.

[0034] The message router 13 determines to which application module 15 the message (each topic information Dm) should be sent, and passes it back to the event hub 12. The event hub 12 distributes each piece of topic information Dm to an application module 15 according to the determination by the message router 13.

[0035] The messaging infrastructure 11 is an example of a routing module that acquires topic information Dm and distributes the topic information Dm to an application module 15 that implements a predetermined function.

[0036] <Function group> The function group 14 includes application modules 15 for realizing various functions and services. The application module 15 includes a memory for storing application programs and a processor for executing the application programs. In the application module 15, various functions are realized, for example, by the processor executing the application programs stored in the memory. When the application module 15 receives topic information Dm, it executes processing according to the function it realizes. Examples of functions realized by the function group 14 include, for example, a "user information management function," a "drive log management function," a "video data management function," and a "memory movie creation and editing function."

[0037] More specifically, an example of application module 15 that realizes the function of creating and editing a memory movie will be described. The application module 15 identifies a content ID related to a common drive from among the content IDs based on the positioning data Dp and event information determined by the event determination unit 22. Then, the application module 15 obtains the video data Dv1 and Dv2 assigned with the identified content ID from the content management unit 3, which will be described later, and creates a short movie based on the video data Dv1 and Dv2.

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

[0039] <Content Management Department> The content management unit 3 includes a communication interface 31, a content processing unit 32, and a storage 33. The content management unit 3 integrates the video data Dv1 received via the communication interface 31 and the video data Dv2 received via the communication interface 31 and stores the integrated data in the storage 33. This allows the video data Dv1 and Dv2 to be centrally managed by the content management unit 3. In the following description, the video data Dv1 and the video data Dv2 may be collectively referred to as the video data Dv. In other words, the video data Dv includes at least one of the video data Dv1 and Dv2.

[0040] The components of the content management unit 3 will be specifically described below.

[0041] The communication interface 31 is a circuit or device connected to a network such as the Internet and used to communicate with other computers, servers, information terminals, etc. In this embodiment, the communication interface 31 is connected to the Internet N (see FIG. 7) and communicates with an information terminal 8 (see FIG. 7) via the Internet N. 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 is an example of a second communication unit that communicates with an information terminal 8 held by a user U of a vehicle Q and receives video data Dv2 captured by a camera 81 (see FIG. 7) of the information terminal 8 from the information terminal 8. Although detailed description thereof is omitted because it is not related to the subject matter of the disclosed technology, the information terminal 8 is, for example, an information terminal such as a smartphone or tablet, and has a function of capturing still images or videos using the built-in camera 81. The information terminal 8 also includes a communication interface 82 (see FIG. 6) that communicates with other authenticated computers and servers via the Internet N.

[0042] Examples of storage include magnetic recording media such as hard disk drives (HDDs), semiconductor recording media such as solid state drives (SDDs), and optical recording media such as DVDs, and are intended for long-term storage of digital data. The storage may be a distributed storage, i.e., data to be stored may be stored in a distributed manner. As described above, the storage 33 stores "content files" and "content information" so that they are managed separately. The storage 33 includes, for example, a first area 33a in which "content information" is stored and a second area 33b in which "content files" are stored. The storage 33 may be a distributed storage, i.e., data to be stored may be stored in a distributed manner. FIG. 3 shows an example of data stored in the first area 33a and the second area 33b of the storage 33, and FIG. 4 shows an example of content information. While this embodiment illustrates an example in which content information is stored in a table format, the storage format is not particularly limited and may be another format, such as a tree format.

[0043] In this embodiment, an example will be described in which video data Dv of a first drive D1 and a second drive D2 are stored in storage 33. The video data Dv of first drive D1 includes video data 11 to 15, No. 11 to No. 15, and the video data Dv of second drive D2 includes video data 21 to 25, No. 21 to No. 25. In the examples of FIGS. 3 and 4, video data 11, 12, 15, 21, 23, and 25 are time-lapse video images captured at predetermined intervals by camera 61 (exterior camera) of drive recorder 6 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 captured by camera 61 (interior camera or exterior camera) of drive recorder 6 during drives D1 and D2 of vehicle Q, and are examples of video data Dv1 and examples of event video data. The video data 14, 22 are still images or videos captured by the camera 81 of the information terminal 8 during drives D1, D2 of the vehicle Q, and are examples of video data Dv2 and examples of event video data. The normal driving video data is video data captured at predetermined intervals during normal driving of the vehicle Q. Furthermore, the event video data is different from the normal driving video data and is video data captured based on a predetermined input.

[0044] 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 assigned content ID is sent to the messaging infrastructure 11 as topic information Dm via the device gateway 2. The content processing unit 32 also performs a virus check on the video data Dv1 to confirm the safety of the data. After confirming the safety of the data, the content processing unit 32 performs predetermined processing on the video data Dv1. Specifically, the content processing unit 32 saves a content file of the video data Dv1 in the second area 33b. The content processing unit 32 also executes processing to acquire content information about the video data Dv1 and saves the acquired information in the first area 33a of the storage 33 in association with the corresponding content ID.

[0045] The content processing unit 32 assigns a content ID to the video data Dv2 received from the information terminal 8 and stores the content ID in the first area 33a of the storage 33. The assigned content ID is transmitted to the messaging infrastructure 11 as topic information Dm via the device gateway 2. The content processing unit 32 also performs a virus check on the video data Dv2 to confirm the safety of the data. After confirming the safety of the data, the content processing unit 32 performs predetermined processing on the video data Dv2. Specifically, the content processing unit 32 stores a content file of the video data Dv2 in the second area 33b. The content processing unit 32 also executes processing to acquire content information of the video data Dv2 from the second video data Dv2 or metadata of the second video data Dv2, and stores the acquired content information in the first area 33a of the storage 33 in association with the corresponding content ID.

[0046] When event video data is received as the first video data Dv1, the content processing unit 32 may generate accompanying video data associated with the event video data and store the event video data and content files of the accompanying video data in the second area 33b of the storage 33. The accompanying video data is not particularly limited, but may be, for example, a thumbnail of the event video data. The path of the accompanying video data is stored in the first area 33a of the storage 33 as content information of the original event video data. The examples of FIGS. 3 and 4 show an example in which two thumbnails (video data 131 and 132) are generated for video data 13, which is event video data. The video data 131 and 132 are, for example, thumbnails of different sizes. In the example of FIG. 4, thumbnails are generated for video data 13, 22, and 24, which are event video data.

[0047] <BFF(Backend for frontend)> 2, the BFF 4 includes a communication interface 41 and a command processing unit 42. The BFF 4 functions as a data exchange window with a mobile application (hereinafter referred to as a "mobile app") implemented in the information terminal 8. Specifically, the communication interface 41 receives and processes commands from the mobile app implemented in the information terminal 8 of the user U.

[0048] The communication interface 41 is a circuit or device connected to a network such as the Internet and for communicating with other computers, servers, information terminals, etc. In the example of FIG. 1, the communication interface 41 is connected to the Internet N (see FIG. 7) and communicates with the information terminal 8 via the Internet N. The communication interface 41 also communicates with the communication interface 31 of the content management unit 3 within the content management server 1. Note that while FIG. 1 shows an example in which the 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.

[0049] The command processing unit 42 executes processing corresponding to commands from the mobile app of the information terminal 8. For example, BFF4 receives commands such as a "request to view drive logs and videos / still images," a "request to create a memory movie," and an "instruction to edit the drive log" from the mobile app, and the command processing unit 42 executes processing corresponding 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 having a "memory movie creation function," receives the memory movie created by the application module 15, and performs processing to send it to the information terminal 8 (mobile app). Furthermore, when the command processing unit 42 receives a command from the information terminal 8 requesting to view drive logs and videos / still images, it retrieves the videos / still images corresponding to the command from the storage 33 and sends them to the information terminal 8.

[0050] <Device management server> 6, the device management server 5 includes a communication interface 51, a content management unit 52, and a storage 53. The device management server 5 acquires content data Dc (including positioning data Dp and video data Dv1) acquired by a drive recorder 6 under management through data linkage. Furthermore, for a drive recorder 6 that is a link target with the content management server 1, the device management server 5 performs data linkage between the content management server 1 and the content data Dc acquired from the drive recorder 6.

[0051] The communication interface 51 is a circuit or device connected to a network such as the Internet and used to communicate with other computers, servers, information terminals, etc. In the example of Fig. 1, the communication interface 51 is connected to the Internet N (see Fig. 7) and communicates with the content management server 1 and the drive recorder 6 via the Internet N. Data linkage with the drive recorder 6 and data linkage with the content management server 1 is performed via the communication interface 51.

[0052] The content management unit 52 manages the content data Dc in the storage 53. Specifically, the content data Dc received from the drive recorder 6 to be managed is stored in the storage 53. FIG. 5 shows an example in which the content data Dc is received from each of the vehicles Q (Q1, Q2, Q3, ...) and stored in each of the storage areas (53a, 53b, 53c) of the storage 53. The content management unit 52 also performs a process of retrieving the content data Dc to be transmitted from the storage 53 and transmitting it to the content management server 1 via the communication interface 51.

[0053] <Vehicle> Next, the configuration of the vehicle Q will be described with reference to Fig. 5. The vehicle Q in this example is equipped with a general in-vehicle system 7, and a drive recorder 6 is installed by a user U as a retrofit.

[0054] <Drive recorder> The drive recorder 6 is a device that acquires driving log data of the vehicle Q and includes 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 captures a predetermined range using the camera at a predetermined time (every predetermined period), and transmits the acquired positioning data Dp and the captured video data Dv1 to the device management server 5. The drive recorder 6 may be in the form of a drive recorder device dedicated to acquiring driving log data, or may be in the form of an information terminal such as a smartphone that has a mobile app for acquiring driving logs installed and is used as a drive recorder. The form in which an information terminal is used will be described later with reference to FIG. 11.

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

[0056] The input unit 62 accepts various inputs. Specifically, the input unit 62 includes, for example, a microphone that captures voices in the vehicle cabin and an operation accepting unit that accepts input operations from the user U. Examples of the operation accepting unit include a push button switch and a touch sensor touch panel. Note that the input operations from the user U may be accepted by voice recognition via the microphone. That is, the microphone may also serve as the operation accepting unit. In addition, in the present disclosure, the microphone arranged in the vehicle cabin may be a "microphone that is installed as standard in the vehicle as the in-vehicle system 7," a "microphone of an add-on device such as a drive recorder 6 that is added to the vehicle Q," or a "microphone provided on an information terminal 8 that the user U brings into the vehicle cabin when driving."

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

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

[0059] The positioning system 65 can use a conventionally known configuration (for example, GPS), receives radio waves from an artificial satellite, and acquires positioning data Dp based on the radio waves from the artificial satellite. As described above, the positioning data Dp is linked to the video data Dv1 captured by the camera 61 from the drive recorder, and is stored in the storage unit 66.

[0060] The storage unit 66 is configured, for example, with a volatile memory such as RAM, or a non-volatile semiconductor memory such as ROM or flash memory. A program for operating the drive recorder 6 is stored in the storage unit 66. The storage unit 66 also temporarily stores 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 linked to the device management server 5 via the communication interface 64.

[0061] <In-vehicle systems> The following briefly describes the parts of the in-vehicle system 7 that are relevant to the subject matter of the disclosed technology, and omits a description of the configuration that is less relevant to the subject matter of the disclosed technology. In this example, the in-vehicle system 7 includes an input unit 71, an output unit 72, a communication interface 73, a group of sensors 74, a group of controllers 75, a group of actuators 76, and a memory unit 77.

[0062] The input unit 71 accepts various inputs. Specifically, the input unit 71 includes, for example, a microphone that acquires audio from within the vehicle cabin, and an operation accepting unit that accepts input operations from the user U. Examples of the operation accepting unit include a push button switch and a touch sensor touch panel. Note that the input operations from the user U may be accepted by voice recognition via the microphone. In other words, the microphone may also serve as the operation accepting unit.

[0063] The output unit 72 is used to output various types of information. Specifically, examples of the output unit 72 include a display panel that displays output information on a display screen, a speaker that outputs audio information, and a liquid crystal display that presents information by turning on and off.

[0064] The communication interface 73 is a circuit or device connected to the Internet N (see FIG. 7) and used to communicate with other computers, servers, information terminals, etc. In the example of FIG. 1, the communication interface 73 does not communicate with any of the device management server 5, the drive recorder 6, and the content management server 1.

[0065] The sensor group 74 includes a camera 741 arranged in the vehicle and a positioning system 742 used for autonomous driving, driving assistance, or the like. The camera 741 includes an exterior camera that captures a predetermined range outside the vehicle, and an interior camera that captures the interior of the vehicle. Although not shown, the exterior camera is, for example, made up of multiple cameras, and is arranged so that when the capture ranges of each camera are combined, a 360-degree range around the vehicle can be captured.

[0066] The controller group 75 is made up of various controllers that control the in-vehicle systems. The controller group 75 is made up of ECUs (Electronic Control Units) arranged in various locations in 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) that assist the driving of the vehicle Q. The actuator group 76 includes driving system actuators related to the driving of the vehicle Q, braking system actuators related to braking of the vehicle Q, and steering system actuators related to steering of the vehicle Q.

[0067] The storage unit 77 includes, for example, a memory and a storage. The memory includes, for example, a volatile memory such as a RAM, and a non-volatile memory such as a ROM or a flash memory. The storage includes, for example, a magnetic recording medium such as a hard disk drive (HDD), a semiconductor recording medium such as a solid state drive (SDD), and an optical recording medium such as a DVD. The storage unit 77 temporarily stores positioning data Dp acquired by the positioning system 742 and video data Dv1 captured by the camera 741.

[0068] <Operation of driving video data recording system> Next, a series of operational flows from the start of driving to the end of driving in the driving video data recording system M will be described with reference to the flowcharts of Figures 8 to 10. Figures 8 to 10 describe the operations and processing in the content management server 1.

[0069] When the power of the vehicle Q is turned on, power is supplied to the drive recorder 6, and the drive recorder 6 starts operating. Specifically, the drive recorder 6 starts capturing images with the camera 61 and acquiring positioning data Dp with the positioning system 65. The drive recorder 6 exchanges content data Dc including video data Dv1 captured by the camera 61 and positioning data Dp acquired by the positioning system 65 with the device management server 5.

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

[0071] In step S1 of Fig. 8, when the device gateway 2 receives an event notification from the device management server 5, it determines whether the event notification indicates the acquisition of video data Dv1 (S2). The device gateway 2 also executes an additional event determination process and a message transmission process (S4). Note that, in the example of Fig. 8, an example is described in which the process of step S2 and the process of step S4 are executed in parallel, but step S2 and step S4 may also be executed in series. For example, step S4 may be executed after the process of step S2, or step S2 may be executed after the process of step S4.

[0072] [Video data acquisition and storage processing] In step S2, if the event notification is a notification regarding acquisition of the video data Dv1 (YES in S2), the content management server 1 executes acquisition processing and storage processing of the video data Dv1 in step S3. In the flow diagram, the process proceeds to step S12 in FIG.

[0073] FIG. 9 is a flowchart showing an example of the process of acquiring and saving video data.

[0074] In step S12, the device gateway 2 requests the device management server 5 to acquire the video data Dv1. The device management server 5 then transmits the video data Dv1 to the device gateway 2, and the device gateway 2 receives the video data Dv1 (S13). At this time, the positioning data Dp and the video data Dv1 associated with the positioning data Dp are received separately. The associated positioning data Dp and the video data Dv1 do not need to be received at the same time; they may be received at different times. The video data Dv1 received by the device gateway 2 is transmitted to the content management unit 3, and the positioning data Dp is transmitted as topic information Dm to the event hub 12.

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

[0076] -Normal driving images- In step S14, if the video data Dv1 is a normal driving image, the flow proceeds to step S15.

[0077] In step S15, the content management unit 3 assigns a content ID to the video data Dv1 and transmits the content ID to the device gateway 2. The content ID of the video data Dv1 received by the device gateway 2 is transmitted to the event hub 12 as topic information Dm. The content management unit 3 also performs a virus check on the video data Dv1 to confirm the safety of the data. Once the safety of the data is confirmed, the video data Dv1 is stored in the second area 33b of the storage 33. The content management unit 3 also executes a process to acquire content information. The acquired content information is associated with the content ID created earlier and stored in the first area 33a of the storage 33. A specific example of content information is shown in FIG. 4 and has already been described. The flow then proceeds to step S5 in FIG. 8.

[0078] -For event photos- In step S14 of FIG. 9, if the video data Dv1 is event video data, the flow proceeds to step S16. In step S16, the same process as in step S15 is executed. In the next step S17, the content management unit 3 creates additional content based on the video data Dv1. The additional content is not particularly limited, but may be, for example, 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 processes of step S16 and step S17 may be executed in parallel. Thereafter, the flow proceeds to step S5 of FIG. 8.

[0079] In step S5 of Fig. 8, the device gateway 2 determines whether the state in which no event notification has been received (hereinafter referred to as the "no-reception state") has exceeded a predetermined drive end determination period for determining the end of the vehicle drive. If the duration of the state in which no event notification has been received is equal to or shorter than the drive end determination period (NO in S5), the processes in steps S1 to S5 described above are repeated. On the other hand, if the duration of the state in which no event notification has been received exceeds the drive end determination period (YES in S5), it is determined that the drive has ended, and in step S6, processing associated with the drive end determination is performed.

[0080] [Additional event determination processing and message transmission processing] Next, the process of determining whether an additional event has occurred and the process of sending a message in step S4 of Fig. 8 will be described. As described above, when an event notification is received (S1), the device gateway 2 executes the process of determining whether an additional event has occurred and the process of sending a message (S4). Fig. 10 is a flowchart showing the process of determining whether an additional event has occurred and the process of sending a message.

[0081] 10, the device gateway 2 determines whether or not there is an additional event. Here, an additional event refers to an additional event that is different from the event notification related to the normal acquisition of a driving log received from the device gateway 2. For example, when the device gateway 2 receives the first event notification after the start of driving the vehicle Q, the device gateway 2 determines that there is an additional event of "start driving" described above.

[0082] If it is determined that there is an additional event, the flow proceeds from step S43 to step S44, and the device gateway 2 transmits a notification of the normal driving event and a notification of the additional event to the event hub 12 as topic information Dm. That is, the device gateway 2 transmits a notification of the event information to the event hub 12. The topic information Dm of the normal driving event may indicate, for example, "photos and videos have been received from the drive record as normal driving log data," "a specific content ID has been assigned to the content manager and saved," or "positioning information has been received." Furthermore, the message of the additional event may indicate, for example, "the normal driving log data (photos and videos) is data indicating the start of a drive." The same applies if it is determined in step S6 of FIG. 8 that there is an additional event of "end of drive," and the device gateway 2 notifies the event hub 12 of the topic information Dm of the additional event, for example, "the drive has ended."

[0083] Returning to FIG. 10, in the next step S46, the topic information Dm received by the event hub 12 is passed to the message router 13 via the topic for the input message. The message router 13 then determines to which function each event should be sent, i.e., the application module 15 to which each piece of event information (here, the normal driving event and the additional event) should be sent. Based on the determination of the message router 13, the event hub 12 sends each piece of event information to the application module 15 to which it should be sent. For example, the drive log management function and the memory movie editing function are notified of the additional events "normal driving event," "start of drive," and "end of drive" when they are received, or at a predetermined timing. The flow then proceeds to step S5 in FIG. 8.

[0084] On the other hand, if it is determined in step S42 that there is no additional event, the flow proceeds from step S43 to step S45, where the device gateway 2 transmits topic information Dm of a normal driving event to the event hub 12. For example, the normal driving log data from when the "drive starts" is determined to when the "drive ends" is determined generally corresponds to a state of "no additional event." In this case, the device gateway 2 transmits topic information Dm indicating a "normal driving event" to the event hub 12. A specific example of the topic information Dm of the normal driving event is the same as in step S44 described above. Thereafter, as in the case of "there is an additional event," in the next step S46, the topic information Dm received by the event hub 12 is passed to the message router 13, which determines the application module 15 to which the message is to be sent, and then passes the information back to the event hub 12. Then, based on the determination of the message router 13, the event hub 12 transmits the event information to the application module 15 to which the message is to be sent. For example, the normal driving event is notified to the drive log management function. The flow then proceeds to step S5 in FIG. 8.

[0085] <Other embodiments> As described above, the embodiments have been described as examples of the technology disclosed in this application. However, the technology in this disclosure is not limited to these, and can be applied to embodiments in which appropriate modifications, substitutions, additions, omissions, etc. are made. Furthermore, it is also possible to combine the components described in the above embodiments to create new embodiments.

[0086] For example, instead of the configuration shown in Fig. 1, the driving video data recording system M may be provided with a plurality of interfaces of different types, as shown in Fig. 11. In Fig. 11, the same components as in Fig. 1 are given the same reference numerals, and the following description will focus on the differences from Fig. 1.

[0087] In the driving video data recording system M of Fig. 11, the device gateway 2 is provided in an anti-corruption layer (ACL) 18 that is external to the content management server 1. The content management server 1 is also provided with a device endpoint 19 instead of the device gateway 2. Furthermore, the driving video data recording system M includes, as application interfaces 17, a backend for frontend (BFF) 171 for information terminals and a backend for frontend (BFF) 172 for web services.

[0088] 11, the configuration and functions of the device gateway 2 are the same as those of the above-described embodiment, and are configured to be able to communicate with the device management server 5 (56 and 57 in FIG. 11). For example, the device gateway 2 receives content data Dc (video data Dv1 and positioning data Dp) through data linkage with the device management servers 56 and 57. Then, the device gateway 2 transmits the video data Dv1 to the content management unit 3 and transmits the topic information Dm to the messaging infrastructure 11.

[0089] The device endpoint 19 has a function as a data exchange window (similar to the function of the BFF 4 described above) with the device management server 58, drive recorder 6 (69 in FIG. 11), or information terminal 8 (P2 in FIG. 11) that is the connection destination, and a function as the device gateway 2 described above. The content management unit 3 has the same configuration and function as those in the above embodiment.

[0090] Three types of vehicles Q4, Q5, and Q6 are illustrated in the example of Fig. 11. Below, an outline of the configuration of the vehicles Q4, Q5, and Q6 and a brief description of the data flow in Fig. 11 will be given.

[0091] In vehicle Q4, an information terminal P1 is placed in vehicle Q and is used as a drive recorder 6. The information terminal P1 is connected to a device management server 56 and is in data communication with the device management server 56. That is, content data Dc (video data Dv1 and positioning data Dp) is transmitted from the information terminal P1 to the device management server 56. The device management server 56 and the device gateway 2 are in data communication with each other, and the content data Dc acquired by the information terminal P1 is data-communicated between the device management server 56 and the device gateway 2. Subsequent processing is the same as in the above-described embodiment.

[0092] The vehicle Q5 is provided with a camera C1 of the drive recorder 68 and a camera C2 for the ADAS 751. The video data Dv1 captured by the camera C1 is linked to the device management server 57, and the video data captured by the camera C2 is linked to the device management server 58. That is, DeThe content data Dc (video data Dv1 and positioning data Dp) acquired by the drive recorder 68 is transmitted to the device management server 57. Similarly, the content data Dc (video data Dv1 and positioning data Dp) acquired by the ADAS 751 is transmitted from the in-vehicle system 7 including the ADAS 751 to the device management server 58. The device management server 57 and the device gateway 2 are data-linked, and the content data Dc acquired by the drive recorder 68 is transmitted from the device management server 57 to the device gateway 2. The subsequent processing is the same as in the above-described embodiment, and the video data Dv1 captured by the camera C1 is stored in the storage 33 of the content management unit 3. The device management server 58 is data-linked with the device endpoint 19 and the content management unit 3. Of the content data Dc transmitted from the in-vehicle system 7 to the device management server 58, the video data Dv1 is transmitted to the content management unit 3, and the positioning data Dp is transmitted to the device endpoint 19. In the content management unit 3, the video data Dv1 received from the device management server 58 is integrated with the video data Dv1 captured by the camera C1 and stored in the storage 33. In the device endpoint 19, an event occurring in the vehicle Q5 is determined based on the positioning data Dp and other content data Dc. In other words, the device endpoint 19 functions as an event determination unit. The device endpoint 19 transmits the received positioning data Dp and other content data Dc to the messaging infrastructure 11 as topic information Dm. Subsequent processing is the same as in the above-described embodiment.

[0093] A camera C3 of a drive recorder 69 is installed in a vehicle Q6, and a user U of the vehicle Q6 carries an information terminal P2. Video data Dv1 captured by the camera C3 and video data Dv2 captured by the camera of the information terminal P2 are linked to the content management unit 3. In the content management unit 3, the video data Dv1 captured by the camera C3 and the video data Dv2 captured by the information terminal P2 are integrated and stored in storage 33. In addition, positioning data Dp acquired by the drive recorder 69 is transmitted to the device endpoint 19 and transmitted as topic information Dm to the messaging infrastructure 11. The processing of the topic information Dm in the messaging infrastructure 11 is the same as in the above-described embodiment.

[0094] 11, an application interface 17 corresponding to the BFF4 of the above-described embodiment is provided. The application interface 17 includes a BFF 171 having a function as a data exchange window with a mobile application implemented in the information terminal P3, and a BFF 172 having a function as a data exchange window with a web system W of a computer (not shown). Specific processes executed by the BFFs 171 and 172 are similar to those of the above-described BFF4.

[0095] Even when the configuration of FIG. 11 is adopted, the same effects as those of the configuration of FIG. 1 described above can be obtained.

[0096] The functions of the above-described embodiments do not need to be included in the blocks shown in the drawings, as long as the processing is performed somewhere in the content management server 1. For example, the function of the event determination unit 22 may be implemented outside the device gateway 2, for example, in one of the application modules 15 in the function group 14.

[0097] Instead of the configuration shown in Fig. 1 described above, a configuration as shown in Fig. 12 may be used. In Fig. 12, components common to Fig. 1 are assigned the same reference numerals, and the following description will focus on the differences from Fig. 1. Fig. 12 shows an example in which a routing module that distributes topic information Dm is provided as application module 15 of function group 14. In Fig. 12, the configuration and operation of messaging infrastructure 11 and function group 14 differ from those of the embodiment described above.

[0098] 12 acquires topic information Dm from sending unit 23 and stores it in a topic. The acquired topic information Dm is then passed to a "routing module" which is an application module 15 having a routing function.

[0099] The routing module (application module) determines to which application module 15 each piece of topic information Dm should be sent, and executes a process of allocating the information to the application module 15. The application modules 15 that receive the topic information Dm execute processes according to the functions they each realize. Other configurations and operations are the same as those of the above-described embodiment.

[0100] The vehicle to which the driving video data recording system and driving video data recording method of the present disclosure are applicable is not limited to automobiles, but may be other vehicles such as bicycles, motorbikes, and railcars. Even when the vehicle is a bicycle, motorbike, or railcar, a drive recorder or information terminal equipped with a positioning system and a camera is installed on the bicycle, motorbike, railcar, or other vehicle, as shown in FIG. 1, FIG. 11, or FIG. 12. The content management server then acquires the positioning data and the first video data from the drive recorder or information terminal. The rest of the configuration and operation are the same as those of the above-described embodiment.

[0101] The technology of the present disclosure can also be applied to an aircraft. In the case of an aircraft, for example, a GPS or a flight recorder mounted on the aircraft can be used as the positioning system and camera. In this case, the content management server also acquires the positioning data and the first video data from the GPS or the flight recorder. The other configurations and operations are the same as those of the above-described embodiment.

[0102] The functions of the above-described embodiments may be executed anywhere in the content management server, and do not necessarily need to be included in the blocks shown in the drawings. For example, the function of the event determination unit 22 may be implemented in a location other than the device gateway 2 (see FIG. 1) or the device endpoint 19.

[0103] <Summary of the embodiment> As described above, the driving video data recording system M according to one embodiment of the present disclosure is a system that records video data Dv1 when a vehicle Q is driving, and includes a content management server 1. The content management server 1 includes a communication interface 21 that receives content data Dc including positioning data Dp acquired at predetermined time intervals by a positioning system (65, 742) provided in the vehicle Q and video data Dv1 captured by a camera (61, 741) arranged in the vehicle Q, and an event determination unit 22 that determines an event occurring in the vehicle Qs based on the content data Dc.

[0104] According to the above embodiment, the event determination unit 22 determines an event occurring in the vehicle Q based on the content data Dc including the positioning data Dp and the video data Dv1 of the vehicle Q. As a result, when the video data Dv1 captured by the camera installed in the vehicle Q is centrally managed by the content management server 1, it is possible to improve the comprehensiveness of events occurring in the vehicle even if there is no direct information on the events occurring in the vehicle.

[0105] The content management server 1 may include a content management unit 3 that assigns a content ID to the video data Dv1 and stores it, and a routing module that acquires topic information Dm and distributes it to an application module that implements a predetermined function. The function of the routing module may be implemented by, for example, the messaging infrastructure 11 or the application module 15. The topic information Dm includes the positioning data Dp, the content ID of the video data Dv1, and information on the event determined by the event determination unit 22.

[0106] As described above, by providing a routing module, the necessary topic information Dm can be obtained in each application module 15, making it easier to search, refer to, and extract content according to purpose, thereby improving the processing speed of the application module 15.

[0107] The event determination unit 22 may determine that an event that the vehicle Q has started to drive has occurred as an event occurring in the vehicle when reception of the positioning data Dp or the driving video data Dv3 starts again after a predetermined time or more has passed since no reception of the positioning data Dp or the driving video data Dv3. Alternatively, the event determination unit 22 may determine that an event that the vehicle Q has finished driving has occurred as an event occurring in the vehicle Q when a state in which the positioning data Dp or the driving video data Dv3 has been received changes to a state in which no reception has occurred, and a predetermined time has passed since the state in which no reception has occurred. Here, the video data Dv1 includes driving video data Dv3 of the area ahead of the vehicle that is captured by a camera (61, 741) while the vehicle Q is traveling and is linked to the positioning data Dp.

[0108] This makes it possible to determine the occurrence of an event such as the start or end of a drive of vehicle Q even without information about events occurring directly in the vehicle, thereby improving the comprehensiveness of events. Also, knowing the start and end of a drive makes it easier to process each drive, thereby improving the processing speed of application module 15.

[0109] When the event determination unit 22 receives audio data and / or in-vehicle video data as input, and the audio data and / or in-vehicle video data meets a predetermined criterion, the event determination unit 22 may determine that an event that could become a memory has occurred inside the vehicle Q. Here, the content data Dc includes audio data acquired by a microphone arranged inside the vehicle Q and / or in-vehicle video data captured by an in-vehicle camera that captures the interior of the vehicle Q.

[0110] This makes it possible, for example, when creating a "memory movie (short movie)" using the application module 15 of the content management server 1, to respond to events by picking up and incorporating video data Dv1 from the time period surrounding the event that could become a memory, thereby enabling the user to create and edit more memorable short movies.

[0111] The content management server 1 is configured to be able to communicate with the device management server 5, which is the storage destination of the video data Dv1 captured by the camera (61, 741), and may receive the content data Dc via the device management server 5. The content management server 1 may also communicate with the drive recorder 6 via the Internet N and receive the content data Dc directly from the drive recorder 6.

[0112] As described above, by providing a plurality of paths for the content management server 1 to receive the video data Dv1, the versatility of the interface of the content management server 1 is improved.

[0113] The application module 15 may identify a first content ID related to a common drive from among the content IDs based on the positioning data Dp and event information, obtain first video data assigned the first content ID from the content management unit 3, and create a short movie based on the first video data.

[0114] With this configuration, when the application module 15 creates a short movie (memory movie), it becomes easier to extract video data related to a specific drive, and the speed at which the short movie is created can be improved.

[0115] In one embodiment of the present disclosure, a method for recording driving video data while a vehicle Q is driving comprises a content management server 1 having a storage 33 receiving content data Dc including positioning data Dp acquired at predetermined time intervals by a positioning system installed in the vehicle Q and video data Dv1 captured by a camera (61,741) installed in the vehicle Q, assigning a content ID to the video data Dv1 and storing it in the storage 33, determining an event occurring in the vehicle Q based on the content data Dc, obtaining the positioning data, the content ID of the video data, and information on the event determined by the event determination unit, and allocating it to an application module 15 that realizes a predetermined function.

[0116] According to the above embodiment, the event determination unit 22 determines an event occurring in the vehicle Q based on the positioning data Dp of the vehicle Q and the content data Dc including the video data Dv1. As a result, when the video data Dv1 captured by a camera installed in the vehicle Q is centrally managed by the content management server 1, the comprehensiveness of events occurring in the vehicle can be improved even if there is no direct information about the events occurring in the vehicle. Furthermore, the positioning data, the content ID of the video data, and information about the event determined by the event determination unit are acquired and distributed to the application module 15, making it easier for the application module 15 to search, refer to, and extract content according to the purpose. This improves the processing speed of the application module 15. [Industrial Applicability]

[0117] The technology disclosed herein is useful as a driving video data recording system that records video data while a vehicle is driving. [Explanation of symbols]

[0118] 1 Content Management Server 12. Event Hub 21 Communication Interface 22 Event Judgment Department 33 Storage 61 Camera 65 Positioning System Dv1 video data Dp positioning data Q Vehicle

Claims

1. A driving video data recording system that records video data while a vehicle is driving, Equipped with a content management server, The content management server a communication interface for receiving content data including positioning data acquired at predetermined time intervals by a positioning system provided in the vehicle and video data captured by a camera disposed in the vehicle; an event determination unit that determines an event occurring in the vehicle based on the content data.

2. 2. The driving video data recording system according to claim 1, The content management server a content management unit that assigns a content ID to the video data and stores the content; a routing module that acquires topic information including the positioning data, the content ID of the video data, and information about the event determined by the event determination unit, and distributes the topic information to an application module that realizes a predetermined function.

3. 2. The driving video data recording system according to claim 1, the video data includes video data of a scene ahead of the vehicle that is captured by the camera while the vehicle is traveling and that is linked to the positioning data; A driving video data recording system in which the event determination unit determines that an event of the vehicle starting to drive has occurred as an event occurring in the vehicle when reception of the positioning data or the driving video data begins again after a predetermined period of time has passed without reception of the positioning data or the driving video data.

4. 2. The driving video data recording system according to claim 1, the video data includes video data of a scene ahead of the vehicle that is captured by the camera while the vehicle is traveling and that is linked to the positioning data; A driving video data recording system in which the event determination unit determines that an event of the end of driving of the vehicle has occurred as an event occurring in the vehicle when the state in which the positioning data or the driving video data is received changes to a state in which it is not being received, and a predetermined time has passed since the state in which it is not being received.

5. 2. The driving video data recording system according to claim 1, the content data includes audio data acquired by a microphone disposed in the interior of the vehicle and / or in-vehicle video data captured by an in-vehicle camera that captures the interior of the vehicle, A driving video data recording system in which, when the event determination unit receives the audio data and / or the in-vehicle video data as input, if the audio data and / or the in-vehicle video data meets a predetermined criterion, it determines that an event that could become a memory has occurred within the vehicle cabin as an event occurring in the vehicle.

6. 2. The driving video data recording system according to claim 1, A driving video data recording system, wherein the content management server is configured to be able to communicate with a device management server that is the storage destination for the video data captured by the camera, and receives the content data via the device management server.

7. 2. The driving video data recording system according to claim 1, the camera is a camera provided in a drive recorder, The content management server communicates with the drive recorder via the Internet and receives the content data directly from the drive recorder.

8. 3. The driving video data recording system according to claim 2, A driving video data recording system in which the application module identifies a first content ID related to a common drive from among the content IDs based on the positioning data and the event information, obtains first video data to which the first content ID is assigned from the content management unit, and creates a short movie based on the first video data.

9. A driving video data recording method for recording video data while a vehicle is driving, comprising: a content management server having a storage, receiving content data including positioning data acquired at predetermined time intervals by a positioning system provided in the vehicle and video data captured by a camera arranged in the vehicle; assigning a content ID to the video data and storing the content ID in the storage; determining an event occurring in the vehicle based on the content data; acquiring the positioning data, the content ID of the video data, and the event information, and distributing them to an application module that realizes a predetermined function; A method for recording driving video data.

Images