Drive recorder and the like

Abstract

To provide a mechanism to keep some of functions of a drive recorder by means of a secondary cell.SOLUTION: A drive recorder comprises: a camera for recording images; a communication processing unit for transmitting state information on the drive recorder; a control unit which controls the communication processing unit; a power source unit which receives power from a vehicle power source and drives the control unit and the communication processing unit; and a secondary cell. The control unit and the communication processing unit are driven with the secondary cell.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a drive recorder and the like. [Background technology]

[0002] As a background technique of this technical field, there is JP 2019-129328 A (Patent Document 1). This publication states that "the high-definition video generating device 20 includes an original video receiving unit 21 that receives an original video 1, which is a high-quality video, a low-bit-rate video receiving unit 24 that receives a low-bit-rate video 2, a learning model generating unit 22 that generates a learning model M using the original video 1 received by the original video receiving unit 21 as teacher data, and a high-definition video generating unit 25 that generates a high-definition video 3 from the low-bit-rate video 2 received by the low-bit-rate video receiving unit 24 using the learning model M corresponding to the low-bit-rate video 2 among the learning models M generated by the learning model generating unit 22. " (See Abstract). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2019-129328 A Summary of the Invention [Problem to be solved by the invention]

[0004] The above-mentioned Patent Document 1 describes a mechanism for uploading low bit rate video from a drive recorder to a cloud using narrowband communication such as LTE (registered trademark) (Long Term Evolution) or LPWA (Low Power Wide Area). However, Patent Document 1 assumes a state in which the vehicle power supply is constantly supplied, and does not consider a case in which the power supply from the vehicle power supply is interrupted. Therefore, the present invention provides a mechanism for maintaining some of the functions of the drive recorder using a secondary battery when, for example, the power supply from the vehicle power source is interrupted.

[0005] In addition, the applicant intends to obtain rights for configurations that aim to obtain effects from parts of the configurations disclosed in this specification and drawings, etc., through divisional applications, amendments, etc. For example, this specification discloses problems in which the parts described as "can" and "is possible" in this specification are read as "is the problem." The problems are described as being independent, and the applicant intends to obtain rights for configurations for solving each problem separately through divisional applications, amendments, etc. Even if the problems are implicitly understood from the description in the specification, the applicant intends to include part of the configurations described in this specification in the scope of the patent claim by amendment or divisional application. In addition, the applicant has disclosed a configuration that solves a problem that combines these independent problems, and intends to obtain rights for it. [Means for solving the problem]

[0006] In order to solve the above problems, for example, the configurations described in the claims are adopted. The present application includes multiple means for solving the above problems, and one example is a drive recorder comprising a camera for recording, a communication processing unit for transmitting status information regarding the drive recorder, a control unit for controlling the communication processing unit, a power supply unit for receiving power from a vehicle power supply and driving the control unit and the communication processing unit, and a secondary battery, wherein the control unit and the communication processing unit are driven by the secondary battery. Effect of the Invention

[0007] According to the present invention, it is possible to provide a mechanism for maintaining some of the functions of a drive recorder using a secondary battery. Problems, configurations and effects other than those described above will become apparent from the following description of the embodiments. The effects of the invention of this application are not limited to this, and effects achieved from the configuration disclosed in the specification and drawings are also disclosed, and the applicant intends to obtain rights to the configuration achieving said effects through divisional applications, amendments, etc. For example, in this specification, statements such as "can" and "is possible" are statements that clearly indicate the effects achieved, and there are also parts that show effects even without statements such as "can" and "is possible." Furthermore, there are effects that can be understood from the configuration even without such statements. [Brief description of the drawings]

[0008] [Figure 1] 2 is an example of the configuration of the entire DVR management system 1. [Diagram 2] 2 is an example of a connection configuration of the management server 102. [Diagram 3] 1 is an example of a hardware configuration of a drive recorder 101. [Figure 4] 2 is an example of a hardware configuration of a management server 102. [Diagram 5] 2 is an example of a hardware configuration of a user terminal 103. [Figure 6] 6 is an example of the data structure of DVR status information 600. [Figure 7] 11A and 11B are diagrams illustrating examples of timings for acquiring location information to be transmitted, etc.; [Figure 8] 2 is an example of a communication sequence during normal use. [Figure 9] 13 is an example of a communication sequence when driven by a secondary battery. [Figure 10] 13 is a diagram showing an example of another communication sequence when driven by a secondary battery. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment shown below is one embodiment of the present invention, and the contents of the present invention should not be interpreted as being limited based on the following description. FIG. 1 shows an example of the configuration of an entire drive recorder (DVR) management system 1. As shown in FIG. The DVR management system 1 includes a drive recorder 101, a management server 102, a user terminal 103, a data center 104, and a management terminal 105, all of which are connected via a network. The network may be wired or wireless, and each terminal can transmit and receive information via the network. The network is not limited to the Internet, and may be a combination of networks with different protocols.

[0010] The drive recorder 101 is a device that is mounted on, for example, an automobile and records video images while driving. The drive recorder 101 is an example of an in-vehicle device. However, the mounting target is not limited to automobiles, and may be any moving body in which the drive recorder 101 can be installed. For example, the mounting target may be automobiles, buses, trucks, motorcycles, etc. In addition, the mounting target may be transportation vehicles such as trains, monorails, linear motor cars, etc. The management server 102 is a server that stores and manages various information such as video information and status information acquired by the drive recorder 101. The various information acquired by the drive recorder 101 may be configured to be transmitted directly from the drive recorder 101 to the management server 102, or may be configured to be transmitted to the management server 102 via a data center 104.

[0011] The user terminal 103 is a terminal used by, for example, a user who drives a car. The user terminal 103 is connected to the drive recorder 101 via a mobile data communication network or an in-vehicle network such as Wi-Fi (registered trademark) of the car, and can operate the drive recorder 101. Furthermore, the user terminal 103 is connected to the management server 102 via these networks and can display various information stored in the management server 102 .

[0012] The data center 104 receives various information acquired by the drive recorder 101 and transmits it to the management server 102. For example, the data center 104 is connected to the drive recorder 101 via an LPWA (Low Power Wide Area) network, receives various information transmitted from the drive recorder 101 via the LPWA network, and transmits the received various information to the management server 102 via the Internet. Note that LPWA wireless communication is capable of long-distance communication with low power consumption. On the other hand, restrictions on the amount of data that can be transmitted per unit time can be an issue. For example, when transmitting a large amount of data, communication delays can be large. The management terminal 105 is a terminal for operating and managing the management server 102 .

[0013] Each terminal of the DVR management system 1 and the management server 102 may be, for example, a portable terminal (mobile terminal) such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or a wearable terminal such as glasses, wristwatch, or clothing. They may also be stationary or portable computers, or servers located on the cloud or network. In terms of function, they may be a VR (Virtual Reality) terminal, an AR (Augmented Reality) terminal, or an MR (Mixed Reality) terminal. Or they may be a combination of a plurality of these terminals. For example, a combination of one smartphone and one wearable terminal may function logically as one terminal. They may also be other information processing terminals.

[0014] Each terminal and management server 102 of the DVR management system 1 includes a processor that executes an operating system, applications, programs, etc., a main storage device such as a RAM (Random Access Memory), an auxiliary storage device such as an IC card, a hard disk drive, an SSD (Solid State Drive), a flash memory, etc., a communication control unit such as a network card, a wireless communication module, a mobile communication module, etc., an input device such as a touch panel, a keyboard, a mouse, a voice input, an input by motion detection by imaging of a camera unit, etc., and an output device such as a monitor or a display. Note that the output device may be a device or terminal that transmits information to be output to an external monitor, display, printer, device, etc.

[0015] The main memory stores various programs and applications (called modules), and the functional elements of the overall system are realized by the processor executing these programs and applications. Each of these modules may be implemented in hardware by integration or the like. Each module may be an independent program or application, or may be implemented as a subprogram or function within a single integrated program or application.

[0016] In this specification, each module is described as an entity (subject) that performs processing, but in reality, a processor that processes various programs, applications, etc. (modules) executes the processing. Various databases (DB) are stored in the auxiliary storage device. A "database" is a functional element (storage unit) that stores a data set so that it can handle any data operation (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. The method of implementing the database is not limited, and may be, for example, a database management system, spreadsheet software, or a text file such as XML or JSON.

[0017] FIG. 2 shows an example of a connection configuration of the management server 102. In this connection configuration example, the drive recorder 101 transmits various information to the management server 102 via the data center 104 . The drive recorder 101 transmits various information of the drive recorder 101 to the data center 104 via a wireless communication network such as an LPWA network. The customer-side management server 202 receives and stores various information from the data center 104 via the Internet using a protocol such as MQTT (Message Queue Telemetry Transport). The management terminal 105 and the user terminal 103 access the customer-side management server 202 via the Internet or a mobile communication network, receive and display various information.

[0018] The same function can also be performed via the service provider's management server 201 of the service provider who manages the DVR management system 1. Once various information of the drive recorder 101 is stored in the service provider's management server 201, it is transmitted to the management terminal 105 or the user terminal 103 via the customer's management server 203 or directly. The various information transmitted and received may be encoded and decoded by each server. Note that the drive recorder 101 may be configured to transmit various pieces of information directly to the management server 102 , rather than via the data center 104 .

[0019] FIG. 3 shows an example of the hardware configuration of the drive recorder 101. The camera 304 captures images of the front, rear, or 360 degrees, and generates video information such as moving images and still images. In addition, by equipping the image sensor of the camera 304 with an AI processing function that performs pre-processing, the following output can be performed in addition to or instead of the generation of normal captured images. The AI ​​processing function has a function of performing image recognition based on the video captured by the camera 304. - Output metadata of objects from images. - Output images in ISP (Image Signal Processor) output format, e.g. YUV or RGB. - Output an image with only a specific area cropped out.

[0020] By performing preprocessing on the image sensor side in this way, it is possible to reduce the amount of data and to perform real-time tracking of the target object using high-speed AI processing. In particular, there is an advantage in that the amount of data (i.e., the amount of communication) from the drive recorder 101 to the management server 102 can be reduced. This is because, even when transmitting data via an LPWA network as in this embodiment, data related to the AI ​​processing function can be expected to be transmitted with low latency, for example.

[0021] The acceleration sensor 305 detects acceleration and generates acceleration information. For example, when a sudden change in acceleration occurs due to an impact, sudden steering, sudden stop, etc., the DVR controller 303 detects the occurrence of an event. By analyzing the change in the acceleration information, the circumstances of an accident that occurred to a car, etc. can be inferred. The SD card 306 is a storage device for recording video information and various other information. Note that the storage device is not limited to an SD card and may be configured to store data, but a flash memory with high vibration resistance is preferable for in-vehicle use.

[0022] The DVR controller 303 is connected to a camera 304, an acceleration sensor 305, an SD card 306, and other sensors (not shown), and controls these. Based on information received from these elements, the DVR controller 303 generates status information indicating the state of the DVR controller 303. The DVR controller 303 also transmits the generated status information to the microcomputer 301. The microcomputer 301 performs the following various processes. Controls the communication processing unit 302. The communication processing unit 302 notifies the DVR controller 303 of the acquired position information. The status information obtained from the DVR controller 303 and the position information obtained from the communication processing unit 302 are converted into, for example, 16-byte data. - Sleep control is performed when the device is powered by a secondary battery. - Executes test modes during manufacturing and testing. The microcomputer 301 is programmable, and stores programs for executing the various processes described above, and the various processes described above are realized by executing these programs with a processing unit of the microcomputer 301. In this embodiment, the processing unit of the microcomputer 301 or the microcomputer 301 itself may also be referred to as a control unit.

[0023] The communication processing unit 302 transmits information about the drive recorder 101 to the management server 102 via a wireless communication antenna 308, directly or via the data center 104. The communication processing unit 302 performs wireless communication in accordance with the LPWA system, which is an example of narrowband communication. The communication processing unit 302 also has a location information acquisition unit implemented by an integrated circuit or the like, and acquires location information based on a signal received from a GNSS antenna 307 compatible with a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System). The location information acquisition unit can also acquire time information, moving speed information, and moving direction information.

[0024] Note that the communication processing unit 302 does not necessarily have to have a location information acquisition unit, and the GNSS antenna 307 may be connected to the microcomputer 301, and these may have the location information acquisition unit. Moreover, a configuration may be adopted in which a location information acquisition unit exists independently and is connected to the microcomputer 301 or the communication processing unit 302 . Further, although the time information is acquired by the position information acquisition unit, the microcomputer 301 may be configured to acquire the position information.

[0025] The drive recorder 101 has a power supply 311 connected to a vehicle power supply 310 . The power supply 311 supplies power received (or sometimes called power reception) from the vehicle power supply 310 to the DVR controller 303 and also charges the secondary battery 312 . The secondary battery 312 is a rechargeable battery such as a lithium ion battery, a nickel cadmium battery, a nickel metal hydride battery, or a lead storage battery. However, it may be a primary battery that is not rechargeable. When the accessory power supply (ACC power supply) is turned off, when the supply of power from the vehicle power supply 310 to the power supply 311 of the drive recorder 101 is interrupted due to a fault such as a broken wire or a disconnected wire caused by an accident, or when the power supply 311 is unable to supply power due to a breakdown or the like, the secondary battery transmits (or may be called power transmission or power supply) power to the microcomputer 301, the communication processing unit 302, etc., and maintains at least some functions of the drive recorder 101.

[0026] The supply voltage from the vehicle power supply 310 of an automobile is generally 12 V. The power supplied from the power supply 311 or the secondary battery 312 is stepped down to a voltage of, for example, 2 V via a DC / DC converter 313 and supplied to the microcomputer 301 and the communication processing unit 302 to drive them. The DVR controller 303, the microcomputer 301, and the communication processing unit 302 can each be implemented as an integrated circuit (chip) such as a SoC (System on a chip), or a plurality of these may be implemented together on a single chip. In particular, in this embodiment, the microcomputer 301 and the communication processing unit 302 work in conjunction with each other, so they may be implemented together on a single chip.

[0027] In this embodiment, the microcontroller 301 and the communication processing unit 302 are configured so that their power supply is separated from the DVR controller 303, and by simply supplying power to the microcontroller 301 and the communication processing unit 302 from a secondary battery, location information and various other information can be transmitted to the management server 102 without starting up the DVR controller 303, thereby reducing power consumption. In particular, the drive recorder 101 can perform long-distance communication with low power consumption by performing wireless communication using the LPWA system. Therefore, the drive recorder 101 can transmit status information of the drive recorder 101 to the remote management server 102 while extending the life of the secondary battery in the drive recorder 101 as much as possible. Furthermore, since the drive recorder 101 transmits status information to the management server 102 using LPWA communication, it is desirable to perform communication frequently or at short intervals while keeping the amount of data to a minimum. Therefore, the status information that the drive recorder 101 transmits to the management server 102 is also based on the knowledge of the inventors of the present application and takes into consideration factors such as the characteristics of LPWA wireless communication and the priority of information to be transmitted to the management server 102.

[0028] In addition, by configuring the communication processing unit 302 to include a location information acquisition unit and a GNSS antenna 307, it is possible to acquire location information and speed information by only driving the low-power communication processing unit 302 without starting the DVR controller 303. In addition, by keeping the drive voltage of the microcontroller 301 and the communication processing unit 302 at a low voltage, such as 2V, compared to the drive voltage of the drive recorder 101, such as 12V, the power consumption used to generate and transmit the DVR status information 600 can be kept low.

[0029] By mounting a small-capacity rechargeable secondary battery as in this embodiment and notifying the management server 102 of the state of the drive recorder 101 when it is driven by the secondary battery, it is possible to notify the administrator even if the user intentionally drives with the drive recorder 101 powered off. Also, it is possible to notify the failure even if the main body cannot be turned on due to a failure. Also, it is possible to track the theft.

[0030] FIG. 4 shows an example of the hardware configuration of the management server 102. As shown in FIG. The management server 102 is configured, for example, by a server placed on a cloud. The main memory device 401 stores programs and applications such as a DVR management module 410 and a video information management module 411. The processor 403 executes these programs and applications to realize each functional element of the management server 102.

[0031] The DVR management module 410 acquires DVR status information indicating the status of the drive recorder 101 from the drive recorder 101, decodes it, and stores and manages it in DVR status information 600 in the auxiliary storage device 402. In addition, the DVR management module 410 transmits some or all of the information obtained by decoding the DVR status information 600 to the user terminal 103 or the management terminal 105 via push distribution or in response to a request from the user terminal 103 or the management terminal 105.

[0032] The video information management module 411 acquires the video information stored in the drive recorder 101 from the drive recorder 101, stores it in the video information 420 of the auxiliary storage device 402, and manages it. Furthermore, the video information management module 411 transmits video information 420 to the user terminal 103 or the management terminal 105 by push distribution or in response to a request from these terminals. The auxiliary storage device 402 stores the DVR status information 600, the video information 420, and the like.

[0033] FIG. 5 shows an example of the hardware configuration of the user terminal 103. The user terminal 103 is composed of a terminal such as a smartphone, a tablet, a notebook PC, or a desktop PC. The main memory device 501 stores programs and applications such as a management server cooperation module 510 and a DVR cooperation module 511. The processor 503 executes these programs and applications to realize each functional element of the user terminal 103.

[0034] A management server cooperation module 510 cooperates with the management server 102, acquires the DVR status information 600 and the video information 420 stored in the management server 102, and displays this information on an output device 505 such as a display. Furthermore, the management server cooperation module 510 cooperates with the management server 102 and can perform various settings of the management server 102 . The DVR link module 511 operates the drive recorder 101 and configures the drive recorder 101 when the drive recorder 101 and the user terminal 103 are connected via an in-vehicle network such as Wi-Fi (registered trademark), for example.

[0035] In addition, the management terminal 105 can also be configured in the same way as the user terminal 103, and can operate the drive recorder 101 and management server 102 and configure them using a DVR collaboration module and a management server collaboration module stored in the main memory device.

[0036] FIG. 6 shows an example of the data structure of DVR status information 600. DVR status information 600 is a diagram explaining the data configuration when the microcomputer 301 of the drive recorder 101 transmits to the management server 102 the status information acquired from the DVR controller 303 and the location information acquired from the location information acquisition unit. The DVR status information 600 may also be referred to as status information regarding the drive recorder 101 .

[0037] In this embodiment, the microcomputer 301 generates 16-byte data of the DVR status information 600, and the communication processing unit 302 stores it in the payload and transmits it to the management server 102 based on the LPWA protocol. The protocol used for transmission is not limited to LPWA, and other communication methods and protocols may be used.

[0038] Item 610 indicates the item of the DVR status information 600 to be transmitted. Type 1 (620), Type 2 (630), and Type 3 (640) indicate three types of transmitted data content, and the numbers in each table indicate the data bit length. The total number of data bit lengths for each Type is 128 bits, or 16 bytes. In addition, there exists a free-format spare data configuration other than that described in item 610 as Type 4 (not shown).

[0039] In this embodiment, when the vehicle power supply 310 is being supplied, the communication processing unit 302 transmits the DVR status information 600 to the management server 102 at one-minute intervals. The microcomputer 301 acquires the position information, speed information, information indicating the recording state, and the like at three different times during this one interval, stores the position information and the like for these three points in time in a 16-byte payload, and can transmit the information to the management server 102 in one transmission process. Type 1 is a format for transmitting location information etc. at one point in time. Type 2 is a format for transmitting location information etc. at two points in time collectively. Type 3 is a format for transmitting information etc. at three points in time collectively.

[0040] FIG. 7 is a diagram illustrating an example of acquisition timing of location information to be transmitted. In Type 1, location information etc. acquired corresponding to the reference time indicated by (0) is transmitted. In Type 2, location information etc. acquired corresponding to two time points indicated by (0) and (1) is transmitted. In Type 3, location information etc. acquired corresponding to three time points indicated by (0), (1), and (2) is transmitted. In the example of DVR status information 600 in Fig. 6, items starting with (0) indicate information such as location information at a reference time. Items starting with (1) indicate location information acquired corresponding to time (1). Items starting with (2) indicate location information acquired corresponding to time (2).

[0041] For example, the microcontroller 301 acquires location information etc. at a 20-second cycle, acquires location information etc. at a reference time (0), generates Type 3 payload data by combining this information with information from 20 seconds earlier (2) and information from 40 seconds earlier (1), packetizes it, and the communications processing unit 302 transmits it to the management server 102 within 2 seconds of the reference time (0).

[0042] Returning to the DVR status information 600 in FIG. 6, the contents of each item 610 will be described. The format type is defined by 2 bits and defines the type of format of the data to be sent. For example, the value 0 indicates that the data is related to the drive recorder. The transmission type is defined by 2 bits and specifies whether the data format type is Type 1 to Type 4. The transmission number indicates the sequence number of the data to be transmitted.

[0043] (0) Time [seconds] indicates the time corresponding to the reference time (0). For example, it is defined in UTC time. The items starting with (0) below are information obtained corresponding to the reference item (0). (0) Latitude (World Geodetic System) indicates the latitude of the location information acquired by the location information acquisition unit. (0) Longitude (World Geodetic System) indicates the longitude of the location information acquired by the location information acquisition unit.

[0044] (0) Time [seconds] is the above time [seconds] shown in a different display format. (0) Zone indicates each coordinate area when, for example, the whole of Japan is divided into eight coordinate areas. (0) Latitude (World Geodetic System) is an alternative display format for the above latitude information, for example, differential position information from the reference position of the coordinate block identified by the above zone. (0) Longitude (World Geodetic System) is the above longitude information in a different display format, for example, differential position information from the reference position of each of the above zones.

[0045] (0) Speed ​​is information on the moving speed of the automobile and the drive recorder 101 mounted thereon, acquired by the DVR controller 303 and the microcomputer 301. (0) Positioning accuracy is information indicating the accuracy of positioning. (0) Recording status is information indicating the details of the recorded content, such as normal recording, event, special event, and stop. The emergency notification indicates whether or not an emergency notification is provided.

[0046] (1) Second difference indicates the time corresponding to a point in time (1) that is different from the reference time (0), and the time difference from the reference time (0) is stored, for example, a time within 62 seconds. The items beginning with (1) below are information obtained corresponding to the time in (1). (1) Latitude difference indicates the latitude information difference from the above (0) latitude. (1) Longitude difference indicates the latitude information difference from the above (0) longitude. (1) Speed ​​indicates the moving speed of the automobile, that is, the moving speed of the in-vehicle drive recorder 101. (1) Recording status indicates the recording status when the information in (1) was acquired. For example, there are normal recording, event, special event, stop, etc.

[0047] (2) Second difference indicates the time corresponding to a point in time (2) that is different from time (0)(1), and the time difference from the reference time (0) is stored, for example, within 30 seconds. The items beginning with (2) below are information obtained corresponding to the time in (2). (2) Latitude difference indicates the latitude information difference from the above (0) latitude. (2) Longitude difference indicates the latitude information difference from the above (0) longitude. (2) Speed ​​indicates the moving speed of the automobile, that is, the moving speed of the in-vehicle drive recorder 101. (2) Recording status indicates the recording status when the information in (2) was acquired. For example, there are normal recording, event, special event, stop, etc.

[0048] Reserved is a reserved area to be defined in the future. The recording error type indicates the state when recording is not successful, such as normal, SD card capacity is insufficient, no SD card, or an error. The power supply state indicates whether power is being supplied normally, i.e., from the vehicle power supply, or from the secondary battery. The model number is information for identifying the drive recorder 101 when there are multiple drive recorders 101.

[0049] FW Version indicates the firmware version. The time to positioning indicates the GNNS positioning period, for example, 30, 40, 50, 60, 80, 100, 120, or more seconds is stored. The SD card capacity indicates the capacity of the SD card. For example, values ​​indicating unknown, 8G or less, 16G, 32G, 64G, 128G, 256G, and 512G or more are stored. The recording mode indicates the resolution of the video information recorded by the drive recorder 101. For example, the effective vertical resolution may be 480 (VGA), 720, 1080 (HD), or other values.

[0050] The recording frame rate indicates the frame rate of the video information. For example, values ​​such as 1 fps, 5 fps, 15 fps, 30 fps, and 60 fps are stored. The number of recorded events indicates the number of events that occur. The camera internal temperature indicates the temperature inside the camera. Note that the contents of item 610 and the data bit length are examples, and other items and data lengths may be used. Also, the bit length of the payload that can be transmitted by LPWA is set to 128 bits, i.e., 16 bytes, but is not limited to this, and may be more or less bit lengths that correspond to the LPWA service.

[0051] According to the configuration of this embodiment, data for determining whether recording is being performed normally by the drive recorder 101, and data for identifying the cause if recording is not performed, can be transmitted to the management server 102. For example, by using the above-mentioned Types 1 to 4 DVR status information 600, it is possible to transmit information such as the normality of recording, firmware version, total recording time and number of overwrites that can be used to understand the lifespan of the SD card, acceleration sensor event notifications, location information, speed, and environmental information such as temperature, humidity, and air pressure obtained by the environmental sensor.

[0052] FIG. 8 shows an example of a communication sequence during normal use. For example, a vehicle power supply 310 such as an accessory power supply (ACC power supply) supplies power to a power supply 311 of the drive recorder 101 when the engine switch of the vehicle is ON or when the ACC power supply switch is ON. The state in which power is supplied to these power supplies 311 is called normal use. The DVR controller 303 notifies the microcomputer 301 that the power has been turned on, that recording has started, and information related to recording (steps 810 and 820).

[0053] The microcontroller 301 generates DVR status information 600 having the item Type 1 (620) in Figure 6 based on the time information, location information, and speed information acquired from the location information acquisition unit, information regarding recording acquired from the DVR controller 303, and status information of the drive recorder 101. Specifically, information including speed, positioning accuracy, recording status, whether or not an emergency notification has occurred, type of recording abnormality, power status indicating that the vehicle is powered by the recording mode, recording frame rate, etc. is coded to generate DVR status information 600. The microcomputer 301 controls the communication processing unit 302 to generate a packet carrying this DVR status information 600 in its payload, and transmits the packet to the management server 102 via the data center 104 (step 830).

[0054] As shown in FIG. 2, the management server 102 decodes the received DVR status information 600, which is 16 bytes of binary data, and acquires the position information and time information. The management server 102 displays this information on the user terminal 103 or the management terminal 105 by push distribution or in response to a request from the user terminal 103 or the management terminal 105 (step 840).

[0055] After the power is turned on, the microcomputer 301 notifies the DVR controller 303 of the location information and time information acquired from the location information acquisition section of the communication processing section 302 (step 850). The DVR controller 303 stores the recording information in association with the position information and time information in the SD card 306 or the like. In addition, the microcontroller 301 acquires location information and time information from the location information acquisition unit of the communication processing unit 302, for example, at intervals of 20 seconds, and combines three sets of location information and time information to generate Type 3 DVR status information 600, which it then transmits to the management server 102 at intervals of one minute.

[0056] When some event such as an impact due to an accident, sudden steering, or sudden stopping occurs, information relating to the event and corresponding to recording is notified from the DVR controller 303 to the microcomputer 301 (step 860). The microcomputer 301 notifies the DVR controller 303 of the location information and time information, and the DVR controller 303 stores the event-related recording information in the SD card 306 or the like in association with the location information and time information (step 870).

[0057] Microcomputer 301 generates DVR status information 600 describing the event-related recording status as (0) recording status, (1) recording status, (2) recording status, etc., and transmits it to management server 102 (step 880). The management server 102 decodes the DVR status information 600 to transmit information indicating that an event has occurred, its location information, time information, etc., to the user terminal 103 or the management terminal 105 via push distribution or in response to a request from the user terminal 103 or the management terminal 105, and displays the information (step 890).

[0058] In addition, the user terminal 103 or management terminal 105 that has been notified of the occurrence of an event such as an accident can store the drive recorder 101 on which the event occurred and the time, and can access the drive recorder 101 via Wi-Fi (registered trademark) or mobile data communication, etc., receive the video footage of the event, and check and manage it. In the example of FIG. 8, DVR status information 600 is transmitted to management server 102 at one-minute intervals. However, if the speed information acquired from the location information acquisition unit indicates that there is little movement, for example at a speed of 3 km / h or less, it may be determined that there is no change and DVR status information 600 may not be transmitted.

[0059] According to the communication sequence of FIG. 8 described above, during normal use when the vehicle power source 310 is supplied, the DVR status information 600 is sent to the management server 102 relatively frequently, for example, every minute, thereby enabling frequent and accurate monitoring of the location and status of the drive recorder 101. In addition, by acquiring location information every 20 seconds, consolidating the location information at three points in time to generate and transmit one DVR status information 600, it is possible to monitor the drive recorder 101 frequently and accurately while reducing communication costs and transmission power consumption.

[0060] In the above sequence, one-way communication from the communication processing unit 302 to the management server 102 is described, but it may be configured as two-way communication such that the management server 102 notifies the communication processing unit 302 of a receipt confirmation notification and other information. In addition, when a specific event occurs, such as when the emergency button on the drive recorder 101 is pressed or when an accident occurs, important data such as emergency notifications may be configured to continue to be notified until the power to the drive recorder 101 is cut off.

[0061] FIG. 9 shows an example of a communication sequence when driven by a secondary battery. For example, when the ACC power supply is turned off because the engine switch is turned off, when the supply of power from the vehicle power supply 310 to the power supply 311 of the drive recorder 101 is interrupted due to a fault such as a broken wire or a disconnected wiring caused by an accident, or when the power supply 311 breaks down and is no longer able to supply power, the microcontroller 301 and communication processing unit 302 are driven by power supplied from the secondary battery, and some of the information required to manage the drive recorder 101 in a power-saving manner is transmitted to the management server 102.

[0062] The DVR controller 303 notifies the microcomputer 301 that the ACC power supply has been turned off (step 910). In addition to the case where the DVR controller 303 actively notifies, the microcomputer 301 may be configured to detect that the ACC power supply has been turned off. In response to this ACC power OFF, the system is switched to backup battery drive, and the secondary battery 312 supplies power to the microcomputer 301 and the communication processing unit 302 (step 920).

[0063] The same process can be performed when the microcomputer 301 detects that the power supply from the vehicle power supply 310 has ceased, for example, when the power supply to the power supply 311 is interrupted or when the power supply 311 is broken and cannot supply power, etc. The same process can also be performed when the user intentionally turns off the power supply of the drive recorder 101. Turning the ACC power off, including these cases, may also be referred to as powering the drive recorder 101 off. Since the microcomputer 301 directly detects the power supply, if the microcomputer 301 is operating on a secondary battery while the power supply is being detected, or if no status notification is received from the DVR controller 303, it can be determined that a malfunction has occurred.

[0064] The microcontroller 301, which is powered by power from a secondary battery, generates DVR status information 600 having items of Type 1 (620) in Figure 6 based on the time information, location information, and speed information acquired from the location information acquisition unit in response to the ACC power being turned off, as well as information regarding recording acquired from the DVR controller 303 immediately before the ACC power being turned off and status information of the drive recorder 101. Specifically, information including speed, positioning accuracy, recording status, whether or not there is an emergency notification, type of recording abnormality, power status indicating that it is powered by a secondary battery, recording mode, recording frame rate, etc. is coded to generate DVR status information 600. The microcomputer 301 controls the communication processing unit 302 to generate a packet carrying this DVR status information 600 in its payload, and transmits the packet to the management server 102 via the data center 104 (step 930). Note that the information included in the DVR status information 600 listed above is merely an example, and it is not necessary to include all of it, and only a part of it may be included.

[0065] The information regarding recording, such as the type of recording abnormality, recording mode, recording frame rate, number of recording events, and status information of the drive recorder 101 obtained from the DVR controller 303 may be notified to the microcontroller 301 by the DVR controller 303 when the ACC power is turned off in step 810 and stored in the microcontroller 301, or may be notified to the microcontroller 301 at an earlier timing and stored. As explained in the example of the communication sequence during normal use in FIG. 8, the communication processing unit 302 transmits information to the management server 102 at one-minute intervals, storing location information, etc. at three points in time. However, if the ACC power is turned off during the one-minute interval, DVR status information 600 may be generated and transmitted that has a Type 2 (630) item that contains location information, etc. at the time the ACC power was turned off, in addition to location information, etc. at the next reference time (0).

[0066] In addition, priority is given to transmission of information related to recording, such as the type of recording abnormality, recording mode, recording frame rate, number of recording events, and status information of the drive recorder 101, and Type 1 information is transmitted when the ACC power is OFF. However, it is also possible to set the priority of "location information" as the transmission content of the DVR status information 600 higher, and to transmit Type 3 information containing location information of three locations indicating the movement trajectory, for example, when the vehicle was traveling even with the ACC power OFF.

[0067] Furthermore, a configuration may be adopted in which Types 1 to 3 are switched depending on the moving speed or moving distance. For example, when the moving speed is slow, such as 10 km / h or less, or when the moving distance from the previous measurement point is relatively short, such as within 50 m, the position information of two locations can be sufficient to indicate the moving trajectory, so the microcomputer 301 selects Type 2, which includes information on recording and status information of the drive recorder 101. On the other hand, when the vehicle is stopped and the moving speed is extremely slow, for example, 4 km / h or less, or when the moving distance is extremely short, for example, within 10 m, the microcomputer selects Type 1 information.

[0068] Specifically, when the stored location information is transmitted every 20 seconds, the microcontroller 301 calculates the distance between each piece of location information, and if the distance is below a certain threshold as exemplified above, it determines that the location information is unnecessary and discards it, and allocates the remaining data area to information regarding recording and status information of the drive recorder 101. All of Types 1 to 3 include status information on the "recording status" that indicates whether the recording is related to an event.

[0069] The management server 102 decodes the received DVR status information 600, which is 16 bytes of binary data, and obtains the position information and time information. The management server 102 transmits and displays the final location information and time information at the time the ACC power was turned off to the user terminal 103 or the management terminal 105 by push distribution or in response to a request from the user terminal 103 or the management terminal 105 (step 940).

[0070] Thereafter, in order to prolong the charge state of the secondary battery, the microcomputer 301 and the communication processing unit 302 enter a sleep state and operate only when determining the state of the drive recorder 101 and transmitting the information obtained therefrom. For example, the microcomputer 301 goes into a sleep state for 10 minutes after transmitting the DVR status information 600 (step 950).

[0071] After the sleep time ends, the microcomputer 301 activates the location information acquisition unit and acquires location information at that time. The microcomputer 301 compares the position information acquired here with the previously acquired position information, and if it determines that these positions are the same, it determines that no movement has occurred and no problem has occurred, and returns to a sleep state without transmitting any information to the management server 102 (step 960). Note that even if the values ​​of the position information are not exactly the same, if the change in the position information is within a relatively close range of values ​​determined in advance, such as a distance within a radius of 3 m, it is determined that the positions are the same.

[0072] The microcontroller repeatedly switches between the sleep state and checking the location information, compares the acquired location information with the previously acquired location information, and if it determines that the two locations are different, determines that some kind of abnormality has occurred (step 970), generates DVR status information 600, and transmits it to management server 102 (step 980). The management server 102 transmits an abnormality notification including the location information and time information to the user terminal 103 or the management terminal 105 by push distribution or in response to a request from the user terminal 103 or the management terminal 105, and displays it (step 990).

[0073] The DVR status information 600 transmitted here is, for example, Type 1 information that includes time information, position information, and speed information acquired from the position information acquisition unit. Since the DVR controller 303 is not started in principle when the camera is powered by a secondary battery, information obtained from the DVR controller 303, such as the type of recording abnormality, SD card capacity, recording mode, recording frame rate, number of recording events, and internal camera temperature, is not included in the DVR status information 600. However, the information may also include information that has been previously acquired.

[0074] When the microcontroller 301 and the communication processing unit 302 are powered by the vehicle power supply 310, the DVR status information 600 includes location information and information related to recording received from the DVR controller 303, and when the microcontroller 301 and the communication processing unit 302 are powered by the secondary battery 312, the DVR status information 600 includes location information but does not include information related to recording received from the DVR controller 303. With this configuration, when power is constantly supplied from the vehicle power source 310, it is possible to manage a wide range of information, including information related to recording. On the other hand, when the vehicle is powered by a secondary battery, a certain level of management accuracy can be maintained by appropriately controlling the range of information management, while limiting the startup of the DVR controller 303 reduces power consumption and extends the life of the secondary battery 312.

[0075] In order to extend the duration of the secondary battery's charged state and to improve the accuracy of checking for abnormal conditions, in this embodiment, if there is no change in the location information, the sleep time is extended successively from 10 minutes to 30 minutes, 1 hour, and 2 hours, and then the 2-hour cycle is continued. After that, if any abnormality is detected, such as a change in location information, or if an event occurs, the sleep time is changed, for example, to every 5 minutes. After that, if there are no more events, such as no more changes in location information, the sleep time is extended again.

[0076] If an abnormality is detected, microcomputer 301 shortens the sleep time and acquires location information from the location information acquisition unit. If the location information is different from the last time it was received, microcomputer 301 transmits DVR status information 600 to management server 102 via communication processing unit 302. On the other hand, if the location information is the same as the last time it was received, microcomputer 301 does not transmit DVR status information 600, assuming that the event occurrence was a false alarm.

[0077] In this way, when there is a high possibility that an abnormality has occurred, the management server 102 receives information more frequently, but when there is no change in position, no information is sent, so it is possible to determine whether it is a false alarm or a confirmed abnormality. However, if an abnormality such as that described above is detected, the DVR status information 600 may be transmitted without fail for a certain period of time, for example, 12 hours, even if the position information has not changed. Also, the sleep time may be always a constant cycle, such as every 30 minutes.

[0078] According to the communication sequence of Figure 9 described above, when the secondary battery is being used after the power supply from the vehicle power source 310 has been cut off, the frequency of transmitting DVR status information 600 is reduced compared to normal use, thereby saving power and extending the usable period of the secondary battery. In addition, the amount of information can be increased immediately after some event occurs, such as a change in location information, thereby improving the monitoring accuracy of the drive recorder 101, while the frequency of transmission can be reduced when no event occurs, thereby saving power.

[0079] Furthermore, when the microcomputer 301 and the communication processing unit 302 are driven by a vehicle power source, the communication processing unit 302 transmits the DVR status information 600 at regular intervals, for example, one minute, even if the change in position is within a relatively short range from the position indicated by the position information corresponding to the previous transmission of the DVR status information 600. On the other hand, when the microcomputer 301 and the communication processing unit 302 are driven by a secondary battery, the communication processing unit 302 does not transmit the DVR status information 600 if the change in position is within a predetermined relatively short range from the position indicated by the position information corresponding to the previous transmission of the DVR status information 600. By configuring in this manner, when power is constantly supplied from the vehicle power source 310, the management server 102 can manage the drive recorder 101 with high accuracy, while when the drive recorder is powered by a secondary battery, the frequency of information transmission can be appropriately controlled to extend the life of the secondary battery while maintaining a certain level of management accuracy.

[0080] If the location information could not be acquired when the power was turned off, the DVR status information 600 including the time when the ACC power was turned off with the location unknown may be notified. If location information is received thereafter, for example, 30 minutes later, it is determined that the device has moved, and DVR status information 600 including the location information can be transmitted. In an environment where the reception or non-reception of location information is unstable, the management server 102 may check the value of the Dilution of Precision (DOP) to determine whether or not there is an abnormality. Also, the microcomputer 301 may be configured not to transmit information continuously if the DOP is poor.

[0081] As shown in Figures 9 and 10, the frequency and transmission interval at which the communication processing unit 302 transmits DVR status information 600 are changed depending on whether the microcontroller 301 and communication processing unit 302 are driven by the vehicle power supply 310 or by the secondary battery 312. Such a configuration enables operation in which the amount of information transmitted to the management server 102 and the like is appropriately controlled while the time for which the charged state of the secondary battery 312 is maintained is extended as much as possible.

[0082] Specifically, when the microcontroller 301 and the communication processing unit 302 are driven by the secondary battery 312, the communication processing unit 302 transmits DVR status information 600 less frequently than when the microcontroller 301 and the communication processing unit 302 are driven by the vehicle power supply 310. In addition, when the microcontroller 301 and the communication processing unit 302 are driven by the vehicle power supply 310, the DVR status information 600 is transmitted at regular intervals, such as every minute, whereas when the microcontroller 301 and the communication processing unit 302 are driven by a secondary battery, the interval at which the communication processing unit 302 transmits the DVR status information 600 is gradually increased, for example, every 10 minutes, 30 minutes, 1 hour, and 2 hours. By configuring in this manner, when power is constantly supplied from the vehicle power source 310, the management server 102 can manage the drive recorder 101 with high accuracy, while when the drive recorder is powered by a secondary battery, the frequency of information transmission can be appropriately controlled to extend the life of the secondary battery 312 while maintaining a certain level of management accuracy.

[0083] In addition, the contents of the DVR status information 600 transmitted by the communication processing unit 302 are changed depending on whether the microcomputer 301 and the communication processing unit 302 are driven by the vehicle power supply 310 or by the secondary battery 312. Specifically, when the microcontroller 301 and the communication processing unit 302 are driven by the vehicle power source 310, the amount of location information included in the DVR status information 600 is increased compared to when the microcontroller 301 and the communication processing unit 302 are driven by the secondary battery 312.

[0084] More specifically, in the above embodiment, when the DVR is powered by the secondary battery 312, the location information contained in the transmitted DVR status information 600 is for one point in time, whereas when the DVR is powered by the vehicle power source 310, the location information is included for three points in time obtained every 20 seconds. By configuring in this manner, when power is constantly supplied from the vehicle power source 310, the management server 102 can manage the drive recorder 101 with high accuracy, while when the drive recorder 101 is powered by a secondary battery, the processing load of the microcontroller 301 and the communication processing unit 302 can be appropriately suppressed to maintain a certain level of management accuracy while extending the life of the secondary battery 312.

[0085] FIG. 10 shows another example of a communication sequence when driven by a secondary battery. The same reference numerals are used for the same flows as in Fig. 9, and only the differences from Fig. 9 will be described. In Fig. 10, the microcomputer 301 and the communication processing unit 302 are driven by a secondary battery, and repeat the determination of location information and the sleep operation, but if it is determined that the acquired location information is different from the previous location information (step 970), a start-up request is sent to the DVR controller 303 (step 1010). Upon receiving the start-up request, the DVR controller 303 temporarily starts up using power from the secondary battery, and transmits various status information, such as information about the drive recorder 101 and information about recording, that is held, to the microcomputer 301 (step 1020).

[0086] The microcomputer 301 generates DVR status information 600 that summarizes the various status information of the drive recorder 101 received and the position information and time information acquired at that time. The microcomputer 301 controls the communication processing unit 302 to transmit the generated DVR status information 600 to the management server 102 (step 1030). The management server 102 transmits an abnormality notification including the location information and time information to the user terminal 103 or the management terminal 105 by push distribution or in response to a request from the user terminal 103 or the management terminal 105, and displays it (step 1040).

[0087] The microcomputer 301 may be configured to transmit the position information and time information acquired from the communication processing unit 302 together with the start-up request to the DVR controller 303, and the DVR controller 303 may store the received position information and time information. Also, the DVR controller 303 that has received the start request may start recording in response to this. A situation in which the location information changes even when the secondary battery is being driven may be judged as an abnormal state, and in such a case, the drive recorder 101 may be started and recording may be started in response to the start request from the microcomputer 301, which may be useful for later analysis of the abnormal state. The recording time may be set to a short time such as 5 minutes to suppress consumption of the secondary battery 312, or one minute of recording may be performed every 10 minutes. Furthermore, the microcomputer 301 may be configured to acquire image information from the DVR controller 303 at regular intervals, and the communication processing unit 302 may be configured to intermittently transmit still image data with reduced image quality and reduced capacity to the management server 102 together with DVR status information 600.

[0088] In the above example, if there is no change in location information when powered by a secondary battery, power consumption is reduced by repeatedly starting and sleeping the microcontroller 301 and communication processing unit 302 temporarily, and if a change in location information occurs, the DVR controller 303 is temporarily started to obtain the necessary status information, thereby saving power and enabling efficient status monitoring. In addition, if the ACC power source is turned off and the secondary battery is used after an event that may have caused an accident, such as an impact, sudden steering, or sudden stop, the DVR status information 600 may be transmitted every time even if the position information does not change. A disconnection or the like may have occurred after the accident, causing the secondary battery to be used. In that case, continuing to transmit information from the drive recorder 101 may be useful in analyzing the accident.

[0089] Furthermore, the microcomputer 301 acquires engine ON / OFF information, and if it detects that the location information has changed while the engine is OFF and the vehicle is being driven by a secondary battery, it can notify the management server 102 of the possibility that theft has occurred and send a theft warning. In addition, when the drive recorder 101 is powered off and running on a secondary battery, but the engine is on and the vehicle is moving, the microcontroller 301 can also notify the management server 102 of an unauthorized driving warning, as this indicates the possibility of unauthorized driving. In addition, the microcontroller 301 may not determine the possibility of theft or unauthorized driving, but may instead transmit engine ON / OFF information, power supply status, and location information to the DVR status information 600, and the management server 102 may determine the possibility of theft or unauthorized driving.

[0090] In this embodiment, information on the location and date and time when an abnormality or event occurred is stored in the microcomputer 301 and is also transmitted to the management server 102. Using this location and date and time information, it is possible to search for recording files with the corresponding location and date and time stored in the drive recorder 101 or management server 102, to list which camera's files are applicable, and to lock the files. This process prevents files that may be related to the occurrence of an abnormality or event from being accidentally deleted, and also makes it easier to analyze the accident.

[0091] In addition, when the user terminal 103 is, for example, a smartphone and has a management server linkage module 510 implemented as a dedicated application, the location information and speed information acquired from the smartphone's input device 504 are compared with the location information and speed information acquired from the location information acquisition unit of the drive recorder 101, and the management server 102 can estimate the driver and passengers based on the degree of match.

[0092] For example, when the management server 102 receives an abnormality notification or event occurrence notification from the drive recorder 101, it can notify the user terminal 103 associated with the estimated driver or passenger by phone, email, message, or other method. Furthermore, if the passengers' schedules are managed in advance by the management server 102, it is also possible to determine whether the passengers are actually in the car.

[0093] In addition, if the image sensor of the camera 304 has an AI processing function for performing pre-processing, the microcontroller 301 may transmit data indicating the results of image recognition based on the image captured by the camera 304 to the management server 102. Although LPWA communications may have significant limitations on the amount of data that can be transmitted per unit time, even in this case, a reduction in the amount of data can be expected compared to the case of transmitting video data, and as a result, data indicating the results of image recognition can be transmitted with low latency to other devices such as the management server 102. The management server 102 and other devices may perform various processes based on the data indicating the results of image recognition.

[0094] The present invention is not limited to the above-described embodiments, and includes various modified examples. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

[0095] In addition, the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. In addition, the above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD. In addition, the control lines and information lines shown are those that are considered necessary for the explanation, and not all control lines and information lines in the product are necessarily shown. In reality, it can be considered that almost all components are connected to each other.

[0096] The scope of the present invention is not limited to the configurations explicitly described in the specification, but includes combinations of various aspects of the present invention disclosed in this specification. The configurations of the present invention that are to be patented are specified in the attached claims, but it is our intention to include configurations disclosed in this specification in the claims in the future, even if they are not currently specified in the claims.

[0097] The present invention is not limited to the configuration described in the above-mentioned embodiment. The components of each of the above-mentioned embodiments and modifications may be arbitrarily selected and combined. Any components of each of the embodiments and modifications may be arbitrarily combined with any components described in the means for solving the invention or any components that embody any components described in the means for solving the invention. We intend to acquire rights to these as well through amendments to this application or divisional applications. Even if there is a description such as "in the case of" or "when", this is not intended to describe a configuration that is limited to that case or time. We also disclose configurations that are not in these cases or times, and we intend to acquire rights. Furthermore, the parts described in order are not limited to this order. We also disclose configurations in which some parts are deleted or the order is changed, and we intend to acquire rights.

[0098] In addition, we intend to obtain rights to the overall design or partial design by converting to a design registration application. The drawings depict the entire device in solid lines, but they include not only the overall design but also partial designs claimed for a part of the device. For example, some parts of the device may be partial designs, and the drawings include some parts of the device as partial designs regardless of the parts. A part of the device may be a part of the device, or a part of that part. We intend to obtain rights to the overall design, as well as partial designs in which any part of the solid line part of the drawing is shown as a broken line part. In addition, the modules, parts, and components inside the device's casing, all of which are shown in the drawings, are subject to trade independently, and we intend to obtain rights to them by converting to a design registration application.

[0099] The above-mentioned embodiment discloses at least the following configuration. (1) A drive recorder, A camera for recording, a communication processing unit that transmits status information related to the drive recorder; A control unit that controls the communication processing unit; a power supply unit that receives power from a vehicle power supply and drives the control unit and the communication processing unit; A secondary battery; Equipped with The drive recorder drives the control unit and the communication processing unit using the secondary battery. With this configuration, it is possible to provide a mechanism for maintaining some of the functions of the drive recorder using the secondary battery even if the power supply from the vehicle power source is cut off. (2) A drive recorder as described in (1), in which the frequency at which the communication processing unit transmits the status information is changed depending on whether the control unit and the communication processing unit are driven by the vehicle power source or the secondary battery. (3) A drive recorder as described in (1) or (2), in which the communication processing unit transmits the status information less frequently when the control unit and the communication processing unit are driven by the secondary battery compared to when the control unit and the communication processing unit are driven by the vehicle power source. (4) A drive recorder as described in any one of (1) to (3), wherein the interval at which the communication processing unit transmits the status information is changed when the control unit and the communication processing unit are driven by the vehicle power source and when the control unit and the communication processing unit are driven by the secondary battery. (5) A drive recorder as described in any one of (1) to (4), wherein when the control unit and the communication processing unit are driven by the vehicle power source, the status information is transmitted at constant intervals, and when the control unit and the communication processing unit are driven by the secondary battery, the communication processing unit transmits the status information at gradually increasing intervals. By configuring as described above in (2) to (5), when power is supplied from the vehicle power source, the management server can manage the drive recorder with high accuracy, while when the drive recorder is powered by a secondary battery, the frequency and interval of information transmission can be appropriately controlled to extend the life of the secondary battery while maintaining a certain level of management accuracy. (6) the communication processing unit has a location information acquisition unit, When the control unit and the communication processing unit are driven by the secondary battery, if a change in position from a position indicated by position information corresponding to a previous transmission of the status information is within a predetermined range, the communication processing unit does not transmit the status information; A drive recorder as described in any one of (1) to (5), wherein when the control unit and the communication processing unit are driven by the vehicle power source, the communication processing unit transmits the status information even if the position change is within a predetermined range from the position indicated by the position information corresponding to the previous transmission of the status information. By configuring in this manner, when power is supplied from the vehicle power source, the management server can manage the drive recorder with high accuracy, while when the drive recorder is powered by a secondary battery, the frequency of information transmission can be appropriately controlled to extend the life of the secondary battery while maintaining a certain level of management accuracy. (7) A drive recorder as described in any one of (1) to (6), in which the content of the status information transmitted by the communication processing unit is changed depending on whether the control unit and the communication processing unit are driven by the vehicle power source or the secondary battery. (8) The drive recorder according to (7), wherein the number of pieces of location information included in the status information is increased when the control unit and the communication processing unit are driven by the vehicle power source compared to when the control unit and the communication processing unit are driven by the secondary battery. By configuring as described above in (7) and (8), when power is supplied from the vehicle power source, the management server can manage the drive recorder with high accuracy. Meanwhile, when the drive recorder is powered by a secondary battery, the processing load on the microcontroller and communication processing unit can be appropriately suppressed, thereby making it possible to extend the life of the secondary battery while maintaining a certain level of management accuracy. (9) A drive recorder as described in (7) or (8), in which, when the control unit and the communication processing unit are driven by the secondary battery, the communication processing unit transmits, in the status information, at least one of location information and time information obtained in response to the power of the drive recorder being turned off. With this configuration, the final location and time when the power supply from the vehicle power source was cut off can be notified to the management server and managed. (10) A DVR control unit that controls the camera, When the control unit and the communication processing unit are driven by the vehicle power source, the state information includes location information and information related to recording received from the DVR control unit, When the control unit and the communication processing unit are driven by the secondary battery, the status information includes location information but does not include information related to recording received from the DVR control unit. The drive recorder according to any one of (7) to (9). With this configuration, when power is supplied from the vehicle power source, it is possible to manage a wide range of information, including information related to recording, while when powered by a secondary battery, it is possible to maintain a certain level of management accuracy by appropriately controlling the range of information management, while limiting the startup of the DVR controller, thereby reducing power consumption and extending the life of the secondary battery. (11) A drive recorder as described in (10), in which, when the control unit and the communication processing unit are driven by the secondary battery, if the change in position from the position indicated by the position information corresponding to the previous transmission of the status information exceeds a predetermined range, the control unit activates the DVR control unit and obtains information related to the recording from the DVR control unit. With this configuration, if there is no change in the location information when the secondary battery is in operation, power consumption is reduced by repeatedly temporarily starting and sleeping the microcontroller and communication processing unit, and if a change in the location information occurs, the DVR controller is temporarily started to obtain the necessary status information, thereby achieving power savings and efficient status monitoring. (12) The drive recorder according to any one of (1) to (11), wherein the communication processing unit performs wireless communication of an LPWA system. With this configuration, the drive recorder can perform long-distance communication with low power consumption, so that the drive recorder's status information can be transmitted while maximizing the duration of the secondary battery. (13) an image processing unit that performs image recognition based on the image captured by the camera; The drive recorder according to any one of (1) to (12), wherein the communication processing unit further transmits data indicating a result of the image recognition. With this configuration, the drive recorder can transmit the results of image recognition based on the video captured by the camera to other devices with low latency, even when performing wireless communication using LPWA or other methods. (14) Camera and a communication processing unit that transmits status information related to the drive recorder; A control unit that controls the communication processing unit; a power supply unit that receives power from a vehicle power supply and drives the control unit and the communication processing unit; A secondary battery; In a drive recorder comprising: A program for causing the control unit to execute any one of the processes described in (1) to (13). With this configuration, a mechanism can be implemented by program that maintains some of the functions of the drive recorder using the secondary battery even if the power supply from the vehicle power source is cut off. (15) A receiving unit that receives the status information from the communication processing unit of the drive recorder according to any one of (1) to (13); a transmitting unit configured to transmit information acquired by decoding the received status information to a user terminal; 2. A management server having: By configuring it in this way, it is possible to densely store and transmit state information and other information necessary for management within a limited payload, and the information can be decoded by the management server and presented to the user.

[0100] The inventions shown in (1) to (15) above can be arbitrarily combined. For example, at least a part of the configuration of at least one of the inventions after (2) may be added to all or a part of the configuration of the invention shown in (1). In particular, it is preferable to add at least a part of the configuration of at least one of the inventions after (2) to the invention shown in (1). In addition, any configuration may be extracted from the inventions shown in (1) to (15) and the extracted configurations may be combined. The applicant of this application intends to obtain rights to the inventions including these configurations. In addition, even if there is a description such as "in the case of" or "when", it is not intended to describe the configuration as being limited to that case or time. These are examples of better configurations, and the applicant intends to obtain rights to configurations other than these cases or times. In addition, the parts described in order are not limited to this order. Configurations in which some parts have been deleted or the order has been changed are also disclosed, and the applicant intends to obtain rights. [Explanation of symbols]

[0101] 1...DVR management system, 101...drive recorder, 102...management server, 103...user terminal, 104...data center, 105...management terminal, 301...microcomputer, 302...communication processing unit, 303...DVR controller, 304...camera, 305...acceleration sensor, 306...SD card, 307...GNSS antenna, 308...wireless communication antenna, 310...vehicle power supply, 311...power supply, 312...secondary battery, 313...DC / DC converter

Claims

1. A drive recorder, A camera for recording, a communication processing unit that transmits status information related to the drive recorder; A control unit that controls the communication processing unit; a power supply unit that receives power from a vehicle power supply and drives the control unit and the communication processing unit; A secondary battery; Equipped with The control unit and the communication processing unit are driven by the secondary battery. Drive recorder.

2. The drive recorder according to claim 1, wherein the frequency at which the communication processing unit transmits the status information is changed depending on whether the control unit and the communication processing unit are driven by the vehicle power source or the secondary battery.

3. A drive recorder as described in claim 1 or 2, wherein the communication processing unit transmits the status information less frequently when the control unit and the communication processing unit are driven by the secondary battery compared to when the control unit and the communication processing unit are driven by the vehicle power source.

4. A drive recorder as described in any one of claims 1 to 3, wherein the interval at which the communication processing unit transmits the status information is changed when the control unit and the communication processing unit are driven by the vehicle power source and when the control unit and the communication processing unit are driven by the secondary battery.

5. A drive recorder as described in any one of claims 1 to 4, wherein when the control unit and the communication processing unit are driven by the vehicle power source, the status information is transmitted at constant intervals, and when the control unit and the communication processing unit are driven by the secondary battery, the communication processing unit transmits the status information at gradually increasing intervals.

6. the communication processing unit has a location information acquisition unit, When the control unit and the communication processing unit are driven by the secondary battery, if a change in position from a position indicated by position information corresponding to a previous transmission of the status information is within a predetermined range, the communication processing unit does not transmit the status information; When the control unit and the communication processing unit are driven by the vehicle power source, the communication processing unit transmits the status information even if the position change is within a predetermined range from the position indicated by the position information corresponding to the previous transmission of the status information. The drive recorder according to any one of claims 1 to 5.

7. A drive recorder as described in any one of claims 1 to 6, wherein the content of the status information transmitted by the communication processing unit is changed when the control unit and the communication processing unit are driven by the vehicle power source and when the control unit and the communication processing unit are driven by the secondary battery.

8. The drive recorder of claim 7, wherein the number of pieces of location information included in the status information is increased when the control unit and the communication processing unit are driven by the vehicle power source compared to when the control unit and the communication processing unit are driven by the secondary battery.

9. A drive recorder as described in claim 7 or 8, wherein when the control unit and the communication processing unit are driven by the secondary battery, the communication processing unit transmits at least one of location information and time information obtained in response to the power supply of the drive recorder being turned off, by including it in the status information.

10. A DVR control unit that controls the camera, When the control unit and the communication processing unit are driven by the vehicle power source, the state information includes location information and information related to recording received from the DVR control unit, When the control unit and the communication processing unit are driven by the secondary battery, the status information includes location information but does not include information related to recording received from the DVR control unit. The drive recorder according to any one of claims 7 to 9.

11. The drive recorder of claim 10, wherein when the control unit and the communication processing unit are driven by the secondary battery, if the change in position from the position indicated by the position information corresponding to the previous transmission of the status information exceeds a predetermined range, the control unit activates the DVR control unit and obtains information related to the recording from the DVR control unit.

12. 12. The drive recorder according to claim 1, wherein the communication processing unit performs wireless communication in accordance with a low power wide area (LPWA) system.

13. an image processing unit that performs image recognition based on the image captured by the camera; The drive recorder according to claim 12 , wherein the communication processing unit transmits data indicating a result of the image recognition.

14. A camera for recording, a communication processing unit that transmits status information related to the drive recorder; A control unit that controls the communication processing unit; a power supply unit that receives power from a vehicle power supply and drives the control unit and the communication processing unit; A secondary battery; In a drive recorder comprising: A program for causing the control unit to execute the process according to any one of claims 1 to 13.

15. A receiving unit that receives the state information from the communication processing unit of the drive recorder according to any one of claims 1 to 13; a transmitting unit configured to transmit information acquired by decoding the received status information to a user terminal; A management server having:

Images