JP6145780B2 - Wearable camera system and video data transfer method - Google Patents

Description

  The present invention relates to a wearable camera system. For example, the present invention relates to a wearable camera system including a wearable camera that is an imaging device that can be attached to a human body or worn clothes.

  In recent years, for example, in order to support the operations of police officers and guards, the introduction of wearable cameras used by police officers and guards is being studied.

  As a conventional example using a wearable camera, for example, there is a wearable surveillance camera system described in Patent Document 1. This wearable surveillance camera system uses an encoding server means for storing a video signal and an audio signal from a CCD camera means and a microphone means worn on the body, and a date / time information signal from a built-in clock means in a pouch means worn on the body. The date and time information encoded and converted into character information can be superimposed on the captured video and recorded.

JP 2006-148842 A

  In the wearable camera system, for example, video data captured by the wearable camera is transferred to a server and recorded in a storage, and the video data is stored so that it can be searched and viewed later. Since video data has a large data size, when transferring video data from a wearable camera to a server, it takes a lot of time to transfer the data, and the wearable camera can be taken and taken at any time and place by the user. May interfere with the use of.

  In order to solve the above-described problems, an object of the present invention is to provide a wearable camera system that can shorten the time for transferring video data and improve convenience.

The present invention is a wearable camera system comprising a wearable camera that can be worn by a user and an in-vehicle recorder mounted on a vehicle on which the user rides, wherein the wearable camera captures a first video, and The stored first video is stored, the stored first video is transferred to the in-vehicle recorder, and the in-vehicle recorder images the second video and is sent from the wearable camera. 1 video and the second video are stored in association with attribute information indicating the content of each video set according to the state of the attribute information addition switch, and the stored first and second videos are stored. A wearable camera system for transferring to a server according to the priority indicated by the attribute information is provided.

The present invention is also a video data transfer method using a wearable camera that can be worn by a user and an in-vehicle recorder mounted on a vehicle on which the user gets, wherein the wearable camera captures the first video. Then, the captured first video is stored, the stored first video is transferred to the in-vehicle recorder, and the in-vehicle recorder captures the second video and is sent from the wearable camera. The first video and the second video are stored in association with attribute information indicating the content of each video set according to the state of the attribute information addition switch, and the stored first and second videos are stored. Is transferred to a server in accordance with the priority indicated by the attribute information.

  ADVANTAGE OF THE INVENTION According to this invention, the time at the time of transferring video data in a wearable camera system can be shortened, and the convenience can be improved.

Explanatory diagram regarding the use of video data captured by the wearable camera and the outline of the wearable camera system according to the present embodiment The block diagram which shows an example of the internal structure of the vehicle-mounted camera system which concerns on this embodiment, and vehicle-mounted PC A block diagram showing an example of an internal configuration of a wearable camera according to the present embodiment Front view showing an example of the appearance of the wearable camera according to the present embodiment The figure which shows the state with which the user mounted | worn the wearable camera which concerns on this embodiment. The figure which shows an example of the data structure of recording data The figure which shows an example of the data structure of a video recording list The flowchart which shows an example of the procedure regarding the transfer operation | movement of the recording data from the wearable camera to a vehicle-mounted recorder in this embodiment The flowchart which shows an example of the procedure regarding the transfer operation | movement of the recording data from the vehicle-mounted recorder to a back end server in this embodiment.

  Hereinafter, an embodiment (hereinafter, referred to as “this embodiment”) that specifically discloses a wearable camera according to the present invention and a wearable camera system that uses the wearable camera will be described in detail with reference to the drawings.

  FIG. 1 is an explanatory diagram regarding the outline of the wearable camera system 100 according to the present embodiment and the use of video data captured by the wearable camera 10. The wearable camera 10 of the present embodiment is an imaging device that can be worn on a body or clothes worn by a user (for example, a police officer (Officer)) 7. The wearable camera 10 has a communication function for performing communication with an in-vehicle system 60 mounted in a car, a server (back-end server) SV in a user organization, and the like.

  In the wearable camera system 100, the wearable camera 10 and the in-vehicle system 60 constitute the front end system 100A, and the management software 70 on the network, the server SV, and the in-station PC 71 which is a PC in the user organization constitute the back end system 100B. . The management software 70 is executed by, for example, the in-station PC 71 or the server SV.

  Here, as an example of the wearable camera system 100 according to the present embodiment, a case where it is used in the police station 5 will be described. In this case, the police officer 7 performs imaging using the wearable camera 10 as a user, and transfers and stores the captured image data to the back-end system 100B in the police station 5, for example. Wearable camera 10 is not limited to a police officer as a user, and may be used in various other establishments (for example, a security company). In this embodiment, a police officer is mainly exemplified as a user.

  The front-end system 100A includes a wearable camera 10 that can be worn by the police officer 7 dispatched to the forefront of the scene, a portable terminal 50 that is held in the police car that the police officer holds or rides, and the police car 6 And an in-vehicle system 60 installed. The in-vehicle system 60 includes an in-vehicle camera 61, an in-vehicle recorder 62, an in-vehicle PC 63, a communication unit, and the like, and configures an in-vehicle camera system, a video management system, and the like.

  The in-vehicle camera 61 is provided at a predetermined position of the police car 6 and includes an imaging device (not shown) that captures images around the police car 6 constantly or at a predetermined timing. The in-vehicle camera 61 is, for example, a front camera (not shown) for imaging the front of the police car 6, and a back seat camera (for example, a seat on which a suspect is sitting) in the police car 6. (Not shown). The video data imaged by the in-vehicle camera 61 is accumulated in the in-vehicle recorder 62, for example, by executing a recording operation. A plurality of in-vehicle cameras 61 may be provided.

  Note that the front camera and the back seat camera may be provided with a microphone (not shown) that collects sounds inside and outside the patrol car 6. In this case, it is also possible to pick up (record) sound produced by the police officer 7 or the suspect in the police car 6.

  The in-vehicle recorder 62 stores video data captured by the in-vehicle camera 61. The in-vehicle recorder 62 can acquire and store video data captured by the wearable camera 10. Further, the in-vehicle recorder 62 may manage meta information such as attribute information given to the video data.

  The in-vehicle PC 63 may be a PC that is fixedly installed in the police car 6 or a wireless communication device such as a PC, smartphone, mobile phone, tablet terminal, PDA (Personal Digital Assistant) that can be carried outside the police car 6. May be.

  The in-vehicle PC 63 enables cooperation between the in-vehicle system 60 and the wearable camera 10 by executing management software (not shown). Further, a UI (User Interface) (for example, an operation device, a display device, and an audio output device) of the in-vehicle PC 63 is also used as a UI for operating the in-vehicle recorder 62.

  When the police officer 7 is dispatched from the police station 5 with a predetermined requirement (for example, patrol), for example, the wearable camera 10 is mounted, and the police officer 7 gets on the police car 6 equipped with the in-vehicle system 60 and heads for the site. In the front-end system 100A, for example, an image of the scene where the police car 6 arrives is captured by the in-vehicle camera 61 of the in-vehicle system 60, and a police officer 7 gets off the police car 6 and captures a more detailed image of the scene by the wearable camera 10. To do.

  Video data of a moving image or a still image captured by the wearable camera 10 is stored in a storage device such as a memory of the wearable camera 10, for example. The wearable camera 10 transfers (uploads) various data including video data captured by the wearable camera 10 from the storage device of the wearable camera 10 to the back-end system 100B.

  Video data of a moving image or a still image captured by the in-vehicle camera 61 is stored, for example, in a storage such as a hard disk (HDD (Hard Disk Drive)) or an SSD (Solid State Drive) included in the in-vehicle recorder 62 of the in-vehicle system 60. The in-vehicle system 60 (for example, the in-vehicle recorder 62) transfers (uploads) various data including video data captured by the in-vehicle camera 61 from the storage of the in-vehicle system 60 to the back-end system 100B.

  Data transfer to the back-end system 100B is performed by connecting by wireless communication from the field, for example, or when patrol is completed and returning to the police station 5, wireless communication, wired communication, or manual (for example, storage) Carry the media).

  In the present embodiment, an operation of transferring (uploading) video data captured by the wearable camera 10 to the back-end system 100B via the in-vehicle system 60 will be mainly described. In this case, video data of a moving image or a still image captured by the wearable camera 10 is transferred from the wearable camera 10 to the in-vehicle recorder 62 of the in-vehicle system 60 and stored. Then, the moving image or still image data captured by the wearable camera 10 or the in-vehicle camera 61 and stored in the in-vehicle recorder 62 is transferred (uploaded) from the in-vehicle recorder 62 to the back-end system 100B. Note that if data transfer from the wearable camera 10 to the in-vehicle system 60 and data transfer from the in-vehicle system 60 to the back-end system 100B are performed simultaneously, the transfer time becomes the later time, and the data transfer efficiency increases. There may not be. For this reason, you may make it transfer from the wearable camera 10 to the vehicle-mounted recorder 62 of the vehicle-mounted system 60 in the period when the vehicle-mounted system 60 is not transferring image data etc. to the back-end system 100B.

  Note that video data captured by the wearable camera 10 can be stored in the storage of the in-vehicle PC 63 and transferred (uploaded) from the in-vehicle PC 63 to the back-end system 100B.

  The back-end system 100B includes a server SV installed in the police station 5 or elsewhere, management software 70 for communicating with the front-end system 100A, and a station PC 71.

  The server SV includes a storage such as an HDD or SSD inside or outside the apparatus. In the back-end system 100B, the server SV accumulates video data and other data transferred from the front-end system 100A in a storage, and constructs a database. For example, the server SV receives video data transferred from the wearable camera 10 or the in-vehicle system 60 (for example, the in-vehicle recorder 62), and stores it in the storage.

  The video data stored in the back-end system 100B is used for, for example, operation / verification of the case by a person in charge in the related department in the police station 5, and a predetermined storage medium (for example, DVD: Digital Versatile Disk) is used as necessary. ) Is copied and submitted as evidence in a predetermined scene (for example, trial). In the present embodiment, the wearable camera 10 worn by the police officer 7 can be used to acquire and store the evidence video at the site more accurately.

  When the police officer 7 is dispatched from the police station 5 and uses the wearable camera 10, the identification information of the police officer 7 (for example, an officer ID (Officer ID)), the identification information of the wearable camera 10 used by the police officer ( For example, camera ID (Camera ID) and identification information (for example, car ID (Car ID)) of the police car 6 used by the police officer 7 are set and registered using the in-station PC 71. As a result, the information is accumulated in the server SV. With respect to video data, it is possible to clearly distinguish when and what police officers have captured using which camera.

  The setting registration of the police officer 7 and the wearable camera 10 is performed, for example, by the person in charge in the police station 5 or the police officer 7 to be dispatched operating the operation device (not shown) of the in-station PC 71, and the in-station PC 71 installs the management software 70. It is done by executing. In this setting registration, information other than the Office ID, Camera ID, and Car ID may be input via the operating device of the in-station PC 71.

  That is, the management software 70 includes, for example, an application for managing the personnel of the police officer 7, an application for managing dispatch of the police car 6 and the like, and an application for managing taking-out of the wearable camera 10. The management software 70 includes an application for searching and extracting specific video data based on attribute information from a plurality of video data stored in the server SV, for example.

  FIG. 2 is a block diagram illustrating an example of the internal configuration of the in-vehicle camera system 65 and the in-vehicle PC 63. In the in-vehicle system 60, the in-vehicle camera 61 and the in-vehicle recorder 62 constitute an in-vehicle camera system 65.

  The in-vehicle recorder 62 includes a CPU (Central Processing Unit) 101, a communication unit 102, a flash ROM (Read Only Memory) 104, a RAM (Random Access Memory) 105, a microcomputer (μCON, microcontroller) 106, and a GPS (Global Positioning System) 107. , GPIO (General Purpose Input / Output) 108, switch 109, LED (Light Emitting Diode) 110, and storage 111.

  For example, the CPU 101 performs control processing for overall control of operations of each unit of the in-vehicle recorder 62, data input / output processing with other units, data calculation (calculation) processing, and data storage processing. .

  The communication unit 102 communicates with an external device via a wireless line or a wired line. The wireless communication includes, for example, wireless LAN (W-LAN (Local Area Network)) communication, near field communication (NFC), and Bluetooth (registered trademark). The wireless LAN communication is performed in accordance with, for example, the IEEE 802.11n standard of Wi-fi (registered trademark). The wired communication includes, for example, wired LAN communication and USB (Universal Serial Bus) communication. The CPU 101 and the communication unit 102 are connected via, for example, PCI (Peripheral Component InterConnect) or USB.

  For example, the communication unit 102 performs wireless communication or wired communication with the in-vehicle camera 61, the in-vehicle PC 63, the wearable camera 10, the in-station PC 71 of the police station 5, and the server SV. The communication unit 102 is wirelessly connected to the wearable camera 10 and receives various data including video data transmitted from the wearable camera 10.

  The flash ROM 104 is a memory that stores a program and data for controlling the CPU 101, for example. Also, various setting information is held. The RAM 105 is a work memory used in the operation of the CPU 101, for example. For example, a plurality of RAMs 105 are provided.

  The microcomputer 106 is, for example, a kind of microcomputer and is connected to each unit (for example, the GPS 107, the GPIO 108, the switch 109, and the LED 110) related to the external interface, and performs control related to the external interface. The microcomputer 106 is connected to the CPU 101 via, for example, a UART (Universal Asynchronous Receiver Transmitter).

  The GPS 107 receives, for example, the current position information and time information of the in-vehicle recorder 62 from a GPS transmitter (not shown) and outputs it to the CPU 101. This time information is used for correcting the system time of the in-vehicle recorder 62.

  The GPIO 108 is, for example, a parallel interface, and inputs and outputs signals between the CPU 101 and an external device (not shown) connected via the GPIO 108. For example, various sensors (for example, a speed sensor, an acceleration sensor, and a door opening / closing sensor) are connected to the GPIO 108.

  The switch 109 is a switch such as a button provided as an input device for the user to perform an operation input of the in-vehicle recorder 62. The switch 109 is, for example, a recording button for starting or stopping recording of video data imaged by the in-vehicle camera 61, and an application for giving attribute information or meta information to the video data imaged by the in-vehicle camera 61. Button.

  The LED 110 is provided as a display device that indicates the operating state of the in-vehicle recorder 62. The LED 110 lights, turns off, and blinks, for example, a power-on state (on / off state) of the in-vehicle recorder 62, a recording state, a connection state of the in-vehicle recorder 62 to the LAN, and a use state of the LAN connected to the in-vehicle recorder 62. Etc. are displayed.

  The storage 111 is configured by, for example, an SSD, an HDD, or the like, and stores and accumulates video data captured and recorded by the in-vehicle camera 61. The storage 111 stores and accumulates video data captured and recorded by the wearable camera 10 when video data is transferred from the wearable camera 10. The storage 111 may store data other than video data. The storage 111 is connected to the CPU 101 via, for example, SATA (Serial ATA). A plurality of storages 111 may be provided.

  The in-vehicle PC 63 includes a CPU 201, an I / O (Input / Output) control unit 202, a communication unit 203, a memory 204, an input unit 205, a display unit 206, and a speaker 207. The in-vehicle PC 63 can communicate with the in-vehicle recorder 62, and can also communicate with the server SV and the in-station PC 71 of the back-end system 100B.

  For example, the CPU 201 authenticates whether or not the police officer 7 can log in to the in-vehicle system 60 by an input operation of the police officer 7 on a login screen (not shown) to the in-vehicle system 60 displayed on the display unit 206. The input operation of the police officer 7 is, for example, an operation for inputting an officer ID and a password. Various types of information related to the police officer 7 to whom login is permitted are stored in advance in, for example, the memory 204, and the CPU 201 uses the information on the login permission target stored in the memory 204 in advance to use the police officer 7. Whether to log in to the in-vehicle system 60 is determined. The login may be a login to the in-vehicle system 60 via the in-vehicle PC 63, or a login to an application that operates the in-vehicle system 60 mounted in the in-vehicle PC 63.

  The I / O control unit 202 controls data input / output between the CPU 201 and each unit of the in-vehicle PC 63 (for example, the communication unit 203, the input unit 205, the display unit 206, and the speaker 207). Relay data to. The I / O control unit 202 may be configured integrally with the CPU 201.

  The communication unit 203 performs wired or wireless communication with, for example, the in-vehicle recorder 62 or the back-end system 100B side. When the police officer 7 is logging in to the in-vehicle system 60, the communication unit 203 transfers and copies the login information stored in the memory 204 to the wearable camera 10, while the police officer 7 logs in to the in-vehicle system 60. If not, the login information is not transferred to the wearable camera 10. The login information includes, for example, an officer ID, a camera ID, and a car ID.

  The memory 204 is configured using, for example, RAM, ROM, nonvolatile or volatile semiconductor memory, functions as a work memory when the CPU 201 operates, and stores a predetermined program and data for operating the CPU 201. . The memory 204 stores, for example, login information related to the police officer 7 who is permitted to log in to the in-vehicle system 60.

  The input unit 205 is a UI for receiving an input operation of the police officer 7 and notifying the CPU 201 via the I / O control unit 202, and is a pointing device such as a mouse or a keyboard. The input unit 205 may be configured using, for example, a touch panel or a touch pad that is arranged corresponding to the screen of the display unit 206 and can be operated by a finger of the police officer 7 or a stylus pen.

  The display unit 206 is a display device configured using, for example, an LCD (Liquid Crystal Display) or an organic EL (Electroluminescence), and displays various types of information. The display unit 206 is included in the video data under the instruction of the CPU 201 when video data captured (recorded) by the wearable camera 10 is input in response to an input operation of the police officer 7, for example. Display video on the screen.

  The speaker 207 is included in the video data under the instruction of the CPU 201 when video data including sound captured (recorded) by the wearable camera 10 is input in response to an input operation of the police officer 7, for example. Output audio. The display unit 206 and the speaker 207 may be configured separately from the in-vehicle PC 63.

  FIG. 3 is a block diagram illustrating an example of the internal configuration of the wearable camera 10. FIG. 4 is a schematic view showing a state where the police officer 7 wears the wearable camera 10, and FIG. 5 is a front view showing an example of the appearance of the wearable camera 10.

  As shown in FIG. 3, the wearable camera 10 includes an imaging unit 11, a GPIO 12, a RAM 13, a ROM 14, and a storage unit 15. The wearable camera 10 includes an EEPROM (Electrically Erasable Programmable ROM) 16, an RTC (Real Time Clock) 17, and a GPS 18. The wearable camera 10 includes an MCU (Micro Controller Unit) 19, a communication unit 21, a USB 22, a contact terminal 23, a power supply unit 24, and a battery 25.

  The wearable camera 10 includes a recording switch SW1, a snapshot switch SW2, and an attribute information addition switch SW3 as an example of an operation input unit. The wearable camera 10 includes LEDs 26a, 26b, and 26c and a vibrator 27 as an example of a state display unit.

  The imaging unit 11 includes, for example, an imaging lens 11a (see FIG. 5) and a solid-state imaging device such as a CCD (Charge Coupled Device) type image sensor or a CMOS (Complementary Metal Oxide Semiconductor) type image sensor. The imaging unit 11 outputs video data of the subject obtained by imaging to the MCU 19. The GPIO 12 is, for example, a parallel interface, and inputs and outputs signals between the recording switch SW1, the snapshot switch SW2, the attribute information addition switch SW3, the LEDs 26a to 26c, the vibrator 27, and the MCU 19. In addition, for example, various sensors (for example, acceleration sensors) are connected to the GPIO 12.

  The RAM 13 is a work memory used in the operation of the MCU 19, for example. The ROM 14 is, for example, a memory that stores in advance a program and data for controlling the MCU 19. The storage unit 15 is configured by a storage medium such as an SD memory, for example, and stores video data obtained by imaging by the imaging unit 11. When an SD memory is used as the storage unit 15, it can be attached to and detached from the housing body of the wearable camera 10.

  The EEPROM 16 stores, for example, identification information for identifying the wearable camera 10 (for example, a serial number as a camera ID) and other setting information. The other setting information includes, for example, login information (for example, car ID and officer ID) obtained by setting registration at the in-station PC 71 and logging into the in-vehicle recorder 62. The RTC 17 counts the current time information and outputs it to the MCU 19. The GPS 18 receives current position information and time information of the wearable camera 10 from a GPS transmitter (not shown), and outputs them to the MCU 19. This time information is used for correcting the system time of the wearable camera 10.

  The MCU 19 has a function as a control unit. For example, control processing for overall control of operations of each part of the wearable camera 10, data input / output processing with each part of the wearable camera 10, and data calculation It performs (calculation) processing and data storage processing, and operates according to the program and data stored in the ROM 14. During operation, the MCU 19 uses, for example, the RAM 13, obtains current time information from the RTC 17, and obtains current position information from the GPS 18.

  The communication unit 21 defines, for example, a connection between the communication unit 21 and the MCU 19 in the physical layer that is the first layer of an OSI (Open Systems Interconnection) reference model. Wireless communication (for example, Wi-fi (registered trademark)) is performed. The communication unit 21 may perform wireless communication such as near field communication (NFC) and Bluetooth (registered trademark). The USB 22 is a serial bus, and enables, for example, the wearable camera 10 to be connected to the in-vehicle system 60 or the in-station PC 71 in the police station 5.

  The contact terminal 23 is a terminal for electrically connecting to a cradle (not shown) or an external adapter (not shown), and is connected to the MCU 19 via the USB 22 and connected to the power supply unit 24. Via the contact terminal 23, the wearable camera 10 can be charged and data including video data can be communicated. The contact terminal 23 is provided with, for example, “charging terminal V +”, “CON.DET terminal”, “data terminals D−, D +” and “ground terminal” (all not shown). CON. The DET terminal is a terminal for detecting a voltage and a voltage change. The data terminals D− and D + are terminals for transferring video data captured by the wearable camera 10 to an external PC or the like via, for example, a USB connector terminal. By connecting the contact terminal 23 and a connector of a cradle (not shown) or an external adapter (not shown), data communication is possible between the wearable camera 10 and an external device.

  The power supply unit 24 supplies the battery 25 with power supplied from a cradle or an external adapter via the contact terminal 23 to charge the battery 25, for example. The battery 25 is constituted by a rechargeable secondary battery, for example, and supplies power to each part of the wearable camera 10.

  The recording switch SW1 is, for example, a push button switch for inputting an operation instruction to start / stop recording (moving image capturing) by a user's pressing operation. The snapshot switch SW2 is, for example, a push button switch that inputs an operation instruction for capturing a still image by a user's pressing operation. The attribute information addition switch SW3 is, for example, a push button switch for inputting an operation instruction for adding attribute information to video data by a user's pressing operation. The recording switch SW1, the snapshot switch SW2, and the attribute information addition switch SW3 are configured so that they can be easily operated even in an emergency. Each of the switches SW1 to SW3 is not limited to the above form, and may be another form of operation input device that allows the user to input an operation instruction.

  LED26a is a display part which shows the power-on state (on-off state) of the wearable camera 10, and the state of the battery 25, for example. LED26b is a display part which shows the state (recording state) of the imaging operation of the wearable camera 10, for example. LED26c is a display part which shows the state of the communication mode of the wearable camera 10, for example.

  The MCU 19 detects the input of each of the recording switch SW1, the snapshot switch SW2, and the attribute information addition switch SW3, and performs processing for the switch input that has been operated. When the MCU 19 detects an operation input of the recording switch SW1, the MCU 19 controls the start or stop of the imaging operation in the imaging unit 11, and stores the video data obtained from the imaging unit 11 in the storage unit 15 as video data of a moving image. To do. When the MCU 19 detects an operation input of the snapshot switch SW2, the MCU 19 stores the video data from the imaging unit 11 when the snapshot switch SW2 is operated in the storage unit 15 as video data of a still image.

  When the MCU 19 detects an operation input of the attribute information addition switch SW3, the MCU 19 assigns preset attribute information to the video data and stores it in the storage unit 15 in association with the video data. At this time, for example, the MCU 19 detects the state of an attribute selection switch (not shown) for selecting an attribute to be associated with the video data, and assigns attribute information according to the setting. Further, the MCU 19 operates the communication unit 21 in a preset communication mode. When the recording operation is started, the MCU 19 drives the LEDs 26a to 26c and the vibrator 27 according to a preset notification mode, and performs notification indicating the state of the recording operation to the outside by LED display and / or vibrator vibration.

  As shown in FIG. 4, the wearable camera 10 is a clothing worn by the police officer 7 so as to capture an image of a field of view from a position close to the viewpoint of the police officer 7, such as the chest of the police officer 7 who is a user. Or worn on the body. With the wearable camera 10 attached, the police officer 7 operates the recording switch SW1 to image a surrounding subject.

  As shown in FIG. 5, the wearable camera 10 is provided with, for example, an imaging lens 11a of the imaging unit 11, a recording switch SW1, and a snapshot switch SW2 on the front surface of a substantially rectangular parallelepiped casing 10A. For example, when the recording switch SW1 is pressed an odd number of times, recording (moving image capturing) starts, and when the recording switch SW1 is pressed an even number of times, the recording ends. For example, each time the snapshot switch SW2 is pressed, a still image is captured when the snapshot switch SW2 is pressed.

  An attribute information addition switch SW3 is provided on the left side as viewed from the front of the housing 10A of the wearable camera 10. When the police officer 7 depresses the attribute information addition switch SW3, the attribute information corresponding to the setting state is assigned to the video data currently recorded or the video data recorded immediately before.

  LED26a-26c is arrange | positioned at the upper surface seeing from the front of the housing | casing 10A of the wearable camera 10, as shown in FIG. Thereby, the police officer 7 can easily visually recognize the LEDs 26a to 26c with the wearable camera 10 attached. Note that the LEDs 26a to 26c may not be seen by anyone other than the seven police officers. Although not shown, a contact terminal 23 is provided on the lower surface of the wearable camera 10 when viewed from the front surface of the housing 10A.

  Next, transfer of video data in the wearable camera system 100 of the present embodiment will be described.

  In the present embodiment, video data captured by the wearable camera 10 is transferred to and saved in the in-vehicle recorder 62 of the in-vehicle system 60. Then, the video data captured by the wearable camera 10 and the video data captured by the in-vehicle camera 61 are collectively transferred from the in-vehicle recorder 62 to the server SV of the back-end system 100B, stored, and stored in the server SV. . The video data is transferred and recorded as video recording data including video data and meta information in association with meta information including attribute information.

  At this time, the wearable camera 10 communicates by connecting to the communication unit 102 of the in-vehicle recorder 62 through the communication unit 21, and recording data including video data stored in the storage unit 15 of the wearable camera 10 is transmitted to the in-vehicle recorder 62. Send. The in-vehicle recorder 62 receives the recording data by the communication unit 102 and stores the transferred recording data in the storage 111.

  In the wearable camera system 100, when the video data recorded by the police officer 7 on the site is stored in the server SV, it is necessary to transfer the data from the wearable camera 10 and the in-vehicle system 60 to the back-end system 100B in a normal method. Since the wearable camera 10 is carried around and used in various places, it may be damaged or lost. In addition, since video data has a large data size, a long time is required for data transfer. For example, depending on the video data, the data transfer time may take 1 hour. The wearable camera 10 often has a low performance and function of the device itself, and has a lower communication speed than the in-vehicle recorder 62 of the in-vehicle system 60. Therefore, more time is required for data transfer. In addition, wearable camera 10 may be restricted by functions at the time of data transfer, such as being unable to record simultaneously with data transfer.

  On the other hand, the in-vehicle recorder 62 is supplied with power from the vehicle (the police car 6) as the in-vehicle system 60, and includes a high-performance CPU 101 and a communication unit 102. By transferring the video data collectively from the in-vehicle recorder 62 to the server SV of the back-end system 100B, the video data can be transferred at high speed using the communication unit 102 having a high communication speed. In addition, the data transfer schedule can be flexibly set by transferring the video data from the in-vehicle recorder 62 at a time. For example, during patrol by the police car 6, during movement by the police car 6, returning to the police station 5, arriving at the police station 5 and parking the police car 6, video data can be automatically transferred at any time during free time. . In addition, when communication lines are busy, video data can be transferred by automatic processing when it is available. As a result, the time required to transfer the video data can be shortened. Also, video data can be transferred using the free time, and the time for data transfer can be used effectively.

  In addition, after the video data is transferred from the wearable camera 10 to the in-vehicle recorder 62, the transferred video data can be deleted. In this case, the wearable camera 10 confirms the completion of the transfer of the video data, and deletes the transferred video data in the storage unit 15. Thereby, in the wearable camera 10, the free space of the storage unit 15 can be increased, and a lot of new images can be captured. Due to the downsizing of the wearable camera 10, even if the capacity of the storage unit 15 is small, a lot of video data can be stored, and the total recording time can be extended.

  FIG. 6 is a diagram illustrating an example of a data structure of recorded data, and FIG. 7 is a diagram illustrating an example of a data structure of a recorded video list. In the wearable camera 10 of the present embodiment, when recording, as shown in FIG. 6, together with the captured video data, meta information including attribute information related to the video data is generated, and the video data is associated with the two data. The data is stored in the storage unit 15 as data. That is, the video recording data recorded in the storage unit 15 includes video data and meta information. When recording with the in-vehicle camera 61, recording data including video data and meta information is recorded in the storage 111 of the in-vehicle recorder 62. When video data is transferred from the wearable camera 10 to the server SV, recording data including the video data and meta information is transferred to the server SV via the in-vehicle recorder 62 and stored.

  Meta information related to video data is recorded in the form of a recorded video list as shown in FIG. The meta information of the recorded video list includes event ID, time information, camera ID, user ID, attribute information, priority flag, and the like. The event ID is identification information for identifying a recording event. In the present embodiment, one recording operation from the start of recording to the end of recording is defined as one event, and an event ID is assigned to each event of the recording operation (hereinafter also referred to as a recording event). As the event ID, a video data ID based on a file name of the video data may be used. The time information is time information of each recording event, and for example, a recording start time (video start time) is given. As the time information, not only the recording start time but also the recording start time and the recording end time, the recording start time and the recording duration time, and the like may be used. In the example of FIG. 7, the recorded video list is recorded in order from the top of the recording start time from the top.

  The camera ID is identification information for identifying each wearable camera 10 or the in-vehicle camera 61. For example, the wearable camera 10 is BWC0001, the in-vehicle camera 61 is CAR0025, and the like. The user ID is identification information of the police officer 7 who is a user who uses the wearable camera 10. When the wearable camera 10 is used, a camera ID and a user ID are set so that it is possible to determine which individual camera used to record the recorded video data.

  The attribute information is classification information for identifying the type of video data. The attribute information is provided according to the operation of the attribute information addition switch SW3 of the wearable camera 10 by the user, the operation of the switch 109 of the in-vehicle recorder 62, or the operation of the in-vehicle PC 63 based on the setting contents of the attribute information set in advance. As the attribute information, for example, an attribute related to an incident that has occurred in the field, such as theft, drunk driving, or parking violation, is used.

  The priority flag is priority information for determining the transfer priority for each video data, for example, information indicating the presence or absence of the priority. The priority flag is given according to, for example, an operation of the attribute information addition switch SW3 by the user, an operation of the switch 109 of the in-vehicle recorder 62, or an operation of the in-vehicle PC 63. The priority information may be information indicating the priority in a plurality of stages. When recording with the wearable camera 10, there is video data that captures a scene where an event to be recorded does not occur, such as when recording using the automatic recording function, and not all video data is necessarily required. By giving a priority flag to video data, video data with a high priority can be transferred with priority. The priority flag can be automatically given to specific attribute information such as attribute information of a case type with high importance.

  Each of the above meta information is given by the processing of the MCU 19 of the wearable camera 10 or the processing of the CPU 101 of the in-vehicle recorder 62 at the start of recording or immediately after the end of recording, and is recorded in the storage unit 15 or the storage 111 in association with the video data. Is done. As shown in FIG. 7, when video data is transferred from the wearable camera 10 to the in-vehicle recorder 62, the video data recorded by the wearable camera 10 and the video recorded by the in-vehicle recorder 62 are recorded in the recorded video list of the in-vehicle recorder 62. Recorded together with data.

  Next, the video data transfer operation in the wearable camera system 100 of the present embodiment will be described in more detail.

  FIG. 8 is a flowchart illustrating an example of a procedure related to a transfer operation of recorded data from the wearable camera 10 to the in-vehicle recorder 62 in the present embodiment.

  Transfer (uploading) of recorded data including video data from the wearable camera 10 to the in-vehicle recorder 62 includes operation instructions from the user, time conditions such as a predetermined time and elapsed time, free space in the storage unit 15 and the amount of accumulated data. It is executed according to preset execution conditions such as capacity conditions.

  The MCU 19 of the wearable camera 10 determines whether the communication unit 21 is wirelessly connected to the communication unit 102 of the in-vehicle recorder 62 (step S11). When not wirelessly connected to the in-vehicle recorder 62, the communication unit 21 of the wearable camera 10 performs a wireless connection process with the communication unit 102 of the in-vehicle recorder 62 to enable wireless communication with the in-vehicle recorder 62 (step S12). . And it returns to the process of step S11.

  When wirelessly connected to the in-vehicle recorder 62, the MCU 19 of the wearable camera 10 determines whether uploading to the in-vehicle recorder 62 is valid (step S13). Here, the MCU 19 determines whether or not the setting for transferring the recording data to the in-vehicle recorder 62 (upload valid) is made based on the setting made in advance for the wearable camera 10. If uploading to the in-vehicle recorder 62 is not valid, the process returns to step S11.

  When uploading to the in-vehicle recorder 62 is valid, the MCU 19 of the wearable camera 10 sets _totalN = (number of recorded data in the wearable camera) and n = 1 as initial parameter settings at the time of recording data transfer (step S14). ). Here, _totalN corresponds to the number of recording data to be transferred, and n corresponds to a counter indicating the order of individual recording data to be transferred. Then, the MCU 19 determines whether or not _totalN is greater than 0 (step S15). Since _totalN is 1 or more at first, the MCU 19 proceeds to the subsequent processing.

  Next, the MCU 19 of the wearable camera 10 sets _cntRety = 5 as a parameter setting for retry (step S16). Here, _cntRety corresponds to the number of retries, and in this example, five retries are set.

  Subsequently, the MCU 19 of the wearable camera 10 reads the recording data to be transferred from the storage unit 15, transmits the recording data to the in-vehicle recorder 62 by the communication unit 21, and uploads it as video (n) (step S17).

  Then, the MCU 19 of the wearable camera 10 compares the hash values of both the data in the wearable camera 10 as the transfer source and the data in the in-vehicle recorder 62 as the transfer destination for the uploaded video (n) recording data (step S18). ). At this time, the MCU 19 requests and acquires the hash value of video (n) from the in-vehicle recorder 62. Subsequently, the MCU 19 determines whether or not the hash values of video (n) match (step S19). By comparing the hash values, it can be determined whether or not the transfer of the recorded data has been executed normally. If the hash values of video (n) match, the MCU 19 determines that the transfer of the recorded data has been executed normally, and deletes the recorded data of video (n) stored in the storage unit 15 in the wearable camera 10. (Step S20).

  Thereafter, the MCU 19 of the wearable camera 10 sets n = n + 1 (step S21) and _totalN = _totalN-1 (step S22), and returns to the process of step S15. In step S15, the MCU 19 determines whether or not _totalN is greater than 0, that is, whether or not recording data to be transferred remains. If _totalN is greater than 0 in step S15, the MCU 19 executes uploading to the in-vehicle recorder 62 in steps S16 to S22 for the next transfer target recording data in the same manner as in the previous time.

  If the hash values of video (n) do not match in step S19, the MCU 19 of the wearable camera 10 sets _cntRety = _cntRety-1 (step S23) and determines whether _cntRety is greater than 0 (step S24). Since _totalN is 5 at first, the MCU 19 returns to the process of step S17 and executes a retry of the video (n) recording data transfer process. When retrying the transfer process five times and _cntRety becomes 0 in step S24, the MCU 19 proceeds to the process of step S21, and n = n + 1 (step S21), _totalN = _totalN-1 (step S22), The process returns to step S15.

  If _totalN becomes 0 in step S15, that is, if there is no recording data to be transferred, the process returns to step S11.

  FIG. 9 is a flowchart illustrating an example of a procedure related to an operation of transferring recorded data from the in-vehicle recorder 62 to the back-end server SV in the present embodiment.

  Transfer (upload) of recorded data including video data from the in-vehicle recorder 62 to the server SV of the back-end system 100B is an operation state (such as an idle state) of the in-vehicle recorder 62 and a communication line state with the back-end system 100B. (Congestion status, etc.), time conditions such as a predetermined time and elapsed time, and the like are executed at a predetermined timing according to preset execution conditions.

  The CPU 101 of the in-vehicle recorder 62 determines whether the communication unit 102 is wirelessly connected to the server SV of the backend system 100B (step S31). When not wirelessly connected to the server SV, the communication unit 102 of the in-vehicle recorder 62 performs a wireless connection process with the server SV to enable wireless communication with the server SV (step S32). Then, the process returns to step S31.

  When wirelessly connected to the server SV, the CPU 101 of the in-vehicle recorder 62 determines whether uploading to the server SV is valid (step S33). Here, the CPU 101 determines whether or not the setting for transferring the recording data to the server SV (upload valid) is made based on the setting made in advance on the in-vehicle recorder 62. If uploading to the server SV is not valid, the process returns to step S31.

  When uploading to the server SV is valid, the CPU 101 of the in-vehicle recorder 62 sets _totalN = _totalM = (number of recording data in the in-vehicle recorder), n = 1, and m = 1 as initial parameter settings when recording data is transferred. Set (step S34). Here, _totalN is the number of recording data to be transferred, _totalM is the number of recording data to be transferred in the initial state, n is a counter indicating the order of individual recording data to be transferred, and m is recording data referred to as a priority transfer target. It corresponds to a counter indicating the number of. Then, the CPU 101 determines whether _totalN is greater than 0 (step S35). Since _totalN is 1 or more at first, the CPU 101 proceeds to the subsequent processing.

  Next, the CPU 101 of the in-vehicle recorder 62 sets _cntRety = 5 as a parameter setting for retry (step S36). Here, _cntRety corresponds to the number of retries, and in this example, five retries are set.

  Subsequently, the CPU 101 of the in-vehicle recorder 62 reads out the recording data to be transferred from the storage 111, refers to the priority flag of the meta information of the recording data, and determines the presence or absence of the priority flag (step S37). When there is a priority flag, the CPU 101 transmits the recording data to the server SV through the communication unit 102 and uploads it as video (n) (step S38).

  Then, the CPU 101 of the in-vehicle recorder 62 compares the hash values of both the data in the transfer-source in-vehicle recorder 62 and the data in the transfer-destination server SV for the uploaded video (n) recording data (step S39). . At this time, the CPU 101 requests and acquires the hash value of video (n) from the server SV. Subsequently, the CPU 101 determines whether or not the hash values of video (n) match (step S40). By comparing the hash values, it can be determined whether or not the transfer of the recorded data has been executed normally. If the hash values of video (n) match, the CPU 101 determines that the transfer of the recorded data has been executed normally, and deletes the recorded data of video (n) stored in the storage 111 in the in-vehicle recorder 62. (Step S41).

  Thereafter, the CPU 101 of the in-vehicle recorder 62 sets n = n + 1, m = m + 1 (step S42), and _totalN = _totalN-1 (step S43), and returns to the process of step S35. In step S <b> 35, the CPU 101 determines whether _totalN is greater than 0, that is, whether the recording data to be transferred remains. If _totalN is greater than 0 in step S35, the CPU 101 executes uploading to the server SV in steps S36 to S43 for the next transfer target recording data as in the previous time.

  In step S40, when the hash values of video (n) do not match, the CPU 101 of the in-vehicle recorder 62 sets _cntRety = _cntRety-1 (step S44) and determines whether _cntRety is greater than 0 (step S45). Since _totalN is 5 at first, the CPU 101 returns to the process of step S38 and executes a retry of the video (n) recording data transfer process. When the transfer process is retried five times and _cntRety becomes 0 in step S45, the CPU 101 proceeds to the process of step S42, and n = n + 1, m = m + 1 (step S42), _totalN = _totalN-1 (step As S43), the process returns to step S35.

  In step S37, when there is no priority flag, CPU101 of the vehicle-mounted recorder 62 determines whether m is larger than _totalM (step S46). Here, when m is equal to or less than _totalM, that is, when the number of recording data being referred to is equal to or less than the number of recording data to be transferred in the initial state and there is still recording data for which the priority flag has not been determined, the CPU 101 , M = m + 1 (step S47), and the process returns to step S35.

  In step S46, when m is larger than _totalM, that is, when the priority flag is determined with reference to all the recording data to be transferred, the CPU 101 of the in-vehicle recorder 62 refers to the time information of the meta information of the recording data. Then, unsent recording data is extracted in order from the oldest recording data with the earliest recording start time (step S48). Then, the CPU 101 proceeds to the process of step S38, and executes uploading to the server SV as the recorded data video (n) in steps S38 to S43, similarly to the recorded data with the priority flag.

  In step S35, if _totalN becomes 0, that is, if there is no recording data to be transferred, the process returns to step S31.

  Note that the transfer of the recording data according to the priority is not limited to the transfer from the in-vehicle recorder 62 to the server SV, but may be performed in the same way in the transfer from the wearable camera 10 to the in-vehicle recorder 62.

  As described above, in the present embodiment, the video data captured by the wearable camera 10 is transferred to the in-vehicle recorder 62 of the in-vehicle system 60 and is stored in the in-vehicle recorder 62 together with the video data captured by the in-vehicle camera 61. And the video data imaged with the wearable camera 10 or the vehicle-mounted camera 61 is collectively transferred from the vehicle-mounted recorder 62 to the server SV of the back-end system 100B, and the video data is stored in the server SV. Thereby, the video data can be transferred to the server SV at high speed by the in-vehicle recorder 62, and the transfer time of the video data having a large capacity can be shortened.

  Also, the transfer of the video data from the in-vehicle recorder 62 to the server SV can be executed at any time by automatic processing during idle time when the user does not operate the system, such as when the police car 5 is moving or when the police car 5 is parked. At this time, when a large amount of time is required for data transfer processing, such as when transferring a large amount of video data, the in-vehicle recorder 62 intermittently transfers the video data at a transferable time to complete the transfer processing. Can do.

  Further, in the wearable camera 10, by deleting the video data that has been transferred to the in-vehicle recorder 62, the free space in the storage unit can be increased and the recordable time can be extended.

  Further, in the in-vehicle recorder 62 or the wearable camera 10, by transferring the video data according to the priority set in the video data, the video data having a high priority can be preferentially transferred and quickly stored in the server SV. .

  As described above, the wearable camera system 100 of this embodiment includes the wearable camera 10 that can be worn by the police officer 7 and the in-vehicle recorder 62 that is mounted on the police car 6 on which the police officer 7 gets. The wearable camera 10 communicates the imaging unit 11, the storage unit 15 that stores the imaging data captured by the imaging unit 11, the communication unit 21 that communicates with the in-vehicle recorder 62, and the video data stored in the storage unit 15. MCU 19 that is transferred to the in-vehicle recorder 62 by the unit 21. The in-vehicle recorder 62 includes a communication unit 102 that communicates with the wearable camera 10 and the transfer destination server SV, a storage 111 that stores video data including video data transmitted from the wearable camera 10, and a storage 111 that stores the video data. A CPU 101 that transfers video data to the server SV by the communication unit 102 at a predetermined timing.

  With the above configuration, the video data captured by the wearable camera 10 can be transferred to the in-vehicle recorder 62, and the video data can be collectively transferred from the in-vehicle recorder 62 to the server SV at a high speed. Therefore, it is possible to shorten the time required for transferring the video data and improve convenience.

  Further, in the wearable camera system 100 according to the present embodiment, the communication unit 102 of the in-vehicle recorder 62 can perform higher-speed communication than the communication unit 21 of the wearable camera 10. Thereby, the video data can be transferred from the in-vehicle recorder 62 to the server SV at a high speed, and the time required to transfer the video data can be shortened.

  In the wearable camera system 100 of the present embodiment, the MCU 19 of the wearable camera 10 transfers video data to the in-vehicle recorder 62 during a period in which the in-vehicle recorder 62 does not transfer data to the server SV. Thereby, the transfer efficiency of video data can be improved, and the time required for transfer can be shortened.

  In the wearable camera system 100 of the present embodiment, the MCU 19 of the wearable camera 10 deletes the transferred video data transferred to the in-vehicle recorder 62 from the storage unit 15. Thereby, the free space of the storage unit 15 can be increased, and the recording time can be extended.

  In the wearable camera system 100 of the present embodiment, the MCU 19 of the wearable camera 10 starts transferring video data when the communication unit 21 is wirelessly connected to the communication unit 102 of the in-vehicle recorder 62. Thereby, when data can be transferred from the wearable camera 10 to the in-vehicle recorder 62, the video data can be transferred by automatic processing. Therefore, it is possible to shorten the time required for transferring the video data and improve convenience.

  In the wearable camera system 100 according to the present embodiment, at least one of the CPU 101 of the in-vehicle recorder 62 and the MCU 19 of the wearable camera 10 has high priority according to the priority information set in the video data to be transferred. Transfer data preferentially. Accordingly, video data having a high priority can be transferred at an early time and stored in the server SV.

  The video data transfer method of the present embodiment is a video data transfer method in a wearable camera system 100 that includes a wearable camera 10 that can be worn by the police officer 7 and an in-vehicle recorder 62 that is mounted on the police car 6 on which the police officer 7 rides. The imaging unit 11 of the wearable camera 10 captures an image, stores the captured image data in the storage unit 15 of the wearable camera 10, and stores the image data stored in the storage unit 15 in the communication unit of the wearable camera 10. 21, the video data including the video data sent from the wearable camera 10 is stored in the storage 111 of the in-vehicle recorder 62, and the video data stored in the storage 111 is mounted on the vehicle at a predetermined timing. Transfer to the destination server SV by the communication unit 102 of the recorder 62. To. Thereby, the time for transferring the video data can be shortened, and the convenience can be improved.

  While various embodiments have been described above with reference to the drawings, it goes without saying that the present invention is not limited to such examples. It will be apparent to those skilled in the art that various changes and modifications can be made within the scope of the claims, and these are naturally within the technical scope of the present invention. Understood. In addition, the constituent elements in the above-described embodiment may be arbitrarily combined without departing from the spirit of the invention.

  INDUSTRIAL APPLICABILITY The present invention is useful as a wearable camera system or the like that can shorten the time for transferring video data and improve convenience.

DESCRIPTION OF SYMBOLS 100 Wearable camera system 100A Front-end system 100B Back-end system 5 Police station 6 Police car 7 Police officer 10 Wearable camera 11 Imaging part 12 GPIO
13 RAM
14 ROM
15 Storage unit 16 EEPROM
17 RTC
18 GPS
19 MCU
21 Communication unit 22 USB
23 Contact terminal 24 Power supply 25 Battery 26a, 26b, 26c LED
27 Vibrator 60 In-vehicle system 61 In-vehicle camera 62 In-vehicle recorder 63 In-vehicle PC
65 In-vehicle camera system 70 Management software 71 Office PC
101 CPU
102 Communication unit 104 Flash ROM
105 RAM
106 Microcomputer 107 GPS
108 GPIO
109 Switch 110 LED
111 Storage 201 CPU
202 I / O control unit 203 Communication unit 204 Memory 205 Input unit 206 Display unit 207 Speaker SV server

Claims (5)

A wearable camera system comprising: a wearable camera that can be worn by a user; and an in-vehicle recorder mounted on a vehicle on which the user rides,
The wearable camera is
Capture the first video, store the captured first video, transfer the stored first video to the in-vehicle recorder,
The in-vehicle recorder is
Attribute information indicating the contents of each of the first video and the second video sent from the wearable camera and set by the state of the attribute information addition switch Save it in correspondence,
Transferring the stored first and second videos to a server according to the priority indicated by the attribute information;
Wearable camera system. The wearable camera system according to claim 1,
The wearable camera transfers the first video to the in-vehicle recorder during a period when the in-vehicle recorder does not transfer data to the server.
Wearable camera system. The wearable camera system according to claim 1 or 2,
The wearable camera deletes the transferred first video transferred to the in-vehicle recorder.
Wearable camera system. The wearable camera system according to any one of claims 1 to 3,
The wearable camera gives the attribute information to the first video, and transfers the first video and the attribute information to the in-vehicle recorder.
Wearable camera system. A video data transfer method using a wearable camera that can be worn by a user and an in-vehicle recorder mounted on a vehicle on which the user rides,
The wearable camera is
Capture the first video, store the captured first video, transfer the stored first video to the in-vehicle recorder,
The in-vehicle recorder is
Attribute information indicating the contents of each of the first video and the second video sent from the wearable camera and set by the state of the attribute information addition switch Save it in correspondence,
Transferring the stored first and second videos to a server according to the priority indicated by the attribute information;
Video data transfer method.