WO2016132678A1

WO2016132678A1 - Wearable camera system and method for synchronously reproducing video data

Info

Publication number: WO2016132678A1
Application number: PCT/JP2016/000333
Authority: WO
Inventors: 稔萩尾; 康志横光; 和彦山口
Original assignee: パナソニックＩｐマネジメント株式会社
Priority date: 2015-02-16
Filing date: 2016-01-25
Publication date: 2016-08-25
Also published as: JP6115873B2; JP2016152443A

Abstract

When a plurality of pieces of video data obtained by image capture of the same event are reproduced, the reproduction times of the respective pieces of video data are synchronized, thereby allowing the situation of the scene to be easily ascertained. A server comprises: a communication unit that receives first video data obtained by image capture using a first wearable camera and second video data obtained by image capture using an external device; a storage unit that stores the first and second video data, which are received from the communication unit, in such a manner that the first and second video data are associated with each other; and a reproduction unit that reproduces the first and second video data stored in the storage unit. The first video data has first recording time information of the image capture using the first wearable camera, while the second video data has second recording time information of the image capture using the external device. The reproduction unit uses the first and second recording time information to synchronize and reproduce the first and second video data.

Description

Wearable camera system and video data synchronous reproduction method

The present disclosure relates to a wearable camera system including a wearable camera that can be worn on, for example, a human body, clothes, or a hat, and a video data synchronous reproduction method for reproducing video data captured by the wearable camera.

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

Here, as a prior art using a wearable camera, for example, there is a wearable surveillance camera system described in Patent Document 1. The wearable surveillance camera system shown in Patent Document 1 stores a video signal and an audio signal from a CCD camera means and a microphone means attached to the body, and a date / time information signal from a built-in clock means in a pouch means attached to the body. Encoding is performed by the encoding back-end server means, and the date / time information converted into character information is superimposed on the captured image and recorded.

JP 2006-148842 A

The present disclosure is a wearable camera system including at least a first wearable camera that can be worn by a user and a back-end server, and the back-end server includes first video data captured by the first wearable camera, A communication unit that receives the second video data captured by the external device, a storage unit that stores the first video data and the second video data received by the communication unit in association with each other, and stores the storage unit in the storage unit A playback unit for playing back the first video data and the second video data, wherein the first video data has first recording time information imaged by the first wearable camera, and The second video data has second recording time information captured by the external device, and the playback unit uses the first recording time information and the second recording time information to Synchronously reproducing video data and second video data of a wearable camera system.

In addition, the present disclosure is a video data synchronized playback method in a wearable camera system including at least a first wearable camera that can be worn by a user and a back-end server, the video being captured by the first wearable camera, and an external device The first video data captured by the first wearable camera, the first video data captured by the first wearable camera and the second video data captured by the external device are received, and the first recording captured by the first wearable camera is received. The first video data having the time information and the second video data having the second recording time information captured by the external device are stored in the storage unit in association with each other, and the first recording time information and the second video data Video data for reproducing the first video data and the second video data stored in the storage unit in synchronization using the recording time information. It is a synchronous playback method.

According to the present disclosure, when reproducing a plurality of video data obtained by imaging the same incident, it is possible to easily grasp the on-site situation by synchronizing the reproduction times of the respective video data.

FIG. 1 is an explanatory diagram regarding the outline of the wearable camera system of the present embodiment and the use of video data captured by the wearable camera. FIG. 2 is a block diagram showing an example of the internal configuration of the in-vehicle camera system and the in-vehicle PC of the present embodiment. FIG. 3 is a block diagram illustrating an example of an internal configuration of the wearable camera according to the present embodiment. FIG. 4 is a block diagram showing an example of the internal configuration of the back-end server of this embodiment. FIG. 5 is a diagram showing a state in which the user wears the wearable camera of the present embodiment. FIG. 6 is a front view showing an example of the appearance of the wearable camera of the present embodiment. FIG. 7 is a diagram illustrating an example of a data structure of recorded data captured by the in-vehicle camera. FIG. 8 is a diagram illustrating an example of a data structure of recorded data captured by the wearable camera. FIG. 9 is a diagram illustrating an example of a data structure of frame parameter information in video data. FIG. 10 is a diagram illustrating an example of the data structure of the frame parameter information in the video data of the recording data captured by the in-vehicle camera. FIG. 11 is a diagram illustrating an example of the data structure of the frame parameter information in the video data of the recording data captured by the wearable camera. FIG. 12 is a flowchart for explaining an example of an operation procedure in which the wearable camera of the present embodiment synchronizes time with the in-vehicle camera system. FIG. 13 is a flowchart for explaining an example of an operation procedure in which the back-end server of the present embodiment reproduces video data of recorded data captured by the wearable camera and the in-vehicle camera.

When a police officer wears a wearable camera and rushes to a designated site with a police car, for example, the police officer only operates the wearable camera to record and record the situation at the scene. In some cases, an in-vehicle camera mounted in a police car is operated to pick up an image of an angle different from that of the wearable camera. Each video data obtained by the wearable camera and the in-vehicle camera is transferred to the back-end server in the police station, and then played back so that the person in charge in the police station can compare each video data. Observe the situation.

Here, a plurality of pieces of video data obtained by imaging the same incident (for example, not only the case of each piece of video data taken by the above-described wearable camera and vehicle-mounted camera, but also the case of each piece of video data taken by a plurality of wearable cameras) If the playback times of multiple videos played back by the back-end server are not synchronized, the time-series context cannot be determined, making it difficult to grasp the situation at the site. There was a problem.

For example, if the target person is different in the same incident (that is, the subject of the wearable camera or the in-vehicle camera), and the playback times of multiple videos played back by the back-end server are not synchronized, It becomes difficult to grasp the status of the serial context. If the target person is the same even in the same case, if each person in the police station tracks the target person when each video data is played back, the chronological context can be confirmed. It takes time and effort. For this reason, if the reproduction times of the respective video data are not synchronized, there is an unsolved problem that it is difficult to grasp the situation at the site.

In the above-mentioned Patent Document 1, the date and time information when the video is captured is imposed on the video data. However, regarding the synchronization when the video data captured by a plurality of cameras is reproduced by the back-end server in the police station described above, No mention is made.

In order to solve the above-described problem, the present disclosure provides a wearable camera that allows a user to easily grasp the on-site situation by synchronizing the reproduction time of each video data when reproducing a plurality of video data obtained by imaging the same incident. It is an object of the present invention to provide a system and a video data synchronous reproduction method.

Hereinafter, an embodiment (hereinafter referred to as “the present embodiment”) that specifically discloses the wearable camera system and the video data synchronized playback method according to the present disclosure will be described in detail with reference to the drawings.

In this embodiment, in a wearable camera system including at least a wearable camera (BWC: Body Worn Camera) and a back-end server that can be worn by a user (for example, police officer 7; the same applies hereinafter), an image is displayed by the wearable camera. An image is captured and an image is captured by an external device (for example, an in-vehicle camera or another wearable camera). The video data captured by the wearable camera and the video data captured by the external device are received by the back-end server. The back-end server stores the first video data having the first recording time information captured by the wearable camera and the second video data having the second recording time information captured by the external device in association with each other. Store in the department. Further, the back-end server uses the first recording time information and the second recording time information to reproduce the first video data and the second video data stored in the storage unit in synchronization.

FIG. 1 is an explanatory diagram regarding the outline of the wearable camera system 100 of this embodiment and the use of video data captured by the wearable camera 10. The wearable camera 10 of this embodiment is an imaging device that a user (for example, police officer 7) can wear on a body, clothes, a hat, or the like. The wearable camera 10 is connected to an in-vehicle system 60 mounted on a car (for example, a police car on which a police officer gets on) or a back-end server (that is, a back-end server SV) in a police station to which the police officer 7 belongs. It has a communication function for performing communication (for example, wireless communication).

In the wearable camera system 100 shown in FIG. 1, the wearable camera 10 and the in-vehicle system 60 constitute a front-end system 100A, and the management software 70 on the network, the back-end server SV, and the in-station PC 71 that is a PC in the police station are back. The end system 100B is configured. The management software 70 is executed by, for example, the in-station PC 71 or the back-end server SV.

Hereinafter, the present embodiment will be described assuming that the wearable camera system 100 is used in the police station 5, for example. The police officer 7 operates the wearable camera 10 to image the situation on the scene or a specific subject (for example, a victim of the incident, a suspect, a visitor around the scene). The wearable camera 10 transfers video data obtained by imaging to, for example, a back-end system 100B in the police station 5 in accordance with a user operation. 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, and a portable terminal (for example, a smartphone, which is held in a police car that is held or used by the police officer) And a vehicle-mounted system 60 installed in the police car 6. 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 installed at a predetermined position of the police car 6 and captures images around the police car 6 (for example, the front of the police car or the back seat in the police car) at regular intervals or at predetermined timings. That is, 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 for imaging a back seat (for example, a seat on which a suspect is sitting) in the police car 6. And a camera (not shown). The video data captured 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.

Further, the in-vehicle camera 61 may have a microphone (not shown) that collects sound inside and outside the police car 6 as a front camera or a back seat camera. 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 portable PC, a smartphone, a mobile phone, a tablet terminal, or a PDA (Personal Digital Assistant) used outside the police car 6. But you can.

The in-vehicle PC 63 enables cooperation between the in-vehicle system 60 and the wearable camera 10 (specifically, communication 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 goes to the site. In the front-end system 100A, for example, an on-site camera 61 of the in-vehicle system 60 captures an image of the scene where the police car 6 arrives, and the police officer 7 gets off the police car 6 to obtain a closer and more detailed image of the scene on the wearable camera 10. Take an image.

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. Various data including video data captured by the wearable camera 10 may be directly transferred from the wearable camera 10 to the back-end system 100B, or may be transferred to the back-end system 100B via the in-vehicle system 60. Good.

Video data of a moving image or a still image captured by the in-vehicle camera 61 is stored in a storage such as a hard disk (HDD (Hard Disk Drive)), SSD (Solid State Drive) or the like provided in the in-vehicle recorder 62 of the in-vehicle system 60, for example. 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 the police station 5 is returned, wireless communication, wired communication, or manual (for example, storage medium) Carry around).

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 the 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 back-end server SV installed in the police station 5 or other places, management software 70 for communicating with the front-end system 100A, and a station PC 71. .

The back-end server SV includes a storage 308 configured using an HDD, SSD, or the like inside (see FIG. 4) or outside. In the back-end system 100B, the back-end server SV accumulates video data and other data transferred from the front-end system 100A in the storage 308, and constructs a database used in each department in the police station. The back-end server SV receives video data transferred from, for example, the wearable camera 10 or the in-vehicle system 60 (for example, the in-vehicle recorder 62) and stores it in the storage 308.

The video data stored in the back-end system 100B is used, for example, by a person in charge in the relevant department in the police station 5 for investigation and verification of the incident, and as required, a predetermined storage medium (for example, DVD: Digital Versatile Disk) ) Is copied and submitted as evidence in a predetermined scene (for example, trial). In the present embodiment, using the wearable camera 10 worn by the police officer 7, it is possible to acquire and store the evidence video on 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, officer ID (Office ID)), the identification information of the wearable camera 10 used by the police officer ( For example, camera ID (Camera ID), identification information of the police car 6 used by the police officer 7 (for example, car ID (Car ID)) is set and registered using the in-station PC 71. Thereby, it is stored in the back-end server SV. With respect to the recorded video data, it is possible to clearly distinguish when and when the police officer uses the camera.

For setting registration of the police officer 7 and the wearable camera 10, for example, the person in charge in the police station 5 or the police officer 7 to be dispatched operates the operation device (not shown) of the in-station PC 71, and the in-station PC 71 executes the management software 70 It is done by doing. In this setting registration, information other than the Office ID, Camera ID, and Car ID may be input via the operation 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 the dispatch of the police car 6 and the like, and an application for managing the 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 back-end server SV, for example.

FIG. 2 is a block diagram showing 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 shown in FIG. 2, the in-vehicle camera 61 and the in-vehicle recorder 62 constitute an in-vehicle camera system (ICV: In Car Video System) 65.

The in-vehicle camera 61 captures video at a predetermined frame rate, and generates frame parameter information (see FIG. 9) indicating frame information for each frame of video data obtained by the imaging. The vehicle-mounted camera 61 generates video data by adding frame parameter information for each frame to the video data (see FIG. 7). The frame parameter information will be described later with reference to FIG.

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, and a microcomputer (μCON, sometimes referred to as a microcontroller) 106. , GPS (Global Positioning System) 107, GPIO (General Purpose Input / Output) 108, switch 109, LED (Light Emitting Diode) 110, and storage 111.

The CPU 101 performs, for example, 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 (for example, the

wearable camera

10 or 10A or the in-vehicle PC 63) 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: Near Field Communication), 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.

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 back-end server SV, for example. The communication unit 102 is wirelessly connected to the

wearable cameras

10 and 10A, and receives various data including video data transmitted from the

wearable cameras

10 and 10A.

The flash ROM 104 is a memory that stores a program and data for controlling the CPU 101, for example, and holds various setting information. The RAM 105 is a work memory used in the operation of the CPU 101, for example, and is provided with either one or a plurality of RAMs.

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. Further, the in-vehicle camera 61 periodically accesses the in-vehicle recorder 62 and adjusts the time so that the system time of the in-vehicle camera 61 and the system time of the in-vehicle recorder 62 are synchronized (matched). Accordingly, the system time in the in-vehicle camera system 65 shown in FIG. 2 (in other words, the respective system times of the in-vehicle camera 61 and the in-vehicle recorder 62) is synchronized (that is, coincides) by correcting the system time in the in-vehicle recorder 62. And).

In addition, in order to make each system time of the vehicle-mounted camera 61 and the vehicle-mounted recorder 62 in the vehicle-mounted camera system 65 correspond, the system time of the vehicle-mounted recorder 62 is corrected using the output of the GPS 107 described above, and the vehicle-mounted camera 61 periodically The method for accessing the in-vehicle recorder 62 is not limited. For example, an in-vehicle recorder 62 may be provided with an NTP (Network Time Protocol) server, and the in-vehicle camera 61 may periodically access the in-vehicle recorder 62 as an NTP server. Furthermore, although details will be described later with reference to FIG. 12, in the present embodiment, the

wearable cameras

10 and 10A periodically access the in-vehicle recorder 62, so that the in-vehicle recorder 62 (that is, the in-vehicle camera system 65) and the wearable camera are wearable. The system time is synchronized with the

cameras

10 and 10A.

The GPIO 108 is, for example, a parallel interface, and inputs and outputs signals between an external device (not shown) connected via the GPIO 108 and the CPU 101. 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 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 adding button for giving attribute information or meta information to the video data imaged by the in-vehicle camera 61 including.

The LED 110 is provided as a display device that indicates an operation state of the in-vehicle recorder 62. For example, the LED 110 turns on, turns off, blinks, etc. the power-on state (on / off state) of the in-vehicle recorder 62, the recording state, the connection state of the in-vehicle recorder 62 to the LAN, and the use state of the LAN connected to the in-vehicle recorder 62. Is displayed.

The storage 111 is configured by, for example, an SSD or HDD, and stores and accumulates video data captured and recorded by the in-vehicle camera 61. In addition, when video data is transferred from the

wearable cameras

10 and 10A, the storage 111 stores and accumulates video data captured and recorded by the

wearable cameras

10 and 10A. 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 back-end server SV of the back-end system 100B and the in-station PC 71.

The CPU 201 authenticates whether or not the police officer 7 can log in to the in-vehicle system 60 by, for example, 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 an operation for inputting, for example, an officer ID and a password. Various kinds 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 advance in the memory 204 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 by 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 login information related to the police officer 7 who is permitted to log in to the in-vehicle system 60, for example.

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 with 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. In addition, the display unit 206 displays the video data under the instruction of the CPU 201 when video data captured (recorded) by the

wearable cameras

10 and 10A is input in response to an input operation of the police officer 7, for example. Display included video on the screen.

For example, in response to an input operation of the police officer 7, the speaker 207 receives video data including sound picked up (recorded) by the

wearable cameras

10 and 10 </ b> A. Output included 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 showing an example of the internal configuration of the

wearable cameras

10 and 10A. The wearable camera 10 shown in FIG. 3 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 outputs, for example, a solid-state imaging device such as an imaging lens 11a (see FIG. 6), a CCD (Charge Coupled Device) type image sensor or a CMOS (Complementary Metal Oxide Semiconductor) type image sensor, and the like. A signal processing unit for converting into video data having a frame of a predetermined format that can be identified by a person. The imaging unit 11 captures a video at a predetermined frame rate, and outputs video data of the subject obtained by the 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 a memory that stores in advance a program and data for controlling the MCU 19, for example. 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 cameras

10 and 10A.

The EEPROM 16 stores, for example, identification information (for example, a serial number as a camera ID) for identifying the

wearable cameras

10 and 10A, 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 cameras

10 and 10 </ b> A 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 cameras

10 and 10A.

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, 10A, data input / output processing between each unit of the

wearable camera

10, 10A, for example. Data calculation (calculation) processing and data storage processing are performed, and operations are performed in accordance with programs 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 the connection between the communication unit 21 and the MCU 19 in the physical layer, which is the first layer of the OSI (Open Systems Interconnection) reference model, for example, and, for example, a wireless LAN (W-LAN) 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, for example, and charges the battery 25. 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 a push button switch for inputting an operation instruction for starting / stopping recording (moving image capturing) by a user's pressing operation, for example. 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 a push button switch for inputting an operation instruction for adding attribute information to the video data, for example, by a pressing operation of the user. The recording switch SW1, the snapshot switch SW2, and the attribute information addition switch SW3 are arranged at positions that can be easily operated by the police officer 7 even in an emergency, for example (see, for example, FIG. 6). 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.

The LED 26 a is a display unit that indicates, for example, the power-on state (on / off state) of the wearable camera 10 and the state of the battery 25. 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 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 in accordance with a preset notification mode, and notifies the outside of the state of the recording operation by LED display and / or vibrator vibration.

The MCU 19 generates frame parameter information (see FIG. 9) indicating various types of frame information in the video data by using, for example, respective outputs of the RTC 17 and the GPS 18 for each frame of the video data output from the imaging unit 11. Alternatively, the MCU 19 includes a system time counting unit 19A that holds the system time of the

wearable cameras

10 and 10A, and may correct the system time using the output of the RTC 17, or may be synchronized with the system time of the in-vehicle camera system 65. Therefore, the system time may be corrected by periodically accessing the in-vehicle camera system 65 (for example, the in-vehicle recorder 62 as an NTP server) without using the output of the RTC 17.

The MCU 19 uses the output of the system time counting unit 19A (that is, the system time of the

wearable cameras

10 and 10A) to generate the frame parameter information, and further adds the frame parameter information to the video data stream to generate video data. (See FIG. 8)). The frame parameter information will be described later with reference to FIG.

FIG. 4 is a block diagram showing an example of the internal configuration of the back-end server SV of the present embodiment. The back-end server SV illustrated in FIG. 4 includes a CPU 301, a memory 302, an I / O control unit 303, a communication unit 304, an input unit 305, an output unit 306, a storage control unit 307, and a storage 308.

The CPU 301 performs, for example, control processing for overall control of operations of each unit of the back-end server SV, data input / output processing with other units, data calculation (calculation) processing, and data storage processing. .

The CPU 301 as an example of a playback unit includes two recorded data RCD1 and RCD2 (for example, recorded data RCD1 captured and recorded by the in-vehicle camera system 65 and recorded data recorded by the wearable camera 10 and stored in the storage 308. RCD2) to the output unit 306 is instructed to the I / O control unit 303. As a result, the recording data RCD1 captured and recorded by the in-vehicle camera system 65 and the recording data RCD2 captured and recorded by the wearable camera 10 are reproduced by the output unit 306, respectively. In the present embodiment, when reproducing the two recorded data RCD1 and RCD2, the CPU 301 arranges two screens (windows) in the output unit 306 (for example, a display) in a comparative manner and synchronizes the recorded times. To play. A method of reproducing the two recorded data RCD1 and RCD2 so that the recorded times are synchronized will be described later with reference to FIG. As a result, the person in charge in the police station having jurisdiction over the back-end system 100B can grasp the situation on the site extensively and clearly.

The memory 302 is configured using, for example, RAM, ROM, nonvolatile or volatile semiconductor memory, functions as a work memory when the CPU 301 operates, and stores a predetermined program and data for operating the CPU 301. . For example, when the CPU 302 instructs the I / O control unit 303 to reproduce (output) the two recorded data RCD1 and RCD2 (see FIGS. 7 and 8) read from the storage 308 by the CPU 301, the recorded data RCD1 and RCD2 are recorded. Is temporarily stored.

The I / O control unit 303 performs control related to data input / output between the CPU 301 and each unit of the back-end server SV (for example, the communication unit 304, the input unit 305, and the output unit 306). Relay data. The I / O control unit 303 may be configured integrally with the CPU 301.

The communication unit 304 performs wired or wireless communication with the in-vehicle camera system 65 of the front end system 100A or the

wearable cameras

10 and 10A via the management software 70. The communication unit 304 as an example of a receiving unit receives the recording data RCD1 and RCD2 transmitted from the in-vehicle camera system 65. The communication unit 304 may receive the recording data RCD2 directly transmitted from the

wearable cameras

10 and 10A.

The input unit 305 is a UI for receiving an input operation of a person in charge in the police station 5 having jurisdiction over the back-end system 100B and notifying the CPU 301 via the I / O control unit 303. It is a pointing device. The input unit 305 may be configured using, for example, a touch panel or a touch pad that is arranged corresponding to the screen output from the output unit 306 and can be operated with the finger of the person in charge or the stylus pen.

The output unit 306 includes, for example, a display device configured using an LCD or an organic EL and / or a speaker that outputs sound, and displays various data on a screen or outputs sound. For example, the output unit 306 captures (records) the recorded data RCD1 captured (recorded) by the wearable camera 10 and the in-vehicle camera system 65 in response to an input operation of a person in charge in the police station 5 having jurisdiction over the back-end system 100B. When the recorded video data RCD2 is input, the video included in the video data in each recorded data is displayed on a different screen under the instruction of the CPU 301.

The storage control unit 307 reads various data stored in the storage 308 or writes various data to the storage 308 in accordance with an instruction from the CPU 301 or the I / O control unit 303.

The storage 308 is configured by, for example, an SSD or an HDD, and stores recording data RCD1 captured and recorded by the in-vehicle camera system 65 (the in-vehicle camera 61), and recorded data RCD2 captured and recorded by the wearable camera 10. accumulate. Further, the storage 308 stores and accumulates recording data captured and recorded by the

wearable cameras

10 and 10A when the recording data is directly transferred from the

wearable cameras

10 and 10A. The storage 308 may store various data other than the recorded data. A plurality of storages 308 may be provided.

FIG. 5 is a schematic diagram showing a state where the wearable camera 10 is worn by the police officer 7. FIG. 6 is a front view illustrating an example of the appearance of the wearable camera 10. As shown in FIG. 5, the wearable camera 10 is attached to clothes or a body 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, for example. Used or attached to the hat via a clip or other fastener. With the wearable camera 10 attached, the police officer 7 operates the recording switch SW1 to image a surrounding subject.

As shown in FIG. 6, 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 in front of a substantially rectangular parallelepiped casing 10K. 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.

Attribute information addition switch SW3 is provided on the left side when viewed from the front of the housing 10K of the wearable camera 10. When the police officer 7 depresses the attribute information addition switch SW3, the attribute information (for example, theft, drunk driving, parking violation, etc.) corresponding to the set state is applied to the video data currently recorded or the video data recorded immediately before. ) Is given. The attribute information is classification information for identifying the type of video data. The attribute information is given according to the user's operation of the attribute information addition switch SW3 of the wearable camera 10, 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 relating to an incident that has occurred in the field, such as theft, drunk driving, or parking violation, is used.

The LEDs 26a to 26c are arranged on the upper surface when viewed from the front of the housing 10K of the wearable camera 10, as shown in FIG. Thereby, the police officer 7 can easily visually recognize the LEDs 26a to 26c in a state where the wearable camera 10 is worn. The LEDs 26a to 26c may not be seen by anyone other than the seven police officers. Further, although not shown, a contact terminal 23 is provided on the lower surface of the wearable camera 10 as viewed from the front of the housing 10K.

FIG. 7 is a diagram illustrating an example of a data structure of the recording data RCD1 captured by the in-vehicle camera 61. FIG. 8 is a diagram illustrating an example of a data structure of the recording data RCD2 imaged by the wearable camera 10. FIG. 9 is a diagram illustrating an example of a data structure of the frame parameter information FPM1 and FPM2 in the video data VDO1 and VDO2. FIG. 10 is a diagram illustrating an example of a data structure of the frame parameter information FPM1 in the video data VDO1 of the recording data RCD1 captured by the in-vehicle camera 61. FIG. 11 is a diagram illustrating an example of a data structure of the frame parameter information FPM2 in the video data VDO2 of the recording data RCD2 captured by the wearable camera 10.

In the wearable camera 10 and the in-vehicle camera 61 of the present embodiment, when video is captured and recorded, as shown in FIGS. 7 and 8, the captured video data VDO1 and VDO2, along with attribute information related to this video data. Meta information MTD1 and MTD2 including the data are generated and stored in the memory in each apparatus as recorded data RCD1 and RCD2 in which the two data are associated with each other. In other words, the recording data RCD2 stored in the memory (for example, the storage unit 15) of the wearable camera 10 includes video data VDO2 and meta information MTD2. Similarly, the recording data RCD1 captured and recorded by the in-vehicle camera 61 includes video data VDO1 and meta information MTD1. The recorded data RCD1 is stored in the storage 111 in the in-vehicle recorder 62. Note that the recorded data RCD1 and RCD2 are preferably transferred to and stored in the back-end server SV via the in-vehicle recorder 62 in terms of communication environment (for example, line speed). In other words, the recording data RCD2 imaged and recorded by the wearable camera 10 may be directly transferred from the wearable camera 10, but in order to shorten the transfer time, the in-vehicle recorder 62 sends video data or the like to the back-end server SV. Video data is transferred from the wearable camera 10 to the in-vehicle recorder 62 during a period in which the camera is not transferred (for example, movement time until patrol shift working hours end and return to the police station), and then the in-vehicle recorder 62 back-end server It is preferable to transfer to SV.

As shown in FIG. 9, the frame parameter information FPM1 and FPM2 are generated for each frame of the video imaged by the in-vehicle camera 61 and the wearable camera 10, and various information of the frame (for example, the recording time (second) of the frame, the frame Recording time (milliseconds), frame number in video data). In the frame parameter information FPM1 and FPM2 shown in FIG. 9, “Record time (sec)”, “Record time (msec)”, and “Frame count” are shown. “Record time (sec)” has a size of 4 bytes and indicates the recording time (second unit) of the frame. Specifically, it is the total number of seconds from a predetermined reference date. The predetermined reference date is not particularly limited, but may be, for example, January 1, 1970, or may be the first day of the year (for example, January 1, 2015). “Record time (msec)” has a size of 2 bytes and indicates the recording time of the frame (in milliseconds). Accordingly, the sum of “Record time (sec)” and “Record time (msec)” is the time (recording time) when the corresponding frame of the actual video data VDO1, VDO2 was recorded. “Frame count” has a size of 4 bytes and indicates a frame number in the video data VDO1 and VDO2.

10 and FIG. 11 will be described in more detail using specific examples.

In the frame parameter information FPM1 shown in FIG. 10, the video data VDO1 of the corresponding frame (frame number “1”) is captured and recorded by the in-vehicle camera 61 when “1002231 + 0.743” seconds have elapsed from the predetermined reference date. It will be. In other words, the time when “1002231 + 0.743” seconds have elapsed from the predetermined reference date is the recording start time of the video data VDO1. Similarly, in the frame parameter information FPM2 shown in FIG. 11, the video data of the corresponding frame (frame number “1”) is captured and recorded by the vehicle-mounted camera 61 when “10027272 + 0.057” seconds have elapsed from the predetermined reference date. It will be done. In other words, the recording start time of the video data VDO2 is the time when “1002722 + 0.057” seconds have elapsed from the predetermined reference date.

That is, according to the frame parameter information FPM1 and FPM2 shown in FIG. 10 and FIG. 11, the in-vehicle camera 61 and the wearable camera 10 are images obtained by imaging the same incident site, but the recording times are different and the synchronization is performed. This means that the in-vehicle camera 61 starts recording earlier than the wearable camera 10. In the present embodiment, the back-end server SV uses the frame parameter information FPM1 and FPM2 regarding the first frame in the video data VDO1 and VDO2 of the respective recording data RCD1 and RCD2 to reproduce the video data VDO1 and VDO2. Start.

Next, an operation procedure for synchronizing the system time between the in-vehicle camera system 65 and the wearable camera 10 will be described with reference to FIG. FIG. 12 is a flowchart for explaining an example of an operation procedure in which the wearable camera 10 according to the present embodiment synchronizes time with the in-vehicle camera system 65. As a premise of the description of FIG. 12, the in-vehicle camera 61 and the in-vehicle recorder 62 in the in-vehicle camera system 65 are synchronized (that is, coincident) with the system time.

12, the wearable camera 10 executes initial processing of the wearable camera 10 main body (S1). The initial processing is, for example, reading initial setting values for various processing into the memory (for example, the storage unit 15) of the wearable camera 10 or booting the OS (Operating System) of the wearable camera 10 to set each value of the wearable camera 10 To read each and make it operable.

The wearable camera 10 determines whether or not it is within the communication area (communication area) of the in-vehicle camera system (ICV) 65 after completing the initial process of step S1 (S2). If it is determined that the wearable camera 10 is not within the communication range of the in-vehicle camera system 65 (S2, NO), the operation of the wearable camera 10 proceeds to step S5. On the other hand, when the wearable camera 10 determines that it is within the communication range of the in-vehicle camera system 65 (S2, YES), it establishes a communication link with the in-vehicle camera system 65 (S3).

After step S3, the wearable camera 10 accesses the in-vehicle camera system 65, and the system time counting unit 19A of the wearable camera 10 makes the system time match (that is, synchronizes) with the in-vehicle camera system 65. Adjust the output (system time). As for the time adjustment for synchronizing the system time, for example, an in-vehicle camera system 65 (either in-vehicle camera 61 or in-vehicle recorder 62) is provided with an NTP server, and the wearable camera 10 accesses this NTP server to access the system. Adjustment is possible by obtaining the time. Alternatively, a unique protocol for adjusting the system time between the wearable camera 10 and the in-vehicle camera system 65 may be used. Note that FIG. 12 describes the synchronization of the system time between the in-vehicle camera system 65 and the wearable camera 10, but the description of FIG. 12 synchronizes the system time between the wearable camera 10 and the wearable camera 10A. The same applies to the case of doing so.

After step S4, the wearable camera 10 waits for a trigger to start recording (S5). That is, the wearable camera 10 stands by until a trigger operation for starting recording (for example, pressing of the recording switch SW1 or starting automatic recording when a predetermined condition is satisfied) is performed.

Note that the processing of steps S2 to S4 shown in FIG. 12 (see dotted lines) is periodically repeated by the wearable camera 10. Even if it is determined in step S2 that the wearable camera 10 is not within the communication range of the in-vehicle camera system 65, the wearable camera 10 and the in-vehicle camera system 65 are different when the recording data is transmitted to the back-end server SV. This is because the system time needs to be synchronized (in other words, the process of step S4 needs to be executed). Accordingly, the processing of steps S2 to S4 shown in FIG. 12 needs to be repeated not only once but also taking into account that the police officer 7 wearing the wearable camera 10 moves, for example. Thereby, when the police officer 7 wearing the wearable camera 10 moves, the wearable camera 10 and the in-vehicle camera system 65 can synchronize the system time when the wearable camera 10 enters the communication range of the in-vehicle camera system 65. It is.

Although FIG. 12 illustrates an operation procedure related to time synchronization between the wearable camera 10 and the in-vehicle camera system 65, the wearable camera 10 transfers (uploads), for example, recorded data RCD2 to the back-end server SV. The system time may be synchronized with the back-end server SV of the back-end system 100B using the same processing as in steps S2 to S4 shown in FIG. Furthermore, the in-vehicle recorder 62 of the in-vehicle camera system 65 synchronizes the system time with the back-end server SV of the back-end system 100B, for example, during or before the recording data RCD1 is transferred (uploaded) to the back-end server SV. May be. In this case, the back-end system 100B holds an NTP server (not shown), and the back-end server SV adjusts the system time by periodically accessing the NTP server.

Next, an operation procedure in which the back-end server SV of the present embodiment reproduces the video data VDO1 and VDO2 of the recorded data RCD1 and RCD2 captured by the wearable camera 10 and the in-vehicle camera 61 will be described with reference to FIG. . FIG. 13 is a flowchart illustrating an example of an operation procedure in which the back-end server SV of the present embodiment reproduces the video data VDO1 and VDO2 of the recorded data RCD1 and RCD2 captured by the wearable camera 10 and the in-vehicle camera 61, respectively. As a premise of the description of FIG. 13, the recording data RCD1 captured by the in-vehicle camera 61 and the recording data RCD2 captured by the wearable camera 10 are stored in the storage 308 of the back-end server SV, and the wearable camera 10 and the in-vehicle camera are recorded. Each system time is synchronized with the system 65 according to the method shown in FIG.

In FIG. 13, the back-end server SV reads the recording data RCD1 captured by the in-vehicle camera 61 from the storage 308 into the memory 302, and acquires the recording start time information (S11). That is, the back-end server SV acquires information indicating when the in-vehicle camera 61 starts recording the first frame of the video data VDO1 based on the frame parameter information FPM1 included in the video data VDO1 in the recording data RCD1. (S11).

Similarly, the back-end server SV reads the recording data RCD2 imaged by the wearable camera 10 from the storage 308 into the memory 302 and acquires the recording start time information (S12). That is, the back-end server SV acquires information indicating when the wearable camera 10 starts recording the first frame of the video data VDO2 based on the frame parameter information FPM2 included in the video data VDO2 in the recording data RCD2. (S12).

The back-end server SV determines whether or not the recording start time of the video data VDO1 of the recording data RCD1 is earlier than the recording start time of the video data VDO2 of the recording data RCD2 (S13). When the back-end server SV determines that the recording start time of the video data VDO1 of the recording data RCD1 is ahead of the recording start time of the video data VDO2 of the recording data RCD2 (S13, YES), the in-vehicle camera system 65 The reproduction of the video data VDO1 of the recording data RCD1 that has been imaged and recorded is started and the video is output to the screen (S14).

The back-end server SV starts playback of the video data VDO1 and then reaches the recording start time of the video data VDO2 of the recording data RCD2 imaged by the wearable camera 10 (S15, YES), that is, the video data VDO1. From the start of playback, “Record time (sec)” of the frame parameter information FPM2 related to the first frame of the video data VDO2, and “Record time (msec)” and “Record time (sec) of the frame parameter information FPM1 related to the first frame of the video data VDO1 ”+“ Record time (msec) ”When the time corresponding to the difference has elapsed, the playback of the video data VDO2 starts on a playback screen different from the playback screen of the video data VDO1 and the video is output That (S16).

Here, when the video data VDO1 and VDO2 are completed, or when the playback of the video data VDO1 and VDO2 is stopped by the operation of the person in charge in the police station 5 having jurisdiction over the back-end system 100B, The end server SV ends the reproduction of the video data VDO1 and VDO2.

On the other hand, when the back-end server SV determines that the recording start time of the video data VDO1 of the recording data RCD1 is not ahead of the recording start time of the video data VDO2 of the recording data RCD2 (S13, NO), the wearable camera 10 The reproduction of the video data VDO2 of the recording data RCD2 that has been imaged and recorded is started and the video is output to the screen (S18).

The back-end server SV starts playback of the video data VDO2 and then reaches the recording start time of the video data VDO1 of the recording data RCD1 imaged by the in-vehicle camera system 65 (S19, YES), that is, the video data VDO2. “Record time (sec)” + “Record time (msec)” of the frame parameter information FPM1 related to the first frame of the video data VDO1, and “Record time (sec) of the frame parameter information FPM2 related to the first frame of the video data VDO2. ) ”+“ Record time (msec) ”When the time corresponding to the difference has elapsed, the playback of the video data VDO1 is started on the playback screen different from the playback screen of the video data VDO2, and the video is output. That (S20).

As described above, in the wearable camera system 100 of the present embodiment, the wearable camera 10 captures an image of the situation of the scene where the police officer 7 rushes, and the in-vehicle camera system 65 ( Specifically, the in-vehicle camera 61) captures an image of the situation at the same site. The back-end server SV receives the recording data RCD2 having the video data VDO2 and the recording data RCD1 having the video data VDO1, and stores the recording data RCD1 and the recording data RCD2 in association with each other in the storage 308. The back-end server SV can associate the recorded data RCD1 with the recorded data RCD2 by assigning a common case number, for example. Further, the back-end server SV uses the frame parameter information related to the first frame of the video data VDO1 and the frame parameter information related to the first frame of the video data VDO2 to reproduce the video data VDO1 and the video data VDO2 in synchronization.

Accordingly, when the wearable camera system 100 reproduces a plurality of video data VDO1 and VDO2 captured in the same incident on the back-end server SV, the playback times of the video data VDO1 and VDO2 captured at different angles are synchronized. As a result, the situation of the scene where the police officer 7 rushed can be easily grasped extensively and clearly. For example, when the situation in the field that is not completely imaged by one camera (for example, the in-vehicle camera 61) can be imaged by the other camera (for example, the wearable camera 10) at that time, the wearable camera system 100 is The situation (for example, time-series context in the same case, victim, suspect, surrounding visitors) can be accurately grasped. Since the in-vehicle camera 61 is installed in the police car, for example, even if the video data VDO1 captured and recorded by the in-vehicle camera 61 is blocked by a police officer or an obstacle, the image is not captured. Since the playback times of the data VDO and VDO2 are synchronized, the person in charge in the police station 5 having jurisdiction over the back-end system 100B can view the video of the blocked portion in the video data VDO2 captured and recorded by the wearable camera 10. It becomes possible to grasp.

In the present embodiment, the video data VDO1 has been described as video data captured and recorded by the in-vehicle camera 61, but it may be video data captured and recorded by the wearable camera 10A shown in FIG. As a result, when the reproduction times of the video data captured and recorded by the plurality of

wearable cameras

10 and 10A are reproduced in synchronization, the back-end server SV broadens the situation at the scene at the time of imaging (recording time). It becomes possible to grasp.

Further, the wearable camera 10 of the present embodiment synchronizes with the system time of the in-vehicle camera 61 (in other words, the system time of the in-vehicle camera system 65) when in the communication range of the in-vehicle camera 61. Thus, when the wearable camera 10 enters the communication range of the in-vehicle camera 61 due to the movement of the police officer 7 wearing the wearable camera 10, the system time of the in-vehicle camera 61 (in other words, the system of the in-vehicle camera system 65). The system time of wearable camera 10 itself can be adjusted to coincide with (time).

In addition, the wearable camera 10 of the present embodiment periodically determines whether or not the vehicle-mounted camera 61 is within the communication range. Thereby, even when wearable camera 10 determines that it is once out of the communication range of in-vehicle camera 61, for example, when police officer 7 wearing wearable camera 10 moves into the communication range of in-vehicle camera 61, The system time of the wearable camera 10 itself can be adjusted to coincide with the system time of the in-vehicle camera 61.

Further, the back-end server SV of the present embodiment reproduces video data corresponding to the preceding recording time when one of the recording times indicated by the frame parameter information FPM1 and FPM2 of the video data VDO1 and VDO2 precedes. Is started first, and when the other recording time coincides with one recording time, reproduction of video data corresponding to the other recording time is started. Thereby, even when the time when the back-end server SV is captured and recorded by the wearable camera 10 and the in-vehicle camera 61 is different, the recording time information of each frame parameter FPM1, FPM2 included in the video data VDO1, VDO2 is obtained. By using this recording time information, it is possible to reproduce the video data VDO1 and VDO2 so that the recording times coincide with each other, and to accurately output the on-site situation.

Although various embodiments have been described above with reference to the drawings, it goes without saying that the present disclosure 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 disclosure. Is done. In addition, the constituent elements in the above embodiments may be arbitrarily combined without departing from the spirit of the present disclosure.

For example, when the performance of the CPU 301 of the back-end server SV is not sufficiently good, the reproduction times of the video data VDO1 and VDO2 may be shifted. Therefore, the back-end server SV periodically determines whether or not there is a difference in the reproduction time of the video data VDO1 and VDO2 after step S16 or step S20, and adjusts the difference if it is determined that there is a difference. May be. That is, the back-end server SV controls the video data VDO1 and VDO2 output on the two screens (two windows) to slow down the playback speed of one or both of the video data so that no deviation occurs in the playback time. It is preferable.

The present disclosure is useful as a wearable camera system and a video data reproduction synchronization method for reproducing a plurality of video data obtained by imaging the same incident and synchronizing the reproduction times of the respective video data so as to easily grasp the situation in the field. It is.

5 Police station 6 Police car 7

Police officer

10, 10A Wearable camera 11

Imaging unit

12, 108 GPIO
13,105 RAM
14 ROM
15 Storage unit 16 EEPROM
17 RTC
18,107 GPS
19 MCU
19A System

time counting unit

21, 102, 203, 304 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
100 Wearable Camera System 100A Front-end System 100B Back-

end System

101, 201, 301 CPU
104 flash ROM
106 Microcomputer 109 Switch 110 LED
111 Storage 202, 303 I /

O control unit

204, 302

Memory

205, 305 Input unit 206 Display unit 207 Speaker SV Back-end server 306 Output unit 307 Storage control unit 308 Storage

Claims

A wearable camera system including at least a first wearable camera that can be worn by a user and a server,
The server
A communication unit that receives first video data captured by the first wearable camera and second video data captured by an external device;
A storage unit for storing the first video data and the second video data received by the communication unit in association with each other;
A playback unit for playing back the first video data and the second video data stored in the storage unit,
The first video data has first recording time information captured by the first wearable camera,
The second video data has second recording time information captured by the external device,
The playback unit uses the first recording time information and the second recording time information to play back the first video data and the second video data in synchronization.
Wearable camera system.
The wearable camera system according to claim 1,
The external device is an in-vehicle camera mounted on a vehicle on which the user rides.
Wearable camera system.
The wearable camera system according to claim 1,
The external device is a second wearable camera different from the first wearable camera;
Wearable camera system.
The wearable camera system according to claim 1,
The first wearable camera synchronizes with the time of the external device when in the communication range of the external device,
Wearable camera system.
The wearable camera system according to claim 4,
The first wearable camera periodically determines whether or not the external device is in a communication range,
Wearable camera system.
The wearable camera system according to claim 1,
The playback unit starts playback of video data corresponding to the one recording time when one of the first recording time information and the second recording time information precedes, and the other recording time information When the recording time coincides with the one recording time, the video data corresponding to the other recording time is started to be reproduced.
Wearable camera system.
A method for synchronously reproducing video data in a wearable camera system including at least a first wearable camera that can be worn by a user and a server,
Taking an image with the first wearable camera,
Capture the video with an external device,
Receiving first video data imaged by the first wearable camera and second video data imaged by the external device;
Associating the first video data having the first recording time information imaged by the first wearable camera with the second video data having the second recording time information imaged by the external device Stored in the server
Using the first recording time information and the second recording time information, the first video data and the second video data stored in the server are reproduced in synchronization.
Video data synchronized playback method.